Past-Due Reminder Best Practices & Templates
Use cadences and copy-ready templates to recover overdue invoices faster
Sending reminders at the right time helps ensure invoices are paid promptly while keeping communication professional and positive.
Below, you'll find recommended reminder intervals along with copy-and-paste email templates that can be used in automated past-due invoice sequences. Each template can be easily customized for your business’s tone, timing, and workflow.
Reminder Sequence Best Practices ⚡
- Start reminders early. Sending your first reminder shortly after the invoice due date greatly increases the chance of timely payment.
- Escalate tone gradually. Begin with friendly reminders, then progress toward direct payment expectations and policy enforcement.
- Repeat strategically. Consistent reminders keep invoices visible without overwhelming customers.
- Reference billing policies. Mention late-fee policies before they take effect so customers have time to resolve the invoice.
- Define a stopping point. Typically around 45–60 days past due before transitioning to manual follow-up or other collections actions.
Example Reminder Cadence ⏱️
| Stage | Timing | Purpose |
|---|---|---|
| Friendly Reminder | 3 days past due | Assumes oversight |
| Follow-Up Reminder | 7 days past due | Maintain visibility |
| Firm Reminder | 14 days past due | Set payment expectation |
| Late Fee Warning | 21 days past due | Policy reminder |
| Late Fee Applied | 30+ days past due | Policy enforcement |
Pre-Built Email Templates ✉️
Click a template below to expand it. Use the Copy Template button to quickly paste it into your reminder sequence.
Email Template
Subject: Friendly Reminder: Invoice {{InvoiceNumber}}
Hi {{CustomerName}},
This is a quick reminder that Invoice {{InvoiceNumber}} for {{AmountDue}}, originally due on {{DueDate}}, appears to still be outstanding.
You can review and pay the invoice here:
{{InvoiceLink}}
If payment has already been submitted, please disregard this message.
Best regards,
{{CompanyName}}
Email Template
Subject: Follow-Up: Invoice {{InvoiceNumber}}
Hi {{CustomerName}},
We're following up regarding Invoice {{InvoiceNumber}} for {{AmountDue}}, which was due on {{DueDate}}.
It appears the invoice may still be outstanding.
You can review and submit payment here:
{{InvoiceLink}}
Please let us know if there are any questions.
Thank you,
{{CompanyName}}
Email Template
Subject: Invoice {{InvoiceNumber}} is Past Due
Hi {{CustomerName}},
We wanted to follow up regarding Invoice {{InvoiceNumber}} for {{AmountDue}}, which was due on {{DueDate}} and remains unpaid.
Please submit payment at your earliest convenience.
You can pay the invoice here:
{{InvoiceLink}}
If payment has already been made, please disregard this message.
Best,
{{CompanyName}}
Email Template
Subject: Reminder: Invoice {{InvoiceNumber}} Past Due
Hi {{CustomerName}},
Invoice {{InvoiceNumber}} for {{AmountDue}} remains unpaid.
Please note that according to our billing terms, invoices unpaid after {{LateFeeDate}} may incur a late fee.
You can review and submit payment here:
{{InvoiceLink}}
Thank you,
{{CompanyName}}
Email Template
Subject: Action Required: Late Fee Applied to Invoice {{InvoiceNumber}}
Hi {{CustomerName}},
We are reaching out regarding Invoice {{InvoiceNumber}}, originally due on {{DueDate}}.
As the invoice remains unpaid, a late fee has now been applied according to our billing policy.
Updated balance: {{AmountDue}}
You can review and submit payment here:
{{InvoiceLink}}
To avoid additional penalties or potential service interruption, please resolve the balance as soon as possible.
Thank you,
{{CompanyName}}
💡 Need to set up your reminder sequences?
If you haven’t configured your past-due invoice sequences yet, start with our step-by-step setup guide . It will walk you through creating and managing your sequences easily.
If you haven’t configured your past-due invoice sequences yet, start with our step-by-step setup guide . It will walk you through creating and managing your sequences easily.
Comments
0 comments
Article is closed for comments.