Two failed charges out of 100 at-risk customers paying $30 a month represent $60 in monthly recurring revenue at risk. In a queued dunning sequence, a retry can succeed before the next email sends—so your workflow must check payment status again before delivery.

Dunning emails ask a customer to resolve a failed payment or an overdue balance. For SaaS subscriptions, that usually means explaining a failed charge and linking to a secure payment-method update page. For a business invoice, it means identifying the overdue invoice and asking the right billing contact to pay or raise an issue. Below is a retry-aware example cadence and adaptable copy for both situations.

What Dunning Emails Are for SaaS Billing

Dunning is the follow-up process for a payment that has not been collected. A failed subscription charge, an invoice that has passed its due date, and a routine reminder sent before an invoice is due are three different events. Each deserves a different message and action.

A failed-payment email follows a recurring charge that a payment processor could not collect. Its usual goal is to help the customer update a payment method or resolve the issue before the subscription is interrupted. A past-due invoice email follows an unpaid business invoice and should identify the invoice and its payment route. A pre-due reminder is a courtesy notice, not a collection request.

Keep the audience and action tied to the event. A card-update link makes sense for a subscription account but may be irrelevant to an invoice recipient who pays by bank transfer. If your billing system cannot tell which event occurred, fix that before automating the message.

Why Dunning Emails Matter for Revenue and Retention

A failed recurring charge can lead to involuntary churn: a customer loses service because a billing issue was not resolved, rather than choosing to cancel. An overdue invoice delays cash collection and can raise days sales outstanding (DSO), a measure of how long it takes a business to collect payment.

The financial effect compounds when the same problem recurs. In a Postmark article, Kristen DeCosta of Churn Buster illustrates a “Rule of 78” calculation: retaining one additional customer per month produces 78 recovered customer-months over 12 months. In the article’s example, 100 at-risk customers paying $30 monthly, with a 2% failure in dunning-email delivery, represent $60 of monthly recurring revenue at risk; the article calculates a $4,500 loss over 12 months using its model. Treat these as an illustration of compounding exposure, not as a recovery benchmark or a forecast for your business.

Email can help a customer understand and fix a billing problem, but a delivered message does not prove a payment was collected. Track payment outcomes separately from email events, and give customers a way to contact a person when the issue is a disputed charge, an incorrect amount, or a billing contact who cannot make the change.

Subscription Dunning vs. Overdue-Invoice Dunning

DetailFailed subscription paymentOverdue invoice
TriggerA recurring charge failsAn invoice remains unpaid after its due date
Typical recipientSubscription billing contact or account ownerInvoice recipient or accounts-payable contact
Primary actionUpdate the payment method or resolve the failed chargePay the identified invoice or contact accounts receivable (AR)
Follow-up logicCoordinate messages with payment retriesCheck invoice status, payment terms, and any dispute
Possible escalationService restriction or cancellation under account termsAR or account-team follow-up under agreed terms

For subscriptions, payment retries and emails form one workflow. A retry may succeed after the initial failure, so an email queued earlier should not go out without a fresh status check. For invoices, exclude payments already received, credited, voided, or under dispute according to your billing rules.

Late-payment fees and interest should appear only when supported by the agreement and applicable policy. If an invoice is part of a larger order-to-cash (O2C) process, make sure the person responsible for AR can correct invoice status and contact details. Do not treat a subscription card-update request as a substitute for that invoice workflow.

What to Include in an Effective Dunning Email

A customer should be able to identify the sender, understand what happened, and take one clear action. Include the service or invoice details needed to recognize the request, but send payment credentials through an authenticated page rather than asking customers to email sensitive information.

Use a short subject that describes the event, such as “Payment failed for your Acme subscription” or “Invoice 1842 is past due.” Explain what happened in a calm, specific sentence, include the relevant date or invoice amount, and make the payment or update link’s destination clear. Add a support route for customers who believe the information is wrong.

Recipient accuracy matters as much as copy. The technical administrator may not be the subscription’s cardholder, and an invoice recipient may no longer work for the customer. Send to the recorded billing contact, then provide a way to report a wrong recipient rather than continuing to message the same address.

Sender authentication also supports trust. DeCosta’s Postmark article names DKIM, SPF, custom return-paths, and DMARC alignment as elements to consider. Its example describes Jan receiving a billing email and forwarding it to Mark, the actual cardholder; forwarding can break DKIM and affect DMARC evaluation. An aligned return-path can provide an SPF-alignment path, but forwarding behavior varies, so test the configuration rather than treating any one setting as a delivery guarantee.

A Retry-Aware Dunning Email Sequence and Timing

Here is a practical starting cadence for a subscription with automated retries on days 0, 3, and 7. The exact retry schedule depends on your payment provider and policy; the important rule is to send each follow-up only if the latest retry failed and the balance is still open.

  1. Day 0 — first failure: Notify the billing contact after the initial failed charge. Explain the issue and provide the secure update link. If your system retries immediately, state that another attempt is scheduled only if that is true.
  2. Day 3 — retry result: If the day-3 retry fails, send a concise reminder with the same update action. If it succeeds, cancel pending notices.
  3. Day 7 — unresolved balance: After another failed retry, explain that payment is still unresolved and offer support. Do not imply that service will stop unless that consequence is planned and consistent with the account terms.
  4. Day 14 — final notice, when applicable: Send only if the charge remains unpaid and a service restriction or cancellation is actually approaching. State the date and consequence accurately.

This is an example cadence, not a universal billing policy. If a retry is scheduled for day 5, move the related follow-up to after its result rather than sending on day 3. For invoices, anchor messages to the due date and agreed payment terms instead: a courtesy notice before the due date, followed by a past-due notice and a later AR follow-up if the invoice is still eligible.

Before every send, re-check payment or invoice state, recipient, and account eligibility. That check prevents a customer who paid after a message was queued from receiving an obsolete request. For event handling and duplicate-work safeguards, see our guide to transactional email queue architecture.

Dunning Email Templates You Can Adapt

The examples below use {{variable_name}} as generic template notation, not Volanea-specific syntax. Map the variables to your billing data and test rendered messages before sending. Each message has one primary action.

Pre-dunning card-expiry notice

Trigger: Your billing system reports an upcoming card expiry before the next subscription charge. Action: Update the payment method before the next billing date.

Subject: Your payment method for Acme may expire soon

Hi {{first_name}},

The card on file for your Acme subscription may expire before your next payment on {{next_billing_date}}. To avoid an interruption, review your payment method here: {{payment_method_url}}.

Need help? Contact {{support_email}}.

Acme Billing

Send this only when your billing data indicates the card needs attention; do not present a predicted expiry as a failed payment.

Initial failed-payment email

Trigger: The first subscription charge fails. Action: Review the payment method.

Subject: We couldn’t process your Acme payment

Hi {{first_name}},

We couldn’t process the {{amount}} payment for your Acme subscription on {{failure_date}}. Please review your payment method using this secure link: {{payment_method_url}}.

If you think this is a mistake, contact {{support_email}}.

Acme Billing

Reminder after a failed retry

Trigger: A scheduled retry fails and the balance remains open. Action: Update the payment method or contact support.

Subject: Action needed to keep your Acme subscription current

Hi {{first_name}},

Our latest attempt to collect {{amount}} for Acme was unsuccessful. Update your payment method here: {{payment_method_url}}. If you have already made this change, contact {{support_email}} so we can review the account.

Acme Billing

Friendly overdue-invoice notice

Trigger: An eligible invoice remains unpaid after its due date. Action: Pay the invoice or contact AR.

Subject: Invoice {{invoice_number}} is past due

Hi {{billing_contact}},

Our records show that invoice {{invoice_number}} for {{amount}} was due on {{due_date}} and remains unpaid. Review and pay it here: {{invoice_payment_url}}.

If payment is already in progress or you have a question, contact {{ar_contact}}.

{{company_name}} Accounts Receivable

Final notice before a real service action

Trigger: An unresolved subscription balance is approaching an authorized service restriction. Action: Pay or contact the billing team by the stated date.

Subject: Please resolve your Acme payment by {{action_date}}

Hi {{first_name}},

Our records show that {{amount}} remains unpaid for your Acme subscription. If it is not resolved by {{action_date}}, {{specific_account_consequence}} may apply under your account terms.

Update your payment method here: {{payment_method_url}}, or contact {{support_email}} if the account details are incorrect.

Acme Billing

Automate Dunning Without Sending Stale Messages

Treat a failed-payment event as a reason to evaluate the account, not an unconditional instruction to send. Check payment status, recipient, and message eligibility when the event arrives and again immediately before delivery. Stop the sequence after payment, cancellation, a dispute, or a handoff to a person, according to your billing rules.

A Volanea integration can send billing messages through the same API used for transactional email. Its sending pipeline processes suppression checks, contact upserts, template rendering, tracking, and delivery; its API documentation also covers webhooks and suppressions. Use delivery and bounce events to route unreachable billing contacts for correction, and keep payment success as a separate event from email delivery.

An illustrative request shape looks like this; the endpoint, authentication, and field names must match the current API documentation:

curl --request POST "$VOLANEA_SEND_ENDPOINT" \\
  --header "Content-Type: application/json" \\
  --data '{
    "from": "Acme Billing <billing@example.com>",
    "to": "billing-contact@example.com",
    "subject": "Payment failed for your Acme subscription",
    "html": "<p>Please review your payment method using the secure link in your account.</p>"
  }'

Volanea accepts a bare sender address or the Name <address> format shown above. Its sk_test_ keys render and log messages but never deliver them, which is useful for checking template output and event handling before production sends. Volanea sends through shared Amazon SES infrastructure and has no dedicated IPs. Plans have no overage billing: when a project reaches its monthly email limit, sending pauses. That pause matters for billing notices, so monitor usage and plan capacity rather than assuming critical messages will continue past the limit.

Use versioned HTML templates when you want to review and roll back copy changes, and test each billing state with realistic event data. For broader integration patterns, see our guide to email API integration and the developer guide to reliable email sending.

Measure Recovery, Not Just Email Activity

Track business outcomes alongside delivery events. For subscriptions, measure failed-payment recovery, payment-update completion, and involuntary churn. For invoice follow-up, measure collection progress and DSO. Break results down by message stage so you can see whether the initial notice or a later follow-up is associated with resolution.

Define the recovery window before comparing campaigns. For example, decide whether a charge counts as recovered when a retry succeeds within seven days of the first notice, and distinguish that from a customer who manually updates a card. Otherwise, the sequence can receive credit for a payment that would have succeeded without an email.

Use bounces and other delivery failures to find bad billing contacts, not as a substitute for payment outcomes. Test one change at a time—such as the day of a follow-up or the wording of its action—and prioritize resolved balances over opens. Open activity may help diagnose visibility, but it does not show that the customer paid.

FAQ

What happens if a customer pays after a dunning email is queued?

Re-check the billing system immediately before sending and cancel the queued message if payment has cleared. If the email has already gone out, send a correction when it would prevent confusion. For example, a successful retry on day 3 should cancel a day-7 reminder rather than trigger a request to update a card that is working.

When should a SaaS team switch from automated dunning to personal outreach?

Hand off the case when the customer disputes the charge, the billing address bounces, the recorded contact cannot act, or the account requires a conversation. For instance, a customer who says an invoice was paid by bank transfer needs a status check from AR, not another automated payment link.

Can dunning emails include late fees or interest?

Only state a fee or interest charge when it is supported by the customer agreement and applicable policy. Identify the amount and basis clearly, and route uncertain cases to the appropriate finance or legal reviewer. A collection message should not threaten a charge that the business is not entitled or prepared to apply.

How can I test a Volanea dunning template without contacting customers?

Use a Volanea sk_test_ key to render and log a message without delivering it. Test the subject, sender format, variable substitution, and the billing event that triggers the template. Then use production credentials only when the account state and recipient checks are ready for real delivery.

Start free with 1,000 emails a month → https://app.volanea.com/signup