Costing & FinanceFree worksheetPDF, Excel, Word export

Procurement Savings Tracker Worksheet

Savings numbers lose credibility when nobody can say how they were calculated. This worksheet fixes the method: baseline price minus new price, multiplied by annual quantity, tagged by savings type.

Download:
InitiativeSupplierSavings typeAnnual qtyBaseline unit priceNew unit priceBaseline spendAnnual savingSaving percentEffective date
$153,600
$10,800
7%
$14,760
$1,980
13.4%
$66,000
$3,500
5.3%
$166,500
$3,600
2.2%
Total baseline spend
$400,860
Total annual saving
$19,880
Blended saving percent
5%
Average saving per initiative
$4,970

Report hard savings (a real price drop on a real purchase) separately from cost avoidance (a rise you prevented). Filter the exported Excel by savings type before sending totals to finance.

Verify savings against ERP invoices

Optional: a read-only comparison of baseline and actual paid prices.

Optional. The tool and every export work without this. No spam.

How to use the worksheet

Add one row per initiative. Enter the annual quantity, the baseline price you can prove from the last purchase order or contract, and the new price. The saving, baseline spend and percent compute automatically. Pick the savings type so hard savings and cost avoidance are never mixed in one total. Export to Excel for your monthly report.

  • Use last paid price as baseline, not the first quote.
  • Use forecast quantity, not hoped-for quantity.
  • Record the effective date for in-year effect.

Savings definitions that survive finance review

Hard savings reduce spend against a baseline and show up in the ledger. Cost avoidance is a prevented increase and does not reduce the budget. Rebates and payment terms benefits are real but belong in their own lines. Agree these definitions with finance once and write them on the first page of the report so the numbers are never contested later.

In-year versus annualized

The saving column is annualized. If an initiative starts in August, only part of it lands in the current year. Multiply by remaining months over twelve when you report in-year impact, and keep the annualized figure for the run-rate view. Reconcile a sample of lines against actual invoices after three months.

Common mistakes

Counting a price drop twice when volume also changed, using list price as baseline, claiming savings on items never bought and including one-time freight in the unit price. Track price and volume effects separately: a lower price on a higher quantity is not a saving on the extra units.

Frequently Asked Questions

What counts as a hard saving?

A price reduction on goods or services you actually buy, measured against a documented baseline and visible in actual spend. It lowers cost in the ledger and should be reconcilable to invoices.

Is cost avoidance real savings?

It has value because it prevents a loss, but it does not reduce spend. Report it separately and never add it to hard savings in a total shown to finance.

How do I pick a baseline?

Use the last price paid in the prior twelve months, or the contract price in force before the change. Document the source. Avoid using a supplier's opening quote or list price.

Should savings be annualized?

Show both. Annualized savings show the run rate, while in-year savings show the budget effect. Label which one each report figure uses.

Netray can compare PO and invoice prices from your ERP against baselines automatically so savings are verified, not estimated.