Invoice price drift is the accumulating gap between the rate a contract specifies and the rate suppliers actually invoice. It is rarely dramatic — a few percent on a line, a superseded rate applied after a renewal, an escalation clause applied early — but it compounds across thousands of lines and years of a master agreement, and it stays invisible for one structural reason: the negotiated rate lives in a PDF that no invoice process ever reads.
Why drift happens without anyone deciding it
Almost none of it is bad faith. Supplier billing systems carry stale rate cards. Renegotiated discounts are applied to new orders but not open ones. Unit-of-measure ambiguity lets a per-item rate bill per-pack. Service call-offs reference "the agreement" without anyone confirming which revision. Each error is small enough to pass approval thresholds; the sum is a standing leak that spend analysis attributes to "price variance" months later.
Why manual checking cannot fix it
The arithmetic is against you: verifying an invoice line means finding the governing contract, locating the current rate table inside it, and matching item, unit, and validity period — several minutes per line, against invoices with hundreds of lines. Teams rationally sample instead, and drift lives in the unsampled majority.
How much drift is normal?
Industry discussions of procurement leakage commonly place total spend leakage — of which invoice drift is one component — in the low single digits of managed spend. The exact figure matters less than its shape: drift concentrates in long-running master agreements with rate tables, in categories with unit-of-measure ambiguity, and in service billing where scope and rate meet loosely. A useful self-test: pick your ten highest-spend agreements and ask how many invoice lines from the last quarter were checked against the contract’s current rate table, item by item. In most organisations the honest answer is a sample, or none — and the drift lives precisely there.
It is also worth separating the two directions of loss. Drift is being billed above the agreed rate. The quieter twin is the agreed rate itself going stale against a falling market — fully compliant invoices, correctly checked, faithfully overpaying. A live pricebook is the prerequisite for catching both: one by checking invoices against it, the other by checking it against the market.
The fix: make the contract machine-readable
Drift ends when the negotiated rate becomes structured data. dmp's contract registry extracts signed agreements into live pricebooks — every rate, unit, and validity window as data — so invoice lines can be checked against the governing rate automatically and exceptions surface as they happen, not at the annual audit. Paired with optimization alerts, the same pricebook also tells you when a correctly-billed rate has drifted from the market — the other kind of leak.
The takeaway: price drift is not a discipline problem, it is a data-format problem. Contracts stored as documents leak; contracts stored as pricebooks defend themselves.