Cost savings (also called hard savings) is a drop in what you actually pay against a historical baseline: (baseline unit price minus new unit price) × volume in the period. Cost avoidance is spend you prevented that would otherwise have happened: (documented "would have paid" price minus actual price) × volume, where the "would have paid" price is a written supplier increase, a set of quotes or a pre-agreed estimate. Finance treats savings as money that can come out of next year's budget. Avoidance protects the budget but does not shrink it, so report it on its own line and count it only when the baseline was documented before you negotiated.
Example (illustrative): a supplier wants to raise a $50 part to $55 on 10,000 units a year. You settle at $52. Annual spend goes from $500,000 to $520,000. Cost savings: $0. Cost avoidance: ($55 - $52) × 10,000 = $30,000. Finance sees spend rise by $20,000. You prevented it rising by $50,000. Both statements are true, and a good savings report shows both.
Cost Savings vs Cost Avoidance at a Glance
| Question | Cost savings (hard savings) | Cost avoidance |
|---|---|---|
| What it measures | Spend reduced below a prior baseline | A spend increase that was prevented |
| Formula | (Baseline price - new price) × current volume | (Documented would-have-paid price - actual price) × volume |
| Usual baseline | Last price paid, current contract price or prior-year actuals | Supplier's written increase, competing quotes, list price or a pre-RFQ estimate |
| Visible in the P&L? | Yes, as lower cost than the prior period | No. Cost stays flat or rises, just by less |
| Can finance cut the budget by it? | Usually yes | No. There is nothing to take out |
| How finance checks it | PO and invoice prices before and after | The baseline document plus the final contract or PO |
| Typical sources | Supplier switch, price reduction at renewal, volume discount, spec change | Increase negotiated down, competitive RFQ on a new buy, price held during inflation, avoided rush freight or fees |
Terms vary between companies. Some finance teams say "cost reduction" for savings, and some lump avoidance in with process and time savings under "soft savings." Agree the labels and the formulas with your finance partner once, in writing, before you report a single number. Most arguments about procurement value are really arguments about definitions.
How Finance Treats Each Metric
Finance accepts cost savings because it can be checked against transactions. You paid $20 per unit last year, the invoices now say $18, and the volume is in the ERP. Nobody has to trust anyone.
Cost avoidance asks finance to accept a counterfactual: "without us, we would have paid more." Finance has three reasonable objections. Every department can claim it avoided something. A supplier's opening request is not proof that the price would have stuck. And avoidance never shows up as a better result, so a team that reports $2 million of avoidance while the P&L stays flat looks like it is inventing numbers.
There is also a budget consequence people forget. When you report hard savings, a CFO may reduce the category budget by that amount next year. That is the point of hard savings, so claim only what is real. Avoidance does not free cash. It explains why the budget held when costs were rising.
Finance will usually accept avoidance when four things are true:
- The baseline was written down before the negotiation started, with a date, by someone other than you (a supplier letter, a quote, an estimate signed off by the budget holder).
- The calculation uses the same method as every other claim.
- The volume is the forecast or actual volume, not a hopeful number.
- Finance reviewed and signed off on it, ideally each quarter.
How to Measure and Calculate Procurement Savings
Price savings = (baseline unit price - new unit price) × volume bought at the new price.
Savings % = price savings ÷ (baseline unit price × the same volume).
Use the volume you actually buy at the new price, not last year's volume. Otherwise changes in demand get counted as procurement wins or losses.
Example (illustrative): last year you bought 10,000 units at $20 ($200,000). This year you buy 8,000 units at $18 ($144,000). Total spend fell by $56,000, but procurement's price savings are ($20 - $18) × 8,000 = $16,000, or $16,000 ÷ $160,000 = 10%. The other $40,000 ($20 × 2,000 fewer units) came from lower demand. That belongs to the business, not to procurement.
Pick the baseline before you calculate
The baseline decides the number, so set the rule per situation and apply it every time.
| Situation | Baseline to use | Counts as |
|---|---|---|
| Repeat purchase, same spec | Last price paid or current contract price | Savings |
| Renewal where supplier asks for an increase | Current price for savings, requested price for avoidance | Split between both |
| New purchase via competitive RFQ | Median or second-lowest compliant quote, or a budget estimate set before the RFQ | Avoidance |
| Spec or design change | Old spec cost at current volume | Savings, credit shared with engineering |
| Price held during an inflationary period | Supplier's written increase notice or the index clause result | Avoidance |
| Avoided fees (rush freight, expediting, late penalties) | A written quote for the fee you avoided | Avoidance |
Worked examples
Renewal with an increase request (illustrative). An office supplies contract runs at $120,000 a year. The supplier proposes $138,000. If you settle at $126,000, savings are $0 and avoidance is $138,000 - $126,000 = $12,000. If you push it to $114,000, split the $24,000 gap so no dollar counts twice: $6,000 savings ($120,000 - $114,000) and $18,000 avoidance ($138,000 - $120,000).
Competitive RFQ on a new purchase (illustrative). You need a piece of equipment with no purchase history. Six compliant quotes come in at $71,000, $74,000, $78,000, $86,000, $95,000 and $106,000. You buy at $71,000. The answer depends on the baseline:
| Baseline | Baseline value | Avoidance claimed |
|---|---|---|
| Average of all quotes | $85,000 | $14,000 |
| Median quote | $82,000 | $11,000 |
| Second-lowest compliant quote | $74,000 | $3,000 |
The average is pulled up by quotes nobody would have accepted. The second-lowest quote is what you would most likely have paid without the last round of competition, which is why finance trusts it most. Whichever rule you choose, choose it before the RFQ closes.
Supplier switch (illustrative). You spend $200,000 a year with Supplier A and move the same volume to Supplier B at $175,000. Gross savings are $25,000. If qualification samples, tooling and onboarding cost $8,000, net savings in year one are $17,000. Report the net figure.
Spec change (illustrative). Engineering moves a component from $15 to $12 on 50,000 units a year: ($15 - $12) × 50,000 = $150,000 savings. Record it as a joint initiative with engineering rather than a procurement-only win.
In-year vs annualized value
A saving signed in October on a January to December fiscal year does not deliver its full annual value this year. A $60,000 annualized saving that starts on 1 October delivers $15,000 in-year (3 of 12 months). Finance books the in-year number. Report both, label them, and stop counting a saving after 12 months unless a new event resets the baseline. One-time items such as a single rebate or a one-off credit count once, in the period received.
A Savings Tracking Template Finance Will Accept
A spreadsheet works if every initiative has the same columns. These are the ones that matter:
| Column | What goes in it | Example (illustrative) |
|---|---|---|
| ID | Unique reference | S-2026-014 |
| Category and supplier | Where the money is | Packaging, Supplier B |
| Type | Hard savings, hard avoidance or soft avoidance | Hard avoidance |
| Baseline price and source | Price plus the document that proves it | $55.00, supplier letter dated 3 Mar 2026 |
| New price | Contracted price | $52.00 |
| Volume basis | Forecast or actual volume and where it came from | 10,000 units, FY26 production plan |
| Annualized value | (Baseline - new) × annual volume | $30,000 |
| Effective and end dates | When the price starts and when you stop counting | 1 Apr 2026 to 31 Mar 2027 |
| In-year value | The part that lands in this fiscal year | $22,500 (9 months) |
| One-off costs | Switching, qualification, tooling, legal | $0 |
| Net value | In-year value minus one-off costs | $22,500 |
| Status | Identified, contracted, realized, validated | Contracted |
| Evidence | Where the quotes, letters and contract live | RFQ export, contract v2 |
| Finance sign-off | Name and date | Pending Q2 review |
The status column is the one most teams skip and the one finance cares about most. "Contracted" means a price was agreed. "Realized" means invoices are actually coming in at that price. The gap between the two is leakage: buyers still ordering the old SKU, a site using a different supplier, or the supplier billing the old rate. Check invoice prices against contract prices each month.
Realization rate = realized value ÷ contracted value. Example (illustrative): you contracted $40,000 of savings, but three of ten sites kept ordering at the old price, so invoices show $28,000. Realization is 70%, and $12,000 is sitting in leakage you can still recover.
From the tracker, a simple monthly dashboard needs only five numbers: hard savings in-year against target, hard avoidance, soft avoidance (shown separately), the pipeline by status, and the realization rate.
How to Document and Prove Cost Avoidance
Avoidance that finance accepts and avoidance that finance ignores differ in one thing: whether the evidence existed before the result. This is the process, with owners and timing:
- Once a year (procurement lead and finance partner): agree the baseline rules in the table above, the hard and soft definitions, and how long a saving counts. Write it on one page.
- Before any negotiation (buyer, day 0): save the baseline. That means the supplier's written increase request, every quote received (not only the winner), or a cost estimate approved by the budget holder before the RFQ goes out.
- During the negotiation (buyer): log what you did: counteroffers, alternative quotes shown, terms traded. Two or three lines is enough.
- At award (buyer, same week): record the final price, volume basis, effective date and calculation in the tracker, and attach the evidence.
- Monthly (procurement analyst): compare invoice prices to contract prices and move initiatives from contracted to realized.
- Quarterly (finance partner, about an hour): review every claim over an agreed threshold, reject anything without evidence, and sign off the rest.
Hard avoidance has a written baseline from outside procurement: a supplier increase notice, a firm quote, a fee you were invoiced and got waived. Soft avoidance rests on estimates: market indices, "the market went up 8%," or a baseline you built yourself after the fact. Report soft avoidance separately, or leave it out until finance trusts your hard numbers.
If a supplier announces an increase verbally, ask for it in writing. It creates your baseline and slows the increase down. A template:
Subject: Proposed price change for [contract or item]. Please confirm in writing.
Hi [Name], thanks for letting us know about the proposed price change. So we can review it properly, please send the current and proposed price for each item, the effective date, and the cost drivers behind the change (for example material, freight or labor) with an estimate of how much each contributes. We will respond within [10] business days. Until new terms are agreed in writing, current contract pricing applies. Regards, [Name]
Competitive bids are the easiest avoidance to prove because the quotes are the baseline. Tools like AuraVMS help here: suppliers bid anonymously through email invites, every quote lands in one side-by-side comparison, and on the Medium Team plan you can export the full RFQ record to Excel and attach it as the evidence file.
How to Report Savings and Avoidance to Finance and Leadership
Keep each metric on its own line, show whether finance has validated it, and never add soft avoidance into a headline savings number. A quarterly summary can be this short:
| Metric (illustrative) | This quarter | Year to date | Finance validated |
|---|---|---|---|
| Hard savings, in-year, net of costs | $42,000 | $118,000 | Yes |
| Hard cost avoidance | $30,000 | $75,000 | Yes |
| Soft cost avoidance | $12,000 | $40,000 | No, for information |
| Contracted but not yet realized | $25,000 | n/a | No |
| Realization rate | 88% | 91% | Yes |
Then translate the numbers into what each audience cares about. Example (illustrative): $75,000 of hard avoidance on a $1.5 million category budget means the budget held flat even though supplier increases would have added 5% ($75,000 ÷ $1.5 million). For a finance lead that is budget protection. For an owner of a small company it might be a hire they did not have to cut.
A few habits keep the numbers credible:
- Report conservative, documented numbers. One inflated claim that falls apart costs more credibility than a year of modest ones earns.
- Give one or two specific stories alongside the totals. "The resin supplier asked for 15% and we settled at 3%" is remembered. "$60,000 avoidance" is not.
- If you want a "total procurement value" line, show it as savings plus validated avoidance, with both parts visible.
- If procurement bonuses or reviews count only hard savings, buyers will chase savings and neglect renewals where avoidance is the real prize. Score both.
Common Mistakes in Measuring Procurement Savings (and the Fix)
- Counting a volume drop as savings. Fix: multiply the price change by current volume only, as in the $16,000 vs $56,000 example above.
- Double-counting the same dollars. Fix: split renewal gaps into a savings part and an avoidance part so each dollar appears once.
- Using the supplier's opening ask or the average quote as the baseline. A 50% increase request nobody expected to stick is not a credible baseline. Fix: use the second-lowest compliant quote, or a written increase request you would realistically have faced.
- Reporting gross instead of net. Fix: subtract switching, qualification and tooling costs in the year they occur.
- Mixing annualized and in-year values. Fix: keep two columns and tell finance which one you are quoting.
- Counting a one-time rebate or credit every year. Fix: book it once, in the period you received it.
- Claiming avoidance from an old price lock. If a three-year contract signed in 2024 holds prices in 2026, that value was created when the contract was signed. Fix: count it in the year of the deal, or not at all after the first 12 months.
- Taking all the credit for cross-functional wins. Fix: record spec changes and demand reductions as shared initiatives and name the other team.
- Stopping at "contracted." Fix: check invoices monthly and report the realization rate.
FAQ
What is the difference between cost savings and cost avoidance in procurement?
Cost savings is a reduction against what you paid before: last year $100,000, this year $90,000, so $10,000 saved. Cost avoidance is an increase you prevented: the supplier asked for a $15,000 increase, you accepted $5,000, so $10,000 avoided. Savings shows up in the P&L. Avoidance does not, because spend still went up.
How do you measure procurement savings?
Multiply the price change by the volume bought at the new price: (baseline price - new price) × volume. Use the last price paid or the current contract price as the baseline, count only the months that fall in the reporting period, subtract one-off costs, and track whether invoices actually reflect the new price.
Is cost avoidance a hard saving?
No. Hard savings reduce spend below a prior baseline and can come out of the budget. Avoidance prevents an increase, so there is nothing to remove from the budget. Report it separately, and split it into hard avoidance (written baseline) and soft avoidance (estimated baseline).
How do you calculate savings on a new purchase with no price history?
There is no prior price, so any value is avoidance. Use a baseline you set before the RFQ closed: the second-lowest compliant quote, the median quote, or a budget estimate approved by the budget holder in advance. The second-lowest quote is usually the most defensible.
Should savings be measured against budget or against last price?
Against last price or the current contract price. Coming in under budget is not savings if the budget was padded or the volume dropped. Use budget only for new spend where finance agreed the estimate before sourcing started.
What is a good cost savings target for procurement?
There is no universal number. It depends on how much spend has been competitively sourced before, how many contracts renew this year, and market conditions. Build the target from the bottom up: list the renewals and sourcing events in the year, estimate each one conservatively, and agree the total with finance. Set separate targets for hard savings and for avoidance.
How can RFQ software help prove procurement value?
The biggest problem with avoidance is missing evidence. An RFQ tool keeps every quote for a sourcing event in one place, so the baseline exists before the award. In AuraVMS, quotes are compared side by side, and the Medium Team plan exports the complete record to Excel for your evidence file.
Demonstrate Your Procurement Value with Data
Savings and avoidance are both real value. The difference is evidence: proving what you prevented takes more documentation than proving what you reduced, and that documentation has to exist before the negotiation, not after.
AuraVMS keeps the competitive part of that record for you. Suppliers bid anonymously, every quote sits in one side-by-side comparison, and you can export the data when finance asks for the evidence.
Try AuraVMS free for 14 days. See how systematic quote comparison creates the evidence you need to prove both savings and avoidance.
[Start Your Free Trial No Credit Card Required]