Invoice Email Template (2026): The Email That Actually Gets You Paid

The $2,400 I Was Too Polite to Ask For

It was 2022, before Clickly, before any of the products I’ve bored you with elsewhere on this site. I’d picked up a chunk of contract work — building a slice of backend for a mid-sized company, the kind with an actual finance department and a Slack channel called #procurement. My first proper B2B client. Agreed rate, agreed scope, $2,400 for the phase. I shipped it. I felt great.

Then I sat down to get paid, and realised I had no idea how.

My instinct — because I’d only ever built consumer stuff — was to send them a Stripe payment link. So I did. Their finance person replied within an hour, politely: “We don’t pay by card. Can you send an invoice with our PO number, net-30, and your bank details? We’ll process it in the next run.”

I had to Google what half of that sentence meant.

I cobbled something together in a Google Doc, exported a PDF, wrote a two-line email so apologetic it read like I was asking for a favour, and hit send. Then I waited. Thirty days came and went. Nothing. Day 38, my rent was due and their $2,400 wasn’t, and I sat there for an entire evening drafting a follow-up, deleting it, redrafting it — terrified of sounding pushy to the client I wanted to keep.

That fear cost me nothing in the end (they paid on day 41, it was just their cycle) but it taught me the thing this post is about. The invoice email — the one where you ask a business to pay you — is a completely different animal from the receipt your app fires off after a card charge. And knowing how to send it, and how to chase it without flinching, is a founder skill nobody hands you.

---

Receipt vs Invoice: They Are Not the Same Email

This trips up everyone who came from building B2C, so let me draw the line hard.

A receipt — the order confirmation email — is sent after money moves. The customer clicked pay, the card went through, and the email confirms it happened. It says “you paid.” Your payment processor almost always fires this automatically, and if you sell software online, your recurring billing tool already handles the whole cycle so you never touch it.

An invoice is the opposite direction in time. It’s sent before money moves, to request it. It says “please pay me, here’s how, here’s by when.” Nobody’s card has been charged. There’s no processor to auto-fire it, because from the card network’s point of view nothing has happened yet.

That gap is exactly where B2B lives. Enterprise procurement does not click a checkout button. They want a formal document referencing their purchase order, payment terms like net-30 (due 30 days after the invoice date — net-15 and net-60 are the other common ones), and a way to pay by bank transfer at the end of that window. I laid out which tool generates that document in the invoice automation guide; this post is about the email it rides in on, and the copy that actually gets you paid.

One more distinction, because it matters for deliverability: an invoice is transactional email, not marketing — one-to-one, triggered by real work, expected. Send it from your normal transactional setup, never your newsletter tool. If that split is fuzzy, the complete email guide is the foundation.

---

What Actually Goes In an Invoice Email

The email itself is short; the load-bearing document is the attached PDF. But the email around it still has one job — make paying you frictionless — and skipping any of these buys you a delay.

• A subject line with the invoice number and your name. Invoice #0042 from Shubham Soni — due 13 Aug. Finance teams file by number and search by it later. Make it findable in one glance.
• The invoice number. Sequential, unique, and it goes in the subject, the body, and the PDF. This is the handle both sides use forever. Skip it and every follow-up becomes “which invoice?”
• The amount and the due date, in plain text in the body. Don’t make them open the PDF to learn what they owe and when. Put “$2,400.00, due 13 August 2026 (net-30)” right there in the email.
• How to pay — specifically. A payment link if you take cards, or your bank details (account name, number, routing/IFSC, SWIFT for international) for a transfer. Vagueness here is the single biggest cause of “I was going to pay but forgot.” Give them the rails.
• The PDF invoice attached. Not just inline in the email body — an actual attached file. Their accounting system needs a document to file against the PO. More on why this is non-negotiable below.
• Payment terms and any late fee, stated once, calmly. “Payment due within 30 days” is enough. A monthly late fee (1.5% is a common convention) only belongs here if you agreed it upfront — a surprise one just starts a fight.
• A human sign-off. One line — “Any questions, just reply” — from a real inbox, not no-reply@. A stuck invoice usually just needs one small clarification, so make it easy for the AP clerk to ping you.

That’s the whole anatomy. Notice what’s not here: no marketing, no upsell, no “check out our new feature.” This is a bill. Treat it like one.

Always attach the PDF — here’s why

The email is for the human. The PDF is for the machine and the auditor. A business client’s accounts-payable process almost always requires a document they can store, match to a purchase order, and produce years later if the tax authority asks. An email body is not that document. So generate a proper PDF — invoice number, both parties’ details, line items, tax broken out, total, due date — and attach it every single time. The email is the delivery van; the PDF is the cargo.

---

The Templates You Can Steal

Here’s the sequence I wish I’d had in 2022. Three emails: the invoice itself, a gentle nudge, and a firm-but-fair final notice. Lift them, swap the details, and send.

1. The initial invoice email

Subject: Invoice #0042 from Shubham Soni — due 13 Aug 2026

Hi Anjali,

Thanks again for the work this month — good to be building with your team.

Please find attached invoice #0042 for the API integration phase.

  Amount due:  $2,400.00
  Due date:    13 August 2026 (net-30)
  PO number:   PO-88231 (as provided)

To pay by bank transfer:
  Account name:  Shubham Soni
  Account no.:   xxxx-xxxx-1234
  Routing/IFSC:  XXXXXXX
  (SWIFT for intl: XXXXXXXX)

Or pay by card here: https://pay.example.com/inv/0042

The PDF is attached for your records. Any questions on the
invoice, just reply to this email — happy to sort it out.

Best,
Shubham

Clean, complete, zero friction. Everything they need to pay is in the body; the PDF is attached for their books. That’s a well-formed invoice email.

2. The polite “just checking in” chaser

Send this a day or two after the due date, not before. It assumes good faith, because nine times out of ten they simply missed it.

Subject: Re: Invoice #0042 — friendly reminder (was due 13 Aug)

Hi Anjali,

Just a gentle nudge on invoice #0042 ($2,400.00), which was
due on 13 August. It may well be sitting in your next payment
run — totally understand these things take a cycle.

I've re-attached the PDF so it's easy to find. If it's already
been processed on your end, ignore this and thank you!

Let me know if you need anything from me to release it.

Cheers,
Shubham

The magic words are “it may well be in your next run” and “if it’s already been processed, ignore this.” You give them an easy out and assume competence. This recovers most late invoices without a hint of tension.

3. The firm overdue notice

If it’s 7–14 days past due and the polite nudge got silence, you escalate — still professional, but now there’s a spine to it.

Subject: Overdue: Invoice #0042 ($2,400.00) — 14 days past due

Hi Anjali,

Following up again on invoice #0042 for $2,400.00, now 14 days
past its 13 August due date. I haven't seen payment come through
and my earlier reminder may have been missed.

Could you confirm the status today, and a date I can expect
payment? If there's a hold-up or a form I need to complete on
your side, tell me and I'll turn it around immediately.

Per the agreed terms, a 1.5% monthly late fee applies to balances
overdue beyond 30 days, which I'd much rather not add.

Thanks,
Shubham

Notice it still offers help (“a form I need to complete?”) and only mentions the late fee if you’d actually agreed one. Firmness is not rudeness. You’re allowed to ask, clearly, for money you earned.

---

Where the PDF Actually Comes From

You don’t hand-build invoice PDFs in a word processor forever — I did, in 2022, and it’s fine for exactly one client. The moment you have a few, generate them from a real tool that numbers them sequentially and remembers your details. And as with most things I write about, you probably already own one.

If you’re on Stripe proper, Stripe Invoicing is built in and priced honestly for a founder: 0.4% per paid invoice on the Starter tier (capped at $2), no monthly fee, and you only pay when the invoice actually gets paid. It generates the PDF, hosts a payment page, and sends the email for you — subject line, reminders, the lot. For a lot of B2B billing that’s the entire job, done.

If you sell through a Merchant of Record like Paddle or Dodo Payments, they auto-generate tax-compliant invoices for every transaction — but remember, that’s for money flowing through their checkout. The classic net-30 client paying you by bank transfer never touches that rail, which is exactly the case a dedicated invoicing tool exists for.

For that, go free first. Zoho Invoice is genuinely free up to 500 invoices a year — a ceiling you won’t hit for ages — and lets you raise an invoice, email it, and record an offline bank payment against it. Wave is the other free pick, strongest in the US and Canada, with unlimited invoices on its free plan. Either one gives you sequential numbering and a proper PDF at $0. I went deeper on all of these — and the exact moment they beat your processor — in the invoice automation breakdown.

A note for founders like me who send the email themselves: if you’re generating the PDF in your own app and firing the email through Resend or ZeptoMail, attach the PDF as a real file and authenticate your domain (SPF, DKIM, DMARC) so the invoice doesn’t land in spam. An invoice in the junk folder is an invoice that never gets paid — and now it’s your fault, not their finance team’s.

One more, for the cross-border crowd: if a client pays you internationally by transfer, put your Wise details on the invoice rather than eating a brutal wire-conversion fee, and Indian founders collecting domestically can raise GST invoices straight out of Razorpay.

---

Chasing Payment Is a Founder Skill

Here’s the part I most needed to hear in 2022, so I’ll say it plainly: being owed money and not chasing it is not politeness. It’s a bug in your business.

I lost a whole evening to the fear of sounding pushy, and the truth was mundane — the client had a payment cycle, my invoice was in it, and one calm follow-up would’ve told me so on day 31 instead of leaving me spiralling. Businesses expect to be chased; their AP teams process dozens of invoices, yours is not special, and a reminder is not an accusation. The founders who get paid on time are simply the ones who send the second email without apologising for existing.

So systematise it and take the emotion out. Due date passes → polite nudge in a day or two. Still nothing after a week or two → firm notice with a requested date. The templates above are that system, and when the follow-up is a script you send on a schedule rather than an agonised decision, the fear evaporates.

And that’s the honest asymmetry: your app can auto-send a thousand receipts a month and never make you think. But the invoice email — the one that brings actual money in — is the one you have to own. The tools generate the PDF; the courage to send the third email is on you.

---

The Bottom Line

An invoice email isn’t a receipt. A receipt confirms money that already moved and your processor sends it for free. An invoice requests money that hasn’t — and in B2B, with POs and net-30 and bank transfers, that’s a real email you send, and often chase.

So: put the invoice number, amount, due date, and payment method in the body; attach a proper PDF for their accounting; generate that PDF from a tool you already own — Stripe Invoicing if you’re on Stripe, Zoho Invoice or Wave for free otherwise. Then, when the due date slides past, send the polite nudge, and if that’s ignored, the firm one — without flinching. The money you earned isn’t yours until it’s in the account, and the second email is what puts it there.

This is the Broken Engineer Guide — I ship the work, then nearly starve because I’m too shy to send the bill, and write it all down so you just send it. Go collect what you’re owed.