Sourcing & Supplier Selection · Sourcing Event
Reverse Auction Event
A ready-to-run workflow that helps procurement teams run competitive price events for well-specified, commoditized categories. 6 stages, 8 pre-built fields and 4…
Explore templateA free Excel and PDF tracker for procurement teams: log each savings initiative, calculate gross, net and in-year savings the same way every time, and get finance sign-off before the number is reported.
Quick answer
A cost savings tracker is a spreadsheet or tool that logs each procurement savings initiative against a baseline. Its core columns are date, item or service, vendor and department, baseline cost, new negotiated cost, savings in dollars and percent, savings type (hard savings or cost avoidance) and status (forecast or realized).
The tracker has two parts. A one-page form for each initiative records the buyer, supplier, category, saving type, calculation method, baseline unit price, new unit price, annual volume and start date, and works out the gross, net and in-year saving. A summary sheet then totals the validated numbers by saving type and by category, splits hard savings from cost avoidance, and shows realized savings against the in-year plan and the target. A sign-off table records the buyer, category manager, budget owner and finance controller.
The problem it solves. Every buyer calculates savings differently, so finance discounts the whole number. The template replaces that with one record, one owner and one visible status.
Every initiative follows the same 6 stages, so anyone can see whether a saving is still a forecast or has been validated and realized.
Record the initiative, category, buyer, supplier and saving type, and pick the calculation method before any number is entered.
Agree the baseline unit price and annual volume with the budget owner, and write down where the baseline came from, such as last year's price or the lowest quote.
Work out the gross annual saving, subtract one-off implementation costs for the net saving, and count only the months affected this year for the in-year saving.
Finance checks the calculation and decides the budget treatment: a hard saving that lowers the budget, or cost avoidance that is reported but not removed.
Each month, compare invoiced prices and volumes with the forecast, so a saving counts as realized only when the lower cost actually shows up in spend.
Report validated and realized savings by category, buyer and period, against the annual target.
These fields sit on each initiative form. Starred fields in the template are mandatory, so a saving cannot be reported without a baseline, a method and a finance status.
(Baseline unit price minus new unit price) times annual volume. A $2 cut on 10,000 units a year is a $20,000 gross saving.
Gross annual saving minus one-off implementation costs, such as switching or setup fees, so the saving is not overstated.
Annual saving times the months affected this year, divided by 12. A $20,000 saving that starts in July adds $10,000 to this year.
Annual saving divided by baseline spend (baseline unit price times volume), so savings on large and small categories can be compared.
| Aspect | Manual process | With the Zapro template |
|---|---|---|
| Savings method | Every buyer calculates savings differently, so finance discounts the whole number | One calculation method per saving type, written on every record |
| Baseline | Baseline chosen after the deal, often the highest past quote | Baseline agreed with the budget owner before the saving is counted |
| Finance validation | Savings reported before finance has seen them | Validation status and budget treatment recorded before reporting |
| Realized savings | Forecast savings reported as if they were banked | Realized savings tracked against the forecast through the year |
| Audit readiness | Evidence reassembled from mailboxes at year end | Baseline, method and sign-off kept on each record |
In Zapro, savings work sits next to the rest of procurement, so the numbers come from the same records as purchasing and invoices.
How procurement teams find, measure and report savings.
A finance check for savings before they are reported.
Zapro dashboards and scheduled reports for spend and savings.
Start from a baseline agreed before the deal, usually last year's price or the average quote. Multiply the drop in unit price by the annual volume for the gross saving, subtract one-off costs for the net saving, and count only this year's months for the in-year figure. Then have finance validate it before you report it.
A hard saving lowers spend against last year or the budget, such as a unit price cut from $10 to $9, so finance can reduce the budget. Cost avoidance stops a cost that would have gone up, such as holding a price when the supplier asked for 8% more. Both are worth tracking, but report them separately so totals stay credible.
Yes. The tracker is free: enter your work email and the Excel file downloads straight away, and a PDF version is available to preview or print. To use it in Google Sheets, upload the Excel file to Google Drive and open it with Sheets, then check that the calculated fields still work before you start entering live savings.
A spreadsheet works while a few buyers track a few dozen initiatives a year. Move to software when several people edit the same file, finance wants an audit trail, or you need realized savings checked against actual invoice prices. At that point savings tracking tools or a procurement suite with spend analytics save rework.
Finance should validate them, usually a finance controller or FP&A analyst, not the buyer who negotiated the deal. They confirm the baseline, the calculation method and whether the saving reduces the budget. Agreeing these rules with finance at the start of the year stops arguments when savings are reported at year end.
Zapro brings intake, approvals, sourcing, contracts, purchase orders, invoice matching and spend analytics into one platform, with configurable dashboards and scheduled reports for the numbers your team tracks.