Overdue Invoice Email Sequence A Complete Automated Campaign

Why sequences beat “random chasing”

Most teams do not have a cash-flow problem. They have a follow-up consistency problem. Random reminders get delayed, rewritten, or sent with mixed tone. Clients notice that. A defined invoice follow up sequence fixes three things at once: timing, clarity, and escalation discipline.

Timing matters because payment priorities shift daily on the client side. If your reminder lands once and disappears, your invoice often drops below procurement tasks, payroll, and urgent vendor requests. Sequence-based reminders keep your invoice visible without emotional language. Clarity matters because busy AP teams action complete records faster. Every message should include invoice number, amount, due date, and payment path. Escalation discipline matters because clients respond better to predictable rules than occasional frustration.

A good invoice chasing email sequence starts friendly, becomes specific, then becomes firm only when needed. If you need a softer opener before Step 1, use this friendly payment reminder email. If the thread reaches later-stage risk, switch to the final notice unpaid invoice template.

The 7-step sequence (with send days + tone)

The sequence below is designed for unpaid invoices that are already overdue. Send days are practical defaults; adjust for your client cycle if needed. The key is to avoid large gaps.

Hi [Name],

Just a quick reminder that invoice #[number] for [amount] was due on [date].

Payment link: [link]

If you already sent payment, please ignore this note.

Thanks,
[Your name]

Hi [Name],

Following up on invoice #[number] ([amount]). Could you share expected payment timing?

Payment link: [link]

Appreciate it,
[Your name]

Hi [Name],

Invoice #[number] for [amount] is now 7 days overdue. Please confirm the payment date.

Payment link: [link]

Best,
[Your name]

Hi [Name],

This is a second notice for invoice #[number] ([amount]), now 14 days overdue.

Please process by [date] or reply with the blocker so we can resolve quickly.

Payment link: [link]

Regards,
[Your name]

Hi [Name],

Invoice #[number] remains unpaid after 21 days. Per terms, late fees may apply after [date].

Please arrange payment now: [link]

Thanks,
[Your name]

Hi [Name],

This is a final reminder for invoice #[number] ([amount]), now 30 days overdue.

If payment is not received by [date], we will move to the next escalation step.

Pay now: [link]

[Your name]

Hi [Name],

Despite prior reminders, invoice #[number] remains unpaid. If unresolved by [date], we will proceed with [collections/legal/process].

Please reply immediately to finalize payment arrangements.

[Your name]

Timing logic, stop conditions and personalization

An automated sequence is only safe when it knows when to stop. Configure these rules before activating anything:

• Stop on payment: the moment the invoice is settled, all remaining steps cancel. This is non-negotiable - one reminder after payment costs more goodwill than five before it.
• Pause on reply: any client response pauses the sequence until you resolve the thread. A disputed invoice must never keep receiving escalation emails.
• Pause on promise: if the client commits to a date, pause until that date passes - then resume with missed-promise wording, not the next generic step.
• Send-day gaps: keep 3-7 days between early steps and up to 14 days at later stages. Larger gaps lose momentum; smaller ones feel like spam.
• Personalization: every step should carry the invoice number, amount, due date and payment link pulled from the actual invoice - plus the client's name and, for firms, their PO reference.
• Business-hours sending: schedule sends for the client's morning, mid-week where possible.

Subject lines per step

Subject lines should mirror sequence tone. Early messages perform better when neutral and concise. Mid-stage reminders should include overdue timing. Final-stage lines should include action language without threats. This pattern supports a high-response dunning email sequence:

• Step 1: “Quick follow-up: invoice #[number]”
• Step 2: “Checking status on invoice #[number]”
• Step 3: “Invoice #[number] is now 7 days overdue”
• Step 4: “Second notice: invoice #[number]”
• Step 5: “Action needed: overdue invoice #[number]”
• Step 6: “Final reminder before escalation: #[number]”
• Step 7: “Unresolved balance: invoice #[number]”

If they reply: 5 common scenarios + exact responses

Replies are where most teams lose momentum. Keep responses short, factual, and next-step driven.

1. “Talk to finance.”
   “Thanks. Looping finance now. Invoice #[number], [amount], due [date] attached with payment link [link]. Please confirm expected payment date.”
2. “We paid already.”
   “Thanks for the update. Please share remittance reference so I can match and close the invoice on our side.”
3. “Need PO / proof.”
   “Attached: updated invoice PDF, PO #[number], and delivery confirmation. Please confirm queue status and payment date.”
4. “Cash flow is tight this month.”
   “Understood. We can accept [installment option] if you confirm dates today. Please reply with preferred plan so we can document it.”
5. No reply after final notice.
   “Invoice #[number] remains unresolved. Per terms, next escalation begins [date]. Reply today to resolve before that step.”

Automate the sequence (upload invoice PDF)

Manual follow-up breaks when you are busy. Automation keeps timing intact, tone consistent, and records complete. Use the overdue invoice sequence generator to extract invoice fields, draft all seven emails, and schedule sends automatically.

1. Upload invoice PDF
2. Generate 7-step sequence
3. Edit each step for tone and terms
4. Click “Start Smart Chasing” and track opens/replies

Sources

• QuickBooks: Late payments report 2025
• Stripe: Payment reminder guidance
• QuickBooks: Send reminders automatically/manually
• Xero: Set up invoice reminders
• Zoho Books: Reminder settings