Direct answer

Your client will not pay. Here is the sequence that works.

Most unpaid invoices are not theft. They are a mix of cash flow, an approver who left, and one uncomfortable question nobody can answer: was the work actually delivered, and was it what was agreed? The side that can answer that question with a record gets paid. Here is the whole sequence, in order, including the step most people skip.

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

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

Why clients do not pay

Four causes cover most of it, and they need different moves. Cash flow: the client is stretching every payment, and yours is one of many. A changed approver: the person who agreed the work left, and the new one will not release money for work they cannot see. A genuine quality argument: the client thinks the work is wrong, which is settled by the agreement and the acceptance state, not by louder invoices. And the delivery argument: the client says the work never arrived, or was never accepted, or was not the work that was agreed. That last cause, and half of the second one, are won or lost on the record. Whoever can show the work, step by step, with times attached, stops arguing and starts settling.

Step 1. Check the boring causes first

Before any escalation, confirm the invoice itself is clean: the amount matches the agreement, the invoice number and date are right, it went to the person who actually releases payments, any purchase order or reference the client requires is on it, and the payment details are correct. A surprising share of "won't pay" is "was never properly asked." Fix the paperwork in one pass, note the fix in one sentence, and resend. No apology tour, no new argument.

Step 2. The reminder that carries the record

The first reminder is short and factual, and it does one thing most reminders never do: it attaches the delivery record next to the invoice. Three lines are enough. The work agreed, the date it was delivered, and where the record of it lives. A reminder that says "invoice 104 attached, work delivered October 3, full record here" lands differently from one that says "just following up," because it quietly answers the only respectable reason to delay.

Step 3. Send the proof packet

At two weeks, stop reminding and start proving. The proof packet is four things in one message: the written agreement, the invoice, the per-step delivery record with its timestamps, and the acceptance state. If the work ran through Zambo, the record already exists and looks like this:

Accepted: the client checked it and released the work

Scope: Retrieval, extraction, verification, and reporting pipeline producing an AI-adoption research packet for a law firm.

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

Scope: AI visibility audit of zambo.dev: homepage copy inventory, on-page citation audit, and evidence-based recommendations.

Notice what the two cards show together. The packet does not claim the client is satisfied. It shows the work, when each step was saved, and whether the client has accepted it, flagged it, or not decided yet. A pending state is not a weakness in your position; it is the client's own unfinished decision, in writing, with the complete work in front of them. If your work did not run through a recording tool, assemble the same packet from sent mail, file history, and version history. It is weaker, because you gathered it yourself after the fact, and it is still far stronger than an argument.

Step 4. The formal demand

At a month, the tone changes and the facts do not. A formal demand names the amount, the agreement it comes from, the date payment is required by, and the route you will take after that date. Keep it boring. One page, no grievances, no adjectives. Send it somewhere that keeps its own delivery record, and keep the proof packet attached, because at this point the packet is the whole case in miniature.

Step 5. The formal routes

After the demand date passes, the standard routes are: a dispute or arbitration process if a platform sits between you and the client, mediation, small claims court for amounts inside its limit, or handing the invoice to a collections agency or selling it at a discount. Which fits depends on the amount, the agreement, and where you and the client are. This page is general information, not legal advice, and local rules vary. Every one of these routes starts with the same question, what is your evidence, and the proof packet is the answer to it.

What proof does not settle

A delivery record proves the saved result was not changed since it was saved, and it shows the acceptance state. It does not prove the work was good. It does not prove who produced the work. And it cannot make a client who has no money pay. Quality arguments are settled by the agreement plus the acceptance state, which is exactly why acceptance belongs inside the record: a client who accepted the work, step by step, has a much smaller dispute left to have.

Set up the next job so this cannot repeat

Three habits end most payment fights before they start. Deliver as a record, not as attachments scattered across email threads: one link, every step, times attached. Put an acceptance test in the written agreement: work is accepted when the client opens the delivery link and accepts, or flags a specific step within an agreed number of days. And invoice against milestones on longer jobs, so the most you can ever argue about is one milestone, not the whole project. The contract page in the related links carries copy-ready clauses for all three.

Frequently asked questions

My client won't pay me. What do I do?

Work the sequence in order. First check the boring causes: wrong contact, wrong amount, missing purchase order, terms the client never saw. Then send one short reminder that carries the invoice and the delivery record together. At two weeks, send the proof packet: the agreement, the invoice, the per-step delivery record with its timestamps, and the acceptance state. At a month, send a formal demand with a date on it. After that the routes are a platform dispute if a platform sits between you, mediation, small claims court, or a collections agency, and each of those goes better with the packet already in the client's hands. Most clients who can pay, pay somewhere on that ladder. The ones who cannot pay are a credit problem, not an argument, and no wording fixes them.

How long should I wait before I escalate?

A workable rhythm: a short reminder within the first week after the due date, the proof packet at two weeks, the formal demand at one month, and a formal route after that. Contracts and local rules vary, and a stricter written agreement beats any general rhythm. What matters more than the exact days is that each step is factual, short, and carries more record than the last, so the client always knows what the next step looks like.

What is a proof packet?

It is the small bundle that settles a delivery argument: the written agreement, the invoice, the delivery record showing each step of the work with the time it was saved, and the acceptance state showing whether the client accepted the work, flagged it, or has not decided yet. Arguments about work are usually arguments about missing records. The packet removes the argument by showing the work itself, in order, with times attached.

What if my client says the work was never delivered?

That sentence hides three different claims: it was never sent, it was sent but never arrived, or it arrived but was never opened. Each one is settled by different evidence, and a delivery record answers the first two outright, because every step in it carries the time it was saved. The full breakdown, with the exact reply to send, is on the sister page: client says I never delivered the work.

How do I stop this happening on the next job?

Deliver the next job as a record instead of an attachment. When the work runs through Zambo, every step is saved as it happens, and the client receives one handover link to check and accept or flag, so the proof packet exists before anyone argues. For $0.99, send the proof packet and end the dispute: get the 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