From Cost Center to Capital Recovery: Rethinking the AR-to-Collections Handoff

At 30 days past due, the probability of collecting a B2B software invoice in full is above 95%. At 60 days, it drops to around 80%. At 90 days, it is below 70%. At 120 days, it sits below 50%. By the time most software companies decide to escalate an unpaid invoice to third-party collection, they have already lost half the value of the receivable — not because the debtor cannot pay, but because the window of maximum leverage expired while the finance team was hoping the customer would "come around."

The pattern is consistent across the software companies we work with. Internal AR sends a handful of polite reminders. Customer success makes a call to preserve the relationship. The finance team discusses the account in a weekly review. Nobody wants to be the person who escalated a customer to collections and triggered a churn event. By the time that reluctance is overcome, the receivable is aged past the point where a demand letter alone would have resolved it — and the decision of whether to escalate to a collection agency or an attorney is no longer a strategic choice but a desperate one.

The real cost of waiting

What makes this pattern expensive is not just the declining recovery rate. It is the compounding effect on the rest of the balance sheet. Every account that crosses 90 days becomes more likely to be written off entirely. And every write-off reduces the trailing revenue metrics that investors and lenders use to price your company. A $50,000 write-off on a $5M ARR portfolio is a statistical rounding error. A $250,000 write-off on a $5M ARR starts to look like a pattern — and patterns get priced into debt facilities, insurance renewals, and acquisition multiples.

A programmatic handoff protocol

• At 60 days past due: The account moves from internal AR to a structured pre-collection review. The contract, the invoices, and the communication history are packaged into a single file. A written assessment of collectibility is produced using the same criteria a recovery partner would apply — debtor creditworthiness, contract enforceability, dispute history.
• At 75 days past due: If the account has not responded to the most recent internal demand, the file is shared with a specialist recovery partner on a contingency basis. No upfront cost. The partner begins a soft-contact phase — verification of the debtor's current legal entity, asset profile, and jurisdiction.
• At 90 days past due: Formal demand is sent by the recovery partner on agency letterhead. At this stage, the receivable is still in the high-recovery window. And because the partner works for a share of what is collected — not a retainer — the software company has no financial risk in the escalation.

The numbers that justify the trigger

A software company with $10M in annual billings and a 2.5% bad-debt rate is writing off $250,000 per year. Moving the escalation trigger from 120 days to 60 days on just half of those accounts — and recovering at the higher 60-day probability rate — would add roughly $85,000 to the recovery line. That is not a theoretical improvement. It is the arithmetic of recovery probability curves applied to the data your aging report already contains.

The reluctance to escalate early is understandable. But the math does not support it. A structured handoff protocol that triggers at 60 days, uses a contingency-based partner, and resolves the account before 90 days preserves the customer relationship because the collection process is professional, measured, and complete before the debtor ever feels "collected." The accounts that would have churned under a 120-day escalation are often the ones most relieved to have the issue resolved.

The takeaway

The AR-to-collections handoff is not a last resort. It is a financial decision with a measurable probability curve. The only question is whether you are deliberately optimizing that timing or letting reluctance make the choice for you.