September 8, 2026
Collections
Collections is the process a subscription business uses to recover payments that are outstanding or overdue, moving an unpaid invoice back to paid through a sequence of automated retries, customer communication, and, when those fall short, manual follow-up or external escalation.
In a subscription business, collections is a continuous, mostly automated function rather than a last resort. Because charges recur on every billing cycle, a share of payments will always fail for reasons that have nothing to do with a customer's intent to pay: an expired card, an insufficient balance, a temporary bank decline, or a fraud filter that stops a legitimate charge. Collections is the machinery that catches those failed and past due invoices, works them methodically, and returns the revenue that would otherwise be lost, while keeping the customer relationship intact.
Why collections matters for subscription businesses
Every failed payment is revenue the business already earned but has not been paid for, and left alone it turns directly into churn. Most of that churn is involuntary: the customer still wants the service, but a payment problem quietly ends the subscription. When collections is weak, that loss compounds every cycle, cash flow becomes unpredictable, and the business ends up reacquiring customers it never meant to lose. Collections is the safety net under Recurring billing that keeps a recoverable failure from becoming a cancellation.
Collections depends on accurate Invoicing upstream: you cannot cleanly recover a charge if the invoice underneath it was wrong to begin with. It leans heavily on Dunning as its primary automated engine, and its outcomes flow into Involuntary churn and MRR, since every invoice it recovers is revenue that stays on the books instead of leaking out.
How to use collections to recover overdue payments
A collections process works an unpaid invoice through escalating stages, starting with the cheapest and least intrusive recovery and moving toward manual effort only when automation is exhausted.
Detection: the system flags an invoice as failed or past due, either when an automatic charge is declined or when an invoiced, terms-based account passes its due date without payment.
Retry: for automatically collected accounts, the system reattempts the charge on a schedule, spacing retries to catch temporary declines and align with when funds or a refreshed card are likely to be available.
Communication: the customer is notified of the failed or overdue payment and prompted to act, usually to update an expired or invalid payment method, through a sequence of reminders that escalates in tone over time.
Self service recovery: the customer updates their payment details or pays through a hosted link, which lets the system collect without any manual work.
Manual follow up: invoices that automation cannot recover are routed to a person for direct outreach, negotiation of terms, or a payment arrangement, most common on higher value or invoiced accounts.
Resolution: a successful payment closes the invoice as paid. An invoice that stays unrecovered past policy is written off as uncollectible, sent to an external collection agency, or allowed to lapse into cancellation, depending on the business's rules.
Collections vs dunning
Collections and dunning are closely related and often used interchangeably, but they are not the same thing. Dunning is the automated core of collections: the scheduled sequence of payment retries and customer reminders that runs when a charge fails, aimed at recovering the payment before the subscription lapses. Collections is the broader process that contains dunning and everything around it, including the manual outreach, payment arrangements, write off decisions, and external escalation that begin where automation ends.
Put simply, dunning is what the system does automatically to recover a failed payment, and collections is the whole discipline of recovering owed money, of which dunning is the first and largest part. A business can run dunning without a mature collections process, but it cannot run collections well without dunning doing most of the work.
Common mistakes with collections
Retrying failed charges on a naive fixed schedule, so attempts land when funds are unlikely to be available and burn through retry limits without recovering the payment.
Treating every decline the same, when a hard decline, such as for a closed account or reported stolen card, needs the customer to act while a soft decline, such as for a temporary or insufficient funds error, often clears on a later retry.
Sending dunning emails that read as generic overdue notices rather than a clear, easy prompt to update a payment method, which suppresses the self service recovery that is the cheapest path.
Letting the retry sequence run so long or so aggressively that it annoys good customers or triggers card network penalties, instead of stopping at a sensible point and handing off to manual follow up.
Failing to update the subscription state and access correctly during collections, so a customer who has paid is still locked out, or one who never paid keeps full access indefinitely.
Benefits and examples
Recovers revenue that was already earned, turning failed payments back into paid invoices instead of silent cancellations.
Reduces Involuntary churn by catching expired cards and temporary declines before they end an otherwise healthy subscription.
Smooths and protects cash flow by shrinking the pool of outstanding and past due invoices each cycle.
Preserves the customer relationship, since a well timed reminder to update a card keeps a paying customer rather than forcing a costly reacquisition later.
Scales recovery across the whole subscriber base through automation, so the business is not manually chasing every failed charge.
Frequently asked questions
What is collections in subscription billing? It is the process of recovering outstanding or overdue payments from subscribers, combining automated retries and customer reminders with manual follow up and, if needed, external escalation, so that earned revenue is not lost to failed payments.
How is collections different from dunning? Dunning is the automated sequence of payment retries and reminders that runs when a charge fails. Collections is the wider process that includes dunning plus manual outreach, payment arrangements, write offs, and escalation. Dunning is the largest part of collections, not a separate thing.
What causes a payment to go into collections? Usually an automatic charge that is declined, commonly an expired or invalid card, insufficient funds, or a bank or fraud filter blocking a legitimate charge, or an invoiced account that passes its due date without paying.
How long should a collections process run before giving up? It depends on policy and account value, but the process typically runs a defined retry and reminder window before an invoice is written off, sent to an external agency, or allowed to lapse into cancellation. A specific recommended window is 27 days.
Can collections reduce churn? Yes. A large share of subscription cancellations are involuntary, caused by payment failures rather than a decision to leave, and recovering those payments directly prevents that churn.