Subcontractor Invoice

Definition — what it is

A subcontractor invoice is the periodic billing a subcontractor submits to the general contractor for its portion of installed work, retainage, and approved changes under its subcontract. It is the upstream feed for the prime's own pay application: subs bill the prime, the prime rolls those billings into its application to the owner, and payment flows back down the chain. A subcontractor invoice is not the same as an ordinary AP invoice, because it bills progress against a subcontract schedule of values, carries retainage, requires lien waivers, and is often governed by pay-when-paid or pay-if-paid terms and prompt-payment statutes. It sits at the center of the contractor's largest cost category and its greatest lien exposure, which is why validating it, retaining correctly, and paying it in the right sequence is a discipline distinct from routine payables.

Also known as: Subcontractor Pay Application, Sub Billing, Subcontractor Payment Request, Sub Requisition

Why it matters — what it protects

Subcontractor cost is usually the largest line in a construction budget, so the accuracy of subcontractor invoices largely determines the accuracy of the job-cost report and the reliability of cost-to-complete. Billing that runs ahead of installed work, or changes billed before they are approved, distorts both the cost picture and the prime's own application to the owner.

The subcontractor invoice is the primary lien-exposure control. A subcontractor or its lower-tier suppliers can lien the project for unpaid work, so the exchange of conditional and unconditional lien waivers tied to each subcontractor payment is what keeps title clear. A prime that pays without collecting waivers can end up paying twice.

It sits inside a legal payment sequence. Pay-when-paid and pay-if-paid clauses, prompt-payment statutes, and the timing of the owner's payment govern when and whether the sub must be paid, and getting the sequence wrong exposes the prime to prompt-payment penalties or to funding subs out of its own cash before the owner pays.

It is where backcharges, retainage, and disputed scope are reconciled. The prime often needs to withhold for defective work, backcharge for cleanup or damage, or hold retainage per the subcontract, and the subcontractor invoice is where those adjustments are documented. Handled loosely, they become disputes; handled rigorously, they protect margin.

Lifecycle — how it moves

1. Subcontract SOV setup

   The subcontract's schedule of values is agreed at buyout, defining the line items the sub will bill against and the retainage terms. A vague sub SOV guarantees billing disputes later.

2. Periodic billing submission

   The sub submits its invoice for the period, showing percent-complete per line, stored materials, retainage, and any change work. Late submission delays the prime's own application.

3. Progress validation

   The prime's project team verifies the billed progress against installed work and the schedule. This is where over-billing by the sub is caught before it enters the prime's application to the owner.

4. Adjustment and backcharge

   The prime applies retainage, withholds for defective or incomplete work, and books any backcharges for cleanup, damage, or delay attributable to the sub. Documentation here is what makes the withholding defensible.

5. Lien waiver exchange

   Conditional waivers for the current billing and unconditional waivers for prior payments are collected from the sub and, where required, its lower-tier suppliers. Missing waivers hold payment.

6. Roll-up into the prime application

   The validated sub billings are consolidated into the prime's pay application to the owner. A sub billing that does not map cleanly to the prime SOV creates a reconciliation problem.

7. Payment per the sequence

   After the owner pays, or per the subcontract's payment terms and prompt-payment law, the prime pays the sub, less retainage and adjustments, within the required window.

8. Retainage release and final billing

   On completion of the sub's scope, punch closure, and final waivers, retainage is released and the sub submits its final billing, reconciling to its adjusted subcontract value.

Anatomy — the data it carries

Subcontract reference

The subcontract and its number the billing draws against, tying the invoice to agreed scope, SOV, and retainage terms.

Billing period

The period the invoice covers, which must align with the prime's billing cycle so it can be rolled up on time.

Subcontract SOV lines

The line items the sub bills against, ideally mapping cleanly to the prime SOV so the roll-up reconciles.

Percent-complete per line

The sub's claimed completion, validated against installed work before it enters the prime's application.

Work completed this period

The value the sub earned this period, the number the prime's team verifies against the field.

Stored materials

Materials delivered but not installed, requiring the same delivery and insurance proof the prime needs to bill them to the owner.

Retainage withheld

The portion held back per the subcontract, which may differ from the prime's retainage with the owner and must be tracked separately.

Change order billings

Amounts billed against approved subcontract change orders, which must be executed before they can be billed or rolled up.

Backcharges and withholding

Amounts the prime deducts for defective work, cleanup, damage, or delay, with the supporting documentation that makes them defensible.

Lien waivers

Conditional current and unconditional prior waivers from the sub and lower-tier suppliers, the control that protects the prime from double payment.

Net amount due

Work completed less retainage, backcharges, and prior payments, the figure the prime will actually pay subject to the payment sequence.

Prompt-payment clock

The statutory or contractual window within which the prime must pay after receiving the owner's payment, governing timing and penalty exposure.

Failure modes — how it breaks

Sub bills ahead of installed work

The subcontractor claims more progress than is in place, and if the prime does not validate before rolling it up, the over-billing flows into the prime's application to the owner and gets certified down, forcing an awkward correction that lands back on the sub.

Paid without collecting lien waivers

The prime pays the sub but fails to collect the unconditional waiver for the prior payment or waivers from the sub's suppliers. A lower-tier supplier then liens the project for work the prime already paid the sub for, and the prime pays twice.

Change work billed before approval

The sub bills for change order work that has not been formally executed. It cannot be rolled into the prime's application, it does not reconcile, and it becomes a dispute over whether the work was authorized at all.

Retainage mismatch across the chain

The prime holds a different retainage rate from the sub than the owner holds from the prime, and the difference is tracked poorly, so at release either the sub is short-paid or the prime releases retainage it has not yet collected from the owner.

Backcharge undocumented and disputed

The prime withholds for cleanup or damage without contemporaneous documentation, and the sub disputes the deduction. Without photos, notices, and a cost basis, the backcharge is unenforceable and the withholding becomes a claim.

Prompt-payment window missed

The owner pays the prime, but the prime does not pass funds to the sub within the statutory window, triggering interest penalties and, on public work, potential claims against the payment bond and damage to the relationship.

Metrics — how it is measured

Progress validation rate

Share of sub billings adjusted for over-claimed progress before roll-up. Measures how well the prime catches over-billing before it reaches the owner.

Lien waiver completeness

Percentage of sub payments made with all required current and prior waivers, including lower-tier, in hand. A direct measure of double-payment risk.

Subcontractor payment cycle time

Days from owner payment received to sub payment issued, measured against prompt-payment obligations.

Retainage reconciliation accuracy

Whether retainage held from subs reconciles to retainage held by the owner across the chain. Prevents releasing what has not been collected.

Backcharge recovery rate

Share of booked backcharges actually collected or withheld successfully. Low rates indicate weak documentation.

Change-billing conformance

Portion of sub change billings tied to executed change orders. Measures discipline in keeping billing behind authorization.

The AI shift — what actually changes

Conversational

You question each sub billing rather than manually cross-checking it: whether the claimed percent-complete matches field progress, whether every prior payment has an unconditional waiver on file, whether change lines tie to executed subcontract change orders, and whether the retainage held reconciles to what the owner holds, each answered from the subcontract and progress records.

Generative

The validation package and the withholding are drafted rather than assembled by hand. Given the sub billing, the subcontract SOV, field progress, and any backcharge basis, a model reports the progress variance per line, computes retainage and net due, drafts the backcharge documentation, and produces the required waiver checklist for the prime's review.

Orchestrated

The sub invoice is coordinated across the subcontract, the field, the prime application, and lien control. It is validated against installed progress, mapped to the prime SOV for roll-up, tied to executed change orders, adjusted for retainage and backcharges, and linked to the waiver exchange so nothing enters the prime's application to the owner that is not verified and protected.

Autonomous

Routine sub-billing intake runs continuously inside guardrails: mapping billings to the subcontract SOV, comparing claimed progress to field data, computing retainage and net due, tracking waivers, and preparing the roll-up for review before the prime's cutoff. Any over-claimed line, any unexecuted change billing, any missing waiver, and every payment release stay with a person.

Prompts — put it to work

Tool-agnostic and copy-ready. Adapt the specifics — thresholds, contract windows, cost codes — to your own project before you run them.

Conversational — Validating a stack of subcontractor billings before rolling them into your application.

Review the subcontractor billings received for this period. For each, compare the claimed percent-complete per line to the latest field progress and flag any line billed ahead of installed work, with the dollar amount of the overstatement. Confirm each change-order line ties to an executed subcontract change order and flag any that do not. Verify we hold an unconditional lien waiver for every prior payment to that sub and that lower-tier supplier waivers are current where required. Confirm the retainage withheld matches the subcontract rate. Give me a validation summary per sub with the specific adjustments to make before I roll these into the prime application.

What good output looks like: A per-sub validation summary naming over-billed lines with dollar amounts, unexecuted change billings, missing waivers, and retainage checks, not a generic description of sub billing.

Follow-ups:

• Which of these overstatements would flow into our owner application if I did not catch them?
• Draft the notes back to the subs whose change work is not yet executed.
• Which subs are missing lower-tier supplier waivers, and what is the lien exposure?

Generative — Preparing the validated net-due and a defensible backcharge on a sub billing.

Prepare the validated payment position for this subcontractor billing. Using the subcontract SOV and the field progress, adjust each line's billed value to supported installed progress, apply retainage at the subcontract rate, and subtract prior payments to compute net due. Then draft the backcharge for the cleanup we performed on the sub's behalf and the material damage attributable to the sub: state the basis, reference the notices and photos, quantify the cost, and deduct it from net due. Produce the required conditional and unconditional lien-waiver forms for this payment. Flag any change-order line not tied to an executed change and any missing supplier waiver.

What good output looks like: A validated net-due calculation with retainage and a documented, defensible backcharge, the required waiver forms, and flags on unexecuted changes and missing waivers.

Follow-ups:

• Rework the net due if the sub disputes half the backcharge.
• Show how this billing maps to our prime SOV lines for the roll-up.
• Produce a short cover note to the sub explaining the adjustments.

Orchestrated — Coordinating sub billings, waivers, and retainage across the chain at cutoff.

At this cutoff, coordinate all subcontractor billings for the roll-up into our owner application. Map each sub billing to the prime SOV lines it supports, validate claimed progress against the field, and identify subs that have not yet billed so I can chase them. Reconcile retainage held from each sub against the retainage the owner holds from us so we neither release early nor short-pay. Confirm the waiver position for every prior sub payment and the conditional waivers for this period, including lower-tier suppliers. Produce a single readiness summary showing what is validated, what is missing, and who owns each gap, and flag anything uncertain rather than assuming it will reconcile.

What good output looks like: A readiness summary mapping validated sub billings to the prime SOV, with retainage reconciled across the chain and every missing billing or waiver named and assigned.

Follow-ups:

• Which sub billings are not yet ready and would delay our owner cutoff?
• Show the retainage reconciliation across the chain by subcontract.
• Draft the chase notes for the missing billings and waivers.

Autonomous — Standing policy for running subcontractor-billing intake and payment sequencing.

Run our subcontractor-billing intake each cycle under these rules. On receipt, map each billing to the subcontract SOV and the prime SOV, compare claimed progress to field data, compute retainage at the subcontract rate and net due, and check the lien-waiver position including lower-tier suppliers. Prepare the validated roll-up for my review before the prime cutoff. Hold and escalate to me, with the numbers, any line billed ahead of installed work, any change billing not tied to an executed change order, any missing waiver, and any retainage that does not reconcile across the chain. Sequence sub payments only after the corresponding owner payment is received or as prompt-payment law requires. Never release a sub payment, never adjust a backcharge, and never waive retainage without my approval.

What good output looks like: A validated, reconciled roll-up each cycle, a short exception queue of over-billing, unexecuted-change, waiver, and retainage flags, and a boundary that payment release, backcharge changes, and retainage waivers always require a person.

Follow-ups:

• Show me this cycle's validated roll-up plus everything you held and escalated.
• Which subs repeatedly bill ahead of progress or submit late?

Get the full Construction AI Prompt Catalog — every prompt in the library in one document.

Maturity — locate yourself honestly

0. Level 0 — Treated like any bill

   Sub billings are handled as ordinary payables with progress unchecked, retainage and waivers tracked on side lists, and payment sequence and lien exposure managed by memory.

1. Level 1 — Structured intake

   Sub billings are logged against subcontracts with retainage applied and waivers requested, though progress validation and roll-up to the prime SOV are manual.

2. Level 2 — Validated and linked

   Billings are validated against field progress and the subcontract SOV, mapped to the prime SOV for roll-up, tied to executed changes, and waivers are tracked to each payment.

3. Level 3 — Assisted validation

   Progress variances, unexecuted-change billings, missing waivers, and retainage mismatches are flagged automatically, and backcharge documentation and net-due are drafted for human review.

4. Level 4 — Operated

   Mapping, progress comparison, retainage and waiver tracking, and roll-up preparation run unattended inside guardrails, while people own payment release, backcharge decisions, and retainage waivers.

Common questions

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

Both are conditional payment clauses in a subcontract. Pay-when-paid delays the prime's obligation to pay the sub for a reasonable time until the owner pays, but the prime must eventually pay regardless. Pay-if-paid attempts to make the owner's payment a true condition precedent, so if the owner never pays, the prime never has to, shifting the owner's credit risk to the sub. Pay-if-paid is scrutinized and unenforceable or limited in many jurisdictions, so the exact wording and governing law matter greatly.

Why collect lower-tier supplier lien waivers, not just the sub's?

A subcontractor's own suppliers and lower-tier subs can file mechanics' liens against the project for unpaid amounts even if the prime paid the subcontractor in full. Collecting waivers from those lower-tier parties, or paying them by joint check, protects the prime from paying twice, once to the sub and again to satisfy a lower-tier lien. This is a routine and important part of validating a subcontractor invoice.

How should a prime handle a disputed backcharge on a sub invoice?

Document it contemporaneously. A defensible backcharge for cleanup, damage, or delay needs written notice to the sub at the time, photographs, and a clear cost basis, deducted transparently from net due on the invoice. Withholding without that record turns the backcharge into a claim the sub can contest, and weakly documented backcharges are frequently given back, so the discipline of documenting at the time is what makes the withholding stick.

Does validating a sub invoice down affect the prime's own application?

Yes, directly. Because the prime rolls validated sub billings into its application to the owner, any over-billing left uncorrected flows upward and is likely to be certified down by the architect or lender inspector, forcing the prime to correct a line and pass the reduction back to the sub. Validating each sub billing against field progress before roll-up keeps the prime's application clean and avoids a chain of awkward corrections.