A customer overpayment should not appear as another expected collection in a four-week AR forecast. The cash has already been recorded. Preserve the remaining customer credit as a separate state until it is applied to an open invoice, refunded, or otherwise resolved through the authorized accounting process. Netting it silently against unrelated invoices can hide both the cash event and the decision that remains.

Intuit's overpayment guidance explains that a customer credit from an overpayment can be applied to another open invoice or refunded. Microsoft's settlement overview notes that when a payment exceeds an invoice, the invoice can close while the payment retains the difference as an open balance. Those are source-system states; the forecast should reflect them without deciding the accounting treatment.

Separate the cash event from the credit decision

Keep two records:

  1. the observed receipt, with date, amount, customer, and reference;
  2. the remaining credit balance, with its source status and internal owner.

The observed receipt belongs in actual cash. The unresolved credit does not belong in a future expected-receipt week. It may affect another invoice later, but that effect is not supported until the application is recorded.

When the credit came from a second payment against the same invoice, use the duplicate-payment credit bridge to preserve both receipts and any later application without counting the extra cash twice.

Classify the overpayment before forecasting

Use four states:

  • **Applied to another open invoice:** reduce that invoice by the recorded applied amount.
  • **Refund pending or recorded:** keep the refund decision outside collection totals and preserve its owner and status.
  • **Credit held for a future invoice:** keep it visible outside the current open-invoice forecast until an invoice and application exist.
  • **Unresolved:** flag the amount as a reconciliation exception and do not infer its destination.

If the payment also settled several invoices, reconcile the invoice allocations before classifying the remainder. Never spread a customer-level credit across rows simply to make the forecast total agree.

Prevent three common forecast errors

First, do not count the full payment as observed cash and leave the original full invoice in a future week. Second, do not count the residual credit as negative expected collections. Third, do not reduce a different invoice unless the source system shows the credit application.

The credit-memo guide explains applied versus unapplied credits. The partial-payment guide covers the opposite condition: cash that reduces but does not fully settle an invoice. The AR balance-versus-collections comparison keeps balance-sheet effects separate from weekly receipts.

Record a reviewable decision trail

Preserve the customer, original invoice, receipt, overpayment amount, current credit balance, application or refund reference, accounting owner, next action, and review date. If the status changes, use a new dated export and retain the prior view for variance review.

AR Pulse uses an authorized QuickBooks receivables export to create an internal cash-action list and four-week collections forecast. It does not post credits, issue refunds, or change accounting records. Finance owners who want an evidence-linked view can apply for AR Pulse.