Dunning

Billing Payments

5 min read

Also known as: Payment Recovery, Failed Payment Recovery, Involuntary Churn Recovery

Dunning is the structured process of recovering failed or overdue payments through automated reminders, retries, and escalation steps.

Definition

Dunning is the systematic process your billing system uses to recover revenue when a customer's payment fails or an invoice goes unpaid. It combines automated card retries, email and SMS reminders, and escalation rules that move an account from gentle nudge to service suspension over a defined timeline.

In practice, dunning runs in the background of any subscription or recurring-billing operation. When a card declines on renewal, the system retries on a smart schedule, notifies the customer, updates the dunning state, and either recovers the charge or escalates to your finance team for manual follow-up.

Dunning is sometimes confused with collections, but they sit at different stages. Dunning is the in-product, pre-collections recovery layer that happens while the customer is still active; collections is what happens after dunning fails and the account is written off or handed to a third party.

Why It Matters

Failed payments are the single largest source of involuntary churn in subscription businesses, often accounting for 20-40% of total churn. A tuned dunning sequence recovers a meaningful share of that revenue without your team touching a single account, which directly improves net revenue retention and LTV.

When dunning is ignored or left on default settings, you bleed revenue twice: once on the failed charge, and again when the customer cancels because they got a clumsy or aggressive reminder. Teams that treat dunning as an afterthought also tend to suspend paying customers by accident, generating support tickets and refund requests that cost more than the recovered invoice.

Examples in Practice

A SaaS company billing 4,000 customers monthly sees a 6% card failure rate at renewal. With a four-step dunning sequence (smart retries on days 1, 3, 5, and 7 plus branded reminder emails), they recover roughly 65% of failed charges without involving support.

A 30-person agency running retainer billing uses dunning to handle ACH returns. When a bank reversal hits, the system pauses the invoice, emails the client's AP contact, and notifies the account lead in Slack on day 3 if still unpaid, preventing awkward 30-day-late surprises.

An e-commerce subscription box uses dunning to coordinate with shipping. If the renewal charge fails, the system holds the next shipment, runs three retries over ten days, and only cancels the subscription if all attempts fail, protecting against shipping a box that was never paid for.

Frequently Asked Questions

What is dunning and why does it matter?

Dunning is the automated process of recovering failed or overdue payments through retries, reminders, and escalation. It matters because failed payments are the largest source of involuntary churn in subscription businesses, and a well-tuned dunning flow can recover the majority of that lost revenue without manual intervention from your finance or support teams.

How is dunning different from collections?

Dunning happens inside your billing system while the customer is still active, using retries and reminders to recover a recent failed charge. Collections happens after dunning has failed, when the debt is past due by 60-90+ days and often handed to an external agency. Dunning is automated and customer-friendly; collections is manual, legal, and adversarial.

When should I use dunning?

Any business with recurring revenue, stored payment methods, or net-terms invoicing should run dunning. The moment you have more than a handful of subscriptions or repeat invoices, manual follow-up on failed payments stops scaling. Dunning becomes mandatory once involuntary churn starts showing up as a measurable line item in your retention reports.

What metrics measure dunning?

Track recovery rate (percentage of failed charges eventually collected), involuntary churn rate, average days to recovery, and the cancellation rate of customers who entered dunning. Also watch retry success by attempt number to tune your retry schedule, and segment recovery by failure reason code so you know which declines are recoverable versus permanently dead cards.

What's the typical cost of dunning?

Dunning is usually bundled into your billing platform rather than priced separately. Costs come from transaction fees on retried charges (typically 2.9% + $0.30 per successful retry on cards) and any SMS or email volume. The economics almost always favor running it: recovering a $99 subscription pays for thousands of reminder emails.

What tools handle dunning?

Dunning is typically built into subscription billing platforms, recurring invoice systems, and payment gateways. Categories include subscription management engines, accounts-receivable automation tools, and standalone dunning specialists that bolt onto an existing billing stack. Some payment processors offer basic retry logic, but full dunning with messaging and escalation usually requires a dedicated billing layer.

How do I implement dunning for a small team?

Start with the defaults in your billing platform, then customize three things: the retry schedule (smart retries beat fixed daily attempts), the email copy (branded, helpful, not threatening), and the final escalation rule (when to suspend service). Review recovery data after 60 days and tighten the sequence. Avoid building this from scratch unless your billing logic is genuinely unusual.

What's the biggest mistake teams make with dunning?

Treating it as a set-and-forget feature. Default dunning sequences are written by software vendors who don't know your customer base, so they often retry too aggressively, send tone-deaf emails, or suspend paying customers over a temporary bank glitch. The second-biggest mistake is not measuring recovery rate, which means teams never know how much revenue is leaking.

Does dunning work for B2B invoicing or only subscriptions?

It works for both, but the cadence differs. B2B net-terms invoicing uses a slower dunning sequence (reminders at day 7, 14, 30, 45 past due) with escalation to an account manager rather than automated suspension. Subscription dunning is faster and more automated because the failure is usually a card decline, not a procurement delay.

Can dunning hurt customer experience?

Yes, if poorly configured. Overly frequent emails, threatening language, or suspending a long-term customer over a single failed charge will damage relationships and trigger cancellations. Good dunning is quiet, helpful, and gives the customer easy paths to update their payment method. The goal is recovery without the customer feeling like they've been sent to collections.

The AMW Suite