First Payment Reminder Email: Template and When to Send It

The first reminder you send after an invoice goes overdue matters more than people think. It sets the tone for the whole exchange — get it right and most clients pay within a few days without any friction at all.

When to send it

Send the first reminder as soon as the invoice is actually late — not weeks later. If terms are Net 15 and payment hasn't landed by day 16 or 17, that's the moment. Waiting longer doesn't make you seem more patient; it usually just means the invoice has slipped further down the client's list of open items. Some freelancers also send a friendly heads-up a few days *before* the due date, which we cover in our piece on the full invoice follow-up sequence.

What the first reminder should assume

Assume it's an oversight, because statistically it usually is. Invoices get buried in inboxes, approval workflows stall, and accounts payable departments run on their own schedule that has nothing to do with your due date. The first email should be genuinely low-friction: short, specific, and easy to act on immediately.

Template

Subject: Invoice #[number] is now overdue

Hi [Name],

Just a quick note that Invoice #[number] for [amount], due [date], hasn't come through yet as of today. It's possible it slipped through — here's the invoice again along with a direct payment link: [link].

Let me know if anything's needed from my end to get this processed.

Thanks,
[Your name]

Why this version works

• It restates the core facts — invoice number, amount, due date — so the client doesn't have to dig through old emails.
• It offers a way out ("it's possible it slipped through") that lets the client pay without feeling accused of anything, which keeps the relationship comfortable if this really was just an oversight.
• It includes a direct payment link rather than asking the client to log into a portal or manually enter your bank details. If you're not using one yet, see our guide on setting up a Stripe Payment Link.
• It ends with a light, specific ask instead of a vague "let me know if you have questions," which invites silence rather than action.

What not to do at this stage

Don't threaten late fees, mention lawyers, or cc anyone. None of that is proportionate to a payment that might be a few days late because of an internal approval delay. Save escalation for later stages — if this reminder doesn't get a response within about a week, move on to a second payment reminder with a firmer tone.

A note on record-keeping

Keep a simple log of when you sent each reminder and what it said. This matters for two reasons: it stops you from accidentally sending a "friendly first nudge" as your fourth email (which undercuts your own credibility), and it becomes useful documentation if the invoice ever needs to go to a formal demand letter or further. A tool that tracks your reminder count and calibrates each email to it — rather than treating every reminder as email number one — solves this automatically, which is the whole idea behind InvoiceNudge.

Variations worth having ready

For a long-standing, reliable client

Keep it even lighter than the standard template — a one-line note is often enough: "Hey [Name], just noticed Invoice #[number] hasn't come through yet — here's the link again in case it's useful: [link]. No rush if it's already in process." A client with a strong track record has earned the benefit of the doubt.

For a brand-new client on their first invoice

Add a touch more detail, since they may not be familiar with your process yet: confirm the payment methods you accept, mention that you're happy to answer any questions about the invoice format, and make sure your payment link is prominent rather than buried at the bottom.

For an invoice with multiple line items or milestones

Reference the specific milestone or phase, not just an invoice number, so there's no ambiguity about which part of a larger project the reminder concerns: "Invoice #1042, covering the discovery phase completed August 1..."

Common first-reminder mistakes

• Sending it too early. A reminder sent the day before the due date isn't a reminder, it's premature and can come across as impatient.
• Sending it too late. Waiting three or four weeks past the due date to send your "first" reminder wastes the low-friction window where a light nudge is most likely to work on its own.
• Making it too long. The first reminder should be short. Longer explanations and justifications belong in later stages if they're needed at all.
• Forgetting to check whether it was already paid. Always verify against your records first — a reminder for an invoice the client already paid (perhaps via a method that didn't sync automatically) damages credibility immediately.

What a good response looks like

A well-calibrated first reminder typically gets one of three responses: payment within a day or two, a quick note explaining a short delay with a new date, or silence. The first two are good outcomes that need no further action beyond a thank-you. Silence after about a week is the signal to move to a second reminder with a firmer, more specific tone.

Timing it around business days

If the due date falls on a weekend or a holiday, it's reasonable to hold off sending the first reminder until the next business day, since the client's finance process almost certainly wasn't running that day either. Sending a reminder that technically fires the moment an invoice crosses into "overdue" territory over a weekend can feel needlessly rigid without adding any real benefit.