Leakage does not error
The reason revenue leakage is chronically under-measured is that it does not fail loudly. A transaction that should have accrued a rebate but did not match its agreement produces no exception. A claim that was never raised produces no alert. A promotion drawn down without evidence settles normally.
Nothing breaks. The money simply is not there, and it shows up a quarter later as unexplained margin variance that finance attributes to mix.
That is what separates leakage from a bad deal. A bad deal is a decision somebody made and can defend. Leakage is the absence of a decision. Which is also why it responds so well to systems work: you are not asking anyone to negotiate better, you are asking the process to stop dropping things.
Describe every leak twice
The most useful discipline we have found is to describe each leak in two registers.
In financial language, because that is what gets it funded. Where the money went, how much, which line of the P&L absorbed it.
In systems language, because that is what gets it fixed. Which two datasets never joined, which identifier failed to resolve, which rule lives in a PDF instead of an engine.
Most organisations have only one of these descriptions. Finance knows the margin is short and cannot say why; IT knows the POS match rate is 88% and cannot say what that costs. The pairing is what turns an argument into a project.
The nine
-
Price erosion and discount stacking. Every concession was defensible; the stack was never approved by anyone because nobody saw it summed. Commonly 1.5–4% of net revenue.
-
Contract drift. You are operating a version of the deal nobody signed, because the contract is a document and the configuration is data with nothing binding them.
-
Identifier mismatch. The match failed, so the money did not move. Match rates of 82–92% are normal, and the unmatched remainder is invisible rather than flagged.
-
Unclaimed entitlement. The threshold was crossed and nobody raised the claim, because the agreement lives in a PDF rather than an engine that watches thresholds. It runs both ways — a supplier rebate never invoiced, or a customer entitlement never accrued. Typically 0.3–1.1% of purchase spend.
-
Promotion and MDF spend leakage. The fund was spent, the proof was not collected. Eight to twenty percent of trade spend lacks adequate support.
-
Accrual drift. The liability on the balance sheet is an estimate disconnected from the transactions, so settlement produces a 10–30% true-up nobody forecast.
-
Unvalidated channel claims. You paid the claim because checking it cost more than the claim. Sampling finds under 1% invalid; line-level validation finds 3–7%.
-
Deduction write-off. It was cheaper to write it off than to fight it — a rational response to a manual matching process, and a habit your counterparties learn.
-
Reporting latency. By the time you saw the number, the quarter was over. Programmes that are not working keep running for another cycle.
Where to start
Not with the biggest number. Start with the leak where you can produce the measurement from your own data fastest, because an internal number is worth ten benchmarks.
For a manufacturer that is usually claim validation: take one quarter of debit or chargeback claims and validate every line against its authorisation. Whatever percentage comes back invalid is your business case, and it is not arguable.
For a distributor it is usually the buying-group reconciliation: purchases, versus submissions, versus what the group settled. Three numbers that should agree, that in most businesses have never been put on the same page.
Either exercise takes a few days and tends to end the debate about whether there is a problem.