Construction remittance advice: allocate one payment to the right invoices

One deposit can cover several projects and billing periods

A Dallas subcontractor sees an $11,000 receipt from a repeat customer. Two projects have open invoices, and the emailed remittance lists several references. Posting the whole amount against the largest balance would make one project look current and leave the other incorrectly overdue.

The remittance describes which bills the payer says a payment covers. The receipt shows what your business actually received; the accounting allocation links that receipt to specific balances. Keep all three connected. The partial-payment guide covers a remaining invoice balance; this guide focuses on a batch payment with multiple invoice references.

Intuit’s remittance guidance identifies payment references and bill-level details. It also distinguishes scheduling and processing notifications. Read the status and reconcile the actual payment rather than treating every emailed document as confirmation of available funds.

Keep the remittance, receipt and allocation as separate evidence

Identify the payer, payment reference, currency and total amount. Then identify every listed invoice and project. Invoice numbers can be similar across jobs, and a remittance may use the customer’s own reference instead of yours. Ask for a cross-reference when the match is unclear.

Check the actual receipt through your established banking and accounting process. A schedule email, processing notice or copy of a check is not the same record as funds received. Use your normal controls for settlement, returned payments and any subsequent correction.

Keep full bank details outside a broadly shared collections worksheet. Link the controlled receipt record instead. If payment-destination instructions changed, use the bank-detail verification workflow through known contacts.

Worked example: $11,000 across three invoices

Original illustrative example: the opening ledger has Invoice A for $6,000 on Job North, Invoice B for $4,000 on Job South and Invoice C for $3,000 on Job North. The remittance identifies payments of $6,000, $3,000 and $2,000 respectively. An actual $11,000 receipt is verified under the business’s normal controls.

The listed allocations total $11,000. After posting them to the identified invoices, A has no remaining balance, B retains $1,000 and C retains $1,000. The opening $13,000 less the $11,000 applied receipt leaves $2,000 open. There are no credits, retainage, taxes, fees or disputes in this simplified example.

Do not apply the full receipt to Job North merely because two of the three invoice numbers belong there. Job North receives $8,000 across A and C; Job South receives $3,000 on B. Keep the batch reference on all three entries so the receipt can be traced without duplicating it.

Keep unmatched cash visible, then correct the allocation trail

This is an alternative fictional batch, not another receipt added to the completed example above. Start again with A $6,000, B $4,000 and C $3,000: $13,000 open. Verify receipt R-204 for $11,000 USD. ALLOC-204-v1 supports $6,000 to A, $3,000 to B and $1,500 to C. The remaining $500 references an unmatched item. Assume no credits, fees, taxes, retainage, disputes or other receipts.

Post only the supported $10,500 allocation under the reviewed accounting policy. A becomes $0, B $1,000 and C $1,500, giving $2,500 open invoices. Separately identify $500 of R-204 as unallocated. Cash control: $11,000 received = $10,500 allocated + $500 unallocated. Invoice control: $13,000 opening − $10,500 allocated = $2,500. Do not show the $2,500 as an additional payment demand while ignoring the $500 already received and awaiting allocation.

Later clarification REM-204-v2 identifies the $500 as payment toward C. Record ALLOC-204-v2 against the same R-204 receipt: C falls to $1,000 and invoice balances total $2,000. Unallocated cash becomes zero and received cash stays $11,000. Adding a new $500 receipt would count the same money twice.

If a further authorized correction says $250 previously assigned to B belongs to C, preserve v1/v2 and record the correction reference COR-204. Reverse $250 of B’s allocation and apply it to C through your accounting system’s correction process. B’s cumulative allocation becomes $2,750 and open balance $1,250; C’s cumulative allocation becomes $2,250 and open balance $750. A remains settled. Total allocated stays $11,000, open invoices stay $2,000 and no new cash is received. Do not silently overwrite the original evidence.

Keep the payer clarification, allocation versions, correction date, reason and responsible reviewer with R-204. A bookkeeping example does not resolve conflicting legal allocation instructions. Use the partial-payment guide for invoice-level follow-up and the customer statement guide to present the corrected balances at a clear cutoff.

Investigate a difference without inventing an allocation

If the receipt is $10,750 but the remittance lists $11,000, record a $250 difference and ask for the explanation. Do not automatically label it a fee, credit or back charge. Each treatment needs its own support and the appropriate accounting or commercial authorization.

If a listed reference cannot be matched, keep the unresolved amount clearly identified under your accounting policy. Ask the payer for the project and invoice detail. Do not silently select the oldest invoice simply to clear an unapplied-payment list.

Intuit’s Payment reference allows one customer payment to link to multiple invoices and describes unapplied payments separately. That supports the distinction between a receipt total and invoice allocations; this article does not provide QuickBooks setup steps or claim an accounting integration.

When a deduction is disputed, use the invoice dispute log. When an authorized credit is posted, use the credit-memo reconciliation guide to avoid subtracting the same adjustment twice.

Update follow-up only after the financial reconciliation

After posting the verified allocation, update the remaining balances in the aging review and weekly cash forecast. A promise can move a forecast scenario; an actual reconciled receipt changes the financial record.

For the example above, close Invoice A’s collection task when the evidence supports it. Keep B and C open for their remaining $1,000 each and ask which payment expectation now applies. Preserve earlier promises in the follow-up log rather than overwriting the history.

A paid accounting balance does not alone complete a waiver or recorded-release task. Use the waiver payment-review guide for that separate document review. Allocation records do not determine the legal effect of a particular waiver.

If a receipt covers a separately approved retainage release, identify that released balance and its allocation once. Keep held retainage outside an ordinary invoice subtotal unless that subtotal already includes it. The retainage ledger tracks held, released-unpaid and received categories; the progress-billing calculator handles the separate request-versus-prior-receipt bridge. These guides do not imply automatic multi-invoice allocation or credit/correction posting in the app.

Download the remittance allocation review sheet

Download the remittance allocation review sheet. Add one row per invoice in a payment batch, repeat the batch reference and record the supported amount applied. Sum allocations once per batch before comparing them with the receipt total.

The CSV is a blank review aid, not an automatic accounting import or a bank feed. Keep the remittance original, receipt evidence, posted allocation record and exception resolution together in your approved system.

Repeat the batch reference on invoice rows, but enter “Receipt total - batch only” once per batch, for example on its first row; leave that field blank on continuation rows. For R-204 v1, the three Amount allocated entries are 6000, 3000 and 1500, summing to 10500 against one 11000 receipt total. Record the 500 unallocated exception and its reviewer separately from invoice allocations. Do not sum a repeated batch receipt total as if it were three deposits. The CSV has no formulas; preserve separate dated copies or a controlled correction log for v2/COR-204.

• Confirm payer, batch reference, currency and receipt status.
• Map each remittance reference to the correct project and invoice.
• Check the sum of allocations against the received amount.
• Assign an owner to every unmatched difference.
• Update remaining balances and document tasks separately.

Remittance allocation questions

Does remittance advice prove cash has arrived? Read its status and verify receipt through your normal controls. A document describing payment scheduling or processing does not complete that check.

Can one payment cover several invoices? Yes; preserve the batch total and each supported invoice allocation rather than recording the receipt more than once.

What if the payer supplies no invoice detail? Ask for it and keep the unresolved allocation visible under your accounting policy. This guide does not establish a legal default allocation rule.

Does a partially paid invoice stop aging? Track the remaining reconciled amount using the documented aging policy. Keep any separate retainage, dispute and deadline review identifiable.