When a real customer payment is applied to the wrong QuickBooks invoice, preserve the receipt as observed cash but rebuild the invoice-level forecast. The intended invoice may still appear overdue, while a different invoice is incorrectly closed or reduced. Do not forecast a second receipt for the same bank transaction and do not prioritize the intended invoice as though no payment evidence exists.
Separate cash truth from application truth
Intuit lists misapplied funds as a cause of a payment-received invoice still appearing unpaid. Its guidance is to review the customer transaction list, identify an unapplied or wrongly applied payment, and link the payment to the correct outstanding transaction. Intuit also points users to Customer Balance Detail when investigating unapplied payments.
The bank receipt and the invoice allocation are two linked facts:
- The receipt answers whether cash arrived.
- The application answers which receivable the cash settled.
A forecast that treats either fact as sufficient can fail in opposite directions. Ignoring the receipt duplicates cash. Trusting the wrong application suppresses a still-open invoice and distorts aging, ownership, and follow-up.
Use the unmatched-payment exception guide when no supported invoice allocation exists. If one payment covers several invoices, use the multiple-invoice allocation workflow instead of forcing the full amount onto one row.
Rebuild the invoice bridge
Preserve the bank transaction or processor receipt, payment date, customer, amount, original QuickBooks application, intended invoice evidence, and reviewer. Then show the transition for both invoices:
- Reverse the unsupported forecast reduction on the wrongly credited invoice.
- Apply the supported reduction to the intended invoice only after the accounting source is corrected or the exception is explicitly documented.
- Keep total observed cash unchanged.
- Recalculate open amounts and expected collection weeks without counting the receipt again.
- Re-run invoice priority after the corrected balances are visible.
Until the books are corrected, label both rows as an application exception. Do not send an ordinary overdue action based only on the misleading source status. The overdue invoice priority matrix should consume verified balances, not replace reconciliation.
Decision rule
One receipt creates one cash event. Correct its invoice allocation, update both affected forecast rows, and preserve a reversible record of the change. If allocation evidence remains incomplete, keep the amount out of new expected collections and assign a cash-application owner.
AR Pulse analyzes an authorized QuickBooks receivables export and highlights invoice-level exceptions. It does not post payments or alter accounting records. View the example report to see how source facts and actions are separated.