Revenue leakage is money a business earned and did not collect. Not money it failed to win, which is a sales problem, and not bad debt, which is a credit problem. Revenue that was contractually owed and quietly never arrived.
The reason it persists is not that finance teams are careless. It is that detecting it requires comparing what should have been charged against what was charged, and in most companies the first of those two numbers does not exist anywhere in a form a machine can read.
Where it actually happens
| Stage | How it leaks | Why nobody notices |
|---|---|---|
| Pricing and discount | Discounts granted outside policy, or stacked in combinations nobody modelled. | Each one was approved by somebody. No single person sees the pattern. |
| Contract to billing | Terms agreed in the contract never reach the billing system, or reach it wrong. | It is a manual re-entry step, and re-entry errors look like data rather than money. |
| Renewal | Uplifts written into the contract are not applied. Renewals go out at last year's price. | The renewal looks successful. Nobody compares it to what the contract entitled you to. |
| Usage and overage | Consumption past the committed tier is metered late, or not at all. | Under-billing generates no complaint, so it has no reporting path. |
The pattern in that last column is the whole problem. Over-billing produces an angry customer within a week. Under-billing produces silence, and silence is indistinguishable from everything working.
You cannot measure it without a reference price
Leakage is a difference, so it needs two values. The invoiced amount is easy; every company has it. The entitled amount, meaning what the agreement actually permitted you to charge, usually lives in a signed PDF and a salesperson's memory.
Until the entitled amount is structured data, every leakage exercise is somebody opening contracts by hand and checking a sample. That finds instances and never finds the rate, which means it cannot tell you whether the problem is worth solving.
The reconciliation that finds it
Three systems hold a version of what a customer owes, and in a healthy company they agree. The exercise is to line them up and look at the disagreements.
- What was sold. The CRM opportunity: product, quantity, term, discount.
- What was agreed. The executed contract, including the clauses added during negotiation that never made it back into the CRM.
- What was billed. The invoice history.
Run the comparison on a single quarter before building anything. The disagreements cluster, and they cluster by cause rather than by customer: one broken handoff, one unenforced clause, one product whose metering was never wired up. Three causes typically explain most of the money.
Fix the recurring leaks, not the large ones
The instinct is to chase the biggest single discrepancy. That is usually the wrong order, because a large one-off is a story and a small recurring one is a system. A pricing rule that under-charges by two per cent on every renewal outruns a single mis-billed enterprise deal within a year, and it keeps running.
Sort the findings by how often the cause fires rather than by the value of the instance. That ordering also tells you which ones are worth automating, since a cause that fires once a quarter does not justify a control.
Most of this is ownership, not tooling
Each leak in the table sits on a boundary. Pricing policy belongs to one function, the contract to another, billing to a third, and renewals to a fourth. The leak is in the handoff, and a handoff belongs to nobody unless somebody is named.
That is the same structural problem as everywhere else in a go-to-market system, and it is why whether operations can change a definition or only report against one decides whether this gets fixed. A team that can see the discrepancy and cannot change the rule producing it will produce an excellent quarterly report about money still going missing.
When not to chase it
Before discounts are governed. If approval is informal, the entitled price is whatever was agreed in the room, and there is no standard to measure against. Decide who approves what first.
When the suspected amount is smaller than the reconciliation. This work is expensive. Sample a quarter, estimate the annual rate, and compare it honestly to the cost of the controls before committing.
While contract terms live only in PDFs. You can still find leakage by hand, and you cannot monitor it. Know which of the two you are buying.
Questions people ask
What is revenue leakage?
Money a business was contractually owed and did not collect. It is distinct from deals you failed to win and from customers who could not pay.
Where does most revenue leakage come from?
The boundaries: discount policy to contract, contract to billing, contract to renewal, and usage to metering. Rarely the billing engine itself, though that is what most articles about it are selling.
How do you detect revenue leakage?
Reconcile what was sold, what was agreed and what was billed across one quarter. The disagreements group by cause, and a handful of causes usually explain most of the money.
Why does under-billing go unreported for so long?
Because it is the one failure nobody complains about. Over-billing surfaces in days through the customer; under-billing has no such path.
Should we fix the biggest leak first?
Usually not. Sort by how often the cause fires. A small error that repeats every renewal outruns a large one-off and keeps running after it is forgotten.
Or skip the search
Want the person who owns it after it ships?
If the work is a standing obligation rather than a bounded project, tell me which system you want built first. You get example profiles and a call with your pick before anything starts.
Placement runs through AYTalent. Engineers are employed and trained on the bench before they start with you.