Pay-when-paid clauses: what subcontractors can actually do about them

Here's the short version: a pay-when-paid clause makes your payment contingent on the head contractor being paid first, and in most of the English-speaking construction world the law has already decided it's unacceptable. Australia voids it in every state. The UK made it ineffective in 1996. New Zealand gives it no legal effect. Canada channels it through a notice regime so strict most contractors can't be bothered using it. Only in the US does the answer genuinely depend on where you're standing — and even there, four of the biggest construction markets have killed the harshest version.

So why does the clause still show up in subcontracts everywhere, including places it's been dead for decades? Because an unchallenged clause works anyway. A subbie who doesn't know the clause is void will wait for payment as if it weren't. This post is about closing that gap.

Pay-when-paid vs pay-if-paid: the distinction that decides everything

The two get used interchangeably on site, but legally they're different animals.

Pay-when-paid is a timing device: you'll be paid when money comes down from above. In principle your entitlement survives; you're just waiting on someone else's cash cycle.

Pay-if-paid is a risk-transfer device: upstream payment is a condition precedent to your entitlement. If the owner goes broke and never pays the head contractor, you were never owed anything — for work you already did, with materials you already bought.

US courts generally read ambiguous wording as the milder timing version, which is why drafters who mean pay-if-paid spell out "condition precedent" in terms nobody can miss. When you're reviewing a contract, that's your first tell: the phrase "condition precedent" near the payment clause means someone thought carefully about moving owner-insolvency risk onto you.

Either version does the same commercial damage: it takes a credit risk you never priced — the owner's solvency and the head contractor's cash discipline — and parks it on the party in the chain least able to carry it.

Where the clause is already dead

Australia. Every state security-of-payment Act gives conditional payment provisions no effect — NSW s 12, Queensland s 74, Victoria s 13, WA s 14. The definitions are deliberately broad: clauses making your payment, or its timing, contingent on the head contractor being paid, or on anything happening under a contract you're not party to, don't operate. The Acts also void attempts to contract around them (NSW's s 34 is the best-known anti-contracting-out provision). If you subcontract in Australia, a pay-when-paid clause is legal noise — see our state-by-state guides starting with NSW security of payment.

United Kingdom. Section 113 of the Construction Act 1996 makes a provision conditioning payment on the payer receiving money from a third party ineffective, with exactly one exception: upstream insolvency. The 2009 amendments closed the workaround era too — making payment conditional on certification or performance under another contract is an inadequate payment mechanism, and the statutory Scheme's terms get written in over it. The UK payment rights guide covers the notice regime that replaced all this.

New Zealand. The Construction Contracts Act 2002 is the bluntest of the lot: a conditional payment provision "has no legal effect" (s 13), and the Act applies "despite any provision to the contrary" (s 12). Since 2015 the definition explicitly catches clauses that make retention release conditional on upstream events as well. Details in the NZ payment claims guide.

Where it's alive and needs managing

United States. State by state, no exceptions to the rule that there's no rule. Pay-if-paid conditions are void in California (the Supreme Court's Wm. R. Clarke v. Safeco decision — they amount to an unconstitutional waiver of lien rights), void as against public policy in New York (West-Fair v. Aetna), banned in Virginia for contracts from January 2023, and void on Delaware private work. Illinois sits in the middle: pay-if-paid is no defense to a lien or bond claim, but survives as a contract defense if drafted clearly. And in a majority of other states, a clearly drafted condition precedent will be enforced. The practical rule: never assume — check your state before signing, not after the owner stops paying. Our US payment rights guide maps the fallbacks: prompt-payment statutes, mechanics liens, and Miller Act bonds on federal work.

Canada. Ontario took a different route: instead of banning pay-when-paid, the Construction Act made invoking it expensive. A contractor who's been paid must pay subs within 7 days. A contractor who hasn't been paid can only defer by issuing a formal notice of non-payment within the statutory deadline, attaching the owner's notice, and — this is the teeth — undertaking to take the owner to adjudication within 21 days. No notice, no deferral: the sub must be paid within 35 days of the proper invoice even if the owner never pays a cent. The Canada prompt payment guide covers the provinces that have followed.

The negotiation, in practice

You have more leverage on this clause than on almost any other, because in three of the five markets you're only asking the other side to delete something the law already voids — refusing is an admission they hoped you wouldn't notice.

Ask one: delete it. "Clause X.X is unenforceable under [the Act] — please remove it." Short, factual, no drama.

Ask two: replace it with a date. If they want something in its place, offer a fixed payment period measured from your payment claim: "within 20 business days of the payment claim." In NSW and WA that's not a concession — it's roughly what statute imposes anyway.

Ask three (US, enforceable states): cap and convert. If you can't get deletion in a state that enforces pay-if-paid, convert it to pay-when-paid with a backstop: "payment shall not be delayed more than 45 days from invoice regardless of receipt of payment from the Owner," plus interest after that. You've turned unlimited credit exposure into a bounded financing cost you can price.

And always: check the clause's friends. Pay-when-paid rarely travels alone. Set-off rights that let them deduct disputed back-charges from anything owed, claim preconditions engineered to invalidate payment claims, and retention release tied to the head contract all do the same damage by another door. The full subcontract checklist walks the set.

If you've already signed one

In the banned jurisdictions: use your statutory rights as if the clause didn't exist, because legally it doesn't. Serve payment claims under the Act, on time, every cycle. The machine only works when you feed it.

In the US enforceable states and Canada: know your dates cold, keep lien and bond rights alive (notice deadlines are unforgiving), and remember that in Ontario a pay-when-paid deferral is invalid unless they followed the notice-and-adjudication procedure to the letter. Most don't.

The fastest way to find these clauses

Reading a 60-page subcontract for one clause pattern is exactly the kind of work that gets skipped at 9pm the night before a job starts. ContractorCounter Review reads the whole document in about a minute and highlights every conditional-payment clause — plus the set-offs, time bars, and retention games that ride along with it — each with a plain-English concern and the ask to send back. US$19 per contract, and you see what it found before you pay.

This article is general information, not legal advice. Payment legislation changes, and how it applies depends on your contract and jurisdiction — for a contract worth serious money, take the marked-up review to a construction lawyer.