Pay application vs invoice: a guide for Texas subcontractors

Pay application vs invoice: compare the accounting basis first

An invoice and a payment application can both ask for construction payment, but their numbers may describe different periods. An itemized invoice can request only this period’s labor, materials or agreed services. A cumulative application connects the current request to the whole subcontract: revised value, work earned to date, retainage and amounts already requested or certified.

The name at the top is not enough to classify a document. An invoice can also contain cumulative information, and a customer may require an invoice alongside a pay application for its accounts-payable system. Read the agreed submission instructions and identify what each number represents before deciding which document to prepare.

ConstructionOnline’s published documentation distinguishes an invoice request from a cumulative payment application. AIA’s subcontractor application resources describe a summary used with a continuation sheet. Those are examples of billing structures, not a requirement that every Texas subcontract use one proprietary form.

For a Texas subcontractor, the contract and payer workflow decide the format

Before the first billing cutoff, ask the general contractor which documents it accepts, where they are submitted, who reviews them and how revisions must be identified. Confirm whether it needs an itemized invoice, a cumulative pay application, a separate invoice number for accounting, or a combination.

AIA publishes subcontractor-specific G702S and G703S documents as well as other payment forms. Use the version required by your agreement and obtain any required licensed document through its publisher. This guide does not reproduce an AIA form. An original spreadsheet is not automatically an accepted substitute.

For a current-period itemization, use our construction invoice template and filled example. For line-by-line cumulative progress, review the schedule-of-values guide. Choosing the correct format comes before copying totals between them.

• Confirm the named customer and subcontract reference
• Record the billing period, submission cutoff and application sequence
• Identify whether prior figures mean requested, certified or actually paid
• List the required backup and the person who can approve changes
• Keep a record of which submitted version the payer accepted

Worked example: the same $15,000 of work in two billing formats

Hypothetical example: a first-tier electrical subcontractor on a Texas private commercial job has an original $100,000 subcontract and a $5,000 approved change. Assume the agreed retainage is 10 percent on all earned work in this illustration, no stored materials, no tax or credits, and no retainage release. These are example contract assumptions, not a statement of a Texas statutory retainage rate.

At the end of the previous application, supported completed work was $35,000. This period adds $15,000, so completed work to date is $50,000. Assume all prior net applications were accepted/certified at $31,500, but the customer has actually paid only $28,000. The unpaid $3,500 belongs in the prior-application receivable record; whether it is overdue depends on the applicable terms and facts.

The adjusted contract value is $105,000. It is a ceiling/reference for this example, not the amount earned. The remaining gross work value is $55,000, calculated as $105,000 minus $50,000.

Why the $13,500 current request is not the whole unpaid balance

In the example, both formats arrive at a $13,500 current request when prepared consistently. The cash ledger tells a different, complementary story: prior net requests of $31,500 less receipts of $28,000 leave $3,500 unpaid from earlier applications. Adding the new $13,500 gives $17,000 unpaid against the net requests.

The $5,000 cumulative retained amount remains on its own record. It is not included in that $17,000 net-request balance, and it should not disappear simply because the current invoice has been prepared. A later approved retainage release needs a separately reconciled request and receipt.

Do not replace the $31,500 prior-application deduction with $28,000 of actual cash and label the resulting $17,000 as entirely new work. That would mix an earlier unpaid request with this period’s request. If the required form uses a different prior-payment basis, follow that definition and add a reconciliation that explains what is already billed, certified and paid.

AIA’s G702 completion instructions distinguish previous certificates when deriving the current application amount. Keep the same discipline when reviewing a customer-specific form: prior certification and bank receipts need separate labels. Use the progress-billing reconciliation guide and partial-payment guide for the related records.

Build the supporting packet around the requested amount

Start with the payer’s actual checklist rather than a universal attachment list. Tie each billed line to an approved scope, a measured quantity, a signed labor ticket or another agreed source record. For a progress application, reconcile the same line from the previous accepted version to this period’s version.

If an invoice accompanies the application only to create an accounting reference, label it with the same application number, period and net request. Tell the reviewer that the documents support the same request; they are not two amounts to pay. Keep the filenames and submission message unambiguous.

Waivers and affidavits can involve different legal statements. In Texas, use the applicable payment-waiver framework and verify the transaction before signature. The Texas conditional and unconditional waiver guide includes a separate field-by-field progress-waiver review.

• Subcontract and approved change references
• Current and previous accepted application identifiers
• Updated SOV or supported invoice itemization
• Required labor, delivery or stored-material backup
• Separate retainage record and any agreed release evidence
• Requested waiver documents with the matching payment facts
• Submission receipt, review comments and accepted revision

Correct a rejected submission without creating duplicate receivables

Suppose the customer rejects the $13,500 request because an approved change reference is missing. Correct the supporting record and identify the resubmission as a revision of the same request. Record which version it replaces. Do not leave both versions as separate unpaid invoices simply because two files were emailed.

If approval changes the amount, document the actual difference and the agreed adjustment process. Keep the original submission and review trail; avoid silently editing historical records so that nobody can reconstruct what was requested. Follow the rejected-invoice resubmission workflow.

When money arrives, use the payer’s remittance and the approved allocation to identify the invoice or application being settled. A deposit with no allocation is not evidence that every earlier request has been paid. Reconcile unclear remittances before changing balances.

Keep billing dates separate from Texas notice and lien review

Sending a pay application, obtaining approval or correcting an invoice does not by itself establish that a Texas statutory notice or filing requirement has been satisfied. A request for payment and a statutory claim-preservation step are different records.

Keep the actual work month, project type, contractual relationships, original-contract date and recipient information available for separate legal review. Do not automatically replace the work month with the date an invoice was approved or resubmitted. Start with the monthly-notice workflow and get qualified Texas construction advice for a live claim.

Texas Notice Tracker organizes invoices, payments, evidence and supported informational review dates. It does not certify a payment application, issue an official AIA document, serve a statutory notice or guarantee that a claim is preserved.

Before submission: a short pay-application vs invoice check

• The document format matches the agreement and payer instructions
• The period and application or invoice number are consistent
• Current-period work is not confused with cumulative earned value
• Approved changes and the adjusted contract value reconcile
• The retainage base and amount follow the reviewed contract assumptions
• Prior applications/certificates and actual receipts have distinct records
• A companion invoice is clearly identified as the same request
• The net request matches supporting schedules and reviewed attachments
• Unpaid earlier requests and held retainage remain visible
• Notice and legal-review tasks are tracked separately from billing approval

Pay application vs invoice: frequently asked questions

Is a pay application the same as an invoice? Both can request payment. A pay application usually includes a cumulative project accounting and supporting package; an invoice may be a simpler current-period bill. The actual agreement and document content determine what must be submitted.

Can a subcontractor submit both? Yes, when the payer’s process requires both. Identify them as documents for the same request and reconcile their amounts so the accounts team does not book two separate charges.

Must every construction invoice use an AIA form? Do not assume that. Check the agreement and submission requirements. If an AIA document is required, obtain the appropriate document and follow its instructions rather than relabeling a generic invoice.

Does a payment application prove the customer has paid? No. Submitted or certified amounts and actual receipts are different records. Save remittance and bank evidence and reconcile the payment allocation.

Does this comparison replace a Texas lien notice? No. Billing documents do not replace a separate review of statutory notices, delivery and filing requirements.