ZAMBO.

Direct answer

Pay in parts is fine. Pay on a record is the point.

A payment plan turns one stuck invoice into a short series of dated promises. It works when the client wants to pay and cannot pay at once. It fails when it is a vague promise with no amounts, no dates, and no rule for a missed part. Here is how to set one up so every part is written, dated, and tied to the work that was already delivered and accepted.

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

Updated October 24, 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.

Step 1. Decide if a plan fits this client at all

A plan is for a willing payer with a cash timing problem: they accept the work, they accept the amount, they cannot produce it in one payment. It is not for a client who disputes the work or the price; a dispute gets answered on the record first, and a plan offered over an open dispute just stretches the argument across months. And it is not for silence: a client who has stopped responding has not asked for a plan, and inventing one for them donates your leverage. One question sorts it: do you accept the invoice, and is timing the only problem? A yes earns a plan. Anything else is a different conversation.

Step 2. Tie the balance to the delivered and accepted work

Before splitting anything, fix what the balance is for. The record format is AER-1, published as an IETF Internet-Draft (draft-zambo-aer1-26), and each step carries a verifiable receipt: a receipt proves the saved result was not changed since it was saved. The two public records below show the two states a balance can sit in:

Accepted: the decision is on the record

Pending: checked, and still waiting on a decision

An accepted record, 4 of 4 steps checked, decided_by client, release_hint ok_to_release, is the clean base for a plan: the work was checked and accepted, so the plan splits a settled debt, and each part payment is just money arriving against a fact. A pending record, 5 of 5 steps checked and no decision yet, release_hint hold, means get the acceptance first and plan second. Splitting an undecided balance invites the client to re-open the work at every part, and the plan becomes four small disputes instead of one settled one.

Step 3. Write the plan down: amounts, dates, and the missed part rule

Keep it short: two to four parts, weeks apart, not months. The first part is paid today, before the plan counts as agreed; a plan that starts later often never starts. Write five things in one message the client confirms: the total balance, each part amount, each part date, what happens while the plan runs (what work, files, or access stays held until which part), and the missed part rule from step 5, stated now while everyone is friendly. The client replies yes to that exact message. That reply is the plan; everything else is conversation.

Step 4. Log every part against the same invoice and the same record

Each part that arrives gets written against the same invoice the same day, with the running balance restated in one line back to the client: part two of four received, this much remains, next part on this date. That running line does three jobs. It proves part payments cannot later be re-described as the full settlement. It keeps the delivery record and the money record as one story a third party could follow. And it makes the end of the plan a non-event: the last part lands, the balance reads zero, and both sides already hold the whole sequence. When the work ran through Zambo, the delivery side of that story is the handover the client already accepted, so the plan is money catching up to a record that was never in question.

Step 5. A missed part: one reset, then the plan ends

Write the day after a missed date, not a week later. Ask what happened and get a new date inside the same week. One missed part with a reason and a new date kept is normal life. A second miss, or a new date missed, ends the plan: say so in one sentence, restate the full remaining balance as due now, and return to the ordinary overdue path with the delivery record attached. Announcing this rule in step 3 is what makes using it in step 5 calm instead of personal. You are not escalating; you are running the agreement both sides confirmed.

Step 6. Set the next job up so no plan is needed

A plan that worked still taught you the client pays slowly. The next job prices that in without punishing anyone: a deposit before work starts, stages billed and accepted as they land, and final files after the final payment. Clients who completed a plan usually accept that shape easily, because it is the same honesty in the other direction: smaller amounts, tied to visible work, on dates everyone can see coming. The plan was the repair. The staged shape is the prevention.

What a record does not settle

A verifiable receipt proves the saved result was not changed since it was saved; it does not prove a client can pay, does not turn a plan into a court order, and cannot collect a part the client refuses to send. The written plan, the acceptance state, and the payment log are what you would show anyone asked to judge the debt. This page is general information, not legal or financial advice.

Frequently asked questions

My client wants a payment plan for an invoice they cannot pay all at once. How do I set it up?

Offer a plan only when the client accepts the work and the amount and timing is the only problem. First get the delivery accepted on the record, so the plan splits a settled debt instead of an open dispute. Then write five things in one message the client confirms: the total balance, each part amount (two to four parts, weeks apart), each part date, what stays held while the plan runs, and the missed part rule. The first part is paid today, before the plan counts as agreed. Log every part against the same invoice the same day and send the running balance in one line. One missed part gets one reset inside the same week; a second miss ends the plan and the full remaining balance falls due. The plan is the confirmed message, not the friendly conversation around it.

How many parts should a payment plan have, and how long should it run?

Two to four parts over two to eight weeks fits almost every freelance invoice. Shorter is safer: each added month is another chance for the client to go quiet, change staff, or hit a new cash problem, and your leverage is highest while the delivery is fresh. Weight the first part heaviest, because it is the part that proves intent; a client who cannot produce a real first part today is not describing a timing problem. Keep parts evenly dated after that, on the client's own pay rhythm if they name one, and never let the plan run past the point where you would still remember the job clearly.

Should I keep working, or hand over files, while a payment plan is running?

Hold the leverage the plan was built on. Work already delivered and accepted is what the plan is paying for, so the remaining files, access, or next stage stay held until the matching part lands, exactly as the written plan states. New work during a plan is a separate decision: starting a fresh job for a client mid-plan stacks a second balance on a first one that is still proving itself. The calm shape is finish the plan, then start the next job on deposit and stages. If you make an exception for a small urgent item, bill it separately and collect it separately, so it never blurs into the plan.

What do I do when a payment plan payment is missed?

Write the day after the missed date. Ask what happened, and get one new date inside the same week, confirmed in the same thread. Do not renegotiate the whole plan around one miss, and do not let the thread go quiet, because silence after a miss is how plans die. If the new date is missed, or a second part is missed, the plan ends under the rule both sides confirmed at the start: the full remaining balance is due now, and you continue on the ordinary overdue path, with the delivery record, the written plan, and the part payment log attached as one packet.

How do I keep the plan itself on a record a third party could check?

Keep the three pieces in one place: the accepted delivery record, the confirmed written plan, and the part payment log against the same invoice. Anyone reviewing the debt later should be able to follow work, decision, plan, and payments without your narration. When the work runs through Zambo, the delivery side is already that shape: every step saved as it happened, the client accepting on the record, and a link the client or a reviewer can open without an account. For $0.99, run the next delivery the same way, so a future balance never needs reconstructing from chat: get the Day Pass. A Day Pass covers 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 for 30 days (one payment) or $290 for 365 days, and $19 for 30 days for $ZAMBO holders, which adds private handover links, your branding, and the approval record as PDF and JSON files.

Related