Why contract compliance quietly erodes margin
Leakage is rarely one big failure. It is many small gaps between what was negotiated and what gets billed — and why checking invoices against the contract, not the purchase order, changes the number.
Contract leakage is rarely a single large failure. It is the accumulation of small, individually unremarkable differences between what was negotiated and what is actually billed — and because each one looks trivial, none of them gets escalated.
Where the money goes
Across the engagements behind our platform, roughly 8.6% of contracted spend is lost to leakage before anyone notices. It surfaces in a handful of recurring places:
- Invoices priced above the agreed contracted rate
- Discounts and rebates that were negotiated but never applied
- Duplicate or erroneous payments inside high-volume categories
- Off-contract buying that quietly bypasses the agreement entirely
Individually these are small. Aggregated across a full spend population, they are the difference between a contract that performs and one that only appears to.
Why it survives review
Most finance teams check invoices against the purchase order, not against the contract. That catches arithmetic, not entitlement — an invoice can be perfectly correct against its PO and still be priced above the rate that was agreed. Pricing errors show up on roughly one in four invoices when the contract itself is used as the reference point.
What changes when the contract is the baseline
Benchmarking every invoice line against the contract, continuously rather than in an annual sample, turns leakage from something discovered afterwards into something prevented. Managed that way, compliance on covered spend runs at about 97%, and the recovered value is straight EBITDA — it was already budgeted and already paid.
The work is unglamorous and relentless, which is precisely why it suits a platform rather than a person. If you would like to see what it finds in your own spend, a no-cost assessment quantifies it in about 30 days.