When a credit note is voided, do not simply add its amount back to a prior forecast. Confirm that the current receivables source now restores the amount due, preserve the earlier snapshot, and reassess collection timing for the newly open residual. The accounting change and the forecast judgment are related, but they are not the same event.
Stripe documents that voiding a credit note on an open invoice reverses its adjustment and increases the invoice amount due. Oracle documents that receivable transaction types determine whether activity updates customer balances and aging. The practical control is therefore source-first: use the current posted transaction state to establish the balance, then make a separate evidence-based timing decision.
Preserve the before and after states
Retain the original invoice, the credit note, its prior status, the void event, the effective date, and the current invoice balance. The earlier forecast may have correctly used the reduced balance at its cutoff. Rewriting that old row makes a later variance look like it never occurred.
Use the weekly AR snapshot change log to classify the restored amount as a source-balance change. Link the new snapshot back to the voided credit note rather than creating an unexplained increase.
Reconcile the restored amount
Start with a simple bridge:
`prior open amount + voided credit amount - later payments - other applied credits = current open amount`
The current source system must support the result. If the void event is visible but the invoice balance has not changed, keep the item as a reconciliation exception. Do not manufacture a receivable in the forecast to anticipate a posting that has not appeared.
The credit-memo pre-forecast check helps separate applied, unapplied, and pending credit states. If the credit was only requested and never issued, use the pending credit request framework instead; there may be no posted credit to reverse.
Reassess timing independently
Restoring an amount due does not restore the old collection date automatically. The customer may still dispute the charge, the invoice may require redelivery, or a prior promise may have covered only the reduced amount. Record the current evidence, supported amount, owner, next action, and review date.
If the invoice was previously closed by the credit note and reopens after the void, treat the reopened balance as a current exception. Assign a collection week only when delivery, acceptance, payment status, or a documented commitment supports it. Otherwise leave timing unassigned while keeping the amount inside the reconciled open-AR population.
Change-control checklist
Confirm the invoice and credit identifiers, the status transition, the source-system effective date, the amount restored, any intervening receipts, current open balance, customer-facing document state, and the reviewer who approved the forecast change. Preserve both the prior and replacement assumption.
Decision rule
A voided credit note can restore an open receivable, but only the current source state establishes the amount. Forecast timing requires fresh evidence. AR Pulse analyzes an authorized QuickBooks receivables export and keeps source facts separate from management assumptions; it does not void credits, alter books, or guarantee collections. Apply for AR Pulse for a source-linked four-week review.