Texas subcontractor invoice checklist: build a payment-ready packet

What belongs in a subcontractor invoice packet?

A general contractor's accounting team should be able to match your invoice to the subcontract without calling the field superintendent to translate it. Start with the legal business name used in the agreement, a unique invoice number, the project identifier and a short description of the billed work. The jobsite nickname alone may not distinguish two phases on the same property.

This checklist is an operational starting point for Texas private commercial projects, not a universal legal form. Read the actual billing provisions, purchase order and portal instructions. Some customers require a schedule of values and a pay application; others accept an invoice with approved tickets. A visually polished PDF can still be incomplete if a required attachment is missing.

Assign one person to assemble the packet and another to check it when staffing allows. A five-minute review of the recipient, period, math and attachments is usually easier than reconstructing a rejected submission several weeks later.

If the reviewer returns a complete or incomplete packet, follow the rejected-invoice resubmission checklist and preserve both original and revised submission evidence.

For an approved adjustment, use the construction credit-memo workflow to avoid reducing the same invoice twice.

Build a payment compliance workflow with evidence for each step

Use payment compliance as a specific checklist, not an overall green status. Separate the customer’s contractual submission requirements, internal approval controls, payment reconciliation and statutory notice review. Acceptance by a billing portal can complete a submission task while an unpaid-work notice question remains open.

Assign one owner and one closure record to each task. If an attachment is missing, the closure record is the corrected packet and acceptance evidence. If payment is promised, keep the task open until actual funds are reconciled. A reminder helps the reviewer return to the file; it does not establish legal compliance.

Keep the work-month record beside the invoice and the follow-up log beside the open balance. Use the retainage basics guide when the request includes a held amount.

Use a construction invoice template that matches the packet

For supported current-period items, use the construction invoice template and filled example. The workbook separates quantities and rates from the supported hold, reviewed tax, approved credit and actual receipts allocated to that invoice.

Keep the job’s required application format as the controlling submission record. A current-period itemized invoice, cumulative progress application and account statement are different records. Do not add an older unpaid request into a new invoice merely to show the full customer balance.

Before sending a workbook copy, replace sample details, reproduce the totals and connect each line to its supporting record. The filename, invoice identifier, work period and version in the submission log should identify the same request.

Choose the required format first with the pay application vs invoice comparison. A supporting invoice worksheet should not become a second new payment request for the same work when the customer requires a cumulative application.

Check the identifiers before the numbers

Use the customer entity that contracted with your business, and identify its billing contact separately. The project owner, general contractor and property manager may be different entities. Do not change the bill-to customer merely because someone else handles the payment portal.

Include the project address and subcontract or purchase-order reference where available. Put the billing period on the invoice, but preserve actual work dates in the supporting records. An invoice created in October can include September work; those dates answer different questions.

Payment instructions should identify an approved payment method without exposing more banking information than necessary. Verify any requested bank-detail change through a known contact using an established channel rather than relying on a reply to the change request.

Separate current work, changes and retainage

Show the amount requested for this billing period, previous billings, approved changes and retainage in a way that can be reconciled. Avoid combining disputed extra work with the base amount under a single unexplained line. A reviewer needs to see which amount has approval support and which item needs a decision.

For illustration, assume $20,000 of current base work and a $3,000 approved change, with contractual retainage of 10% applied to both. Gross earned work is $23,000, retained funds are $2,300, and the current requested payment is $20,700. This example assumes that retainage basis; use the actual contract on a real job.

A pending $1,500 proposal is not included in that approved-change total. Keep it in a separate pending-change schedule with its own supporting records. Our guide to unpaid change orders in Texas explains how to organize that approval trail.

Do not present contractual retainage as an unexplained overdue deduction. Use the retainage notice and recordkeeping guide to plan a separate review of retained balances.

Attach enough evidence to make review practical

Match each billed line to a useful source: a signed delivery ticket, approved time-and-material record, quantity calculation or progress photograph. Keep the full archive internally, but send a navigable packet. Two hundred unlabelled photos may make a valid request harder to assess.

Use filenames that identify the project, date and subject. A short attachment index can explain that Exhibit A supports the installed quantity while Exhibit B supports the approved change. Confirm that the documents actually open and that the submitted PDF is readable on an ordinary screen.

If the customer requires a waiver, check its scope and payment condition before signing. Treat waiver review as a separate step, not a routine attachment tick-box. See conditional and unconditional Texas lien waivers for the distinctions.

• Check totals against the invoice register.
• Match the billed scope to supporting records.
• Label approved and pending changes separately.
• Review requested waiver language and amount.
• Remove unrelated customer documents before uploading.

Preserve submission and correction history

Save the exact invoice and attachments sent, the submission date, the destination and any portal confirmation. An internal status of sent should identify an actual transmission record. If a portal rejects the packet, save that rejection and assign an owner to correct it.

Keep the original invoice number when a customer requests a correction unless your accounting process requires a replacement. Make the revision clear and explain whether it supersedes the previous version. Avoid two active receivables for one billing event.

Chapter 28 distinguishes an owner's qualifying payment request from downstream payment triggers tied to upstream receipt. An invoice date alone therefore does not establish every statutory due date. Read the Texas prompt-payment guide before treating a billing term as the legal deadline.

Record the date the customer acknowledges a complete packet separately from the original submission date. That preserves the facts without assuming that an administrative rejection resets every contractual or legal clock.

Make the next action specific

At each follow-up, ask a question that the recipient can answer: Is the packet complete? Which line is disputed? Who must approve it? What payment date is currently expected? Record the reply and assign a follow-up date rather than leaving the invoice in a general waiting folder.

If payment arrives, reconcile it to the invoice before changing its status. Use the partial-payment workflow when the remittance covers only part of the balance. If the balance remains unresolved, prepare a factual construction payment demand.

Maintain a separate calendar for work-month and notice review. Section 53.056 addresses notices for certain claimants other than original contractors. An ordinary invoice should not be assumed to satisfy it.

Complete fictional packet: a $20,900 subcontractor payment request

Original fictional example: Cedar Trade Services bills Oak Commercial Builders for September 1–30, 2026 electrical work on project TX-1046, a private commercial fit-out. The subcontract reference is SC-1046-E and the customer reference is PO-1046-08. These names, identifiers and amounts are examples, not real customer records.

Assume this is the first request: $20,000 of supported base work plus approved change CO-02 for $2,000 gives $22,000 gross current billing. The fictional subcontract applies 5% retainage to both items: $1,100 held and $20,900 requested. For this example only, assume the tax review supports $0 tax and there are no approved credits or prior receipts. Real tax treatment and retainage terms must be reviewed separately; the sample rates are not defaults.

Pending proposal CO-03 for $3,000 remains outside the approved $22,000 billing. List its status separately so a reviewer can see it without treating it as approved or requesting it twice. Record actual work dates through the work-month ledger, even if the invoice is prepared in October.

Give the submitted packet one version, TX-1046-INV-001-v1, and an attachment index that connects each billed amount to its source. The filenames below illustrate an orderly packet; follow the actual customer’s file-type, naming and portal requirements. Keep unrelated customer records and sensitive payment credentials out of the upload.

The construction invoice workbook and filled example can support a current-period invoice. Use the prescribed application if the agreement requires one. Before applying any real tax amount, gather the evidence described in the construction sales-tax review guide.

Missing-document checks before the packet leaves the office

Compare the actual files with the customer’s requirements, not merely the attachment filenames. Open the outgoing PDF, check legibility and confirm that its project, period and version match the invoice. A file named approval is not evidence that the billed scope was approved.

Use the table to assign the next action. When something is unresolved, record the owner and the missing evidence. Follow the agreed submission rules; do not invent approval, backdate a document or describe an incomplete packet as accepted. If the receiver allows a partial submission, preserve that instruction and identify what remains outstanding.

• Confirm the correct billing entity, receiver, project and work period.
• Reconcile base work, approved changes, retainage, reviewed tax and credits.
• Identify pending changes without including them as approved amounts.
• Open every required attachment and check its scope and legibility.
• Assign each unresolved item an owner; save the exact version actually sent.

Correction example: replace the packet without duplicating the invoice

Continue TX-1046-INV-001-v1. The portal returns receipt R-482 but then rejects the packet because the CO-02 approval attachment is missing. R-482 proves submission, not acceptance. Save the rejection message, affected item and original packet, and assign the project manager to locate the approval.

The reviewer confirms that the $2,000 change was already authorized and supplies the missing approval. Because the example’s billed work and amount do not change, v2 remains the same $20,900 request. Record a revised submission date, attach the approval and corrected index, and identify v2 as superseding v1. Ask the receiver how to mark the earlier version superseded; keep one receivable for this billing event.

A concise fictional resubmission note is: TX-1046-INV-001-v2 replaces v1; added the existing CO-02 approval and updated the attachment index; requested amount remains $20,900. Please confirm the replacement is complete and the prior version is superseded. This is a packet-identification example, not a message sent to a customer.

If the actual correction changes the approved scope, amount, tax or credit, reconcile that change before submitting and follow the accounting process for adjustments. Do not keep the number unchanged merely to match this example. Preserve the review decision and the link between original and replacement records.

Use the full rejected-invoice resubmission workflow for the correction history. Then record the receiver’s completeness response, dispute details and next owner in the payment follow-up log. An accepted packet or a promised payment should not be recorded as collected funds.

Invoice checklist FAQs

Do I need one particular Texas subcontractor invoice template? This guide does not prescribe a mandatory template. Use the form and supporting packet required by the agreement and applicable project rules.

Should I delete a rejected invoice? Preserve the submission history. Mark the rejection, correction and replacement clearly so your ledger does not count both versions.

Does a professional PDF guarantee faster payment? No. It can reduce avoidable clarification, but funding, disputes and contractual issues may still prevent payment.

What should I check before pressing send? Confirm the parties, project, dates, calculations, attachments, recipient and saved copy. Then assign the next follow-up owner.