Unit of measure mismatch: paid per case, billed per each

Unit of measure mismatch is a margin drift type where an invoice bills quantity in a different unit than the contract's rate is priced on. Read the full guide.

Twitter LinkedIn WhatsApp
Ask AI: ChatGPT Claude Gemini Grok
Unit of measure mismatch: paid per case, billed per each

Unit of measure mismatch is a form of margin drift where the invoice bills a quantity in one unit while the contract prices that same line in another, and no one converts between them before payment. A pallet gets billed as a case, a ton gets billed as a short ton, a linear foot gets billed as a square foot. The dollar amount looks plausible on its own, so it clears review.

Unit of measure mismatch survives approval because the invoice reads correctly in isolation. AP checks that a quantity was received and that a price was applied to it. Neither check asks whether the quantity's unit matches the unit the contract's rate card was built on.

A vendor billing 40 units at the contracted per-unit rate looks identical whether those 40 units are cases or pallets. The mechanism is a silent substitution, not a price change, which is why it does not show up as a rate increase anywhere in the ERP.

Correcting it requires reading the contract's unit definition next to the invoice's unit label, line by line, not just matching the numbers.

1. What is unit of measure mismatch?

Unit of measure mismatch is when a vendor invoice states a quantity in a different unit than the one the contract's rate card is priced on, so the contracted rate gets multiplied against the wrong base quantity. It is not a price change and not a rate card violation on its face. It happens at the point where a physical quantity is converted into a billing line, and it produces an invoice total that looks internally consistent even though it.

It differs from a rate card violation because the rate itself is often correct. The error sits entirely in the quantity's unit, which is why it can pass a rate check cleanly.

2. How does unit of measure mismatch happen on a real invoice?

It happens when a vendor's billing system defaults to its own standard unit while the contract was negotiated in a different one, commonly weight versus count, case versus each, or linear versus square measure. The vendor's warehouse or dispatch system records quantity the way it always has, and that figure flows to the invoice unchanged, without a conversion step that checks it against the contract's stated unit.

Freight, packaging, and MRO categories carry this risk because physical goods are measured multiple ways, and each conversion between them is a place the label can drift silently from the contracted one.

3. Which categories carry this risk?

Unit of measure mismatch concentrates in categories where the same physical good has more than one legitimate way to be counted or measured. Freight and 3PL, packaging and corrugate, MRO and Class C consumables, and equipment rental all carry it because weight, count, and volume conversions sit between the vendor's operational system and the invoice line, and each conversion is a place the stated unit can drift from the contracted one.

No single category is immune to it; these are simply where the conversion step is most exposed to error.

  • Freight and 3PL: Weight, cube, and pallet count are each valid billing units for the same shipment, and contracts do not always specify which one governs.
  • Packaging and corrugate: Sheets, cases, and pallets nest inside each other, so a single conversion error compounds across the invoice.
  • MRO and Class C consumables: Bulk items sold by weight or length get billed by each, or the reverse.
  • Equipment rental: Daily versus weekly versus monthly rate bases can be mislabeled as a simple unit count.

4. How is unit of measure mismatch caught and prevented?

Catching it requires reading the contract's unit definition against the invoice's unit label on every line, not just checking that a rate was applied correctly, because three-way matching confirms quantity and price but does not test whether the quantity's unit matches the one the rate was negotiated on. Prevention means stating the billing unit explicitly in the contract and rejecting invoices whose unit label does not match it.

This is a mechanical, line-level check once the contract states the unit, not a judgment call left to whoever approves the invoice.

For the wider pattern this sits inside, start with the margin drift guide.

5. Frequently Asked Questions (People Also Ask)

What is unit of measure mismatch in simple terms?

It is when an invoice bills a quantity using a different unit of measure than the one the contract's price was set against, such as billing by the case when the contract prices by the pallet, so the correct rate gets applied to the wrong quantity.

Is unit of measure mismatch the same as a rate card violation?

No. A rate card violation is charging the wrong price for a correctly stated unit. Unit of measure mismatch is charging the contracted price against a quantity stated in the wrong unit, which changes the effective price without changing the rate on paper.

Does three-way matching catch unit of measure mismatch?

Three-way matching checks that the invoice quantity matches the purchase order and receipt, and that the price matches the agreed rate. It does not check whether the unit those quantities are expressed in matches the unit the contract's rate was negotiated on.

Which contract terms prevent unit of measure mismatch?

A contract that states the billing unit explicitly for every priced line, for example per pallet with 48 units per pallet stated, removes the ambiguity a vendor's default billing system might otherwise introduce.

Can unit of measure mismatch happen without any wrongdoing by the vendor?

Yes. It commonly originates in a vendor's own operations or dispatch system defaulting to its standard unit, not in an intentional overbill. The result on the invoice is the same regardless of intent.

How is unit of measure mismatch different from index escalation misapplied?

Index escalation misapplied concerns the rate itself moving against the wrong index or trigger. Unit of measure mismatch concerns the quantity the rate is multiplied against being stated in the wrong unit. Either can occur independently of the other on the same invoice.

What data does an AP team need to check for unit of measure mismatch?

The contract's stated billing unit for each priced line, the invoice's stated unit for the same line, and the underlying receiving or shipping record in its native unit, so the conversion can be verified rather than assumed.

Does this affect fixed-price contracts?

It affects any contract priced per unit, whether the rate itself is fixed or tiered. A fixed per-unit rate applied to a mismatched unit still produces an incorrect total.

1. What is unit of measure mismatch?

Unit of measure mismatch is when a vendor invoice states a quantity in a different unit than the one the contract's rate card is priced on, so the contracted rate gets multiplied against the wrong base quantity. It is not a price change and not a rate card violation on its face. It happens at the point where a physical quantity is converted into a billing line, and it produces an invoice total that looks internally consistent even though it. It differs from a [rate card violation](/glossary/rate-card) because the rate itself is often correct. The error sits entirely in the quantity's unit, which is why it can pass a rate check cleanly.

2. How does unit of measure mismatch happen on a real invoice?

It happens when a vendor's billing system defaults to its own standard unit while the contract was negotiated in a different one, commonly weight versus count, case versus each, or linear versus square measure. The vendor's warehouse or dispatch system records quantity the way it always has, and that figure flows to the invoice unchanged, without a conversion step that checks it against the contract's stated unit. Freight, packaging, and MRO categories carry this risk because physical goods are measured multiple ways, and each conversion between them is a place the label can drift silently from the contracted one.

3. Which categories carry this risk?

Unit of measure mismatch concentrates in categories where the same physical good has more than one legitimate way to be counted or measured. Freight and 3PL, packaging and corrugate, MRO and Class C consumables, and equipment rental all carry it because weight, count, and volume conversions sit between the vendor's operational system and the invoice line, and each conversion is a place the stated unit can drift from the contracted one. No single category is immune to it; these are simply where the conversion step is most exposed to error. - Freight and 3PL: Weight, cube, and pallet count are each valid billing units for the same shipment, and contracts do not always specify which one governs. - Packaging and corrugate: Sheets, cases, and pallets nest inside each other, so a single conversion error compounds across the invoice. - [MRO and Class C consumables](/glossary/mro-and-class-c-consumables-audit): Bulk items sold by weight or length get billed by each, or the reverse. - Equipment rental: Daily versus weekly versus monthly rate bases can be mislabeled as a simple unit count.

4. How is unit of measure mismatch caught and prevented?

Catching it requires reading the contract's unit definition against the invoice's unit label on every line, not just checking that a rate was applied correctly, because three-way matching confirms quantity and price but does not test whether the quantity's unit matches the one the rate was negotiated on. Prevention means stating the billing unit explicitly in the contract and rejecting invoices whose unit label does not match it. This is a mechanical, line-level check once the contract states the unit, not a judgment call left to whoever approves the invoice. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide.

Questions & Answers

What is unit of measure mismatch in simple terms?

It is when an invoice bills a quantity using a different unit of measure than the one the contract's price was set against, such as billing by the case when the contract prices by the pallet, so the correct rate gets applied to the wrong quantity.

Is unit of measure mismatch the same as a rate card violation?

No. A rate card violation is charging the wrong price for a correctly stated unit. Unit of measure mismatch is charging the contracted price against a quantity stated in the wrong unit, which changes the effective price without changing the rate on paper.

Does three-way matching catch unit of measure mismatch?

Three-way matching checks that the invoice quantity matches the purchase order and receipt, and that the price matches the agreed rate. It does not check whether the unit those quantities are expressed in matches the unit the contract's rate was negotiated on.

Which contract terms prevent unit of measure mismatch?

A contract that states the billing unit explicitly for every priced line, for example per pallet with 48 units per pallet stated, removes the ambiguity a vendor's default billing system might otherwise introduce.

Can unit of measure mismatch happen without any wrongdoing by the vendor?

Yes. It commonly originates in a vendor's own operations or dispatch system defaulting to its standard unit, not in an intentional overbill. The result on the invoice is the same regardless of intent.

Margin Drift Resources