Invoice Email Templates: First Send, Reminder, Overdue, Final Notice

Late payment is rarely malice; the invoice was missed, the approver was away, or nobody knew who to ask. A clear invoice email and a calm, predictable reminder sequence gets most invoices paid without a phone call. The four templates below escalate gently from first send to final notice. Send them from billing@yourdomain.com so every message lands in the same thread, is matched to your company, and is authenticated by your own domain.

Quick summary

• Day 0: invoice sent, with total, due date and payment details in the body.
• Due date minus 3 days (optional for new clients): a courtesy note that the invoice is due this week.
• Due date plus 3 days: friendly reminder assuming an oversight.
• Due date plus 14 days: overdue notice, firmer tone, ask for a payment date.
• Due date plus 30 days: final notice stating the consequence (late fee, work paused, collections or small claims) and a last deadline.

The sequence at a glance

1. Day 0: invoice sent, with total, due date and payment details in the body.
2. Due date minus 3 days (optional for new clients): a courtesy note that the invoice is due this week.
3. Due date plus 3 days: friendly reminder assuming an oversight.
4. Due date plus 14 days: overdue notice, firmer tone, ask for a payment date.
5. Due date plus 30 days: final notice stating the consequence (late fee, work paused, collections or small claims) and a last deadline.

Subject line options

• "Invoice [number] from [Company] - due [date]"
• "Reminder: invoice [number] due [date]"
• "Overdue: invoice [number] ([amount]) - please advise payment date"
• "Final notice: invoice [number] - action required by [date]"

Template 1: sending the invoice

Subject: Invoice [number] from [Company] - due [date]

Hi [First name],

Please find attached invoice [number] for [brief description of work or goods].

Amount due: [amount] [currency]
Due date: [date] ([N]-day terms)
Reference to quote on payment: INV-[number]

Payment details:
Bank: [bank name]
Account name: [company legal name]
Account number / IBAN: [number]
Sort code / SWIFT: [code]
[Mobile money or card link if you offer it]

If you need a PO number added or the invoice addressed differently, reply and I will reissue it today.

Thank you for your business.

[Full name]
[Company] Billing
billing@[yourdomain].com | [phone]

Template 2: friendly reminder (3 days after due date)

Subject: Reminder: invoice [number] due [date]

Hi [First name],

A quick reminder that invoice [number] for [amount] was due on [date]. I have attached it again in case the original went astray.

If payment is already on its way, thank you and please ignore this. If there is anything holding it up, such as a missing PO number or a query on the amount, let me know and I will sort it out.

Kind regards,
[Full name]
[Company] Billing

Template 3: overdue notice (14 days after due date)

Subject: Overdue: invoice [number] ([amount]) - please advise payment date

Hi [First name],

Invoice [number] for [amount] is now [N] days overdue. I have not had a reply to my reminder on [date].

Could you confirm by [date, 3 working days away]:
- the date payment will be made, or
- any reason the invoice cannot be paid as issued

Our terms are [N] days and [late fee or interest clause, if any, in one sentence]. I would much rather resolve this by email than apply it.

Invoice attached. Payment details are on it.

Regards,
[Full name]
[Company] Billing
[phone]

Template 4: final notice (30 days after due date)

Subject: Final notice: invoice [number] - action required by [date]

Dear [First name],

Despite reminders on [date] and [date], invoice [number] for [amount] remains unpaid, [N] days past its due date of [date].

Unless payment is received by [date, 7 days away], we will [state the consequence: apply the late payment fee of [amount] / pause ongoing work / refer the debt to a collections agency / file a claim in the small claims court]. We do not want to do this and a payment or a call today will stop the process.

To pay: [payment details or link]
To discuss: [phone], or reply to this email.

Yours sincerely,
[Full name]
[Title], [Company]

Timing and tone

Send invoices the same day the work is delivered; every day of delay is a day added to your payment cycle. Send reminders in the morning of a working day in the client's country. Keep the tone at each step exactly as warm as the previous reply deserved: a client who replied "sorry, paying Friday" gets a thank-you, not the overdue template. Escalate on a schedule, not on emotion, and never skip a step. If a client is consistently late, the fix is shorter terms or a deposit on the next job, not angrier emails.

Mistakes that delay payment

• Payment details only in the PDF; if the attachment is stripped or unopened, the client cannot pay.
• Sending invoices from a personal Gmail so the client's accounts payable team cannot match the sender to the supplier record.
• Vague due dates such as "on receipt". Write the calendar date.
• Reminders that apologise for asking. You did the work; asking for payment is normal.
• Threatening a consequence you will not follow through on; the next invoice will be paid even later.
• Not checking your own delivery logs. If the invoice bounced, the client is not late, you are.

Common questions

Can I automate the reminders?

Yes. Most invoicing tools send reminders on a schedule, and you can point them at your own SMTP mailbox on port 587 with STARTTLS so they come from billing@ on your domain. If you have a developer, the same sequence can be sent through the OquMail send API (a POST to https://api.oqumail.com/api/v1/emails with from, to, subject and html) from billing@ with a Bearer API key.

Should I charge late fees?

Only if they are in your terms and were on the quote. State them plainly from the first invoice so a late fee is never a surprise, then apply them consistently or not at all.

What if the client says they never received the invoice?

Resend immediately, in the same thread, and check your delivery log for the original. On OquMail the per-message log shows whether the receiving server accepted it. Then ask for a specific accounts-payable address so it does not happen again.