What is savings realization (reported vs. realized)?
Savings realization is the test of whether a reported procurement saving actually becomes lower spend, avoided cost, or another verified financial outcome after the deal is signed.
Savings realization is the discipline of checking whether a procurement win turns into a finance-recognized result. The contract may show a lower price, the buyer may have negotiated down a proposed increase, or the supplier may have promised a rebate. Realization asks what actually appears after that: lower invoices, avoided increases, paid credits, reduced demand, or a different cost that offsets the win.
What is the difference between reported and realized savings?
The useful split is reported versus realized.
| Savings number | What it is |
|---|---|
| Reported savings | What the team claims when the negotiation closes |
| Realized savings | What can be traced after the fact to a baseline Finance accepts |
Those two numbers can differ for good reasons: volume changed, the baseline was a supplier's opening ask rather than a prior invoice, the new supplier required extra inventory, or the team counted a market price drop as if it came from negotiation.
What are the types of reported savings?
This is why reported savings need types.
| Savings type | What it does |
|---|---|
| Hard savings | Reduce actual cost against a verified prior-period baseline |
| Cost avoidance | Prevent a proposed increase, but the spend line may still rise year over year |
| Soft savings | Improve time, quality, service, or risk position, but should not be forced into a cash number unless the measurement is clear |
How do you make a savings number defensible?
- Treat the baseline as the argument. A saving against last year's invoice is easier to defend than a saving against list price or a supplier's first proposal. If the baseline would not survive a Finance review, the reported number should carry a lower confidence label.
- Check realization after award. A negotiated rate is not enough. The team still has to confirm that buying shifted to the new contract, volumes matched the assumption, rebates were collected, and operational trade-offs did not erase the benefit.
- Separate the buckets in the report. One blended savings total is usually where confusion starts. A cleaner page shows hard savings, cost avoidance, estimates, offsets, and open assumptions separately, so a CFO can see what is bankable and what still needs proof.
For the wider task map, see AI procurement use cases.
Work this yourself — from the course
Related questions
See what the platforms caught — and missed
Twenty procurement tasks, four AI platforms, real dated runs. Lesson 2 is free to read, no account needed.