.png)
In short: A negotiated discount becomes a realized procurement saving when it is actually applied to purchases. That requires contract terms to carry through to purchase orders and invoice checks, with clear responsibility for resolving discrepancies.
The negotiation went well. The new contract includes a lower unit price, and the expected savings appear in the procurement report. A few months later, an invoice still arrives at the old price.
The approver can see that delivery has been completed. The person who placed the order knows they received what they needed. But checking the negotiated discount would mean looking up the contract separately.
What matters here is how the agreed terms reach the people placing orders, confirming delivery and approving invoices.
In August 2026, Censuswide surveyed 2,005 chief procurement officers and other senior leaders with procurement responsibility in the US and UK, on behalf of Agiloft. Among respondents, 97% were confident that their organizations consistently captured the value they had negotiated.
Yet 81% encountered discrepancies between contracted and invoiced prices at least occasionally. And 52% reported missing out on a contractual remedy in the previous year because it had not been tracked or acted on in time. [1]
This vendor-commissioned survey is based on respondents’ own assessments, rather than audited savings. The figures do not establish how much money an average company loses. They do, however, suggest that confidence in capturing negotiated value can coexist with gaps in execution.
Expected savings rest on an assumption: a certain volume will be purchased over a defined period under the negotiated terms. Realized savings can then be assessed against an agreed baseline, using actual purchases and the amounts invoiced or subsequently adjusted.
Consider a simple illustrative example. The previous unit price was HUF 1,000, and the new price is HUF 950. With planned annual purchases of 10,000 units, the expected price saving is HUF 500,000.
Suppose the company ultimately buys 8,000 units. Of these, 6,000 are invoiced at the new price, while 2,000 are incorrectly billed at the old price:
| Item | Amount |
|---|---|
| Planned price saving on 10,000 units | HUF 500,000 |
| Price saving available on the 8,000 units actually purchased | HUF 400,000 |
| Price saving reflected in the invoices | HUF 300,000 |
| Outstanding difference due to incorrect invoicing | HUF 100,000 |
This example assumes the product and all other terms remain unchanged, and excludes taxes and additional costs. Lower purchase volume explains HUF 100,000 of the shortfall against plan. That is not necessarily a problem: the company may simply have needed fewer units. Another HUF 100,000 arises from incorrect invoicing and still needs to be resolved, for example through a credit note.
The person placing an order needs to know which contract applies, which products or services it covers, and the terms available under it.
For a volume discount, for example, it matters whether the threshold applies to a single order, one site or the company’s total annual purchases. That information needs to be clear and accessible where the order is created.
Confirming delivery and checking the price are separate tasks. One establishes whether the goods have arrived or the service has been performed. The other checks whether the invoiced amount matches the applicable terms.
The reviewer may therefore need access to the price in effect at the relevant date, the quantity and any relevant contract amendments.
Once a price discrepancy has been identified, it needs an owner and a status that can be tracked. Who will contact the supplier? When is a correction expected? Has the credit note arrived?
Planned and realized savings can be reported separately to show how much of the expected benefit has materialized. They should not be added together. In the example, a HUF 100,000 credit note increases realized price savings from HUF 300,000 to HUF 400,000. Applying a discount that was already negotiated should not generate another saving on top of that total.
A practical way to review the process is to choose one contract that is used regularly. Select a specific term, such as a discounted unit price, and trace it through a few related purchase orders and invoices.
The information may be available, but in a different system. An updated price list may never have reached the reviewer. Or everyone may be aware of the discrepancy, while no one has been assigned to resolve it.
Each finding points to a specific improvement. Tracking procurement savings then becomes part of day-to-day operations, and reporting gives a clearer picture of how much of the negotiated benefit has actually been achieved.
When can procurement savings be considered realized?
When the negotiated benefit is reflected in actual purchases or the amounts invoiced and adjusted, and can be demonstrated using the company’s agreed measurement method. This requires a defined baseline, reporting period and approach to changes in purchase volume.
Why is a reduction in unit price not enough to measure savings?
Because actual results can also be affected by purchase volumes, product mix and other costs. A change in unit price is an important measure, but it does not explain the full movement in spend.
Who is responsible for ensuring that contractual discounts are applied?
Responsibilities span several functions. Procurement clarifies the commercial terms, the person placing the order applies them, and finance checks the invoiced amounts. The company’s process also needs to assign clear ownership for resolving discrepancies.
.png)
.png)
.png)
