Search for the phrase "revenue leakage" and you'll find page after page of billing software. Quote-to-cash platforms, revenue assurance tools, invoice reconciliation, and contract compliance all promise to recover money that slipped through the cracks. It's a well-established market, backed by analyst reports, CFO guides, and customer success stories.
These products solve a real problem. They recover revenue that businesses have already earned but failed to collect.
But that's not the leak this site is about.
The problem is that B2B companies use the same phrase to describe two very different issues. One is well understood. It has software, industry benchmarks, and the attention of finance teams. The other is much larger, happens earlier in the revenue process, and doesn't even have its own product category.
When companies confuse the two, they often buy a solution for the first problem, report that "revenue leakage" has been fixed, and continue losing money to the second. This article separates the two leaks, explains why they are different, and shows how to recognise which one is affecting your business.
Leak one: earned but not collected
The first leak happens after a contract has been signed but before the money reaches your bank account.
The causes are familiar. A company delivers a service but never bills for all of it. Old pricing remains in place after a renewal. Contract price increases are never applied. Invoices are delayed because information falls between the CRM and the billing system. Discounts are approved that should never have been given. In every case, the company has already earned the revenue. The work has been done. The customer has received the service. The money simply never arrives.
At first, I assumed this was the one area with reliable numbers. After all, finance teams measure it, software tracks it, and vendors publish statistics about it. Then I followed the sources.
One of the most widely quoted claims says businesses lose between 1% and 5% of revenue to this type of leakage, usually attributed to EY. But tracing the citation leads from a Forbes article to a dead link on EY's website. Along the way, even the meaning of the figure changes. Some versions refer to EBITA, others to EBITDA, and others simply say revenue.
Another common statistic claims that 42% of companies experience revenue leakage, usually attributed to MGI Research. The company is real, but the published source leads only to its general research page. The original study cannot be found.
That leaves an uncomfortable conclusion. Even the better-known type of revenue leakage is often supported by statistics that can't be properly verified.
The important difference isn't the quality of the published benchmarks. It's that this leak can be measured using your own data. Your contract says one thing. Your invoice says another. Your bank account records what was actually paid. The gap between those records is the leak. You don't have to trust anyone else's percentage. You can calculate your own.
This leak is also limited by the value of the contracts you've already won. You can never lose more than you failed to collect. That's why software works so well here. Reconciliation software compares records, identifies mismatches, and highlights missing revenue. When companies recover that money, most of it goes straight to profit because the cost of serving the customer has already been paid.
If your business relies on complex contracts and manual billing, investing in these tools makes sense. I don't build those systems, and I'm glad companies specialise in doing that work well.
Leak two: never earned at all
Now look at how the billing software industry defines revenue leakage. Most glossaries describe it as money a business earned but failed to collect. They make a clear distinction between that and revenue loss—income the business never earned in the first place.
That definition draws an important boundary. Everything that happens before a contract is signed sits outside the scope of these tools. That's where the second leak begins.
It happens in the handovers between marketing, sales, and customer success. A promising lead sits in a queue until it goes cold because different teams disagree on what "qualified" means. A deal stalls between the product demo and the proposal. A customer never expands because the onboarding experience falls short of what sales promised. None of these failures appear on an invoice because they happen long before billing begins.
A long-standing IDC estimate suggests that this kind of misalignment costs businesses 10% or more of annual revenue. As I've argued before, that's an estimate rather than a measurement of your business. But it is a reasonable starting point for understanding how large this problem can become.
The second leak behaves very differently from the first. It cannot be reconciled because there is nothing to reconcile. A deal that was never created leaves no financial record. A lead that died because it sat in a queue looks exactly the same in the CRM as a lead that was never likely to buy. Once the opportunity disappears, the evidence often disappears with it. No piece of software can automatically find something that never happened.
That explains why there is a mature software market for the first leak but not for the second. Software is excellent at comparing records and spotting differences between them. The defining feature of the second leak is that the missing revenue never created the records software needs to analyse. This difference also changes how we should think about industry statistics.
The first leak doesn't depend on published benchmarks for very long. A business can compare its contracts, invoices, and payments, then replace a generic estimate with its own measured number.
The second leak offers no such shortcut. There is no report you can run to calculate the value of deals that were never created or opportunities that quietly disappeared between teams. That gap creates a vacuum, and unsupported percentages quickly fill it. Without a direct measurement, the only honest choices are to treat published figures as broad estimates or to build a method that measures the problem specifically for your own business.
Why the confusion is expensive
Using the same phrase for two different problems creates an expensive mistake.
A board raises concerns about "revenue leakage". Finance responds by buying a billing or revenue assurance platform. Collections improve. EBITDA increases. The investment delivers exactly what it promised. The company then concludes that the problem has been solved. But the solution could never have addressed the second leak.
Good billing practices recover revenue from deals you've already won. They cannot improve the accuracy of your forecast because forecast misses begin much earlier, when the pipeline no longer reflects reality. They cannot reduce the cost of growth because that money leaks away before a contract even exists. They cannot increase customer expansion because expansion often fails during the handover to customer success, long before an invoice is ever created. That's why fixing your billing won't fix your forecast.
Not because the billing software failed, but because it was solving a different problem. So before you invest, spend two minutes identifying which leak you're actually dealing with.
If your symptoms include gaps between contracts and invoices, invoice disputes, missed price increases, or rising days sales outstanding, you're looking at leak one. Buy the software. That's exactly what it's designed to fix.
If your symptoms look different—forecasts that are consistently missed even though every department reports green dashboards, rising customer acquisition costs, quiet discounts at renewal, or large deals that slip from quarter to quarter—you have leak two.
No amount of billing automation will solve those problems. Most businesses of any size suffer from both leaks. The mistake is assuming they're the same. They aren't. They're different problems, and they need different tools.
Two leaks, two instruments
The first solution already exists. Finance owns it. Reconciliation software compares contracts, invoices, and payments, then identifies revenue that should have been collected but wasn't.
The second solution has to work differently. It can't start with software because the evidence it needs was never recorded in the first place. Instead, it has to build a picture from the information that does exist.
It compares what the CRM records with what appears in the financial data. It examines what happens at each handover between marketing, sales, and customer success. It measures those handovers against a single, consistent framework so the business can measure the problem today and measure it again after improvements have been made. That's the instrument I build.
The distinction matters. Billing software protects revenue you've already earned. Commercial Engine Maturity Assessment (CEMA) identifies the revenue your business is currently structured never to earn.
Both leaks are real. Only one has an established software market ready to solve it. So the next time someone raises "revenue leakage" in a leadership meeting, ask one simple question before anyone approves a budget:
Which leak are we talking about—the money we earned but never collected, or the money we never earned at all?
The first has a mature software category waiting for you. The second is still waiting to be measured.
Most companies can name one of these leaks and are caught out by the other. Which of them costs you more is an empirical question, and your own numbers already hold the answer.
Free, 30 minutes. No preparation needed.