3PL Rate Mismatch: Check Billed vs Contracted Rates

What a 3PL rate mismatch means

A rate mismatch is a supported difference between the billed unit rate and the governing contract rate for the same charge event. A historical rate, public benchmark, broad category match, or number from the wrong effective period cannot establish the expected amount.

The strongest comparison ties one invoice line to one active rate rule using a provider charge code or unambiguous description, compatible unit, matching facility or channel, event date, currency, and contract scope.

Evidence required

The raw invoice line with quantity, billed rate, billed amount, service date, currency, references, and source coordinate.
The signed rate card or pricing exhibit plus the governing MSA, SOW, and amendments.
The exact contract rule: charge code, unit, recurrence, scope, conditions, effective range, and citation.
Any operational fact used by the rule, such as item count, shipment weight, zone, packaging, or service level.
The dispute-window clause and supported anchor date.

The calculation

Unit-rate comparisoncandidate variance = billed amount − (supported quantity × active contract rate)

Synthetic example

Invented rates, quantities, references and amounts; not a customer record or provider allegation.

An invented invoice bills 800 orders × $1.40 = $1,120. The cited invented active unit-rate rule prices the same 800 orders × $1.25 = $1,000. Candidate variance: $120 for review.

The $120 is not automatically owed, claimable, submitted, credited, or recovered.

Use exact decimal arithmetic and the contract’s rounding rule. If the invoice amount does not equal displayed quantity × displayed rate, preserve that separate line-extension question instead of forcing both issues into one formula.

Why the unit guard exists: the versioned engineering corpus exposed a case where a displayed quantity was actually a percentage base. The arithmetic tied exactly while the unit was incompatible with the candidate rule. See the corpus regression that changed the rate check.

Which rate was active on the event date?

Identify the invoice line’s service or event date.
Find every rate-card version and amendment that could cover it.
Apply the agreement’s document-precedence language.
Confirm facility, channel, service level, charge condition, currency, and unit.
Store the selected rule and every conflicting or missing source.

A later invoice date does not automatically move an earlier service into a newer rate period. An amendment may also override only one charge family. Read how to read a 3PL rate card before normalizing the expected rule.

Strong code match versus category-only match

An explicit invoice code mapped to the same contract code is stronger than a broad semantic category. “Storage” may refer to pallets, bins, cubic feet, seasonal surcharges, or aged inventory. Category-only matches should remain review-only until the intended rule is resolved.

What can explain the difference?

A signed amendment or written concession changed the rate.
The billed quantity and the contract rate use different units.
A service condition, facility, channel, weight band, zone, or packaging rule selects another price.
A tier, minimum, allowance, surcharge, percentage base, or external index changes the expected amount.
The invoice uses another currency or a contract-defined conversion and rounding method.
The line description mapped to the wrong contract category.

Unresolved explanations become explicit blockers. Do not select a favorable assumption merely because the math then produces a larger variance.

How Auditario treats this check

Exact flat, unit, first/additional, and matrix comparisons can be Verified-eligible in principle when inputs, citations, mapping, window, and the exact check/provider/layout cell are certified. Percentage, cost-plus, tier, time-tier, and minimum mechanics have stricter review ceilings.

Review today

Auditario is prelaunch: secure document intake is not open, there are 0 certified publication cells, and $0 is presently claimable. No current rate candidate can be published as a provider allegation. Read the methodology, inspect the synthetic sample, and see the current product status.