The Best Workflow for Chasing Late Paying Clients (Day 0 to Day 60+)

Most people chase late invoices the same way: they notice one is overdue (usually while doing something else), feel a spike of annoyance, fire off an awkward email, and then forget about it for another two weeks. That's not a workflow. That's a mood.

The best workflow for chasing late paying clients is the opposite of that: a fixed sequence of steps tied to days-overdue, where every step has a trigger, an action, and a decision point. You build it once. Then you stop making in-the-moment judgment calls about whether today is the day you nag someone.

Here's the full sequence, Day 0 to Day 60+. It's deliberately tool-agnostic — you can run it from a spreadsheet, your calendar, your email client, or dedicated software. The workflow is the asset, not the tool.

Why a workflow beats "following up when you remember"

Two reasons, and they're both about removing you from the loop.

First, consistency is what gets you paid. Clients learn your patterns fast. If your follow-ups arrive like clockwork, you become the invoice they pay first, because they know you won't go quiet. If your follow-ups are random, you're the invoice that can wait.

Second, a pre-decided workflow kills the emotional tax. The hardest part of chasing money isn't writing the email — it's deciding to send it. When the rule is "Day 7 overdue means reminder #2 goes out," there's no decision left to make. The workflow already made it.

The step by step late payment workflow

Each step below has the same structure: trigger (what starts it), action (what you do), and decision point (how you know whether to proceed or branch). Copy this into whatever you use as an invoice follow up workflow template and adjust the day numbers to your payment terms.

Day 0 — Invoice sent (the step everyone skips)

Trigger: You send the invoice.

Action: Log it somewhere with three fields: client, due date, and amount. Then send one line alongside the invoice: "Invoice #142 attached — due July 10. Let me know if anything needs changing on it (PO number, billing contact, etc.)."

Decision point: None yet. But that one line matters more than it looks. It surfaces wrong-contact and missing-PO problems on Day 0 instead of Day 30, and those two problems cause a huge share of "late" payments that were never going to arrive on time.

Day –3 — Pre-due nudge

Trigger: Three days before the due date.

Action: A short, friendly heads-up:

"Hi Sam — quick note that invoice #142 ($2,400) is due this Friday. If it's already scheduled, ignore me!"

Decision point: If the client replies with a problem — disputed amount, missing approval, "we never got it" — you've just caught it before the invoice is even late. Fix the issue, reset the clock, and the rest of this workflow may never run.

This is the highest-ROI step in the entire sequence, and almost nobody does it manually, because remembering "three days before due" across multiple invoices is exactly the kind of thing human brains are bad at.

Day 1–3 overdue — First reminder

Trigger: Due date passes with no payment.

Action: A neutral, assume-good-faith reminder. Most late payments at this stage are oversight, not avoidance, so the tone is "FYI," not "where's my money":

"Hi Sam — invoice #142 ($2,400) was due July 10 and I haven't seen it come through yet. Could you check on it when you get a chance? Happy to resend if it's gone missing."

Decision point: Did they reply?

• Replied with a date → log the promised date and set a check on it (see Day 14).
• Replied with a problem → branch out of the workflow and resolve the dispute first. Reminders don't fix disputes; they just irritate someone who already has a reason not to pay.
• No reply → continue to Day 7.

Day 7 — Second reminder, slightly firmer

Trigger: Seven days overdue, no payment, no committed date.

Action: Same facts, less softness. Add a specific ask:

"Hi Sam — following up on invoice #142, now a week past due. Can you confirm when payment will go out? If there's an issue with the invoice on your end, tell me and I'll sort it today."

Decision point: Same branches as before. One addition: if this is a repeat-offender client, make a note — not to act on now, but because pattern data is what tells you whether to change their terms on the next project.

Day 14 — Phone call or direct message

Trigger: Fourteen days overdue, or a promised payment date that came and went.

Action: Change the channel. Email is easy to ignore; a call or a direct message (Slack, WhatsApp, text — whatever you actually use with this client) is not. Keep it short and factual: invoice number, amount, days overdue, "when can I expect it?"

Decision point: A broken promise is its own signal. One missed "it'll go out Friday" is normal corporate slowness. Two is a yellow flag — from here on, only accept commitments with a specific date, and escalate the moment a date slips.

Day 21 — Pause work and say so

Trigger: Three weeks overdue with no firm commitment.

Action: If you're still actively working for this client, this is the escalation trigger most freelancers fire way too late. Pausing work isn't a punishment; it's the natural consequence of an unpaid bill, stated calmly:

"Until invoice #142 is settled, I'm pausing work on the current project. Happy to pick it straight back up once payment lands."

Decision point: If there's no active work to pause, skip ahead — your next lever is the Day 30 letter. Either way, this is also the point to apply any late fee your contract allows, and to reference it in writing.

Day 30 — Formal demand

Trigger: Thirty days overdue.

Action: Send a formal letter (email is fine, but make it read like a letter): all outstanding invoices itemized, total owed, late fees applied, and a hard deadline — usually 7 to 14 days — with a stated consequence: collections, small claims, or legal action, whichever you're actually prepared to do.

Decision point: Only threaten what you'll follow through on. An ignored ultimatum teaches the client that all your deadlines are soft.

Day 45–60+ — Execute the consequence

Trigger: The demand deadline passes.

Action: Do the thing you said. For most small invoices that means a collections agency (they typically take 25–50%) or small claims court (cheap to file, and the filing itself often shakes the payment loose). For tiny amounts, the honest move is sometimes to write it off — but do it as a decision, with the client fired in your head, not as a slow fade.

Decision point: Is the recovery worth more than the cost of recovering it? Run that math once, coldly, and act on the answer.

Making this AR chasing process run itself

A workflow on paper still depends on you noticing that today is somebody's Day 7. That's the failure point — not the steps, the triggers.

So wire the triggers to something that isn't your memory. The minimum viable version is a spreadsheet with due dates plus recurring calendar blocks. The better version is anything that watches due dates and fires the reminders for you, so the sequence runs even during the weeks you're slammed with actual work — which, not coincidentally, are exactly the weeks invoices slip.

That's the real test of the best workflow for chasing late paying clients: it keeps running when you're too busy to think about it. Build the sequence above into your system once, and chasing payments stops being a recurring crisis and becomes a process that quietly executes in the background.

If you'd rather not run the triggers by hand, automated payment reminder tools can execute this exact sequence for you.