Dunning for B2B SaaS: Automating Dunning Sequences on Unpaid Subscription Invoices

Dunning in B2B SaaS means two completely different jobs, and most teams only automate one of them. Card retry dunning recovers failed credit card charges on self-serve plans and is handled by Stripe, Chargebee, Recurly or Zuora. Invoice dunning chases the invoiced contracts your sales team closed, where a human at the customer has to approve and schedule a payment. Billing tools barely touch the second one, which is where the money actually sits.

The gap shows up the moment a company moves upmarket. Self-serve revenue is on file and retries itself. Then the first $60,000 annual contract lands, the customer asks for net 45 and a PO number, and the invoice goes to an accounts payable inbox nobody on your team has ever spoken to. Your billing platform marks it sent and stops. Ninety days later somebody finally notices.

What is dunning in B2B SaaS?

Dunning is the structured sequence of reminders and escalations that runs from the moment a payment is due until it is collected or written off. In B2B SaaS it covers two separate failure modes: a card that declines on renewal, and an invoice that a customer has received but not yet approved or paid. The first is a payments problem. The second is a collections problem.

The word itself is old, and the general process is the same one every business uses. We cover the mechanics and the legal framing in more depth in what dunning actually means, and there are ready-to-send wordings in our dunning letter templates.

What is the difference between card retry dunning and invoice dunning?

Card retry dunning is automated recovery of a declined charge against a payment method you already hold. Invoice dunning is persuading a person to schedule a payment they have not yet approved. They fail for different reasons, they are fixed by different tools, and confusing them is why finance teams end up with a billing platform that reports 94 percent recovery while receivables keep climbing.

If most of your revenue is invoiced rather than charged, the second column is your real problem and no amount of smart retry logic will move it.

Why do B2B SaaS invoices go unpaid?

Rarely because the customer cannot pay. In B2B software the common causes are procedural: the invoice never reached the right AP contact, it is missing a purchase order number the customer requires, it went to a portal like Coupa or Ariba that nobody on your side submits to, or an internal approver has been on leave for two weeks. A smaller share are genuine disputes over usage overages, seat counts or credits from a mid-term downgrade.

Two of those causes are worth separating out because they are unique to subscriptions. First, mid-term changes create credit notes that customers use as a reason to hold the whole invoice rather than pay the undisputed portion. Second, auto-renewal invoices arrive without a fresh human decision behind them, so they sit in an approval queue longer than a negotiated invoice would.

What should a B2B SaaS dunning sequence look like?

Start before the due date, escalate by channel rather than by tone, and put a named human at the end of it. A sequence that only ever sends email from a noreply address trains the customer to ignore it. Here is a sequence that works for invoiced B2B contracts.

The detail that matters most is the day 5 step. Escalating sideways to the commercial owner, rather than sending a sterner email to the same silent inbox, is what unsticks most B2B invoices. AP does not prioritize your invoice; the person who bought your product does.

When should you escalate from email to a phone call?

Once two emails have gone unanswered, or roughly day 15 past due, whichever comes first. Email deliverability is the silent killer here: invoice reminders from a billing platform frequently land in spam or a shared inbox nobody owns, so silence is not a signal of refusal. A single call establishes whether the invoice was received, who owns approval and when payment is realistically scheduled, which is information no reminder sequence can produce on its own.

Almost no receivables platform will actually place that call. Sidetrade is the notable exception among the major vendors, with an agent it states can make up to 1,000 calls a day. AccountsReceivable.ai makes live AI phone calls as part of the standard sequence, which is the step most teams skip because it is the one that needs a person.

Which tools handle dunning for B2B SaaS?

Split the question by which dunning you mean. For card retries, your billing platform already does it and a separate tool is usually waste. For invoice dunning, you want an AR platform that connects to your ledger, not your billing engine.

If you are evaluating the wider category rather than dunning alone, our page on dunning management software covers the feature checklist, and invoice to cash software maps how dunning fits alongside cash application and dispute handling in one process.

How do you dun a customer without churning them?

Segment before you sequence. A customer who is three days late on their fourth consecutive on-time renewal should not get the same treatment as one who has been late four quarters running. Sending both the same day-5 escalation is how good customers get annoyed and bad ones stay comfortable.

The useful segmentation inputs are payment history, contract value, and whether the account is healthy in the product. That last one is easy to overlook: an account that stopped logging in two months ago is not a collections problem, it is a renewal problem wearing a collections costume, and chasing it harder will not help. Teams that pipe product usage and support signals into one account view can tell those two situations apart before finance picks up the phone.

Do you need dunning software if you use Stripe or Chargebee?

If all your revenue is card-on-file, no. Stripe Smart Retries and the equivalents in Chargebee and Recurly handle involuntary churn well, and bolting a second tool on top adds cost without adding recovery. The moment you start invoicing on net terms, yes, because those platforms send reminders but do not escalate, do not call, do not read remittance advice off an email attachment and do not apply the cash back to your ledger.

The practical test: pull your aging report and split it by how the customer pays. If the balance over 30 days past due is concentrated in invoiced contracts, your billing platform is not the tool that fixes it.

Where to go from here

Work out which of the two dunning problems you actually have, then buy for that one. For most B2B SaaS companies past their first few enterprise contracts, the answer is invoice dunning, and the fastest improvement is not a longer email sequence but a shorter path to a human conversation. Our AR software built for SaaS billing models covers subscription-specific handling like credits and mid-term changes, and collections automation software covers the sequencing and escalation engine in more depth.