A paid invoice can still appear open when the payment and invoice are recorded but not linked in the same customer, job, or accounts receivable population. It can also happen when report settings or dates do not align. Treat the row as a reconciliation exception until the source system shows the supported application; do not mark the forecast row paid merely because someone says cash arrived.
Intuit's troubleshooting guidance says a paid invoice may remain in an open-transactions view when QuickBooks does not recognize the invoice and payment as matched, including when the transactions use different AR accounts or jobs under the customer. Microsoft's settlement overview similarly distinguishes posting a customer payment from settling it against the correct invoice. The management question is therefore not only “Did cash arrive?” but also “Which source invoice did the recorded payment close?”
Preserve four states
Do not collapse the workflow into paid versus unpaid. Keep these states separate:
- cash not observed and invoice open;
- cash observed but payment application unresolved;
- payment applied and a residual balance remains;
- payment applied and invoice balance is zero.
Only the last state supports removing the full invoice from future collection assumptions. The second state is an application exception, not another expected receipt.
Troubleshoot in source order
- **Confirm the receipt.** Preserve the payment date, amount, customer, reference, and source-system identifier.
- **Confirm the invoice.** Preserve invoice number, customer or job, AR account, original amount, and open balance.
- **Compare customer and job.** The payment and invoice must belong to the same supported customer population.
- **Compare AR account.** A mismatch can prevent the application from closing the intended invoice.
- **Review payment application.** Identify whether the receipt was left unapplied or attached to another invoice.
- **Align report settings and date.** A report cutoff can show a different state than a later transaction screen.
- **Escalate corrections.** If the books require a change, assign it to the authorized accounting owner. Do not edit the source system from the forecast.
Update the forecast safely
If cash is recorded but the application remains unresolved, remove the receipt from future expected cash but keep the invoice row visible as a reconciliation exception. This prevents double counting while preserving the open-report problem. Once the supported application is visible in a new dated export, update or close the invoice row from that source fact.
If only part of the invoice was settled, use the partial-payment workflow. If cash is present without a supported invoice match, use the unapplied-payment diagnostic. The cash-receipt cutoff guide keeps the recorded date aligned with the forecast snapshot.
A useful exception record
Record the invoice reference, receipt reference, amount, unresolved reason, accounting owner, next action, review date, and the export version that will confirm resolution. Avoid placing the same amount in both observed receipts and an expected future week.
What “revert” can mean in this review
A newly observed search asks what “revert” means in QuickBooks. Do not infer one cause from that word. In an AR review, it should trigger a comparison of the audit history, payment link, applied credits, customer or job, A/R account, and report date. Intuit's current troubleshooting guide recommends checking the audit log and misapplied funds when an invoice unexpectedly appears paid or open.
If a payment was actually returned and the invoice was reopened, use the returned-payment forecast workflow. If the receipt still exists but its application is wrong, keep it in the reconciliation path instead.
AR Pulse analyzes an authorized QuickBooks receivables export and does not change books or contact customers. The output is an internal action and forecasting layer, not a replacement for payment application. Finance teams can view the example report.