A category manager negotiates a three-year contract for corrugated packaging at $0.87 per unit, with estimated annual volume of 2.4 million units. Contract value: $2.09 million per year. Procurement reports $2.09 million in spend under management and a 6% savings versus the prior contract.

Finance, 12 months later, records actual packaging spend of $2.47 million. Volume came in 11% higher. Freight surcharges added $82,000. Three change orders for custom runs added $114,000. The category manager insists savings were delivered. Finance sees a cost increase of $380,000 versus plan. Both are looking at real numbers. They are looking at different numbers.

"The relationship between finance and procurement is somewhere between unfriendly and hostile. They lack a common language for cost." — Sievo

The two terms, defined precisely

DimensionContract ValueContract Spend (Actual)
What it isForward-looking negotiated estimateBackward-looking realized cash outflow
Who owns itProcurement — recorded at signingFinance — recorded at payment
What it includesBase price × estimated volumes, optional scope, ceiling valuesActual invoices paid, real quantities consumed, actual unit prices, freight, duties, change orders, rebates
When it's measuredAt contract award (point-in-time estimate)Over the contract period (cumulative actual)
What it excludesVolume overruns, scope creep, maverick spend, price variances, implementation costsNothing — it is the total cash impact

Contract value is an estimate built on assumptions — forecasted volumes, negotiated unit prices, anticipated scope. Contract spend is what happened after those assumptions met reality. The two diverge for seven operational reasons, none of which are procurement failure and all of which procurement must track.


Where the gap comes from: the seven leakage points

Volume variance. Procurement negotiates on forecasted demand. Operations consumes at actual demand. If the forecast called for 2.4 million units and operations used 2.66 million, the 11% volume overrun adds cost that was never in the contract value — but appears in finance's actual spend.

Purchase price variance. The actual unit price diverges from the negotiated price. Commodity index adjustments, currency moves, freight surcharges, and rush fees all flow through PPV. A contract with quarterly copper-indexed pricing will produce variance every quarter. Procurement negotiated the formula. Finance absorbed the result.

Scope creep and change orders. Contract scope expands after signing — additional services, custom runs, expedited delivery — without formal re-valuation of the contract. The original contract value stays fixed. Actual spend grows.

Maverick spend. Purchases that bypass approved contracts entirely. They hit finance's P&L through expense reports and p-cards but never touch procurement's contract value records. Medius research found 86% of procurement professionals report late payments from missing information or errors — a symptom of disconnected procurement and finance data.

11%
Contract value leakage post-signature (WorldCC + Ironclad)
9.2%
Annual revenue drain from poor contract management (Concord)
75%
of contracts lack KPIs linked to TCO (McKinsey)

Timing and accrual differences. Procurement records committed cost at purchase order issuance. Finance records cash impact at invoice payment. A December PO with January delivery and February payment spans three reporting periods across two fiscal calendars. The contract value might be reported in Q4 while the spend hits in Q1 of the following year.

Hidden costs. Implementation fees, training, maintenance escalators, software overages, and compliance costs often sit outside the contract value estimate. McKinsey found these add 10–20% to total costs (McKinsey).

Savings measurement mismatch. This is the deepest source of procurement-finance conflict. Procurement typically reports cost avoidance as savings: "I negotiated $0.87/unit when the market was at $0.94 — that's 8% saved." Finance reports actual spend versus prior-year actual: "We spent $2.47M this year versus $2.23M last year — that's a 10.8% cost increase." Both calculations are correct. They measure different things. Sievo calls this "the language gap that makes procurement look dishonest to finance and finance look ungrateful to procurement."

When terms are confused
Procurement reports $180K savings. Finance shows $380K cost increase. CFO loses trust in procurement reporting. Category manager feels their work is unrecognized. Budget overrun caught months too late.
When terms are distinct
Procurement tracks contract value vs. baseline as negotiation performance. Finance tracks actual spend vs. budget as cost management. Both metrics coexist. Variance is investigated, not blamed.

When the distinction matters most

Quarterly business reviews. If procurement reports "contract value under management" and finance reports "actual spend," the numbers will not match. Establishing that they are different metrics before the QBR prevents a 20-minute argument about whose numbers are right.

Budget setting. Finance often uses last year's contract values as next year's budget baseline. If actual spend exceeded contract value by 11%, the budget is already too low before the fiscal year starts. Resourceful Finance Pro recommends finance use trailing actual spend, not contract values, for budget baselines — and procurement should flag expected variances quarterly.

Supplier performance reviews. A supplier that delivered exactly at the contracted price but whose total cost to the organization was 15% higher due to change orders and rush fees has a cost performance problem, not a price performance problem. Procurement alone misses this. Finance alone cannot trace it to the contract. Only joint review catches it.

Savings reporting to the board. When the CPO reports $4.2 million in savings and the CFO reports flat spend, the board asks hard questions. WorldCC notes that procurement's "primary mandate ends where the gap begins — at signature." Closing that gap with post-award tracking is the difference between credible and incredible savings reporting.


What this means in practice

For your five largest contracts by value, pull both the contract value at signing and the trailing 12-month actual spend from your ERP or AP system. Calculate the variance as a percentage. If any contract shows more than 5% variance, map the gap to the seven leakage points above. Volume variance and PPV are operational drivers — fix forecasting and index clauses. Scope creep and maverick spend are process failures — fix change order approvals and guided buying.

Establish a joint procurement-finance quarterly review of the top 10 contracts. Procurement brings contract value and negotiated savings. Finance brings actual spend and budget variance. The gap between them is not a problem to hide — it is data to manage.


Sources

  1. WorldCC — Closing the Procurement Value Gap. Accessed June 26, 2026.
  2. Sievo — Cost Reduction: The Common Language Between Finance and Procurement. Accessed June 26, 2026.
  3. McKinsey — Contracting for Performance: Unlocking Additional Value. Accessed June 26, 2026.
  4. Tipalti — Procurement and Finance Collaboration Guide. Accessed June 26, 2026.
  5. Resourceful Finance Pro — Fix the Finance-Procurement Gap. Accessed June 26, 2026.
  6. Planergy — Procurement-Finance Alignment. Accessed June 26, 2026.
  7. Trace Consultants — Why Procurement Savings Leak After Award. Accessed June 26, 2026.