Dunning management for UK SaaS and subscription businesses
By InvoiceReminder Editorial Team · Published 6th August 2026
For UK businesses built on recurring revenue, the steady flow of subscription payments is the lifeblood of the company. But what happens when that flow is interrupted? Failed card payments, often called "involuntary churn," are a silent profit killer for SaaS and subscription companies. This isn't the same as chasing a one-off, 30-day net invoice; it requires a specialised process known as dunning management, which focuses on customer retention just as much as payment recovery.
This article breaks down how to build an effective dunning strategy for your UK subscription business. We'll explore why it's fundamentally different from traditional credit control, detail the steps for recovering failed payments, and explain how to communicate with customers without driving them away for good.
Why Subscription Dunning is a Different Beast
If your background is in traditional B2B services, your instinct for a late payment might be to pick up the phone or send a firm reminder. For subscription businesses, especially those with a high volume of lower-value monthly payments, this approach is both impractical and counter-productive.
The key difference is intent. A client failing to pay a £5,000 invoice for a completed project is often a cash flow or administrative issue on their end. A customer whose £20 monthly subscription payment fails is very rarely doing so deliberately. It's almost always a technical glitch with their payment card.
Therefore, the goals of dunning management are twofold and equally important:
- Recover the payment: Secure the revenue for the current billing period.
- Retain the customer: Fix the underlying payment issue and keep the customer subscribed for future periods.
Aggressive chasing tactics that might work for a large, single invoice will likely cause a subscription customer to churn permanently. Your dunning process must be treated as a customer service function, not a collections one.
The Anatomy of a Failed Subscription Payment
To fix the problem, you first need to understand the causes. Failed payments, which payment processors often categorise as "declines," fall into two main camps.
- Soft Declines: These are temporary failures. The card is valid, but the transaction couldn't be processed at that moment. Common causes include insufficient funds, a temporary block from the issuing bank, or network timeouts. These are often resolved by simply retrying the payment a day or two later.
- Hard Declines: These are permanent failures. The card is no longer valid, and retrying the payment with the same details will always fail. Causes include the card being reported lost or stolen, the account being closed, or the card details being entered incorrectly in the first place.
Your dunning strategy must account for both. A "smart retry" schedule can resolve many soft declines automatically, whereas hard declines always require customer intervention.
Common reasons for failed payments include:
- Expired Card: The most frequent culprit. The card on file has passed its expiry date.
- Insufficient Funds: A classic soft decline, common in B2C and with smaller businesses.
- Bank/Security Blocks: A customer's bank may block a recurring charge if it looks unusual, or due to Strong Customer Authentication (SCA) requirements.
- Cancelled Card: The customer has reported the card lost or stolen and has been issued a new one with a different number.
- Incorrect Details: The CVC or postcode on file is no longer correct.
Building an Effective Dunning Strategy for UK Subscription Businesses
A robust dunning strategy has three phases: preventing failures before they happen (pre-dunning), managing the recovery process (active dunning), and deciding what to do when automation fails (post-dunning).
Pre-Dunning: Preventing Failures Before They Happen
The best way to handle a failed payment is to stop it from occurring.
- Card Expiry Notifications: Send an automated email to customers 30-45 days before their card on file is due to expire. The message should be friendly and helpful, with a direct, secure link to their billing page to update their details.
- Payment Method Updaters: Many modern payment processors (like Stripe and GoCardless) have relationships with card networks (like Visa and Mastercard). They can often automatically update a customer's card details when a new card is issued, without the customer having to do anything. Check if your payment gateway offers this service.
- Clear In-App Billing Portal: Make it incredibly easy for customers to find where to update their payment details within their account settings. Don't hide it three clicks deep in a confusing menu. A prominent "Billing" or "Subscription" link is essential.
Active Dunning: The "In-Dunning" Sequence
When a payment inevitably fails, you need a calm, automated, and escalating sequence of communications and actions. This is where you combine automated emails with smart payment retries. The goal is to be persistent but not annoying.
Here is a sample dunning schedule for a typical monthly subscription:
| Day | Action(s) | Communication (Email) | Tone & Goal |
|---|---|---|---|
| 0 | Payment fails. Retry #1 (smart retry). | Optional Email: Send an immediate, friendly email. Subject: "Heads-up: We had an issue with your payment." | Informational & Low-Pressure: Assumes a temporary glitch. Provides a link to update details but doesn't create urgency. |
| 3 | Retry #2 (if still failing). | Email #1: Send a clear, direct email. Subject: "Action Required: Update your payment details for [Your Product]". | Helpful & Direct: Explains the payment failed again. Stresses the benefit of the service they might lose. Provides a clear call-to-action link. |
| 7 | Retry #3 (if still failing). | Email #2 & In-App Notice: Send a firmer email. Subject: "Your [Your Product] access is at risk". Display a banner inside the app. | Urgent but Fair: Clearly states that service will be suspended soon if the issue isn't resolved. Reassures them their data is safe. |
| 14 | Final Retry #4. | Email #3 (Final Notice): Subject: "Final Notice: Your [Your Product] subscription has been suspended". | Informative & Consequential: Confirms the service is now suspended. Explains exactly how to reactivate by paying the outstanding amount. |
| 21+ | Suspend service (or downgrade). | Email #4 (Optional): A week or two later, a final "We'd love to have you back" email can be sent before closing the account. | Recovery & Feedback: A last-ditch attempt to win them back or gather feedback on why they churned. |
This schedule gives the customer ample opportunity to fix the issue and respects that they may not see the first email immediately.
Post-Dunning: Managing Subscription Arrears
If your automated dunning sequence completes and the payment has still not been recovered, you have a decision to make. For a £20/month subscription, launching a full-scale debt recovery process is almost never worth the time, cost, or reputational damage.
Your main options are:
- Downgrade to a Free Plan: If you have a freemium model, automatically moving the user to the free tier is an excellent strategy. It keeps them in your ecosystem, their data is preserved, and they can easily upgrade again in the future.
- Suspend and Hold: Suspend their account access but hold their data for a defined period (e.g., 90 days). This allows for easy reactivation if they return. Your terms of service should be clear about your data retention policy for suspended accounts.
- Write Off and Cancel: For low-value subscriptions, the most pragmatic solution is often to write off the small debt and cancel the account. The administrative cost of chasing a single £20 payment far outweighs the amount itself.
The key is to have a clear, automated policy. You cannot afford to make these decisions on a case-by-case basis when you have hundreds or thousands of subscribers.
Dunning vs. Traditional Invoice Chasing: A Direct Comparison
To crystallise the difference, let's compare the two processes side-by-side.
| Feature | Subscription Dunning | Traditional Invoice Chasing |
|---|---|---|
| Primary Goal | Retain the customer, recover the payment. | Collect the specific debt owed. |
| Common Cause | Technical issue (e.g., expired card). | Customer cash flow, administrative delay, dispute. |
| Communication Tone | Helpful, customer-service oriented, automated. | Professional, firm, escalating to legalistic. |
| Automation Level | High. Relies on automated retries and emails. | Often manual or semi-automated. |
| Legal Tools | Rarely used. Focus is on service suspension. | Uses Late Payment Act (statutory interest & compensation). |
| Typical Value | Low (£10 - £200 per month). | High (£500 - £50,000+ per invoice). |
| Outcome of Failure | Involuntary churn (customer is lost). | Debt recovery, legal action, damaged relationship. |
As the table shows, applying the mindset of traditional B2B credit control to a SaaS business is a recipe for high churn and a poor customer experience.
Leveraging Automation for Dunning and Arrears
Manually tracking failed payments, retrying cards, and sending email sequences is not a scalable activity for any subscription business. Automation is non-negotiable.
Many all-in-one subscription management platforms like Chargebee or Recurly have sophisticated dunning management built-in. If you're using a payment processor like Stripe Billing, it also includes configurable "smart retries" and dunning email capabilities. These are excellent, purpose-built tools.
However, many UK small businesses and startups manage their recurring revenue streams through recurring invoices generated by their accounting software, such as Xero, QuickBooks, or FreeAgent. While this is a common workflow, it often lacks the sophisticated, automated dunning logic of dedicated subscription platforms, leaving founders or admin staff to chase these small, overdue payments by hand. For businesses managing subscriptions via recurring invoices, the manual follow-up can be overwhelming. This is where tools like InvoiceReminder come in, automating the email chasing sequence for those overdue invoices and freeing up time that's better spent serving customers.
Whatever your stack, the principle is the same: automate the process, define the rules, and only intervene manually when the automated process has run its course without success.
Frequently asked questions
What is "dunning"?
Dunning is the process of communicating with customers to collect payments on accounts receivable. In the context of subscription businesses, it specifically refers to the automated process of contacting customers whose recurring payment has failed, with the dual goals of recovering the payment and retaining the customer.
What is a good recovery rate for failed payments?
Industry benchmarks vary, but a well-optimised dunning process can typically recover between 30% and 50% of payments that initially fail. The exact rate depends heavily on your customer base (B2B vs. B2C), price point, and the sophistication of your dunning tools and communications. The key is to measure your rate and continually test different email copy, timings, and retry schedules to improve it.
Should I suspend a customer's service immediately after a failed payment?
No, this is generally a bad practice that leads to high churn. A failed payment is often a temporary issue. You should always offer a "grace period" of at least 7-14 days, during which you attempt to retry the card and communicate with the customer, before suspending service. Suspending access immediately is a punitive measure that alienates customers who had no intention of missing a payment.
Can I charge late payment fees on a failed subscription in the UK?
This is complex. For B2B transactions based on an invoice, you can rely on the Late Payment of Commercial Debts (Interest) Act 1998 to charge statutory interest and a fixed compensation sum. However, for an automated, recurring card payment (especially B2C), this is much harder. Charging extra fees for failed card payments can be seen as punitive and may be challenged as an unfair term under consumer protection law. Your ability to do so depends entirely on what is clearly stated in the terms and conditions the customer agreed to. In most cases, it's not worth the risk or customer ill-will for a small monthly subscription.
How many times should I retry a failed card payment?
A "smart retry" schedule is better than retrying every day. A good starting point is to retry 3-4 times over a two-week period. Payment processors often suggest optimal schedules based on their data, which might look like: retry 1 day after failure, then 3 days later, then 5-7 days later. Retrying too frequently can lead to the issuing bank blocking your transactions altogether.
Automate Your Chasing and Get Paid Faster
Manually chasing payments, whether they're for one-off projects or recurring subscriptions, is a significant drain on the time and energy of any business owner. Setting up an automated system is crucial for efficient credit control and maintaining healthy cash flow.
For UK small businesses, freelancers, and accountants using Xero, FreeAgent, Sage, or QuickBooks, InvoiceReminder helps you stop chasing invoices by hand. It sends scheduled, automated chasing emails using configurable escalation rules, moving from friendly reminders to final notices without you having to lift a finger. The platform currently offers a plan with unlimited email reminders at no cost, with no card required to sign up. InvoiceReminder is built by the team behind WeCovr, a company authorised and regulated by the Financial Conduct Authority which has arranged over one million insurance policies for UK customers.