Revenue Leakage

What is revenue leakage?

Revenue leakage (also called revenue loss, revenue slippage, or billing leakage) is the gap between what a company is contractually owed and what it actually collects. It happens when invoices go unpaid, charges fail silently, discounts are applied incorrectly, renewal dates are missed, or upsell opportunities go uncaptured. Operators use revenue leakage as a diagnostic metric to find and fix collection failures.

The cumulative impact of leakage is significant. A $10M ARR company leaking 3% annually loses $300K — enough to fund 2 full-time hires or 6 months of additional marketing spend. The problem compounds because most leakage is invisible in standard reporting. The CRM shows the deal as "closed-won." The finance tool shows the invoice as "sent." But the money never arrived.

For B2B SaaS companies with recurring revenue, healthy leakage rates sit below 2% of annual revenue. Companies between 2-4% have identifiable and fixable leakage sources. Above 5% typically signals systemic billing or renewal process failures that require immediate operational intervention.

Revenue leakage is not margin compression. Margin compression measures profitability declining on revenue you did collect. Revenue leakage measures money you never collected at all. Both reduce the bottom line, but they have different causes and different fixes.

Why revenue leakage matters for operators

Revenue leakage represents the highest-leverage profitability fix available to most operators — because it recovers money already earned without requiring new customers, new channels, or new products. Every dollar of recovered leakage drops directly to the bottom line.

The operational blind spot exists because leakage hides in the gaps between systems. The CRM marks a deal as won. The billing system sends an invoice. But between those two events, things break: a payment method expires, a discount code is applied twice, a renewal date passes without a notification, an annual contract auto-converts to month-to-month at a lower rate.

A typical $8M ARR SaaS company auditing revenue leakage for the first time discovers $180K-$400K in annual losses across 3-5 sources. The most common finding: failed payment retries that the billing system silently abandoned after 2 attempts, converting paying customers to involuntary churn. The second most common: discounts that were approved for the first contract year but never removed at renewal.

Revenue leakage formula

Revenue Leakage = Expected Revenue - Actual Collected Revenue

Example:
Expected Revenue (based on contracts + renewals): $847,200
Actual Collected Revenue (cash received in Stripe): $819,450

Revenue Leakage = $847,200 - $819,450 = $27,750 (3.3%)

What each component means:

• Expected Revenue: The total revenue the company should collect based on active contracts, agreed pricing, scheduled renewals, and committed upsells. Pull this from the CRM (contract values) and billing system (scheduled invoices).
• Actual Collected Revenue: The cash that was actually received and recognized. Pull this from the payment processor (Stripe, payment gateway) or accounting system (QuickBooks, Xero). Do not use "invoiced" amounts — use "collected" amounts only.

Revenue leakage rate (percentage):

Revenue Leakage Rate = (Expected Revenue - Actual Collected Revenue) / Expected Revenue x 100

Example:
($847,200 - $819,450) / $847,200 x 100 = 3.3%

Some operators break leakage into sub-categories for diagnosis: billing leakage (failed charges, invoice errors), renewal leakage (missed renewals, downgrades at renewal), and pricing leakage (unauthorized discounts, grandfathered rates never updated).

Revenue leakage benchmarks

How revenue leakage varies across B2B company segments. Ranges based on EY Global Revenue Leakage Survey (2024) and industry-observed data.

Sources: EY Global Revenue Leakage Survey 2024, Zuora Subscription Economy Index, industry-observed ranges.

Common mistakes when measuring revenue leakage

1. Using invoiced revenue instead of collected revenue as the baseline

Invoiced revenue includes invoices that were sent but never paid. Comparing expected revenue to invoiced revenue understates leakage because it counts unpaid invoices as "collected." Always use cash received from the payment processor or accounting system.

2. Ignoring involuntary churn as a leakage source

When a credit card expires and the payment retry fails, most billing systems mark the customer as churned after 3-4 attempts. This is involuntary churn — the customer did not choose to leave. Smart dunning sequences recover 20-40% of failed payments. Without them, the company records churn when it should record a billing recovery.

3. Not auditing discount persistence at renewal

A 20% discount approved for a new customer's first year should expire at renewal. In practice, many billing systems carry the discount forward automatically. A $15K ACV deal renewed at 20% off for 3 additional years costs $9K in leakage that never shows up as a "discount" — it just looks like a smaller contract.

4. Measuring leakage annually instead of monthly

Annual leakage audits catch the total damage but not the source in real time. Monthly measurement — comparing expected collections to actual collections — allows operators to identify and fix leakage sources within 30 days instead of discovering them during an annual finance review.

5. Treating all leakage as equal

A $500 failed charge on a $500/month customer is a different problem than a $500 pricing error across 50 accounts. The first requires a dunning fix. The second requires a billing system audit. Categorizing leakage by source — billing, renewal, pricing — enables targeted intervention.

How Fairview tracks revenue leakage

Fairview's Margin Intelligence engine reconciles expected revenue from the CRM with actual collected revenue from Stripe, QuickBooks, or Xero — calculating the leakage gap automatically. The Operating Dashboard displays leakage as a dollar amount and percentage, with drill-down by source category.

When Fairview detects a leakage pattern — a cluster of failed charges, a renewal cohort with persistent discounts, a pricing discrepancy between the CRM contract value and the billing system — the Next-Best Action Engine generates a specific recommendation: "12 accounts with expired payment methods have failed retry sequences. Total at-risk revenue: $14,200. Trigger manual outreach."

The Weekly Operating Report includes a leakage summary with week-over-week trends, enabling operators to track recovery progress against identified sources.

→ See how Fairview detects revenue leakage

Revenue leakage vs margin compression

People sometimes confuse revenue leakage with margin compression. They affect the bottom line differently.

Revenue leakage is a collection problem. Margin compression is a profitability problem. A company can have zero leakage and still experience severe margin compression — and a company with perfect margins can still leak 4% of revenue through billing failures. Both need separate tracking.

FAQ

What is revenue leakage in simple terms?

Revenue leakage is money your business earned but never collected. It happens when charges fail silently, discounts persist beyond their agreed term, renewals get missed, or billing errors go undetected. The average B2B SaaS company loses 1-5% of annual revenue to leakage — money that is already owed but never arrives.

How do you calculate revenue leakage?

Subtract actual collected revenue from expected revenue. Expected revenue comes from active contracts and scheduled renewals in your CRM. Actual collected revenue comes from your payment processor or accounting system. The difference is your leakage. Express it as a percentage: (Expected - Actual) / Expected x 100.

What are the most common sources of revenue leakage?

The five most common sources: failed payment retries (involuntary churn), persistent discounts that were not removed at renewal, billing errors (wrong amount invoiced), missed renewal dates, and uncaptured upsell revenue from contract expansions that were agreed but never billed. Failed payments alone account for 20-40% of total leakage in most SaaS companies.

What is a normal revenue leakage rate for SaaS?

Below 2% of annual revenue is considered well-managed. Between 2-4% is average and indicates fixable leakage sources. Above 5% signals systemic billing or renewal process failures. Growth-stage SaaS companies ($1-10M ARR) typically leak 2-4% before implementing dedicated leakage tracking (EY Global Revenue Leakage Survey, 2024).

How often should you audit for revenue leakage?

Monthly. A monthly reconciliation of expected vs. actual collected revenue catches new leakage sources within 30 days. Annual audits reveal the total damage but miss the opportunity for early intervention. The highest-impact cadence is a monthly audit with a quarterly deep review by leakage category.

How do you fix revenue leakage?

Start by categorizing leakage into billing (failed charges, invoice errors), renewal (missed dates, persistent discounts), and pricing (unauthorized discounts, grandfathered rates). Then address each category: implement smart dunning for billing leakage, set renewal reminders for renewal leakage, and audit discount rules for pricing leakage. Most companies recover 40-60% of identified leakage within 90 days.

Related terms

• Margin Compression — The gradual decline of profit margins over time, distinct from leakage because it affects collected revenue rather than uncollected revenue
• Gross Margin — Revenue minus cost of goods sold, expressed as a percentage — the profitability metric most immediately affected by recovered leakage
• Contribution Margin — Revenue minus all variable costs for a specific channel or segment, used to identify where leakage has the greatest profit impact
• Operating Intelligence — Software that connects business data to surface insights like revenue leakage automatically
• Churn Rate — The percentage of customers or revenue lost in a period, often inflated by involuntary churn caused by revenue leakage

Fairview is an operating intelligence platform that tracks revenue leakage automatically alongside margin compression, contribution margin, and forecast confidence. Start your free trial →

Siddharth Gangal is the founder of Fairview. He built leakage detection into the platform after discovering that most operators do not know they are losing 1-5% of revenue until someone reconciles the numbers for them.