Texas subcontractor final-payment closeout: records, retainage and releases

Finished work is the start of financial closeout

The crew leaves the site, the equipment moves to the next project and the job feels finished. The office may still be waiting for approved changes, retained funds or a corrected final payment application. Marking the whole project complete at that point can hide the work that remains.

Use separate milestones for field completion, document submission, final billing, collection and release handling. Each milestone should have a responsible person and supporting evidence. This lets the team close routine tasks while keeping a disputed balance visible.

This guide focuses on organizing a private commercial subcontractor's payment file. It does not establish completion under your contract or Texas lien law. Contract definitions, recorded documents and project events need their own review when dates or rights are disputed.

Build one reconciliation before preparing the final request

Start with the executed subcontract amount and separately list approved changes. Show payments and actual credits already applied. Keep pending changes, disputed deductions and retainage visible rather than forcing them into a single unexplained net figure.

Check the ledger against bank receipts and remittance advice. A customer email saying payment was issued is a follow-up event, not the same as collected funds. A credit promised by a supplier also needs to be distinguished from a credit actually posted.

Attach the contract versions and the current change log to the review file. Use the unpaid change-order guide for disputed extras and the back-charge guide when deductions need supporting detail.

Example: the final invoice does not settle the pending extra

Hypothetical example: a flooring subcontractor uses the amounts above. Its $16,000 ledger balance includes $8,000 identified as contractual retainage. A separate $2,500 extra remains unresolved. Before sending the final package, the office asks whether the proposed release would affect that extra and sends the wording for qualified review.

The business records the unresolved item alongside the final billing packet instead of assuming that a note on its own spreadsheet preserves every right. It also records which documents the contractor says are missing and who will supply them.

If $8,000 arrives, the office reconciles the remittance before declaring the project paid in full. The remaining $8,000 and the pending extra keep their own status. This example demonstrates file organization, not the legal effect of a particular payment or reservation.

Turn the contract's closeout requirements into a checklist

Read the actual subcontract and relevant exhibits to identify the documents required for the final application. Depending on the work, the list may include warranties, approved as-built information, operation manuals, inspection records or other specified deliverables. Do not add an invented universal checklist to a project whose contract requires something different.

For each required document, record the version, recipient, submission date and response. A file uploaded to a portal may be received but awaiting review. Keep those statuses separate so a rejected attachment does not disappear behind a green submitted label.

Identify the reason for each outstanding payment question: missing document, unapproved change, disputed work, retained funds or reported upstream nonpayment. The pay-if-paid review guide addresses the last category.

For labor extras supported by field tickets, use the T&M labor billing review to connect hours, rate support and prior billing before closing the exception.

Review releases against the actual payment event

A final invoice, a conditional waiver, an unconditional waiver and a recorded lien release serve different purposes. Keep them as separate records, identify their stated amount and scope, and check that the authorized person reviews the document before signing.

Section 53.283 prohibits requiring an unconditional progress or final waiver before payment in good and sufficient funds. Section 53.284 provides applicable waiver forms. Section 53.152 addresses furnishing a release after payment and a written request. Review the actual document and current statute with counsel.

Read the conditional and unconditional waiver guide before treating a contractor's standard form as routine paperwork. If a lien was recorded, use the release-after-payment guide for that additional task.

Save the signed document, payment support and any recording confirmation together. Do not describe a lien as released merely because someone drafted a document or sent an unsigned copy.

Keep unpaid retainage and review dates active

An accounting status such as final invoice submitted does not decide a statutory review date. Keep open retainage and ordinary unpaid balances identifiable while the completion facts and any notices are reviewed.

Use the retainage notice guide for the separate retainage question. Record where each completion or termination date came from and distinguish a reported event from a verified document.

Archive the project only when someone has reviewed unresolved items, confirmed the current financial status and assigned any continuing obligations. Warranty tasks may remain even after payment. Conversely, field work may be complete while collection tasks remain active.

• Reconcile the signed contract, changes, credits and receipts.
• Identify retainage and pending extras separately.
• Verify contract-required documents and review responses.
• Review waiver and release wording before signing.
• Record actual funds received and their allocation.
• Confirm any required release or recording step.
• Retain originals and a readable final chronology.

Use separate closeout statuses

A small status board can distinguish field work complete, documents submitted, documents accepted, final request issued, funds received and release steps completed. Keep pending changes or disputed deductions on an exception list with a named owner.

This avoids two opposite errors: archiving the job while money remains unpaid, or keeping routine field tasks open after their actual completion. Link each financial status to the final reconciliation and the relevant waiver review.

Give each closeout exception its own owner and evidence

Before archiving, list each unresolved financial or document item separately. A received payment may close a collection task while a rejected warranty attachment remains open. A pending change should retain its own status even if the undisputed base balance is paid.

Download the final-payment exception register. This blank worksheet organizes internal review; it is not a release, a legal reservation or a substitute for contract-specific advice. Keep original documents alongside the register.

Final-payment closeout FAQs

Does submitting the final invoice mean I should archive the job? No. Submission, acceptance, collection and release handling are separate milestones.

Can I include an unapproved change in the final balance? Identify its disputed or pending status accurately and obtain advice on the request. Do not label it approved just to make the closeout total simpler.

What if the customer asks for a release before sending money? Review the form and payment arrangement. Conditional and unconditional documents have different effects; do not decide from the filename alone.

What should remain in the archive? Keep the executed agreement, change records, final reconciliation, submission evidence, receipts, relevant notices and signed release records together, with any continuing tasks clearly identified.