What is revenue leakage? The complete guide

Revenue leakage is revenue that your own agreements say you should have received, but that never reaches an invoice or your bank account. It is not revenue you miss because a customer says no. It is money you have already earned: a won deal that is never invoiced, an annual price increase that is forgotten, additional work that is never recorded, a discount that should have ended. It almost always arises in the handovers between systems and departments, and because nobody appears to be doing anything wrong, it often goes unnoticed for years.

This guide covers the whole subject: what revenue leakage is and is not, where it comes from, how large it is, how to calculate it, and the main causes one by one.

What is revenue leakage?

A workable definition: revenue leakage is the difference between the revenue you are entitled to on the basis of your agreements and your delivery, and the revenue you actually receive.

That definition has three parts:

1. Agreements. What was sold, at what price, on what terms? Deals, quotes, contracts, price lists.
2. Delivery. What was supplied? Products, hours, licences, additional work, usage.
3. Receipts. What was invoiced and paid?

Leakage sits in every gap between those three. There is an agreement but no invoice. More was delivered than invoiced. Something was invoiced but not paid, and nobody follows it up.

What revenue leakage is not

Revenue leakage is often confused with other forms of lost revenue. The distinction matters, because the remedy is entirely different.

• Lost deals are not leakage. A prospect who chooses a competitor owes you nothing.
• Churn is not leakage in itself. A customer who cancels in line with their contract is exercising a right. What is leakage: a customer who quietly buys less while committed to a minimum volume, or a cancellation nobody saw coming because the warning signs were lost between systems.
• Low prices are not leakage as long as they were a deliberate choice. A price below what your pricing policy allows, which nobody approved, is.
• Fraud can cause leakage, but most revenue leakage has nothing to do with intent. It comes from processes that do not quite close.

Why revenue leakage is so hard to see

The awkward thing about revenue leakage is that it leaves no trace in your normal reporting. An invoice that was never sent does not appear in your receivables. A price increase that was never applied is not an anomaly in your accounts: the invoice matches what is in the system. A customer who pays too little does not ring you up about it.

Every system does what it is supposed to do. The CRM records the deal. The accounting system books the invoice that is created. The auditor checks that what was booked is correct. Nobody checks whether what was booked is complete compared with what was agreed.

That is why revenue leakage is usually discovered by chance: during due diligence, a system migration, the departure of an employee, or when a customer calls about something else.

Where does revenue leakage come from?

Revenue leakage almost always arises at a handover. From sales to finance, from contract to invoicing, from project to administration, from one system to another. The more handovers, the more leaks. A full overview of the places and causes is in where revenue leakage comes from. The main ones in brief:

How much revenue leaks?

This is the question everyone asks, and the honest answer is that there is no reliable average that applies to your company. A commonly cited estimate puts it at 1 to 5 percent of revenue, with higher percentages in smaller companies with a lot of manual work. That is a range for getting an order of magnitude, not a benchmark.

What determines the figure for your company:

• The number of handovers between systems and departments.
• The complexity of your pricing: bespoke terms, volume tiers, indexation, bundles, additional work.
• The share of recurring revenue: errors repeat every period.
• How long a leak can run before someone notices.
• How much manual work sits between the sale and the invoice.

For a company with EUR 10 million in revenue, 1 to 5 percent means between EUR 100,000 and EUR 500,000 a year. Whether you are at the bottom, the top or outside that range, you only know once you measure. Worked out in more detail in how much revenue a B2B company leaks on average.

How do you calculate revenue leakage?

You calculate revenue leakage per finding, not as one big number. For each finding you establish three things:

1. The difference per period. What should have been invoiced, and what was invoiced?
2. One-off or recurring. A forgotten invoice for additional work is one-off. A rate that is too low is recurring.
3. The duration. How long has it been running, and how long would it continue if nobody intervened?

Worked example: suppose the annual 3 percent indexation has not been applied for 25 customers. Those customers pay an average of EUR 15,000 a year.

• Missed per customer per year: EUR 450.
• For 25 customers: EUR 11,250 a year.
• If two indexation dates have been missed: in the second year you miss just over EUR 900 per customer, more than EUR 22,500 in total.
• Without intervention it grows further every year.

The total of all findings, one-off plus annually recurring, is your revenue leakage. The full method, including how to extrapolate from a sample, is in how to calculate revenue leakage.

The main causes, one by one

Revenue leakage follows a limited number of recurring patterns. An extended list with concrete cases is in 25 examples of revenue leakage. The main categories are below.

Between CRM and billing

The most common and often the largest source. A deal is marked as won in the CRM, but the information does not reach invoicing, or only partly. The customer is not set up, the product lines are copied differently, the start date slips. Sales reports revenue that finance never sees. See revenue leakage between CRM and billing.

Between contract and invoice

The contract contains terms that no system knows about: volume tiers, minimum commitments, rates for additional work, discounts with an end date. Invoicing runs on whatever was entered at the start, and every later agreement has to be carried through by hand. See revenue leakage between contract and invoice.

Wrong prices

A customer gets an old price, the wrong tier or a discount that was never approved. Or the same product goes out at three different prices without anyone knowing why. See revenue leakage from wrong prices.

Missed price indexation

One of the most underestimated leaks, because it starts small and compounds. An indexation clause skipped for one year does not cost a few percent once, but every year after that as well, because the base stays too low. See revenue leakage from missed price indexation.

Missed upsells

Strictly speaking not revenue you already had, but revenue a customer was ready for. A customer who has outgrown their plan, has more users than their licence covers, or routinely buys additional work that would be cheaper and more predictable under a larger contract. See revenue leakage from missed upsells.

Expired contracts

Contracts that have ended but carry on silently on the old terms. Or contracts that should have been renegotiated, where nobody was watching the end date. See revenue leakage from expired contracts.

Wrong subscriptions

In recurring revenue: customers on the wrong plan, with too few licences invoiced, or on a rate that no longer exists. Or subscriptions that were not stopped after a cancellation, which creates the opposite problem: credit notes and unhappy customers. See revenue leakage from wrong subscriptions.

Manual administration

Every time a person copies data from one system to another, something can go wrong. A typo in a quantity, a line that is skipped, an email left sitting in someone's inbox during their holiday. See revenue leakage from manual administration.

Data problems

Duplicate customers, missing fields, outdated prices in the item master, deals without product lines. Poor data rarely causes a leak directly, but it makes every other leak larger and harder to find. See revenue leakage from data problems.

Revenue leakage by business model

Which leaks weigh most depends on how your company makes its revenue. The same cause can be a side issue in one company and the largest item in another.

Project businesses, construction and installation. The biggest risk lies in additional work and staged payments. Additional work is often agreed verbally or by email and reaches the administration months later, or never. Stage invoices lag behind progress, and at final account, items are missing that nobody can substantiate any more.

Consultancy and professional services. Here, hours leak. Billable hours booked as internal, rates not adjusted after a consultant's promotion, budgets exceeded without asking the client for approval.

MSPs and IT services. Quantities that grow without invoicing growing with them: workstations, users, devices, third-party licences that are recharged. On top of that, work outside the contract done as a "quick favour".

SaaS. Licences and usage that do not match the subscription, discounts that continue after the first year, customers on plans that no longer exist.

Wholesale and distribution. Customer-specific price agreements that are not in the item master, rebates and volume tiers calculated incorrectly, deliveries invoiced late or not at all.

The life cycle of a leak

Almost every leak goes through the same stages, and each stage makes it more expensive.

1. Origin. Something goes wrong in a handover. A field is not filled in, an email is left unanswered, a date is not recorded.
2. Repetition. With recurring revenue, the next invoice goes out on the same wrong basis. And the next. Nobody looks, because the invoice looks normal.
3. Normalisation. After a few months the wrong amount is the normal amount. It is in the budgets, the forecast and the customer value. Nobody remembers what the agreement was.
4. Expiry. Over time, recovering it becomes commercially awkward and sometimes contractually impossible. All that remains is correcting it for the future.

The sooner you see a leak, the more of it you recover and the smaller the conversation with the customer. A correction after one month is an administrative error. A correction after three years is a negotiation.

Why it belongs on the board's agenda

Revenue leakage is often seen as an administrative problem, something for the finance team to sort out. That is a misconception, for three reasons.

It hits margin directly. A euro recovered from a leak has no costs attached. No purchasing, no hours, no marketing. Almost all of it goes to the bottom line. Few other improvements have that effect.

It sits between departments. The leak between CRM and billing belongs neither to sales nor to finance. It belongs to nobody, which is why nobody fixes it. Only someone above both departments can assign ownership.

It distorts decisions. If your revenue figures do not match your agreements, your forecast is wrong, your customer value is wrong and your view of which products are profitable is wrong.

How to stop revenue leakage

Stopping revenue leakage happens in three phases.

1. Find and price

You need to know where you leak and how much. That can be done with a manual analysis: won deals against invoices, contracts with indexation against the latest invoices, hours worked against hours invoiced. It can also be done with an external audit. AutoMaat offers a one-off, personally conducted Revenue Audit for this, which covers eight areas and prices every finding in euros. What matters is that every finding gets an amount, so you know where to start.

2. Recover where you can

Not every leak can be recovered. A forgotten invoice for additional work from last month can usually just be sent. An indexation skipped for three years is harder, contractually and commercially. Decide per finding what is reasonable, taking account of the relationship and what the contract allows. The most important thing is not the past, but getting it right from now on.

3. Prevent

This is the phase with the most long-term value. Every finding points to a cause: a handover that does not close, a missing field, a date nobody monitors. Close those causes and the leak does not reopen. That can be done with process agreements, better integrations and continuous monitoring that reports a new leak within days instead of after a year.

Step by step: your first leakage check

You can do this within a month, without any software.

1. Export all won deals from the past twelve months from your CRM, with customer, date and amount.
2. Export all invoices for the same period plus three months, with customer, date and amount.
3. Find the first invoice for each deal. Flag every deal without an invoice and every deal where the invoiced amount is clearly lower.
4. List all contracts with an indexation clause. Compare the rate on the latest invoice with the rate a year earlier.
5. Pick ten projects or customers with additional work. Compare recorded additional work with invoiced additional work.
6. Put an amount on every finding, one-off or per year.
7. Add it up and decide whether you want to tackle this structurally.

Frequently asked questions

What is the difference between revenue leakage and lost revenue?

Lost revenue is broader: it also includes lost deals and customers who cancel. Revenue leakage is specifically revenue you were entitled to on the basis of agreements and delivery, but that you do not invoice or do not receive.

Is revenue leakage the same as fraud?

No. Fraud can be one cause, but the vast majority of revenue leakage arises without intent, in handovers between systems and departments that do not quite close.

How do I know whether my company has revenue leakage?

Warning signs: sales and finance quote different revenue figures, nobody can quickly say which customers have an indexation clause, additional work is agreed outside the systems, and revenue per customer falls without any cancellations. The only certainty comes from putting deals, contracts and invoices side by side.

Can my auditor find revenue leakage?

An auditor checks whether what has been booked is fairly stated. Revenue that was never invoiced is not in the books. Whether you invoice everything you agreed therefore usually falls outside the regular audit.

Who is responsible for revenue leakage?

Because it arises between departments, it often belongs to nobody. In practice it works best when one person, usually the finance director or the managing director, owns the integrity of the revenue chain, with clear tasks for sales, operations and finance.