Forty-three minutes into the quarterly review, the CFO asked one question: "Of that fourteen point two million, how much landed in my P&L?" The pause that followed was the kind that finishes careers. Procurement knew the savings were real. Finance knew the numbers did not match. Neither could prove their case.

This is not a tooling gap. It is not a talent gap. It is a measurement gap. Procurement tracks savings at contract signature. Finance tracks savings when invoices clear. Between those two moments, 30-60% of negotiated savings disappear — not because anyone lied, but because the two functions measure fundamentally different things with fundamentally different baselines.

30-60%
Negotiated savings lost between signature and P&L impact
~50%
Pipeline value that disappears between planning and execution (McKinsey)
45%
Procurement teams expecting higher cost avoidance targets in 2026 (Hackett Group)

The two definitions problem

Procurement and finance use the same word — "savings" — to mean different things. Procurement counts savings at contract signature: the unit price dropped from $100 to $92, multiplied by projected volume. Finance only counts savings when the invoice arrives at $92 and the budget line decreases accordingly. If volume drops or implementation delays by two quarters, procurement already reported the full number while finance sees a fraction of it.

The gap has a name: savings leakage. Most procurement teams lose 30-60% of negotiated savings between contract signature and invoice payment. The causes are structural: volume shifts, delayed implementation, off-contract buying, and baseline disputes. None of them show up on the procurement dashboard because the dashboard stops tracking at the moment of negotiation.

"The gap between 'procurement says we saved X' and 'finance sees X on the P&L' is where credibility breaks down."
— Suplari, Cost Savings Tracking Tools for Procurement

McKinsey research, cited in the same analysis, found the average savings pipeline loses roughly half its value between planning and execution. A procurement team that reports $10 million in negotiated savings typically delivers $4-7 million in actual P&L impact — not because they are inflating numbers, but because their tracking system stops at Stage 1.

Why baselines destroy credibility

The second structural problem is the baseline. Procurement calculates savings off one of several possible reference points: the previous contract price, the supplier's list price, a should-cost model built two years ago, or a market benchmark that may not reflect the relevant geography or volume tier. Each produces a different number.

Finance, by contrast, works from the general ledger. There is one baseline: what was actually spent in the prior period. When procurement claims $5 million in savings off a should-cost baseline and finance sees spend only down $2 million year-over-year, the credibility gap opens. Both numbers are "correct" within their own methodology, but only one methodology ties to the P&L.

Comprara's research on procurement savings claims identifies this as a foundational problem: "Off the previous contract price, which itself was negotiated against a market that has since moved. Off list price, which the supplier sets and adjusts at will. Each of these answers gives a different number, and only one is the answer the CFO will accept."

Cost avoidance: the third rail of procurement reporting

Cost avoidance is where most procurement-finance friction lives. A supplier proposes an 8% increase. Procurement negotiates it down to 2%. The procurement team reports a 6% cost avoidance as a savings win. Finance sees that costs went up 2% and moves on.

Procurement is not wrong that the negotiation produced real value. But reporting cost avoidance in the same category as hard savings — and mixing both into a single savings number — destroys credibility. The Hackett Group found that 45% of procurement teams expect cost avoidance targets to increase in 2026. More aggressive targets mean more scrutiny from finance, not less.

How procurement reports it
Suppliers proposed +8%, we settled at +2%. Reported savings: 6% cost avoidance + 3% price reduction = 9% total savings on the category.
Result: "We saved 9%." Finance: "Spend went up 2%. This does not match."
How finance wants to see it
Hard savings (P&L impact): 3% price reduction, confirmed against invoice data. Cost avoidance (disclosed separately): 6% increase avoided vs market proposal.
Result: "We delivered 3% to the P&L and avoided 6% in proposed increases." Finance: "The 3% checks out. The 6% is noted."

Closing the gap in four steps

1
Define together
Agree on savings definitions with FP&A before negotiations begin. Hard savings, cost avoidance, and soft savings must have separate line items.
2
Validate baselines
Finance must approve the baseline price, volume assumptions, and methodology. Procurement cannot set its own exam and grade itself.
3
Track to invoice
Link each initiative from contract → PO → invoice. Compare actual paid vs baseline. Isolate procurement's impact from FX, volume, and market shifts.
4
Report in finance periods
Map savings to GL codes, cost centers, and financial periods. Report realized savings against the same closing calendar finance uses for P&L.

What this means in practice

  1. Split your savings report into three columns. Hard savings (P&L verified), cost avoidance (separate, with market context), and soft/productivity gains (labeled separately). Never mix them into one number. The Hackett Group data shows boards are scrutinizing procurement claims more intensely — the mixed number loses every time.
  2. Get FP&A to co-sign the methodology. The fastest way to close the credibility gap: have finance validate the baseline and the realization method. If procurement is the only function signing off on its own savings, the number will never survive a CFO's question. Independent validation is not optional.
  3. Track one initiative end-to-end before scaling. Pick one category, one supplier contract. Map it from negotiated rate through actual invoices. Measure the leakage. If the number is 40% or higher — which the data says it likely is — you have the business case for a closed-loop tracking system.

FAQ

Why does finance distrust procurement savings reports?

Finance distrusts procurement savings because procurement reports savings at contract signature while finance only recognizes savings when they appear in actual invoices and reduced budget lines. The timing gap, combined with weak baselines and mixing of cost avoidance with hard savings, creates a credibility problem where 30-60% of negotiated savings never materialize on the P&L.

What is the difference between negotiated savings and realized savings?

Negotiated savings are calculated at the time of contract signing using a baseline price comparison. Realized savings are validated against actual invoices and confirmed to have reduced spend and budget lines. McKinsey research finds the average savings pipeline loses roughly half its value between planning and execution.

How can procurement close the credibility gap with finance?

Three steps close the gap: agree on savings definitions and baselines with FP&A before negotiations, track savings from contract through PO to invoice using closed-loop systems, and have finance co-own the methodology and validate results independently so procurement is not marking its own homework.

Sources

  1. Suplari — Realize Savings in Procurement: How to Prove What Your Team Actually Delivered
  2. Comprara — Why Procurement Savings Claims Fail Financial Scrutiny
  3. Suplari — Cost Savings Tracking Tools for Procurement
  4. Simfoni — Procurement Savings: How to Define, Measure, and Report Cost Reductions
  5. Arkestro — Cost Avoidance vs Hard Savings: How CFOs Actually Measure Procurement Value
  6. Varisource — How to Build a Credible Procurement Savings Report, 2026