Pay-When-Paid vs. Pay-If-Paid: How Contingent-Payment Clauses Work

A pay-when-paid clause gives the general contractor a reasonable time to pay a subcontractor after the owner pays. A pay-if-paid clause makes the owner's payment a condition of the subcontractor getting paid at all. One delays money. The other can cancel it.

Both are contingent-payment clauses, and subcontract language treats them as close cousins, which is exactly why they get confused. The practical consequence of signing one instead of the other shows up months later, when an owner stops paying and a specialty trade discovers which side of that line its contract sits on.

This is an explanation of how the clauses operate, not legal advice. Enforceability turns on state law and on the exact words in your subcontract, and a construction attorney in your jurisdiction is the person who should read those words.

Key Takeaways

• Pay-when-paid is a timing mechanism. Courts in most states read it as giving the GC a reasonable period to pay after receiving owner funds, not as permission never to pay.

• Pay-if-paid is a risk-allocation mechanism. Where it's enforceable and drafted as a true condition precedent, owner non-payment becomes the subcontractor's loss.

• Enforceability varies sharply by state. Several states void pay-if-paid clauses outright or limit them by statute, and others require explicit condition-precedent language.

• Neither clause automatically waives lien rights, but both change the timeline you're working against, which makes notice deadlines more dangerous than usual.

• A GC whose own payment operation runs on time removes most of the practical sting from either clause, which makes disbursement speed a contract-risk question as much as an accounting one.

What is a pay-when-paid clause?

A pay-when-paid clause says the general contractor will pay the subcontractor after the owner pays the general contractor. Most courts read that as a timing provision, meaning the GC owes the money regardless and the clause only sets when payment comes due.

The standard judicial reading is that payment is owed within a reasonable time after the sub's work is complete and approved, whether or not the owner has funded the draw. What counts as reasonable depends on the project, the draw cycle, and the state. A GC who has been paid and still hasn't released the sub's portion is usually well past reasonable no matter how the clause reads.

A typical clause reads, "Contractor shall pay Subcontractor within ten (10) days of Contractor's receipt of payment from Owner for Subcontractor's work." Nothing in that sentence says the sub loses its money if the owner defaults. It sets a trigger and a window.

How long can a GC wait to pay under pay-when-paid?

A reasonable time, which is a legal standard rather than a number. In practice, courts have found periods of a few months reasonable on projects with slow draw cycles and periods far shorter unreasonable where the GC had already been paid.

The operational reality is more useful than the legal standard. If your GC's accounts payable process takes three weeks to cut a check after the draw lands, the clause isn't what's costing you; the payment machinery is. Slow disbursement gets blamed on contract language constantly, and it's usually a process problem hiding behind a clause.

What risk does pay-when-paid actually shift?

Timing risk, not credit risk. The sub finances the gap between finishing work and getting paid, which is real and expensive, but the obligation to pay stays with the GC.

That gap has a price. PYMNTS Intelligence's 2026 Growth Corporates Working Capital Index found that growth corporates lose roughly 4.1% of revenue chasing overdue B2B payments, which is the cost of collections effort rather than the cost of the float itself. For a specialty trade running thin margins on a handful of projects, chasing is what the office manager does instead of bidding work.

Material costs make the wait worse. The index for materials and components for construction advanced 0.6% in August 2026 and 5.1% over the prior twelve months, according to the Bureau of Labor Statistics' Producer Price Index news release for August 2026. Money owed on a March invoice buys less in September, and protecting construction cash flow through the gap is the whole discipline.

What is a pay-if-paid clause?

A pay-if-paid clause makes the owner's payment to the general contractor a condition precedent to the general contractor's obligation to pay the subcontractor. Where that clause is enforceable and properly drafted, an owner who never pays means a subcontractor who never gets paid.

The mechanism is contract law rather than construction practice. A condition precedent is an event that has to occur before a duty arises. If the event doesn't happen, the duty never comes into existence, so there's nothing to sue on. That's a different posture entirely from a payment that's owed but late.

A clause drafted to achieve that usually says so explicitly, in words like these. "Receipt of payment by Contractor from Owner for Subcontractor's work is an express condition precedent to Contractor's obligation to pay Subcontractor, and Subcontractor expressly assumes the risk of Owner's non-payment."

What makes a clause a true condition precedent?

Explicit language. Courts generally require clear words showing the parties intended to shift the risk of owner non-payment, because that's an unusual allocation and judges don't infer it from ambiguity.

Three drafting markers show up in clauses that hold:

• The phrase "condition precedent" appears by name.

• The clause states that the subcontractor assumes the risk of owner non-payment.

• The language avoids "when," "after," and "upon," which read as timing rather than condition.

All three matter. A clause that says payment is due "upon receipt of funds from Owner" is generally interpreted as pay-when-paid, however the GC intended it.

Ambiguity gets resolved against enforcement in most jurisdictions. That's a real protection, and it's also the reason contracts administrators who want an enforceable clause write it in the clunkiest possible language.

Protect cash flow on every project

Modernize AP to cut costs, speed approvals, and reduce payment risk — with the real-time visibility construction finance teams need to scale without adding headcount.

Download the whitepaper

Are pay-if-paid clauses enforceable?

It depends on the state, and the variation is wide enough that the answer for one project tells you nothing about the next. Broadly, states fall into three camps:

• Void by statute or as against public policy, treating the shift of owner-credit risk onto subcontractors as unacceptable.

• Enforceable where the condition-precedent language is explicit and unambiguous.

• Enforceable but narrowed, so the clause bars the contract claim while lien and bond remedies survive.

Public projects often follow separate rules under state prompt-payment statutes and little Miller Acts, which can override subcontract language entirely. Check the statute for the state where the project sits, not where your office sits.

How do pay-when-paid and pay-if-paid compare side by side?

Enforceability descriptions are general. State law and the specific contract language control.

The line between the two columns is thinner in practice than the table suggests, because the drafting is what decides which column a clause lands in. A contracts admin who writes "pay if paid" in the heading and timing language in the body has written a pay-when-paid clause with a misleading label.

How do these clauses interact with lien rights and retainage?

They run on separate tracks, and that's the part subs most often get wrong. A contingent-payment clause governs the contract claim against the GC. Mechanics lien and payment bond rights are statutory remedies against the property or the surety, and most states don't let a subcontract clause waive them by implication.

Retainage is a third thing again. Retainage is a withheld percentage of each approved payment, typically 5% to 10%, held back until the project reaches completion. That money is earned and owed; it's just held. A contingent-payment clause conditions the whole payment, retained portion included, on a third party's behavior.

The dangerous interaction is the calendar. Lien deadlines run from the last date of work or the last furnishing of materials, not from the date you realize you aren't getting paid. A sub sitting quietly under a pay-when-paid clause for four months can preserve a perfect contract claim and lose the lien that would have made it collectible. Understanding conditional versus unconditional lien waivers before signing the monthly waiver matters for the same reason.

How can subcontractors manage contingent-payment risk?

Start at the negotiation, because the leverage is highest before signing and near zero afterward. Ask to strike the condition-precedent language, or to cap the contingency at a fixed number of days after which payment becomes due regardless.

When the clause survives, several practices reduce what it can cost you:

• Underwrite the owner as well as the GC. Ask who's funding the project and whether there's a construction loan or a bond behind it.

• Document completion precisely, with dated photos and signed field tickets, because the reasonable-time clock starts from an event someone will later dispute.

• Calendar every statutory notice and lien deadline at contract signing rather than when payment goes late.

• Track how change orders affect payment, since unsigned change-order work is the most common category of unpaid work on a contested project.

• Price the risk into the bid where the clause is aggressive. A pay-if-paid subcontract is a riskier instrument than a pay-when-paid one and should not carry the same margin.

Cost visibility matters more than usual under these clauses, because you need to know your actual exposure on a project before deciding how hard to fight. Construction job costing that updates weekly tells you what's at stake; a job-cost report that closes monthly tells you after the decision window.

The broader market context is worth holding in mind. U.S. construction spending ran at a seasonally adjusted annual rate of $2,157.6 billion in July 2026, 3.8% below the July 2025 estimate, according to the U.S. Census Bureau's Monthly Construction Spending release. Contracting volume is when owners get slower to pay and GCs get more aggressive about pushing contingent clauses down the chain, so this is a good year to read the subcontract carefully.

What can a GC do to make these clauses less painful?

Pay faster than the clause requires. That sounds glib, and it's the single thing that most changes a subcontractor's experience of a project, because most payment delay in construction is operational rather than contractual.

The paper problem is the usual culprit. Estimates of how much B2B volume still moves on paper vary more than they should. AFP's 2025 Digital Payments Survey put checks at 26% of B2B payments, down from 33% in 2022, with 73% of organizations transitioning to electronic payments, while PYMNTS Intelligence reported in 2026 that roughly two in five commercial transactions were still tied to checks and about a third of B2B payments still went out on paper. The spread depends on whether you're counting transactions or dollars and who's in the sample. Construction sits at the high end of any of those estimates. AFP's 2022 Payments Cost Benchmarking Survey found 92% of organizations receive incoming payments by check and 86% make outgoing payments by check, and construction has moved more slowly than most sectors since.

Electronic rails have kept scaling around it. Total ACH Network volume reached 8.9 billion payments in the first quarter of 2026, up 4.8% year over year, with B2B ACH volume growing 9.4% to 2.1 billion transactions, according to Nacha's Q1 2026 ACH Network statistics. ACH's share of noncash payments by value rose from 72% to 74% between 2021 and 2024, running 39.7 billion transactions worth $104.06 trillion, according to the Federal Reserve's 2025 Federal Reserve Payments Study. A GC still cutting checks on a weekly run is adding a week of delay that no clause required.

Standardizing subcontract payment terms helps too, and how business payment terms work is worth settling across a portfolio rather than negotiating project by project. So does moving subs onto ACH payments with remittance detail attached, which cuts the follow-up calls that eat an office manager's week.

Keeping the payment chain moving with Corpay

A contingent-payment clause bites hardest when the GC's own payment operation is slow, because every internal delay lands on top of whatever the contract already permits.

Corpay runs AP automation as a fully managed service for contractors. Subcontractor invoices and pay applications get captured and coded without rekeying, approvals route to the project manager wherever the project manager is, and payment goes out across virtual card, ACH, or check depending on what each sub accepts. Customers see about 40% time saved on the AP cycle, and implementations go live in weeks.

Single-use virtual cards close after one transaction, which removes a category of payment fraud that construction sees more of than most industries. Card payments also earn rebates, and we pay out more than $800M in rebates per year to customers on spend that was going out anyway.

We're an ERP complement rather than a replacement, with 100+ ERP integrations, including NetSuite, Sage Intacct, Business Central, and Acumatica, so project-tagged payments reconcile back into job costing instead of being retyped. The construction payment management pillar covers how the pieces fit together on a portfolio of active jobs, and choosing construction payment software walks the evaluation. The working-capital case sits in how to optimize cash flow with AP automation.

Frequently Asked Questions

What is the meaning of pay when paid?

A pay-when-paid clause means the general contractor will pay the subcontractor after receiving payment from the owner. Most courts treat it as a timing provision rather than a condition, so the GC still owes the money within a reasonable time even if the owner never funds the draw.

What is an example of a pay-if-paid clause?

A typical clause reads, "Receipt of payment by Contractor from Owner for Subcontractor's work is an express condition precedent to Contractor's obligation to pay Subcontractor, and Subcontractor expressly assumes the risk of Owner's non-payment." The explicit condition-precedent and risk-assumption language is what distinguishes it.

What is the difference between pay-when-paid and pay-if-paid?

Pay-when-paid sets when payment is due; the debt exists either way. Pay-if-paid conditions whether the debt arises at all on the owner paying the GC. The first shifts timing risk to the subcontractor, the second shifts the owner's credit risk.

Are pay-if-paid clauses enforceable?

It varies by state. Some states void them by statute or as against public policy, some enforce them where condition-precedent language is explicit, and others enforce the clause while preserving lien and bond remedies. Public projects may be governed by prompt-payment statutes instead.

How long can a contractor wait to pay under a pay-when-paid clause?

A reasonable time, which courts assess case by case rather than by a fixed number of days. Project draw cycles, industry practice, and state prompt-payment statutes all factor in. A GC that has already received owner funds and still hasn't paid is usually outside the range.

Does a pay-if-paid clause shift the risk of owner non-payment to the subcontractor?

That's precisely its purpose, and where enforceable and properly drafted, it does. The subcontractor takes on credit exposure to a party it never contracted with and often never met. That's why the clause is void in several states and read narrowly in many others.

Do these clauses affect lien rights?

Generally not by themselves. Mechanics lien and payment bond rights are statutory remedies that most states won't treat as waived by implication. The practical danger is the calendar, since lien deadlines run from the last date of work rather than from the date payment goes late.

David Luther

Product Marketing Program Manager

David Luther, MBA is a product marketing program manager with years of experience in commercial banking, finance, and technology sectors, with research and writing appearing in financial publications.

Payments Automation

Risk management