What is dunning in accounts receivable?
Dunning is the process of sending escalating reminders to collect on overdue invoices. Here is how the process works, the stages it moves through, and best practices.
Dunning is the process of sending customers a sequence of reminders to collect payment on overdue invoices. The reminders escalate in tone as the invoice ages, starting with a friendly nudge and ending, if needed, with a final notice before the account moves to a person or a collection agency.
The word comes from an old term for demanding payment, but the modern practice is less about demanding and more about structured, polite persistence. Done well, dunning gets most invoices paid early with a light touch, so only the genuinely stuck accounts ever reach a stern message. Done badly, it is either too quiet to recover cash or so aggressive it damages the customer relationship.
How the dunning process works
Dunning starts the moment an invoice is sent and follows it through to payment. The collector, or the system standing in for one, watches each invoice against its due date and sends the right message at the right age.
The mechanics are simple. Identify which invoices are approaching or past due. Send a reminder that names the exact invoice, the amount, and the due date, with a clear way to pay. Wait a set number of days. If the invoice is still open, send a firmer message. Repeat until the customer pays, raises a dispute, or the balance crosses a threshold that warrants a personal call.
The hard part is doing this consistently across a full ledger. A team chasing hundreds of invoices by hand will always let some slip, usually the mid-size ones that are too small to feel urgent and too large to ignore.
Dunning stages and cadence
Most teams run a four-stage cadence tied to net-30 terms. Adjust the spacing to your own terms and to how a given customer usually pays.
- Due-date reminder. Sent a few days before or on the due date. Assumes the customer simply has not paid yet. Friendly and short.
- First overdue notice. Sent three to five days past due. Notes the invoice is now late, with a payment link front and center.
- Escalation notice. Sent 15 to 30 days past due. Firmer, names the days overdue, and invites the customer to set up a payment date if they cannot pay in full.
- Final notice. Sent 45 to 60 days past due. States what happens next, such as a credit hold or escalation to collections, if the balance stays open.
The cadence is a default, not a rule. A reliable customer who is two days late needs a softer touch than a serial offender at the same age. The whole point of escalation is to match firmness to risk.
Dunning best practices
A few habits separate a sequence that recovers cash from one that just fills an inbox.
- Name the specifics every time. The exact invoice number, amount, and due date. Vague reminders get ignored.
- Make paying effortless. Put a payment link in every message. Attach the invoice or statement so the customer cannot stall on "send me a copy."
- Escalate tone, not volume. More email does not collect more cash. A controlled rise in firmness does.
- Pause on a dispute or promise. The moment a customer raises an issue or commits to a date, stop the automated chase and route them to a person. Sending a final notice to someone who already promised to pay Friday destroys trust.
- Pick the channel the customer reads. Email is the default, but a text or a call lands faster for some accounts. Match the channel to the relationship.
Manual vs automated dunning
Manual dunning relies on a collector to remember every invoice, decide when to chase it, and write each message. It does not scale. As the ledger grows, the team triages to the largest balances and the rest age quietly.
Automated dunning fixes the consistency problem by running the reminders on a schedule. Every invoice gets chased at the right age, regardless of size. The limit is that most automation is rigid. It fires the same template at the same interval whether the customer is a first-time late payer or a chronic one, and it cannot read a reply.
The next step past rigid schedules is outreach that adapts per account. Instead of one fixed cadence, the timing, tone, and channel flex to how each customer actually behaves and pays.
How Rex handles dunning
Rex runs dunning as an agent, not a scheduler. It watches every invoice across the ledger, decides the right moment to reach out, and chooses the tone and channel that fit each account based on its history and risk. When a customer replies with a question, a dispute, or a promise to pay, Rex reads it, acts on it, and pauses the chase, so nobody gets a final notice they did not earn.
That means the routine follow-up runs itself continuously, and a person only sees the accounts that genuinely need a human decision. See how Rex runs collections end to end.
Frequently asked questions
- What does dunning mean in accounts receivable?
- Dunning is the process of communicating with customers to collect payment on overdue invoices. It usually runs as a series of reminders that grow firmer in tone as an invoice ages, from a friendly nudge near the due date to a final notice before escalation.
- What are the stages of dunning?
- A typical dunning cycle has four stages: a pre-due or due-date reminder, a first overdue notice a few days late, an escalation notice around 15 to 30 days past due, and a final notice near 45 to 60 days before the account moves to a person or collections.
- What is the difference between manual and automated dunning?
- Manual dunning means a collector decides when to chase each invoice and writes each message by hand. Automated dunning runs the reminders on a schedule. Agentic dunning goes further and decides the timing, tone, and channel per account, then acts on replies on its own.