Who validates procurement savings: finance
Why “claimed” and “validated” must stay apart, and how to do it
By Alexandre Lio, founder of The Procurementor, ex-Amazon EMEA and ex-Cellnex
Last updated:
A procurement saving is secured only once finance has confirmed it from the contract and the invoices. As long as procurement claims and measures its own results, the figure is a claim.
This article is written for the CFO as much as for the head of procurement: it describes what finance should check, and what procurement should bring so that validation takes a few minutes per line.
Claimed is not validated
The conflict of interest is structural: procurement is judged on the savings it announces. This is not about honesty, it is about governance, and the standard answer is separation of duties. A claimed saving is an estimate made by the party that benefits from it. A validated saving has been confirmed by a third party with no stake in it. Confusing the two is like confusing an order book with revenue.
What finance checks
| Check | Question asked | Evidence expected |
|---|---|---|
| Baseline | Where does the “before” price come from, and was it set before the negotiation? | Last invoice or approved budget |
| Type | Does spend go down, or is an increase avoided? | The supplier's increase request, where relevant |
| Achieved price | Is the new price contractual? | Signed contract or amendment |
| Volume | Is it the volume actually ordered, or an assumption? | Purchase orders and invoices |
| Timing | Since when, and for how many months of the financial year? | Contract effective date |
These five checks follow the rules of the procurement savings methodology. The volume check is the one most often skipped: a saving calculated on a budgeted volume reaches the P&L only if that volume is really ordered.
Worked example: from €180,000 claimed to €131,000 validated
Over a quarter, a procurement team claims twelve savings lines worth €180,000. After review:
| Status | Lines | Amount |
|---|---|---|
| Validated | 9 | €131,000 |
| Rejected | 2 | €34,000 |
| Claimed, awaiting evidence | 1 | €15,000 |
| Total claimed by procurement | 12 | €180,000 |
The two rejected lines are instructive. The first, €22,000, counted a drop in volume as a saving: the company had bought less, at the same price. The second, €12,000, used the supplier's first offer as its baseline although a last price paid existed. The figure reported to leadership is €131,000. The €15,000 still pending will enter it only when the signed amendment is provided.
The five most common reasons for rejection
- A drop in volume counted as a saving.
- A baseline chosen after the negotiation, or more favourable than the last price paid.
- Cost avoidance presented as a hard saving. The difference is explained in cost avoidance vs cost savings.
- A run-rate announced in place of in-year impact, or a one-time saving annualised. See recurring vs one-time savings.
- Double counting: the same saving claimed by two teams, or carried over from one year to the next.
None of these implies bad faith. They almost always come from a rule that was never written down. Once the rule is set, the rejection rate falls within two or three reviews, and validation becomes a formality.
Who validates, and when
- The buyer claims the saving and attaches the evidence.
- The team lead reviews the baseline and the type before it is submitted.
- The finance validator, usually a financial controller, confirms or rejects. It is never the person who made the claim.
- The review happens every month, before the close, so the validated total keeps pace with financial reporting.
A small team needs nothing more: one person in finance, a monthly slot, and a simple rule about the evidence to provide.
How the tool enforces it
In the tool, the right to validate is restricted to the “finance validator” role in the database, not only in the interface: a buyer cannot validate their own savings. Every line carries a status, “claimed”, “validated” or “rejected”, and the reference total counts validated lines only. Every validation is dated and written to an append-only audit log.
Validation only means something if the baseline has not moved in the meantime: that is the point of the baseline locking rule.
Frequently asked questions
Who should validate procurement savings?
Finance, most often the controlling or FP&A team. The person who validates must not be the one who claims, nor report to them.
What does finance check before validating?
Five things: the baseline, the type of saving, the price actually contracted, the volume actually ordered and the effective date. Each is proven by a document: invoice, contract, purchase order.
What happens to a rejected saving?
It stays visible with its status and does not count in the reference total. Keeping track of rejections is useful: they show where the method is not yet understood.
How often should savings be validated?
Every month, before the close. A yearly validation comes too late: the evidence is hard to find and the gaps can no longer be corrected.