# Dunning Email Examples for SaaS

> Dunning email examples for SaaS companies, from first payment failure to final notice and recovery confirmation, with tips on tone, timing and design.

Source: https://comppound.com/blog/dunning-email-examples-for-saas (published 2026-07-15)

Dunning emails notify customers when a payment fails and help them update their payment details before they lose access. They are one of the most effective tools for reducing involuntary churn, which is the churn that happens when a customer who intended to keep paying is lost because a card expired, a bank flagged a charge or the person who owned the card left the company. The dunning email examples for SaaS below cover the full sequence, from the first failed charge to the confirmation that everything is fixed, along with the reasoning behind each one.

Good dunning emails are clear, helpful and timely. They treat a failed payment as a routine problem, which it usually is, rather than as a customer mistake.

## The principles behind good dunning emails

Before the templates, it helps to understand what each email is trying to do. A customer whose payment failed usually doesn't know it yet, isn't thinking about your product and may not be the person who can fix it. The email has to get noticed, explain the situation quickly and make the fix effortless.

That starts with a clear subject line. Dunning emails compete with everything else in the inbox, and a vague subject like "Account notice" is easy to ignore. Say plainly that a payment didn't go through. The body should explain what happened in one or two sentences, without technical jargon from the payment processor.

Each email should have one direct action: update payment details. Don't add links to new features, a survey or the blog. The only thing that matters in this email is getting the payment method fixed.

Avoid blame and threats. Most failed payments happen because a card expired or was replaced, not because the customer is trying to avoid paying. A tone that implies wrongdoing annoys loyal customers and makes them less likely to act. At the same time, be clear about the timeline. If access will change on a certain date, say so. Clarity is respectful, and it gives the customer a reason to act now.

Finally, make the update process easy. The best dunning flows let the customer update their card through a secure link without logging in, because the billing contact at a B2B company may not have a login at all, or may have forgotten it. Every extra step between the email and the updated card loses some customers.

## Example 1: The first failure

Send this immediately after a payment fails.

> **Subject:** Your [Product] payment didn't go through
>
> Hi [Name],
>
> We tried to charge your card ending in [last four] for your [Product] subscription, but the payment was declined.
>
> This often happens when a card expires or is replaced. You can update your payment details here:
>
> [Update payment method]
>
> Your account remains active, and we'll try the payment again in a few days.
>
> If you have questions, just reply to this email.
>
> Thanks,
> The [Product] team

This email does several useful things. Naming the last four digits helps the recipient identify which card is affected, which matters in companies with several cards. The line explaining that this often happens when a card expires removes any sense of accusation. Reassuring the customer that the account is still active and that you'll retry the charge sets a calm tone. Many customers fix the problem from this first email simply because it reached them before the issue felt urgent.

## Example 2: The second reminder

Send this a few days later if the payment is still unresolved.

> **Subject:** Reminder: update your payment details for [Product]
>
> Hi [Name],
>
> We still haven't been able to process your payment for [Product]. To avoid any interruption, please update your payment method:
>
> [Update payment method]
>
> It only takes a minute.
>
> Thanks,
> The [Product] team

The second email is shorter and slightly more direct. It introduces the idea of interruption without stating a deadline yet. "It only takes a minute" addresses the most common reason people put off tasks like this: they assume it will be tedious. If your update flow genuinely takes a minute, say so. If it doesn't, fix the flow before you write the line.

## Example 3: The value reminder

Send this before the final notice, reminding the customer what they would lose.

> **Subject:** Keep your [Product] workspace active
>
> Hi [Name],
>
> Your team has [created X projects / tracked X reports] in [Product]. We'd hate for you to lose access because of a payment issue.
>
> Update your payment method here to keep everything running:
>
> [Update payment method]
>
> Thanks,
> The [Product] team

This email shifts the focus from the payment to the work the customer has invested in your product. Seeing that their team has built dozens of reports or projects makes the cost of losing access concrete. Only include usage details that are accurate and meaningful. If the account has barely been used, a line about how many projects they created will either look odd or remind them they don't need the product. In that case, a general sentence about keeping their workspace and data intact works better.

## Example 4: The final notice

Send this shortly before access changes.

> **Subject:** Your [Product] account will be paused on [date]
>
> Hi [Name],
>
> We haven't been able to process your payment. On [date], your account will be paused, and you won't be able to access your workspace.
>
> Your data will be kept for [time period], and you can reactivate anytime by updating your payment details:
>
> [Update payment method]
>
> If something has changed and you need help, reply to this email and we'll work it out.
>
> Thanks,
> The [Product] team

The final notice is the most direct email in the sequence, and it should be. It names a specific date and explains exactly what will happen. It also reassures the customer that their data won't disappear immediately, which reduces panic and leaves the door open to coming back later.

The line inviting a reply is important. Some customers aren't paying because something has changed: the budget was cut, the champion left or the company is switching tools. Giving them a way to talk to a person can lead to a downgrade, a pause or a conversation that saves the account. A rigid automated sequence would lose it.

## Example 5: Account paused

Send this when access is restricted.

> **Subject:** Your [Product] account has been paused
>
> Hi [Name],
>
> Your [Product] account is now paused because we couldn't process payment. Your data is safe and will be kept until [date].
>
> To restore access, update your payment details:
>
> [Reactivate account]
>
> Thanks,
> The [Product] team

Use calm, factual language. The customer may be frustrated or embarrassed. Telling them their data is safe and making reactivation a single click gives them an easy path back. Some customers only notice the problem when their team loses access, so this email often prompts a quick fix from someone who missed every earlier message.

## Example 6: Recovery confirmation

Send this as soon as the payment succeeds.

> **Subject:** Payment received, you're all set
>
> Hi [Name],
>
> Thanks for updating your payment details. Your [Product] subscription is active, and everything is back to normal.
>
> Thanks,
> The [Product] team

This email closes the loop. Without it, customers who updated their card may wonder whether it worked, and some will contact support to check. It costs nothing to send and leaves a good final impression of an otherwise awkward process.

## Timing the sequence

A typical sequence sends the first failure email on day zero, a reminder around day three, the value reminder around day seven and the final notice somewhere between day ten and day fourteen. The paused-account email goes out when the grace period ends. These timings are a starting point, not a rule.

Align the schedule with your payment retry logic and your grace period. If your billing system retries the card on day three and day seven, send the reminders just before or just after those retries so the messaging matches reality. If a retry succeeds, cancel the remaining emails immediately. Nothing confuses a customer more than a "final notice" for a payment that went through two days earlier.

Consider your customer mix as well. Annual contracts with larger customers may justify a longer grace period and more personal outreach, because the account is worth more and the billing process inside a bigger company moves more slowly.

## Who should receive dunning emails

Send dunning emails to the billing contact and to account admins. In B2B accounts, the person who entered the card during signup may not be the person who manages billing today. They might have left the company, changed roles or handed purchasing to a finance team.

Let customers add multiple billing contacts, and prompt them to keep the list current. When an email to the billing contact bounces, that is a strong sign the contact has left, and your sequence should fall back to the admins. For high-value accounts, a customer success manager reaching out personally after the second failed email can recover accounts that automated emails would miss.

## Design tips

Keep dunning emails simple and mostly text. Heavy graphics, large images and complex layouts can trigger spam filters and look like marketing, which is the opposite of the impression you want. Use a single clear button for updating payment, and make sure the link works well on mobile, since many people will open the email on their phone. Test the full flow on a phone, from opening the email to submitting new card details, before you launch the sequence.

## Add in-app messages

Email is not the only channel. Show a banner in the product for admins when a payment has failed. Some customers will see the banner before they check their email, and a message inside the tool they use every day is hard to ignore. Keep the banner wording consistent with the emails and link to the same update flow.

Avoid showing the banner to every user in the account. A regular team member can't fix billing and may find the message alarming. Target it to admins and billing roles.

## Measure performance

Track open and click rates for each email, but focus on payment recovery rate by email, which tells you which messages actually prompt action. Measure time to recovery, since faster recovery means fewer days of uncertainty and less risk of the customer churning in the meantime. Watch your overall involuntary churn rate over months to see whether the sequence is improving.

Test subject lines and timing to improve recovery. A clearer subject on the first email, or moving the value reminder a few days earlier, can make a noticeable difference. Change one thing at a time so you can tell what helped.

## The takeaway

Dunning is a quiet part of retention that many SaaS teams set up once and forget. A thoughtful sequence uses clear subject lines, one action per email, a calm tone, honest deadlines and an update process that works without logging in. Pair it with in-app banners for admins, keep billing contacts current, and review recovery rates regularly. Start with the six examples above, adapt them to your retry schedule, and refine them as the data comes in.

## Keep reading

- [Trial Expiration Emails That Convert Without Begging](/blog/trial-expiration-emails-that-convert-without-begging)
- [B2B SaaS Welcome Emails: What to Send in the First 24 Hours](/blog/b2b-saas-welcome-emails-what-to-send-in-the-first-24-hours)

## Frequently asked questions

### What is a dunning email?

An email sent to notify customers of a failed payment and ask them to update payment details.

### How many dunning emails should SaaS companies send?

Commonly three to five over one to two weeks, aligned with payment retries and grace periods.

### Should dunning emails be automated?

Yes, though high-value accounts may benefit from additional personal outreach.

## About Comppound

Comppound runs SEO and AI search for B2B SaaS companies: a person sets the plan and reviews samples and every high-risk page, and AI speeds up production.

- [Get the free report](https://comppound.com/ai-visibility-report): When buyers ask ChatGPT about your category, are you in the answer?
- [Book a call](https://comppound.com/contact): Most of this works better when buyers can find you first