Rejected construction invoice in Texas: correct and resubmit the payment packet

Identify what “rejected” means on this project

A portal shows “rejected” beside a September billing, but the office does not know whether the contractor disputes the work or simply needs a missing attachment. Treating those situations as the same problem can waste another billing cycle. Start by saving the status, the reviewer’s message and the original packet exactly as submitted.

An administrative return might identify the wrong project number, a missing attachment or an inconsistent total. A substantive dispute can concern approved scope, quantity, workmanship or an offset. A routing problem means the request did not reach the intended recipient. Ask the reviewer to identify the affected item and amount so the next submission addresses the actual obstacle.

If the packet was never received, you need delivery evidence and a correct destination, not a cosmetic invoice revision. Use the payment-ready invoice checklist to review the original package before changing it.

Create a version log instead of overwriting the first invoice

Choose a consistent method such as the original invoice number with an R1 revision suffix or a documented portal revision field. Follow the project’s numbering instructions. Mark whether the revised packet replaces the earlier request, reduces it or contains a separate additional billing. Avoid creating two collectible ledger entries for one obligation.

Keep the unaltered original file, original submission receipt, rejection message, revised file and resubmission receipt together. Preserve work dates independently of billing dates. An office correction is easier to explain when the record shows what changed and why, rather than presenting two different PDFs with the same filename.

Correct only what the evidence supports

Compare the rejected packet against the subcontract, approved changes, schedule of values and receiving instructions. Check party names, project reference, billing period, invoice number, arithmetic and attachments. A request to supply proof of a change order does not give permission to describe an unapproved change as approved.

If the reviewer proposes a deduction, request the basis and isolate the affected amount. Record a disagreement separately from an administrative correction. For disputed change work, see the unpaid change-order guide; for a proposed chargeback, use the back-charge review workflow.

• Reconcile every attachment against the revised summary.
• Explain whether the total changed and identify the adjustment.
• Avoid changing work dates to make an older balance look new.
• Review any requested release independently; correction and waiver are different decisions.

Worked example: fix an attachment without duplicating the balance

Illustrative private-project example: a September request includes $18,000 of supported earned value, including a documented approved change. Contractual retainage for the example is $1,800, with no other adjustments or prior billing on this request. The amount requested is $16,200. The reviewer returns it because the approval attachment was not included.

The office supplies that attachment in R1. Earned value stays $18,000; the example retainage stays $1,800; the request stays $16,200. The accounts-receivable ledger should not become $32,400 merely because two versions exist. Link R1 to the original request, confirm replacement handling and keep the original receipt as historical evidence.

If a correction changes the earned value, show the revised arithmetic and its supporting reason. The unchanged-total example is not a rule that all revisions must keep the same amount.

A complete rejection-to-resubmission trail: September work, October correction

This fictional continuation of INV-1042 uses the unchanged $16,200 request above. The $18,000 earned value includes an already approved $2,000 change; 10% retainage is an example contract assumption, not a universal Texas rate. Assume reviewed $0 tax, no credits and no earlier receipts. The problem is a missing copy of the existing approval, not new approval obtained after the return.

Assign the correction to the project administrator and the approval-document check to the project manager. Keep one folder or linked record for the original invoice, each packet version and the receiving evidence. The dates below describe this example only; they are not suggested billing cutoffs or legal deadlines.

• Attachment added: CO-02 signed approval. Amount, work period and underlying invoice identity unchanged.
• Keep the original rejection and both receipts; do not backdate R1 or delete the first upload.
• After the $5,000 receipt, $11,200 open request + $1,800 retained = $13,000 uncollected earned value. Do not add the original and replacement requests together.
• If no acknowledgement arrives, record “submitted, receipt saved; reviewer confirmation pending” and assign a follow-up. Do not invent an acceptance date.

If the amount changes: reconcile the correction before recording payment

A separate fictional branch starts again from the original $18,000 gross / $16,200 request, not from the unchanged-total outcome above. Suppose a documented review finds that a $2,000 work line was counted twice, and the parties confirm its removal. Corrected supported earned value is $16,000. At the same illustrative 10% retainage, retained funds become $1,600 and the corrected request is $14,400. This is an evidenced correction, not an instruction to accept an unsupported deduction.

The request decreases by $1,800, because both the $2,000 gross duplicate and its $200 retainage component are removed. If the original $16,200 was already posted, use the accounting system’s approved adjustment process so the net request becomes $14,400. The bridge below illustrates one linked credit/adjustment; an accountant should determine the appropriate document and posting treatment. If nothing was posted, do not manufacture a credit merely to imitate this example.

Keep the agreed correction, R1, adjustment reference and receipt allocation linked. The credit-memo guide covers adjustment records; the payment-allocation guide covers deposits spanning invoices. If the $2,000 remains disputed, preserve that dispute rather than applying this confirmed-correction example as though agreement exists.

Before closing the correction task, verify the reviewer handoff

A correction task can be complete while payment remains open. Use the evidence appropriate to each status, and keep the balance active until an actual payment or supported adjustment is recorded.

• Route remaining review questions to the payment follow-up log. An unresolved valuation question belongs in the invoice dispute log.
• Use the invoice-packet checklist before the next submission. A complete packet supports review; it does not establish payment approval or change automated product eligibility.

Confirm how the reviewer treats the replacement

Ask which submission channel to use, whether the current billing cutoff applies and whether the portal retains the earlier receipt. Preserve the reviewer’s answer rather than assuming that “accepted” means certified, approved for payment or actually paid. Track these statuses separately.

TxDOT’s PEPS invoicing guidance gives a specific public-program example: it warns against duplicate submissions and explains correction of rejected invoices. That guidance concerns its consultant invoicing process; it is not a universal construction subcontract rule or a private-project payment clock. Use it as an example of why the actual receiving program’s instructions matter.

For a private project, preserve contractual and statutory receipt evidence. Do not decide that all payment or notice deadlines restarted just because R1 was uploaded. Texas Chapters 28 and 53 address different rights and requirements. If timing is disputed, have a qualified Texas construction attorney review the full original-and-revised record.

Send a short, factual replacement note

An original example for office use: “Attached is INV-1042 R1 for September work. It replaces the September 30 packet and adds the approved-change attachment identified in your October 2 return message. The requested amount remains $16,200. Please confirm receipt, replacement status and whether any identified deficiency remains.” This is an administrative cover note, not a statutory notice or legal demand.

Set one follow-up owner and a reasonable review checkpoint. When payment arrives, allocate it to the underlying obligation and update the linked versions together. If a portion remains unresolved, preserve that amount and reason rather than marking the entire request complete. The partial-payment guide explains that reconciliation.

Rejected-invoice questions

Should I issue a new invoice number? Follow the receiving instructions and your accounting controls. A revised number should not create a duplicate balance or erase the original submission history.

Does adding an attachment change the work month? No. Record when work was actually furnished separately from the correction and resubmission dates.

Does resubmission automatically restart a Texas payment deadline? Do not assume so. The relevant contract, receipt facts, reason for return and applicable law need review.

What if only part of the invoice is disputed? Identify the disputed line and amount, preserve the reviewer’s reason and track the remaining balance separately. Do not convert a recordkeeping label into a legal conclusion.