Construction invoice dispute log: separate the challenged amount from the next action

“Invoice disputed” is too vague to run a payment review

A San Antonio drywall subcontractor receives a short message: “We have an issue with this invoice.” One office employee marks the whole balance disputed. Another continues sending reminders for the full amount without asking what is wrong. A week later, nobody can explain whether the problem is a missing attachment, a quantity disagreement or an alleged back charge.

Start by recording the actual objection in neutral language. Link the original message and identify the line, quantity or condition the customer challenged. Avoid conclusions such as “customer refuses to pay” when the only evidence is a request for supporting documents.

The payment follow-up log tracks contacts and promises. This dispute log adds the disputed issue, each party’s stated amount and the evidence needed to resolve it. The two records should share invoice references without becoming duplicate financial ledgers.

Classify the issue before assigning the next action

A returned attachment is normally a packet-completeness task. A disagreement about installed quantities is a scope or valuation issue. An alleged damage deduction needs the supporting charge and contract review. Labeling all three “resubmit” can hide the actual decision that is required.

For missing fields or attachments, use the rejected-invoice resubmission guide. For deductions, use the back-charge record checklist. Neither an internal category nor a customer’s portal status establishes the legal validity of an objection.

Keep the claim, objection and resolution history visible

Use one issue ID for each distinct objection. Record the project, invoice version, date received, claimed amount, customer’s stated amount, questioned line, source evidence, response owner and next review date. Add a resolution field that shows who approved the outcome and which ledger transaction, if any, implemented it.

The claim field should preserve what your business submitted. The customer-stated field should preserve what the customer said. A third field can hold your reviewer’s proposed resolution. This avoids turning an allegation into an accepted credit just because a spreadsheet needs a smaller open balance.

Store evidence links rather than pasting entire email threads into every row. Use precise file labels and access controls. Keep personal contact information limited to the people who need it for the payment task.

Worked example: a $12,000 invoice with one challenged line

Original fictional example: the subcontractor claims $12,000. The customer says $9,000 is accepted and challenges a $3,000 finish-work line. A verified $5,000 payment is received and applied to the accepted portion of this invoice. Assume no retainage, credit or other deduction in this example.

The ledger shows $7,000 still open. The operational log separates $4,000 remaining from the customer-stated accepted portion and $3,000 in the challenged portion. The log does not authorize withholding, calculate statutory interest or determine whether the customer’s objection is a good-faith legal dispute.

A useful next action is specific: “Project manager to compare the disputed finish-work line with the dated field photographs and signed scope clarification by Wednesday.” A generic “follow up” leaves the office without a decision owner.

Keep collection decisions separate from legal deadlines

Texas Property Code Chapter 28 addresses prompt payment and contains provisions involving good-faith disputes. The applicable framework depends on the project and facts. Do not use an internal dispute label as permission to withhold a particular amount, suspend work or abandon a notice review. Have the actual contract and dispute reviewed by qualified Texas counsel.

The statute also treats Chapter 53 rights separately. Maintain the work-month record and monthly notice review while the office negotiates the invoice. A payment promise or scheduled meeting should not automatically overwrite the legal-review calendar.

If the business approves an adjustment, document the authority and use the credit-memo workflow. Preserve the original invoice and the reason for the adjustment rather than erasing the disputed history.

Questions to ask at the weekly dispute review

Is every open issue assigned to someone? An objection without an owner tends to return unchanged at the next meeting.

What would resolve the issue? Identify the missing measurement, document or decision. More reminders will not fix an undefined factual disagreement.

Does a partial payment settle the disputed portion? Do not assume that from the deposit alone. Review the remittance, contract and any settlement or release language separately.

When is an issue closed? Record the agreed or reviewed outcome, authorized financial transaction and remaining exceptions. “Closed” in a task log should not conceal an unpaid balance in the ledger.