Pay-When-Paid vs. Pay-If-Paid: The Subcontract Clauses That Shift Owner Risk
Pay-when-paid and pay-if-paid are two contract clauses that appear in subcontracts and look nearly identical on a casual read. Both say that the GC's payment to the sub depends in some way on the GC getting paid by the owner. The difference — and it's a big one — is whether the owner's payment is a timing condition (pay-when-paid) or a fundamental precondition to the sub's right to collect at all (pay-if-paid).
A pay-when-paid clause says the GC will pay the sub within a reasonable time after receiving payment from the owner. The sub still gets paid even if the owner never pays — it just might take longer. A pay-if-paid clause says the GC will pay the sub only if the owner pays the GC. If the owner never pays, the sub never gets paid, even if the sub did the work perfectly. The difference is the difference between slow payment and no payment.
Pay-when-paid clauses provide that the GC will pay the sub after receiving payment from the owner. Courts across most US jurisdictions have interpreted these clauses as timing provisions — they affect when the sub gets paid but not whether. If the owner doesn't pay within a reasonable period, the GC still has to pay the sub out of their own funds after that reasonable time has passed.
The 'reasonable time' is the key concept. It's a flexible standard that depends on the nature of the project, the reasons for the owner's non-payment, and the GC's ability to pursue collection. On a typical commercial project, a reasonable time might be 60-90 days beyond normal payment terms. On a project where the owner is disputing the work, reasonable time may extend longer. But it does not extend indefinitely, and eventually the GC's obligation to pay the sub becomes absolute.
Pay-if-paid clauses are different. They treat the owner's payment to the GC as a condition precedent to the sub's right to collect. If the owner never pays, the sub never gets paid — the clause shifts the owner's payment risk entirely from the GC to the sub.
For the clause to be enforced as pay-if-paid, courts generally require very specific language. Clauses that say 'the subcontractor shall be paid when the contractor is paid' are usually interpreted as pay-when-paid even if the GC intended them as pay-if-paid. Clauses that explicitly state that owner payment is a 'condition precedent' to the GC's obligation, and that the sub assumes the risk of owner non-payment, are more likely to be enforced as pay-if-paid.
Subs who see language like 'condition precedent,' 'condition of payment,' or 'sub assumes the risk of nonpayment by the owner' should treat these as red flags. This is pay-if-paid language, and signing a subcontract with this language means accepting the risk that a perfectly-performed project could still result in zero payment.
US states have taken different positions on pay-if-paid enforceability, creating a patchwork legal landscape that matters when multi-state contractors are negotiating.
Approximate state positions on pay-if-paid enforceability
- Enforceable with specific language (most states) — pay-if-paid clauses are enforced if the language clearly states the condition precedent
- Statutorily prohibited (several states including California, North Carolina, New York, Wisconsin) — state statutes expressly prohibit or limit pay-if-paid clauses
- Limited enforcement — some states enforce pay-if-paid only against specific types of claimants or in specific circumstances
- Public policy exceptions — even in enforceable states, courts sometimes refuse enforcement when the GC's conduct contributed to the owner's non-payment
California's Civil Code §8122 is a frequently-cited example — it makes pay-if-paid clauses void in construction subcontracts as against public policy. Subs working on California projects have statutory protection against the clause regardless of what the subcontract says. Other states have similar protections; still others enforce pay-if-paid vigorously when the language is clear.
A critical nuance: pay-if-paid clauses generally only affect the contractual payment obligation between the GC and the sub. They do not extinguish the sub's mechanic's lien rights against the property. A sub who is barred by pay-if-paid from collecting from the GC may still be able to file a lien against the property and collect from the owner directly.
This is one reason mechanic's lien rights matter so much on private construction work. The contractual payment chain (owner → GC → sub) can be disrupted by pay-if-paid, but the statutory lien right (sub → property) operates independently. Subs working on projects with pay-if-paid clauses should pay special attention to lien notice and filing deadlines, because the lien may be their only collection mechanism if the owner goes sideways.
Identifying which clause is in a given subcontract is a matter of reading the language carefully. Here are the typical patterns:
Get AP insights in your inbox
Get our weekly roundup of AP automation tips and industry news. No spam, ever.
No spam. Unsubscribe anytime.
Clause patterns to recognize
- Pay-when-paid language — 'Contractor shall pay Subcontractor within X days after receipt of payment from Owner' (no condition-precedent language)
- Pay-if-paid language — 'Payment by Owner to Contractor is a condition precedent to Contractor's obligation to pay Subcontractor'
- Aggressive pay-if-paid — 'Subcontractor expressly assumes the risk of nonpayment by the Owner'
- Mixed language — some subcontracts have multiple provisions that interact ambiguously, which courts generally interpret against the drafter (usually the GC)
Subs in strong negotiating positions can push back on pay-if-paid language. Common approaches include:
How subs negotiate payment clauses
- Request pay-when-paid with a backstop — 'within 7 days of receipt, but in no event later than 90 days after invoice'
- Carve out GC-fault situations — if the owner's non-payment is due to GC performance issues, sub still gets paid
- Preserve lien rights explicitly — clause doesn't waive lien rights or bond claims
- Add good-faith collection obligation — GC must diligently pursue the owner for payment, not just sit on a claim
- Request progressive reduction — pay-if-paid for the first 30 days after owner-payment delay, pay-when-paid thereafter
Pay-if-paid exposure is not a theoretical concern. Owner payment problems happen — owner bankruptcy, major project disputes, funding issues on development projects. On any given project, the base-rate risk that the owner fails to pay the GC in full is small but not zero; a GC with a pay-if-paid subcontract who faces owner non-payment pushes that risk onto the sub.
For sub finance teams, pay-if-paid subcontracts are higher risk than pay-when-paid subcontracts, and the internal credit decision should reflect that. The owner's financial health becomes a direct sub concern under pay-if-paid — requesting pre-qualification documents on the owner (financial statements, funding evidence) becomes a standard precaution, not an unusual ask.
For GCs using pay-when-paid or pay-if-paid subcontracts, AP workflow has to track which clauses apply to which subs. When an owner delays payment, the AP team needs to know which subs get paid anyway (pay-when-paid after a reasonable time) and which get held (pay-if-paid under the clause). Getting this wrong either triggers a breach of the pay-when-paid timing obligation or produces unnecessary payments in violation of the company's legal rights.
For sub AP teams, understanding which clauses apply to each incoming GC relationship is a credit-policy matter. A sub with a heavy concentration of pay-if-paid subcontracts has more embedded risk than a sub with pay-when-paid relationships, and cash planning should reflect that difference.
Pay-when-paid and pay-if-paid are not interchangeable contract features. One is a timing provision that affects payment speed; the other is a risk-allocation provision that can deny payment entirely. Subs who sign pay-if-paid subcontracts assume the owner's payment risk — a meaningful exposure that should be priced into the bid, documented on the sub's credit analysis of the owner, and protected with diligent lien-rights practice. The clause language looks similar; the commercial consequence is dramatically different.
Written by
Jordan Patel
Compliance & Legal
Former corporate counsel specializing in construction contracts and tax compliance. Writes about the documentation layer — COIs, W-8/W-9, certified payroll, notice-to-owner deadlines — and the legal backbone behind audit-ready AP.
View all posts