What it means
A service company completes work under a customer contract, but its billing system still holds an older price, so the invoice is lower than the agreed charge, and a revenue leakage review traces that difference from the contract through delivery, invoice, adjustment and collection. Salesforce describes revenue leakage across the revenue lifecycle, including pricing, contracts, billing and renewals, and TM Forum publishes a revenue-assurance leakage framework for telecom operators, so the shared lesson is to follow a transaction through its full chain rather than count only unpaid invoices.
Set the scope by deciding whether the review covers one product, contract group, channel, period or the whole business, and state what counts as earned revenue. Start with entitlement, since a signed contract, approved order or published tariff sets the charge and conditions and an internal forecast alone is not a customer obligation.
Check delivered activity by comparing service logs, shipments, usage meters or completed milestones with what was eligible to bill, remembering that unapproved work may not be collectible. Trace price setup to confirm that approved rates, volume bands and effective dates reached the quoting and billing systems, because a correct contract can still produce a wrong invoice.
Check discounts, since promotional, loyalty and negotiated reductions should have an owner, eligible customer and expiry, and a discount left active too long may leak revenue. Review contract amendments and renewals, because a change to scope or price can be agreed outside the original form and automatic continuation, expiry or price escalation can be missed, so verify whether each was executed and how the billing team learned of it.
Watch billing triggers as well, since some invoices issue after delivery, a usage threshold or milestone approval and a missed trigger can leave earned fees unbilled. Separate unbilled from overdue, because work completed but not invoiced is a different issue from an invoiced balance awaiting payment and the controls differ, and inspect credits and refunds, since a valid correction should identify the original invoice and reason while repeated manual credits can hide a product or process fault.
Use reconciliations that match order to delivery, delivery to invoice, invoice to ledger and ledger to cash, allowing for timing. Avoid counting disputed amounts as certain, because a customer may reject an invoice for a defective delivery or an ambiguous contract and recoverability needs evidence.
Identify the root cause, since an omitted usage record calls for metering repair and an obsolete price table calls for change control, and a one-off manual invoice fixes neither. Sample transactions by risk, with high-value amendments, manual overrides, unusual discounts and new product launches deserving closer checks, and state the population and sampling method.
Track leakage stages by recording identified, validated, billed, collected and prevented amounts separately, because detection is not recovery, and estimate the amount by multiplying an approved unit-price difference by eligible delivered units and then adjusting for taxes, agreed credits and collectibility. Measure recurrence, because if the same error returns after a correction the underlying configuration or handoff process needs to change, and assign ownership so that sales manages terms, operations confirms delivery, billing issues invoices and finance reconciles collections through a shared exception queue.
Protect customers by correcting invoices and explaining adjustments under contract and local law, since a surprise back-bill for a long period can damage trust or be time-barred, and set approval controls because not every suspected undercharge should become a debit note. After a price change, run a sample of representative invoices as a prevention test, and remember that for an owner a revenue leakage review is a disciplined search for earned charges lost along the handoff chain, with the goal of accurate, fair billing and not indiscriminate demands for more money.
In practice
Real-world examples.
Example
A signed rate increase never reaches the billing table, so eligible invoices use the old price. The review compares the signed amendment with the price table and finds the effective date was never entered. The table is corrected and a sample of later invoices is tested.
Example
Completed service usage is recorded but never triggers an invoice. The usage file arrives with a new format that the billing system ignores. The team repairs the feed and reviews earlier months for unbilled usage.
Example
A legitimate service credit is incorrectly labelled leakage until the customer agreement is checked. The agreement shows the credit was owed for an outage, so no charge is raised. The finding is recorded as a valid adjustment, not a loss.
Formula
Calculation
Illustrative validated gap = eligible units x (approved price - invoiced price), adjusted for lawful credits, taxes and evidence
Worked example. A fictional company's approved price is $52 per unit, but 400 eligible units were invoiced at $50.
- Suspected gap = 400 x ($52 - $50) = 400 x $2 = $800.
- If $100 of agreed credits applies to those units, the validated gap = $800 - $100 = $700.
- This does not mean $700 has been collected. Approval, customer communication, local law on back-billing and collectibility still decide how much is billed and received.Case study
Seen in the real world.
This entirely fictional example follows Harbor Maintenance. A contract amendment raised a service price, but billing kept the old rate for two months. The team checked signed terms and delivered work, notified affected customers appropriately and changed its price-update approval workflow.
The case does not assume every old invoice may be back-billed under local law. The price rose from $50 to $55 a visit, with 120 visits a month, so the monthly gap was 120 x $5 = $600. The contracts allowed back-billing for only the latest month, so Harbor billed $600 and wrote off the other $600, and the workflow now requires a sample invoice check after every price change.
Watch out
Common mistakes.
- Calling every uncollected invoice revenue leakage without checking the dispute and collectibility.
- Treating a suspected price mismatch as money recovered before validating the contract.
- Fixing one invoice while leaving the outdated price table in place.
Questions
People also ask.
What is the first check?
Verify the contract or approved tariff and what was actually delivered.
Is an unpaid invoice leakage?
It may be a collection issue; trace billing, entitlement and payment separately.
How should recovery be reported?
Separate suspected, confirmed, invoiced and collected amounts.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%Related