Construction payment follow-up log: turn promises into documented next actions

Why an aging report needs a conversation record beside it

An aging report shows an old invoice. It does not tell the next staff member that the reviewer requested one missing delivery ticket, that it was uploaded yesterday or that the person promising payment is not the person approving it. Without that history, the office repeats the same call and makes little progress.

Build the follow-up log beside the reconciled receivable ledger. The ledger holds financial transactions; the log holds conversations, evidence and tasks. Use the receivables aging guide to identify balances, then use this log to decide what to do about each one.

This is an original record-management workflow. It does not describe a dedicated Texas Notice Tracker collections module, promise automated collection, or replace the office’s accounting system. A shared approved spreadsheet or existing task system can carry the log if access and history are managed.

Use fields that make the next action visible

Add a balance-as-of date and the source ledger reference. When another person opens the log, they should know whether the amount includes the latest payment or credit. Keep confidential bank details and unrelated personal information out of the general task list.

Link evidence rather than copying long email threads into one cell. A short factual summary with a controlled-access record is easier to review and less likely to expose unrelated information.

Make status labels describe evidence, not optimism

Suggested office labels include not received, under review, missing attachment, approved with evidence, payment promised, receipt awaiting allocation, partially paid and disputed. Define each label in the team’s workflow. Do not use “approved” when the only evidence is a receptionist saying someone will look at it.

A promise should include the promised date and any condition. “After owner draw” is less specific than an expected calendar date and still is not a receipt. If no date is provided, leave the expectation unresolved and set a follow-up task rather than inventing one.

For missing documentation, link the invoice checklist. For a returned packet, link the resubmission workflow. The goal is to fix the actual blocker rather than add more calls.

If the blocker is an order or receiving mismatch, use the PO and invoice matching review to identify the specific exception before another follow-up.

Worked example: an $8,000 promise becomes one $2,000 receipt

Illustrative scenario: INV-410 has an $8,000 reconciled open balance on October 5. On October 8, the receiver requests a missing ticket and says payment may be made October 14 if the packet is approved. On October 9, the office sends the ticket and saves a receipt. As of the October 11 review, no cash has been received.

The last row is a future hypothetical event, not an October 11 receipt. Keep it out of the current ledger until the payment actually occurs and is allocated. Use the partial-payment guide for that later reconciliation.

Use factual follow-up wording tied to the open issue

A useful message identifies the invoice, prior event and one request. For example: “Following your October 8 request, the delivery ticket was submitted October 9. Please confirm whether the packet is complete for review and whether the conditional October 14 payment expectation remains current.” This original example asks for evidence instead of assuming approval.

If the promise date passes, record that fact and the next response. Do not delete the old promise; the history explains why the task is being escalated. If the receiver disputes an amount, save the written basis and route it to the person authorized to resolve it.

Use a payment demand letter only after the appropriate review of the actual situation. A routine status request and a formal escalation serve different purposes; copying increasingly forceful wording does not resolve a missing attachment.

Run a weekly review that ends with assigned tasks

Start with the accounting balance, then review changes since the last meeting. Identify missing documents, broken promises, unallocated receipts and unresolved disputes. Close a task when its evidence is complete, not when someone gets tired of seeing it on the list.

Texas notice and filing review uses its own facts and applicable law. This log is not a legal calendar. Link the project to the monthly notice review and preserve the work-month record even while payment conversations continue.

• Reconcile receipts and approved credits before discussing balances.
• Check whether each promise has a date and condition.
• Give every open blocker a responsible person.
• Set an internal follow-up date based on the actual situation.
• Keep the legal deadline-review queue separate and active.

Hand off an open task with a specific closure test

A useful handoff tells the next person what would close the task. “Waiting for payment” is too broad when the current question is whether an attachment reached the reviewer. Split that question from receipt allocation and leave the remaining balance visible.

Download the payment follow-up handoff sheet. Use one row per action, link controlled-access evidence and save prior promises. The CSV has no automation or statutory deadline calculations.

Payment follow-up log questions

How often should we call? Set an office cadence based on the receiver’s instructions and actual status. This guide does not prescribe a legal or universally effective call schedule.

Should “payment promised” reduce the balance? No. The worked example leaves the amount open until an actual receipt or authorized adjustment is recorded and reconciled.

What if two people contact the same customer? Use one task owner and a shared event history so both people can see the last request before making another one.

Can a log prove statutory notice was delivered? A conversation note is not a substitute for the required notice record and delivery evidence. Keep those records in the separate reviewed notice packet.