Dunning

Dunning is the escalating sequence of reminders a business sends a customer about an overdue invoice: a routine nudge first, a firmer notice next, and a final warning if neither lands. What makes dunning dunning, rather than just a collections email, is the escalation itself. One reminder sent once is a nudge. A planned sequence that gets firmer in tone and more specific in consequence as a balance ages is dunning.

The word carries German roots (mahnung, a warning) and the practice is older than the software built to run it, but the mechanics haven't changed: match the message to how overdue the invoice actually is, and don't send the same soft reminder to an account that's ninety days past due that you'd send to one that's five.

The dunning levels: how the escalation actually works

A dunning sequence typically runs three or four levels, each tied to how far the invoice has aged past terms:

• Level 1, the friendly reminder. Sent a few days before or just after the due date. Assumes the invoice was overlooked, not disputed. Tone is informational, not urgent.
• Level 2, the firm reminder. Sent once an invoice has aged into a company's middle aging buckets, typically 30 to 60 days past due. States the amount, references the original invoice, and asks for a specific response: payment, a payment date, or an explanation.
• Level 3, the final notice. Sent once an invoice has aged into the oldest buckets. States the consequence plainly: a credit hold, a referral to collections, or both, by a stated date.
• Level 4, escalation out of dunning. Once automated or semi-automated dunning stops working, the account moves to a direct collections call, a credit hold, or a write-off decision, each a judgment call rather than a scheduled send.

Skipping a level doesn't make collection faster. A level-3 final notice sent to a customer who never received a level-1 reminder reads as disproportionate and often triggers a dispute instead of a payment, which adds a cycle to the very aging the dunning sequence was supposed to shorten.

Dunning and the accounts receivable aging: the cadence follows the buckets

Dunning without the accounts receivable aging behind it is just a mail-merge. The aging is what tells a dunning sequence which level an invoice has earned: an invoice sitting in the current bucket shouldn't receive a level-2 notice, and one that's drifted into the 90-plus bucket shouldn't still be getting a friendly nudge. Every dunning cadence is only as accurate as the aging driving it.

This is also why dunning breaks quietly when the aging is wrong. An invoice that's actually been paid but shows open because the payment sits unapplied, see cash application for how that matching works, gets dunned anyway, and a customer who already paid receiving a collections notice is one of the fastest ways to damage a relationship a dunning sequence was supposed to protect. Clean cash application isn't a nice-to-have upstream of dunning. It's a precondition.

What a dunning letter actually needs to say

A dunning notice that works states four things plainly: the specific invoice number and amount, how many days past the due date it sits, what response is being asked for, and what happens next if nothing changes. A generic "your account is past due" notice with no invoice detail forces the customer to go find the invoice themselves before they can even act, which slows the exact response the dunning sequence exists to speed up.

Tone matters as much as content, and it should shift deliberately across the dunning levels rather than starting firm and staying there. A level-1 reminder that reads like a threat trains customers to argue with every nudge, which defeats the purpose of having levels at all.

Dunning vs. collections: where one ends and the other begins

Dunning is the scheduled, templated part of the process: reminders that escalate on a cadence, built from the aging, sent without much case-by-case judgment. Collections is what happens once dunning stops working: a phone call, a negotiated payment plan, a credit hold, or a write-off decision, each requiring a person to weigh a specific customer's circumstances rather than apply a template. A dunning sequence that routes every unresolved account straight to a human collections queue once it exhausts its levels is doing its job; one that just repeats the final notice indefinitely has stopped being useful and started being noise.

Why dunning still needs a human send gate

A dunning sequence is the part of accounts receivable most exposed to a customer directly, which makes an unreviewed send the riskiest kind of automation to run. A reminder drafted against stale aging data, sent to the wrong contact, or escalated past a strategic account's actual relationship can cost more in goodwill than the invoice is worth. The discipline that holds regardless of who or what drafts the message: nothing goes out under a company's name without a human reviewing it first, at least until a segment has proven itself safe to run on its own cadence.

Related terms: Accounts Receivable Aging, Cash Application, Days Sales Outstanding (DSO)

Related skill: Collections Dunning Drafts

Go deeper: Accounts Receivable Automation

Building the right dunning level for every open invoice, every cycle, depends on the aging being current and the cadence actually running on schedule, which is exactly the work that slips first when a team is stretched thin. Adopt's agents keep the receivables aging current and draft the next dunning reminder against it, escalating by bucket and customer history instead of waiting for someone to find the hour. Collection calls, credit holds, and write-off decisions stay with your team. Nothing reaches a customer and nothing posts without a reviewer's sign-off. Sign up free.