Texas Notice Tracker
Start free
PAYMENT FOLLOW-UP

Texas construction payment demand letter: what to include before sending

Review a filled Texas construction payment-demand example, a $10,500 reconciled request, attachment checklist and follow-up steps separate from lien notices.

••10 min read•Texas Notice Tracker Editorial Team
Texas trade contractor reviewing payment correspondence beneath the heading Construction Payment Demand
AI-generated editorial illustration. Payment correspondence should identify the balance and requested response without overstating legal rights.

Direct answer

A construction payment demand should identify the parties and project, explain the supported unpaid balance, reference the billing history and ask for a specific response. It is not automatically a Texas statutory lien notice, and a response date you choose does not extend legal deadlines.

Decide what the letter needs to accomplish

A payment demand is useful when routine follow-up has stopped producing a clear answer. It consolidates the facts into one document that the customer can forward to accounting or management. Its immediate purpose is to obtain payment or a specific explanation of what remains unresolved.

Before writing, decide whether the problem is an incomplete invoice packet, an approval delay, a disputed deduction or a customer that has stopped responding. Those situations call for different requests. Asking for a missing approval is more useful than sending a generic threat to sue.

This guide covers administrative payment correspondence on Texas private commercial construction work. It does not supply a legal notice form or determine whether a debt is enforceable. Public projects, bankruptcy, threatened litigation and unusual contract provisions need a different review.

Reconcile the amount before describing it as owed

Prepare a dated ledger showing original billings, approved adjustments, collected and allocated payments, and the remaining amount requested. Keep proposals outside the invoice and held retainage separate. An accounting balance does not by itself prove a legally due amount.

Hypothetical example used throughout this guide: fictional Cedar Electrical LLC is a first-tier subcontractor to fictional Mesa General Contractors LLC on a privately owned Texas commercial office project, Project C-104. Invoice CE-104-03 was submitted April 1, 2026 for March ordinary electrical work totaling $18,000. A $7,000 collected receipt on April 10 was supported and allocated entirely to this invoice. Credit CM-04 for $500 was agreed and issued April 15. At the April 20 statement cutoff, the ledger request is $10,500.

A separate $2,000 change proposal CP-02 remains disputed, unapproved and unbilled; it is outside the $18,000 invoice and outside this payment request. No retainage, tax, interest, legal fees, other credits or other invoices are included. Do not increase this example's request to $12,500 or silently label the proposed change approved.

Check for money in transit or received under another reference immediately before sending. The partial-payment reconciliation checklist and customer statement guide help make each adjustment traceable. If allocation is unresolved, disclose the received money and the unresolved allocation rather than acting as if no payment occurred.

If the customer deducted an alleged correction cost, preserve the stated reason and your position separately. The Texas subcontractor back-charge guide explains the itemized records to request; a proposed deduction is not automatically an agreed credit.

RecordAmountEffect on this request
Invoice CE-104-03, April 1$18,000Opening billed amount
Collected/allocated receipt R-410, April 10−$7,000Reduces this invoice once
Agreed credit CM-04, April 15−$500Reduces this invoice once
Statement v1, April 20$10,500Current administrative request
Unbilled disputed proposal CP-02$2,000Excluded; not added to $10,500

Use a structure the customer can act on

Address the correct contracting entity and send the letter through the applicable contractual channel. An accounts-payable contact can help route the issue, but that person is not automatically the required recipient of every notice. Verify names and addresses from the agreement and current records.

Keep the opening direct: identify the project, invoice and amount requested. Then give a brief chronology with the submission date, relevant approval history and payments already credited. Attach the details rather than hiding the main request in a long narrative.

Ask for either payment information or an itemized explanation. Choose a reasonable administrative response date and label it as your requested response date. Do not represent a self-selected seven-day deadline as a universal statutory requirement.

PartIncludeAvoid
HeadingBusiness, customer and project identifiersOnly a jobsite nickname
BalanceReconciled amount and statement dateAn unexplained lump sum
HistorySubmission, approvals and creditsUnsupported assumptions about motive
RequestPayment date or itemized objectionA vague demand to respond immediately
AttachmentsInvoice and relevant supportUnrelated private project records

Filled example: a factual $10,500 payment request

This original filled outline uses the fictional facts above. It is an administrative request for review, not an attorney demand, statutory lien notice, Chapter 56 objection or ready-to-send legal form. Real recipients, contact details, contract requirements, dates and amounts need verification before use.

Date: April 20, 2026. From: Cedar Electrical LLC, accounts team. To: Mesa General Contractors LLC, the verified contract payment contact, through the agreed submission channel. Project: C-104, private commercial office electrical work. Subject: Payment status request — invoice CE-104-03 — $10,500.

Our April 20 statement shows a $10,500 remaining balance on invoice CE-104-03, submitted April 1 for March electrical work. The $18,000 invoice has been reduced by the $7,000 payment received and allocated April 10 and agreed credit CM-04 of $500 issued April 15. The enclosed statement and receipt/credit references show this calculation.

Please confirm by April 27 the amount you schedule for payment and its expected payment date, or identify each item you dispute and the supporting reason. If your records include another payment or agreed credit, please send its date, amount and remittance reference so we can reconcile it.

Unbilled change proposal CP-02 for $2,000 is excluded from this request and remains separately under review. This request adds no interest, attorney fees or other charges.

Please reply through our existing verified business contact and payment channel. April 27 is our requested administrative response date; it is not a statement of a statutory deadline or an extension of any separate notice or filing requirement.

Attachments: A1 invoice/submission record; A2 April 20 statement v1; A3 receipt R-410 and supported allocation; A4 credit CM-04 and agreement; A5 relevant March work/acceptance backup. Use the checklist below to verify the actual files, and remove any unsupported assertion before sending.

Match every assertion to a supporting record

The attachment index should allow the recipient to reproduce the request without receiving unrelated project records. Preserve the complete contract and legal-notice archive internally; include relevant extracts only when needed and reviewed. Do not disclose banking credentials, private employee data or unrelated customer records.

Before release, an authorized reviewer should confirm the correct legal entity and contractual delivery channel, statement cutoff, cash allocations, agreed credit, excluded proposal, actual attachment versions and next follow-up owner. Record unknowns instead of filling gaps with guessed approvals or upstream receipt dates.

An operational evidence packet supports review; it does not certify a debt, send a legal notice or expand the product's supported automation. Use the invoice packet checklist for billing evidence and the dispute log to keep challenged items and next actions visible.

Request assertionSupport to verifyIf the record is missing
$18,000 March invoice submitted April 1A1 invoice plus submission record and A5 scope/work backupVerify submission and scope; do not invent approval
$7,000 received and allocated April 10A3 actual receipt record and remittance/allocation supportDisclose actual cash and unresolved allocation
$500 agreed creditA4 issued credit plus evidence of agreementKeep a proposal separate from an agreed adjustment
$10,500 cutoff balanceA2 dated statement v1 tied to A1/A3/A4Reconcile the difference before sending
$2,000 CP-02 excludedSeparate proposal/change and dispute logDo not add an unapproved proposal to billed debt
Customer has not paid upstreamActual source and date, if relevantMark a reported statement; do not assert verified nonreceipt
Final letter and included attachmentsSaved sent version, index, recipients and transmission evidenceA draft or subject-line screenshot is insufficient

Keep payment requests and lien notices on separate tracks

Texas Property Code Chapter 53 has its own notice requirements. A letter asking a customer to pay is not automatically the notice required under Section 53.056. Review the monthly notice deadline guide and the notice-of-intent distinction before relying on a collection letter.

Do not postpone deadline review because someone promised to answer next week. Track the work period and required notice tasks separately from the date requested in your letter. A negotiation log is useful evidence, but it is not a replacement for that calendar.

For prompt-payment analysis, Chapter 28 uses different triggers for owner payments and downstream payments. Do not assume the subcontractor's invoice date starts every statutory clock. The Texas prompt-payment guide covers those distinctions.

Do not add an unreviewed threat to stop work, file a lien or charge legal fees. Those actions involve separate conditions. Escalation should follow a review of the contract, current law and actual project facts.

A Section 56.052 objection to further enforcement of a contingent payment clause has its own request, receipt, effectiveness and exception rules. This administrative wording does not claim to be that objection. If the response invokes owner nonpayment, use the pay-if-paid versus timing guide and preserve the exact contractual language for review.

Preserve the exact letter and assess the response

Keep the final sent version, attachments, recipient details and evidence of transmission together. If a draft changes, retain the version actually delivered. A screenshot of a subject line alone does not show what the recipient received.

When the customer responds, record the specific amount accepted, disputed or scheduled for payment. If the reply says only that payment is being processed, ask who owns the next action and when an update is expected. Keep the tone factual even when the delay is frustrating.

Forward new information to the person maintaining the ledger and deadline calendar. A payment promise should not be posted as cash received. A proposed settlement should not silently become an agreed credit.

If the response raises a legal dispute, organize the signed subcontract, relevant correspondence, work records, invoices, payments and notice history for qualified Texas construction counsel.

Continuation of the fictional example: $2,500 is actually received April 23 with written allocation to CE-104-03. Preserve the April 20 statement as v1, issue a dated v2 showing $10,500 − $2,500 = $8,000, and notify the recipient that v2 supersedes the earlier requested balance. Total collected cash is now $9,500, and $18,000 − $9,500 − $500 = $8,000. The excluded $2,000 proposal remains excluded. A promise to send $2,500 would not produce this revision.

SnapshotCumulative collectedAgreed creditInvoice open
April 20 statement v1$7,000$500$10,500
April 23 statement v2 after actual receipt$9,500$500$8,000

Decide what to do with each kind of response

If the customer identifies missing backup, supply it and preserve the corrected submission without erasing the original. If it claims a deduction, ask for the itemized basis and reconcile disputed and undisputed amounts. If it reports payment, ask for remittance details and confirm actual receipt.

If no response arrives by your requested administrative date, escalate the factual file to the person authorized to choose the next step. Do not assume your chosen response date extends a lien deadline. Use the notice calendar independently.

Payment demand letter FAQs

Can I email a routine payment request? Follow the contract and customer instructions, and preserve transmission evidence. Requirements for a statutory notice must be checked separately.

Should I attach every project document? Send the records needed to explain the request, with an index. Keep the broader archive available for review.

Does a demand letter guarantee payment or preserve lien rights? No. It documents a request; enforceability and notice compliance require separate analysis.

What if the customer pays only part? Record and allocate the collected amount, update the balance and check any accompanying settlement or waiver language before treating the matter as closed.

Related reading

PAYMENT-RISK WORKSPACE

Turn project facts into a review queue.

Keep unpaid work months, parties, invoices, documents and estimated review dates in one private workspace.

Create your free account

Official sources

  1. Texas Property Code Chapter 28 — prompt-payment framework
  2. Texas Property Code Chapter 53 — statutory notice requirements
  3. Texas Business & Commerce Code Chapter 56 — separate contingent-payment objection rules

Source note: Reviewed October 29, 2026. Verify the current statute and obtain qualified advice for a specific project or claim.