Dunning

7 collections email templates that get invoices paid

Seven copy-ready templates for every stage of overdue, from friendly pre-due reminders to final notice, with subject lines and sending logic.

Most collections emails fail for structural reasons, not tone reasons.

They arrive without the invoice number. They ask for payment without saying how. They read like a form letter, so the customer treats them like one. Or they go out three weeks late because nobody owned the follow-up.

The templates below fix the structure. Each one follows an escalation logic: start light and factual, get more direct as the balance ages, and change the channel or the sender when email alone stops working. Copy them, fill in the brackets, and adjust the firmness to fit the relationship.

What makes a collections email work

Before the templates, the five rules they all follow:

  • Lead with facts: invoice number, amount, due date, days overdue. The customer should never have to ask which invoice you mean.
  • Make exactly one ask per email. Pay, confirm a date, or explain the holdup. Not all three.
  • Make paying easy. Include the payment link, portal, or remittance details every time.
  • Keep the trail clean. Every email is a written record. Factual and professional beats clever every time.
  • Escalate the channel, not just the tone. A louder third email rarely beats a phone call or a note from the account owner.

Template 1: Pre-due reminder (3 days before the due date)

Send this before anything is late. It prevents the most common cause of slow payment, which is not resistance but inattention.

Subject: Invoice [INV-1042] for [amount] due [date]

Hi [Name],

Quick heads-up that invoice [INV-1042] for [amount] is due on [date]. You can pay here: [payment link].

If anything on the invoice looks off, reply and I will sort it out right away.

Thanks,
[Your name]

Template 2: Due-date nudge (day the invoice is due)

Short and assumptive. Most customers who intended to pay simply have not gotten to it.

Subject: Due today: invoice [INV-1042], [amount]

Hi [Name],

Just a nudge that invoice [INV-1042] for [amount] is due today. Payment link: [link].

Let me know once it is submitted so I can confirm receipt on our end.

Thanks,
[Your name]

Template 3: First overdue notice (7 days past due)

Still friendly. Assume an oversight, and give them an easy way to tell you if something is wrong.

Subject: Following up: invoice [INV-1042], [amount]

Hi [Name],

I wanted to follow up on invoice [INV-1042] for [amount], which was due on [date] and is now [7] days overdue.

If payment is already on the way, please disregard this note. If there is a question on the invoice or you need different payment details, reply and I will help.

Payment link: [link]

Thanks,
[Your name]

Template 4: Check for a dispute (14 to 21 days past due)

At this stage, silence usually means one of three things: the invoice is lost internally, someone is disputing it quietly, or cash is tight. Ask directly.

Subject: Is there an issue with invoice [INV-1042]?

Hi [Name],

Invoice [INV-1042] for [amount] is now [18] days overdue. Before I keep following up on payment, I want to check: is there anything about this invoice holding things up?

If there is a dispute, a missing PO, or an approval stuck somewhere, tell me and I will work it with you. If it is simply timing, a payment date I can plan around would help.

Thanks,
[Your name]

Template 5: Direct request (30 days past due)

Drop the softening. Name the facts, name the consequence, and ask for a specific commitment. Loop in the account owner if you have not already.

Subject: Payment needed: invoice [INV-1042], [30] days overdue

Hi [Name],

Invoice [INV-1042] for [amount] is now [30] days past due. I need a payment date from you this week.

If I do not hear back by [date], I will need to pause [service / future shipments / release of the next milestone] until the balance is resolved, per our terms.

You can pay here: [link]. If you would rather talk it through, I am available [two time options].

Thanks,
[Your name]

Template 6: Final notice (45 to 60 days past due)

This one goes to a senior contact, with the original recipient CC'd. It should read like the last email before a different process starts, because it is.

Subject: Final notice: invoice [INV-1042], [amount]

Hi [Senior contact name],

I am writing because invoice [INV-1042] for [amount], originally due [date], remains unpaid at [55] days overdue despite several follow-ups with [original contact].

Please arrange payment by [date]. If the balance is not resolved, we will [hand the account to collections / begin the formal dispute process / suspend the account] as a next step.

Payment link: [link]. I am happy to discuss a short payment plan if that helps resolve this faster.

Regards,
[Your name]

Template 7: Broken promise follow-up

The customer said Friday. It is now Tuesday. This is the highest-leverage email in collections, because it holds someone to their own commitment without sounding aggressive.

Subject: Re: payment planned for [Friday]

Hi [Name],

Following up on your note that payment for invoice [INV-1042] ([amount]) would go out on [Friday]. I have not seen it arrive yet.

Can you confirm the new payment date? If something changed on your end, I would rather know now so we can plan around it.

Thanks,
[Your name]

Make the sequence run itself

Templates only work if they go out on time. The teams that collect fastest do three things:

  • They attach each template to an aging trigger, so the right email goes out at 3 days before due, on the due date, and at 7, 18, 30, and 55 days overdue without anyone remembering to send it.
  • They review drafts before sending, because a template with the wrong invoice facts is worse than no email at all.
  • They track what was sent and what was promised, so the broken-promise email writes itself from the follow-up history.

That is the whole game. Consistent touches, correct facts, and a clear escalation path will collect more cash than any single perfectly worded email.

Frequently asked questions

How many collections emails should I send before calling the customer?

Most teams send two to three emails before a call: a pre-due reminder, a due-date nudge, and one overdue notice. If the balance is large or the customer has gone quiet, call after the first overdue notice instead of waiting through the full email sequence.

Should collections emails come from AR or from the account owner?

Early reminders can come from AR or billing. Once an invoice passes 30 days overdue, the account owner or sales contact should be looped in, because they usually have the relationship leverage that gets a response.

What should I never put in a collections email?

Avoid threats you will not follow through on, legal language you have not cleared, and emotional or accusatory tone. Every collections email is a written record, so keep it factual, specific, and professional.

More from the blog

Keep exploring.

Operations

Why promise dates belong inside the receivables workflow

Promise dates are most useful when they stay connected to invoice context, follow-up history, collector activity, and forecast review instead of living in side notes.

Read post
Integrations

How to plan receivables integrations without slowing the rollout

A practical integration plan starts with the receivables workflow, then maps ERP, accounting, CRM, billing, payment, API, and secure file sources around launch.

Read post
Forecasting

How controllers can run a better weekly cash review

A stronger weekly cash review connects open receivables, planned billing, payment behavior, promises, and collector activity into one operating conversation.

Read post