Why Procurement Savings Do Not Reach the P&L

A buyer renegotiates a price from €100 to €95. Planned volume is 100,000 units. Procurement records €500,000 of savings.

Nothing about that calculation is wrong.

Then the year ends. Actual volume was only 80,000 units, so the price effect at real volume is €400,000. Finance had already budgeted €97 per unit, so the improvement against budget is €160,000.

Now three numbers describe the same negotiation: €500,000, €400,000 and €160,000.

This is the savings-realization gap in its simplest form. Procurement and finance are not necessarily disagreeing about what happened. They are often measuring different things.

The trouble starts when those different numbers are all called "savings" without saying what they mean.

Agree the baseline before celebrating the result

A saving only exists relative to something.

That reference point might be last year's price, the supplier's first offer, an approved budget, a forecast, a should-cost estimate or the price the business would otherwise have paid. Each answers a different question.

Negotiating a supplier from €110 to €100 may be excellent work if €110 was a credible increase that would otherwise have happened. But if the approved budget already assumed €100, finance will not see €10 per unit of new budget reduction. The buyer prevented a cost increase. They did not create the same amount of releasable cash.

Both forms of value matter. They should not be reported as though they were interchangeable.

The cleanest approach is to agree the savings baseline with finance before the measure is booked. If procurement uses previous price while finance uses budget, the reconciliation problem has already been created on day one.

Keep negotiated value, realized value and P&L impact separate

There are several useful stages between a signed deal and a number visible in the accounts.

The negotiated value shows what the commercial change is worth at the agreed reference assumptions. The realized value adjusts for what actually happened, such as actual volume and actual implementation date. The finance impact asks what changed against the budget or forecast that management is measuring.

Those numbers can legitimately differ.

Suppose the better price goes live two months late because master data is not updated. Part of the negotiated saving disappears. Suppose demand falls by 30 percent. The better price still exists, but there are fewer units on which to realize it. Suppose half the sites continue buying from the incumbent catalogue. The contract is good; compliance is not.

A savings process that stops at signature cannot see any of this.

Cost avoidance deserves its own line

Procurement often creates substantial value by stopping costs from increasing.

A supplier asks for 10 percent more. The buyer challenges the cost basis and the supplier withdraws the increase. On €10 million of annual spend, procurement has protected €1 million of cost.

That is worth reporting.

It is still different from taking €1 million out of an existing budget. If the budget assumed flat pricing, finance will see that procurement prevented a deterioration, not that it released €1 million for another investment.

Calling both numbers "hard savings" creates arguments that are completely avoidable. A better report shows them separately: budget-reducing savings, cost avoidance, working-capital effects, one-off value and other commercial benefits.

The function gets more credit, not less, when the categories are honest.

Most leakage happens after the negotiation

A signed price does not automatically become a realized saving.

The new price has to reach the ERP system. Purchase orders have to reference the correct contract. Sites have to buy through the negotiated channel. Rebates and credits have to be collected. Scope changes need to be controlled. The supplier cannot quietly recreate margin through freight, minimum-order charges, expedited delivery or a later "exception" that never gets reconciled.

This is why a savings initiative needs an owner after the buyer has finished negotiating it.

For each material saving, someone should know the agreed baseline, expected annual value, start date, affected spend, budget owner, implementation status and actual realized value. When the actual number moves away from the negotiated one, the reason should be visible: volume, timing, compliance, scope, currency, mix or an error in the original assumption.

Without that bridge, procurement sees a completed negotiation while finance sees an unexplained variance.

Reconcile with finance during the year, not at year-end

The worst time to discover that procurement and finance use different savings logic is the annual review.

A monthly or quarterly reconciliation is far more useful. It allows both teams to see which projects are landing, which are leaking and which assumptions have changed. The procurement number can be reduced when reality changes without turning the adjustment into a dispute about whether the negotiation was successful.

That discipline also improves future targets. If a category repeatedly realizes only 60 percent of negotiated value because implementation is weak, the answer is not a more ambitious sourcing target. It is fixing implementation.

Procurement credibility grows when the number in its presentation is the same number the controller is willing to defend.

There is a conversation problem inside savings realization too. Suppliers try to reopen scope. Internal users ask for exceptions. Stakeholders keep buying the old way because it is easier. Buyers sometimes give back value in those follow-up conversations without treating them as part of the original negotiation.

Voice2Evolve can be used to rehearse those moments, but the core discipline is simpler: define the number with finance, follow it through implementation, and keep negotiated value separate from what actually reaches the accounts.

A lower number that finance can verify is worth more than a spectacular number that disappears when somebody opens the ledger.