Direct answer

Unpaid invoice? Pause the work, cleanly, and say exactly how it restarts.

Pausing new work when the last invoice is overdue is normal, professional, and far cheaper than finishing another stage on top of a debt. Here is when to pause, the boring checks to run first, the exact message to send, what to protect before you pause, and how staging stops the situation repeating.

See the instrument first: the live demo runs one real call and hands you its verifiable receipt, no signup.

Updated October 19, 2026. The delivery records quoted below are real and public, with their client decision states read back from the live service on publication day.

The rule underneath the question

An overdue invoice changes what new work is. Before the due date, extra work is goodwill. After it, extra work is an unsecured loan to a client who has already shown you their payment timing. Pausing is not rude and it is not a dispute. It is the normal commercial response, used by agencies, trades, and platforms everywhere: the account is overdue, so the account pauses. The mistake is not pausing. The mistake is pausing late, angrily, or without a record, or not pausing at all until the unpaid pile is too big to argue about calmly.

Do the boring checks first

Before the pause message, confirm the position in one pass: the invoice amount matches the agreement, it went to the person who releases payments, any purchase order reference is on it, the due date has actually passed under the agreed terms, and no payment is already in flight with a date attached. A pause announced over a paperwork error on your side costs you the standing the pause was meant to protect.

Pause in writing, with a restart attached

The pause message in the questions below does three jobs: it states the fact, it states the state change, and it makes restarting effortless. Keep the delivered work checkable throughout the pause, like the two states every delivery record already carries:

Accepted: the client checked it and released the work

Still open: the record waits for the client's decision

The pending record is the honest picture of a paused job: the work exists, the client can still open it, and the decision, and the payment that follows it, are visibly still theirs to make.

What a pause does not do

A pause does not collect the invoice. It stops the debt growing while the existing routes, reminder, proof packet, formal demand, and the formal routes after that, do the collecting. It also does not override a contract that promises continuous service or a notice period: read your agreement, and where the money is large or the contract is complex, get advice for your situation. This page is general information, not legal advice. A verifiable receipt proves the saved result was not changed since it was saved. It does not prove the work was good, and Zambo never holds client funds.

Restarting well

When payment lands, restart promptly, confirm the restart in one line, and invoice the next stage the staged way: deposit or milestone first, delivery record building as it runs, acceptance at the end. A client who paid to restart has told you the pause worked exactly as designed. Thank them by being boring about it: no lecture, no probation speech, just the staged rhythm from here on.

Frequently asked questions

Can I stop work if a client has not paid my last invoice?

Yes, in most working arrangements you can pause new work when an earlier invoice is overdue, and pausing early is far better than quietly finishing the next stage on top of an unpaid one. Check your written agreement first: a pause or suspension clause, a payment schedule, and any notice period in it govern the details, and contracts and local rules vary. Then pause in writing, factually, in one short message: name the unpaid invoice and its due date, say that new work pauses until it is paid, name what stays safe in the meantime, and name the restart: work resumes the day payment lands. Keep delivering nothing new, keep arguing about nothing else, and keep the record of the work already done intact and checkable. A clean pause is a business state, not a punishment.

When should I pause, and when should I keep going?

Pause when the overdue amount is real money, the due date has passed, and there is no agreed payment date in writing. Keep going, briefly and on a named date, when the client has given a specific payment date, the paperwork on your side is the actual blocker, or a tiny delay is normal for that client's payment cycle and the history is clean. What you should not do is start a new full stage on an overdue invoice because a conversation felt friendly. Friendly is not a payment state. The states are paid, due, overdue, and paused, and your work follows the state, not the mood.

What do I actually say when I pause work?

Short, written, and complete in one message. A working form: invoice [number] for [amount] was due on [date] and is still open. I am pausing new work on the project from today until that invoice is paid. Everything delivered so far stays available at [delivery link], and I will restart on [first working day] once payment lands. No grievances, no history of the relationship, no threats. The message works because it names the fact, the consequence, and the restart, so the client has exactly one clear action to take.

What should I protect before I pause?

The record. Before the pause starts, make sure everything already delivered is saved somewhere the client can check and you can point to: the delivered stages, their dates, and the acceptance state for each. If the client later says the paused job was never delivered, or was delivered wrong, that record is the answer. Do not delete work, withhold already paid-for deliverables, or damage anything the client owns: a pause stops new work, it is not leverage over finished work, and crossing that line turns a clean payment position into a dispute about you.

How do I stop this happening again on the next job?

Stage the work so an unpaid invoice can only ever be one stage deep: deposit at the start, each stage invoiced and accepted before the next begins, and a pause clause written into the agreement. Run the work through Zambo so each stage lands as a verifiable receipt on one handover link, with its acceptance state visible to both sides. For $0.99, set up the next job in stages, so the pause decision is written in the agreement and backed by the record instead of improvised mid-argument: https://zambo.dev/day-pass/ A Day Pass covers 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 a month or $290 a year, and $19 a month for $ZAMBO holders, which adds private handover links, your branding, and the approval record as PDF and JSON files.

Related