Definition
Realized savings vs. negotiated savings: Negotiated savings are the projected reduction in cost agreed with a supplier at the time a contract or price is signed. Realized savings are the portion of that reduction that actually shows up in what the organization pays and in its financial results.
Negotiated savings and realized savings measure two different moments in the life of a procurement decision. Negotiated savings are the reduction in cost that an organization agrees with a supplier when a contract, price change or new sourcing award is signed, typically calculated by comparing the new price to a baseline and multiplying by expected volume. Realized savings are the portion of that agreed reduction that actually materializes, verified in what the organization pays on invoices and ultimately in its budget or profit and loss statement. The difference between the two is often called savings leakage.
Why the distinction matters
A signed contract is a promise, not a result. Many procurement functions report success at the moment of award, but the business only benefits if the new terms are used, billed correctly and sustained over time. When procurement reports negotiated figures and finance cannot find them in the numbers, credibility suffers on both sides.
The distinction also changes behavior. A team measured on negotiated savings is rewarded for signing deals. A team measured on realized savings is rewarded for implementation, compliance and supplier performance after signing, which is where much of the value is won or lost.
Negotiated vs. realized savings at a glance
| Negotiated savings | Realized savings | |
|---|---|---|
| When it is measured | At contract signature or award | During and after implementation |
| Based on | Baseline price, new price and forecast volume | Actual invoiced prices and actual volumes |
| Source of evidence | Bids, quotes, contract terms | Invoices, AP data, budgets, general ledger |
| Main owner | Procurement | Procurement and finance together |
| Main risk | Overstated baselines or optimistic volume | Leakage from non-compliance, billing errors or delays |
| What it tells you | The potential value of a decision | The value the business actually captured |
How realized savings are measured
There is no single universal standard, and organizations define savings differently. A common approach calculates realized savings as the difference between the baseline unit price and the actual unit price paid, multiplied by the actual volume purchased over the measurement period. The key difference from negotiated savings is that both the price and the volume come from actual transactions, not from the contract or forecast.
A sound methodology usually defines:
- The baseline. Typically the last price paid, a weighted average over a prior period or, for new purchases, the average or lowest compliant bid. The choice should be agreed before the work begins.
- Volume treatment. Whether savings are calculated on forecast or actual volume, and how changes in demand are handled.
- Recognition timing. When savings count, for example as invoices are paid rather than when the contract is signed.
- Savings types. How hard savings, cost avoidance and other value such as payment terms or risk reduction are classified and reported.
- Validation. Who confirms the figures, typically finance, and what evidence is required.
Some organizations go a step further and track whether savings reached the budget, meaning the budget holder’s allocation was actually reduced rather than the freed-up funds being spent elsewhere.
Why savings leak
Several recurring causes explain why realized savings fall short of negotiated savings:
- Off-contract buying. Stakeholders continue to purchase from previous suppliers or outside the agreement.
- Billing errors. Suppliers invoice at old rates, add unapproved fees or apply escalations that the contract does not support.
- Slow implementation. Transitions to new suppliers or terms take longer than planned, delaying the start of savings.
- Volume changes. Actual demand differs from the forecast used to calculate the negotiated figure.
- Scope creep and change orders. Additional work is added outside the negotiated scope at higher rates.
- Baseline inflation. The original baseline was set too high, so the negotiated figure overstated the real reduction.
An example of the gap
For example, suppose a hypothetical company renegotiates a services contract and reports an annual reduction of 100,000 dollars based on a lower hourly rate and forecast hours. Six months later, an invoice review shows that two sites are still billed at the old rate because the supplier did not update its system, and a third site has added work through change orders at an uncontracted premium. The realized savings for that period are well below half the pro-rated negotiated figure, even though the contract itself is sound. Correcting the billing, recovering overcharges and pricing the additional work under the agreement recovers much of the gap.
Common pitfalls
- Reporting savings at award and never revisiting them.
- Allowing procurement to define baselines without finance agreement.
- Mixing cost avoidance with hard savings in a single headline number.
- Assuming a supplier will bill new rates correctly without checking.
- Ending tracking once a project closes, before leakage becomes visible.
How to close the gap
- Agree the methodology with finance before sourcing begins, including baselines, savings types and recognition rules.
- Plan implementation as part of the deal, with owners, timelines and communications to stakeholders who buy from the contract.
- Load contract terms into systems so purchase orders and invoice matching reflect the new prices.
- Audit invoices against contract terms, particularly in the first months after a change.
- Monitor compliance by tracking spend going to off-contract suppliers.
- Report both figures, negotiated and realized, so leadership can see where value is being lost.
How S2V approaches realized vs. negotiated savings
The distinction between negotiated and realized value is central to how S2V works. An agreement is not the finish line. In the Potential and Priority stages, S2V establishes baselines and savings definitions with finance up front, so that every opportunity in the portfolio is measured the same way from the start.
In the Performance stage, Execute builds implementation into every sourcing and negotiation effort. In the Value stage, Sustain and S2V Pulse track results in actual invoices and financial data, flag leakage and report realized value alongside what was negotiated, so leadership sees what actually reached the enterprise.
Related
- Assess — S2V Compass
- Execute — S2V Accelerator
- Sustain — S2V Pulse
- Enterprise Software Renewals
- Facilities & Janitorial Services
Frequently asked questions
What is the difference between negotiated and realized savings?
Negotiated savings are the reduction agreed on paper when a deal is signed, usually calculated against a baseline price and forecast volume. Realized savings are what the organization actually saves once the new terms are in use, measured in invoices, budgets or the P&L.
Why are realized savings usually lower than negotiated savings?
Common reasons include spend continuing to flow to old suppliers, invoices billed at the wrong price, volumes that differ from forecast, scope creep and change orders, and delays in implementing the new contract. Savings can also be offset if budgets are simply spent elsewhere.
Is cost avoidance the same as savings?
Not usually. Cost avoidance refers to preventing a cost increase, such as holding a price when a supplier requested an increase. It has real value, but it does not reduce spend against the prior period, so many finance teams track it separately from hard savings.
Who should validate realized savings?
Ideally finance and procurement agree on the methodology in advance, including the baseline, how volume changes are treated and when savings are recognized. Finance validation gives the numbers credibility with executives and the board.
How long should realized savings be tracked?
At minimum, for the life of the contract or the period the savings were claimed over. Many organizations track through at least the first full year of the new terms, because leakage often appears after the initial transition.