Texas subcontractor work-month tracking: separate work dates from invoice dates

One invoice can contain several work months

A late invoice often reaches the office as one number: $18,400 outstanding. That number is useful for a collection call, but it can hide when the underlying work happened. A billing package may combine the end of one month, the beginning of another and a change item approved later. Treating its issue date as the date of every activity makes the project record harder to explain.

A work-month ledger is a practical bridge between field records and accounts receivable. It does not need to replace your accounting software. Its job is to make each billed item traceable to the labor or material record that supports it, while keeping uncertain allocations visible.

This guide describes an office workflow for private commercial subcontractors. It does not calculate your legal deadline or determine eligibility for a lien. Public projects, residential work, retainage and specially fabricated materials need separate review.

Pair this work-month record with an accounts-receivable aging review, keeping due-date payment follow-up separate from statutory notice review.

If a packet misses the receiver’s cycle, use the missed billing cutoff checklist without changing when work was actually furnished.

Use separate fields for separate events

Give every entry a project identifier, source reference and activity date. Add the calendar month as its own field. Then record the invoice number, invoice issue date and contractual payment information separately. Never overwrite the activity date when a revised invoice is issued.

Record the source of the amount as well as the amount itself. A time-and-material ticket, a schedule-of-values allocation and an agreed lump-sum billing may support different kinds of entries. Where a monthly value requires an allocation, show the method and the person who reviewed it rather than presenting a guess as measured fact.

Worked record: one $13,000 invoice, two work months

Hypothetical assumptions: a first-tier mechanical subcontractor on a privately owned Texas commercial project, original owner–contractor contract January 5, 2026. Invoice INV-119, issued September 9, combines $13,000 of ordinary labor and delivered materials. No retainage, tax, credits, disputed changes, specially fabricated undelivered materials or other invoices are included. The values below are reviewed billing allocations, not proof of legal claim entitlement.

The office's initial work-month summary assigns $8,000 to August and $5,000 to September. A $4,000 payment is actually received September 25, with written remittance specifically allocating it to the August portion of INV-119. At this snapshot the invoice remains $13,000, cumulative cash is $4,000, and open allocations are August $4,000 plus September $5,000, totaling $9,000.

Keep a separate source record for each activity, invoice submission and receipt. A September invoice date does not move August work into September. Equally, an invoice reference alone does not prove that every dollar of a later receipt belongs to one activity month. If allocation is unresolved, preserve and disclose the actual receipt while requesting clarification rather than inventing a month assignment.

The table is a control total: monthly billed allocations must sum to the invoice; allocated receipts must match the supported cash applied to it; remaining allocations must sum to the open invoice. Use the remittance-allocation guide and partial-payment reconciliation guide for other receipt situations.

Keep collection aging and notice review side by side

An accounts-receivable report asks how long an invoice has been unpaid. A notice review asks different questions about the project, parties and underlying activity. Both reports can be useful, but they should not share a single date field merely for convenience.

Texas Property Code Section 53.056 connects ordinary derivative-claimant notice timing to the month labor or materials were provided, with different residential and nonresidential rules. Section 53.054 also calls for work-month information in certain lien affidavits. That is why retaining activity-month records matters.

Use the monthly-notice guide for the separate legal review. A revised invoice or another promise of payment should trigger an update to the file; it should not automatically reset a statutory task.

HB 2237 Sections 37–38 tie that amendment framework to the original owner-contract date, not simply the date your subcontract or invoice was signed. Preserve that original-contract evidence. This guide does not apply an ordinary-work month to a retained-sum or undelivered special-fabrication claim without separate review.

Review the ledger before the month closes

Set a recurring office check that joins field records, submitted invoices and receipts. Ask the foreman about unbilled work before the accounting cut-off. A delivery that has not reached the billing package can still be important to the project history.

Start with missing records, not just large balances. Look for activities without invoices, invoices without activity support, receipts without allocation instructions and disputed changes without a written status. Assign a named person and a near-term follow-up to each gap.

Keep the daily work report and delivery-ticket file accessible from the ledger. Store original records once and reference them rather than creating several copies with conflicting annotations.

• Match each active project to its current contract and party sheet.
• Confirm which activities belong to each calendar month.
• Link invoices and receipts without replacing original dates.
• Separate unpaid retainage from ordinary billing questions.
• Record unresolved allocations and who will investigate.
• Send deadline-sensitive gaps for qualified review promptly.

Correct the record without erasing its history

Correct the source link and explain the effect; do not erase the original snapshot. In this same fictional invoice, delivery ticket DT-0831 covers $1,200 of the initial September allocation. Its actual supported delivery date is August 31, while office entry occurred September 2. The initial summary incorrectly used the entry month. A reviewer confirms the dated ticket and receiving record and creates correction C-01 on September 28.

C-01 moves that same $1,200 from September to August: August billed allocation becomes $9,200 and September becomes $3,800. Invoice INV-119 is still $13,000. The original $4,000 receipt remains allocated to August under the stated remittance, so corrected open amounts are August $5,200 and September $3,800, still $9,000 total. This is a classification correction, not another invoice, receipt or credit.

Preserve the initial summary, original ticket and receiving evidence, corrected row, reason, reviewer and September 28 correction date. The activity date remains August 31 and the entry date September 2; the correction date replaces neither. Alert the person reviewing affected notice tasks because a wrong work month can affect an earlier review date. A later correction or revised invoice does not restart a statutory clock or repair an already missed step.

If the available records do not establish August 31, retain the uncertainty and escalate it; do not backdate a daily report to obtain a preferred calendar result. For party-identity gaps, use the project information request guide.

Keep activity, entry, billing and correction dates in one traceable row

After correction, a DT-0831 row records actual supported delivery August 31, office entry September 2, invoice INV-119 issued September 9, reviewed value $1,200 and correction C-01 made September 28. Link receipt R-925 through the month/invoice allocation record; do not copy the full $4,000 receipt onto every source row and sum it repeatedly.

Store original evidence once, with stable references from the ledger. The following field checklist makes the row reviewable without claiming that a spreadsheet validates the notice or creates legal rights. The initial app automation remains limited to supported private-commercial first-tier records; this full office ledger is not a promise of an automated accounting integration.

A task should link to the actual monthly-notice review and lien timeline workflow. The ledger supplies factual inputs; content, recipients, delivery, filing and enforcement still require their separate reviews.

Work-month tracking FAQs

Can my spreadsheet use one row per invoice? Yes, for collections, but use linked detail rows when that invoice contains multiple work months. The summary should reconcile to the detail.

What if I do not know the exact activity date? Mark the uncertainty and preserve the records that establish what you do know. Ask the field team for support; do not invent precision.

Does this ledger prove my notice was valid? No. It organizes factual inputs. Required language, recipients, delivery, timing and claim eligibility remain separate questions.

When should I begin? At project setup. Adding a month field to current reports is easier than reconstructing several months after a payment dispute.