Practical perspectives

Procurement Savings Baseline: A Finance Review Worksheet

Separate opportunity, negotiated value and realized savings with an auditable price, volume and timing example.

On this page
  1. Agree the method
  2. Keep stages apart
  3. Reconcile the lines
  4. Record the decision

A sourcing team negotiates a ten-dollar price reduction and reports a ten-thousand-dollar saving. The forecast assumed 1,000 units, but only 600 were bought after the new contract took effect. Without a defined baseline and time period, both numbers can look correct while meaning different things.

This worksheet complements the procurement savings validation software guide. Agree the method with Finance before reporting a result.

1. Agree what is being measured

Record whether the project claims a price reduction, cost avoidance, budget reduction, working-capital effect or recovered overcharge. These measures use different baselines. Define the legal entity, SKU or service, currency, tax treatment, comparison period and who can approve a change. Do not add categories together merely because all are displayed as currency.

  • Comparable scope: same specification, service level and unit of measure.
  • Baseline: approved prior price or budget, dated and sourced.
  • Effective date: the new term applies only after it starts.
  • Adjustments: volume mix, one-time costs, rebates and currency effects.

2. Keep opportunity, contract and actual result separate

Fictional unit-price example, before taxes and implementation cost
StageCalculationAmountMeaning
Opportunity($100 − $90) × 1,000 forecast units$10,000Potential effect if forecast volume occurs.
Contracted claimSigned $90 price, effective July 1Not yet realizedContract term is established.
Observed price effect($100 − $90) × 600 eligible actual units$6,000Gross effect on actual eligible purchases.
Net realized result$6,000 − approved implementation costsDepends on costsFinance-approved reporting amount.

The $4,000 difference between opportunity and observed gross effect is lower eligible volume, not a failure of the negotiated unit price. If the product mix or specification changed, even the $6,000 needs adjustment.

3. Reconcile contract and transaction evidence

Match each eligible invoice or order line to the new contract, effective date and unit of measure. Exclude quantities outside the agreed scope and explain invoice credits separately. Keep both the source transaction and the reviewer correction so Finance can reproduce the number.

SpendHQ publishes a finance-focused savings validation workflow ↗. Spendkey publishes opportunity assessment and transaction-to-contract audit controls ↗. Ask a vendor to show which stage its product actually validates in the offered package.

4. Record Finance approval and later changes

Minimum approval record
FieldReviewer needs
Method and baselineVersioned definition, source and approver.
Contracted termSigned price and effective date.
Actual volumeEligible transaction lines and exclusions.
Final amountGross, adjustments, net and Finance decision.

If volume changes next quarter, publish a new period result with its own transactions. Do not silently replace an earlier approved number or claim the same benefit again in a separate initiative.

Sources