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

Two Clauses, Very Different Consequences

If you subcontract work out, your subcontracts almost certainly contain language that ties a sub's payment to when, or whether, the owner pays you. These clauses go by two names: pay-when-paid and pay-if-paid. They sound similar. In practice, they are not. Pay-when-paid shifts the timing of your payment to the sub. Pay-if-paid shifts the risk of the owner never paying from you onto the sub.

Understanding which clause you are actually writing into your subcontracts, and what it means for your obligation to pay when the owner is slow or never pays, is one of the most practical things you can do before you send a subcontract out for signature.

Pay-When-Paid: A Timing Clause

A pay-when-paid clause makes your receipt of owner payment a condition of when the sub gets paid, not whether the sub gets paid. You act as a conduit. Once owner funds arrive, the clock starts, and you must pay the sub 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. You remain ultimately responsible. The owner's nonpayment just triggers a reasonable delay, not a permanent excuse.

Here is a realistic example. Your mechanical sub completes rough-in work worth $85,000. You submit the pay application to the owner. The owner is slow and takes 45 days to fund it. The pay-when-paid clause allows you to hold the sub's check until the owner's money hits. But once it does, you 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 you, the sub gets nothing. Your 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 in your subcontract is even valid.

How to Spot the Difference in a Contract

The practical test is this: look for the phrase "condition precedent." If your subcontract says that owner payment is a condition precedent to the sub's payment, it is a pay-if-paid clause. If it says you 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 checking in your own subcontract form:

• 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 sub's cash position.

What This Means for Your Cash Flow Planning

Even a pay-when-paid clause creates a real float problem for the subs on your job. If the owner takes 45 days to pay you, and you then take 7 to 10 more days to pay the sub, the sub is carrying 52 to 55 days of unbilled labor, materials, and equipment on its 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 your application, the sub is not just waiting. The sub may be absorbing a loss.

Expect a careful sub to take a few steps before the subcontract is signed, and plan for each one:

• Asking for the owner's financial backing. A sub may request proof that the project has secured financing or that the owner has the funds committed. You do this with owners. Subs can ask you for the same assurance.
• Negotiating a cap on the pay-if-paid exposure. Some subs get the clause limited to disputed amounts only, meaning you must pay for all undisputed work regardless of owner payment status.
• Checking 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 issue the subcontract.
• Factoring the float into the price. A sub who knows it will be carrying 45 to 60 days of cost before it sees cash will build the carrying cost into its bid. Financing is not free, whether the sub borrows it or uses its own reserves.

The GC's Perspective: Using These Clauses Responsibly

When you pass 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 your 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 Writing Into Your Subcontracts

Pay-when-paid and pay-if-paid clauses are not interchangeable boilerplate. One creates a timing gap. The other can wipe out your sub's right to payment entirely. Read the specific language, check your state's enforcement rules, and expect your subs to 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.