Overdue Invoice Email Template for Polite Payment Follow-Up

An overdue invoice email is a collection note, not a threat. It should make the legitimate next step easy while leaving room for a customer who has already paid, needs a corrected invoice, or has a billing dispute.

Before sending

Check the current billing state immediately before rendering:

State	Send overdue email?	Better action
Unpaid and undisputed	Yes	Payment reminder
Paid since the last job ran	No	Suppress
Payment pending	Usually no	Wait for settlement
Disputed	No generic reminder	Route to billing owner
Payment plan or extension	Use agreed schedule	Send only if the agreement says to
Invoice voided	No	Suppress

Escalation sequence

Timing	Tone	Content
First overdue notice	Helpful	Invoice, amount, due date, payment link
Second notice	Direct	Days overdue, impact of continued non-payment
Final notice	Specific	Actual service or collections consequence

Use the customer’s contract and real policy. Do not threaten suspension, fees, or collections unless those outcomes are documented.

Template

Subject: Invoice {{invoice_number}} is {{days_overdue}} days overdue

Preheader: Review the invoice and payment options.

Hello {{billing_contact_name}},

Invoice {{invoice_number}} for {{total_amount}} was due on {{due_date}} and still shows as unpaid.

[Review and pay invoice]

If you have already paid, please disregard this message or send the payment reference to {{billing_support_email}}. If the invoice needs correction or you need to discuss timing, reply to this email before {{next_action_date}}.

{{actual_consequence_if_any}}

{{company_name}}

Make the action safe

Use a secure portal URL, not raw card details in the email. Show invoice number and amount on the destination page so the recipient can confirm the action. If several invoices are overdue, link to a reconciled account view rather than sending a confusing chain of individual notices.

Stop rules

Cancel future reminders when:

• payment settles;
• the invoice is voided or credited;
• a dispute is opened;
• the billing owner records a payment plan;
• the customer unsubscribes from optional reminders, while retaining legally required notices;
• a support case takes ownership of the communication.

Use invoice ID plus reminder stage as the idempotency key. A retry should not advance the escalation stage twice.

QA checklist

• Days overdue is calculated from the invoice timezone and due date.
• The amount and currency match the source system.
• The payment button is authorized and works on mobile.
• The copy distinguishes “unpaid” from “payment failed.”
• The final consequence is truthful and approved by finance.
• Payment or dispute events suppress the next message.

For failed card attempts, use the dunning email template; for the original record, use the invoice email template.

Tone by relationship

For a first overdue notice, assume the customer may have missed the date. For a long-standing account, mention the billing contact and offer a reply path. For a final notice, state the actual service consequence and date, but do not use pressure that finance has not approved.

Avoid “last warning” language when the account is under dispute or a payment is pending. It damages trust and can cause the customer to pay twice.

Operational details

Run the reminder against the ledger immediately before enqueueing. A nightly job can race with a payment webhook, so use invoice status and payment timestamp together. Make the reminder stage idempotent and keep a record of the last notice sent.

For enterprise accounts, route the notice to the billing contact and account owner when the contract permits it. For self-serve accounts, use the secure portal and a clear support address. Measure recovered invoices, days to payment, disputes, and opt-outs.