Revenue leakage in SaaS: the 1–3% of ARR hiding in your billing gaps

The invoice was sent. The service was delivered. The customer used the software for three months. And the invoice went to 120 days, then to 180—then got written off as a bad-debt expense because the finance team had already closed the quarter and the AR was "too much work to chase."

That's not churn. That's revenue leakage—and it is almost certainly sitting in your sub-ledger right now.

Leakage is not what you think it is

When SaaS finance teams hear "revenue leakage," most heads go to billing errors: seat undercounts, usage not captured, renewal escalators not applied, credits given but never reversed. Those are real, and most subscription billing platforms have run-rate leakage audits that find them. Industry estimates put total billing leakage at 1–5% of ARR, depending on contract complexity and billing infrastructure quality.

But billing errors are the part the billing system can find. There's a larger category the billing system never sees: invoices that were valid, were delivered, and were never paid.

The aging report is a leakage report. Every line item at 90+ days past due is revenue the P&L has recognized but the bank account has not received. If your renewal rate is 90% but your cash conversion on invoiced receivables is 93%, you didn't lose 10% of your revenue to churn—you lost an additional 7% to non-payment, and that number never appears in the churn analysis.

The 2% you already paid for

Run the math on your own book. A $10M ARR SaaS company with a 2% invoiced-but-uncollected rate has $200K sitting in past-due receivables. At our standard 25% contingency on fresh accounts placed under 12 months, recovering that $200K costs $50K in fees. Net recovery: $150K that hits the P&L as pure recovery—revenue the company already earned but had stopped expecting to collect.

Compare that to earning $150K of new ARR. At a 3× revenue multiple, a public SaaS company needs $50K of new ARR to create that same $150K of enterprise value. The recoverable receivable is already sitting in your AR aging. You've already paid the sales commission on it. You've already recognized it in your public or board reporting. The only question is whether you convert it to cash.

What makes a past-due invoice collectible

Not every aged receivable is recoverable. The ones that are share a common profile: the contract is valid, the service was delivered, and the debtor has the financial capacity to pay. The documents that prove that profile are:

• A signed order form or contract—with the debtor's entity name matching the invoice, not a parent company or a trade name
• An invoice trail—showing the invoice was sent, delivered, and not disputed within the contract's dispute window
• Usage or access logs—proving the software or service was actively used during the billing period (the single most effective silence-breaker in a collection conversation)
• Payment history—partial payments, past payments on the same contract, or payments on older invoices that establish the debtor as a willing payer who has simply stopped

When a SaaS company places an account with those four documents in hand, the case moves from "maybe" to "proven collectible" within the first review. The documentation is not a formality—it is the difference between a 10-day resolution and a six-month stalemate.

The gap most finance teams miss

Finance teams track churn. They track NRR and gross retention. They track monthly recurring revenue and ARR additions. Many do not track what was billed, went past due, and stayed there—because their reporting framework treats a recognized receivable as revenue, and the collection as a working-capital event rather than a revenue event.

This creates a blind spot. A customer who stops paying but never formally cancels falls between two reporting categories: the revenue team does not flag them (they are not technically churned), and the AR team works them but without the escalation discipline reserved for churn risks. The account sits at 150 days, then 210, then gets written off as an operating expense in the bad-debt line.

The function that closes that gap is not better billing software. It is a collection process that starts at 90 days, not at 180.

How to recover it

The recovery process for invoiced-but-uncollected SaaS receivables is the same one we use for every account, and it is designed for cases where the debt is valid and the dispute is absent or manufactured:

• Free claim evaluation—We review the contract, the invoice trail, and the debtor's profile. We tell you honestly what is collectible, what the expected recovery range is, and whether to place it. No cost, no obligation.
• Contract and documentation review—We confirm the entity, the payment terms, and the enforceability of the agreement. If the contract is missing a venue clause or an interest provision, we adjust the strategy.
• Strategic demand—Contact via the channel the debtor actually responds to. For SaaS debtors, this is often email with a PDF of the signed order form attached. The demand frames the obligation, the usage evidence, and the settlement options.
• Settlement or full recovery—Most SaaS accounts settle within 45 days. Those that don't escalate to demand letter, then to legal placement if the balance justifies it. Same contingency fee on every outcome—we only get paid when you do.

The pricing is the same as domestic: 25% for accounts under 12 months old, 33% for older debt, 40% for second placements from another agency. No recovery, no fee. Free evaluation.

The short version

Revenue leakage in SaaS is real, it's measurable, and most of it is not in your billing software—it's in your 90+ aging bucket. If you have $10M ARR with even a 2% leakage rate, there is $200K of already-recognized revenue sitting in your sub-ledger. The invoicing is done. The service was delivered. The only missing step is the collection call. Send us the contract and the aging report. We'll tell you in one business day what's recoverable.