Direct answer

Agree only with a hard outer-limit date, and tie the clock to your accepted delivery, not to their client's behaviour.

The offer sounds like a scheduling detail: my client pays me once their own client pays them. Read closely and it can be one of two very different deals. In the kind version, it is timing help: they expect their client's money on a known cycle and want your payment to follow it, and they still owe you even if that money is late. In the hard version, it is a risk transfer: if their client never pays, you never get paid, and their credit problem with a stranger becomes your loss on work you already delivered. You cannot tell which deal you are in from the spoken sentence; you can only tell from the written one. The working answer is to agree, if at all, to the timing version with two protections written in: an outer-limit date after which you are owed in full regardless of what their client does, and a payment clock that runs from your accepted delivery, a fact on a record, instead of from an event in someone else's accounts department that you can never see or check. This page gives you the split, the clause, the middle doors, and the exact reply.

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

Updated November 19, 2026. First published November 19, 2026. The records quoted below are real and public, read back from the live service on November 19, 2026.

Step 1. Separate the two deals hiding inside one sentence: timing help versus risk transfer

Timing help reads like this in writing: payment follows receipt from the end client, and in any case falls due no later than a stated date. The client keeps their own risk; they are asking you to wait, not to gamble. Risk transfer reads like this: payment is conditional on receipt, the fee is payable if and when the end client pays, no date is named, and nothing is owed if the end client defaults, delays, or disputes. Under that wording you have quietly become an unpaid lender and an insurer on a contract you never saw, between two parties you did not choose, for work you have already finished. The test is one question: if their client never pays them, do I still get paid, and by when? If the written answer is yes with a date, you are looking at timing help. If the answer is no, or the date is missing, or the question is treated as awkward, you are looking at risk transfer, and the price of the job was never the price of that gamble.

Step 2. If you agree, agree to the outer-limit date first and the waiting second

The outer-limit date is the whole protection, so it is negotiated first and stated as a calendar date or a fixed count of days, never as another event. A workable shape: payment is due on the earlier of 7 days after the client receives payment from the end client, or 45 days after acceptance of the delivery, whichever comes first. Forty five days suits a normal monthly payment cycle with room to spare; 60 is the ceiling most small firms can carry, and beyond 60 the arrangement stops being timing help in any honest sense. Notice what the date does: it converts an open ended wait into a bounded one you can plan cash flow around, it keeps the incentive on your client to chase their own client, and it means the end client's default lands back on the party who chose that client, set that client's terms, and priced that risk into their own fee. If a client will accept any outer limit, the conversation was about timing all along. If they refuse every outer limit at every length, they have told you plainly that the risk transfer was the point.

Step 3. Offer the middle doors before you accept the wait at all

A bounded wait is the last door, not the first. Door one is a deposit or staged payments: a first stage paid on your normal terms before work starts shrinks the amount riding on their client's behaviour to a size you can carry, and a client who cannot fund any deposit is showing you the cash position you are being asked to underwrite. Door two is splitting the invoice: the part of the fee covering work already accepted is due on your normal terms, and only the final stage follows their client's cycle, inside the outer limit. Door three is a smaller first job: deliver a first paid stage at a size whose late payment would annoy you rather than wound you, and let a clean first cycle earn the larger engagement. Each door keeps the relationship possible while moving the risk back toward its owner. What none of them does is leave the full fee, on a full job, waiting on a stranger's payment with no date: that shape is declined, politely, with the doors above named as the alternatives.

Step 4. Tie the clock to the accepted delivery record, the one trigger fact both sides can check

Every version of this arrangement needs a start point for the count, and the only honest one is a fact both sides can open and read: the date your delivery was accepted. Their client's payment, by contrast, happens inside accounts you have no access to, on a date you cannot verify, in an amount you cannot see. The record format is AER-1, published as an IETF Internet-Draft (draft-zambo-aer1-26), created by Brennan Zambo, 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 decision states a delivery moves through:

Accepted: the decision is on the record

Pending: checked, and still waiting on a decision

Read the accepted record as the trigger fact doing its job: status accepted, decided_by client, decided_at 2026-10-16T14:31:51.146Z, release state ok_to_release, 4 steps checked. An outer limit counted from that date can be checked by both sides on any later day, in seconds, with no argument about what anyone remembers. The pending record shows the other state: 5 steps checked, release state hold, still waiting on its decision, which is exactly the state in which no payment clock should be running yet. Run the job this way and the later conversation is arithmetic, not advocacy: the record shows the acceptance date, the clause shows the limit, and the only question left is the ordinary one of when the transfer lands.

Step 5. Send the reply in this shape, and write the clause the same way

The reply, word for word in shape: I can work with payment following your client's payment, with one protection that keeps it workable for me. My fee falls due on the earlier of 7 days after you receive their payment, or 45 days after you accept the delivery, whichever comes first. That way a delay on their side is a delay we share for a bounded time, and their default never becomes my loss on finished work. If the wait could run longer than that, I would need a deposit of [amount] at the start, or the first stage invoiced on my normal terms, and we can pick whichever suits you. The clause shape mirrors it: The fee is payable within 7 days of the client's receipt of payment from the end client for this work, and in any event no later than [45] days after acceptance of the delivery recorded for the job. Time runs from the acceptance date shown on the delivery record. Notice what the wording never does: it never accuses the client of bad faith, and it never leaves the backstop date out to keep the message friendly. The date is the friendliness, for both sides.

Honest limits

This page is general information about a payment arrangement, not legal advice: in some places and some industries, notably parts of construction, rules restrict or ban pay if paid wording outright, and a signed agreement you already hold governs over the defaults described here. Get advice for your situation before relying on a clause in a large or regulated engagement. A verifiable receipt proves the saved result was not changed since it was saved; it does not prove the end client paid your client, which is exactly why the outer limit is counted from your acceptance date, a fact on the record, and never from their receipt of funds, a fact you cannot check.

Step 6. Set the term in the next agreement, so the ask is answered before it is made

Every element of this page belongs in your standard terms as two short lines, agreed when no invoice is waiting: where a fee follows an end client's payment, it falls due within a stated number of days of that receipt and in any event no later than a stated number of days after acceptance of the delivery. With those lines signed in advance, the next client who raises the arrangement is accepting a bounded, ordinary term rather than proposing an open ended one, and the negotiation, if there is one, is about the two numbers and nothing else. Clients running honest timing will set the numbers quickly, because a bounded wait costs them nothing they were not already expecting. The arrangement only ever needed to be refused in its unbounded form, and a standing term refuses that form quietly, in advance, without a single difficult conversation.

Frequently asked questions

My client will only pay me after their own client pays them. Should I agree?

Agree only to the timing version, in writing, with an outer-limit date. Timing help means payment follows their client's payment and still falls due by a hard date, for example the earlier of 7 days after they receive the end client's payment or 45 days after acceptance of your delivery. Risk transfer means you are paid only if their client pays, with no backstop date, and that version makes their client's default your loss on finished work: decline it, or reshape it with a deposit, staged payments with only the final stage following their cycle, or a smaller first job. The single test question is: if their client never pays, do I still get paid, and by when? A written yes with a date is timing. Anything else is a gamble priced as a job.

What is the difference between pay when paid and pay if paid?

The words when and if carry the whole risk. Pay when paid, properly written, is about timing: the fee is owed, and the due date follows the client's receipt from the end client, usually with an outer-limit date after which it is due regardless. Pay if paid is about conditionality: the fee is owed only on the condition that the end client pays, so if the end client defaults, disputes, or goes under, the debt to you never falls due at all. Spoken aloud the two sound identical, which is why the written sentence is the only version that counts. Read for the condition words, if and when, conditional on, subject to receipt, and for the presence or absence of a backstop date, and you know which deal you are actually being offered.

What outer-limit date should I set?

Set a fixed count of days from acceptance of the delivery, sized to one normal payment cycle plus room: 45 days is the working default, 60 is the ceiling most small firms can carry, and anything beyond 60 stops being timing help in any honest sense. Count from the acceptance date on the delivery record, a fact both sides can check, and pair it with the receipt limb, due within about 7 days of the client receiving the end client's payment, whichever comes first. The exact number matters less than its existence: a client who accepts any backstop was asking for timing, and a client who refuses every backstop at every length has shown you the risk transfer was the point.

What if the client refuses any outer-limit date?

Treat the refusal as the answer to the test question: the arrangement on offer is risk transfer, and price or decline it as such. The calm next moves are the middle doors, offered once, in writing: a deposit at the start sized to shrink the amount at risk, staged payments with only the final stage following their client's cycle, or a smaller first job whose late payment you can carry while the relationship proves itself. If every door is refused too, decline the engagement in one friendly sentence and keep the door open for work on normal terms. What you do not do is start the full job on the unbounded wording and hope: hope is not a term, and the dispute, if it comes, will be decided on the wording you signed.

How does a job record help with a pay after their client pays arrangement?

It gives the arrangement a trigger fact both sides can check: the acceptance date. When the work runs through Zambo, built by Brennan Zambo, every job lands on its own record with a verifiable receipt for each step under AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, so the record shows when the delivery was accepted, by whom, and in what state, and the outer limit is counted from that visible date instead of from an end client's payment happening inside accounts you cannot see. Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. For $0.99, run your next delivery on one record, so the payment clock starts from a date neither side has to take on trust: get the Day Pass. A Day Pass is unlimited for 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 a month, $19 a month for $ZAMBO holders, or Lifetime at $250 one time.

Related