A Supply-Chain Payment Delay Hits Your Account
Your customer says they cannot pay you until they are paid by their customer further up the chain — 'pay-when-paid' in practice, even if not in the contract.
What this scenario teaches
- Recognise informal pay-when-paid behaviour for what it is
- Check whether your contract actually ties payment to theirs
- Hold the customer to their own obligation to you
- Protect yourself in extended supply chains
- Know when to escalate despite the explanation
8 min read
The scenario
Your invoice is overdue and the customer's explanation is that they are waiting to be paid by their customer further up the chain. 'As soon as the head contractor pays us, you'll be paid' — a familiar refrain in construction, logistics, manufacturing and any tiered supply arrangement. The implication is that your payment is contingent on a transaction you are not party to and have no control over.
The instinct is to accept it as just how the industry works. But unless your contract genuinely makes payment to you conditional on them being paid, their cash-flow problem up the chain is not your problem to absorb. You contracted with them, and their obligation to you usually stands on its own feet.
What's really going on
'Pay-when-paid' is being asserted informally even where the contract does not provide for it. Your customer is treating their own receivable risk as yours to carry, which conveniently shifts the cost of a delay further up the chain onto you. In some industries, contractual pay-when-paid or pay-if-paid clauses are limited or unenforceable under security-of-payment legislation — so the explanation may not even reflect the legal position.
Underneath, the customer may simply be using your money as a buffer: holding your payment while they wait, because it eases their cash flow at your expense. It can also flag that the customer is thinly capitalised and entirely dependent on upstream payment to meet downstream obligations — a fragility worth noting. The key point is that, unless your contract clearly ties your payment to theirs, their obligation to you is independent, and you are entitled to hold them to it.
Your options
- Check your contract. Confirm whether your terms actually make payment conditional on the customer being paid — most do not.
- Hold them to their obligation. Restate, politely but firmly, that your contract is with them and your invoice is due regardless of the upstream position.
- Use any statutory protection. In some industries, pay-when-paid clauses are limited or void under security-of-payment law.
- Tighten future terms. Require deposits or shorter terms on exposed work in extended chains.
- Escalate the overdue balance. If the delay drags on, treat it as the overdue debt it is.
Recommended approach
Check your contract first to confirm what it actually says — in most cases your customer's obligation to pay you is not conditional on them being paid, and once you know that, you can hold them to it. Respond politely but firmly: your agreement is with them, the invoice is due on its terms, and the upstream position is theirs to manage, not yours to fund. In industries with security-of-payment regimes, informal pay-when-paid may carry even less weight than the customer suggests, so it is worth checking that protection.
Going forward, protect yourself in long chains with deposits or shorter terms on exposed work, and treat heavy reliance on upstream payment as a sign of customer fragility worth watching. If the delay persists despite a clear, independent obligation, escalate it like any overdue debt — you can refer the debt with the contract and account history attached. The Academy lesson library covers structuring terms to reduce supply-chain exposure.
What to avoid
Do not accept 'we'll pay when we get paid' as binding just because it is common — check whether your contract actually says so, because usually it does not. Avoid carrying the customer's upstream receivable risk for free; their cash-flow gap further up the chain is not yours to absorb. Never ignore the warning in a customer who is wholly dependent on upstream payment to meet their obligations to you — it can signal fragility. This is general guidance, not legal advice. Pay-when-paid rules vary by industry and jurisdiction, so take advice where security-of-payment legislation may apply.
The lesson
- Unless your contract says so, your customer's obligation to pay you is independent of their own receipts.
- Informal pay-when-paid often carries less weight than the customer suggests — check the contract.
- Security-of-payment law limits or voids pay-when-paid clauses in some industries.
- Heavy reliance on upstream payment can signal customer fragility — watch it and tighten terms.
Frequently asked questions
Do I have to wait until my customer is paid up the chain?
Usually not, unless your contract genuinely ties your payment to theirs — most do not. Their upstream cash-flow gap is generally their problem, not yours. This is general guidance, not legal advice.
Are pay-when-paid clauses enforceable?
It depends on the industry and jurisdiction. In some sectors, security-of-payment legislation limits or voids such clauses. Check your contract and take advice where these regimes apply.
How do I protect myself in a long supply chain?
Require deposits or shorter terms on exposed work, keep clear records of your independent contract, and treat heavy upstream dependence as a risk signal worth monitoring. General information only.
Real situations, the right call
When an account goes past talking, Merion recovers it — commission-only, no upfront fee.