Identified, negotiated and realized savings are not the same
An analysis may identify a lower price, a sourcing project may negotiate it, and a contract may record it. None of those stages proves that the organisation actually purchased at the new terms. Realized savings require eligible demand to move to the selected supplier, use the correct item or service, follow the agreed price and remain compliant throughout the measurement period.
Spend leakage is the gap created when that operating path breaks. It includes purchases from non-preferred suppliers, outdated catalog prices, unapproved substitutions, late purchase orders, invoice exceptions and volumes that never move to the awarded agreement. The issue is therefore cross-functional: procurement can negotiate value, but requesters, approvers, suppliers, finance and systems all influence whether it is captured.
Where spend leakage usually appears
Map each risk to a control located as early as possible. A guided buying rule prevents an error before the order; an invoice check only detects it after the commitment. Both have value, but prevention normally costs less than correction.
Demand and specification
The business continues to request the former item, brand or service scope, so the awarded alternative never becomes the default.
Supplier and channel
Users buy outside the preferred supplier, bypass the catalog or pay with an uncontrolled channel because the approved route is harder to use.
Price and terms
Catalogs, price lists, freight conditions or rebates are not updated, causing orders and invoices to use obsolete commercial terms.
Invoice and exception
A non-PO invoice, quantity variance or manual coding step disconnects the payment from the original sourcing and contract decision.
Build a control chain from award to payment
For recurring purchases, catalogs and punchout connections reduce manual interpretation by presenting approved content at the point of request. For complex services, use rate cards, milestones, statements of work and acceptance rules. The control must match how the category is actually purchased.
- Define the baseline. Record the period, scope, volumes, currencies, one-off effects and exclusions before claiming an opportunity.
- Translate the award into buying content. Update preferred suppliers, catalog items, contracted prices, approval rules and requester guidance together.
- Assign adoption owners. Name the category owner and the business owners responsible for moving demand to the new agreement.
- Monitor transactions. Compare orders and invoices with contract terms, including item, unit, price, freight, tax treatment and volume tier.
- Resolve exceptions. Route each variance to a named owner, record the reason and distinguish legitimate exceptions from avoidable leakage.
- Validate the benefit. Reconcile procurement calculations with finance rules and avoid counting the same saving in several initiatives.
Measure adoption, leakage and realized value separately
Do not hide these measures inside a single score. High adoption can coexist with poor price compliance, while low adoption may be caused by a genuine scope change. Review the underlying transactions and reasons before assigning corrective actions.
| Measure | Question answered | Practical calculation |
|---|---|---|
| Contract adoption | Is eligible demand using the agreement? | Spend through the awarded agreement divided by eligible spend. |
| Channel compliance | Are users following the approved buying path? | Approved-channel transactions divided by eligible transactions. |
| Price compliance | Are orders and invoices using agreed prices? | Compliant lines divided by checked contract lines. |
| Leakage value | What value was not captured? | Expected compliant cost minus actual comparable cost, after valid exceptions. |
| Realized savings | What benefit can finance validate? | Actual eligible volume multiplied by the validated unit benefit, adjusted for agreed rules. |
A practical 90-day anti-leakage cadence
During the first month, reconcile awarded suppliers, contracts, catalogs and current transactions. Correct obvious content errors and agree the savings baseline. During the second month, focus on the business units and requesters with the largest deviations; remove usability barriers before escalating non-compliance. During the third month, stabilise a monthly review covering adoption, price variance, exception causes, open actions and finance validation.
The goal is not to eliminate every exception. It is to make exceptions visible, justified and temporary. A controlled exception carries a reason, an owner and an expiry date. An invisible exception becomes the new process and erodes the business case.
Is maverick spend the same as spend leakage?
Maverick spend is one important source of leakage, but leakage is broader. It can also occur with the preferred supplier when the wrong price, item, volume tier or contractual condition is used.
Who should own realized savings?
Procurement should maintain the initiative logic and operational actions, while finance should validate the recognition rule. Business owners are essential because they control adoption and demand.