Sample pre-due nudge
Subject: “Reminder: INV-1042 due Friday ($2,400).” Body: “Hi Alex — friendly note that invoice INV-1042 ($2,400) is due Friday. PDF is attached; you can pay here: [pay-now link]. If AP needs anything else on the invoice, reply to this thread.” Keep it short so it does not feel like a collections note.
Sample day-after-due status ask
Subject: “INV-1042 — checking on payment status.” Body: “Hi Alex — invoice INV-1042 ($2,400) was due yesterday. Happy to resend the PDF or update billing details. Pay now: [link]. Otherwise, what date should I expect payment?” Ask for a date instead of assuming bad intent.
Sample ~7-day overdue status ask (still reminder tone)
Subject: “INV-1042 ($2,400) — still open as of [date].” Body: “Hi Alex — following up on invoice INV-1042, due [original due date]. The balance ($2,400) is still open. PDF and pay-now: [link]. Is there a blocker on your side (PO, billing contact, or review), or should I plan on payment by [suggested date]?” One clear question beats a list of consequences.
Suggested cadence (decide before the first ask)
For many freelancers: (1) first payment request on send day, (2) light pre-due nudge for larger invoices, (3) next-business-day status ask after due, (4) firmer status ask around seven days overdue, then (5) move to overdue email examples if still unpaid. Write the cadence once so you are not inventing tone under stress. Net 30 jobs use the same idea timed to the terms clock—see the Net 30 guide for day numbers.
Edge cases that change the reminder
Client said “we pay on the 15th”: acknowledge that date in the reminder and keep pay-now ready. Partial payment: restate the remaining balance on a revised invoice before reminding. Multiple open invoices: one reminder per invoice number so AP can clear the right balance. Shared inbox / AP portal: keep subject searchable with INV- and amount; avoid “Re: quick question” that hides the invoice.
Failure modes and when to switch guides
Starting a new thread without the invoice number, sending reminders without a pay-now link, escalating to late-fee threats on the first nudge, and mixing three invoices into one email. If the balance is clearly late and you need firmer tone ladders, use overdue invoice email examples. If the issue is Net 30 clock mechanics, use the Net 30 guide. First-ask structure lives on the client payment request email page; copy libraries live on the template page.