The Dunning Process: How It Works and When to Escalate

What Is the Dunning Process?

The dunning process is the structured sequence of communications a business sends to collect payment on overdue invoices. It typically starts with a soft reminder shortly after the due date passes and escalates through progressively firmer outreach until the account pays, disputes the invoice, or gets referred to collections or legal.

The word "dunning" comes from 17th-century English slang for persistent debt collection. The mechanics have changed. The underlying problem has not: customers who don't pay on time require a defined, repeatable process to move them from overdue to paid without damaging the relationship unnecessarily or writing off recoverable balances.

How the Dunning Process Works

A well-designed dunning process has four components: a trigger, a cadence, defined escalation thresholds, and an exit condition.

The trigger is the day the invoice goes past due. Some teams add a grace period of one to three days before the first outreach. That's fine for long-standing customers. For new accounts or accounts with a history of slow payment, start on day one.

The cadence is how often you reach out and through which channels. Email is the default. Phone calls should enter the sequence by day 14 at the latest. Waiting past 21 days to make a phone call gives slow payers too much runway and signals that your process has no teeth.

Escalation thresholds define what changes at each stage — who owns the account, what authority they have, and what actions are on the table. A credit analyst sending reminder emails is stage one. A credit manager calling and flagging the account for hold review is stage three. A collections referral is stage five. Without defined thresholds, "escalation" is just louder emails.

The exit condition is when you stop dunning and take a different action entirely. Most credit teams are fuzzy on this. Define it before you need it: after X days past due with no response, the account goes on credit hold and gets referred to formal collections or outside counsel. Vague escalation that never arrives at a consequence trains customers that your process has no real endpoint.

A Standard Dunning Process Timeline

These intervals are starting points, not rules. A $500 invoice from a customer with a 10-year payment history warrants more patience than a $50,000 first order from a new account with no payment track record. Calibrate the timeline to account risk, not just invoice age.

Dunning Process vs. Dunning Letter

A dunning letter is one output of the dunning process — a specific written communication at a specific stage. The process is the full system: who does what, when, through which channel, and what happens next. Focusing only on the letters is why most dunning programs underperform. The letter quality matters less than the consistency of the process around it.

Where Dunning Processes Break Down

Most credit teams know what a dunning process should look like. Few have one that actually runs consistently. The failure modes are predictable.

No defined ownership at each stage. The credit analyst sends the first two emails. After that, it's unclear who follows up, so no one does. The account ages into the 60+ day bucket without anyone making a phone call.

Sales interference. A sales rep asks the credit team to hold off on dunning because they're working on a renewal or upsell. The account stretches to 90 days. The renewal doesn't close. The credit team is left chasing a large balance they were discouraged from pursuing earlier. Define the policy in advance: sales can request a pause of X days maximum, once, with credit manager approval. No verbal holds.

Disputes buried in the process. The dunning sequence keeps firing on an invoice the customer has formally disputed. They stop responding to all outreach because they've told you once that the invoice is wrong. Disputes need to exit the dunning queue and enter a separate resolution track immediately. Mixing the two generates noise and burns credibility.

No consequence at the end. The process says "60 days: refer to collections" but that step rarely happens because it feels like giving up or damaging the relationship. If your exit condition is consistently skipped, it isn't an exit condition — it's a formality. Collections referrals on accounts past 90 days with no response are not a relationship risk. The relationship is already gone.

Automated Dunning: What It Solves and What It Doesn't

HighRadius and Bectran both automate dunning sequences — scheduled emails, workflow triggers, templated escalation. This solves the consistency problem. It does not solve the dispute detection problem, the ownership problem, or the consequence problem. Automation that fires on disputed invoices or accounts in active sales conversations creates more noise than a manual process would.

The right use of automation in dunning: handle stages one through three mechanically, then hand off to a human for stages four and beyond. The early emails are template work. The phone call, the credit hold decision, the demand letter — those require judgment about the specific account and relationship.

The Monitoring Problem Dunning Doesn't Fix

A dunning process manages accounts that have already gone past due. It doesn't prevent them from going past due in the first place.

The credit teams with the lowest DSO aren't just better at dunning — they're better at catching payment behavior changes before the invoice ages. A customer who historically pays in 22 days and starts stretching to 35 is showing a signal. That signal is visible in real-time credit monitoring weeks before the invoice appears in the 30-day aging bucket.

The dunning process is a symptom management tool. Monitoring is the prevention layer. You need both, but teams that invest only in dunning will always be reacting to problems that better monitoring would have surfaced earlier.

See the full accounts receivable collections guide for what happens after the dunning process ends and the account moves to formal collections.

Frequently Asked Questions

What is the dunning process in accounts receivable?

The dunning process is the structured sequence of communications AR and credit teams use to collect overdue invoices. It starts with reminders shortly after the due date and escalates through firmer outreach, account holds, and eventually collections referral if payment is not received.

How many dunning attempts should you make before referring to collections?

Most credit policies define a referral point at 60 to 90 days past due after multiple unanswered contacts. The right number depends on invoice size, customer history, and account value. The more important rule: define the threshold in your credit policy and enforce it consistently rather than extending indefinitely to avoid a difficult conversation.

What's the difference between dunning and collections?

Dunning is the internal process of contacting customers directly to request payment. Collections is the formal process of recovering debt through a third-party agency or legal action when internal efforts have failed. Dunning comes first; collections is the exit condition when dunning doesn't work.

Should you automate the dunning process?

Automate the early stages (reminder emails, scheduled follow-ups). Keep humans involved from the escalation stage onward. Fully automated dunning that runs without dispute detection or sales coordination creates relationship damage without improving recovery rates on the accounts that actually need attention.