Dunning Automation for B2B SaaS: The 2026 Playbook

A failed payment is not a lost customer. It is, in most cases, a logistics problem: an expired card, an ACH bounce on a Tuesday, a bank timeout during a processing window. SaaS companies without structured dunning typically recover only 30–40% of failed payments. With a well-built dunning engine, that number climbs to 70–80%. The gap is pure cash left on the table — and for involuntary churn specifically, it can account for 20–40% of total SaaS churn according to Paddle/ProfitWell retention data.

For B2B SaaS finance teams, especially those managing hybrid or usage-based billing at $5M–$100M ARR, dunning automation is one of the most direct levers over cash collection speed. Get it right and you compress DSO, cut involuntary churn, and reclaim hours your AR team spends chasing invoices manually. Get it wrong and you either burn customer trust or lose revenue that customers were ready to pay.

This guide covers how to design, automate, and operate dunning for B2B SaaS — sequences, retry logic, segmentation, usage-based billing edge cases, and how dunning connects to the broader contract-to-cash workflow.

What Is Dunning Management?

Dunning management is the process of systematically following up with customers to recover overdue or failed payments through a combination of automated reminders, payment retries, and escalation workflows. In B2B SaaS, dunning covers everything from pre-due-date reminders and Stripe retry logic to CSM escalation on high-value accounts and formal collections handoff.

B2B dunning is structurally different from consumer subscription dunning. Consumer dunning typically means retrying a card and sending two emails before canceling. B2B dunning involves invoices with Net 30 or Net 60 terms, multiple stakeholders on the buyer side (AP clerk, controller, CFO, procurement), PO number requirements, and the need to preserve relationships with accounts worth tens or hundreds of thousands in ARR.

Failed B2B payments stem from a wider range of causes: expired cards, ACH failures, billing disputes, missing PO numbers, incorrect billing contacts, or simply budget cycle timing. Your dunning system needs to handle all of these — and it needs to know the difference between them, because the right response to an expired card is very different from the right response to a disputed usage charge.

Why Dunning Directly Affects DSO

Effective dunning automation typically reduces DSO by 3–7 days on average, with larger gains possible when dunning is paired with upstream billing automation and downstream cash application. Dunning sits at the tail end of the cash collection chain, but it is often the highest-impact intervention because it targets revenue that has already been earned and invoiced.

The math is straightforward. Every day a failed payment sits unaddressed adds a day to DSO. For a company processing $5M in monthly invoices, shaving three days off DSO frees ~$500K in working capital. According to McKinsey's accounts receivable automation research, automated dunning combined with proactive AR outreach can reduce DSO by as much as 30% — but that figure reflects the combined effect of dunning plus broader AR automation, not dunning in isolation.

Three DSO levers compound together: accurate upstream billing, automated payment retries, and structured dunning sequences. Dunning is the most visible of the three — it's where the money actually lands back in your account — but it performs best when the upstream work is also automated. An accurate invoice with clean contract terms dunned well collects faster than a disputed invoice dunned aggressively. For a broader view of tools that attack all three levers together, see our DSO reduction software buyer's guide.

How to Design an Effective Dunning Sequence

A dunning sequence is a structured series of communications and payment retries sent at defined intervals to recover an overdue or failed payment. The best sequences share three design properties: they start before the due date, they escalate with defined timing, and they match tone to relationship stage.

Start Before the Due Date

The most effective dunning sequences begin before a payment is overdue. A brief reminder 3–5 days before the invoice due date catches expired cards, flagged payment methods, and budget approval bottlenecks before they become collections issues.

Pre-due-date reminders also set the tone of the relationship. When your first touchpoint is a helpful nudge rather than a past-due notice, the customer perceives the interaction differently. You are less "collections" and more "operational partner" — and in B2B, that framing compounds across renewals and expansion.

Map the Escalation Ladder

A dunning sequence should follow a clear escalation path with defined timing at each stage:

• Day -5 to -3 (pre-due reminder): Brief, neutral reminder with invoice details and a payment link.
• Day 0 (payment failure or due date): Immediate notification within one hour of failure. Include the specific error context and a direct link to update payment info.
• Day 3: Second automated retry if decline type allows. Second email with slightly more specific guidance (alternative payment methods: ACH, wire, updated card).
• Day 7: Third follow-up from a real sender address — not no-reply@. Mention account status explicitly.
• Day 14: Escalation email that flags the account and, for high-value accounts, loops in a CSM or account manager.
• Day 21–30: Final notice with service restriction warning. Human on your side, not an automated template.

This cadence aligns with the retry patterns used by leading smart-dunning systems including Stripe Smart Retries, Churnkey, and ProfitWell Retain. The specific days matter less than the principle: frequent early touches, then spaced escalation with human involvement layered in as the stakes rise.

Match Tone to Relationship Stage

Your first email after a failure should assume good faith. Something broke; you're letting them know. By day 14, the tone can shift to acknowledge urgency without being adversarial. By day 30, you are stating consequences clearly.

Tenure also matters. A customer who has paid on time for three years and hits a card expiration is a different situation than a new account with a declined payment on their second invoice. Your sequences should reflect that. A long-tenured account deserves a longer leash and a warmer tone; a brand-new account needs tighter escalation so you catch churn risk before it compounds.

Automating Payment Retries

Payment retry logic is the mechanical backbone of dunning automation. The distinction between soft and hard declines determines whether a retry makes sense at all.

Soft declines are temporary failures: insufficient funds, bank timeouts, processing errors. These should be retried after 24–72 hours, when the underlying condition may have resolved. Hard declines are permanent: stolen card flags, closed accounts, invalid card numbers. Retrying a hard decline wastes processing capacity and can damage your standing with payment processors — some gateways flag merchants who repeatedly retry known-bad cards.

Stripe Billing includes Smart Retries, which uses Stripe's network-wide payment data and machine learning to optimize retry timing. Stripe also runs an automatic card updater that obtains refreshed card details from issuing banks before expiration causes a failure — a quiet, proactive recovery mechanism that resolves a meaningful percentage of would-be failures invisibly.

For B2B SaaS teams with complex billing, the right approach is to let Stripe Smart Retries handle timing optimization while layering your own communication sequences on top. Don't fight the ML by scheduling manual retries that conflict with Stripe's automated attempts. And don't rely on Stripe retries alone — they recover a baseline percentage, but the 70–80% recovery rate that mature dunning programs achieve comes from combining smart retries with structured email cadences, segmentation, and human escalation.

LedgerUp Insight: Stripe Smart Retries optimize when to retry; LedgerUp's Ari agent optimizes what happens around the retry — drafting the right follow-up for the customer's tenure and contract value, surfacing exceptions in Slack, and writing collection outcomes back to NetSuite, Sage Intacct, or Xero automatically.

Personalizing Follow-Ups by Customer Segment

A one-size-fits-all dunning sequence is the single most common design mistake in B2B SaaS. Segmenting by account value, customer health, and aging bucket materially changes recovery rates and preserves relationships with your largest accounts.

Segment by Account Value

A $500/month account and a $50,000/month account should not receive the same dunning sequence. High-value accounts warrant earlier human involvement — if your largest customer's payment fails, a CSM should know within hours, not after two weeks of automated emails go unanswered.

For enterprise accounts, the handoff from automation to human outreach might happen at day 7. For SMB accounts, automation can run the full 30-day sequence before a person gets involved. The economics of AR effort follow the same principle as sales effort: concentrate human time where the revenue is.

Segment by Customer Health Score

If your CRM tracks customer health scores, use them. A healthy account with a failed payment is almost certainly a technical issue — treat it that way with a brief, low-pressure notification. An at-risk account with a failed payment could be a churn signal, and faster escalation to your CS team gives you a chance to address the underlying relationship issue alongside the payment problem.

Churning customers with payment failures may not justify aggressive collections effort at all. Spending cycles dunning an account that has already decided to leave often yields nothing but frustration on both sides — and a negative G2 review.

Segment by Aging Bucket

Aging buckets provide a clean framework for escalation. The bucket determines both the sender and the tone:

• 0–30 days: Automated email sequences, soft and assumptive.
• 31–60 days: CSM or account manager escalation. Offer a payment plan if appropriate.
• 61–90 days: Formal collections notice. Service restrictions may apply.
• 90+ days: Legal review or handoff to a collections agency, depending on account size and contract terms.

The handoff between buckets should be automatic. If your dunning tool requires someone to manually escalate an account from "soft follow-up" to "CSM involvement," that handoff will be missed on busy weeks — and busy weeks are exactly when you need it to fire.

Dunning for Usage-Based and Stripe Billing Environments

Usage-based billing creates dunning challenges that flat-rate subscriptions simply don't have. Variable invoice amounts mean customers sometimes dispute charges they don't immediately recognize, and a dispute is a fundamentally different dunning trigger than a declined card.

UBB invoices are typically generated after the billing period closes, so customers receive a bill for consumption that already happened. Your dunning cadence needs to account for the fact that the customer may need time to validate the invoice against their own usage data before paying. Rushing a collections sequence on a usage-based invoice that the customer hasn't had a chance to review creates friction, not cash. A useful pattern: hold the aggressive escalation touches for usage-based invoices until day 14+, after the typical AP review window has closed.

Your dunning automation needs to distinguish between three situations:

1. "Can't pay" — payment method issue. Retry and communicate.
2. "Won't pay" — churn signal or relationship issue. Escalate to human.
3. "Disputes the amount" — billing accuracy issue. Stop dunning, route to billing review.

Each requires a different response. Retrying a disputed invoice accomplishes nothing. Sending a collections email for a billing error damages trust and invites the customer to delay further while they investigate.

Stripe's metered billing follows the same Smart Retry logic as standard subscriptions, but the dispute rate tends to be higher because variable charges are less predictable to the customer. Grace periods before service restriction are especially important for UBB — cutting off a customer mid-cycle because of a billing dispute has immediate operational consequences for them and reputational consequences for you.

Common Dunning Mistakes to Avoid

1. Starting too late. Waiting until an invoice is 30+ days overdue before first outreach means you've already lost a month of potential recovery time. Pre-due-date reminders and same-day failure notifications are baseline.
2. One-size-fits-all sequences. Same cadence, tone, and escalation for every account regardless of value, tenure, or health score wastes recovery on high-value accounts and over-invests in low-value ones.
3. Ignoring failure type. Retrying hard declines wastes processing cycles and can trigger fraud flags with payment processors. Retry logic must read decline codes and route accordingly.
4. No human escalation path. Fully automated sequences that never involve a person miss the accounts where a phone call or a Slack message to the customer's champion would resolve the issue in minutes.
5. Sending from no-reply@. Day 7 and beyond, messages should come from a real sender. no-reply@ signals automation, which customers ignore. A real address invites reply — and a reply is often all it takes to unstick a payment.
6. Disconnected ERP sync. Collecting a payment is only half the job. If the collected amount doesn't apply to the correct open invoice in NetSuite, Sage Intacct, or Xero, you've traded a collections problem for a reconciliation problem.
7. Dunning disputes instead of routing them. A customer who questions an invoice needs a billing conversation, not another retry. Treating disputes like declines poisons the relationship and delays resolution.

How Dunning Fits Into Contract-to-Cash

Dunning doesn't operate in a vacuum. It sits inside the broader contract-to-cash workflow: contract execution → invoice generation → payment collection → dunning (when needed) → cash application → reconciliation. Treating dunning as a standalone problem usually means solving it twice — once in your collections tool and again when the outcome has to be reflected in your ERP.

Contract terms directly inform dunning parameters. A customer on Net 60 terms with a contractual grace period shouldn't enter your dunning sequence on day 31. Late fee clauses, escalation rights, and payment method requirements all live in the signed agreement. If your dunning automation can't read those terms, someone has to configure every account manually — which means, in practice, they won't.

Invoice accuracy upstream is one of the most overlooked dunning levers. Many B2B dunning triggers, especially for usage-based billing, originate in invoice errors: wrong amounts, missing PO numbers, incorrect billing contacts. Fixing invoice generation reduces the volume of payments that ever enter a dunning workflow in the first place.

CRM data personalizes the collections experience, and ERP sync closes the loop. LedgerUp approaches this by reading signed contracts via its Ari agent to set collections timing automatically, surfacing Stripe payment failures in Slack-native workflows, and syncing outcomes back to NetSuite, Sage Intacct, and Xero for reconciliation. Every dunning action traces back to the original agreement, and every recovered payment lands in the right ledger without a human copying data between systems.

The broader principle applies regardless of tooling: your dunning system should be informed by contract terms, connected to your billing and CRM data, and reconciled in your ERP. Gaps between any of those systems create manual work that scales poorly — and the first place that manual work shows up is in DSO.

FAQ

What is dunning management?

Dunning management is the process of communicating with customers to collect overdue or failed payments through structured follow-ups, payment retries, and escalation workflows. In B2B SaaS, dunning typically involves automated email sequences, payment retry logic, segmentation by account value and health, and defined handoff points where a human takes over when automation can't resolve the issue.

How does dunning automation reduce DSO?

Dunning automation reduces DSO by compressing the time between a payment failure and successful collection, with effective programs typically delivering 3–7 days of DSO improvement on average. Automated sequences start outreach immediately after a failure, retry payments at optimized intervals, segment follow-ups by customer risk, and escalate to human teams before accounts age into later buckets — and the impact compounds further when dunning is paired with upstream billing automation and ERP-level cash application.

What is a dunning sequence?

A dunning sequence is a structured series of communications — typically emails combined with automated payment retries — sent at defined intervals to recover an overdue or failed payment. Effective B2B sequences begin with a pre-due-date reminder, escalate through 3–5 follow-up emails over 30 days, shift sender from automated to human around day 7, and include clear triggers for CSM or collections involvement on high-value accounts.

How should dunning differ for usage-based billing?

Dunning for usage-based billing requires longer review windows, dispute-aware routing, and grace periods before service restriction because customers need time to validate variable consumption charges. Unlike flat-rate subscriptions, UBB dunning must distinguish between payment method failures, account-level churn signals, and invoice disputes — retrying or dunning a disputed invoice accomplishes nothing and damages trust, so disputes should route to billing review instead of collections.

What is the best dunning software for Stripe billing?

The best dunning software for Stripe Billing layers segmentation, communication sequences, and ERP reconciliation on top of Stripe's native Smart Retries and automatic card updater. Stripe's built-in retry logic recovers a baseline percentage of failed payments, but growth-stage B2B SaaS teams typically reach 70–80% recovery only when they add a collections automation platform that personalizes follow-ups by account value and health, escalates exceptions to humans via Slack, and writes outcomes back to NetSuite, Sage Intacct, or Xero. Platforms like LedgerUp, Tesorio, and Kolleno fit this profile; see our collections automation comparison for a side-by-side view.

How many dunning emails should you send before escalating?

Send 3–5 dunning emails over the first 30 days before escalating to human outreach or formal collections. A typical cadence includes an immediate failure notification, a soft follow-up around day 3–5, a firmer email from a real sender at day 7, an escalation email at day 14, and a final notice before day 30 — with specific timing and sender adjusted based on account value, customer health score, and tenure.

What is the difference between soft and hard declines in payment retry logic?

Soft declines are temporary payment failures (insufficient funds, bank timeout, processing errors) that should be retried after 24–72 hours, while hard declines are permanent failures (stolen card, closed account, invalid card number) that should not be retried at all. Good dunning automation reads the decline code returned by the payment processor and routes accordingly — retrying hard declines wastes processing capacity and can trigger fraud flags with your payment gateway.

How does dunning connect to contract-to-cash automation?

Dunning connects to contract-to-cash automation as the recovery step between invoice generation and cash application, informed upstream by contract terms (Net terms, grace periods, late fee clauses) and closed downstream by ERP reconciliation (applying recovered payments to the correct open invoice in NetSuite, Sage Intacct, or Xero). Treating dunning as a standalone workflow creates reconciliation debt; treating it as one step inside contract-to-cash means every recovered payment traces back to the signed agreement and lands in the right ledger automatically.

Ready to automate your contract-to-cash workflow end-to-end? LedgerUp's AI agent Ari reads signed contracts, generates invoices, runs intelligent dunning, and reconciles payments across Stripe, NetSuite, Sage Intacct, QuickBooks, and Xero — deployed in 1–2 weeks.

‍Book a LedgerUp demo