ZAMBO.

Direct answer

Your contact left. The new person inherits a file, not your memory.

The person who hired you, briefed you, and accepted the work has left the company. Their replacement looks at your invoice and sees a number from a stranger for work they never ordered, never watched, and cannot check. Will not pay is often not malice at that moment. It is a new person refusing to put their name on a decision they cannot defend inside their own company. So the job changes shape: you are no longer chasing a payment, you are handing a finished job to a second decider who starts from nothing. Everything the first person knew from being there has to travel in one packet a stranger can check without you in the room. Here is the packet, the message that carries it, and the order to work in.

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

Updated November 1, 2026. First published November 1, 2026. The two delivery records quoted below are real and public, with their client decision states read back from the live service on November 1, 2026.

Step 1. Stop re-selling the work. Start a handover instead

The instinct is to explain how good the work was, how hard it was, and how happy their predecessor was with it. To the new person that is all weather: pleasant, unverifiable, and beside the point. What a replacement can actually act on is a small set of checkable facts, in this order: the company agreed this work at this price, named in a document both sides have. The work was delivered, on these dates, in this form. Someone with the standing to decide on the company side checked it and accepted it, on this date. This invoice, for this amount, is the bill for that accepted work, and it was due on this date. If your first message to the new person contains those four facts with a link or an attachment behind each one, you have not sent a plea. You have sent them the file they were missing, and approving it becomes the defensible move inside their company, which is the thing they actually needed.

Step 2. Build the packet for a reader who was not there

Assemble it as if the reader will never speak to you. One, the agreement: the signed contract, purchase order, or the accepted quote in writing, with the price and payment terms visible, not buried on page nine. Two, the delivery: what was handed over and when, in a form the new person can open today, not a link that died with the predecessor's account. Three, the acceptance: who on the client side accepted the work, in what role, and on what date, with the acceptance itself attached, whether that is a sign-off message, an approval in a system, or a delivery record like the ones in step 3. Four, the money trail so far: the invoice number, the amount, the due date, any part already paid, and every reminder already sent, so the new person does not have to wonder whether they are looking at a first ask or a fifth. Five, one line naming what you need from them: not a general hope of payment, but a decision, an approval or a named objection to a named item, by a stated date. Five parts, each one page or one link. A packet longer than that reads as a defence. This length reads as a file.

Step 3. Read the two states the delivery can sit in when the decider changes

A personnel change is exactly the moment when it matters whether acceptance lives in a person's inbox or on a record anyone at the company can open. 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 states a delivery can carry:

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, decided 2026-10-16T14:31:51.146Z in that example, does not become un-accepted because the individual who clicked it has left. The decision sits on the record, dated, with its release state showing, and the new person inherits a closed question instead of an open one: the work was checked and accepted on the company side, so the remaining act is payment, not a fresh review of a finished job. A pending record, 5 of 5 steps checked and release_hint hold, is the exposed position: the work is checked and was simply never decided before your contact left. There the packet has a second job: ask the new person, by name, to record the decision their predecessor never got to, accepts or flags a named step, so the job closes on a record instead of on whoever happens to be in the chair.

Step 4. Send one introductory message that assumes good faith

Write to the new person as a colleague handing over a file, because the tone of this message sets the whole negotiation. Four short paragraphs. Who you are and what the company engaged you to do, in one sentence, with the agreement date. What was delivered and accepted, with the packet link in the same paragraph, so every claim sits next to its evidence. The invoice position in plain numbers: number, amount, due date, days outstanding, nothing coloured in. And the ask, with a door in it: if anything in the packet is unclear or does not match their records, name the item and you will walk it with them this week. Two things never go in this message: complaints about their predecessor leaving, and urgency theatre about your own bills. The new person has no debt of loyalty to you. They have a professional interest in not inheriting a mess, and the message works when it offers them a clean file instead of a grievance.

Step 5. Separate 'I was not here' from a real objection, item by item

If the answer comes back as a refusal, ask one calm question: which item in the packet does not hold up. Then sort what you hear. I was not here and I cannot approve what I did not see is a process objection, and the packet plus a short walkthrough answers it: offer to go through the delivery against the agreement with them, step by step, on the record, at a time they pick. The price or the scope is wrong is a document objection, and the agreement decides it, not either person's memory of a call. The work itself is not good enough is a quality objection, and it gets the ordinary treatment: named defects against the agreed work get fixed, and a general dislike of a finished, accepted job is not a defect list. What you never accept is a blanket refusal with no item named. A company can dispute a line. It cannot honestly dispute a file it will not open, and saying so, politely, in writing, is usually the sentence that gets the file opened.

Step 6. Remember the debt belongs to the company, and route it that way

If the new person stalls after the packet and a fair window, widen the circle inside the client, in writing, keeping the same factual tone. The accounts payable contact, who pays approved invoices as a process and often needs only the purchase order reference and the acceptance to release a payment a manager is sitting on. The departed contact's manager, who owned the budget the work was charged against. Whoever signed the agreement or the purchase order, if that is a different name again. At each step you send the same packet, not a growing dossier of frustration, and you name the same single ask: a decision or a named objection by a date. People leave companies every week. Agreements, deliveries, and acceptances are how a company remembers what it owes after the people change, and a debt documented that way survives every handover it meets. If the full circle produces neither payment nor a named objection inside a reasonable window, the file you have built is, not by accident, exactly the packet any further step will ask for.

Step 7. Set the next engagement up so no departure can orphan it

Three lines in the next agreement close this hole for good. Line one: two named contacts on the client side, the decider and a named backup, with the sentence that either may accept work and approve invoices. Line two: delivery and acceptance live on a record the company can open without any one person's account, so a departure never takes the file with it. Line three: invoices go to a shared accounts address as well as to your contact, from the first invoice, so the money trail exists in a system the company keeps. None of this signals distrust. Every large company already works this way internally, and a client who resists naming any backup or any shared address is telling you, while it is still free to hear, that your whole position depends on one person's continued employment.

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 contract's terms, cannot show who inside a company holds budget authority today, and cannot make a company pay. The agreement, the delivery and acceptance record, the invoice trail, and your written packet are what the conversation stands on. This page is general information, not legal advice.

Frequently asked questions

My contact at the client company left and the new person will not pay my invoice. What do I do?

Treat it as a handover to a second decider, not as an argument. Build one packet for a reader who was not there: the agreement or purchase order with the price and terms, the delivery itself in a form they can open today, the acceptance naming who on the client side accepted the work and when, the invoice trail with number, amount, due date, and reminders sent, and one line naming the decision you need and its date. Send it with a short, good-faith introductory message that puts the packet link next to every claim. If they refuse, ask which named item in the packet does not hold up, and sort the answer: a process objection gets a walkthrough, a document objection is settled by the agreement, a quality objection needs named defects. The company owes the invoice, not the departed person, so after a fair window, route the same packet to accounts payable, the budget owner, and the agreement signer.

Does an acceptance by someone who has left still count?

On the ordinary shape of these engagements, yes, in the way that matters for this conversation: the acceptance was an act done for the company, in that person's role, at that date, and the work was delivered and priced against it. That is exactly why where the acceptance lives matters. An acceptance that exists only as a warm sentence in a departed person's chat history invites the successor to treat the decision as personal and gone. An acceptance recorded with the delivery, dated and showing its state, reads as the company's own file: in the worked example on this page the record shows status accepted, decided_by client, decided 2026-10-16T14:31:51.146Z, release_hint ok_to_release, 4 of 4 steps checked. You are not asking the new person to trust the predecessor's taste. You are showing them a closed decision they have inherited, which is a much smaller thing to stand behind.

The new person says they would never have approved this work. What then?

Answer the sentence literally, because it contains two different claims. Whether they would have chosen this work is a preference about a decision that is not theirs to remake: the company ordered it, it was delivered as agreed, and their predecessor accepted it. Whether the work fails the agreement is a checkable claim, and there you should be generous and specific: invite them to name the items that fail, walk the delivery against the agreement with them on the record, and fix anything that is genuinely a defect, fast and visibly. What does not follow from either claim is a discount or a refusal on the whole invoice. A successor can renegotiate the future. Renegotiating the price of accepted work backwards, on the ground that a different person now holds the chair, is a thing no company could run its own purchasing on, and most new managers know it once the file is in front of them.

Should I redo any of the work to win the new person over?

Almost never as a payment strategy. Small, named goodwill, a file re-exported in the format their team uses, a short handover walkthrough, costs little and buys a working relationship with the person who may commission the next job. Redoing substantive work, or accepting a reduced price, to get an accepted invoice paid teaches the company that a staff change is a discount event, and it spends your strongest asset, a clean file, on a problem the file already solves. Do the walkthrough, fix real defects, and keep the money conversation on the record. If the new relationship later brings new work, price it as new work, gladly, with the new decider named in the agreement from day one.

How do I set up the next job so a staff change cannot strand my invoice?

Put the decision on a record that belongs to the engagement, not to a person: two named client contacts who can each accept and approve, delivery accepted step by step on a handover the company side can open without any one account, and invoices copied to a shared accounts address from the first one. When the work runs through Zambo, every step carries a verifiable receipt under AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, and the acceptance sits on the same record as the work, so a successor opens one link and sees what was delivered, what was checked, and what was decided. New users get 20 calls and 1 wrap-up free every day, and picking up work in another AI is always free. For $0.99, run the next engagement that way and let the record survive the next departure: get the Day Pass. A Day Pass is unlimited for 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