How Much Money Is Your Procurement Function Quietly Losing?

Your team negotiated a seven per cent reduction on a major category last year. You reported it. Finance recorded it. Twelve months on, the actual spend in that category is up four per cent, and nobody has done anything wrong. Volumes moved. A few urgent orders went outside the agreement. Two sites carried on using the old supplier because switching was inconvenient. Every one of those is defensible on its own. Together they consumed the entire saving and more. How much of what your function negotiated last year actually reached the invoice?

Why this matters now

Procurement value leaks quietly, and the current environment widens most of the gaps at once. Longer shipping routes push more organisations into expedited freight, which is bought under time pressure and outside agreements. Local content requirements narrow the qualified supplier pool, which reduces competitive tension in categories that used to have plenty.

The Saudi Local Content and Government Procurement Authority decision of February 2026 to raise minimum local content thresholds on the Mandatory List, phasing in from August 2026, is a good example of a change that will shift real pricing for anybody supplying into government contracts.

None of this is a reason for procurement to expect worse results. It is a reason to measure them properly, because in a moving market the difference between a negotiated price and a realised price gets wider, and the organisations that do not track it will believe they are performing better than they are.

Before the arithmetic

When your team reports a saving, what happens to that number afterwards?

The third and fourth options describe the majority of procurement functions, including some very good ones. It is not dishonesty. It is that measuring realisation properly requires finance to cooperate on data that is organised for accounting rather than for category management.

What happened to Priya

Priya runs indirect procurement for a services group with operations across three Gulf markets. Around nine hundred suppliers, most of them small, spread across facilities, IT, travel and professional services.

She had a good year. A consolidation exercise across facilities took eleven per cent out of that category. Travel moved to a single agency with better rates. Professional services got a rate card where previously there had been none. Reported savings for the year were substantial and the number was accurate at the point it was calculated.

The following year she asked a simple question that nobody had asked before. What did we actually spend?

Facilities was close to plan. Travel was not. Roughly a fifth of travel bookings were still going outside the agency, mostly last minute and mostly by senior staff who found the agency slow. Professional services was worse. The rate card existed and was being applied, but the mix had shifted towards the more expensive grades, so the average hourly rate had risen even though every individual rate had fallen.

Neither of those is a procurement failure in the usual sense. Nobody breached anything. The agreements worked exactly as designed. What was missing was anybody watching the space between the agreement and the invoice.

Her second year target was not a bigger saving. It was realisation. Less impressive on a slide, considerably more valuable.

Your turn. Six decisions.

There is no trick answer here. At least two options in most of these are defensible. What separates them is what you are prepared to trade, and whether you could defend the trade afterwards.

Savings are a forecast until somebody checks

Procurement has a measurement problem that most functions would not tolerate anywhere else in the business.

A saving is calculated at the point of agreement, based on a comparison between an old price and a new one, at an assumed volume, with an assumed mix, on the assumption that everybody buys the way the agreement intends. Every one of those assumptions is a variable, and none of them is checked.

In any other function that would be called a forecast. In procurement it gets called a result, reported as a result, and occasionally used to justify headcount.

The correction is not more rigour in the negotiation. Procurement teams are generally good negotiators. It is a discipline after the deal, comparing what was agreed to what was actually spent, and treating the difference as the number that matters. Functions that make that switch usually report lower savings in year one and are believed for the first time.

Close the gap between the deal and the invoice

Four steps, applied to your top five categories. This is not a systems project. Most of it can be done with a spend extract and a fortnight of attention.

Your savings leakage estimate

Rough but useful. Run it on your largest category and the number will tell you whether this is worth a proper exercise.

Why leakage survives in well run functions

Savings leakage is not a symptom of a weak procurement team. It is often worse in strong ones, because strong teams negotiate larger reductions and therefore create larger gaps between the agreed price and the practical reality of how an organisation buys.

The first structural reason is that procurement is measured at the moment of agreement and disbanded immediately afterwards. The category manager who negotiated the deal moves to the next category. Nobody owns the twelve months during which the value either lands or does not.

The second is data. Realisation measurement needs spend data organised by category, supplier and unit price. Most finance systems organise data by cost centre and general ledger code, which is the correct structure for accounting and the wrong one for category management. Bridging the two is genuinely difficult and it is the point at which most realisation initiatives quietly stop.

The third is political. A number that shows realisation running at sixty per cent of reported savings is uncomfortable for everybody. Procurement looks worse. Finance looks like it accepted numbers it should have questioned. The business units look non compliant. There is rarely anybody whose interests are served by producing that figure, which is why it does not get produced.

What an experienced procurement leader does with this is counterintuitive. They publish the realisation figure voluntarily, before anybody asks, and they publish it low. The short term cost is a smaller headline number. The long term gain is that every subsequent procurement figure is believed, which is worth considerably more than one year of flattering reporting.

The strategic argument is straightforward. Procurement value that cannot be traced to the invoice is indistinguishable from a claim. Functions that can trace it get involved earlier in decisions, because finance trusts their arithmetic. Functions that cannot stay downstream, processing requisitions, wondering why nobody consults them before the requirement is set.

Where do you actually stand?

Six questions on how value is tracked in your organisation. Answer for practice rather than policy.

Score two points for a confident yes, one point for partly, zero for no. Then read your band below.

The part nobody puts in a job description

There is a moment in a procurement career where the job stops being about getting a better price and starts being about proving that a better price occurred.

Most people arrive at it late, because negotiation is visible, satisfying and rewarded, while measurement is tedious and initially makes your results look worse. It is entirely rational to avoid it.

But the professionals who make the switch acquire something that negotiation alone never delivers, which is financial credibility. When your numbers are trusted, you are consulted earlier. When you are consulted earlier, you influence what gets bought rather than only how it gets bought. That is the actual difference between a senior buyer and a procurement leader, and it has very little to do with negotiation skill.

It is worth asking honestly whether your reporting today would survive a finance director who genuinely wanted to test it. If the answer is uncertain, that uncertainty is currently limiting how far upstream you get invited.

Where a formal programme actually helps

Cost analysis, savings measurement and procurement performance sit in defined parts of a structured syllabus, which is useful because they are difficult to learn on the job. Nobody in a busy function has time to teach you a measurement method.

Two Blue Ocean Academy programmes address this at different depths.

CIPP or CIPM, in one line each

If both look plausible, the honest test is the one in the assessment above. If you scored in the lower two bands, start with CIPP. If you scored in the upper two and the gaps were strategic rather than technical, CIPM is the better fit.

One question before you go

One to argue about with your finance director. If procurement reported half the savings it does today but every reported figure could be traced to an invoice, would the function be worth more to the business or less?

The professional and the company in this article are composites written to illustrate a realistic situation. They are not a documented case study.