Savings types: identified, validated, realized, and avoided

A category manager reports $15 million in savings for the quarter. The CFO's general ledger shows indirect spend unchanged. The numbers are not fraudulent. They are different categories of savings being reported under the same label. Procurement uses "savings" to mean four different things: identified, validated, realized, and avoided. Most organizations track only the first, report all four under one heading, and wonder why Finance refuses to accept the total.

The four types are not interchangeable. Each has its own definition, its own verification standard, and its own relationship to the P&L. Using them interchangeably is the single largest source of the credibility gap between procurement and finance. This article defines each type precisely, explains why the distinctions are not academic, and shows what organizations that get this right do differently.

Identified savings: the number at contract signing

Identified savings — also called negotiated or pipeline savings — is the value estimated during sourcing, based on the difference between a baseline and the new contracted terms. A sourcing event reduces unit price from $10 to $8 on an annual volume of one million units. Procurement records $2 million in identified savings. The contract is signed. Nothing has been purchased yet. No invoice has been paid.

Suplari frames this as Stage 1 savings: "The list price on a new contract is $50, the competitor quote was $65, so $15 of savings is claimed." It is the easiest number to calculate and the easiest to overstate. Most organizations stop here. They declare victory at contract signature and move to the next sourcing event. Identified savings assume full compliance, unchanged volume, and no downstream leakage. All three assumptions are usually wrong.

Realized savings: the number on paid invoices

Realized savings is the actual, P&L-impacting reduction in spend measured on paid invoices and general ledger entries. Previous annual logistics spend was $20 million. After a new carrier contract, invoices for the comparable 12-month period total $15 million. That $5 million is realized savings. It shows up in the financial statements. Finance can see it.

The gap between identified and realized is where most of the credibility problem lives. Suplari's enterprise data shows a typical 30 to 40% gap. A 15% planned savings becomes a 7% actual savings after maverick spend, volume changes, and compliance failures eat away at the negotiated rate. Efficio Consulting is more blunt: savings leakages of 50% or more occur if the points between contract signature and bottom line are not actively managed. Zycus notes that invoices hold the key to avoiding leakage, but most procurement teams never connect their sourcing platform to the accounts payable data that would tell them what was actually paid.

Validated savings: the number Finance agrees to

Validated savings is the highest maturity stage. It means realized savings have been reconciled with Finance, with auditable attribution isolating procurement's specific contribution from volume changes, market price movements, and operational projects that also affect spend. Total logistics spend drops $5 million year over year. Analysis shows $3 million from procurement's carrier rate renegotiation, $1 million from supply chain warehouse consolidation, and $1 million from reduced shipping volume. Finance signs off that $3 million counts as procurement savings. The methodology and documentation are retained for audit.

Almost no organizations reach this stage without deliberate governance. Suplari describes validated savings as savings that "survive scrutiny from even the most skeptical CFO" and are "auditable by a third party." Without validation, procurement claims are challenged or dismissed. With validation, the monthly argument about whose numbers are correct ends because there is one set of numbers both sides have agreed to.

Avoided savings: the cost that did not happen

Avoided savings — cost avoidance — is spend that would have occurred absent procurement intervention but never materializes. It is measured against a counterfactual, not a prior baseline. A supplier announces a 10% price increase. Procurement negotiates to hold prices flat. The avoided 10% is cost avoidance. A supplier proposes a 5% increase. Procurement limits it to 2%. The 3% differential is cost avoidance. Other examples include negotiating fixed-price clauses in volatile markets, eliminating penalty provisions, preventing rush-order freight surcharges, or securing free supplier training that would otherwise have been a line item.

Finance is inherently skeptical of cost avoidance because it does not show up as reduced spend in the P&L and the counterfactual baseline is, by definition, hypothetical. Provalido summarizes the tension: "Finance doesn't systematically recognize soft or intangible cost savings." But if cost avoidance did not add value, organizations would not employ people to negotiate price-increase caps, fixed-price clauses, and penalty eliminations. The answer is not to stop tracking cost avoidance. It is to stop calling it hard savings.

When the distinctions matter: three operational scenarios

Scenario 1: The quarterly review with the CFO. Procurement reports $20 million in total savings: $8 million identified but not yet realized, $5 million cost avoidance against projected increases, $7 million realized and validated. Present the single $20 million figure and Finance dismisses all of it. Present three separate figures with clear definitions and Finance accepts the $7 million, acknowledges the $5 million with appropriate caveats, and holds the $8 million as provisional until invoices confirm it.

Scenario 2: Budget planning. Finance asks how much of the identified pipeline can be counted toward next year's budget reduction targets. If procurement cannot separate what typically reaches the P&L from what does not, Finance either applies an arbitrary haircut of 50 to 70% or ignores procurement's input. Organizations that track realized-to-identified ratios by category give Finance a specific answer: "In IT hardware, our 12-month trailing realization rate is 82%. In facilities services, it is 61%." Finance uses those numbers.

Scenario 3: Procurement performance evaluation. A category manager's bonus depends on reported savings. Without validated savings as the metric, the incentive is to maximize the identified number regardless of realization. With validated savings as the bonus metric, the same person who previously optimized for the biggest contract-signing number now follows up on compliance, tracks invoices, and closes the loop. Behavior follows compensation.

What this means in practice

• Define each savings type in a shared document with Finance before the next negotiation cycle. Agree on what counts as hard savings versus cost avoidance and what baseline each category uses.
• Audit your last four quarters: what percentage of identified savings became realized? What percentage became validated? If you do not know either number, you do not have a savings tracking system. You have a savings claiming system.
• Separate cost avoidance from hard savings in every report, dashboard, and presentation. Use two columns. Do not add them together into one number.
• Move from identified to realized as the primary procurement KPI. Make validated the bonus metric. If compensation follows realization, behavior follows compensation.