Direct answer

A demand letter for an unpaid invoice, with the evidence pack attached. The pack is what makes the letter work.

Anyone can write a stern letter. Clients ignore stern letters every week. What changes the outcome is the attachment set: a letter that calmly names the agreement, the delivery, the acceptance, and the exact balance, with each claim backed by a numbered exhibit the client can open and check. At that point the letter is not a threat. It is a preview of the packet a court, a bank, or their own manager would read next, and paying the invoice becomes the cheapest option on the table.

Make the central exhibit checkable before you send: check any Zambo receipt free at zambo.dev/verify, with no signup. If the work ran through Zambo, its handover link is exhibit 2 and 3 in one.

Updated October 24, 2026.

Assemble the pack before you write a word

Exhibit 1: the agreement. Contract, statement of work, approved proposal, or the message thread where scope and price were agreed in writing.

Exhibit 2: proof of delivery. The delivery record saved at handover, the delivery email with its date, or the download record. The download version is covered in prove the client downloaded the files.

Exhibit 3: proof of acceptance or use. The approval reply, the recorded handover acceptance, or the work live in the client product or site, printed with its date.

Exhibit 4: the invoice and the chase trail. The invoice with number, date, due date, and line items, plus every reminder you sent, in date order.

Exhibit 5: the balance math. One page: agreed price, payments received, balance due. The total must match the invoice and the letter exactly.

If an exhibit is missing, that is information too. A missing acceptance exhibit means the letter leans harder on delivery and use. A missing agreement exhibit means this job is the last one you start without the terms in writing. Work with the pack you have, and note the gaps for your own setup afterwards. The dispute that is still at the talking stage is covered in client disputing my invoice.

The letter, section by section

Opening: identify everything in four lines. Your name or business, the client name, the invoice number and date, and the balance due. No preamble, no history of the relationship.

Facts: five short sentences, each pointing at an exhibit. The work was agreed on this date (exhibit 1). It was delivered on this date (exhibit 2). It was accepted, or put into use, on this date (exhibit 3). The invoice was issued on this date with payment due on this date (exhibit 4). Reminders were sent on these dates and the balance remains unpaid (exhibits 4 and 5). Facts with exhibit numbers read differently from complaints. They read as a filing.

Demand: one sentence with a date. Please pay the balance of the stated amount by a specific calendar date, typically 7 to 14 days from the letter, by the stated method. A date, not a phrase like as soon as possible.

Consequence: one calm sentence. If payment is not received by that date, you will pursue the available routes to recover it, which can include a payment dispute process or small claims court, without further notice. Name only routes you are genuinely willing to take. The court version of this packet is ready if you need it: small claims court evidence for an unpaid invoice.

Door left open: one sentence. If any part of the invoice is disputed, ask them to identify that part in writing by the same date, so the undisputed part can be paid. This sentence does real work: it removes the excuse that a small question froze the whole invoice.

Close: attachments listed. List the exhibits by number and title, and keep the tone flat and factual to the final line. The letter should read like it was written by someone who expects to be paid, because the packet says so.

Sending it so it counts

Send it by a route that leaves its own record. Email with the pack attached, plus a tracked postal copy for larger amounts where that is normal in your jurisdiction. Keep the sent email, the attachments exactly as sent, and any delivery confirmation together.
Send the checkable links, not just printouts. Where an exhibit is a Zambo handover or receipt, include the live link in the letter. A client who clicks and watches the record check out at zambo.dev/verify understands the packet is not a bluff.
One letter, then silence until the date. Follow up messages before the deadline soften it. If the date passes with no payment and no written dispute, move to the route you named. Doing what the letter said is what makes your next letter, to anyone, credible.
Keep your own file complete. Letter, pack, proof of sending, and any reply, in one folder. That folder is the start of the court packet or the chargeback response if it comes to that. The chargeback version is in Stripe chargeback evidence for AI work, and the general evidence principles are in can AI agent logs be used as evidence.

Honest limits

This page is practical guidance on structure and evidence, not legal advice, and formal demand requirements vary by jurisdiction and by contract. If your agreement has its own notice clause, follow it over anything here. For a large balance or a complicated dispute, a lawyer reviewing the letter before it goes is money well spent.

And the evidence limit that governs the whole pack: a verifiable receipt proves the saved result was not changed after it was saved. It does not prove the work was worth the price or that the advice in it was right. The letter claims what the exhibits show, no more, which is exactly why it works.

Set up the record before you need it

The pack above is hard to assemble after the fact and trivial to have ready when the work runs through a recorded path from the start. Run the job through Zambo, close it with a handover, record the acceptance, and exhibits 2 and 3 exist before an invoice is ever late.

Work run through the Zambo MCP endpoint at zambo.dev/mcp (153 tools, 35 on the default surface) saves its result when the call runs and returns a verifiable AER-1 receipt (draft-zambo-aer1-26) for every call. In short, an agent receipt is a record of one ai agent tool call that anyone can check: it keeps the exact saved bytes and their sha-256 digest, and it proves the result was not changed since it was saved, not that it was right. Start free: 20 free calls per day, then they upgrade. The Day Pass is $0.99 for 24 hours. Checking any receipt is always free at zambo.dev/verify.

Questions, answered

What should I attach to a demand letter for an unpaid invoice?

Five exhibits: the agreement, proof of delivery, proof of acceptance or use, the invoice with the reminder trail, and a one page balance calculation. Number them, refer to the numbers in the letter body, and make sure the balance figure is identical in the letter, the invoice, and the math page.

How long should I give a client to pay after a demand letter?

A specific date 7 to 14 days out is the common pattern: long enough to process a payment, short enough to keep pressure real. Check your contract first, because some agreements set their own notice periods, and those govern. Whatever date you choose, act on it when it passes.

Should a demand letter threaten court?

It should state consequences calmly and truthfully, once. If small claims court is a genuine next step for this amount in your state, saying so is factual, and your attached packet shows the claim is assembled. Threatening routes you will not take teaches the client to ignore the next letter.

What if the client disputes part of the invoice after my letter?

That is progress, not failure. Ask for the disputed part in writing, invoice and press for the undisputed part immediately, and answer the disputed part from the record: delivery and acceptance exhibits usually settle which parts were agreed and received. The remaining disagreement shrinks to something two reasonable parties, or a court, can decide quickly.

Can I write a demand letter without a written contract?

Yes. Exhibit 1 becomes the message thread where scope and price were agreed, plus any earlier paid invoices on the same terms. Courts and clients both read that as evidence of an agreement. The letter works the same way; you simply cite the thread where a contract would go, in full, not cherry picked.

Start where the work starts: run the next job through zambo.dev/mcp, close it with a handover, and check any receipt free at zambo.dev/verify. If you only need a day, the Day Pass is at zambo.dev/day-pass.

Proof works best when it travels with the work itself. The AER-1 badge kit turns verifiable receipts into an embeddable badge for project pages, docs, and profiles, so anyone who sees the claim can reach the check in one click.