Skip to main content

How do I automate dunning and collections reminders?

Schedule reminders relative to the due date (a few days before, then at set intervals after), with escalating tone and channel, and add a suppression check before each send confirming the invoice is still genuinely open and undisputed. Most accounting systems support scheduling this natively; the suppression check is what prevents the most damaging automation failure.

Zuny FesterBy Zuny Fester, Head of Operations and Marketing
Reviewed by Zuny Fester
Published Last reviewed Editorial policy

Part of the accounts receivable and collections guide.

Typical scheduleA reminder before the due date, then escalating reminders after
What escalatesTone, channel, and sometimes who the message comes from
Critical safeguardConfirm the invoice is still open and undisputed before each send
Where this often lives nativelyMost accounting systems' invoicing settings

Setting up the schedule

A typical dunning sequence starts with a friendly reminder a few days before the due date, followed by a firmer reminder shortly after it's overdue, and escalating further at set intervals (7, 14, 30 days past due, for example) with increasingly direct language and sometimes a change in who the message appears to come from — moving from an automated system email to a message from an account manager.

Why the suppression check matters more than the schedule

A well-designed schedule is worthless if a reminder fires on an invoice that's already been paid or disputed. Before each scheduled send, confirm at that moment — not when the sequence was originally scheduled — that the invoice is still open, that no payment has posted even if not yet applied, and that no dispute or support ticket is linked to it. This single check is what prevents the most common and most damaging automation failure in collections.

Next step

Map the finance workflow with the most exposure and prove the automation path.

Bring the invoice, contract, payment reconciliation, or customer finance workflow you have to defend at audit. Loopfour can map the trigger, controls, integrations, and approval loop.

Book a workflow review

Checklist

Setting up an automated dunning sequence

  • Schedule a reminder before the due date
  • Escalate tone and interval after the due date passes
  • Check invoice status immediately before every send, not just at scheduling time
  • Suppress the sequence if a dispute or support ticket is linked to the account

Frequently Asked Questions

Weight by a combination of dollar amount, days overdue, and known customer risk signals — the largest, oldest, or highest-risk accounts generally warrant manual attention first.

Often yes — a large strategic account may warrant a more personal message earlier in the sequence than a standard automated one used for smaller accounts.

Commonly two to three automated reminders before a person gets involved, though this varies by account size and relationship importance.

Sources

Related