Two beliefs ruin most invoice chasing. The first: that reminding a customer about money is rude, which produces silence until resentment. The second: that firmness works from message one, which produces paid invoices and dead relationships. The fix for both is the same: a ladder, where each stage is polite for its position but the position keeps advancing. The customer always knows where they stand, and you never have to decide tone in the moment you are most annoyed.
All four templates below are also a single downloadable pack: overdue-invoice-email-templates.md. Use them with or without any tool, ours included.
The four-stage ladder
Stage 1 · The nudge (3-5 days past due)
Assume good faith, because it is usually true: invoices slip. The nudge gives an easy out and asks nothing but attention.
Subject: Re: Invoice #1082 Hi Sam, A quick nudge on invoice #1082 for $2,340, which came due on June 26. I know these slip through; if it is already in process, please ignore me. If anything on the invoice needs fixing on our side, reply here and I will sort it today. Payment link below. Thanks, Alex
Stage 2 · The check-in (about 15 days)
Still warm, but now with a question that requires an answer. Naming possible reasons (missing PO, invoice question, timing) makes replying easy and surfaces real blockers, which stage 1 politely did not ask about.
Subject: Re: Invoice #1082: checking in Hi Sam, Following up on invoice #1082 for $2,340, now about two weeks past its June 26 due date. Is anything holding it up: a question about the invoice, a missing PO number, or timing on your end? If timing is the issue, tell me what date works and I will note it. If it is already scheduled, a quick "paid on [date]" is all I need. Best, Alex
Stage 3 · The direct ask (about 30 days)
The tone shift stage. No apology, no "just checking in": a specific request with a specific date. For any meaningful amount, make this stage a phone call first and send the email as the written record. Thirty days is also where you check your own side honestly; if the work had a problem, better to hear it now than in a dispute.
Subject: Invoice #1082: 30 days past due Hi Sam, Invoice #1082 for $2,340 is now 30 days past due, and I have not heard back on my earlier notes. I want to resolve this without it getting awkward for either of us. Can you tell me by Thursday when payment will be made? If there is a problem with the invoice or with our work, I would honestly rather hear it than chase silence. Regards, Alex
Stage 4 · The final notice (45-60 days)
Formal, factual, and only containing consequences you will actually enact. An empty threat teaches the customer that stage 4 is survivable, which retroactively deletes your whole ladder. If your terms include a late fee, this is where it appears; if they do not, do not invent one mid-chase.
Subject: Invoice #1082: final notice before next steps Hi Sam, Despite several attempts to reach you, invoice #1082 for $2,340, due June 26, remains unpaid. I need payment or a concrete payment plan by August 8. If I have not heard from you by then, I will pause further orders on the account and apply the late fee provided in our terms. I would much rather resolve this directly. Reply here or call me at (555) 014-2210. Alex Rivera Harbor Supply Co.
Timing, and the judgment calls between the stages
- Same thread, always. Reminders in the thread where the work was agreed carry the context with them and are impossible to claim were missed.
- Scale timing to the amount. An invoice that is a meaningful share of your month moves through the ladder faster; a $90 invoice to a ten-year customer can ride the slow schedule.
- The moment they engage, leave the ladder. A customer negotiating a payment plan gets plan reminders on plan dates, not stage 3 next week. The ladder is for silence.
- Check payment status immediately before every send. The reminder that crosses a payment in the mail is forgivable; the one sent two days after the money landed is remembered. This is the single best argument for reviewing every reminder before it goes: drafting can be automated, but the last-second context check is the send decision itself.
- Log everything. Dates sent, replies, promises made. If stage 4 ever becomes a collections conversation, the log is the asset.
When to stop
The ladder ends at a decision, not at a fifth email. When the stage 4 deadline passes, the question changes from "how do I get paid" to "what is this relationship worth": enforce the late fee, pause the account, hand the balance to collections, or write it off and decline the next order. Any of those is better than months of increasingly hollow reminders, which cost your time and teach your customer base exactly how long your patience runs. Prevention beats all of it; invoices that go out on time with clean details age dramatically better, which is the subject of the invoicing automation guide.
And if you want the ladder to run itself up to the send button: drafting each stage at the right time, in the right thread, with the live balance checked, that is precisely the shape of work an approval queue handles, and our chase-overdue-payment template implements this exact ladder with a human review on every send.
Common questions
Send the first gentle nudge 3 to 5 days after the due date. Earlier reads as aggressive over what is often an honest slip; later teaches customers that your due dates are soft. Then roughly day 15, day 30, and day 45-60 for the remaining stages.
From a person, in the same thread where the work was agreed. Reminders from a faceless accounts@ address are easy to ignore and slightly insulting to a relationship customer. The exception is stage four, where a formal tone from the business is appropriate.
At stage three (30 days) for any meaningful amount, or immediately whenever an invoice is large relative to your month. Phone converts because it is harder to defer a person than an email; follow the call with the written version for the record.
When stage four’s deadline passes without engagement, stop sending emails and make the business decision: late fee per your terms, pause on future work, collections, or write-off. Endless polite reminders past 60 days just document that your deadlines mean nothing.
Automate the drafting and the timing, keep the send behind a human review. The two failure modes of fully automatic dunning, chasing an invoice paid this morning and firing a firm reminder mid-dispute, are both context problems that a ten-second review catches.
See the approval queue for yourself
Connect your tools read only, watch flo.space prepare the first actions, and approve one when you trust it. Nothing sends without you.