Back to blog
guides

Invoice Email Template: 8 Examples to Copy (First Send to Final Notice)

Eight copy-paste invoice email templates: first send, polite reminder, formal chase, final notice, paid confirmation, recurring monthly, dispute response.

By Ivan Obodianskyi··13 min read

A perfectly-formatted PDF invoice attached to a one-liner email ("Invoice attached, thanks") gets paid eventually. A perfectly-formatted PDF invoice attached to a clear, scannable email body gets paid faster. The email body is what your client's accounts payable team actually reads — the PDF is the document of record, but the email is the routing decision.

Below are eight invoice email templates you can copy and adapt — covering the whole arc from first send through final notice. Each comes with a one-paragraph note on why it works, because templates without rationale tend to misfire.

For the mechanics of attachments, subject lines, and AP portals, see how to send an invoice. For the timing logic on late-payment follow-ups, see how to follow up on an unpaid invoice. This guide focuses on the language — what to write in the body of each email.

Template 1 — First send

The invoice is finished, the PDF is attached, you're sending it for the first time. This is the email that sets the tone for the entire payment cycle.

Subject: Invoice #2026-007 — Smith Design / PO-4521

Hi Maria,

Please find attached invoice #2026-007 for the May design sprint.

Summary:
- Invoice:     #2026-007
- Period:      May 1–15, 2026
- Amount:      $5,700.00 USD
- Due date:    June 6, 2026 (Net 30)
- PO:          4521
- Payment:     ACH (details on the invoice)

Let me know if you need anything else for processing.

Thanks,
Jane Smith
Smith Design
EIN: 12-3456789

Why it works: Every fact AP needs to make a routing decision is in the body. They can approve, code, and queue the invoice without opening the PDF. The PO reference puts the invoice straight into the matching process. The EIN at the bottom saves a verification email later.

Template 2 — Gentle reminder (1–3 days past due)

The due date passed yesterday. Most clients haven't even noticed — the invoice is in a queue, in spam, or in someone's "I'll get to it" pile. A friendly nudge resolves the majority of these.

Subject: Invoice #2026-007 — quick check

Hi Maria,

Just a quick note that invoice #2026-007 ($5,700) was due
yesterday and I haven't seen payment come through yet.

Could you confirm receipt and let me know if there's anything
missing for processing? Happy to resend the invoice if needed.

Thanks,
Jane

Why it works: Zero accusation, zero apology. It assumes the client missed it (which is almost always true at this stage) and offers to fix it. Asking "could you confirm" forces a response — if they reply "yes, scheduled for Tuesday," you have a date. If they reply "we never got it," you've flushed out the real problem in 12 hours instead of two weeks.

Template 3 — Second reminder (day 7 past due)

A week late. "They probably just forgot" no longer holds up. Time to escalate the tone slightly and surface any process delays.

Subject: Invoice #2026-007 still showing as outstanding

Hi Maria,

Following up on invoice #2026-007 ($5,700) — it's now 7 days
past due (issued May 7, due June 6).

Per our agreement, payments more than 7 days overdue are subject
to a 1.5% monthly late fee. I haven't applied that yet, but
wanted to flag it.

Could you confirm when this is scheduled to pay? If there's a
hold-up in AP, I'd like to help unblock it.

Thanks,
Jane

Why it works: Three moves in one short email — references the prior reminder by implication, names the contractual late fee (signal, not threat), and asks a specific question that requires a specific answer. "When is this scheduled to pay?" can't be deflected with "we're working on it" — they either give a date or surface the actual blocker.

Template 4 — Formal chase (day 14 past due)

Two weeks. You've tried email twice. The polite-and-friendly approach has run its course. This email is the bridge between "reminder" and "warning."

Subject: Invoice #2026-007 — 14 days past due

Hi Maria,

Invoice #2026-007 ($5,700) is now 14 days past due. I sent
reminders on June 7 and June 13 and haven't received a response.

Could you please:

1. Confirm the invoice was received and routed correctly
2. Provide a specific payment date
3. Let me know if there's a dispute or hold on this work

Per our agreement, the late fee (1.5% monthly) will be applied
starting today, adding $85.50 to the balance due.

I'd much rather resolve this by email than escalate. Please
respond by [date — 3 business days from now].

Thanks,
Jane

Why it works: Three numbered asks make the response unambiguous — the client can't answer in a vague way. The "I'd rather resolve this by email" line keeps the door open while making it clear other channels exist. Applying (not just threatening) the late fee gives the client a financial reason to respond.

Template 5 — Final notice (day 30 past due)

A month past due. If your earlier emails warned about stopping work or escalation, you have to follow through here or your terms become a bluff.

Subject: FINAL NOTICE — Invoice #2026-007

Hi Maria,

Invoice #2026-007 is now 30 days past due. As noted in my
emails of June 7, 13, and 20, this is my final written notice
before escalation.

Updated balance, including late fees:

  Original invoice:    $5,700.00
  Late fee (1.5%):     $   85.50
  Total now due:       $5,785.50

Effective today, I am pausing all new work on the Smith Design
account until this invoice is paid in full.

If payment is not received by [date — 14 days from now], I will
refer this matter to [collections / small claims court /
my attorney].

Please confirm receipt of this notice.

Jane Smith
Smith Design

Why it works: Drops the friendly register entirely. Specific dollar amounts, specific deadline, specific consequence. "Please confirm receipt of this notice" forces a written acknowledgment — useful evidence if you do end up in court. Choose only one of collections/small-claims/attorney in your real version (multiple options reads as bluffing).

Template 6 — Recurring monthly invoice

Monthly retainers, subscriptions, ongoing services. You'll send this same email roughly 12 times a year, so it should be short and easy to skim.

Subject: Invoice #2026-007 — Smith Design / May retainer

Hi Maria,

Attached is invoice #2026-007 for the May retainer.

- Invoice:     #2026-007
- Period:      May 1–31, 2026
- Amount:      $4,000.00 USD
- Due date:    June 30, 2026 (Net 30)
- Payment:     ACH (details unchanged from prior months)

No PO needed unless your process has changed. Let me know.

Thanks,
Jane

Why it works: Brief, predictable, repeats the exact format your client's AP team has come to recognize. "Payment details unchanged" pre-empts the "are the bank details still the same?" reply that otherwise costs a day. The "no PO needed unless..." line addresses the common drift where companies introduce PO requirements mid-engagement.

Template 7 — Paid confirmation / thank-you

Money landed. Many freelancers skip this email. They shouldn't — it's free relationship maintenance and signals professionalism that lingers when the client is choosing whether to renew or refer you.

Subject: Receipt — Invoice #2026-007 paid

Hi Maria,

Confirming receipt of payment for invoice #2026-007 ($5,700)
on June 6. Receipt #R-2026-007 is attached.

Thanks for the prompt payment — much appreciated.

If you have anything else on the runway for June, happy to
slot it in.

Thanks,
Jane

Why it works: Closes the loop. The PDF receipt attachment gives the client clean paperwork for their bookkeeping. The "anything else on the runway" line is a soft sell that costs nothing and occasionally surfaces new work. The "thanks for the prompt payment" line gently trains clients to pay on time — they get acknowledged for it.

Template 8 — Responding to a payment dispute

The client paused payment because something is wrong (or they claim it is). Maybe a scope dispute, a quality complaint, or a billing question. The wrong response — defensive or capitulating — usually makes it worse.

Subject: Re: Invoice #2026-007 — happy to walk through

Hi Maria,

Thanks for flagging the concern on invoice #2026-007. Before
we adjust anything, I'd like to make sure we're aligned on what
was delivered:

Scope per our agreement (dated April 28):
- 24 design hours @ $200/hr — completed May 1–15
- Three concept rounds — delivered May 3, 8, 14
- Final asset handoff — delivered May 15

Could you point me to the specific item you're disputing? If
there's been a misunderstanding, I'd rather fix it than haggle
on the total.

I'll hold the late-fee clock at today's date while we work
through this. Could we get on a 15-minute call this week?

Thanks,
Jane

Why it works: Acknowledges the dispute without conceding. References the contract, lists deliverables, and asks them to be specific about what's wrong. Holding the late-fee clock is a small concession that buys cooperation. Offering a call shifts the conversation off email where it tends to go in circles.

Customizing for your tone

The templates above lean toward US professional B2B — clear, friendly-but-not-warm, slightly direct. Adjust for your context:

Creative agency / SaaS startup style. Drop the formal salutation ("Hi Maria" → "Hey Maria"), trim the email further, drop the EIN line. The summary table can become two lines: amount and due date.

Enterprise / large-client style. Keep the formal salutation, add "Dear" + last name if the client uses that register, include the EIN/registration number explicitly, attach a W-9 or VAT certificate if it's their first invoice with you.

International B2B. Add your VAT or GST registration number, note the applicable tax rate, and use ISO date format (YYYY-MM-DD) which is less ambiguous than US-style 5/14/2026. For EU reverse-charge supplies, add the "Reverse charge" notation.

Solo client / consumer-style. Drop the AP-style structured summary. A two-sentence body ("Here's the invoice for May. Due June 6. Let me know if you have questions.") is fine. Reserve the structured format for B2B AP teams.

Subject line patterns

What works:

  • Invoice #2026-007 — Smith Design / PO-4521 — identifiable, searchable
  • Invoice #2026-007 — May retainer — identifiable, descriptive
  • Invoice #2026-007 — quick check — for reminders, signals tone
  • FINAL NOTICE — Invoice #2026-007 — for final emails, signals urgency

What kills opens or routing:

  • Invoice attached — non-searchable, generic
  • Payment / Invoice — too vague
  • URGENT (in normal cases) — cried-wolf phrase that AP teams filter
  • Your invoice from Jane — third-person about yourself, awkward
  • Subject lines over 60 characters — AP-system displays truncate them

The pattern that works: Invoice #[number] — [your business] / [PO if applicable]. Searchable, sortable, unambiguous.

Common mistakes

"Invoice attached, thanks"

The single most common invoice email. The body has no information. The client can't make any decision from it. They have to open the PDF, parse it, then re-route. Multiply that by 200 invoices a day in AP and you understand why your invoice sits.

Sending from a personal email address

[email protected] works for friends; AP systems treat it with suspicion. Use a domain-based email — even [email protected] on a $10/year domain looks materially more professional and clears spam filters more reliably.

Forgetting to repeat the invoice number in the body

If the subject line has the number but the body doesn't, copy-paste into a ticketing system loses the reference. AP teams routinely strip subject lines when filing. Put the number in both.

Apologizing in follow-up emails

"Sorry to bother you about this, but..." weakens the position. The client owes you money for work you delivered. State the facts, ask for action, sign off. No apology.

Threatening without follow-through

Every email after a missed payment that mentions "I will escalate" — and then doesn't — trains the client to ignore your terms. Either follow through or don't threaten. Choose one path and execute it.

Sending the same template to a 5-person client and a 5,000-person client

A two-person agency owes you money — fix it with a phone call. A 5,000-person enterprise can't get on a phone call — escalate in writing through their AP escalation paths. Match the message to the org.

Missing the right payment terms

If your invoice says "Due Upon Receipt" but you don't follow up until day 30, you've given up the leverage of your own terms. See due upon receipt meaning for when it applies.

FAQ

Should I include the invoice details in the email body or just attach the PDF?

Both. Attach the PDF as the formal document of record. Summarize the key facts (number, amount, due date) in the email body so AP can route without opening the PDF. The body summary is what determines how fast the invoice moves through their queue.

What's the right subject line for an invoice email?

Invoice #[number] — [your business] / [PO if applicable]. The invoice number is the most useful sort/search key. Including the PO when applicable gets the invoice straight to the matching system. "Invoice attached" or "May invoice" both fail in AP searches.

How often should I follow up on a late invoice?

A graduated cadence: day 1–3 reminder, day 7 firmer reminder, day 14 formal chase, day 21 warning, day 30 final notice. The full cadence with timing logic is covered in how to follow up on an unpaid invoice.

Should I CC anyone on invoice emails?

Direct contact in TO, AP in CC for the first send. From day 7+ of late-payment follow-ups, escalate by moving AP to TO and the project contact to CC, or CC their finance lead. Don't BCC anyone you wouldn't want the recipient to know about.

Do I need a different tone for international clients?

Slightly. EU and UK clients expect more formal salutations and ISO date formats. Asian clients (Japan, Korea) often expect very formal email register. Latin American clients tend to be more relational — a personal greeting goes a long way. Adjust the salutation and date format; the structured summary stays the same.

Can I use these templates verbatim?

Yes — they're written to be copy-paste with bracketed fields ([name], [date], [amount]) to swap in. The reasoning blocks under each template explain what's load-bearing in the wording so you can adapt confidently.

When should I switch from email to phone?

Day 14 past due if email hasn't gotten a substantive response. Phone calls are harder to ignore than email and force a real-time answer. After the call, send a same-day email summarizing what was discussed — that summary is your paper trail if it ends up in court.

Should I send invoice emails on Friday afternoon?

No. Friday afternoon emails land in inboxes Monday morning with everything else and get deprioritized. Tuesday–Thursday morning in the client's local time is the highest-visibility window. The same applies to reminder emails.

Ready to send your first invoice?

Free account: 3 invoices forever. No card required.

By

Ivan Obodianskyi

Ivan is the founder of InvoicePeak. He built the product after years of patching invoicing in Word and Excel for himself and his freelance clients.

Related articles