Allocate a customer credit memo to the supported invoice balances before updating the forecast. Reduce each invoice only by the amount actually applied to it, preserve any unapplied remainder as a separate customer-credit state, and never record the credit as incoming cash.
Intuit's credit-memo guidance explains that a credit memo can reduce an invoice partially or fully. When automatic application is enabled, QuickBooks can apply a credit to the oldest unpaid invoice and then continue to later invoices until the credit is used. That behavior can change several invoice balances at once, so an invoice-level forecast needs an allocation bridge.
Preserve the customer-level credit event
Start with one credit record containing the customer, credit memo number, date, original amount, reason category, source reference, and current applied or unapplied state. Then create one allocation row for each affected invoice.
| Allocation field | Purpose | | --- | --- | | Credit memo ID | Links every allocation to one source credit | | Invoice ID | Preserves the invoice receiving the reduction | | Applied amount | Changes only the supported invoice residual | | Application date | Shows when the source balance changed | | Remaining credit | Exposes any unapplied customer balance | | Reviewer and source | Makes the bridge auditable |
The sum of allocations plus the unapplied remainder should equal the original credit amount. The sum of revised invoice residuals should reconcile to the current authorized A/R report.
Update each invoice once
Suppose a credit is applied across three invoices. Do not subtract the full credit from each invoice, and do not subtract it once from a customer subtotal while also using already-reduced invoice balances. Choose the source representation, reconcile it, and preserve invoice identity.
For each invoice:
- Record the pre-application open balance from the prior snapshot.
- Record the observed credit allocation.
- Calculate the supported residual.
- Retire only the prior assumption attached to the reduced amount.
- Review the remaining balance for a new expected week or unassigned state.
Intuit's invoice-payment documentation similarly preserves invoice-specific payment amounts when one customer payment covers several invoices. A credit is not a payment, but both workflows demonstrate why allocation belongs at the invoice level.
Separate credit from cash
A credit memo reduces what the customer owes. It does not create a receipt. If the memo closes an invoice, remove that supported residual from expected collections and classify the change as a credit, not forecasted cash collected.
If the credit remains unapplied, keep it visible beside the customer without guessing which invoice it will reduce. The auto-applied credit guide covers source settings that can change allocation. The partial credit-note guide explains the related sequence when observed cash and a credit both affect one invoice.
Decision rule
One credit event can affect several invoice rows, but it should change the portfolio exactly once. Preserve the memo, allocation, residual, owner, and review date; then forecast only the verified open balances.
AR Pulse analyzes an authorized QuickBooks receivables export and keeps findings linked to supplied source rows. It does not issue or apply credits or change accounting records. Apply for AR Pulse when customer-level credits need an invoice-level cash review.