Remittance advice should not reduce an invoice forecast by itself. Treat it as customer-provided matching evidence: it can identify the invoices a payer intends a receipt to settle, but expected cash becomes observed only when the related bank transaction is present and the payment is recorded and matched without duplication.
Keep three events separate
A clean cash-application record distinguishes:
- **Advice received:** the customer lists intended invoice allocations.
- **Bank receipt observed:** money appears in the authorized bank or payment record.
- **Invoice settlement recorded:** the receipt is posted and applied to specific open invoices.
Microsoft's advanced bank-reconciliation documentation separates generating a customer payment from settling open invoices. It also describes unmatched bank transactions and a review path before posting. That distinction is useful even for a smaller QuickBooks-based team: a receipt can exist without a reliable invoice match, and an allocation note can exist before the receipt.
Use advice as a reconciliation key
Capture the advice date, payer, payment reference, listed invoice numbers, stated amounts, currency, expected value date if supplied, source location, and reviewer. Then look for a corresponding bank receipt or recorded payment. Never copy the advice amount into actual cash simply because the document looks complete.
When the money arrives, reconcile:
`matched allocations + unapplied residual = observed receipt`
Also confirm that the sum applied to any invoice does not exceed its current open balance. The one-payment-to-many-invoices guide handles split allocation across several invoices. The unmatched-payment framework keeps observed cash visible when the payer or invoice match is still uncertain.
Prevent forecast double counting
Before the bank receipt is observed, remittance advice may strengthen a timing assumption, but it remains expected cash. After the receipt is observed, remove that amount from the forward forecast and place any unmatched portion in a cash-application exception lane. Do not retain the same dollars as both expected weekly collections and actual cash.
If advice lists a partial payment, reduce only the recorded amount after receipt and settlement. Keep the remaining invoice balance open with its own evidence and timing. The partial-payment forecast guide explains the residual control.
J.P. Morgan's cash-application guide describes connecting payments and remittance information to open receivables. That process supports matching; it does not justify inventing a receipt that has not been observed. Community discussions about remittance inboxes informed this page's workflow language, not any claim about prevalence or time saved.
Build the exception queue
Route four cases separately: advice with no receipt, receipt with no advice, advice and receipt with a difference, and matched receipt waiting for posting. Give each one an owner, next action, and review date. Preserve the dated source records so a later correction can be explained.
Decision rule
Use remittance advice to match and review, not to manufacture actual cash. Keep expected timing, bank receipt, and invoice settlement as separate states until all amounts reconcile. AR Pulse works from an authorized receivables export to make those exceptions and internal actions visible; it does not contact customers or change the books. View the example report.