Skip to content
The AR Agent

A collections email sequence for every step and every reply

· 11 min read

A good collections email sequence is not just a list of reminders.

The real work starts when the customer replies.

They might promise to pay next Friday. Ask for a PO number. Say the invoice is wrong. Tell you to contact accounts payable. Claim it has already been paid. Or simply ignore you.

Each response needs a different next step.

Below is a complete accounts receivable collections sequence you can use from before the due date through final notice, plus templates for the replies that usually slow payment down.

Why use a collections sequence?

Ad hoc chasing is easy when you have five invoices.

It gets harder when you have 50.

One invoice gets chased twice. Another gets forgotten. Somebody promises to pay Friday, but nobody follows up the following Monday. A customer asks for a PO, the email is forwarded internally, and the invoice sits untouched for another three weeks.

A repeatable AR collections process gives every unpaid invoice a next action.

It should tell you:

  • When to contact the customer.
  • What you are trying to achieve.
  • What happened last time.
  • Whether the customer made a payment promise.
  • Whether something is blocking payment.
  • What needs to happen next.

The emails are only part of that process.

A complete collections email sequence

Here is a simple starting sequence for B2B invoices.

Timing Goal What you want from the customer
7 days before due Prevent a problem Confirm everything is ready
Due date Make payment easy Pay as agreed
3 days overdue Check for a simple delay Payment date or blocker
7 days overdue Get clarity Firm payment date
14 days overdue Resolve or escalate Commitment or owner
30 days overdue Escalate internally Resolution
Final notice Decide what happens next Payment or clear response

Your exact timings can vary.

The important part is that each stage moves the invoice forward.

Step 1: Pre-due reminder

The first email does not need to sound like collections at all.

Its job is to catch simple problems before the invoice becomes overdue.

Subject: Invoice [Invoice number] due [Due date]

Hi [Customer name],

Just a quick reminder that invoice [Invoice number] for [Amount] is due on [Due date].

I've attached the invoice here for reference.

Please let me know if you need anything from our side before payment is processed.

Thanks,

[Your name]

For more early-stage wording, see our payment reminder email templates.

Step 2: Due date

Keep this short.

Subject: Invoice [Invoice number] due today

Hi [Customer name],

A quick reminder that invoice [Invoice number] for [Amount] is due today.

I've attached a copy here for reference.

Please let me know if there are any questions.

Thanks,

[Your name]

Step 3: Three days overdue

Now ask whether something is holding payment up.

Subject: Payment reminder: invoice [Invoice number]

Hi [Customer name],

I'm following up on invoice [Invoice number] for [Amount], which was due on [Due date].

Could you confirm when payment is scheduled?

If there's anything holding it up, let me know and I'll help get it resolved.

Thanks,

[Your name]

This is where the sequence starts to branch.

If the customer replies, do not automatically send the seven-day reminder next.

Deal with what they said.

Step 4: Seven days overdue

If there has been no useful response, ask for a firm payment date.

Subject: Payment date for invoice [Invoice number]

Hi [Customer name],

Invoice [Invoice number] for [Amount] is now overdue.

Please could you confirm the date payment will be made?

If there is an issue preventing payment, let me know what is needed from our side.

Thanks,

[Your name]

Step 5: Fourteen days overdue

By now, you should be trying to get ownership of the issue.

Subject: Overdue invoice [Invoice number]

Hi [Customer name],

I'm following up again regarding invoice [Invoice number] for [Amount], due on [Due date].

Please confirm when payment will be made, or let me know who I should speak with to get this resolved.

If something is blocking payment, please send me the details and I'll make sure it reaches the right person.

Thanks,

[Your name]

Step 6: Thirty days overdue

If the invoice is still unpaid, consider whether another person should be involved.

That might be accounts payable, finance or a more senior contact.

Subject: Invoice [Invoice number] now 30 days overdue

Hi [Customer name],

Invoice [Invoice number] for [Amount] remains unpaid and is now 30 days overdue.

Please confirm when payment will be made.

If you are not the right person to resolve this, could you point me to the person who is?

Thanks,

[Your name]

For a deeper escalation ladder, see our past due invoice email templates.

Step 7: Final notice

A final notice should be factual.

No drama. No threats you are not prepared to follow through on.

Subject: Final notice: invoice [Invoice number]

Hi [Customer name],

This is a final notice regarding invoice [Invoice number] for [Amount], which was due on [Due date] and remains unpaid.

Please arrange payment or contact me by [Date] to confirm how the balance will be resolved.

If there is an issue with the invoice that has not yet been raised, please let me know.

If we do not hear from you by [Date], we will review the next steps available to us for recovering the outstanding amount.

Regards,

[Your name]

Our guide to collecting unpaid invoices covers what to consider if normal collections activity has run its course.

What to do when the customer replies

Invoice overdue, follow-up sent

Customer replies

  1. “We’ll pay on Friday”Confirm the date in writing. Follow up if it’s missed.
  2. “We need a PO number”Pause reminders, fix the PO and resend the invoice.
  3. “Send it to accounts payable”Get the right contact and redirect the invoice.
  4. “We never received the invoice”Resend it with the amount and due date.
  5. “There’s a problem with the invoice”Pause chasing and resolve the dispute first.
  6. “We’re having cash flow problems”Agree a realistic payment plan in writing.
  7. “It’s already been paid”Ask for remittance details and check your records.
  8. No reply at allCheck the contact, then escalate gradually.
The reply decides the next step, not the calendar.

This is the part most collections sequences miss.

The customer has replied. Great.

Now what?

Reply: "We'll pay on Friday"

Do not just say "Thanks."

Confirm the promise in writing.

Hi [Customer name],

Thanks for confirming.

I've noted payment of [Amount] for Friday, [Date].

I'll check back if we haven't received it after then.

Thanks,

[Your name]

Then record the date.

If Friday passes without payment, follow up.

Hi [Customer name],

We had payment of [Amount] scheduled for [Date], but I can't see it received yet.

Could you confirm the updated payment date?

Thanks,

[Your name]

A payment promise should always create a next action.

Reply: "We need a PO number"

Stop the normal sequence.

Get the PO.

Then resend the invoice.

Hi [Customer name],

Thanks for letting me know.

I've updated invoice [Invoice number] with the PO number and attached the revised copy here.

Could you confirm this now has everything needed for payment?

Thanks,

[Your name]

Sending another overdue reminder while the invoice is still missing required information does not help.

Reply: "Send it to accounts payable"

Get the right details and redirect the invoice.

Hi [Customer name],

Thanks.

Could you send me the correct accounts payable contact or email address?

I'll resend invoice [Invoice number] directly to them.

Thanks,

[Your name]

Once you have the contact:

Hi [Accounts payable contact],

[Customer name] asked me to send invoice [Invoice number] for [Amount] directly to you.

I've attached the invoice here. It was originally due on [Due date].

Could you confirm when payment is scheduled?

Thanks,

[Your name]

Reply: "We never received the invoice"

Make it easy.

Do not argue about whether you sent it.

Hi [Customer name],

No problem.

I've attached invoice [Invoice number] again here. The amount is [Amount] and the original due date was [Due date].

Could you confirm you've received it and let me know when payment is expected?

Thanks,

[Your name]

The goal is to get paid, not prove that your sent folder is correct.

Reply: "There's a problem with the invoice"

Pause the collection sequence.

Find out exactly what is disputed.

Hi [Customer name],

Thanks for flagging this.

Could you let me know exactly what looks incorrect or what you would like us to review?

I'll get it to the right person on our side and come back to you.

Thanks,

[Your name]

Once a genuine invoice dispute has been raised, continuing to send standard dunning emails can make the situation worse.

Resolve the issue first.

Then confirm what is payable and when.

Reply: "We're having cash flow problems"

This is no longer a normal reminder problem.

You need a realistic commitment.

Hi [Customer name],

Thanks for being open about that.

What amount can you realistically pay now, and what schedule could you commit to for the remaining balance?

If you send me the dates and amounts you can manage, we can review the options.

Thanks,

[Your name]

You do not have to accept the proposed plan.

But a specific plan is more useful than another vague promise to "sort it soon."

If you agree a schedule, record every payment amount and date.

Reply: "It's already been paid"

Check before chasing again.

Hi [Customer name],

Thanks for letting me know.

Could you send me the payment date and any remittance details or payment reference?

I'll check it against our records.

Thanks,

[Your name]

If the payment is there, stop the sequence.

If you cannot find it, go back with the specific information you checked rather than sending another generic reminder.

Reply: no reply at all

Silence needs its own path.

First, check the basics.

  • Is the email address correct?
  • Is the person still at the company?
  • Is there an accounts payable address?
  • Do you have another legitimate contact?
  • Has the customer responded on an older email thread?

Then escalate gradually.

A simple message could be:

Hi [Customer name],

I'm following up again regarding invoice [Invoice number] for [Amount], due on [Due date].

I've not heard back to my previous emails.

Please could you confirm who I should speak with about payment, or when the invoice will be paid?

Thanks,

[Your name]

If repeated emails go unanswered, continuing to send the same message indefinitely is not a strategy.

Decide when the invoice should move to a more formal stage.

Rules every collections sequence should follow

The templates matter less than the rules behind them.

Stop when the invoice is paid

Obvious, but important.

Once payment is confirmed, the customer should not receive another overdue reminder.

Pause during a dispute

A disputed invoice needs resolving.

Do not keep sending standard reminders while someone on your team is still investigating it.

Keep the conversation together

Where practical, keep replies in the same email thread.

It makes the history easier for both sides to follow.

Record every payment promise

"Friday" should become an actual date in your system.

Then somebody needs to check whether payment arrived.

Record the blocker

If the invoice cannot be paid because of a missing PO, wrong contact or invoice query, record that.

"Overdue" is a status.

"Waiting for PO 48172 from procurement" tells you what needs to happen.

Escalate sensitive cases to a person

Not every collections decision should be automatic.

A major dispute, important customer relationship or unusual situation may need judgment from somebody in your business.

What should you track against each invoice?

At minimum:

  • Invoice number.
  • Amount outstanding.
  • Due date.
  • Last contact date.
  • Last customer response.
  • Current blocker.
  • Promised payment date.
  • Next action.
  • Next action date.
  • Whether the invoice is disputed.
  • Who owns the next step.

This is what stops collections becoming a pile of email threads and sticky notes.

Manual vs automated collections sequences

A manual collections sequence can work when invoice volume is low.

The problem is consistency.

Someone has to remember which invoice needs a follow-up, what the customer said last time and whether a promised payment date has passed.

Basic automated payment reminders solve part of that by sending scheduled emails.

But collections does not follow a straight line.

A customer reply changes what should happen next.

A promise to pay needs tracking.

A missing PO creates a task.

A dispute should pause normal chasing.

A wrong contact needs replacing.

That is the difference between automating reminders and automating more of the actual accounts receivable collections work.

You can see how The AR Agent works.

Frequently asked questions

What is a collections email template?

A collections email template is a reusable message for following up an unpaid B2B invoice. Good templates usually cover different stages, such as a friendly reminder, payment date request, escalation and final notice. The template is only part of the process. What happens after the customer replies is just as important.

How many emails should be in a collections sequence?

There is no perfect number. A practical sequence might include a pre-due reminder, due-date message, several overdue follow-ups and a final notice. What matters is that each email has a purpose. If the customer replies with a blocker or payment promise, the sequence should change rather than continuing automatically.

What should I do when a customer promises to pay?

Confirm the amount and promised payment date in writing, record the commitment, then check whether the payment arrives. If the date passes without payment, follow up on the missed promise and ask for an updated date. Do not let the promise disappear into an email thread.

Should I keep chasing an invoice during a dispute?

Not with ordinary payment reminders. If the customer raises a genuine problem with the invoice, pause normal chasing and get the issue resolved. Once both sides understand what is payable, confirm the amount and new payment expectation in writing.

What is the difference between a reminder sequence and collections automation?

A reminder sequence mainly schedules messages around invoice dates. Collections automation goes further by helping manage what happens after the message, such as tracking payment commitments, identifying blockers, pausing disputed invoices and deciding what should happen next based on the customer's response.

When should I send a final collections email?

Usually after normal reminders and attempts to resolve the invoice have failed. The exact timing depends on the invoice value, payment terms, customer history and situation. A final notice should clearly state what is owed, set a response or payment deadline and explain that you will review further recovery options if it remains unresolved.

How The AR Agent handles this

The AR Agent follows up overdue invoices by email, but the main difference is what happens after the customer responds.

It reads replies, identifies common blockers and keeps the next action tied to what the customer actually said. A promise to pay becomes a tracked date. A missed promise triggers another follow-up. A missing PO or wrong contact becomes a blocker to resolve. A dispute pauses normal chasing.

When a situation genuinely needs human judgment, The AR Agent asks rather than guessing.

Every email, promise, blocker and action stays recorded against the invoice and customer, while working with QuickBooks, Xero, Gmail and Outlook.

Try The AR Agent free for 30 days, no card required.

Try The AR Agent free for 30 days

Tell us a little about your business and we’ll be in touch to get you set up. No card required.

Accounting software

No card required.