Dunning Management
Dunning management is the automated process of recovering revenue from failed payments. It includes smart payment retry logic (re-attempting charges at optimal times), customer communication sequences (emails and SMS notifying customers of payment issues), and escalation workflows that progressively increase urgency before an account is cancelled.
Payment Recovery Rate
Up from 30% through optimized dunning at BatchService
Why Dunning Management Matters for SaaS Companies
Failed payments are the #1 cause of involuntary churn, representing 20-40% of total churn in most SaaS companies. Effective dunning recovers 50-70% of failed payments, directly translating to recovered revenue. For Seed to Series B companies, implementing dunning is often the highest-ROI retention initiative you can pursue.
An Operator's Take
At BatchService, the default Stripe retry logic was recovering about 30% of failed payments. We replaced it with a custom dunning workflow: retry timing optimized by failure reason code (insufficient funds retried on the 1st and 15th of the month — paydays; expired card retried after a pre-expiration update email). We added a 4-email sequence with escalating urgency: friendly reminder, payment update request, service interruption warning, final notice. Recovery rate went from 30% to 68%. On $380K in annual failed payments, that was an additional $145K recovered — pure profit since these were already-acquired customers.
Dealing with this at your company?
Get a free diagnostic — no pitch deck, just an honest assessment of where you stand.
Common Mistakes
What I see go wrong most often in the field.
Relying on your payment processor's default retry logic. Default retries are not optimized for your customer base or failure types.
Cancelling accounts immediately after payment failure. A 7-14 day grace period with communication recovers significantly more revenue.
Sending generic payment failure emails. Emails that explain the issue clearly and include a one-click payment update link recover 2-3x more than generic notifications.
Not tracking dunning metrics: recovery rate, time to recover, and recovery by failure reason code.
What to Do This Week
Concrete steps you can take right now.
Audit your current payment failure recovery rate. What percentage of failed payments are eventually recovered?
Implement custom retry timing based on failure reason codes: insufficient funds on likely paydays, expired cards after sending update reminders.
Build a 4-step email sequence: friendly reminder (day 1), specific instructions (day 3), service warning (day 7), final notice (day 12).
Use the Revenue Leakage Scorecard to assess your dunning effectiveness relative to best practices.
Related Resources
Frequently Asked Questions
What is a good dunning recovery rate?
Best-in-class dunning recovers 60-70% of failed payments. The average SaaS company using default processor retries recovers only 25-35%. The gap is substantial — improving from 30% to 65% recovery on $300K in annual failed payments saves $105K in revenue per year.
How many dunning retries should you attempt?
Typically 4-8 retry attempts over a 14-21 day grace period. Space retries based on failure reason: insufficient funds benefit from waiting for paydays (1st, 15th of month). Expired cards benefit from longer gaps to allow the customer to update payment info. Always pair retries with email communication.
Operations & Systems Consultant
16+ years leading operations and growth, including through a $2B exit and an IPO. I untangle the software and processes companies accumulate over time and rebuild them into systems teams can run.
Need Help With Billing Automation?
Most established companies are paying for operational debt they can't see. Let's figure out what it's costing you.
16+ years leading companies · Senior-level, not junior staff · Fixed-fee or embedded engagements