Pay-If-Paid vs. Pay-When-Paid: The Subcontract Clause That Decides Whether You Get Paid When the Owner Stalls

You finished your scope two months ago. The work passed inspection, your crew is already on the next job, and your invoice is sitting in the general contractor's accounts-payable queue. Every time you call, you hear the same line: "We haven't been paid by the owner yet — you'll get paid when we get paid."

That sentence feels like a brush-off. But whether it is legally true depends almost entirely on a single paragraph buried in your subcontract — the contingent-payment clause. Two clauses that sound nearly identical do radically different things to your money. One merely sets the timing of your payment. The other can eliminate the GC's obligation to pay you at all. If you are a subcontractor, supplier, or specialty trade contractor, knowing which one you signed is the difference between a late check and a total loss.

The Two Clauses, Side by Side​

Pay-if-paid: payment as a condition, not a promise​

A pay-if-paid clause makes the owner's payment to the GC a condition precedent to the GC paying you. In plain terms: if the owner never pays the GC, the GC never has to pay you. The entire risk of owner nonpayment shifts downstream onto your shoulders.

Typical language looks like this: "Subcontractor's receipt of payment is expressly conditioned upon and subject to Contractor's receipt of payment from Owner for Subcontractor's work." Courts generally enforce these clauses only if the condition-precedent language is clear, express, and free from ambiguity. Vague wording like "payment when received" usually will not qualify — which brings us to the second clause.

Pay-when-paid: a schedule, not a shield​

A pay-when-paid clause only addresses timing. It says the GC will pay you within a defined period after the GC receives payment from the owner — for example, "within seven days after Contractor receives payment from Owner." If the owner pays, the clock starts. If the owner never pays, the GC still owes you; payment is merely delayed for a "reasonable time," after which you can demand it.

This is the standard approach in widely used industry forms. The AIA contract documents, for example, use pay-when-paid timing language rather than condition-precedent language — a meaningful signal about what the industry considers the fair default.

How courts tell them apart​

When a payment dispute reaches a courtroom, judges look for the magic words. To create a true pay-if-paid condition, the clause generally must say explicitly that owner payment is a condition precedent to the subcontractor's right to payment, or use equally unmistakable conditional language. Anything short of that — "pay when paid," "payment out of funds received," "as and when received" — is typically read as a timing provision.

The practical rule: ambiguity favors the subcontractor. If the clause can reasonably be read either way, most courts will treat it as pay-when-paid, meaning the GC owes you regardless. GCs and their lawyers know this, which is why modern subcontracts drafted in the GC's favor spell out the condition precedent in unmistakable terms. Read your subcontract with a highlighter before you mobilize, not after the checks stop coming.

Where Pay-If-Paid Will Not Save the GC​

Even a crystal-clear pay-if-paid clause is worthless in a growing list of states that have declared these provisions void and against public policy. As of recent counts, at least eight states prohibit pay-if-paid clauses: California, Illinois, Massachusetts, New York, North Carolina, South Carolina, Virginia, and Wisconsin. Some did it by statute; California and New York got there through court decisions striking the clauses down as violations of public policy.

Virginia is the most recent major addition. Its 2022 law expressly prohibits making an owner's payment a condition precedent to paying a subcontractor, while still allowing pay-when-paid timing clauses — provided they require payment within a reasonable period not to exceed 60 days. That structure is the emerging national template: ban the risk shift, keep the schedule.

Two warnings for working subs:

1. Your state's list may have grown. Legislatures revisit this issue regularly, and courts in additional states have refused to enforce ambiguous clauses even without a statute. Check the current law in every state where you take work — the clause that was enforceable on your last job may be void on this one.
2. State law can follow federal work too. Federal projects apply their own bonding regime (more on that below), but legal analysis has noted that state conditional-payment law can still matter to federal contractors and subcontractors depending on the contract's choice-of-law provisions. Do not assume a federal job makes state protections irrelevant.

What to Do Before You Sign​

The cheapest payment dispute is the one you negotiate out of the subcontract before starting work. Use this checklist on every new agreement:

• Strike condition-precedent language. Replace "conditioned upon receipt of payment from Owner" with timing language: "Contractor shall pay Subcontractor within [7/10/15] days after receipt of payment from Owner."
• Add an outside payment date. Even with pay-when-paid language, add a backstop: "or within [45/60/90] days after Subcontractor's proper invoice, whichever is earlier." Without it, "reasonable time" becomes whatever a judge says it is, months later, at your expense.
• Preserve lien and bond rights explicitly. Never sign language waiving your right to file a mechanics lien or make a bond claim before you have actually been paid. Conditional lien waivers exchanged with each pay application are normal; advance blanket waivers of future rights are a red flag.
• Add late-payment interest. A monthly interest rate on overdue balances will not make a broke GC solvent, but it changes the economics of slow-paying you and compensates you when "reasonable time" stretches.
• Confirm the money exists. On private jobs, ask whether the project has a payment bond or how the owner is financing the work. On federal jobs over the threshold, the Miller Act requires the prime to furnish a payment bond — verify the surety's name and the bond number before you start, while everyone is still friendly.

What to Do When Payment Stalls​

If the checks stop and the "we haven't been paid yet" calls begin, move quickly and in writing. Payment rights in construction are deadline-driven, and most of them expire whether or not anyone warned you.

1. Send everything in writing. Follow up every phone call with an email restating what was promised and when. A paper trail of the GC acknowledging the debt — and blaming the owner — is useful everywhere from negotiation to litigation.
2. Protect your preliminary-notice rights. Many states require subcontractors and suppliers to serve a preliminary notice within days or weeks of first furnishing labor or materials to preserve lien rights. If you missed it, check whether a late notice still preserves partial rights — but never assume.
3. Calendar your lien deadlines now. Mechanics lien recording windows run from completion or last furnishing, often 60 to 120 days depending on the state, and foreclosure suits have their own clocks. Docket both dates the day trouble starts, not the day before they expire.
4. On federal work, mind the Miller Act's two clocks. Second-tier claimants with no direct contract with the prime must give the prime written notice of the claim within 90 days of the last date labor or materials were furnished, and any suit on the payment bond must be filed within one year of last furnishing. These deadlines are strictly applied — courts have let sureties off entirely over defective notice. Send the notice by certified or registered mail, and copy the owner, the surety, and your customer on the job.
5. Check for a state "Little Miller Act." State and municipal public projects generally cannot be liened (you cannot foreclose on a courthouse), so nearly every state has its own payment-bond statute with its own notice periods and thresholds. They resemble the Miller Act but differ in the details that determine whether your claim survives.
6. Treat lien waivers as cash-register receipts. Sign unconditional waivers only for money actually received and cleared. A signed unconditional waiver for an unpaid invoice can destroy an otherwise valid lien claim.

Bookkeeping for Contingent Payment​

Payment clauses are legal documents, but they behave like accounting problems. A receivable whose collection depends on someone else getting paid first needs different handling than ordinary trade AR. Set up your books to reflect that reality:

• Segregate at-risk receivables. Tag invoices tied to contingent-payment jobs separately from ordinary receivables so your aging report tells the truth. A 75-day-old invoice the GC will pay next week and a 75-day-old invoice gated behind an insolvent owner are not the same asset, and your cash forecast should not pretend they are.
• Forecast cash on expected timing, not invoice dates. For pay-when-paid jobs, model collection around the owner's payment cycle plus the contractual pay window — and around the outside date if you negotiated one. For pay-if-paid exposure in states where the clause is enforceable, weight those receivables for the real risk of nonpayment and line up bridge capacity (a draw on your line of credit, deferred equipment purchases) before the gap hits.
• Book an allowance for doubtful accounts honestly. If a GC is blaming the owner for months, that receivable is impaired in substance even if no one has said the word "default." A realistic reserve keeps your profit picture honest and forces the hard conversation — with your CPA, your banker, and yourself — while you still have options.
• Job-cost the waiting. Track every dollar the delay costs the job: extended general conditions, stored-material insurance, remobilization, your own time chasing payment. These costs are recoverable in many payment disputes and change-order negotiations, but only if they were recorded contemporaneously rather than reconstructed a year later.
• Calendar every legal deadline in your accounting system. Preliminary notices, lien recordings, 90-day Miller Act notices, one-year suit deadlines — these are payables of attention, and your books already track dates for everything else. Put statutory deadlines where you will actually see them: alongside the receivable they protect.

Keep Your Payment Rights as Organized as Your Work​

The lesson of every "you'll get paid when we get paid" story is the same: the subcontractor who understood the payment clause before signing — and who documented, noticed, and calendared everything after — gets paid first and argues least. Read the clause, negotiate the backstop, know your state's stance on pay-if-paid, and run your receivables like the contingent assets they are.

Maintaining clear, contemporaneous financial records is what makes all of that possible. Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data — no black boxes, no vendor lock-in. Get started for free and see why developers and finance professionals are switching to plain-text accounting.