A client goes from “due yesterday” to “60 days overdue” in ways that look like a pattern: the invoice lands in their inbox, they intend to pay it, something else gets prioritized, your email reminder lands, they think “I’ll get to that next week,” and six weeks later you’re still waiting.
By then, you’ve written a polite reminder. Then another. Then you’re stuck between sending a fourth identical email (which doesn’t work) or escalating to something that feels aggressive (which kills the working relationship you wanted to keep).
There’s a middle path. A sequence that escalates without poisoning the well. The difference is structure: each touch does different work, and the sequence itself does the heavy lifting that repetition alone can’t.
The phases
A late invoice moves through three decision states on the client’s side. Each state needs a different approach.
Days 1 to 14: It slipped their mind. Most invoices in this window are not refusals; they’re forgotten. The bookkeeper was sick. The card declined and nobody checked the system. Your one or two friendly emails net you 50% of your recovery without creating tension.
Days 15 to 30: It’s been deprioritized. They saw your reminder, decided to pay something else first, and now your invoice is in the stack. They haven’t refused it; they’ve just put it lower than other things. A shift from “did you forget” to “when can you do this” changes the dynamic.
Days 30 to 60: A decision has been made. Consciously or unconsciously, they’ve concluded they won’t pay this voluntarily. They may come back later with a dispute. They may suddenly pay when something else resolves. But left alone, they won’t move. This is where structure stops being helpful and escalation becomes necessary.
After day 60, the inbox is no longer the right tool.
Day 1 to 7: Friendly reminder
Send on day 1 (the day after due). This is your cheapest move. Make it easy.
Subject: Quick reminder: invoice #4401
Hi [first name],
Just a heads up that invoice #4401 ($4,200) was due yesterday. If it’s already on its way over, ignore this.
If not, here’s the payment link: [link]
Let me know if anything’s needed on my side.
Thanks,
[Your name]
Follow up on day 7 only if there’s no response. Change the subject line (no longer “reminder,” now “follow-up”), acknowledge the lack of response, and ask for confirmation one way or the other.
Subject: Invoice #4401 follow-up
Hi [first name],
Following up on invoice #4401 ($4,200), which was due last week. Wanted to make sure it didn’t get caught in a spam filter.
Can you confirm by Friday whether there’s an issue on your end, or whether it’s just a timing thing? Either way works; I just want to know where things stand.
Payment link: [link]
Thanks,
[Your name]
The ask at day 7 is not “pay now” but “respond.” A response tells you whether you’re in the “they forgot” bucket or the “they’re ignoring it” bucket. That’s the info that changes your next move.
Day 14 to 21: Specific, time-bound ask
By day 14, a lack of response is itself a signal. Switch from “please respond” to “here’s what I need.”
Subject: Invoice #4401 update needed
Hi [first name],
Invoice #4401 ($4,200) is now two weeks past due and I haven’t heard back. I’d like to close this out without it dragging on.
Can you reply by [specific date, 3 business days out] with one of these:
- A date you’ll pay by
- A specific issue blocking payment
- Confirmation you’ve already paid (with reference number)
If I don’t hear back, I’ll assume option 2 and follow up by phone to figure it out.
Payment link: [link]
Thanks,
[Your name]
The structure here matters. Three choices, each specific, each actionable. This forces a decision instead of allowing them to think “I’ll deal with that later.” The mention of a phone call is not a threat; it’s a signal that the written conversation isn’t working and you’ll move to a different channel.
Day 21 to 30: Pattern interrupt and acknowledgement
By day 21, if you haven’t heard from them, they’re avoiding you. Stop sending invoice-reminder emails. Send something that breaks the pattern.
Subject: Are we still on good terms?
Hi [first name],
I’m sending this one differently because the standard reminders haven’t gotten a reply, and I’d rather check in directly.
Invoice #4401 ($4,200) is now three weeks past due. Either there’s something specific I can fix on my end, or there’s something going on at yours that I should know about, or this is heading toward a more formal recovery process.
I’d much rather talk through option 1 or 2. Reply to this email or text me at [number] and we’ll figure it out.
[Your name]
This one is shorter, softer, and more direct. It acknowledges the pattern. It gives him an out. It also, subtly, signals that you’re not going to keep sending the same thing. The pattern interrupt alone moves about 15% of stalled accounts.
Day 30 to 45: Settlement or payment plan
If you’re at 30 days with no response, a discount is your cheapest recovery lever. A client who won’t respond to email might suddenly engage when the number changes.
Subject: Invoice #4401 settlement option
Hi [first name],
Invoice #4401 ($4,200) is now 30 days past due. Before this gets handed to a formal recovery process, I want to offer a one-time settlement:
Pay $3,150 (25% off) by [specific Friday] and we’ll consider it paid in full.
Settlement link: [discounted link]
If a single payment isn’t workable, reply and tell me what is. I’d rather find a path than send another reminder.
Thanks,
[Your name]
The math: a $1,050 discount to get $3,150 today beats a 35% contingency to an agency (which would net you $1,470 on a full recovery, and costs $0 if they don’t recover). It also keeps the relationship intact.
If they don’t take the settlement, follow up at day 45 with a payment plan instead. Same tone, different offer: three monthly payments of $1,400 instead of one lump sum.
Day 60: Final notice
If nothing has worked by day 60, the inbox is no longer the right tool. This final email puts the decision in front of them: pay, dispute, or escalate.
Subject: Invoice #4401 final notice before escalation
Hi [first name],
Invoice #4401 ($4,200) is now 60 days past due. None of the earlier outreach has produced a response or a payment.
This is the last message I’ll send before moving the account to a formal recovery process. To avoid that, I need one of the following from you by [date, 5 business days out]:
- Payment in full: [link]
- A signed payment plan
- A written dispute with specifics
If I don’t hear back by [date], the account moves to recovery. The recovered amount stays your money. We don’t sell or assign the debt.
I’d much rather close this directly. Hoping we get there.
Thanks,
[Your name]
This is the last email to send yourself. After this, escalation (software-driven recovery, collection agency, or write-off) is the only move.
Rules that matter more than the wording
One channel per touch through day 30. Email on day 1, email on day 7, email on day 14, then switch to email + phone if you have the number. Stacking channels on the same day (email + SMS + LinkedIn on day 14) reads as harassment, not communication.
Use the same thread. Reply in-line to your day-1 email so the whole history sits in one conversation. Easier for them to track. Easier for you to forward to recovery if it goes there.
Specific dates, not “ASAP.” “Reply by Friday” gives them a decision point. “When you get a chance” is indefinite.
Escalate in tone, not just in content. Days 1 to 14 are collaborative (“let’s figure this out”). Days 14 to 30 are formal but still friendly. Days 30 to 60 are professional but acknowledge the issue. After day 60, the next step is not a better email; it’s a different tool.
When the sequence stops working
After day 60, you have three honest paths: write the account off, hand it to a collection agency, or run a formal first-party recovery. Sending an eighth email is the move that produces unrecovered debt.
A structured recovery program (like ti3) handles the day-60-forward work for you. Five weeks of escalating emails, SMS reminders, and a final demand notice, all sent in your name. Settlement and payment-plan links the debtor can self-serve. Money routes directly to your account. The software does the work that email-and-hope can’t.
For accounts under $1,500 of collectible value, the math still favors a discount (settle at 75%) over formal recovery. For accounts above that, software or agency recovery beats doing nothing.
Frequently asked
How long should I wait between touches?
Seven days between touches in the first 30 days (day 1, day 7, day 14, day 21, day 30). Five business days after that (day 30, day 45, day 60). Less than five days reads as harassment. More than 14 days lets the account drift back into “I’ll deal with it later.”
Should I CC a manager or do this in a new thread?
Don’t CC until day 30. Before that, a CC reads as escalation when you don’t want to signal that yet. After day 30, a clean CC (“looping in [AP contact] so this doesn’t slip through cracks”) is appropriate.
What if they reply with a dispute?
A dispute pauses the clock. Respond factually within 48 hours. Either you adjust the invoice or you document that the original stands. The written record matters if it escalates.
Can I use this sequence if I have a long-term client relationship?
Yes. The whole point of this sequence is to escalate without damaging the relationship. You’re not being aggressive; you’re being clear and structured. Good clients respect clarity.
How do I know which accounts are worth all this work?
That’s the question that stops most owners cold. If an invoice is $500 or less, discounting it heavily (or writing it off) usually costs less than the time you’d spend. If it’s $1,500 to $5,000, the sequence above is your best bet. If it’s above $5,000, you might escalate to formal recovery sooner (around day 45, not day 60).
What to do next
If you have accounts in the day-1-to-day-30 window right now, pull the templates above and start the sequence this week. If you have accounts stuck at day 30 to day 60 with no movement, the inbox isn’t enough. Run a free recovery analysis to see which accounts are actually collectible, what your options are, and what the timeline looks like. The rest is just math from there.