How Long Does a Contractor Have to Pay a Subcontractor? The Subcontractor Payment Timeline Explained
- What does the subcontractor payment timeline look like in practice?
- What do prompt payment laws require, and when do they apply?
- How do pay-when-paid and pay-if-paid clauses change the timeline?
- How can general contractors pay subcontractors faster without adding AP work?
- Pay subcontractors on a predictable schedule with Corpay
How long does a contractor have to pay a subcontractor? On federal construction contracts, a prime has seven days from the moment it receives the owner's money. On private work, the deadline comes from the subcontract first and from a state prompt payment statute second.
That two-part answer is the whole problem. A subcontractor payment timeline on a private job gets assembled out of clauses, and each clause hands the wait to a different party. Some of the delay is contractual, some of it is statutory, and a stretch in the middle belongs to nobody in particular. Sorting out which is which tells you where you have leverage and where you're simply early.
Key Takeaways
The payment clock starts when a complete pay application lands, so a missing waiver or an uncoded change order resets the calendar instead of pausing it.
Federal construction contracts carry a fixed statutory pass-through window, while private jobs default to the subcontract unless a state prompt payment act reaches them.
Subcontractors wait considerably longer than the general contractors paying them believe they do, and the gap shows up first in payroll planning.
Pay-when-paid clauses set timing. Pay-if-paid clauses try to move the risk of owner nonpayment down the chain, and state courts treat them very differently.
Retainage rides outside the progress-payment clock and settles after final acceptance, on a schedule the contract names.
What does the subcontractor payment timeline look like in practice?
Five things have to happen before a subcontractor sees money on a progress payment. The billing period closes, a pay application goes up the chain, the architect or owner's rep certifies it, the owner funds it, and the prime passes payment down to the subs covered by that draw. Retainage rides alongside the whole sequence and settles at the end.
Each stage has an owner and a source for its length, and the sources are different in kind. Two of them come out of your subcontract, one comes out of the owner's contract with the prime, and one may come out of a statute. Construction put in place ran at a seasonally adjusted annual rate of $2,210.2 billion in May 2026, according to the U.S. Census Bureau's Monthly Construction Spending release, and nearly all of it moves through some version of this sequence.
Stage | What has to happen | What sets the length |
Billing cutoff | The sub closes the period and assembles the pay app package | The subcontract's billing calendar, usually a fixed monthly date |
Pay application | The packet reaches the prime with backup, waivers, and change order documentation | The subcontract's submission deadline, plus however long the packet takes to correct |
Certification | The architect or owner's rep reviews and certifies the work in place | The owner-prime contract's review window |
Owner payment | The owner funds the certified amount | The owner-prime contract, or a prompt payment statute on public work |
Pass-through | The prime pays each sub covered by the draw | The subcontract's payment clause, bounded by a statute where one applies |
That structure is where the expectation gap comes from. Subcontractors waited 56 days on average to be paid, while general contractors believed payment went out 30 days after a pay application, according to Billd's 2025 National Subcontractor Market Report as reported by Construction Dive. Neither side is lying. The GC is counting from the day the packet cleared its own review, and the sub is counting from the day the work was done, and the difference between those two dates is the part nobody manages. Tightening it is a construction payment management problem long before it becomes a banking problem.
When does the payment clock actually start?
The clock starts at a complete pay application. Finishing the work doesn't start it, and that distinction costs subcontractors more money than any single clause in the contract, because an incomplete packet loses its place in line. It comes back, gets fixed, and re-enters the queue at the next cycle, which on a monthly billing calendar can cost thirty days for one missing signature.
A complete packet on a typical commercial job carries:
A signed AIA G702 application and G703 continuation sheet, or the owner's equivalent form
Schedule of values line items that match the approved schedule, including any executed change orders
Conditional lien waivers from the sub and from its own lower-tier subs and suppliers
Certified payroll where the job requires it, along with current insurance certificates
Stored material documentation with proof of purchase and, where required, off-site storage evidence
Vendor-master setup belongs on that list too, even though it sits outside the packet. A sub whose W-9, remit-to detail, or 1099-NEC reporting information is stale in the GC's system can clear every review and still stall in AP. The practical move is to ask the GC's AP lead which document bounces pay apps most often on that specific job, then put that document at the front of your packet. In my experience it's usually a conditional waiver from a second-tier sub, and it's late because nobody asked for it until the packet was already assembled.
Working out the real cycle from your own history, then billing against it, beats arguing about it after the fact. That kind of planning is the foundation of construction cash flow management for trade contractors, since the pay-app calendar drives payroll far more than the construction schedule does.
How do progress billing and the certification step affect timing?
Certification sits between the pay application and the owner's payment, and it's the stage with the least visibility for a subcontractor. The architect or owner's representative reviews the requested percentages against the work in place, adjusts anything that doesn't match, and certifies an amount. Progress billing works on percentage of completion, so a disagreement about how much of a line item is in place becomes a payment delay instead of a formal dispute, and it usually gets resolved by moving the difference to the next application.
Federal work puts a hard number on the owner's side of that step. On federal construction contracts, a progress payment is due within 14 days after the designated agency office receives the payment request, under the Office of Management and Budget's prompt payment rule at 5 CFR 1315.14(c)(1)(i). Private owners rarely commit to anything that specific, which is why the certification window is worth reading closely in the owner-prime contract when you can get a copy of it.
Where does retainage sit in the sequence?
Retainage sits outside the progress-payment clock entirely. The owner withholds a percentage of each certified progress payment, the prime withholds a matching percentage from each sub, and the held funds stay put until the work is complete and accepted. Nothing about the pay-app calendar releases them.
The federal rule gives a date. Retained amounts must be paid by the date specified in the contract, or absent a specified date, by the 30th day after final acceptance, under 5 CFR 1315.14(c)(1)(ii). Private contracts usually tie release to substantial completion, punch list closeout, or final acceptance, and the mechanics of holdback, step-downs, and release are covered in depth in our guide to how retainage works in construction.
What do prompt payment laws require, and when do they apply?
Prompt payment laws set a floor under the contract. They cap how long a party can hold money that has already been paid to it for someone else's work, and they attach interest when that cap is exceeded. They don't rewrite the subcontract, and on many private jobs they don't reach it at all.
The federal baseline is the cleanest example. A prime contractor on a federal construction contract must pay each subcontractor not later than 7 days from receipt of payment out of amounts paid to the contractor under that contract, with an interest penalty at the Treasury rate published under 41 U.S.C. 7109, per FAR 52.232-27. The clock keys off the prime's receipt of funds, so the sub's seven days can't start until the government has actually paid.
State prompt payment acts follow a similar shape on state and municipally funded work, and many of them extend some version of the rule to private construction. What varies is nearly everything else. The trigger event and the day count differ from state to state, the interest rate differs, and states disagree about whether the parties can contract around the rule at all. Several also condition the remedy on a written notice the claimant has to send first. A fifty-state table would be stale before it published. The method that holds up:
Identify the funding source. Federal, state, municipal, and private work each sit under a different rule set, and a federally assisted state project may sit under two.
Find the prompt payment statute for the state where the project is located, not the state where either company is headquartered.
Read your subcontract's payment clause next, since the statute usually operates as a floor and the contract can be more favorable.
Check the notice and demand requirements before you need them. Several states condition the interest remedy on a written demand that starts its own clock.
What is the difference between public and private job deadlines?
Public work generally carries a statutory deadline, and private work generally carries a contractual one. On federal and most state-funded projects, the statute names the number of days and the interest that runs after it, and the contract clause is usually written to track the statute instead of competing with it. That's why a sub on a public job can often answer the "when do I get paid" question with a date instead of an estimate.
Private jobs default to the subcontract. Where a state's prompt payment act covers private construction, the statute puts an outer bound on the payment clause, but the clause still governs everything inside that bound, including the billing calendar, the submission deadline, and the conditions on the payment. Two subs working the same week on adjacent private projects in the same city can be on genuinely different calendars, and the reason is almost always a difference in the payment clause, since the same state law reaches both projects.
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 whitepaperWhat happens when a payment is late under a prompt payment statute?
Interest starts running, usually automatically on public work and often only after written demand on private work. The interest rate comes from the statute, and it's frequently well above what the paying party earns on the cash it's holding, which is the entire point of the mechanism.
Notice requirements sit underneath the interest remedy and they're easy to miss. Preliminary notice deadlines, in particular, are counted from first furnishing labor or materials rather than from the day payment went late, so a sub that waits until a payment is 60 days overdue to start reading the statute may have already lost a remedy it never invoked. Lien and bond claims run on their own calendars alongside the statutory one, and they interact with waivers already signed on prior pay applications, which is why the conditional and unconditional lien waiver distinction matters more than it looks like it should. Honestly, how a preliminary notice interacts with the statutory interest clock is variable enough across states that I wouldn't trust a general answer to it, including this one, without checking the specific statute.
How do pay-when-paid and pay-if-paid clauses change the timeline?
A pay-when-paid clause sets timing. It says the prime will pay the sub within some period after the owner pays the prime, and courts in most states read it as a timing mechanism that gives the prime a reasonable time to pay, without erasing the obligation if the owner never pays at all. A pay-if-paid clause attempts something different. It makes the owner's payment a condition precedent to the prime's obligation, which moves the risk of owner insolvency onto the subcontractor. Enforceability varies by state, and several states void pay-if-paid clauses outright or require language so explicit that most drafted attempts fail.
Clause | What it shifts | Effect when the owner never pays |
Pay-when-paid | Timing of the prime's obligation | The prime still owes the sub, typically within a reasonable time |
Pay-if-paid | Risk of owner nonpayment | The prime may owe nothing, where the clause is enforceable and clearly drafted |
Reading your own clause carefully is worth an hour. The words "condition precedent" are the tell, and their absence is a strong sign you're looking at a timing clause. A subcontractor negotiating a new master agreement has more leverage on this language than on almost anything else in the document, because the GC's own risk position is usually unaffected by striking it on a well-funded job.
When can a general contractor legally hold back payment?
A general contractor can withhold payment for cause, and the causes are narrower than the practice suggests. Reasons that give a prime a defensible hold on some or all of a requested amount include:
Defective, incomplete, or non-conforming work identified in the certification
Missing conditional or unconditional lien waivers from the sub or its lower tiers
Change order work billed before the documentation was executed
Backcharges for cleanup, damage, or work the prime had to self-perform
Unpaid claims from the sub's own suppliers or lower-tier subs
Withholding for cause usually has to be specific, and a prime that holds the full application over one disputed line item is exposed on the undisputed remainder.
Withholding without cause is where statutory interest attaches. Holding a sub's money because the owner is slow, because the GC's own cash position is tight, or because a different job went badly gives the sub a claim under the payment clause and, where one applies, under the prompt payment statute. Change orders deserve their own attention here, since work performed on a verbal direction and billed before the paperwork catches up is one of the most common reasons a legitimate hold turns into a fight. The payment workflow behind a signed change order is worth getting right before the work starts, not after the pay app bounces.
How should a subcontractor escalate a late payment?
Escalate in order, and document each step, because each one builds the record the next one needs:
Confirm the packet cleared. Ask the GC's AP contact whether the application was certified and what amount was approved, and get it in writing.
Send a written payment demand that cites the subcontract's payment clause and the date the obligation was triggered.
Invoke the statute if one applies, in the form it requires, and start the interest running.
Preserve lien or bond rights on their own deadlines, which run independently of the payment demand.
Stop work only after checking what the subcontract and the statute require, since suspension rights are usually conditioned on notice and a cure period.
The order matters because steps one and two resolve most cases. A surprising share of late payments trace back to a packet that was never marked complete in the GC's system, and a phone call finds that in ten minutes.
How can general contractors pay subcontractors faster without adding AP work?
Slow payment costs the U.S. construction industry $299 billion, according to Rabbet's 2025 Construction Payments Report. The same survey found that 82% of contractors reported work delayed or stopped because of a payment delay, and respondents tied slow payment to an estimated 14% of total project costs. A GC paying subs on a predictable calendar is buying schedule certainty, and it's buying it at a price most owners would approve if anyone framed it that way.
Owner-side funding risk is the part a GC can't fix, and it's worth naming so the rest of the plan is honest. In the Associated General Contractors of America and Sage 2026 Construction Hiring and Business Outlook, 63% of contractors reported that an owner postponed or canceled a project in the past six months, and 37% of those cited a lack of funding or uncertainty about a funding source. When the money upstream is uncertain, no amount of AP discipline creates it. What AP discipline does is make sure that every dollar that does arrive moves down the chain immediately instead of sitting in a queue.
Four levers do most of the work on the GC side. Clean pay-app intake, so packets arrive complete and get marked complete the same day. Standardized documentation, so waivers and certificates follow one format across every sub. One approval path, so a certified application doesn't get re-reviewed by three people in sequence. And payment on the rail the sub already accepts, which is where GCs quietly lose days they think they've saved. The trade-offs among check, ACH, and virtual card are laid out in our breakdown of how construction firms pay subcontractors, and the operational work of getting subs onto an electronic rail in the first place is covered in why vendor enrollment determines a virtual card program's success.
Which controls speed up approval instead of slowing it down?
The controls that speed things up are the ones applied at intake rather than at approval. Coding a pay application to the job, phase, and cost code when it arrives means the project manager reviews a document that's already reconciled to the budget, and project-level spend visibility stops being a month-end reconstruction exercise. Routing rules that send an application to one approver based on amount and job, with a named backup, remove most of the sitting time.
Exception handling deserves a real path of its own. A packet missing one waiver should route to a coordinator who chases it, instead of sitting in an approver's queue looking like a decision. Payment verification belongs in the same conversation, since the pressure to move money quickly is exactly the condition that payment fraud schemes in construction are built to exploit, and a bank-detail change request that lands during a rushed pay cycle earns extra scrutiny.
Does paying faster pay for itself?
Often, yes, though the return shows up in three different places and only one of them is easy to measure. The measurable one is discount capture, since a GC that can reliably pay early has something to trade, and the mechanics of funding that position are worked out in our look at early-payment discounts in construction.
The other two returns are real and harder to book. Subs price risk into their bids, and a GC with a reputation for paying on the day it says it will gets sharper numbers than one that pays whenever the owner gets around to it. Deeper bidder pools follow the same logic, especially in trades where capacity is tight and good subs can choose their general contractors. Neither shows up on a line item, and both show up in the bid tab.
Pay subcontractors on a predictable schedule with Corpay
The last mile is where predictable payment plans usually break. Your ERP handles job costing, commitments, and the accounting for every one of those pay applications, and then the money has to actually move, get delivered on a rail the sub accepts, and come back into the ledger in a form your accountants can reconcile. Corpay's Procure-to-Pay solution set, which covers AP automation for construction finance teams, sits in exactly that gap.
We enroll your subcontractors and suppliers, then deliver payment across ACH, virtual card, or check based on what each vendor accepts. The funding posts back as a single transaction that reconciles to the job cost ledger. Our managed service handles the supplier outreach and the follow-up, which is the part that usually stalls when an AP team of three is also closing the month. Corpay maintains 180+ ERP integrations via API, SFTP, or file-based connections, including NetSuite, Sage Intacct, Dynamics 365, Acumatica, and QuickBooks.
If your subs are waiting on a calendar nobody controls, that's a fixable operations problem. See how Corpay AP automation shortens the pass-through step, and how virtual card payments give you a rail that pays fast and earns rebate on spend you're already making.
Frequently Asked Questions
How long does a contractor have to pay a subcontractor?
On federal construction contracts, seven days from the day the prime receives payment from the government. On private work, the subcontract's payment clause controls, subject to any state prompt payment statute that reaches private construction in the state where the project sits.
What happens if a contractor does not pay a subcontractor?
The subcontractor has a contract claim for the unpaid amount and, where a prompt payment statute applies, a claim for statutory interest on top of it. Lien and bond rights run on separate deadlines that start from first furnishing labor or materials, so those need to be preserved even while a payment demand is pending.
Can a contractor withhold payment to a subcontractor?
Yes, for cause. Defective work, missing lien waivers, undocumented change orders, and backcharges are all defensible reasons to hold a specific amount. Holding an entire application over a disputed line item, or holding because the owner is slow, is where statutory interest and a payment claim typically attach.
What should you do if a contractor does not pay a subcontractor?
Confirm in writing that the pay application was certified and for what amount, then send a written demand citing the subcontract's payment clause. If a prompt payment statute applies, invoke it in the form the statute requires, and preserve lien or bond rights on their own deadlines, which run whether or not the demand resolves.
What percentage of a contract is typically retained?
The retained percentage comes from your subcontract, and state law may cap it, particularly on public work. There's no single national figure, so read the retainage clause in your subcontract first, then check whether a statutory cap applies in the state where the project is located.
Does a pay-when-paid clause mean a subcontractor never gets paid if the owner defaults?
Generally no. Courts in most states read pay-when-paid as a timing provision that gives the prime a reasonable time to pay while leaving the obligation intact. A pay-if-paid clause is the one that attempts to make owner payment a condition precedent, and its enforceability depends on the state and on how explicitly it's drafted.
- What does the subcontractor payment timeline look like in practice?
- What do prompt payment laws require, and when do they apply?
- How do pay-when-paid and pay-if-paid clauses change the timeline?
- How can general contractors pay subcontractors faster without adding AP work?
- Pay subcontractors on a predictable schedule with Corpay
Switch to Corpay
Discover how making the move to Corpay streamlines payments and strengthens your business.
Talk to an ExpertSmarter payments. Stronger growth. Keep business moving.
Corpay powers payments for 800,000+ businesses worldwide. Let’s build what’s next for yours.