The Complete Guide to Dunning Management for SaaS

What Is Dunning?

Dunning is the process of communicating with customers to collect overdue payments. In SaaS, it specifically refers to the automated system that handles failed subscription payments — retrying charges, notifying customers, and preventing involuntary churn.

The term comes from the 17th-century English word "dun," meaning to make persistent demands for payment. Modern dunning is less about demanding and more about helping: most failed payments happen because of expired cards, insufficient funds, or bank-side issues — not because customers don't want to pay.

Why Dunning Matters for SaaS

Failed payments are the silent killer of SaaS revenue. The numbers are stark:

• 9% of MRR is at risk from failed payments at any given time
• 20-40% of all SaaS churn is involuntary — caused by payment failures, not unhappy customers
• $129 billion is lost to failed payments in subscription businesses annually
• Optimized dunning recovers 70-85% of failed payments vs. ~50% with basic retry logic

For a SaaS company with $100K MRR, that means $9,000/month is at risk. The difference between recovering 50% and 80% of that is $2,700/month — or $32,400/year.

Dunning is one of the highest-ROI activities in SaaS operations. Unlike customer acquisition (which costs money) or product improvements (which take time), dunning recovers revenue from customers who already want to pay.

How Payment Failures Happen

Understanding why payments fail is the first step to recovering them. Payment failures generally fall into two categories:

Soft Declines (70-80% of failures)

Soft declines are temporary. The card is valid, but the transaction was declined for a transient reason:

• Insufficient funds — the most common reason. The customer's account balance is too low.
• Card issuer unavailable — the bank's system is temporarily down.
• Processing error — a network issue between Stripe and the bank.
• Velocity limit — too many transactions in a short period.

Soft declines are highly recoverable. Retrying at the right time often succeeds.

Hard Declines (20-30% of failures)

Hard declines are permanent (for that card). The transaction will never succeed without customer action:

• Expired card — the card has passed its expiration date.
• Lost or stolen card — the bank has blocked the card.
• Invalid card number — the card number on file is wrong.
• Card not supported — the card type isn't accepted.

Hard declines require the customer to update their payment method. No amount of retrying will work.

The Decline Code Matters

Stripe provides specific decline codes that tell you exactly why a payment failed. Your dunning strategy should treat different codes differently:

| Decline Code | Type | Best Response | |---|---|---| | insufficient_funds | Soft | Retry in 2-3 days | | card_declined (generic) | Soft | Retry in 1-2 days | | expired_card | Hard | Email customer immediately | | incorrect_cvc | Hard | Email to re-enter card | | processing_error | Soft | Retry within hours | | do_not_honor | Soft/Hard | Retry once, then email |

The Anatomy of a Dunning System

A complete dunning system has five layers:

1. Pre-Dunning (Prevention)

The best dunning is preventing failures in the first place:

• Card expiration alerts — email customers 30 days before their card expires
• Account updater — automatically update card numbers when banks reissue cards (reduces failures by 25-35%)
• Payment method diversification — offer multiple payment methods (cards, ACH, bank transfer)

2. Automatic Retries

When a payment fails, the system retries the charge on an optimized schedule:

• Day 1: Immediate retry (catches processing errors)
• Day 3: Second retry (gives time for insufficient funds to clear)
• Day 5: Third retry
• Day 7: Fourth retry
• Day 14: Final retry

The optimal retry schedule depends on your customer base, but most SaaS companies see the best results with 4-6 retries over 14-21 days.

3. Customer Communication

This is where most companies fail. Your email sequence should:

• Inform the customer about the failure (Day 1)
• Remind them to update their card (Day 3-4)
• Motivate them with value reminders (Day 7)
• Create urgency with a deadline (Day 10-14)
• Offer alternatives like discounts or plan changes (Day 12)
• Send a final notice before cancellation (Day 14)

See our dunning email templates for copy-paste examples of each.

4. Save Offers

Before canceling a subscription, offer alternatives:

• Discount — 10-25% off the next 1-3 months
• Pause — freeze the subscription for 30-60 days
• Downgrade — move to a cheaper plan

Save offers can retain 15-30% of customers who would otherwise churn. The key is timing — offer them after initial retries fail but before cancellation.

5. Win-Back

After a subscription is canceled due to payment failure, send a reactivation campaign:

• Day 3 post-cancellation: "Your data is safe, come back anytime"
• Day 7: Offer a reactivation discount
• Day 30: Final reminder before data deletion

Win-back campaigns recover 5-15% of canceled subscriptions.

Building vs. Buying Dunning Software

Building In-House

You can build a dunning system using Stripe webhooks and your email provider. Here's what's involved:

Pros:

• Full control over the experience
• No additional monthly cost
• Deep integration with your product

Cons:

• Significant engineering time (2-4 weeks minimum)
• Ongoing maintenance burden
• No built-in analytics or benchmarks
• Easy to get wrong (timing, decline code handling, edge cases)
• No A/B testing infrastructure

Using Dedicated Software

Dunning-specific tools handle everything out of the box:

Pros:

• Set up in 5-30 minutes
• Battle-tested email sequences and retry logic
• Analytics and recovery rate tracking
• Save offers and win-back automation
• Continuous optimization

Cons:

• Monthly cost ($29-$500+/month depending on the tool)
• Less control over edge cases
• Another tool in your stack

The Decision Framework

| Factor | Build | Buy | |--------|-------|-----| | MRR under $10K | Maybe | Probably not (recovery gap is small) | | MRR $10K-$100K | Probably not | Yes (ROI is clear) | | MRR over $100K | Only if you have dedicated billing eng | Yes | | Engineering bandwidth is scarce | No | Yes | | You want to iterate on dunning | Build | Buy |

For most SaaS companies between $10K and $100K MRR, buying makes more sense. The cost of a dunning tool ($30-$100/month) is trivial compared to the revenue it recovers.

Dunning Metrics You Should Track

Primary Metrics

1. Recovery Rate — percentage of failed payments that are eventually collected. Target: 70-85%.

2. Net Revenue Recovered — total dollar amount recovered per month. This is your dunning ROI.

3. Involuntary Churn Rate — percentage of customers lost to payment failures. Target: under 1% monthly.

Secondary Metrics

4. Time to Recovery — average days between failure and successful payment. Lower is better.

5. Email Open/Click Rates — how engaging are your dunning emails? Benchmark: 40-60% open rate, 15-25% click rate.

6. Save Offer Acceptance Rate — what percentage of customers accept a discount/pause/downgrade? Benchmark: 10-30%.

7. Win-Back Rate — percentage of canceled-for-payment customers who reactivate. Benchmark: 5-15%.

How to Calculate Recovery Rate

Recovery Rate = (Recovered Payments / Total Failed Payments) × 100

Track this monthly. If your recovery rate is below 65%, your dunning system needs work. The biggest opportunities are usually:

1. Adding more touchpoints to your email sequence
2. Introducing save offers
3. Optimizing retry timing based on decline codes

Common Dunning Mistakes

1. Not Dunning At All

Surprisingly common. Many SaaS companies rely entirely on Stripe's default behavior (a few retries and a basic email). This leaves 30-40% of recoverable revenue on the table.

2. Too Aggressive, Too Fast

Sending three emails on Day 1 with "YOUR ACCOUNT WILL BE DELETED" language destroys trust. Failed payments are rarely the customer's fault. Start gentle, escalate gradually.

3. Ignoring Hard Declines

Hard declines (expired card, invalid number) will never succeed on retry. The only path to recovery is getting the customer to update their payment method. If your system retries hard declines without emailing the customer, you're wasting time.

4. One-Size-Fits-All Approach

A customer paying $9/month and a customer paying $999/month should not get the same dunning treatment. High-value customers might warrant a personal call or Slack message in addition to emails.

5. No Save Offers

If the only outcomes are "payment succeeds" or "subscription canceled," you're missing the middle ground. Many customers will accept a discount or plan change when given the option.

6. Stopping After Cancellation

The relationship doesn't end at cancellation. Win-back campaigns recover 5-15% of churned customers. Your data retention window is a natural opportunity.

Dunning and Compliance

CAN-SPAM

Dunning emails are transactional (related to an existing subscription), not marketing. They're exempt from most CAN-SPAM requirements. However, you should still:

• Include your business address
• Provide a way to contact you
• Not use deceptive subject lines

GDPR

If you serve EU customers:

• Dunning emails are covered under "legitimate interest" (you have a contractual relationship)
• You must still honor data deletion requests
• Your data retention window after cancellation should be documented in your privacy policy

PCI Compliance

Your dunning system should never handle raw card numbers. Use tokenized payment methods (Stripe handles this). Your dunning emails should only reference the last 4 digits of the card.

Key Takeaways

1. Dunning is the highest-ROI activity in SaaS operations — it recovers revenue from customers who want to pay
2. A complete system has 5 layers: pre-dunning, retries, communication, save offers, and win-back
3. Different decline codes need different strategies — don't treat soft and hard declines the same
4. Send 4-6 emails over 14-21 days — start friendly, escalate gradually
5. Track your recovery rate — target 70-85%. Below 65% means your system needs work
6. Most SaaS companies should buy, not build — the ROI math is clear for $10K+ MRR

Involuntary churn is the most fixable problem in SaaS. With the right dunning system, you can recover the majority of failed payments and keep customers who want to stay.