The challenge isn’t knowing dunning matters. It’s designing a cadence firm enough to get paid without damaging customer relationships, then executing it consistently at scale. Transformance automates this through CollectPulse, running email sequences and AI-powered collection calls autonomously so your team focuses on the escalations that require real judgment.
Key Takeaways
- Effective dunning requires a tiered cadence with tone that escalates gradually across delinquency buckets
- Manual AR teams often leave a significant share of overdue accounts uncontacted in any given week. Automation is designed to close that gap to full coverage
- Six ready-to-use email templates cover the full arc: from pre-due reminder to final demand
- The automation rule: systematize the first two or three touches, apply human judgment at the escalation stage
- Based on Transformance deployment data, consistent dunning coverage can reduce DSO by 8-15 days within 90 days
In This Article
- What Is the Dunning Process?
- How to Design a Dunning Cadence
- 6 Dunning Email Templates by Delinquency Bucket
- How Does Dunning Automation Change the Equation?
- What Should You Automate vs. Handle Manually?
- Dunning Metrics That Actually Matter
What Is the Dunning Process?
What Is Dunning?
Dunning is the systematic process of contacting customers with overdue invoices to secure payment. It runs as a tiered sequence: friendly reminders early, firmer written notices mid-cycle, and formal escalation (credit holds, demand letters, or collections referral) for accounts that don’t respond.
The term comes from 17th-century English slang: a “dun” was a creditor’s agent who persistently demanded payment. The name stuck. The core idea hasn’t changed.
Modern dunning isn’t about pressure tactics. It’s about consistency. Industry experience consistently shows that companies with a formal, automated dunning cadence collect materially faster than those relying on ad-hoc follow-up. The difference is cadence design and coverage, not collector skill.
How to Design a Dunning Cadence
A dunning cadence defines how many times you contact a customer, through which channels, and at what tone. Most finance teams design this informally, which is why coverage is inconsistent. A deliberate approach defines the stages before the first invoice goes overdue.
Step 1: Define Your Delinquency Buckets
Group invoices by age. A standard four-bucket structure for B2B AR:
- Pre-due (Day -3 to Day 0): Optional reminder before the due date. Highly effective for first-time or infrequent payers.
- Early (Day 1-15 past due): Friendly reminders. Assume administrative delay, not intent to avoid payment.
- Mid (Day 16-45 past due): Firm notices. Tone shifts to professional urgency. Reference credit terms explicitly.
- Late/Escalation (Day 46+ past due): Escalate to credit holds, legal review, or agency referral based on customer tier and invoice value.
Step 2: Set Contact Frequency and Channels
A workable baseline for most B2B AR teams:
- Day -3: Pre-due email
- Day 1: First reminder email
- Day 7: Second email
- Day 15: Third email (firm tone)
- Day 21: Phone call or AI collection call
- Day 30: Written notice
- Day 45: Final demand with escalation notice
Adjust frequency up for high-value accounts and calibrate down for strategic customers where relationship preservation matters more than collection speed.
Step 3: Apply Tone Laddering
Tone laddering is where most teams go wrong. Staying too friendly too long lets payments slip. Escalating too fast creates disputes and damages relationships. The right approach: professional courtesy through day 14, professional firmness through day 30, formal demand after.
Step 4: Define Escalation Rules
Escalation rules should be automatic, not left to individual discretion:
- Route invoices above a defined threshold (for example, over $10,000) to a human collector at day 21, regardless of email response status
- Trigger a credit hold review at day 45 for any open balance
- Flag disputed invoices immediately and remove them from the standard dunning cadence; route to a dedicated dispute workflow instead
For accounts where the dispute involves trade deductions or pricing claims, understanding what deductions management involves helps clarify which cases belong in a dispute track versus a standard payment follow-up.
6 Dunning Email Templates by Delinquency Bucket
Copy and adapt the templates below. Bracketed fields are placeholders for your invoice data and company details. Tone escalates deliberately across the six stages.
Template 1: Pre-Due Reminder (Day -3)
Subject: Friendly reminder: Invoice [INV-####] due [Due Date]
Hi [First Name],
Just a quick note that Invoice [INV-####] for [Amount] is due on [Due Date]. Please let us know if you have any questions or need the invoice resent.
Thank you,[Your Name][Company] | Accounts Receivable
Template 2: First Reminder (Day 1-3 Past Due)
Subject: Invoice [INV-####] is now past due
Hi [First Name],
Invoice [INV-####] for [Amount] was due on [Due Date] and doesn’t appear to have been settled yet. If payment has already been sent, please disregard this message.
If not, a quick update on expected timing would be appreciated. You can reach us at [email] or [phone].
Thank you,[Your Name][Company] | Accounts Receivable
Template 3: Second Notice (Day 8-14 Past Due)
Subject: Second notice: Invoice [INV-####] outstanding [X] days
Hi [First Name],
We’re following up on Invoice [INV-####] for [Amount], now [X] days overdue. We haven’t received payment or a response to our earlier message.
Please confirm payment status or let us know if there’s a question about this invoice. Continued delay may affect your credit terms with us.
[Your Name][Company] | Accounts Receivable
Template 4: Firm Notice (Day 15-30 Past Due)
Subject: Urgent: Invoice [INV-####] requires immediate attention
Dear [First Name],
Invoice [INV-####] for [Amount] is now [X] days past due. This is our [X]th attempt to contact you about this balance.
Per our agreed payment terms, we require payment by [Response Deadline] to avoid a formal escalation, which may include a credit hold or referral to our collections team. Please contact us immediately to arrange payment or flag any dispute.
[Your Name][Company] | Accounts Receivable[Direct contact]
Template 5: Escalation Notice (Day 31-45 Past Due)
Subject: Final notice before escalation: Invoice [INV-####]
Dear [First Name],
Despite multiple attempts to contact you, Invoice [INV-####] for [Amount] remains unpaid at [X] days past due.
Effective immediately, your account has been placed on credit hold. No new orders will be processed until this balance is resolved. If we do not receive payment or a written payment proposal by [Response Deadline], this balance will be referred to [our legal team / a third-party collections agency].
To resolve this matter, contact [Name] at [email/phone] today.
[Your Name][Company] | Accounts Receivable
Template 6: Final Demand (Day 46+)
Subject: Final demand: Invoice [INV-####], [Amount] outstanding
Dear [First Name],
This is a formal final demand for payment of Invoice [INV-####] in the amount of [Amount], now [X] days outstanding.
This balance will be forwarded to [our legal counsel / a collections agency] on [Response Deadline] if full payment or a signed payment plan is not received by that deadline. Additional recovery costs may be added.
To avoid further action, contact [Name] at [email/phone] immediately.
[Your Name][Company] | Accounts Receivable
Review Templates 5 and 6 with your legal team before use. Language requirements for formal demand letters vary by jurisdiction.
How Does Dunning Automation Change the Equation?
Manual dunning has a coverage problem. Finance teams relying on manual follow-up commonly leave a large share of overdue accounts uncontacted in any given week. The rest sit untouched because collectors prioritize by memory or by whichever accounts called in that morning.
Automation solves coverage first. Every invoice is actioned within 24 hours of becoming overdue. Emails go out on schedule, calls trigger at the right delinquency stage, and nothing slips because a collector was traveling or tied up with an escalation.
The second benefit is consistency. Manual teams vary tone and timing based on whoever is running the queue that day. Good dunning software standardizes the cadence: the right message, the right tone, the right timing, for every account, every cycle.
Transformance handles this through CollectPulse, which runs automated email sequences alongside an AI calling agent (Vero) designed to contact overdue accounts across 70+ languages, captures promise-to-pay dates, and writes outcomes back to the system automatically. A three-person shared services team can run cross-border dunning in French, Spanish, and Italian simultaneously, without adding native-speaker headcount.
For a closer look at how AI agents handle the full payment-to-posting workflow, see agentic AI for cash application: from remittance to GL posting.
What Should You Automate vs. Handle Manually?
Not every overdue account belongs in a fully automated dunning queue. The right split depends on invoice value, customer tier, and dispute likelihood.
Automate first:
- All invoices below a defined threshold (for example, under $5,000) through the full email cadence
- Day 1 and Day 7 reminders across all accounts, regardless of value
- Promise-to-pay tracking and verification follow-ups
- Early-stage dunning for accounts with no prior dispute history
Keep human in the loop:
- Invoices above your threshold at the escalation stage
- Accounts with open disputes or claims in progress (separate dispute workflow, not dunning cadence)
- Strategic customers where the commercial relationship requires direct human contact
- Accounts approaching credit limit violations that need cross-functional input
The rule of thumb: automate the first two or three touches for every account, then apply human judgment at the escalation point. Collectors spend their time on negotiations that matter, not on leaving voicemails for $800 invoices.
Dunning Metrics That Actually Matter
Tracking the right numbers tells you whether your cadence is working or just generating activity.
Days Sales Outstanding (DSO): The primary metric. DSO measures the average number of days to collect payment after a sale. A falling DSO confirms your dunning is working; a rising DSO signals that cadence timing, tone, or coverage needs adjustment. Based on Transformance deployment data across its customer base, consistent automation coverage is designed to deliver DSO reductions of 8-15 days within 90 days. For context on how DSO fits the broader collections picture, see what order-to-cash means and 10 AI use cases reshaping it.
Collection Effectiveness Index (CEI): Measures the percentage of receivables successfully collected in a period. A CEI above 80% is generally considered strong for B2B. Below 70% indicates a cadence or coverage problem worth diagnosing before adding headcount.
Promise-to-Pay Capture Rate: The percentage of outbound contacts resulting in a committed payment date. If your rate is below 30%, your messaging isn’t prompting a response. Try leading the subject line with the specific invoice amount and due date rather than generic account language.
First-Touch Resolution Rate: The percentage of overdue invoices paid after the first dunning contact. High first-touch resolution means your timing is right and your customers are responsive. Low rates suggest the first contact is going out too early or the tone is too soft to prompt action.
Write-Off Rate: The percentage of AR balances written off as uncollectable. Sustained improvement in DSO and CEI typically suppresses write-off rate over time, because consistent dunning catches deteriorating accounts before they age past recovery.
Track these monthly, broken down by customer segment and invoice age bucket. If mid-tier accounts consistently cluster in the 30-60 day bucket while top customers pay on time, that’s a cadence calibration problem, not a staffing one.
Conclusion
A dunning process works when it’s tiered in tone and executed at full coverage. The six templates above cover the full delinquency arc; the cadence design steps give you a structure to run them consistently.
The teams that collect the most aren’t the ones with the most collectors. They’re the ones that automate the first three touches for every account, apply human judgment at the escalation point, and track the metrics that tell them when the cadence needs adjustment.
Frequently Asked Questions
What is a dunning letter?
A dunning letter is a formal written notice sent to a customer with an overdue invoice requesting payment. It typically includes the invoice number, amount due, original due date, and a deadline for payment before further action is taken. Dunning letters range from polite payment reminders to formal legal demands, depending on how far the invoice has aged past due.
How many dunning emails should you send before escalating?
Most B2B dunning cadences use three to four email contacts before escalating to phone outreach or formal notices. A standard sequence: day 1 reminder, day 7-10 second notice, day 15-21 firm notice, then escalation from day 30 onward. Adjust timing to match your payment terms and average customer payment cycle.
What is the difference between a dunning notice and a collections notice?
A dunning notice is a standard AR follow-up sent by your team as part of a routine payment cadence. A collections notice is a formal legal or agency document issued when standard dunning has failed, typically signaling imminent referral to a third party or legal action.
What should dunning automation software do?
Good dunning software sends tiered email sequences, triggers calls at defined delinquency thresholds, captures and tracks promise-to-pay commitments, escalates based on rules rather than manual routing, and reports on coverage rates, contact rates, and DSO impact. Integration with your ERP ensures dunning status always reflects current payment data, not a stale snapshot.
How do you handle disputed invoices in a dunning cadence?
Disputed invoices should exit the standard dunning cadence immediately and route to a separate dispute workflow. Continuing to send dunning emails on a disputed invoice damages the customer relationship without improving recovery odds. Bring the invoice back into the dunning cadence only after the dispute is resolved.
What DSO improvement is realistic from a better dunning process?
Based on Transformance deployment data, a consistent, automated dunning cadence with full invoice coverage is designed to reduce DSO by 8-15 days within 90 days. The improvement depends on baseline DSO, customer payment behavior, and the degree to which the previous process relied on manual, ad-hoc follow-up.
