Pay-When-Paid vs. Pay-If-Paid: What Every GC Needs to Know

Pay-when-paid and pay-if-paid sound alike but carry very different risks. Here is what contractors need to know about each clause before signing a subcontract.

EZBilling Team Jul 3, 2026 5 min read
Two Clauses, Very Different Consequences

If you subcontract work, you have almost certainly seen contract language that ties your payment to when, or whether, the owner pays the general contractor above you. These clauses go by two names: pay-when-paid and pay-if-paid. They sound similar. In practice, they are not. One shifts the timing of your payment. The other shifts the risk of never getting paid at all.

Understanding which clause you are actually agreeing to, and what it means for your cash flow, is one of the most practical things you can do before signing a subcontract.

Pay-When-Paid: A Timing Clause

A pay-when-paid clause makes the GC's receipt of owner payment a condition of when the sub gets paid, not whether the sub gets paid. The GC acts as a conduit. Once owner funds arrive, the clock starts, and the sub must be paid within a defined window, typically 7 to 10 days.

Courts in most states read pay-when-paid as a timing mechanism only. If the owner never pays, the clause does not extinguish the sub's right to payment. The GC remains ultimately responsible. The owner's nonpayment just triggers a reasonable delay, not a permanent excuse.

Here is a realistic example. A mechanical sub completes rough-in work worth $85,000. The GC submits the pay application to the owner. The owner is slow and takes 45 days to fund it. The pay-when-paid clause allows the GC to hold the sub's check until the owner's money hits. But once it does, the GC must pay. The sub does eventually collect.

Pay-If-Paid: A Risk-Transfer Clause

Pay-if-paid is a different animal. When enforced, it transfers the risk of owner nonpayment entirely onto the subcontractor. If the owner never pays the GC, the sub gets nothing. The GC's obligation to pay becomes contingent on an event that may never happen.

For a pay-if-paid clause to be enforceable, courts generally require that it be written with clear and unambiguous language. Vague conduit language is usually read as pay-when-paid. Courts look for specific wording that makes the sub's right to payment expressly contingent on owner payment. Something like: "Payment by Owner to Contractor is a condition precedent to Contractor's obligation to pay Subcontractor." That phrase, or close variations, signals pay-if-paid intent.

Not every state enforces pay-if-paid clauses. California, New York, Wisconsin, North Carolina, and several others have either banned them outright or severely restricted their enforcement. Some states require that the clause be conspicuous, set apart from other text, or acknowledged separately. Know your state's law before assuming the clause is even valid.

How to Spot the Difference in a Contract

The practical test is this: look for the phrase "condition precedent." If the contract says that owner payment is a condition precedent to your payment, it is a pay-if-paid clause. If it says the GC will pay the sub within X days after receiving payment from the owner, courts most often treat that as pay-when-paid.

A few other signals worth noting:

  • Explicit risk language: Pay-if-paid clauses often say something like "Subcontractor assumes the risk of Owner's nonpayment."
  • Absence of a backstop date: Pay-when-paid clauses frequently include a fallback, such as "within 7 days of owner payment, but no later than 60 days from invoice date." Pay-if-paid clauses often omit that fallback entirely.
  • Prompt payment act overrides: Many states have prompt payment statutes that impose hard deadlines on GC-to-sub payments regardless of contract language. A solid pay-if-paid clause in a state without such protections is a genuine threat to your cash position.
What This Means for Your Cash Flow Planning

Even a pay-when-paid clause creates a real float problem. If the owner takes 45 days to pay the GC, and the GC then takes 7 to 10 more days to pay you, you are carrying 52 to 55 days of unbilled labor, materials, and equipment on your own balance sheet. On a $500,000 subcontract, that is serious working capital exposure.

Pay-if-paid adds a layer of risk on top of that timing gap. If the project owner runs into financial trouble, files bankruptcy, or disputes the GC's application, you are not just waiting. You may be absorbing a loss.

A few steps protect you before the contract is signed:

  • Ask for the owner's financial backing. Request proof that the project has secured financing or that the owner has the funds committed. GCs do this with owners. Subs can ask GCs for the same assurance.
  • Negotiate a cap on the pay-if-paid exposure. Some subs get the clause limited to disputed amounts only, meaning the GC must pay for all undisputed work regardless of owner payment status.
  • Check the state's prompt payment law. Many state statutes override pay-if-paid clauses on public work entirely. On private projects, the protections vary. Know what applies before you sign.
  • Factor in the float when pricing the job. If you know you will be carrying 45 to 60 days of cost before you see cash, build the carrying cost into your bid. Financing is not free, whether you borrow it or use your own reserves.
The GC's Perspective: Using These Clauses Responsibly

If you are the GC passing these clauses down to your subs, be direct about what you are doing. Pay-if-paid shifts financial pain onto the people doing the work. If the owner you are dealing with has creditworthiness questions, share that context. A sub who understands the risk can price it or walk away. A sub who finds out later that the clause was enforced against them after an owner default is a sub who never works for you again, and who tells others.

Pay-when-paid is a reasonable cash-management tool. Pay-if-paid should be reserved for situations where the owner risk is real and visible, and where your contract with the owner also contains corresponding protections.

Whatever structure you use, document your pay applications cleanly. When an owner disputes a GC application and the sub asks why their check is late, you need a clear paper trail showing exactly what was billed, what was approved, and what remains disputed. Sloppy billing invites disputes that extend the float for everyone on the payment chain.

Know What You Are Signing

Pay-when-paid and pay-if-paid clauses are not interchangeable boilerplate. One creates a timing gap. The other can wipe out your right to payment entirely. Read the specific language, check your state's enforcement rules, and price the cash-flow risk into every job where these clauses appear.

Cash flow visibility starts with clean billing and cost data. EZBilling gives you both in one system built for construction.

Ready to simplify your AIA billing?

EZBilling handles G702/G703 progress billing, job costing, and compliance tracking in one platform built for general contractors.

Start 30-Day Free Trial Schedule a Demo

Related Posts