Spend Leakage

A negotiated price does not save money if nobody uses it, and spend leakage describes the gap between intended purchasing value and what happened, which can arise before ordering, during use or at payment. A fictional company has a $50 contracted unit price but buys identical approved items for $60 elsewhere without a valid reason, so the extra $10 per unit may be avoidable leakage.

Do not equate all off-contract spending with loss, because the contracted item may be unavailable, unsuitable or more expensive after freight, so validate the comparison and approved exceptions. Amazon Business describes maverick spend as buying outside an agreed contract, preferred source or policy, and notes that the purchase can still be legitimate, so that concept is one possible source of leakage, not a guarantee of financial loss.

Other leakage can come from invoice errors, unused subscriptions, missed discounts or service-level benefits not delivered, and PRGX describes overpaying, failing to use paid assets and missing negotiated outcomes as broad value-leakage patterns. Compare contract, order, receipt and invoice where relevant, because a price difference can be a data error or approved variation and the audit trail should show the actual agreed term.

A fictional invoice shows $55 per unit while the current contract says $50, so AP verifies freight, dates and any approved price change before disputing it. Duplicate payment is another risk, since two invoice numbers may cover one delivery or two different deliveries may look similar, and a fictional supplier that sends a corrected invoice with a new number requires finance to check whether the earlier version was paid before processing the replacement.

Investigate rather than automatically rejecting a legitimate bill. Demand itself can leak value when buyers order more than they need, because a cheap unit price does not help if excess stock expires, and usage and disposal records reveal the total cost.

A fictional office that buys bulk supplies to earn a discount and then discards half has not created net value from the discount. Define the baseline carefully, because "savings lost" should be compared against a realistic, available option and like-for-like quantities, quality and terms, and invented counterfactuals should be avoided.

A fictional analyst claims $100,000 leakage from all nonpreferred purchases, and procurement removes categories with no eligible agreement and recalculates a defensible figure. Supplier credits and rebates may not be automatic, since a contract may require volume thresholds, timely claims or specific reporting, so track eligibility and receipt separately.

Classify suspected, validated and recovered leakage with distinct statuses, because finding a discrepancy does not mean it is owed back and an agreed credit is not cash until applied or paid; a fictional audit that flags a $2,000 pricing issue, wins a $1,500 credit from the supplier and later sees finance apply it should keep all three figures separate in its report. Root causes matter more than one-off recovery, since a bad catalogue price, confusing approval path or weak invoice match can create repeat cases, so fix the process, measure recurrence and make the compliant route usable, because employees may bypass a slow system to get necessary work done.

Look across purchasing channels and check supplier identities, since card, expense and invoice-only transactions may not appear in purchase-order data and duplicate names, subsidiaries and currency differences can distort analysis, so clean data without merging genuinely distinct vendors. Prioritise by recoverability, recurring value and risk while keeping claim deadlines in view, and use a shared register so procurement, AP, finance and service teams can connect their evidence, labelling any estimate that mixes avoidable cash overpayment with hypothetical service value.