GC not paid by the owner? A subcontractor collections workflow

The relationship problem behind an upstream-payment explanation

In a 2026 r/Contractor thread, a subcontractor describes profitable repeat work with a net-90 GC while carrying multiple jobs’ labor and materials. The poster wants to preserve the relationship but says the cash gap constrains other decisions. This is an unverified account, not evidence that net-90 terms apply to the industry.

The operational lesson is that a good sales relationship can still need a defined credit review. Separate two questions: what has happened to the existing payment, and what further exposure the company can support. Treating both as a vague request to “be patient” makes it difficult for the office to plan.

Sources: Reddit r/Contractor: Dealing with a GC that pays 90 days out (2026 discussion; anecdotal)

Identify the exact upstream pay application

Ask which owner application includes your billing, its submission period, the amount included and the current review state. Preserve the GC’s answer as a statement unless supporting records are available through the agreed process. You may not be entitled to every owner or lender record, so request the information relevant to your payment and approved communication channel.

If the GC has not included your work, ask what prevented inclusion and when the corrected package can enter review. An unsigned subcontract change, a late package and an owner funding delay require different decisions. Link the upstream reference to your own invoice without replacing your accounting identifier.

Ask questions that distinguish review from funding

“The owner has not paid” can describe several events. Ask whether the application was received, certified or otherwise approved where those steps apply. Then ask whether payment was authorized, released or received. A lender draw can have its own process, and the GC’s estimate of its timing is still an estimate.

Use the table as a fact-finding guide rather than a statement that every project uses each stage. Put unknowns in the record. If the GC cannot name a reviewer or checkpoint, that uncertainty belongs in the cash forecast and exposure discussion.

Keep contract interpretation separate from the status call

Pay-when-paid and pay-if-paid language can have materially different effects, and interpretation depends on the actual wording and governing law. Give the signed subcontract, amendments, relevant prime-contract flow-downs and payment history to the qualified reviewer. Do not let a label in an email substitute for that review.

Ask the reviewer to identify the basis for the due date, potential notice requirements and available remedies. The collector can gather event dates and communications; the adviser determines what those facts mean. Preserve both the operational checkpoint and any separately verified legal deadline.

Public projects can involve different payment mechanisms

FAR 52.232-27 contains subcontractor-payment provisions for covered federal construction contracts, including a seven-day payment provision tied to receipt for satisfactory subcontract performance. U.S. DOT’s Part 26 guidance addresses prompt payment and retainage on DOT-assisted contracts. Neither source creates a universal deadline for all commercial projects.

First establish the project type and governing contract requirements, including any applicable agency deviations. Ask the adviser or relevant contract administrator which mechanism applies and what evidence or process it requires. Do not copy a federal deadline into a private-job demand merely because both jobs involve a GC and an owner.

Sources: Acquisition.gov: FAR 52.232-27, Prompt Payment for Construction Contracts (federal clause); U.S. DOT: Official Part 26 questions and answers, prompt payment and retainage (DOT-assisted work)

Worked example: an upstream payment covers only part of your billing

Assume a fictional $40,000 net progress balance is open. The GC states that $30,000 was included and approved in the owner’s current application, while $10,000 relates to a pending change. The GC later reports receipt of the $30,000 but has not confirmed release to your company.

Route the $30,000 to a payment-release inquiry with the GC’s controller and keep the $10,000 on the change-decision path. Neither statement changes the booked $40,000 automatically. Ask accounting to verify receipts before reducing AR, and ask the qualified reviewer to determine whether the GC’s payment explanation changes any relevant contractual obligation.

If the GC promises $20,000 this week, show the residual $10,000 in that release path and the separate $10,000 pending-change question. A single date attached to all $40,000 would overstate the information the team actually has. Use conditional and confirmed amounts separately in the forecast.

Review new exposure before accepting more work

Prepare a customer view showing open progress balances, retainage, aged disputes and remaining commitments. Include projected payroll and material cash needed before expected receipts. Existing work may have contractual duties that a new bid does not, so have the responsible team distinguish them before choosing a credit action.

Potential topics for a future agreement include payment milestones, billing cutoffs, document requirements and acceptable payment methods. Deposits, joint checks, direct payment arrangements or changed terms need appropriate agreement and review. None should be presented as a unilateral fix for an existing contract.

Escalate unanswered facts before repeating the same call

Use the approved sequence: billing contact, project reviewer, controller or principal, then the authorized commercial or legal channel when appropriate. A routine follow-up should name the unresolved fact and requested checkpoint. Preserve correspondence and the submitted versions so the next person can act without reconstructing the account.

Buildalytic offers payment-status follow-up that can be reviewed for this information-gathering step. Test a GC response that identifies a missing owner approval and one that simply repeats “not paid yet.” The useful handoff preserves uncertainty and assigns the next person; it does not invent a payment date or decide whether work may be suspended.

Sources: Buildalytic: Construction payment follow-up