Client not paying an invoice: the six-rung ladder

When a client is not paying an invoice, walk six rungs in order and count the days from the due date, not from the day you sent it. Nudge on day 3, as a reply on the original invoice thread. Call on day 10 and ask for a date. Send a formal notice on day 21 that names the agreed terms and the day work pauses. Pause on day 30. Decide on day 45: recover on a written payment plan, write off and archive, or hand it to collection. Each rung has one channel, one script, and one condition that moves you to the next.

Most operators never walk that sequence. They send one reminder, feel awkward, wait, send a second reminder that reads exactly like the first, and then either let it go or write something at 11pm they would not have written at 11am. Chasing feels personal because you improvise it every time. Write the sequence down once and it stops being about you.

Why page one does not answer the question

Search "client not paying invoice" in English and the first screen is invoicing-software content marketing: ten tips, a reminder template, advice to stay polite. None of it is wrong. You already know an overdue invoice needs a courteous reminder. The part that goes missing is what happens on day 10 that did not happen on day 3, and at what point you are allowed to stop delivering.

The way to ask a client to pay an overdue invoice is to ask for a date instead of asking for the money, and then to change the channel every time the date does not arrive. That is the whole sequence below.

That last one is the question operators actually ask. A services founder posted his version of it on Indie Hackers: should he continue the work and send reminders, or stop it until they pay, even though the client had a launch coming up. An unnamed stop-work point means the answer is always keep going, and that is how a late invoice quietly becomes free work.

One assumption underneath everything below. Most late payers are disorganised, not hostile. The invoice is sitting in an approval queue behind eleven others, or the person who signs it was away, or it landed in an inbox nobody opens. The ladder is written for that client. It still works on the small number who are stalling on purpose, because every rung ends in a date and a record.

The six-rung ladder

Days count from the due date. Day 0 is the day the money was supposed to arrive.

Rung	Day	Channel	What changes on the record	Exit condition
1. Due	0	none	Status: due	Paid
2. Nudge	+3	Reply on the invoice email thread	Status: nudged. Promised-pay date if given.	A payment or a date
3. Call	+10	Phone, not email	Status: called. Promised-pay date. Named owner.	A promised date, in writing
4. Formal notice	+21	Written, copied to whoever signs	Status: formal notice. Amount at risk. Charge applied.	Payment or a written plan
5. Pause	+30	Written, plus the calendar	Status: paused. Delivery blocked.	Payment or termination
6. Decide	+45	Internal	Status: recovered, written off, or in collection	Closed

The days are a default, not a law. A client on 60-day terms who has always paid on day 58 does not need a call on day 10. What matters is that the interval is decided in advance, once, rather than in the moment when you are annoyed and short of cash.

Rung 1: Due, day 0

Do nothing. A due date passing is not an event yet. Payment runs are weekly at most companies, bank transfers land a day or two late, and a client who pays on day 2 has not done anything to you.

The only thing that happens on day 0 is that the record changes state. The account moves to due, which means it is now something you are tracking rather than something you are hoping about.

Rung 2: Nudge, day 3

Reply on the original invoice email, in the same thread, so the invoice is right there above your message. A fresh email with a new subject line makes the client hunt for the attachment, and hunting is what gets an invoice postponed.

Three rules for this one. Assume an oversight. Do not apologise for writing. Ask for a date, not for the money.

Hi [name],

Invoice [number] for [amount] was due on [date] and I don't have it marked as paid on my side. Attaching it again in case it needs to go back into the queue.

Can you confirm the date it's scheduled for? If it's already gone out, tell me the day it left and I'll chase it at my end.

Thanks, [you]

What you are collecting here is not the payment. It is a date, in writing, from a named person. That is the thing rung 3 will be built on.

Rung 3: Call, day 10

Ten days in, a second email is the same email. Change the channel. Pick up the phone, and call the person who runs the budget rather than the person you normally work with, if you know who that is.

The call has one purpose: get a date out of their mouth. You are not asking for the money, you are asking when.

"Hi [name], it's [you]. I'm calling about invoice [number], the one from [month]. It's ten days past due and I wanted to ask you directly: when can I expect it?"

Then stop talking. The pause is the whole technique. Most people fill it with the real answer, which is usually a process problem you can work with: it needs a PO number, it missed the run, the approver is out until Thursday.

If they give you a date, repeat it back and say you will confirm it in writing. If they give you a reason but no date, ask again in one sentence: "That's fine. What date should I expect it by?"

Then send this the same day, while the call is still true:

Hi [name],

Good to talk. Confirming what we agreed: invoice [number], [amount], paid by [date]. I'll leave it there until then.

[you]

A promise that only exists in a phone call evaporates in about a week. A promise in an email is something you can quote back without arguing about what was said.

Rung 4: Formal notice, day 21

Three weeks past due, the register changes. This one is written, it goes to whoever signs the agreement as well as your usual contact, and it cites the terms you both agreed rather than how you feel about the delay.

Four things belong in it: the amount, the days overdue, the late-payment charge your terms specify, and the date work pauses. Neutral throughout. No threats, no capital letters, no line about how this is affecting you.

Subject: Invoice [number], [n] days overdue

Hi [name], copying [signatory] as they sign off on our agreement.

Invoice [number] for [amount] was due on [date] and is now [n] days overdue. On [date] you confirmed it would be paid by [date]. It hasn't arrived.

Our agreement of [date] sets payment at [n] days and a late-payment charge of [amount or rate] after that. I'm applying it from today, which makes the total [amount].

The same agreement pauses work when an invoice passes [n] days. That date is [date].

Please send either the payment or a written date by [date].

[you]

Notice where the authority comes from. Every number in it is traceable to the agreement you both signed, so nothing in it is your opinion. That is the difference between a formal notice and an angry email with better spelling.

Rung 5: Pause, day 30

This is the rung nobody writes about, and it is the one the operator was searching for. Work stops.

Say it calmly, in writing, and say exactly what restarts it. A pause announced as a term reads as a business decision. The same pause improvised in frustration reads as an ultimatum, and an ultimatum invites the client to argue with you instead of paying you.

Hi [name],

Invoice [number] is [n] days overdue, so as of today I've paused work on [project]. Nothing is lost: the current build is where we left it and I'm holding your slot until [date].

Work restarts the day the payment clears. If the date is the real problem, send me a written schedule and I'll restart against that instead.

[you]

Two details make this land. Say what is preserved, because the client's first fear is that their work has been deleted or de-prioritised forever. And give a second door, the written schedule, so that a client who genuinely cannot pay this week has something to reach for other than silence.

Rung 6: Decide, day 45

Forty-five days past due, the account gets a decision rather than another message. Three outcomes, and you pick one.

Recover on a written plan. Split the amount, name the dates, and get an explicit yes. Not "let's see how next month looks."

Invoice [number], [amount]. Agreed schedule: [amount] by [date], [amount] by [date]. Work restarts on the first payment. Reply "agreed" and I'll treat it as accepted.

Write off and archive. The amount comes off your receivables and the account stops appearing in your live client list. The record stays, the history stays, and a flag stays on the account permanently.

Hand it to collection. A debt collection agency or a lawyer, depending on the amount. Once it is handed over, you stop contacting the client about the money entirely.

Not deciding is the fourth option, and it is the expensive one. An unpaid invoice you have neither collected nor written off sits in your receivables inflating a number you plan with, and the account re-enters the pipeline six months later as if none of it happened.

The promised-pay date, the field nobody keeps

Operators record what they sent. Almost nobody records what the client said back.

"End of the month" is a commitment with a date attached, and the moment you write that date down, three things change. The next contact has an opening line that is not a complaint: you said the 30th. You can sort your accounts by promises that have expired instead of by how bad you feel about each one. And you can see, across a year, which clients keep their dates and which ones name a date to end the conversation.

You do not have a chasing problem. You have promises nobody wrote down.

Store it as a real date field, not as text in a notes box. A date field sorts. A note does not. Alongside it, keep the rung the account currently sits on and the name of the person responsible for the next contact, because "someone should follow up" is not an assignment.

Three decisions taken before the invoice goes out

Most of this is won before anything is overdue.

Terms in writing. The payment window, the late-payment charge, and the stop-work point, agreed at signature. All three are easy to write into a contract in March and nearly impossible to introduce on day 30, when the client will hear them as a punishment invented on the spot. This is also the only place rung 4 gets its charge from. An agreement that does not name a late-payment charge does not have one, and the formal notice has nothing to quote.

Money up front. A deposit or a milestone split, so no single invoice carries the whole engagement. This is the only one of the three that changes what happens to you rather than what you say, and it is the reason a late payment is an inconvenience for some businesses and an emergency for others.

A named chaser. The person who follows up is not the person delivering the work. Splitting those two roles takes the relationship out of the conversation, and it means the follow-up happens even in the week when the delivery person is buried. On a small team the chaser can be the same human wearing a different hat, as long as the record says who owns it.

What a CRM does here, and what it does not

Syncek does not send invoices, take payments, or connect to your accounting tool. The invoice lives where it already lives. What we hold is the client record and the board the chase runs on.

Any stage-based object in Syncek becomes a Kanban pipeline, so the six rungs are six columns and every account sits in exactly one of them. Time-in-stage shows on every card, which turns "how long has this been at formal notice" from a memory into a number. Date fields hold the promised-pay date, the owner field holds the name of the chaser, and a saved view sorted by promised-pay date gives you the list of promises that have already expired. Columns sort, views save, and your team opens the same board you do.

We do not remind you, notify you, or chase anything on your behalf. There is no email sync, no automation, and no AI reading your client relationships. The dates get entered by the person who had the conversation, and the pass happens because it is on somebody's calendar.

If you want to run the ladder on your own accounts, Syncek offers a 15-day free trial of the Business tier with full access and no credit card. Pricing is published on the site. Export to CSV or JSON anytime, including after you cancel.

Get the guide

We've prepared a guide to keep on hand while you build or audit your CRM. 14 pages, A4.

The card lives on the resource page: the late invoice chase card. Drop your email, get the PDF, and keep it open the next time an invoice slips.

The chase card is a fourteen-page A4 guide you can keep next to the screen: the six rungs with their day, channel, script opener, record change, and exit condition, plus the three pre-invoice decisions, the three outcomes at rung 6, and a blank column for your own terms.

Frequently asked questions

What should you do when a client is not paying an invoice?

Walk six rungs in order, counting days from the due date rather than the day you sent it. Nudge on day 3 in the original invoice thread. Call on day 10 and ask for a date. Send a formal notice on day 21 naming the agreed terms. Pause work on day 30. Decide on day 45: a written payment plan, a write-off, or collection. Each rung has one channel and one exit condition.

When should you send the first payment reminder?

Three days after the due date, not on it. Payment runs are weekly at most companies and transfers land a day or two late, so a client who pays on day 2 has done nothing to you. Send the day-3 nudge as a reply on the original invoice email so the invoice sits above your message, assume an oversight, and ask for a date rather than for the money.

How many chasing steps make sense?

Six, and each one changes something. Day 0 changes the record's status. Day 3 asks for a date in writing. Day 10 changes the channel to a phone call. Day 21 is a formal notice citing the agreed terms. Day 30 pauses work. Day 45 decides between a plan, a write-off, and collection. Repeating the same reminder in the same channel is what makes chasing feel endless.

Can you stop work if a client does not pay?

Yes, and the point is to name the day in advance rather than decide it while annoyed. Put the pause in your terms, cite it in the day-21 formal notice, and apply it on day 30 in writing. Say what is preserved, because the client's first fear is that their work is gone, and offer a written payment schedule as a second door.

What is a promised-pay date and why should you record it?

It is the date the client says the invoice will be paid, taken from a named person and confirmed in writing the same day. A promise that exists only in a phone call fades within about a week; a promise in an email can be quoted back without arguing over what was said. It is also the field almost no invoicing tool keeps, which leaves the next rung with nothing to stand on.

When should you write an invoice off?

At day 45, as one of three deliberate outcomes rather than a slow fade. A write-off takes the amount off your receivables, removes the account from the live client list, and keeps the record and its history with a flag on it. The alternatives at that same decision point are a written payment plan with named dates, or handing the debt to collection.