AR & collections

Dunning Emails That Get Invoices Paid: Sequence and Templates

The tone that gets an invoice paid changes depending on where you are in the sequence — and most teams only ever write one version.

Nitisha GubreleyFounder & CEO, Vyomiyra2 min read

Dunning is the structured, escalating sequence of payment reminders sent as an invoice moves from upcoming to due to overdue. Most teams write one reminder email and send a version of it every time, regardless of how overdue the invoice actually is. That undersells the tool — a reminder sent three days before an invoice is due should read nothing like a notice sent forty-five days after it.

A working sequence

  1. 3 days before due — friendly, informational, no pressure. The goal is just to make sure the invoice didn't get lost.
  2. On the due date — a straightforward reminder that today is the day, still low-pressure.
  3. 7 days overdue — a clear reminder that the invoice is now past due, with the amount and a direct payment link restated.
  4. 15–30 days overdue — firmer in tone, may reference next steps if payment isn't received, and often copies the account owner or a manager.
  5. 30+ days overdue — a final notice before escalation to a call, a collections process, or involving account management directly.

Example: early reminder (3 days before due)

Subject: Invoice #1042 due in 3 days

Hi [Name], just a quick heads-up that invoice #1042 for $[amount] is due on [date]. You can pay directly here: [link]. Let me know if anything looks off or if you need anything from us to process it. Thanks!

Example: firm overdue notice (30+ days)

Subject: Invoice #1042 — now 32 days overdue

Hi [Name], invoice #1042 for $[amount], originally due [date], is now 32 days past due. We haven't received payment or heard back on the earlier reminders. Please arrange payment by [date] using this link: [link]. If there's an issue on your end, reply directly and we'll sort it out — otherwise we'll need to escalate this internally.

What makes a dunning sequence actually work

  • Every email restates the invoice number, amount, and due date — never make someone dig for the details.
  • Always include a direct payment link. A reminder that requires a manual bank transfer converts far slower than one with a one-click option.
  • Escalate tone gradually, not all at once — jumping straight to a firm notice on day one damages relationships with customers who were simply going to pay on time anyway.
  • Know when to pick up the phone instead of sending another email — past a certain point in the sequence, a call gets a response an email won't.

How Vyomiyra helps

Vyomiyra drafts the right stage of the sequence automatically based on where an invoice sits in its aging, so nothing slips through because someone forgot to send the day-30 reminder. The AR team reviews and sends — and decides exactly when an account needs a call instead of another email.

More on this topic

How to Read an AR Aging Report (With Examples)

An aging report turns "customers owe us money" into exactly who, how much, and how urgently it needs attention.

How to Calculate Days Sales Outstanding (DSO) and Why It Matters for Cash Flow

DSO is the single number that turns "we're profitable on paper" into "we actually have the cash."

Related pages

Collections Automation

Learn how finance teams can improve collections cadence, prioritisation, and follow-up tracking.

Accounts Receivable Automation

See how AR teams can structure collections follow-up and receivables workflows.

Collections Automation for AR Teams

Focus on prioritisation, follow-up throughput, and collections visibility for AR teams.

See how Vyomiyra structures this workflow.

Book a demo or start the free trial to evaluate AP, AR, approvals, and audit-ready workflow execution on real finance work.