Every sourcing event ends with a savings number. Procurement reports it, finance books it into the forecast and everyone moves on. Months later the realized savings come in lower than planned, and nobody can say exactly why. The usual answer is off-contract spend: purchases that bypass the agreement procurement worked hard to negotiate.
The leak rarely comes from bad intent. A project manager needs a service urgently and uses a supplier they know. A plant buys a part from a local distributor because the contracted supplier’s lead time looked long. A contracted supplier invoices last year’s rate because nobody told accounts payable the price changed. Each case is small. Across a spend base they add up to a meaningful share of addressable savings, and because they are spread across thousands of transactions, no single one triggers an alarm.
This article is for chief procurement officers and procurement operations leads who want to measure the problem accurately and fix it with controls rather than reminder emails. It breaks off-contract spend into its forms, shows where each one hides and lays out a practical sequence for closing the gap. The goal is not to police every requester. It is to make the contracted option the default and to catch the exceptions before money leaves the business.
The three forms of off-contract spend
Treating all leakage as maverick buying hides the fact that each form needs a different control. Separate them before you measure anything.
- Wrong supplier, a purchase from a non-contracted supplier for a category where a preferred agreement already exists.
- No contract reference, a purchase from the right supplier that is never linked to the agreement, so terms and volume tiers are not applied.
- Wrong price, an invoice from a contracted supplier at a rate, discount or surcharge that does not match the current price schedule.
- Expired coverage, continued buying after the agreement lapsed, usually on old terms with no negotiated protection.
- Scope creep, purchases from a contracted supplier for items or services the agreement does not cover, priced at list.
Wrong supplier is the form most programs measure because spend analytics tools can spot it by comparing vendor and category. The other forms need contract data. You cannot flag a wrong price without the price schedule, and you cannot flag expired coverage without the end date. That is why leakage programs often stall: the contract data sits in a repository nobody connected to purchasing. Procurement can see the agreement, and payables can see the invoice, but no system compares the two line by line. For context on how contracts and purchasing systems fit together, see source-to-pay vs procure-to-pay.
A purchase order can reference a contract while the invoice lines beneath it carry different prices or items. Compliance measured at the PO header looks healthier than reality. Measure the share of invoice line value that matches an active contract, the right supplier and the agreed rate.
Where off-contract spend hides in the process
Leakage enters at predictable points. Map your own process against these and you will usually find the largest source within a week.
- Free-text requisitions. Requesters describe what they need in a text box, and buyers pick whatever supplier is fastest rather than the contracted one.
- Non-PO invoices. Services, subscriptions and one-off purchases arrive as invoices with no order, so nothing checks them against a contract before payment.
- Stale price files. Price changes, indexation and tier discounts are agreed in contract amendments but never loaded into the ERP or catalog.
- Card spend. Purchasing cards bypass requisitioning entirely, which suits low-value purchases but lets recurring category spend escape.
- Lapsed agreements. Contracts expire quietly while orders continue, and the supplier keeps billing at terms that no longer bind anyone.
A five-step plan to bring spend back under contract
Step 1, Baseline by form
Pull twelve months of invoice line data and classify each line as compliant, wrong supplier, no reference, wrong price, expired or out of scope. The split tells you where to invest. Many organizations find price and reference gaps are larger than they expected.
Step 2, Make contract terms machine-readable
Extract price schedules, tiers, index clauses, end dates and covered categories from the executed agreements into structured fields. AI extraction speeds this up for large portfolios, but a reviewer should confirm every rate before it drives payment decisions.
Step 3, Steer requests at intake
Replace free-text requisitions with guided buying that suggests contracted suppliers and catalog items first. Requesters rarely resist a preferred option when it is the easiest one. Exceptions should require a reason code, which gives you data on why people go around the contract. If the same reason keeps appearing, such as lead time or coverage gaps, fix the agreement rather than the requester.
Step 4, Check invoices against contract price
Add a validation step that compares each invoice line with the active price schedule and flags variances above a tolerance. Route exceptions to the buyer and supplier manager rather than paying and chasing credits later. This single control recovers value that upstream steering misses.
Step 5, Manage expiry before it happens
Alert category managers well before an agreement ends so they can renew, rebid or consolidate. Block new orders against expired contracts unless someone approves an extension. Report compliance rate by category monthly so owners see the trend and can intervene where it slips.
Connect contract price schedules to every invoice
See how Aavenir links executed agreements to sourcing, purchasing and AP so off-contract spend is flagged before payment.
Why contract data is the missing piece
Spend analytics tells you what was bought and from whom. It cannot tell you what should have happened unless it knows the terms. Organizations that close the leakage gap tend to have one thing in common: the contract is a data object that purchasing and payables can query, not a PDF in a folder. When the price schedule, covered scope and end date are fields, guided buying can steer requesters to the right supplier, invoice checks can compare rates automatically and expiry alerts fire on time. The value leakage checklist covers the same principle from the contract side. Industry benchmarks consistently place leakage from price and compliance gaps at a noticeable share of addressable spend, and the fix is structural rather than behavioral. Training buyers helps. Connecting systems helps more, because the right behavior becomes the path of least resistance instead of an extra step people have to remember under deadline pressure.
Controls mapped to each form of leakage
Use this as a starting point for your control design. Most organizations need all five rows covered before compliance rates improve in a durable way. Start with the row that carries the most value in your baseline, prove the control works, then move to the next one rather than launching everything at once.
| Form of leakage | Primary signal | Best control point | Owner |
|---|---|---|---|
| Wrong supplier | Vendor not preferred for category | Guided buying at request | Category manager |
| No contract reference | PO or invoice lacks agreement ID | Requisition and PO creation | Procurement operations |
| Wrong price | Invoice rate differs from schedule | Invoice validation before payment | Accounts payable |
| Expired coverage | Order date after contract end | Expiry alerts and order blocks | Contract owner |
| Scope creep | Item not in covered categories | Catalog and scope rules | Buyer |
Off-contract spend is not a people problem to solve with policy memos. It is a data problem. Once contract terms flow into requisitioning and invoice validation, most leakage is stopped at the point of entry, and the savings procurement negotiated finally show up in the numbers finance reports.
For related guidance, see GPO and supply contract price accuracy for health systems, ServiceNow supplier onboarding: closing the contract gap and Why oilfield service rate schedules leak margin.
