Pay-When-Paid vs. Pay-If-Paid: What's the Difference and Why It Matters

The Most Dangerous Three Words in a Contractor Agreement

"Pay-when-paid" and "pay-if-paid" are two clauses that every subcontractor needs to understand cold before signing anything. They're easy to confuse, and contractors get burned by this mix-up every year — sometimes for tens of thousands of dollars.

Here's the plain-English version of each one.

Pay-When-Paid: A Timing Provision

A pay-when-paid clause tells you when the general contractor (GC) will pay you — not whether they will.

It looks like this:

"Payment to Subcontractor shall be made within 7 days of General Contractor's receipt of payment from Owner."

This means the GC is using the Owner's payment to the GC as a scheduling trigger for paying you. The GC still owes you the money — they're just telling you it'll come after they get paid upstream.

The critical part: In most states, courts interpret pay-when-paid clauses as a timing provision only. The GC can delay payment while they chase the owner, but they can't use it as a permanent excuse to withhold your money forever. Eventually, you'll get paid.

Pay-If-Paid: A Risk Transfer

A pay-if-paid clause is different — and far more dangerous.

It looks like this:

"Payment to Subcontractor is expressly contingent upon General Contractor's receipt of payment from Owner. If Owner fails to pay General Contractor, Subcontractor shall have no claim against General Contractor for such amounts."

See that last sentence? That's the trap. This clause attempts to transfer the Owner's non-payment risk entirely onto you, the subcontractor. If the Owner goes bankrupt, disputes the work, or simply refuses to pay the GC — you get nothing, even if your work was done perfectly.

Courts in some states enforce these clauses literally. In others, they refuse to enforce them unless the language is very specific. But you don't want to be in a courtroom arguing about it.

How to Tell Them Apart in a Contract

Look for these signal phrases:

| Pay-When-Paid | Pay-If-Paid | |---|---| | "when received" | "contingent upon receipt" | | "within X days of receipt" | "if and only if" | | "upon payment by Owner" | "no obligation to pay unless" | | Timing language | Conditional language ("if", "only if", "contingent") |

The word "contingent" is your biggest red flag. So is any language that says the GC has "no obligation" to pay you if the Owner doesn't pay them.

What States Say About It

Several states have passed laws that limit or eliminate pay-if-paid enforcement:

• California, Wisconsin, and a handful of others have statutes that make pay-if-paid clauses unenforceable in construction contracts
• Texas, Florida, Georgia and many others allow them — but courts often require extremely clear language to enforce them
• Even where they're legal, judges sometimes refuse to enforce vague pay-if-paid language

Know your state's rules. But don't rely on them — a court battle is expensive even when you win.

What to Do When You See These Clauses

If you see pay-when-paid: This is generally acceptable, but add a backstop. Negotiate a maximum delay — "in no event later than 30 days after Subcontractor's invoice" is standard protective language.

If you see pay-if-paid: Push back immediately. Try to:

1. Delete the clause entirely
2. Replace it with pay-when-paid + a 30-day cap
3. At minimum, add language that limits the contingency: "Payment is contingent upon receipt from Owner, but in no event later than 90 days from invoice date"

If they won't negotiate: Price the risk into your bid. A pay-if-paid contract is riskier than a standard one — it should cost more.

The Bottom Line

If your contract says anything close to "we'll pay you if we get paid" — that's a pay-if-paid clause, and you're taking on risk that belongs to the GC. Know the difference, flag it before you sign, and negotiate from there.

Upload your contract to ContractDoctors and our AI will flag pay-when-paid and pay-if-paid clauses automatically — and tell you exactly what the language means for your cash flow.