Pay-If-Paid vs. Pay-When-Paid: What Subcontractors Must Know in 2026

A pay-if-paid clause shifts the risk of the owner's insolvency from the general contractor onto the subcontractor. Payment from the owner becomes a 'condition precedent' to any obligation to pay the sub — meaning if the owner never pays, the GC never has to pay either. The sub has performed, but its right to payment is contingent on money it does not control.

A pay-when-paid clause, by contrast, addresses only timing. It gives the GC a reasonable period to pay after receiving funds, but the obligation to pay the sub survives. If the owner fails to pay within a reasonable time, the GC must still pay out of its own pocket. The risk of owner default stays where the parties can best manage it — with the contractor who selected and contracted with the owner.

Because the consequences are so severe, the law has split sharply. A growing group of states — including California, Delaware, Illinois, Indiana, Kansas, Montana, Nevada, New York, North Carolina, Ohio, South Carolina, Utah, and Wisconsin, with Virginia joining by statute in 2022 — bar or void pay-if-paid clauses as contrary to public policy. In those states, a condition-precedent payment clause is generally unenforceable no matter how carefully it is drafted.

The majority of states — more than thirty, including Florida, Michigan, and Pennsylvania — still permit pay-if-paid clauses, but with a catch: courts in those states demand that the condition precedent be expressed clearly and unambiguously. Vague language is construed against the drafter and read as a mere pay-when-paid timing provision. Texas takes a middle path, regulating contingent-payment clauses by statute so they are enforceable only when specific statutory conditions are met. Several states — among them Hawaii, Maine, Nebraska, New Hampshire, North Dakota, South Dakota, and Wyoming — have no clear rule at all.

Even where pay-if-paid clauses are allowed, the markers courts look for are explicit: phrases like 'condition precedent,' 'the subcontractor expressly assumes the risk of owner non-payment,' and 'receipt of payment by Contractor from Owner is a condition precedent to any obligation to pay Subcontractor.' Absent that kind of unmistakable language, the safer judicial assumption is that the parties intended only to set the timing of payment, not to extinguish it.

This interpretive default is the subcontractor's friend. It means ambiguity is an argument for getting paid, and that a clause buried in dense boilerplate without the magic words may not carry the weight the contractor assumes.

An important backstop: neither a pay-if-paid nor a pay-when-paid clause, by itself, waives a subcontractor's mechanic's lien or payment-bond rights. Those are statutory remedies that run against the property or the surety, not against the contractor's promise to pay. In several states, a properly perfected lien can override a pay-if-paid defense entirely, because the lien claim does not depend on the contractual condition.

That is why preserving lien and bond rights — and refusing any clause that purports to waive them in advance — matters even more when a contingent-payment clause is present. The lien may be the only path to payment when the money upstream stops.

Treat any condition-precedent payment language as a high-risk item to escalate before the redline goes out. The standard ask is to convert it into a timing provision: payment due within a set number of days of a proper invoice, with an outside date after which payment is due regardless of whether the owner has paid. Confirm the governing-law clause, because the same provision can be void in one state and fully enforceable in another.

Finally, confirm the clause does not also try to waive lien or bond rights, and that retention and final-payment provisions are not quietly tied to the owner's payment as well. The goal is simple: MGroup should be paid for work it has performed on a defined timeline, not made the unpaid financier of someone else's project.