Blog · Finance metrics and formulas · Procurement
A finance and procurement guide to historical and counterfactual savings baselines, with a checked price-reduction example, an avoided supplier increase and the evidence needed before reporting a benefit to the CFO.
Cost savings reduce a comparable cost; cost avoidance prevents a credible future increase. The difference is the baseline. A lower price than you previously paid can support a cost-reduction claim. Holding a price flat against an evidenced increase can support a cost-avoidance claim. Both can matter, but they answer different questions in the CFO's report.
For a US finance or procurement team, keep realized reductions, avoided increases and productivity benefits in separate columns. State the period and whether each changes an approved budget, a cash forecast or only the capacity available to the business.
| Category | Baseline | What the comparison establishes | CFO reporting question |
|---|---|---|---|
| Cost savings | Comparable historical price or cost, approved by finance | A reduction against the previous cost for the stated scope | Has the reduction been realized, and where does it enter the budget or forecast? |
| Cost avoidance | Evidenced future cost without the action | An increase or new outlay prevented by the action | Was that future cost credible, and was it included in the plan? |
| Productivity benefit | Time or capacity required before the change | Capacity released for other work | Did spending fall, or was capacity redeployed? |
“Hard savings” and “soft savings” are management labels whose definitions vary between companies. For this guide, hard savings means a finance-accepted reduction in comparable spending. A soft benefit has value but has not demonstrated that reduction. Your finance policy may classify an avoided funded expense differently; show the underlying comparison so the label cannot hide it.
For a comparable purchase, the classification formulas are:
Price-based cost savings = (historical baseline unit price - actual unit price) × eligible actual quantity
Price-based cost avoidance = (evidenced future unit price without the action - actual unit price) × eligible actual quantity
Use the same specification, service level, currency and cost basis. Record whether prices include freight, rebates and other relevant charges. If those differ, reconcile them before comparing. The savings claimed against savings realized guide owns the invoice-line realization method and leakage checks; this page owns which baseline and benefit category to use.
These synthetic examples cover a full reporting year. Quantities are actual eligible purchases, not a promised run rate. No taxes, freight changes or specification differences affect the comparisons.
| Initiative | Approved comparison | Cost at baseline on actual volume | Actual cost | Benefit and classification |
|---|---|---|---|---|
| Packaging price reduction | Previously paid $50 per unit; now $45; 10,000 units | $500,000 | $450,000 | $50,000 realized price savings |
| Maintenance supplier increase prevented | Existing price $20 per unit; evidenced future price $23; agreed price $20; 8,000 units | $184,000 at the proposed price | $160,000 | $24,000 cost avoidance |
The packaging comparison is ($50 - $45) × 10,000 = $50,000. That is a reduction against the prior unit price at this year's actual volume. It is not automatically the change in total category spending: quantities and other purchases may also have changed.
The maintenance comparison is ($23 - $20) × 8,000 = $24,000. At the historical $20 price, the same volume also cost $160,000. The historical price reduction is therefore $0. Report $24,000 as an avoided increase, not as a reduction in what the company used to pay. Retain the supplier's dated proposal and evidence that the increase would have applied without the negotiation.
The CFO pack should show $50,000 of realized price savings and $24,000 of evidenced cost avoidance on separate lines. If finance wants a combined benefits view, preserve those categories underneath it. Do not imply that their sum is an equal reduction in last year's expense or this year's approved budget.
Suppose an invoice-review change releases 600 hours over the year. At an approved loaded rate of $80 per hour, the capacity valuation is $48,000. If salaries and paid hours are unchanged, the demonstrated payroll reduction is $0. Report the hours, the valuation basis and how the team used the capacity.
The manager also says the change avoided a proposed analyst hire costing $120,000 for a full year. That can be a separate future-spending scenario, but it needs evidence: demand that required the role, its funding and intended start date, and confirmation that the role was canceled because of this change. Without that evidence, keep the $120,000 claim unverified and out of confirmed benefit totals.
Do not count both the $48,000 capacity valuation and the full avoided-hire claim for the same work as independent benefits. If finance later accepts the hire avoidance, replace or reconcile the overlapping capacity claim. A role that was never needed is not a saving merely because it was discussed.
Keep a benefit register with one row per initiative and reporting period. At minimum, include:
Show gross benefit and implementation costs separately before presenting a net figure. Keep annualized estimates distinct from benefits earned in the reporting period. A new contract price is evidence of an agreed rate; invoice lines establish whether it was paid.
For the procurement coverage question, use the spend-under-management workbook. It shows the spending within the selected management policy; it does not establish that every managed dollar delivered savings. Link its coverage results to the benefit register rather than applying a headline savings percentage to all spend.
A list price becomes the counterfactual. A supplier's opening quote does not prove the company would have paid it. Keep the credible alternative, effective date and approval behind an avoided-cost claim. If they are missing, report an unverified scenario.
Lower volume becomes a price saving. Buying fewer units can lower total spend without any sourcing improvement. Measure price effects on comparable actual volume and show demand changes separately.
An avoided increase becomes a budget cut. If the budget never included the increase, preventing it does not release that amount from the approved plan. Explain which comparison the benefit improves.
Loaded hours become cash. A rate times hours values capacity. Show the canceled spend, reduced paid hours or changed forecast before calling it a cash reduction. The fixed vs variable costs guide explains why a reduction in activity does not necessarily reduce the cost base.
One initiative is claimed twice. Two teams can contribute to one negotiation; one outcome still needs one benefit record. Likewise, the same released hours cannot support both a full capacity claim and a full staffing claim without an overlap adjustment.
Reporting stops at contract signature. A claimed price reduction may not reach every invoice. Track realization through the existing invoice-line method and retain forecast benefits as forecast until the evidence arrives.
Covirage works from the invoice exports, baseline register and operating files your team already holds. Finance approves the definitions and counterfactuals. Covirage's tools compute every figure, reconcile the selected scope and retain the supporting rows; the external AI model explains what changed and what remains unverified. A business team can begin with files without a data-team project.
See Covirage for procurement for the file-based setup. For the related question of whether a negotiated reduction actually reached the ledger, read savings claimed against savings realized.
Cost savings compare the new cost with a comparable historical cost. Cost avoidance compares the new cost with an evidenced future cost that would otherwise have occurred. Rejecting a proposed supplier increase can avoid cost while leaving the amount paid unchanged from last year.
Not necessarily. Companies use hard and soft savings differently. Finance may classify a prevented contractual increase as cost avoidance and released staff capacity as a productivity benefit. Define the categories before reporting and say whether any benefit reduces an approved budget or cash outflow.
For a comparable unit-price increase, avoided cost = (evidenced future unit price without the action - agreed unit price after the action) x eligible actual quantity. Keep the proposed price, its effective date and finance's approval of the counterfactual. A speculative list-price increase is weak evidence.
Released time is a productivity benefit unless it produces an evidenced spending reduction, such as less paid overtime or a canceled funded hire. Hours multiplied by a loaded hourly rate value the capacity; they do not prove that payroll or cash spending fell.