Dunning is the process of contacting customers, on a set schedule, to collect payments they owe. It covers two situations. One is an invoice that has passed its due date without payment. The other is an automatic recurring charge, such as a subscription or payment plan instalment, that has failed. In both, the business sends a planned sequence of reminders that gets firmer over time until the customer pays.
Dunning is the methodical communication a business uses to collect overdue or failed payments: a predefined series of reminders and retries, each triggered by time passing or by a payment event. A dunning process is the written version of that series, setting out each message and its timing, and what happens when the customer responds.
The word is old and sounds harsher than the practice. Most dunning messages are polite reminders, and most of the ones that work are short and specific. What distinguishes dunning from ordinary follow-up is that it is planned in advance and applied to every account the same way.
Two kinds of dunning
Invoice dunning and failed-payment dunning share a name and a goal, but they start from different places and need different tools.
| Invoice dunning | Failed-payment dunning | |
|---|---|---|
| What triggers it | An invoice passes its due date unpaid | An automatic card or bank charge is declined or returned |
| Typical customer | B2B accounts on payment terms | Subscribers, members, customers on payment plans |
| Usual cause | Approval delays, cash timing, disputes, forgetting | Expired or replaced cards, insufficient funds, closed accounts |
| What the customer must do | Pay the invoice | Often nothing; or update their payment details |
| Timescale | Weeks to months | Days |
| Main tool | Reminder emails, calls, statements | Automatic retries plus an update-your-card link |
The difference in cause is the important part. A customer whose card expired usually still wants the service and has no idea a payment failed. A customer ignoring a 40-day-old invoice knows exactly what's going on. Writing the same message to both gets one of them wrong.
The dunning process for unpaid invoices
Invoice dunning runs on the calendar, counted from the due date. A typical process for net 30 accounts moves through four stages:
- Courtesy: a reminder before the due date and another on the day, each with a payment link.
- Early overdue: reminders a few days and about a week after the due date, assuming an oversight.
- Firm: from two to four weeks overdue, messages that ask for a payment date, followed by a phone call, with the customer's accounts payable team included.
- Final: from around 45 to 60 days, escalation to a decision-maker, a payment plan offer, then a final notice naming the next step.
The early stages can be fully automated. The later ones need a person, because by then the reason for non-payment is usually specific and needs an answer. For the wording at each stage, see our payment reminder email templates for the early messages and the past due invoice emails for the later ones.
Dunning for failed recurring payments
When an automatic charge fails, the clock runs much faster. The customer is usually still active and the fix is usually simple, but each day the payment stays failed is a day closer to the customer losing access, or simply drifting away.
Why recurring payments fail
- The card has expired, or the bank has replaced it after loss or fraud.
- The card or bank account has insufficient funds on the day of the charge.
- The card issuer declined the charge, sometimes because its fraud checks flagged it.
- The bank account was closed, or the customer revoked the authorization.
Only the last of these reflects a decision by the customer to stop paying. The rest are what subscription businesses call involuntary churn: customers lost through payment failure rather than choice.
A recovery sequence
- Day 0: the charge fails. Send the customer a short notice with a secure link to update their payment details. Keep the service running.
- Day 2 or 3: retry the charge automatically, if the decline reason suggests a retry could succeed (insufficient funds can resolve once a paycheck lands; a closed account won't).
- Day 5 to 7: if the retry fails, send a second notice, with the link again and the date service will be paused.
- Day 10 to 14: a final retry and a final notice.
- Afterwards: pause or cancel the service as your terms say, and send a confirmation that tells the customer how to restart.
Ask your processor which decline reasons are worth retrying and how many retries its rules allow. Retrying a card that has been reported stolen achieves nothing except another decline.
Bank account (ACH) payments have their own rules
When a recurring payment is collected by ACH debit and the bank sends it back, the return arrives with a reason code, and Nacha's rules govern what you can do next. Nacha calls resubmitting a returned debit "reinitiation." Its published rules require a reinitiated entry to carry the description "RETRY PYMT," and they treat reinitiating any entry returned as unauthorized as an improper practice. In practice, that separates a debit returned for insufficient funds, which your processor may be able to retry within Nacha's rules, from one the customer reported as unauthorized, which needs a fresh authorization from the customer before you collect again. Our guide to ACH return codes explains the common codes and what each one calls for, and your processor can confirm how its retry settings apply Nacha's reinitiation rules.
What good dunning is worth
Recovery rates differ from one business to the next, so run the numbers on your own. Take a hypothetical software company with 600 customers on a $45 monthly plan, and suppose 4% of charges fail in a given month.
- Failed charges: 600 × 4% = 24 a month, worth 24 × $45 = $1,080.
- If a single retry and one email recover 35% of them: $1,080 × 35% = $378 recovered.
- If a full sequence with an update-your-card link recovers 70%: $1,080 × 70% = $756 recovered.
The difference is $378 a month, or $4,536 a year ($378 × 12), and it compounds, because every recovered customer is billed again the following month. On the invoice side the arithmetic is different but the principle holds: a consistent process collects money that ad hoc chasing misses.
How to design a dunning cadence
Anchor every step to an event
Each message should be triggered by something specific, such as a due date, a failed charge, or the number of days since either. "Send reminders sometimes" is not a process. "Email on day 3 after a failed charge, with the update link" is.
Change the channel and the sender as you escalate
Early messages can be automatic emails from your billing address. Later ones should come from a named person, then by phone or text, then from someone more senior. A change of sender signals a change of seriousness better than capital letters do.
Write stop rules
Every dunning process needs rules for when to stop. Stop the moment the account is paid, which requires your payment records and your reminders to be connected. Pause when the customer disputes the charge or agrees a plan, and route the account to a person. Nothing damages a relationship faster than an automated final notice to a customer who paid yesterday.
Segment by value
A $45 subscriber and a customer with $60,000 of open invoices shouldn't get the same treatment. Large accounts warrant a personal call early; small recurring accounts can run on automation almost end to end.
Measure it
Track three numbers each month: the share of failed or overdue payments eventually recovered, the average days to recover them, and the amount written off. If the first number falls or the second rises, look at which step in the sequence stopped working.
For recurring billing, automatic charging is the starting point. Recurring payments of the kind we set up charge customers automatically on the schedule you set, for subscriptions or payment plans, and our guide to recurring billing covers how to set those plans up so fewer payments fail in the first place.
Frequently asked questions
Is dunning the same as debt collection?
No. Dunning is the business's own process for collecting from its own customers, usually while the relationship is still active. Debt collection, in the sense of a collection agency or legal action, typically starts after dunning has failed. Outside collection comes with its own rules and costs; our guide to collecting unpaid invoices covers when to consider it.
What is a dunning letter?
A dunning letter is any message in the sequence, by email or post, that asks a customer to pay an overdue or failed payment. The term often refers to the formal later stages, where the letter states the amount, the history of reminders and a deadline. Early dunning letters are usually just short, polite emails with a payment link.
Does dunning annoy customers?
Badly designed dunning does, especially when it gets the amount wrong or keeps reminding a customer who has already paid. A well-designed sequence mostly helps customers, especially on failed card payments, because it tells them about a problem they didn't know they had and gives them a quick way to fix it before their service is interrupted.
Sources
- Nacha: ACH Network Risk and Enforcement Topics (reinitiation of returned entries), accessed 15 November 2026