An unmatched customer payment is observed cash but not yet evidence that a specific invoice was collected. Keep the receipt out of expected collections, preserve the affected invoices at their recorded open balances, and create one cash-application exception until the customer and invoice allocation are supported.
Microsoft’s cash-application guidance separates matched customer transactions from unmatched bank-statement transactions. Intuit’s deposit-linking guidance shows that a bank deposit can require customer identification and application through Receive payment before the invoice is updated.
Avoid the two common forecast errors
The first error is to leave the unmatched receipt as expected future cash even though the bank already shows it. The second is to remove an invoice solely because its amount resembles the receipt. Either choice can double count cash or clear the wrong customer balance.
Maintain two temporary views:
- **Observed cash:** receipt date, amount, bank reference, payer text, and source account.
- **Unresolved AR:** candidate customer and invoices, possible allocation, evidence missing, owner, and review date.
The relationship between them remains unconfirmed until the payment is applied and a refreshed receivables report shows the resulting balance.
If the payment has no invoice reference
Treat a missing invoice number as a routing problem, not permission to guess. Preserve the payer text, bank reference, amount, date, currency, and any remittance channel. Then compare customer identity before amount, because the same rounded amount can appear on several invoices or customers.
| Available evidence | Next internal step | | --- | --- | | Customer and one invoice ID agree | Validate the source relationship and refreshed balance | | Customer agrees but several invoices fit | Request or retrieve allocation detail | | Amount agrees but payer identity conflicts | Keep unmatched and investigate the payer record | | No usable reference or remittance | Assign an owner and review date without clearing AR |
If the receipt is a duplicate payment that becomes a customer credit, use the duplicate-payment credit bridge rather than applying it to the closest open invoice.
Work the exception in a fixed order
Confirm that the receipt is customer cash rather than a transfer, refund, loan, or other non-AR movement. Compare payer name, memo, amount, invoice references, remittance advice, and customer records. Consider whether the payment covers several invoices, includes a customer credit, or came from a parent or payment agent.
Do not force an exact-amount match when evidence points elsewhere. If multiple allocations remain plausible, keep the receipt unmatched and request the minimum additional remittance detail. Record every allocation change so later reviewers can reproduce the decision.
The unapplied-payments guide explains how unapplied cash can coexist with aging balances. The multiple-invoice payment guide covers supported allocation across open items.
The cash application versus collection forecasting comparison shows where this reconciliation work ends and the forward-looking timing decision begins.
When a payer sends allocation details before or alongside the receipt, use the remittance-advice reconciliation guide. It keeps advice, observed cash, and invoice settlement as separate states so the same dollars cannot remain in both actuals and expected collections.
Forecast treatment after resolution
Once applied, remove only the amount actually credited to each invoice. Keep any residual invoice balance in the forecast and any residual customer credit in its proper record. Preserve the bank receipt date separately from the application date so forecast variance is tied to the observed customer payment, not the cleanup date.
If the receipt later reverses, reopen the evidence review instead of automatically restoring the prior collection assumption. The returned-payment guide explains that reversal boundary.
Decision rule
Cash can be real while its invoice destination is unknown. Count it once as observed cash, clear no invoice without support, and keep the mismatch visible as a named exception. The QuickBooks export checklist provides the invoice fields needed for reconciliation, and the AR Pulse example shows the intended source-row traceability.