Procurement Savings Verification

A buyer negotiates a lower unit price and announces savings, but three months later freight and rush orders offset part of the reduction. Procurement savings verification separates the agreed price from the value actually captured.

Glacier Lake Partners describes using a baseline and transaction evidence to distinguish negotiated from realised savings, and Umbrex discusses savings validation in procurement processes; both are consulting perspectives, so the finance policy should define reporting treatment. Set a baseline before the change, recording item, specification, supplier, location, currency, quantity and delivery terms, since a vague last-year spend number is not enough.

Define the initiative as a price cut, a new supplier, demand reduction or avoiding a planned increase, and label these separately. Preserve the agreement, because a signed quote or contract establishes negotiated terms, not proof that every subsequent invoice used them, and check the effective date, as orders before the new price starts do not create realised savings.

Match comparable units, since a different specification or package size changes cost and quality, and normalise before attributing a price difference. Hold volume separate, because buying fewer units reduces total spend but is not automatically a procurement price saving, and check mix, as a shift toward cheaper products may reflect customer demand and should not be credited entirely to negotiation.

Include landed cost (freight, duty, packaging and surcharges), and consider quality, because defects, scrap or rework can consume the headline benefit. Validate transactions: purchase orders, receipts, invoices and credit notes should tie to the stated initiative, and a catalogue update alone does not prove use.

Reconcile rebates by tracking thresholds and actual settlement, since a rebate contingent on volume may not be earned, and separate cash from accounting, as a price reduction affects costs when goods are purchased or consumed under applicable accounting, not necessarily at signature. Review service effects too, because longer lead times can increase safety stock or emergency freight.

Avoid double counting by keeping a single initiative ID and agreed attribution when procurement and operations both claim the same improvement. Use actual quantities, multiplying a comparable unit saving by eligible purchases during the period, because forecast volumes can support scenarios but not booked realisation.

Show currency effects separately, since a change in exchange rates may alter local cost without any supplier concession, and document exceptions such as one emergency order at the old price, including it in realised performance with an explanation. Have finance review the method, so each project does not choose a favourable baseline, and measure leakage, the gap between negotiated potential and verified outcome, rather than hiding it in other.

Do not present a temporary discount or expiring contract as a permanent annual benefit, and label any annualised run rate as projected. Retain an audit file with baseline, contract, transaction sample, calculation and sign-off, and treat an unresolved supplier dispute over a credit or revised price as not fully realised until its status and evidence are clear; for owners, verified savings are the portion supported by comparable real transactions after meaningful offsets, not the largest number in the supplier proposal.