Contract leakage: most savings die after signature

A procurement team spends four months negotiating a software contract. They lock in a 3% annual price cap, quarterly volume rebates starting at $500K, and service credits if uptime falls below 99.5%. The ink dries. Six months later, the supplier raises prices 4.2% because nobody checked the cap clause. The rebate is never claimed because AP does not know the threshold was hit. The service credits expire because nobody tracks uptime. The contract delivered 60% of what was negotiated. This is contract leakage — and it costs companies 8-12% of contract spend every year.

The signature-to-invoice gap is where value dies

Procurement negotiates. Accounts payable pays. Between those two functions sits a gap that no one owns. The contract has 40 pages of commercial terms — price escalation limits, volume thresholds, rebate schedules, service level credits, audit rights. The invoice has four fields: amount, date, PO number, supplier name. AP matches the invoice to the PO, not to the contract. Every clause that requires someone to check, calculate, or enforce is a clause that will not be enforced.

The gap is organizational, not technical. 57% of CPOs identify siloed working as the single biggest barrier to value delivery, according to Deloitte's Global CPO Survey. Contract value lives in a PDF on a shared drive. Invoice data lives in the ERP. Nobody connects the two systematically.

"Most organizations treat the contract as a negotiating artifact, not a performance instrument. Once it's signed, it goes into a drawer. The value negotiated at the table never reaches the P&L because there is no governance bridge."
— Procurement advisory firm benchmark analysis

---

The four silent drains on contract value

Price escalation is the biggest single leak. A contract with a 3% annual cap lets the supplier raise 3% — but if nobody validates the invoice against the cap, the actual increase can be 5%, 7%, or more. A study by procurement advisory firms found that in organizations without automated contract compliance checks, approximately 60% of contracts with escalation caps had at least one invoice exceeding the cap in a given year.

Volume rebates are second. A supplier agrees to pay 2% back when annual spend crosses $1M. The buyer crosses $1.2M. The rebate is $24,000. But the rebate clause says "buyer must submit a claim within 60 days of year-end." Nobody in procurement tracks cumulative spend against rebate thresholds. Nobody in finance knows the rebate clause exists. The $24,000 stays with the supplier.

---

Why AP cannot fix this — and procurement should not expect them to

Accounts payable processes invoices. Their KPIs are processing speed, accuracy against the PO, and payment cycle time. AP does not read contracts. They are not trained to interpret escalation clauses. They are not measured on rebate capture. Expecting AP to enforce contract terms is like expecting the warehouse team to conduct supplier audits — wrong function, wrong incentives, wrong tools.

The fix is a dedicated contract governance function positioned between procurement and finance. This is not a full-time role for every contract — it is a lightweight process that flags high-value contracts for quarterly review. A $50K contract with a single line item needs less governance than a $2M multi-year agreement with five commercial levers.

---

What contract governance looks like, in practice

Three things. First: a living tracker of active contracts mapped to their commercial terms — price caps, rebate thresholds, SLA credits, discount windows. Not a PDF. A structured record that someone updates when spend data changes.

Second: a quarterly review cadence. Not annual. Quarterly is frequent enough that rebate claims are still within their filing window and escalation violations have not compounded across multiple invoices. The review compares actual spend and performance against contracted terms and flags variances.

Third: contract terms designed for enforceability. A rebate clause that says "supplier shall calculate and pay rebates quarterly" is enforceable. One that says "buyer may claim rebates within 60 days of year-end upon written request" transfers all the work to the buyer. Most contracts use the second version. Procurement negotiators should insist on the first.

---

What this means in practice

1. Audit your top 20 contracts by spend. Pull the contract PDF. Compare negotiated price caps against actual invoices. Check whether rebate thresholds were crossed and whether claims were filed. Expect to find 2-3 contracts with recoverable leakage immediately. Timeframe: 2-4 weeks.
2. Build a contract governance tracker. A spreadsheet is sufficient for the first year. Columns: supplier, contract value, key commercial terms (price cap, rebate schedule, SLA credit), actual spend YTD, variance, status. Assign one person to update it quarterly. Timeframe: 1 month to build, ongoing.
3. Change the rebate clause in your template. Replace "buyer may claim" with "supplier shall calculate and pay." Move the burden to the party that already has the data. Timeframe: next contract cycle.
4. Give AP a one-page contract summary per high-value supplier. Not the full contract — a single sheet with the commercial terms AP needs to catch before paying. Price cap, discount window, anything that affects the payment amount. Timeframe: 1 week per top-20 contract.
5. Measure realized vs negotiated savings. If your procurement team reports $5M in negotiated savings but finance sees $3M on the P&L, the $2M gap is leakage. Track it quarterly and report it alongside the savings number. What gets measured gets governed. Timeframe: starting next quarter.

---