GuardianPrice
← Resources

Unit-of-measure normalization: the quiet source of fake variances

6 min read

If your first invoice audit produced a list of 300% overcharges, you almost certainly have a unit-of-measure problem rather than a supplier problem. Nothing destroys trust in an audit faster than walking into a supplier meeting with variances that evaporate on inspection.

Why it happens

Contracts are negotiated in the unit the buyer thinks in. Invoices are printed in the unit the supplier's ERP ships in. Neither side is wrong, and neither side maintains a mapping. The mapping has to live in your audit layer.

Build an alias table, per supplier

A global UoM dictionary is not enough, because the same abbreviation means different things to different distributors. 'BD' is a bundle at one and a board at another. Keep aliases scoped to the supplier, with a global fallback, and require an explicit conversion factor rather than inferring one.

  • Store the raw invoice unit, the raw contract unit, the canonical unit and the factor used — audits must be explainable.
  • Convert quantity and price together; converting only one silently doubles the error.
  • Where no factor exists, mark the line unmatched with reason 'unit mismatch' instead of guessing.
  • Review new aliases as part of supplier onboarding, not as a firefight during a dispute.

Measure the payoff

Track unmatched-by-unit-mismatch as its own metric per supplier. It should trend to near zero within two import cycles. If it does not, the supplier is changing units mid-contract, which is itself worth raising at renewal.

Related reading

New to the vocabulary? The glossary defines every term used here, and the audit checklist turns it into a process.

See this on your own invoices

Audit your first 500 invoice lines free. No card required.