Skip to content
ObligaAI

What Is Revenue Leakage?

On this page

Revenue leakage is money a company has earned under its customer contracts but never bills or never collects. The contract says the customer owes it. The invoice says something smaller. Nobody notices, so the gap is never recovered.

It is a sell-side problem. The company providing goods or services loses the money, not the buyer. Typical causes are a price uplift that was never applied, usage above a tier that was billed at the base rate, a minimum commitment that was never trued up, a milestone that was delivered but not invoiced, or a promotional discount that kept running after it should have ended.

Revenue leakage is usually quiet. No customer complains about being undercharged. Each miss is small, but it repeats on every invoice until someone checks the contract against the bill.

How Revenue Leakage Happens

Most leakage happens in the hand-off between the signed contract and the billing system. Sales negotiates the terms. Legal finalises the wording. Billing or finance operations then has to turn that wording into invoice lines. Anything that is not set up correctly at that point, or that changes later, can leak.

BCG describes leakage as “the problem of unrealized revenue from products sold or services performed” and links it to manual invoicing, pricing discretion in client-facing roles and gaps in data systems. One example it gives is a chemical services company that kept invoicing outdated prices because its contracts were not digitised (BCG).

The most common sources are:

  • Missed escalators and uplifts. A price escalation clause raises fees each year by a fixed percentage or by an index such as CPI. If nobody updates the billing rate on the anniversary date, the customer keeps paying last year’s price.
  • Usage over tier. The contract prices usage in bands. Usage grows past the first band, but invoices still use the base rate or ignore the overage.
  • Unenforced minimums. A minimum purchase commitment or take-or-pay contract entitles the seller to a shortfall payment. The shortfall is never calculated or invoiced.
  • Unbilled milestones. Work is delivered and accepted, but the milestone invoice is never raised, or it is raised months late.
  • Expired discounts. A first-year or ramp discount was meant to end. The billing system keeps applying it.
  • Renewal price terms. An automatic renewal clause renews the contract at a new rate, but the old rate rolls forward.
  • Changes nobody carried through. A contract amendment or side letter changes a fee, scope or term, and the billing set-up is never updated.
  • Unused remedies. A late payment fee the contract allows is never charged. Whether to charge it is a commercial choice, but it should be a deliberate one.

Revenue leakage usually starts where contract wording becomes invoice lines, or when terms change after set-up.

Get up to 9% back on your contracts

Why Revenue Leakage Matters

Leaked revenue is margin. The cost of delivering the service has already been incurred. Any amount that should have been billed and was not comes straight off profit.

It also compounds. An uplift missed in year one means every later uplift starts from the wrong base. On a multi-year contract, a single setup error can affect every invoice until renewal, and it can shrink the annual contract value and total contract value the business actually realises compared with what it signed.

The problem is widespread. In BCG’s survey of more than 2,000 business leaders, 45% said leakage is a systemic problem, and BCG reports that most companies lack automated revenue assurance processes (BCG).

There is a reporting angle too. Under IFRS 15, revenue follows a five-step model: identify the contract, identify the performance obligations, determine the transaction price, allocate it, and recognise revenue when each obligation is satisfied (IFRS Foundation). The contract terms drive the transaction price. If billing drifts away from those terms, finance has to explain the difference. How a specific gap should be accounted for is a question for your accountants and auditors, not this article.

Finally, leakage is a customer-relationship issue. Back-billing a customer for two years of missed uplifts is a harder conversation than applying the uplift on time. Whether you can recover past amounts at all depends on the contract wording, any limitation or notice provisions, and the governing law. This article is not legal or accounting advice.

A Worked Example With Illustrative Figures

The figures below are illustrative only. They show how small misses add up on one customer contract.

A software company signs a three-year subscription with these terms:

  • Base fee of $10,000 per month.
  • A fixed 4% uplift on each anniversary.
  • Usage up to 50,000 transactions a month included; $0.05 per transaction above that.
  • A 10% discount for the first six months only.

Here is what goes wrong in year two:

ItemContract saysInvoicedMonthly gapAnnual gap
Base fee after 4% uplift$10,400$10,000$400$4,800
Overage (average 58,000 transactions)$400$0$400$4,800
Expired 10% discount still applied$0 discount$1,000 discount$1,000$12,000
Total  $1,800$21,600

In this illustration, one contract leaks $21,600 in a single year. If the uplift is still missed in year three, the base gap grows, because the contract would now call for $10,816 a month. None of these errors is visible on the invoice itself. They only show up when someone puts the clause next to the bill.

Illustrative: three small misses on one contract add up to $21,600 in a year, and none of them is visible on the invoice.

If the uplift were tied to CPI instead of a fixed 4%, the check would also need the right index. The US Bureau of Labor Statistics advises escalation users to “identify precisely which CPI index series will be used” and shows the calculation: take the change in index points between two periods, divide by the earlier value and multiply by 100 (BLS). A contract that names the index, base period and adjustment date clearly is much easier to bill correctly.

Revenue leakage is often confused with nearby ideas. The differences matter because each has a different owner and a different fix.

TermSideWhat is lostTypical owner
Revenue leakageSell sideAmounts customers owe but are not billed or collectedFinance, billing operations, revenue operations
Contract value leakageBoth sidesAny value the contract promised but the business did not realiseFinance, procurement, legal
OverbillingBuy sideAmounts a supplier charges above the contractProcurement, accounts payable
Bad debtSell sideAmounts billed but never paidCredit and collections

Contract value leakage is the umbrella. Revenue leakage is the sell-side part of it. Supplier overbilling and unclaimed service credits are the buy-side parts.

Revenue leakage is also different from bad debt. Bad debt starts with an invoice that was raised and not paid. Revenue leakage usually starts earlier: the right invoice was never raised.

It also differs from pricing strategy. Choosing to waive an uplift for a strategic customer is a decision. Revenue leakage is when nobody decided, and the money was simply missed.

How to Track and Prevent Revenue Leakage

The fix is not complicated. It is discipline: compare what the contract says with what was billed, on a regular cycle, with someone accountable for the answer.

  1. Build a single record of billable terms. For each customer, list the fees, uplift dates and method, usage tiers, minimums, milestones, discounts with end dates, and renewal terms. Include every amendment and side letter. This is the core of contract obligation management on the sell side.
  2. Calendar the dates that change price. Anniversaries, discount end dates, renewal dates and milestone due dates should trigger a billing review before the next invoice run, not after it.
  3. Reconcile invoices against the contract. Run a contract-to-invoice check each billing cycle. The logic mirrors invoice reconciliation and three-way matching on the buy side, but in reverse: the question is whether you billed enough, not whether you were charged too much.
  4. Reconcile usage against invoices. Compare usage or delivery records with what was billed. For software, this is the logic behind a license true-up.
  5. Check price lists and rate cards. Make sure the rate card in the billing system matches the one in the signed contract, including any customer-specific rates.
  6. Set a materiality threshold. Decide the minimum amount worth investigating so the team spends time on gaps that matter.
  7. Assign an owner and a decision. Each finding needs someone to confirm it, decide whether to bill it, and record why. Some gaps will be deliberate concessions; those should be documented, not left as unknowns.

BCG recommends starting with a diagnosis of root causes, piloting quick wins, then scaling, alongside auditing and simplifying manual steps in quote-to-cash (BCG).

Where ObligaAI Fits

ObligaAI’s revenue leakage product compares customer contracts with invoices so uplifts, usage and milestones are not missed. It reads customer contracts, order forms, renewals, price lists, usage reports and invoices, and checks fees, escalators, usage tiers, discounts, minimums, milestones and renewal terms.

It matches records across three streams: contract to invoice, usage to invoice, and milestone to invoice. Each finding shows the clause, the invoice, the shortfall, its dollar value and a recommended action. Clauses are turned into plain-language obligations linked to the source passage, with a confidence score. Tolerance can be set per customer or organisation-wide, with a minimum amount below which nothing is flagged.

ObligaAI is advisory first. Findings are suggestions with the clause attached, never automatic changes, and no invoice is changed until the right person signs it off. It works as an overlay beside the billing and contract systems you already run, not a replacement for them.

You can start free or start a conversation about your setup.

Frequently Asked Questions About Revenue Leakage

What is a simple definition of revenue leakage?

Revenue leakage is money your customers owe under their contracts that you never bill or never collect. It is the gap between what the contract entitles you to and what your invoices actually charge.

What are the most common causes of revenue leakage?

The most common causes are missed price uplifts, usage billed below the contracted tier, minimum commitments that are not enforced, milestones that are not invoiced, discounts that run past their end date, and amendments that never reach the billing system.

Is revenue leakage the same as contract value leakage?

No. Contract value leakage covers both sides of the business. Revenue leakage is the sell-side part: money you should have billed customers. The buy-side parts include supplier overbilling and unclaimed service credits.

Can you back-bill a customer for missed revenue?

Sometimes. It depends on the contract wording, any limitation or notice provisions, the customer relationship and the governing law. Get legal advice before back-billing significant amounts. This article is not legal advice.

How often should we check for revenue leakage?

Check every billing cycle for high-value or complex contracts, and before each anniversary, renewal or discount end date. A one-off review finds past gaps; a regular cycle stops new ones.

Who should own revenue leakage?

Usually finance or billing operations, working with sales operations and legal. The key is that one named person owns each finding and records whether it was billed, waived or disputed.

Sources

More in Billing & Finance

Get up to 9% back on your contracts

Start with a few contracts of your own and see what ObligaAI finds.