Resources

How Long Should Dunning Run? Finding the Window

How long should dunning run? Too short, and you cancel subscribers whose only problem was a payday that had not arrived yet. Too long, and you spend weeks emailing people who decided to leave the moment their card failed, annoying them, irritating issuers with stale retries, and delaying the clean cancellation or winback conversation that should follow. The right window is not a magic number. It is a balance between the shape of recovery over time — heavily front-loaded, with a long thin tail — and the real costs of keeping a failed account open. This piece works through that trade-off, why the tail flattens, and why monthly and annual plans deserve materially different windows. To design the day-by-day schedule inside whatever window you choose, use the dunning cadence planner alongside this piece.

What the window has to cover

A dunning window has three jobs that pull in different directions. First, it must span at least one full pay cycle for the largest failure category. Insufficient funds is the largest decline category at 40.6% across 5.4M failed payments, according to Churnkey's published analysis of Stripe data — and an insufficient-funds failure is fundamentally a calendar problem. A window shorter than a typical pay interval writes off the single biggest recoverable group before their account is funded again. Second, the window must allow a spaced retry schedule rather than a burst. Retries fired in the first few days, hours apart, hit the same empty account and the same issuer flags repeatedly. Third, the window must give outreach time to work: subscribers open email late, route card updates through a finance contact, or need a weekend to deal with it. Compress the window and all three mechanisms degrade at once. That is the argument against the three-to-five-day sequences many billing defaults ship with — they are built for administrative tidiness, not for how failures actually resolve.

Why the tail flattens

Recovery within a window is not evenly spread. The first retry and the first clear notice recover the easy share: transient declines, funded accounts, prompt updaters. Each subsequent attempt and touch recovers less than the one before, because the remaining pool is increasingly composed of harder cases — subscribers who have disengaged, cards that were replaced without the subscriber bothering to update yours, and quiet quitters using the failure as an exit they did not want to initiate. The marginal touch still earns something for a while: according to Churnkey's published analysis of Stripe data, each additional dunning email touch adds roughly 1–2 points of recovery, which is a real return on a near-free channel. But that return is measured across a healthy sequence, not indefinitely. By the late tail, you are spending deliverability, goodwill, and support attention to recover a trickle, while the account sits in a limbo that is bad for your numbers and worse for the subscriber relationship. Diminishing returns are not an argument for a short window. They are an argument for knowing where your flattening point is and ending with intention — a final notice and a clean state — instead of letting the sequence peter out or grind on by default.

The costs of running long

• Issuer and network patience. Retrying stale failures long after the window of plausibility — especially failures that have hardened — works against you at the processor level. Smart windows stop retrying what cannot succeed. Hard declines should exit the retry track immediately, whatever your window is.
• Subscriber experience. Every week of notices after a subscriber has mentally left converts an amicable lapse into an irritating memory. That memory decides whether a winback email in three months gets opened or deleted, and whether the person recommends you in the meantime.
• Operational drag. Past-due accounts consume support time, muddy your active subscriber count, and delay the moment your team can read true churn. Long windows hide problems that a clean end state would make visible.
• Access given away. If access continues during dunning — a policy choice this site covers in its grace period guidance — a long window is also a long stretch of unpaid service, which changes the economics entirely for high-cost products.

Monthly versus annual plans

The window should scale with what is at stake and how the subscriber experiences time in your product. For a monthly plan, a window in the range of two to three weeks covers a full pay cycle, allows a properly spaced retry schedule, and still ends well inside the next billing period, so the subscriber is never two failures deep. Stretch much beyond that and the unpaid window approaches the value of a whole month of service. For an annual plan, the math flips. The amount at stake is twelve times larger, the subscriber relationship is typically deeper, and the failure often involves a replaced card on a charge the subscriber was not expecting this month. A longer, more patient window — with more spaced touches, a genuine final notice, and room for a human conversation on high-value accounts — pays for itself, because recovering one annual renewal funds a great deal of dunning. Annual subscribers also renew against a charge they may not remember authorizing in size, so early touches should carry the context: what the plan is, when it started, what continued access includes. The retry timing piece, when to retry failed payments, goes deeper on spacing attempts inside either window.

Setting your window with your own data

Published benchmarks set the shape; your own recovery curve sets the number. Pull the last few months of failed payments and plot recoveries by day since failure. Most operators see the same pattern: a strong first week, a meaningful second week carried by the pay cycle and the final notice, and then a cliff. Your window belongs a little past the point where daily recoveries flatten, with your final notice placed where it can still trigger the last genuine cluster of action rather than after it. Then check the window against segment reality: low price points behave differently — Churnkey's published analysis notes low price points under $10 per month show the highest involuntary share at roughly 35% — and high-volume, low-price products often justify a tighter, more automated window, while low-volume, high-price products justify a longer one with a human in it. Re-run the curve quarterly. Failure mixes shift with your pricing, your acquisition channels, and the economy your subscribers live in. The measurement discipline for this is covered in measuring dunning performance, and the recovery calculator helps you price the difference between candidate windows before you commit to one.

Where a modern recovery sequence sits

As a reference point for the shape — not a prescription — Swipe Again runs decline-code-aware smart retries with up to 6 attempts over roughly 16 days, with hard declines never retried, alongside branded dunning emails, SMS in the sequence, and card-update pages. That sits deliberately in the monthly-plan sweet spot: long enough to span a pay cycle and space attempts properly, short enough to end with a clear final state inside the billing period. It is $179/mo flat ($1,799/yr) with no percentage of recovered revenue and no MRR tiers, across nine platforms: Stripe, Recharge, Seal Subscriptions, Skio, Loop Subscriptions, Chargebee, Recurly, Braintree, and Paddle. Whatever tooling you use, judge a proposed window against the same tests: does it cover a pay cycle, does it space retries instead of bursting them, does it end with a real final notice, and does it stop the moment recovery makes the rest unnecessary?

The bottom line

Dunning should run long enough for time to do its work — one pay cycle, spaced retries, outreach that late openers can still act on — and not one week longer than your own recovery curve justifies. Monthly plans usually land near two to three weeks. Annual plans earn a longer, more deliberate window. Measure where your tail flattens, put the final notice at the flattening point rather than after it, and let the account close cleanly when the window ends. A dunning window is a promise with a date on it. Keep the date honest.

Frequently asked questions

How long should a dunning cycle last for a monthly subscription?

For most monthly plans, roughly two to three weeks works well. That span covers a full pay cycle for insufficient funds failures, allows retries to be spaced sensibly instead of burst in the first days, and ends inside the next billing period so a subscriber never falls two payments behind during recovery.

Why do annual plans need a longer dunning window?

The amount at stake is much larger, the subscriber relationship is usually deeper, and the failure often involves a card replaced since the charge a year ago. A longer window with spaced touches and room for a personal conversation pays for itself when a single recovered renewal is worth twelve monthly payments.

When does extending dunning stop paying off?

When your own recovery curve flattens. Recoveries concentrate in the first one to two weeks, carried by early retries, the pay cycle, and the final notice. Past the flattening point, extra touches recover very little while costing goodwill, deliverability, and support time. Plot recoveries by day since failure to find your point.

Should retries continue for the whole dunning window?

Retries should be spaced across the window for soft declines, but they are not the same as the window itself. Hard declines should never be retried at any point, and any failure that converts to a hard decline should leave the retry track immediately and move to a card update request instead.

How often should I revisit my dunning window?

Quarterly is a sensible cadence. Your failure mix shifts with pricing changes, new acquisition channels, and your subscribers economic conditions, and each shift moves the point where the recovery tail flattens. Re-plot recoveries by day since failure and adjust the window and final notice placement to match.