Chasing invoices feels awkward because most people do it reactively — they follow up when annoyance finally beats politeness, which is both too late and too emotional. The fix is a fixed calendar that runs the same way for every invoice, decided the moment you hit send. Nothing on it depends on how you feel about the client that week.
The schedule at a glance
| Day | Action | Mode |
|---|---|---|
| Day 0 (send day) | Send invoice + confirm receipt | |
| Due date | Friendly nudge if unpaid | |
| Due +1 to +3 | Check payment actually landed | You, internally |
| Due +7 | First follow-up, ask for a payment date | |
| Due +14 | Firm follow-up, mention terms/late fee | |
| Due +21 | Phone call | Phone, then recap email |
| Due +30 | Final notice with deadline | |
| After deadline | Escalate | See below |
On Net 15 terms the whole cycle from send to final notice is about 45 days. On Net 60 it's 90 — one more argument for shorter terms (how to choose).
Day 0: the send-day setup
Two things happen the day you send the invoice. First, ask for confirmation: "Attached is invoice INV-0233 for $1,850, due October 1 — could you confirm it's arrived and has what your accounts team needs?" That one sentence surfaces wrong-recipient and missing-PO problems on day 0 instead of day 35. Second, put the follow-up dates in your calendar right now — due date, +7, +14, +21, +30. The schedule only works if it's automated away from your mood.
Due date and the first week: stay light
On the due date, if payment hasn't arrived, send a two-line nudge: the invoice is due today, PDF re-attached, "if it's already on its way, please ignore this." No accusation — a meaningful share of clients pay on the due date itself.
At +7 days, follow up properly and ask for a specific date: "When can I expect payment?" A committed date turns the next follow-up from nagging into "checking in on what you told me." Full copy-paste wording for each of these emails is in late payment reminder templates.
Weeks two and three: firm, then human
At +14 days, the tone shifts from friendly to businesslike: reference the due date, the prior reminder, and — only if your invoice terms included one before the lateness — the late fee that's about to apply (how late fees work).
At +21 days, stop emailing and call. Email is easy to ignore; a pleasant phone call to the person who hired you usually isn't. Ask what's holding things up, agree a date, and send a same-day recap email so the verbal promise becomes a written one.
Day 30 and beyond: escalate on rails
At +30 days, send a final notice: the history of reminders with dates, a hard deadline 7 days out, and the consequence — paused work, late fees, and further steps to recover the balance. If the deadline passes, you're no longer following up; you're escalating: payment plan, stopped work, demand letter, small claims or collections, in that order. That ladder is covered in what to do when a client won't pay.
Keeping it non-awkward
- Blame the system, not the client. "My bookkeeping runs reminders weekly on overdue invoices" is true the moment you adopt this schedule, and it depersonalizes every email.
- Same schedule for everyone, favorite clients included. Consistency is what makes it feel administrative rather than pointed.
- Never apologize for invoicing. "Sorry to bother you about this" teaches clients your invoices are optional. "Checking in on invoice INV-0233" is complete.
- Stay warm on the project channel. You can discuss next sprint enthusiastically while accounts-you sends reminder #2. Clients separate the two more easily than you'd expect.
The schedule also starts stronger when the invoice itself announces it:
Example: invoice whose terms announce the follow-up schedule
Stating the reminder cadence on the invoice makes every later email expected rather than awkward.
Day 0 of the schedule is sending a clean invoice promptly — InvoiceKo generates one free in your browser, no signup, no watermark, with autosave so a half-finished invoice is never lost. Then put the dates in your calendar and let the system do the chasing.