How do I validate realised procurement savings against budget?

To validate a realised (realized) procurement saving against budget, check three things. First, that the saving was measured against an agreed baseline, rather than only against a budget that may have been padded. Second, that the lower price actually shows up in what you paid, at the volumes you actually bought. Third, that someone outside the deal, usually finance, has seen the evidence and signed it off. A saving that passes all three is realised. One that has only been negotiated is still projected, and should be reported that way.

Baseline and budget are not the same thing

Most arguments between procurement and finance about savings come from mixing these two up.

• Baseline: what you would have paid without procurement's work. Usually last year's price, the incumbent supplier's renewal quote, or the average of the quotes you received.
• Budget: what finance set aside for that spend. It may include contingency, inflation or a guess.

Procurement measures savings against the baseline. Finance cares about the budget, because that is where cash is released. The UK government's own savings rules draw the same line: cash-releasing savings "lead to a direct reduction" in a department's budget, while non-cash-releasing savings do not (Cabinet Office technical note, 2025).

So a validated saving needs both numbers on the record: the saving against the baseline, and whether it reduces a budget line. Cost reduction usually does. Cost avoidance (stopping a price rise) usually does not, because the budget never included the rise. Our guide on cost avoidance vs cost reduction covers the difference.

A worked example

A small business renews its office cleaning contract.

	Amount
Budget for the year	£50,000
Baseline (last year's price, same scope)	£48,000
New contract price	£42,000
Saving against baseline	£6,000
Underspend against budget	£8,000

The underspend is £8,000, but procurement's saving is £6,000. The other £2,000 was headroom in the budget, and it was never going to be spent. Claiming £8,000 is how savings reports lose finance's trust.

Six months in, actual spend is £21,500. Half a year at the old price would have been £24,000, so the realised saving so far is £2,500, not the £3,000 the contract suggests. Why? An extra deep clean was ordered at £500. That is a scope change, not a failed saving, but it has to be explained. Validate £3,000 against the agreed scope and record the £500 separately, or validate £2,500 and say why. Either is fine. Not saying is the problem.

How to validate realised savings, step by step

1. Agree the baseline before the deal. Write down which baseline you are using and why. Agree it with finance before the sourcing event, not after the result.
2. Classify the saving. Cost reduction, cost avoidance or process saving. Mark whether it should reduce a budget line (cash-releasing) or not.
3. Record the assumptions. Volumes, start date, contract length, owner. A saving based on 1,000 units is wrong if you buy 600.
4. Wait for delivery. A signed contract is a projected saving. It becomes realised when the lower price is paid, period by period. Split long contracts into milestones (quarterly works for most) and realise each one when it completes.
5. Check against actual spend. At each milestone, compare what you paid with the baseline price at the volumes you actually bought. The spend figures come from your accounting system.
6. Strip out things procurement did not cause. Lower volumes, a supplier price index falling, a service you stopped using. The Cabinet Office note also excludes savings that only move or defer a cost, and anything counted twice.
7. Get sign-off with evidence. A named person in finance (or jointly with procurement) checks the evidence: the old price, the new contract, the spend for the period. Only signed-off savings go in the report.
8. Decide on the budget. For cash-releasing savings, finance decides whether to reduce next year's budget for that line. If the budget stays the same, the money gets spent elsewhere, and it often does.

For the reporting side, see how to track and report procurement savings to your CFO.

Doing it without a spreadsheet war

A spreadsheet can hold all of this. The trouble is that procurement keeps one version and finance keeps another. Our free procurement savings tracker template gives you the columns if you want to start there, and the savings tracker calculator helps with the numbers.

If you want one shared record, oboloo is free-forever procurement software for SMEs and charities, and savings validation and realisation is part of the free plan:

• Unlimited savings initiatives, each with its baseline, assumptions, timing and owner recorded upfront.
• Cost avoidance, hard savings and process savings tracked as separate types.
• Validation by procurement, finance or jointly, as your organisation works.
• Savings move to realised when milestones are hit, and only validated savings make it into reports.
• Dashboards that separate pipeline, projected and validated savings, with reporting by project, team, supplier and timeline.

The realised percentage is worked out only against the baseline of the milestones that have completed, so unfinished work does not dilute it (how savings are calculated in oboloo). Savings Plus ($20 per user a month, billed annually, 14-day free trial) adds unlimited savings milestones, savings document attachments for your evidence, and savings approvals. Registered charities get 50% off paid plans, forever. For other tools, see our comparison of procurement savings tracking software.

Where it fits less well: oboloo does not hold budgets, invoices or actual spend. The comparison with what you paid uses figures from your accounting system. If you want savings matched to invoices automatically, you need a spend analytics or purchase-to-pay tool, and oboloo is not one.

FAQs

What is the difference between realised and negotiated savings?

A negotiated saving is agreed in a contract. A realised saving has actually been paid at the lower price, for the volumes you bought. Report the two separately.

Should procurement savings be measured against budget or baseline?

Against an agreed baseline, usually last year's price or the incumbent's renewal quote. Then record separately whether the saving reduces a budget line. Measuring only against budget rewards padded budgets.

Who should validate procurement savings?

Someone who did not negotiate the deal. In most organisations that is finance, or finance and procurement jointly. The point is a second pair of eyes on the evidence.

When does a procurement saving count as realised?

When the lower price has been paid for a period. For a multi-year contract, realise it milestone by milestone, not all at once on signing.

Does cost avoidance show up in the budget?

Usually not. Stopping a price rise saves money compared with what would have happened, but the budget never included the rise, so no budget line goes down. Track it, but label it clearly as cost avoidance.