Key Takeaways
- Dunning is the structured collections process of contacting customers through escalating reminders to recover overdue invoices, outstanding receivables, or failed subscription charges before accounts reach formal debt collection.
- The process follows a defined timeline, starting with gentle payment reminders before the due date and escalating through formal notices, phone calls, and legal action over 7 to 60+ days past due.
- Two distinct types exist in practice. B2B invoicing dunning targets overdue trade invoices with multi-channel escalation, while SaaS subscription dunning automates failed card retries and in-app prompts to prevent involuntary churn.
- Manual dunning creates persistent AR blind spots. One global SaaS company running manual payment reminders across six disconnected systems kept DSO at 50 to 60 days, well above SaaS benchmarks, until automating the sequence brought DSO below 30 days.
- Effective dunning balances persistence with legal limits. Federal and state laws restrict contact hours, frequency, language, and disclosure to unauthorized third parties, and penalties apply to businesses and their collection agents alike.
- Automating dunning at the AR layer, not inside the ERP, gives finance teams real-time visibility into at-risk accounts without waiting for the aging report to refresh.
What Is Dunning?
Dunning is the structured business process of contacting customers to collect payment on overdue invoices, outstanding receivables, or failed subscription charges. The process moves through an escalating sequence of reminders, formal notices, and collection actions designed to recover the amount owed while preserving the customer relationship.
In enterprise accounts receivable, dunning sits between routine billing and formal debt collection, and the consistency of the sequence directly affects days sales outstanding (DSO) and cash flow predictability.
How the Dunning Process Works
The dunning process follows a structured, escalating sequence of communications. Each stage increases in urgency as the invoice ages, and the goal at every step is to secure payment while keeping the customer relationship intact.
- Gentle Reminders: Friendly automated emails, SMS messages, or app notifications sent shortly before or after a payment due date passes. These handle the most common cause of late payment: the customer simply forgot or missed the invoice. Most collections management teams start here because a polite nudge resolves the majority of overdue balances without friction.
- Firm Notices: Direct phone calls or formal written demand letters when the balance remains unpaid past the first reminder window. The tone shifts from informational to transactional, clearly stating the amount, the number of days overdue, and any late-fee or credit-term consequences. At this stage, the accounts receivable team may also place a hold on new orders or flag the account for senior review.
- Escalation and Collections: Handover to internal credit teams, external collection agencies, or legal action if all previous attempts fail. This is the last resort, typically triggered 60 to 90+ days past due, and carries real costs: agency fees, legal expenses, and the likely loss of the customer. Effective dunning sequences minimize the number of accounts that reach this stage.
Dunning Process Timeline
A typical enterprise dunning sequence maps specific actions to defined intervals after the invoice due date. The exact timing varies by company policy, industry, and the value of the account, but the structure below is representative of what most order-to-cash teams follow.
The intervals compress or stretch depending on the relationship. A high-value enterprise customer with a 20-year history may get a longer runway and more personal outreach at each stage. A new customer with a small balance and no payment history may move to escalation faster.
The critical operational point is that every step in this timeline needs to happen on schedule, for every overdue invoice, regardless of volume. When the AR team is pulling aging reports manually and drafting individual emails, the sequence breaks down at scale. Invoices slip through, reminders go out late, and the escalation path stalls because no one tracked which account hit the 30-day mark.
Types of Dunning
Dunning takes two distinct forms in practice, and the mechanics differ enough that they need different operational setups.
B2B Invoicing Dunning
This is the traditional form. A company sells goods or services on credit terms (net 30, net 60), and dunning is the process of chasing overdue trade invoices through emails, statements, calls, and escalation. The AR team works from an aging report, and the dunning sequence is typically semi-manual: automated reminders for the first two stages, then personal outreach for anything past 30 days. The complexity scales with the number of customers, entities, and currencies. A manufacturer running 400+ distributors across five systems faces a fundamentally different dunning problem than a SaaS company with 50 enterprise accounts.
SaaS and Subscription Dunning
In recurring billing, dunning handles failed credit card charges, expired cards, and missed billing cycles. The goal is to recover the payment and prevent involuntary churn, which is when a customer loses access not because they wanted to cancel but because a technical payment failure went unresolved. The dunning tools here are automated card retries at optimized intervals, account updater services that refresh expired card details, and in-app or email prompts directing the customer to update their payment method. Stripe, Chargebee, and similar billing platforms handle this natively.
Dunning Best Practices
These are the operational practices that separate effective dunning from one that leaks cash and damages customer relationships.
1. Start before the due date, not after it. The single highest-impact change most AR teams can make is sending a payment reminder 5 to 7 days before the invoice is due. A pre-due reminder catches invoices that were lost in approval queues, misrouted, or sitting in someone's inbox without a PO match. It costs nothing and eliminates a meaningful percentage of "overdue" invoices that were never genuinely late.
2. Segment your dunning sequences by customer risk and value. A blanket escalation path treats a Fortune 500 account with a 15-year payment history the same as a new customer whose first invoice is overdue. Segment by payment history, account value, and credit risk. High-value, low-risk accounts get a longer runway and personal outreach earlier. High-risk, low-value accounts move to automation and earlier escalation. The aging report is the starting point, but it is not the segmentation itself.
3. Use multiple channels, and match the channel to the stage. Email works for reminders. Phone calls work for firm notices and escalation. In-app prompts work for subscription recovery. A dunning sequence that relies on email alone loses effectiveness after the second message because the customer has already trained themselves to ignore it. The shift to a different channel signals that the urgency has changed.
4. Track every touchpoint and keep a clean audit trail. Every reminder sent, every call made, every response received needs to be logged against the invoice and the customer account. Without this, the AR team cannot tell whether a customer was contacted, what was promised, or whether the escalation timeline is on track. The audit trail also protects the business if the account reaches legal action or dispute resolution.
5. Automate the routine, personalize the exceptions. The first two stages of the dunning sequence, pre-due reminders and first overdue notices, should be fully automated for every invoice. No human should be reviewing an aging report to decide whether to send a standard reminder. The human time goes to accounts that did not respond to automated outreach, accounts with partial payments or disputes, and accounts where the commercial relationship requires a phone call rather than a template email.
6. Measure what matters: DSO, not email open rate. The point of dunning is to collect cash faster, not to send more reminders. Track DSO by customer segment, the percentage of invoices paid within terms, the percentage that reach each escalation stage, and the average days to collect by bucket. If automated dunning sends 40% more reminders but DSO stays flat, the sequence is not working. Connect the dunning metrics to the cash flow forecast so the CFO sees the collection pipeline, not just the receivables balance.
7. Define a clear policy and communicate it to customers. The dunning policy, including payment terms, late-fee structure, escalation timeline, and collections referral threshold, should be documented, approved by finance leadership, and communicated to customers during onboarding. A customer who knows that accounts past 45 days are referred to collections is more likely to pay at the 30-day notice than one who assumes late payment has no consequences.
Legal and Compliance Limits on Dunning
Dunning is a lawful business process, but it operates within legal boundaries that restrict how, when, and how often a business can contact a debtor.
In the United States, the Fair Debt Collection Practices Act (FDCPA) governs third-party debt collection and prohibits practices including repeated or excessive contact, threats of violence or arrest, use of obscene or abusive language, misrepresentation of the amount owed, and false claims about legal consequences. Many state laws extend similar protections. Businesses contacting their own customers (first-party dunning) face fewer federal restrictions but are still bound by state consumer-protection laws and by the general prohibition on harassment and deception.
The practical rules for an enterprise AR team:
- Contact only during reasonable hours (typically 8 a.m. to 9 p.m. in the customer's time zone).
- Do not disclose the debt to unauthorized third parties, including the customer's colleagues or family members.
- Stop contact if the debtor sends a written cease-and-desist, except to confirm that contact will stop or to notify of specific legal action.
- Accurately state the amount owed, the creditor's identity, and the debtor's rights.
- Do not threaten action the business does not intend to take (empty legal threats, false credit-reporting warnings).
In India, the Reserve Bank of India's guidelines on recovery agents and the Consumer Protection Act, 2019 set broadly similar limits. Enterprise AR teams operating across multiple countries need jurisdiction-specific policies, which is another argument for automated workflows that enforce the right escalation path by region rather than relying on individual collectors to know the rules.
Why Is It Called Dunning?
The term comes from the 17th-century English verb "to dun," which meant to make insistent, repeated demands on a debtor for payment. At that time, commerce ran on informal credit between merchants and customers, and dunning was a face-to-face process: shopkeepers and tradespeople extended goods on trust, then followed up through personal visits, letters, or messengers when payments lagged. The word likely traces back even further to the Old English "dun," meaning to make a loud noise or clamor, which captures the persistent, hard-to-ignore nature of the process.
The term survived because the process survived. Modern dunning is automated rather than face-to-face, but the core mechanic is identical: structured, escalating persistence aimed at recovering what is owed before the relationship, or the receivable, is written off.
What Is Dunning in SAP?
In SAP ERP (specifically the SAP FI module), dunning is a standard program that identifies customers with overdue invoices and generates payment reminder letters automatically based on configured rules. SAP's dunning process is one of the most commonly asked about in finance interviews and certifications because of how widely SAP runs in large enterprises.
The key SAP dunning transaction codes:
- F150 (Dunning Run): The main transaction. Selects overdue items based on dunning area, customer, and company code, calculates the dunning level for each item, and generates the dunning notices.
- FBMP (Dunning Procedure Configuration): Defines the dunning procedures, levels, intervals, and texts. Most enterprises configure 3 to 4 dunning levels with escalating urgency.
- FBL5N (Customer Line Item Display): Used to review individual customer open items and their dunning status, which shows how many dunning notices have been sent and the current dunning level.
The limitation of SAP's native dunning is that it operates inside the ERP's own data. If payment data, banking data, or collection notes live in other systems, and in most enterprises they do, the dunning run has an incomplete picture. An account may show as 30 days overdue in SAP while a payment is already in transit through a gateway, or a credit note is pending approval in a separate workflow. This gap between ERP-native dunning and the full receivables picture is what drives many finance automation investments.
Why Dunning Controls Matter in Accounts Receivable
Dunning is not just an operational convenience. It is a control point in the order-to-cash cycle that directly determines how much cash is tied up in receivables and how quickly the business can convert revenue into working capital.
The cost of weak dunning controls is concrete. When reminders go out late or inconsistently, overdue balances age into the 60-day and 90-day buckets where recovery rates drop sharply. When there is no unified view of which customers have been contacted, on which invoices, through which channels, collectors duplicate effort on some accounts and miss others entirely. When dunning data is scattered across the ERP, a CRM, email inboxes, and spreadsheets, the CFO's receivables report shows a number but not the story behind it.
A global cloud HCM provider operating across 130+ countries ran into exactly this pattern. Finance data sat in six disconnected systems, including an ERP, two accounting platforms, two CRMs, and a billing system, with no common receivables view. Manual payment reminders kept collection effectiveness below 80%, and DSO hovered at 50 to 60 days, well above SaaS benchmarks. The issue was not that the team was not working hard. It was that no one could see, in real time, which accounts were at risk across all six systems simultaneously.
After unifying the data behind a single AR dashboard and replacing manual reminders with automated, geography-specific dunning sequences, DSO dropped below 30 days. At-risk accounts fell by 75%, and manual AR effort dropped by 80%. The team shifted from chasing invoices to managing exceptions.
The lesson is consistent across industries: dunning controls need to sit above the ERP, not inside it, because the data that determines whether an invoice is genuinely overdue lives across multiple systems that the ERP cannot see.
How to Automate Dunning
Manual dunning, where someone reviews an aging report, drafts individual emails, and tracks follow-ups in a spreadsheet, works when the AR book is small. It breaks at scale. The failure mode is not dramatic. It is quiet: reminders go out a few days late, escalation timelines slip, and invoices that should have been collected at 15 days end up in the 45-day bucket where recovery costs more and takes longer.
Automating dunning means three things in practice:
1. Automated trigger and send. The system monitors open invoices against their due dates and sends the right message at the right time for every invoice, on the schedule defined in the dunning policy. No manual review of the aging report, no individual email drafting, no risk that an invoice falls between the cracks during month-end when the team is busy with close tasks.
2. Real-time at-risk account identification. Instead of discovering overdue accounts when the aging report refreshes, the system flags accounts moving toward the next escalation stage in real time. This gives the collections team a head start on the accounts that will need personal outreach, and it gives the CFO a rolling view of the receivables pipeline. Bluecopa's AI-native Samyx Recon engine handles this across banks, ERPs, and gateways simultaneously, matching payments to invoices as they arrive rather than in batch.
3. Geography and policy-specific sequences. Enterprises operating across multiple countries need dunning sequences that respect local legal limits, language, time zones, and escalation thresholds. A single global template does not work when India, the Philippines, Singapore, and South Africa each have different contact-hour rules and consumer-protection frameworks. Automated workflow rules route each account through the correct sequence based on its jurisdiction, customer segment, and account value.
For teams evaluating dunning automation tools specifically, we reviewed the category in detail: 9 Best Dunning Automation Software Platforms for 2026.
Frequently Asked Questions
1. What is the main purpose of dunning in accounts receivable?
Dunning exists to collect overdue payments through structured, escalating reminders before the account reaches formal debt collection, protecting both cash flow and the customer relationship.
2. What is meant by dunning in SAP?
In SAP, dunning is the automated program (transaction F150) that selects overdue customer invoices, calculates the dunning level based on configured procedures, and generates payment reminder letters.
3. Why is it called dunning?
The term comes from the 17th-century English verb "to dun," meaning to make insistent, repeated demands on a debtor for payment, likely from the Old English word for making a loud noise.
4. What is the difference between dunning and collections?
Dunning is the internal reminder and escalation sequence a business runs before an account is overdue enough to require formal action. Collections is the later stage involving third-party agencies or legal proceedings.
5. How many dunning levels should an enterprise configure?
Most enterprises use three to four levels, starting with a friendly reminder and escalating to a formal demand letter, with the interval between levels typically ranging from 7 to 15 days depending on customer segment and account value.
6. Can dunning reduce DSO?
Yes. Consistent, automated dunning sequences directly reduce days sales outstanding by collecting invoices faster. One enterprise reduced DSO from 50 to 60 days to below 30 days after automating geography-specific dunning across 130+ countries.

Book a demo
See Bluecopa run on your own close
70%
Faster month-end close
95%
Reduction in manual effort
100%
Data accuracy
30 min · your ERP · no slide deck







