AutomationIntermediate8 min read

Dunning Automation

Dunning Automation is the system that detects failed subscription payments and recovers them through a sequence of intelligent retries, customer communications, and payment-method updates — without manual intervention. Failed payments cause 20-40% of all SaaS churn ('involuntary churn') and are almost entirely recoverable: 65-75% of failed charges can be collected within 30 days using adaptive retry timing, branded recovery emails, and one-click card-update flows. KnowMBA POV: dunning is the most underestimated revenue lever in SaaS. A $20M ARR company with 2% monthly involuntary churn and naive dunning is losing ~$1M/year of recoverable revenue — and most CFOs cannot tell you the involuntary churn number off the top of their head.

Also known asFailed Payment RecoverySmart DunningPayment Retry AutomationInvoluntary Churn RecoveryCard Decline Recovery

Challenge a friend Browse library

The Trap

The trap is treating dunning as 'send the customer an email when their card declines.' Naive daily retry recovers 40-50% of failures. Smart dunning (Stripe Smart Retries, Recurly's machine learning, Maxio's recovery engine) recovers 65-80% by retrying at issuer-specific optimal times, swapping payment networks, using account updater services to refresh expired cards automatically, and triggering branded customer flows rather than generic 'your payment failed' notices. The second trap is over-aggressive dunning: 7 emails in 14 days creates unsubscribes and brand damage. The third trap is firing the customer too fast — the typical SaaS cancels accounts after 3-4 failed retries, but most card failures are temporary (insufficient funds, expired card) and 30-day patience recovers significantly more revenue than 14-day patience.

What to Do

Step 1: measure involuntary churn separately from voluntary churn — most SaaS finance teams don't, and that's the root cause of dunning being underinvested. Step 2: deploy a billing platform with smart dunning built in (Stripe Billing, Recurly, Chargebee, Maxio) — never build dunning logic in-house. Step 3: enable card account updater (Visa Account Updater, Mastercard Automatic Billing Updater) to refresh expired cards automatically — this alone recovers 8-15% of failed charges. Step 4: design a 14-30 day dunning sequence with adaptive retry timing, branded HTML emails, in-app notifications, and one-click card-update links. Step 5: set hard cutoff at 21-30 days (not 7-14) — patience pays in this category. Track Failed Payment Recovery Rate monthly and benchmark against industry: anything under 65% is a fix opportunity.

Formula

Failed Payment Recovery Rate = Successfully Collected Failed Charges / Total Failed Charges × 100

In Practice

Stripe published research on Smart Retries showing that Stripe Billing customers who enabled the adaptive retry feature recovered an average of 12-15% MORE failed payments than customers using naive scheduled retries. On a $25M ARR business with 1.5% monthly involuntary churn, that delta is $45-55K/month or $540-660K/year of recovered revenue with zero additional headcount. Recurly's customer benchmarks show similar magnitudes: their Decline Salvage product recovers 78% of failed transactions on average for customers who fully implement the workflow (vs 50-55% baseline for customers using basic dunning). The industry pattern is consistent: dunning sophistication is worth tens of basis points of churn reduction, which compounds into 7-figure ARR retention for mid-market SaaS.

Pro Tips

01
Card account updater services (Visa Account Updater, Mastercard ABU) are the lowest-effort, highest-ROI dunning move. They refresh expired card numbers automatically when issuers reissue cards, recovering 8-15% of charges that would have failed for 'expired card' reason. Most billing platforms (Stripe, Recurly, Chargebee) support this with a one-toggle setting. Turn it on if you haven't.
02
Retry timing matters more than retry count. Stripe's data shows that retrying at the same time of day is far less effective than retrying at issuer-specific optimal times — typically 2-4 days after the failure for insufficient-funds errors (after payday) and immediately for soft-decline errors. Naive retry every 24 hours leaves ~30% of recoverable revenue on the table.
03
Best-in-class dunning sequences combine 4-6 emails over 21-28 days, in-app notifications, and SMS for high-value accounts. The single most-effective email is the 'one-click update your card' email — make sure the link goes directly to a hosted payment page where they can update the card in 15 seconds. Long forms kill recovery rates.

Myth vs Reality

Myth

“Failed payments are mostly fraud or bad customers — those churns aren't recoverable”

Reality

Empirical data from Stripe, Recurly, and Chargebee consistently shows the opposite. The dominant failure reasons are insufficient funds (recovered by waiting until payday), expired cards (recovered by account updater services), and issuer-side soft declines (recovered by retry within 24 hours). Genuine fraud or chargeback is <10% of failures. The vast majority of failed charges represent willing customers with temporary payment issues — they will pay if your dunning sequence works.

Myth

“Dunning is a finance function — engineering shouldn't prioritize it”

Reality

Dunning is a revenue retention function and should be owned by whoever owns net retention. The work is mostly configuration (not engineering) once a billing platform is in place, but the strategic ownership belongs with growth/RevOps. Treating dunning as a finance back-office task is why most companies have a recovery rate stuck at 50% when 75% is achievable with the same tools.

Try it

Run the numbers.

Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.

🧪

Knowledge Check

A $30M ARR SaaS has 1.8% monthly involuntary churn (failed payments not recovered). Their current Failed Payment Recovery Rate is 52%. What is the realistic ARR upside from upgrading to smart dunning + account updater?

Industry benchmarks

Is your number good?

Calibrate against real-world tiers. Use these ranges as targets — not absolutes.

Failed Payment Recovery Rate

% of failed subscription charges eventually collected within 30 days

Best in Class (smart dunning + ABU)

75-85%

Mature

65-75%

Average

50-65%

Naive / No Dunning

< 50%

Source: Stripe Smart Retries Benchmarks / Recurly Decline Salvage Report

Involuntary Churn Rate (monthly)

% of monthly ARR lost to failed payments not recovered (B2B SaaS)

Best in Class

< 0.7%

Good

0.7-1.2%

Average

1.2-2%

Critical

> 2%

Source: Recurly Subscription Industry Benchmarks 2024

Real-world cases

Companies that lived this.

Verified narratives with the numbers that prove (or break) the concept.

🔁

Stripe Smart Retries (Customer Pattern)

2018-present

success

Stripe's Smart Retries product uses machine learning to determine optimal retry timing on a per-issuer, per-card basis. Customer outcomes consistently show 12-15 percentage point lift in Failed Payment Recovery Rate compared to fixed-schedule retry. The mechanism: rather than retrying at 24/48/72 hours uniformly, Smart Retries waits until the customer's specific issuer is most likely to authorize (e.g., 2 days after a known payday cycle for an insufficient-funds decline). On a $25M ARR business with 1.5% monthly involuntary churn, the lift typically retains $500-700K of annual ARR.

Recovery Rate Lift

+12-15 percentage points

Mechanism

ML-driven per-issuer optimal retry timing

Typical ARR Retention (mid-market)

$500K-$1M/year

Configuration Effort

Minimal (one-toggle for Stripe Billing)

Adaptive retry timing is one of the highest-ROI features available to subscription businesses. The cost is zero (included in billing platform) and the upside is hundreds of basis points of net retention.

Source ↗

📉

Recurly Decline Salvage

2019-present

success

Recurly's Decline Salvage product combines smart retry, account updater services, and machine-learning-driven dunning sequence optimization. Recurly publishes that customers who fully implement Decline Salvage achieve 78% Failed Payment Recovery Rate on average, vs 50-55% for customers using basic dunning. Across their customer base, this has translated to billions of dollars of recovered ARR. The pattern matches Stripe's: dunning sophistication is the difference between losing 2% monthly to involuntary churn and losing 0.7%.

Recovery Rate (full implementation)

78% average

Recovery Rate (basic dunning baseline)

50-55%

Cumulative ARR Recovered

Billions across customer base

Components

Smart retry + ABU + ML-optimized sequences

The full dunning stack (retry + account updater + sequence optimization) compounds — no single move delivers the full lift, but together they shift recovery from 50% to 75%+.

Source ↗

Decision scenario

The Dunning Investment Decision

You're CFO of a $25M ARR vertical SaaS. Involuntary churn is 1.9% monthly. Failed Payment Recovery Rate is 48%. Three paths forward: (1) Status quo — 'dunning is fine', (2) Configure smart dunning + account updater on existing Stripe Billing, (3) Hire a collections analyst to manually work the dunning queue.

ARR

$25M

Monthly Involuntary Churn

1.9%

Recovery Rate

48%

Annual Failed-Payment Volume

~$11M

Annual ARR Lost to Involuntary Churn

~$5.7M (cumulative)

Decision 1

The math says dunning is one of the largest revenue leaks in the business. The execution question is whether to fix it with technology, headcount, or both.

Status quo — dunning is finance plumbing, focus on new logoReveal

12 months later, involuntary churn is still 1.9% and recovery rate is still 48%. Cumulative ARR lost: ~$5.7M. The CRO's heroic new-logo year is partially eaten by dunning leakage. Board asks a pointed question about gross retention. The status quo decision is the most expensive decision available — it just doesn't show up on a P&L line.

ARR Retention: −$5.7M (cumulative loss)Net Retention Rate: Drag of ~3-4 points/year

Configure smart dunning + account updater on Stripe Billing — 3 sprint cycles of workReveal

Live in 6 weeks. Recovery rate climbs from 48% to 73% within 90 days. Annual ARR retained: ~$2.7M. Net retention rate improves by ~2 points. Configuration cost: ~$25K of internal time. ROI: 100x+. This becomes the highest-ROI move RevOps shipped this year.

Recovery Rate: 48% → 73%Annual ARR Retained: +$2.7MConfiguration Cost: −$25KNet Retention Rate: +2 percentage points

Hire a collections analyst at $90K to manually work the dunning queueReveal

Analyst onboards in 60 days. Manually contacts failed-payment customers. Recovers an incremental 5-7 points of recovery rate (so 48% → 54%). Annual ARR retained: ~$650K. Net of $90K + benefits, true ROI is ~6x. Better than status quo, but a fraction of what platform configuration delivers — and now you're hiring against a problem that should have been solved with a checkbox.

Recovery Rate: 48% → 54%Annual ARR Retained: +$650KAnnual Headcount Cost: −$110K (loaded)

Related concepts