Some of your customers are cancelling without ever clicking cancel. Their card expired, their bank declined the charge, their balance was short by four dollars on the day you billed them. They never made a decision to leave. Your billing system made it for them.

Dunning management is the process that catches those payments before they turn into lost customers. Done badly, it is three identical emails and a silent shutoff. Done well, it recovers a meaningful share of revenue you had already earned, from customers who still want your product.

This guide covers what dunning management actually involves, how to build a retry and communication sequence that works, what separates a hard decline from a soft one, and how to tell whether dunning software is worth the line item.

What Is Dunning Management?

Dunning management is the system a subscription business uses to detect failed payments, retry them intelligently, and communicate with the customer until the payment succeeds or the account closes.

The word itself is old. It comes from “dun”, meaning to persistently demand payment. In modern recurring billing it has a narrower meaning: everything that happens between a declined charge and its resolution.

A complete dunning process has four moving parts working together.

Detection. Your billing system flags the failure and captures the reason code the issuing bank returned.

Retry logic. The charge is attempted again on a schedule shaped by why it failed in the first place.

Customer communication. Email, in-app messages, SMS or a combination, telling the customer what happened and giving them a way to fix it.

Resolution. The payment succeeds, the customer updates their card, or the subscription is cancelled or downgraded according to rules you set in advance.

Miss any one of those and the other three underperform. Retries with no communication feel like a black box to the customer. Communication with no retries puts all the work on them. Neither recovers what it should.

Why Failed Payments Deserve Their Own Playbook

Most retention work is aimed at customers who are choosing to leave. Better onboarding, better support, better pricing, a smarter cancel flow. That work matters, and it addresses voluntary churn.

Failed payments are a different problem with a different solution. The customer is not unhappy. They have not evaluated alternatives. In many cases they do not even know the charge failed. This is involuntary churn, and treating it as a billing back-office task rather than a retention problem is why so much of it goes unrecovered.

Here is the practical difference. Winning back a customer who cancelled deliberately means changing their mind. Winning back a customer whose card expired means getting a new card number in front of your payment processor. The second one is far more tractable, and it is usually cheaper than any acquisition channel you run.

Hard Declines and Soft Declines Are Not the Same Problem

Retrying every failed charge on the same schedule is the most common mistake in dunning, and it comes from ignoring the decline reason.

Soft declines are temporary. Insufficient funds, a transaction limit, a bank system timeout, a suspected-fraud hold that clears on its own. The card is valid. The charge might succeed tomorrow with no action from anyone. These are worth retrying, and retrying is often all you need to do.

Hard declines are permanent. Card expired, card reported lost or stolen, account closed, transaction not permitted. Retrying a hard decline will fail again, forever, no matter how you time it. Some processors will penalise you for repeated attempts on a known-bad card. The only path forward is getting new payment details from the customer.

So the first branch in your dunning logic is not “how many times do we retry”. It is “what did the bank actually tell us”. Soft declines go into a retry schedule with light-touch messaging. Hard declines skip straight to asking the customer for a new card, because nothing else will work.

If your current setup retries everything four times over eight days and then gives up, you are wasting attempts on hard declines and being too impatient with soft ones.

Building a Retry Schedule That Works

There is no universal perfect schedule, and anyone who tells you there is has not looked at their own data. What holds up across most subscription businesses is a set of principles.

Spread attempts out rather than clustering them. Four retries in four days mostly tests the same bank balance four times. Spreading the same four attempts across two to three weeks gives payday cycles a chance to land in between.

Align at least one attempt with a payday. For consumer subscriptions this is one of the highest-yield adjustments available. The 1st and the 15th, and the last working day of the month, are worth targeting.

Cap the total attempts. Somewhere between four and six is typical. Past that, recovery rates fall off and you are mostly generating processor fees and annoying issuing banks.

Do not retry hard declines at all. Route them straight to a card-update request.

Track by cohort, not in aggregate. Recovery rate for insufficient-funds declines and recovery rate for expired-card declines behave completely differently. Averaging them hides which part of your process is broken.

A reasonable starting sequence for soft declines looks like day 0, day 3, day 7, day 14, with the day 14 attempt nudged to align with the nearest payday. Then measure and adjust. Your customer base, price point and billing day will move the optimum.

Writing Dunning Emails People Actually Act On

The dunning email is the part most teams get wrong, usually by making it sound like a collections notice.

Remember who is receiving it. This is an existing customer who likes your product enough to be paying for it. The tone should be closer to “heads up, something needs a quick fix” than “your account is delinquent”.

A few things separate dunning emails that recover revenue from ones that get ignored.

Say what happened in the subject line. “Your payment did not go through” beats “Action required regarding your account”. Vagueness reads as phishing, and phishing gets deleted.

Put the fix one click away. A link straight into a hosted card-update page, already authenticated where you safely can. Every extra step between the email and a working card number costs you recovery.

Tell them what they lose and when. Not as a threat. As information. “Your account stays active until 18 August” is genuinely useful and gives the message urgency without hostility.

Vary the sequence. Three sends of the same template is a filing system, not a sequence. Email one is a friendly heads up. Email two adds the deadline. Email three is short, direct, and mostly a button.

Send from a human address. Replies to a no-reply address are recovery opportunities you will never see.

Then there is the channel question. Email alone leaves recovery on the table, because the same inbox problems that bury your product updates bury your dunning emails. An in-app banner reaches customers who are still actively using the product, which is exactly the group most likely to fix the problem. SMS works for consumer subscriptions and mobile-first products, and is usually too aggressive for B2B.

Pre-Dunning: The Step Most Teams Skip

The cheapest failed payment is the one that never happens.

Pre-dunning means contacting the customer before the charge, when you can already see it is likely to fail. The main trigger is a card expiry date that falls before the next billing date. You know weeks in advance. A single email two weeks out asking them to update their card converts far better than any recovery email sent after the fact, because nothing has broken yet and there is no friction to overcome.

Other pre-dunning triggers worth wiring up include a card that failed on a previous cycle and was recovered manually, and an upcoming annual renewal at a materially higher amount than the customer last paid.

Teams that add pre-dunning usually find it removes a chunk of their dunning volume entirely. That is the goal. Recovery is a fallback, not a strategy.

Card Updater Services Do Some of the Work for You

Visa Account Updater and Mastercard Automatic Billing Updater are network-level services that push new card details to merchants when a card is reissued, replaced or renumbered. Most major payment processors expose them, sometimes automatically and sometimes as a setting you have to switch on.

Check whether yours is enabled. It is one of the highest-return five-minute tasks in subscription billing, because it silently prevents expired-card failures without the customer doing anything at all.

Coverage is not total. Not every issuing bank participates, and the services only cover certain card types. Treat them as a layer that reduces your dunning volume, not as a replacement for a dunning process.

Dunning Management Software: What to Look For

Every billing platform includes some dunning capability. Whether the built-in version is enough depends on your volume and how much of your revenue sits in failed charges.

If you evaluate dedicated dunning management software, these are the features that actually change outcomes.

Decline-code-aware retry logic, not a fixed schedule. If the tool cannot branch on hard versus soft declines, it is a scheduler, not a dunning system.

Multi-channel messaging. Email plus in-app at minimum.

A hosted card update page that works on mobile and does not require the customer to log in and hunt through billing settings.

Cohort-level reporting. Recovery rate broken down by decline reason, plan, tenure and billing amount. Aggregate numbers will not tell you what to change.

Testing support. The ability to run different sequences against different segments and compare, without engineering work each time.

Clean handoff to retention. What happens to a customer you could not recover matters as much as the recovery attempt itself.

A word on cost. Dunning tools usually price as a percentage of recovered revenue or a flat monthly fee. Percentage pricing looks fair and can get expensive quickly if a large share of your recovery would have happened anyway through simple retries. Ask for a baseline comparison before signing.

The Metrics That Tell You Whether It Is Working

Four numbers, tracked monthly.

Recovery rate. Failed charges eventually collected, as a percentage of all failed charges. This is the headline number.

Involuntary churn rate. Customers lost specifically to payment failure, as a percentage of total customers. Track it separately from your overall churn rate or it will hide inside the total.

Time to recovery. Days between first failure and successful collection. Shorter is better, and a rising number usually means your sequence has gone stale.

Recovery rate by decline reason. The diagnostic. If insufficient-funds recovery is healthy and expired-card recovery is poor, your problem is the card update flow, not your retry schedule.

Track these against your net revenue retention and the picture gets clearer still, because failed payments suppress NRR in a way that looks like customer dissatisfaction when it is nothing of the kind.

Common Dunning Mistakes

Cutting off access immediately. A customer locked out on day one has no reason to fix anything. Give them a grace period and say clearly when it ends.

Retrying hard declines. Covered above. It cannot work and it can hurt your processor relationship.

One email, three times. Sequences that do not escalate get ignored after the first send.

Burying the update link. If the customer has to log in, find billing settings and locate the right button, you have lost most of them.

Treating dunning as finance’s problem. Failed payments are a retention issue with a billing trigger. When finance owns it alone, the messaging reads like debt collection and nobody measures the churn impact.

Never revisiting the sequence. Payment behaviour shifts. A schedule that worked two years ago is not automatically working now.

Where Dunning Ends and Retention Begins

Not every failed payment is recoverable. When you have exhausted retries and the customer has not updated their card, you have a decision to make, and defaulting to instant cancellation throws away the option value in that account.

Better endings exist. A pause instead of a cancellation keeps the relationship alive for customers whose problem is temporary cash flow, and subscription pauses tend to convert back at rates that make them worth offering. A downgrade to a cheaper plan keeps some revenue and all of the relationship. A targeted retention offer at the point of failure catches customers who were quietly reconsidering the cost anyway.

That handoff is where dunning stops being a billing function and becomes part of your retention flow. Churnfree sits at that point, giving customers who are about to lapse a real alternative to leaving, whether they arrived there by clicking cancel or by a card that stopped working.

FAQs

What Is Dunning Management in Simple Terms?

It is how a subscription business handles payments that fail. The system detects the failure, retries the charge on a schedule, emails the customer with a way to fix it, and follows a set of rules if the payment never succeeds.

What Is a Dunning Email?

A dunning email tells a customer that a payment failed and asks them to resolve it. Effective ones state the problem plainly in the subject line, link directly to a card update page, and say when access will be affected.

How Many Times Should You Retry a Failed Payment?

Four to six attempts over two to three weeks is a common range for soft declines, with at least one attempt timed near a payday. Hard declines such as an expired or closed card should not be retried at all, because they will fail every time.

When Is the Best Time to Send a Dunning Email?

Send the first one immediately after the failure, while the context is fresh. Space later sends to match your retry attempts rather than sending on a fixed daily cadence, so the customer is never told a payment failed on a day you did not actually attempt one.

What Is the Difference Between Dunning and Involuntary Churn?

Involuntary churn is the outcome, meaning customers lost because a payment failed. Dunning is the process you run to prevent that outcome. Good dunning management is the main lever you have on involuntary churn.

Do You Need Dedicated Dunning Management Software?

Not always. If your billing platform supports decline-code-aware retries, multi-channel messaging and a decent hosted card update page, that may be enough. Dedicated tools earn their cost when failed payments are a material share of revenue and you want cohort-level reporting and sequence testing without engineering time.

What Is Pre-Dunning?

Contacting a customer before a charge you expect to fail, most often because their card expires before the next billing date. It prevents the failure instead of recovering from it, and it converts better than any post-failure email.