By clicking “Accept”, you agree that cookies may be stored on your device in order to improve site navigation, analyze site usage, and help us with our marketing efforts. Check out our for more information.

Guides

Revenue leakage: definition, causes, calculation and fixes

#QUOTE-TO-CASH Insights
Opencell #QUOTE-TO-CASH Insights cover: Revenue leakage, the guide

Revenue leakage: definition, causes, calculation and fixes

OpencellNovember 21, 202618 min read

The easiest revenue to win is the revenue you have already won.

Companies spend a lot of energy winning new customers. They spend much less checking that the customers they have already signed pay everything they owe. Between the contract and the cash, part of the revenue evaporates: a discount that never ends, an option activated but never billed, usage lost along the way, a contractual price increase forgotten.

This is revenue leakage. It makes no noise, appears in no account and nobody complains about it, least of all the customer. Yet according to a 2026 DigitalRoute study of 631 European and American executives, six organizations in ten estimate that at least 2% of their revenue is exposed to billing errors, and one in three puts it at 5% or more.

This guide explains what revenue leakage is, what it costs, where it happens from quote to cash, how it varies by industry, how to calculate it, detect it and above all prevent it. For the overall sales cycle framework, see also our guides to quote to cash and billing.

What is revenue leakage?

Revenue leakage is revenue a company has earned, through a signed contract or a delivered service, but does not bill, bills wrongly or never collects. It comes from errors, omissions and breaks between teams and systems, not from a commercial decision.

The best image is a leaking pipe: water comes in through the contract, it should come out through cash collection, and every loose joint lets a little escape. Taken one by one, each leak seems negligible. Added up across thousands of customers and hundreds of thousands of invoices, they become a significant amount.

It helps to distinguish revenue leakage from related notions:

Notion What it refers to Example
Revenue leakage Revenue earned but not billed, wrongly billed or not collected An option active at the customer but missing from the invoice
Lost opportunity Revenue that could have been earned with another decision Price too low, offer poorly positioned, deal not closed
Fraud Loss caused deliberately by a third party or an employee Fraudulent use of a telecom line, misappropriation
Bad debt An accurate invoice that is never paid Defaulting customer
Commercial discount A price reduction decided and owned An approved goodwill gesture

The most important line is the one between choice and error. A decided discount is not a leak. A discount granted for three months and still applied two years later is one.

How much does revenue leakage cost?

Recent studies put exposure to billing errors at several points of revenue. In the 2026 DigitalRoute survey, 60% of organizations estimate that at least 2% of their revenue is at risk, and 33% put it at 5% or more. For a €100 million company, each point represents €1 million a year, almost entirely margin.

The same DigitalRoute study, carried out in April and May 2026 among 631 senior executives in the UK, the US, Germany, France, the Nordics and Benelux, offers three more findings:

  • customers often find the errors: 29% of organizations first discover their billing problems through customer disputes, compared with 17% through automated controls,
  • confidence exceeds proof: 56% of executives say they are very confident in the accuracy of their invoices, but only 22% can provide within 24 hours the file that justifies an invoice,
  • usage weighs more and more: 70% of organizations say that at least 26% of their revenue depends on usage or consumption, where leaks are most frequent.

Two reasons make this cost particularly high. First, a euro recovered from a leak is a euro of margin: it requires no new customer and no new sales spend. Second, a leak is recurring: an option forgotten for a subscriber is forgotten every month, until someone notices.

Conversely, not every error works against the company. Overbilling is an error too. It costs nothing at the time, but it is paid for in disputes, credit notes, time spent and lost customers.

The 10 sources of revenue leakage, from quote to cash

Revenue leakage happens all along the quote-to-cash cycle: in the price catalog, the quote, the contract, the order and activation, usage collection, rating, the invoice, collection, credit notes and renewals. Leaks are born mostly at handoffs between teams and between systems.

Step Typical leak How it happens
1. Catalog and prices Outdated or inconsistent price A price increase is decided but not carried into every system
2. Quote Off-policy discount A discount granted without approval or end date
3. Contract Clause not applied Annual indexation, minimum usage or penalty never billed
4. Order and activation Active service not billed Technical activation does not trigger the subscription in billing
5. Usage Data lost Usage records rejected, duplicated or never collected
6. Rating Wrong price applied Tier, plan or proration calculated wrongly
7. Invoice Late or wrong invoice Month-end billing, tax errors, wrong entity
8. Collection Payment not recovered Rejected direct debit not retried, no reminder, payment not matched
9. Credit notes Unjustified credit note Uncontrolled goodwill gesture, double refund
10. Renewals Frozen price or cancellation not processed Contract renewed at the old price, service kept running without a contract

Of these ten sources, three account for a large share of losses at companies billing services:

  • activation without billing, when the system that starts the service does not talk to the system that bills,
  • lost usage, when usage data goes through several collection and checking steps without anyone comparing what comes in and what goes out,
  • forgotten contract clauses, such as annual indexation or minimum commitments, written in a PDF but never configured.

Our quote-to-cash guide shows why these handoffs are so fragile.

Leakage by pricing model and industry

The more complex the pricing model, the higher the risk of leakage. A one-off sale leaks little; a subscription leaks at every plan change; usage-based billing leaks as soon as a usage record is lost. Telecoms, energy, SaaS, AI and IoT combine these risks.

Model or industry Most frequent leaks Read more
Subscription Miscalculated proration, upgrade not billed, temporary discount never stopped, failed direct debit Recurring billing
Usage-based billing Usage records lost or rejected, wrong tier, overages not billed Usage-based billing
Telecoms Calls and data not rated, services active on the network but missing from billing, roaming agreements settled wrongly Telecom billing and BSS
Energy Meter readings and estimates trued up wrongly, taxes applied wrongly, supplier switches dated wrongly Energy billing software
SaaS and AI Users or credits consumed beyond the contract, API calls not counted, minimum commitments not billed SaaS billing
IoT Devices activated without a subscription, fleet poorly reconciled, partner payouts wrong IoT billing

What these industries have in common is volume. An error of a few cents, repeated across millions of usage events or hundreds of thousands of subscribers, becomes a considerable amount. That is why these industries were the first to organize the fight against leakage.

Why leakage stays invisible

Revenue leakage is invisible because it produces no event: no wrong invoice to dispute, no unhappy customer, no accounting entry. It only appears when you reconcile two sources that should match, for example active services and billed services.

Several reasons explain why leaks go unnoticed:

  • each team sees only its own tool: sales see the CRM, operations see the network or the technical platform, finance sees the ERP. Nobody sees the whole journey,
  • customers never report underbilling: only overbilling comes back, as disputes,
  • controls check the invoice, not what is missing: teams check that an invoice is right, rarely that an invoice should have existed,
  • spreadsheets fill the gaps: enterprise accounts, exceptions and special offers are often handled by hand, outside any control.

A few warning signs should raise suspicion of a leak:

Signal What it may reveal
The number of active customers grows faster than billed revenue Active services not billed
Disputes often concern the same offers Price rules configured wrongly
Many manual adjustments before each billing cycle A system that cannot bill some offers
Discounts nobody can trace Discounts with no end date or approval
Gaps between measured usage and billed usage Usage data lost or rejected
A long time to launch a new offer Offers worked around by hand in billing

How to calculate revenue leakage

To calculate revenue leakage, compare expected revenue, calculated from contracts and services actually delivered, with revenue actually billed and then collected. The gap, adjusted for decided discounts and bad debts, gives the leakage.

The basic formula:

Leakage rate = (expected revenue − billed revenue) ÷ expected revenue × 100

Expected revenue is rebuilt from three sources: contracts (prices, approved discounts, clauses), active services (subscriptions, options, devices or lines in service) and measured usage.

Example: a service provider has 20,000 subscribers. Reconciling the technical platform with billing shows that 300 options at €15 a month are active but not billed. The leak is 300 × 15 = €4,500 a month, or €54,000 a year. If these options have been active for 18 months on average, the cumulative loss reaches €81,000, only part of which can be recovered from customers.

Three precautions:

  • start with a limited scope: one offer, one customer segment, one billing month,
  • separate recoverable and lost leaks: back-billing the past is rarely possible or commercially desirable,
  • count overbilling too: it does not lose money immediately, but it costs in disputes and trust.

Detecting leakage: a 6-step audit

A revenue leakage audit maps the cycle from quote to cash, then systematically reconciles data that should match: contracts and subscriptions, active and billed services, measured and billed usage, invoices issued and payments received.

  1. Map the cycle. Draw the journey of a sale, from quote to cash, with the teams, systems and data transfers at each step. Spot re-keying and intermediate files.
  2. Reconcile contracts and subscriptions. Does every signed contract have a subscription in billing, at the right price, with the right discounts and indexation clauses?
  3. Reconcile active and billed services. Compare the list of services, options, lines or devices active in technical systems with what is billed.
  4. Reconcile measured and billed usage. Count usage records at each step, from collection to invoice, and explain every gap: rejections, duplicates, pending data.
  5. Reconcile invoices and payments. Identify failed payments not retried, receivables not chased and unmatched payments.
  6. Quantify, fix and prevent. Rank leaks by amount, fix the cause in the process or configuration, and put a permanent control in place so they do not come back.

A one-off audit reveals past leaks. Only continuous control prevents the next ones. That is the principle of revenue assurance.

Revenue assurance: the telecom method for every company

Revenue assurance is the discipline that organizes permanent control of revenue: automatic reconciliations at each step, alert thresholds, named owners and tracking of recovered losses. Born at telecom operators, it now applies to any company billing subscriptions or usage.

Operators were the first to formalize this function, because they process billions of usage events and a loss of a few per thousand represents large sums. A revenue assurance team often works alongside the fraud management team.

Its principles apply to any company:

  • end-to-end controls, from the network or technical platform all the way to accounting,
  • automatic reconciliations, run at every cycle and not once a year,
  • thresholds and alerts: a gap above a defined level triggers an analysis,
  • one owner per control, with tracking of causes and fixes,
  • measured gains: amounts detected, recovered and avoided.

For a company without a dedicated team, the first step is to give one person end-to-end responsibility for revenue, often in finance or operations, and give them the essential reconciliations.

Revenue leakage KPIs

The main revenue leakage KPIs are the leakage rate, the share of active services not billed, the share of usage records rejected, the disputed invoice rate, credit note volume and the share of failed payments not recovered.

KPI What it measures What it reveals
Leakage rate Gap between expected and billed revenue The overall scale of the problem
Active services not billed Share of services in operation with no matching billing A break between activation and billing
Rejected usage Share of usage records rejected or pending The quality of collection and configuration
Disputed invoices Share of invoices that are disputed Errors visible to the customer
Credit note volume Credit notes relative to revenue After-the-fact corrections, uncontrolled gestures
Failed payments not recovered Share of rejected payments never settled The effectiveness of dunning and collection
Manual adjustments Number of manual corrections per cycle Offers the system cannot bill

These KPIs are best tracked every month, by offer and by customer segment. A drop in the number of manual adjustments is often the first sign that a billing system has become reliable.

How to prevent revenue leakage

To prevent leakage, remove re-keying, base sales, activation and billing on a single offer catalog, automate price and usage calculation, check invoices before sending and monitor gaps continuously. A single billing platform, open to CRM and ERP, is the most effective lever.

The levers, in order of impact:

  1. A single offer catalog. The same products, prices and rules serve the quote, the order and the invoice. A price increase is made in one place.
  2. Controlled discount rules. Every discount has a cap, an approval and an end date, managed automatically by the system.
  3. Activation that triggers billing. When an order goes into service, it automatically creates the billable subscription.
  4. A controlled usage chain. Every usage record is counted, checked and traced from collection to invoice; rejections are handled, not forgotten. See our guide to billing mediation.
  5. Configured contract clauses. Indexations, minimum commitments and penalties live in the system, not only in the contract.
  6. Pre-invoice checks. Comparison with the previous invoice, detection of abnormal amounts, tax checks.
  7. Automated collection. Failed payments retried, graduated reminders, automatic cash application. See our guide to reducing DSO.
  8. Continuous monitoring. The KPIs above, tracked every month.

What AI changes

AI agents are particularly useful against leakage, because they can spot what is out of the ordinary in large volumes: an abnormally low invoice, a customer whose usage drops for no reason, a discount that lasts too long. Our guide to AI agents for billing presents these use cases and the conditions for success.

Where Opencell fits

Opencell is an open source monetization platform covering the whole cycle where leaks occur: a single offer and price catalog, quotes, orders and activation, usage collection and rating, billing, payment and dunning. Because every step shares the same data, the breaks that cause leakage disappear. The platform integrates with CRM and ERP through more than 200 APIs and connectors.

Born in telecoms in 2007, where fighting revenue leakage is a discipline in its own right, Opencell now manages €14 billion in revenue for around fifty customers, including Orange Business Services, Engie, TotalEnergies, OVHcloud, La Poste and Actility.

Frequently asked questions about revenue leakage

What is revenue leakage?

Revenue leakage is revenue a company has earned, through a contract or a delivered service, but does not bill, bills wrongly or does not collect. It comes from errors, omissions and breaks between teams and systems, not from a commercial decision.

What are the most common causes of revenue leakage?

Services activated but not billed, lost usage data, discounts with no end date, contract clauses such as indexation never configured, pricing errors and failed payments never recovered.

How much revenue do companies lose to leakage?

It depends on the pricing model and process quality. In a 2026 DigitalRoute survey of 631 executives, 60% of organizations estimate at least 2% of revenue is exposed to billing errors, and 33% put it at 5% or more.

How do you calculate revenue leakage?

Compare expected revenue, rebuilt from contracts, active services and measured usage, with revenue actually billed. The leakage rate is the gap divided by expected revenue. It is best to start with a limited scope, such as one offer and one billing month.

What is revenue assurance?

Revenue assurance is the discipline that organizes permanent control of revenue through automatic reconciliations, alert thresholds and named owners. Born in telecoms, it applies to any company billing subscriptions or usage.

How do you prevent revenue leakage?

Remove re-keying, use a single offer catalog for quote, order and invoice, automate pricing and usage rating, check invoices before sending and track a few KPIs every month, such as active services not billed.

What is the difference between revenue leakage and lost opportunity?

A lost opportunity is revenue that could have been won with another decision, such as a higher price. Revenue leakage is revenue already won, provided for by the contract or the service delivered, then lost along the way through an error.

Is revenue leakage the same as bad debt?

No. Bad debt is a correct invoice that is never paid. Revenue leakage is revenue that was never billed, was billed wrongly or was lost through process failures, including failed payments nobody followed up.

Revenue leakage does not show. It has to be measured.

Revenue leakage is one of the few growth sources that needs no new customer. It only requires looking at the cycle from quote to cash as one whole, reconciling what should match and removing the breaks that let money slip away.

Key takeaways:

  • revenue leakage is revenue earned but not billed, wrongly billed or not collected,
  • exposure often runs to several points of revenue, almost entirely margin,
  • leaks are born at handoffs: activation, usage, contract clauses, discounts,
  • they are detected through reconciliations and prevented by a single catalog and automated billing,
  • revenue assurance turns a one-off audit into permanent control.

The cheapest revenue to win is the revenue you have already won.

Go further with Opencell

Opencell is an agile, open source monetization platform that automates quote-to-cash, from quote to cash collection, for subscription and usage-based services. Born in telecoms in 2007, where fighting revenue leakage is a discipline in its own right, it manages €14 billion in revenue for around fifty customers, including Orange Business, Engie, TotalEnergies, OVHcloud, La Poste and Actility.

Want to measure and reduce your revenue leakage?

Optimize your recurring revenues with Opencell

Get a demo