Chargeback forecasting requires two separate decisions: how to record the bank-side cash reversal and whether the accounting source now shows a valid customer receivable. A chargeback is not automatically a routine open invoice, and submitting evidence in a dispute does not justify a collection week.
Intuit's current open-transaction guidance distinguishes reversing a returned or declined payment from deleting the original transaction trail. Stripe's dispute lifecycle separates the disputed payment, response evidence, and later outcome.
Direct chargeback forecast treatment
- Preserve the original invoice, payment, and deposit as historical facts.
- Record the actual cash reversal on its observed date.
- Re-run the authorized customer and AR records after the accounting workflow is complete.
- Show a restored customer balance only if the source supports it.
- Keep any potential recovery unassigned until current evidence supports timing.
This sequence explains why the cash forecast can change before the AR population does. The processor event and the accounting treatment may not share the same timestamp.
Do not erase the original collection
Deleting the original receipt from a variance review makes it impossible to explain why the forecast first appeared correct and later changed. Add the chargeback as a new dated event tied to the same invoice and payment.
Track invoice number, original open balance, payment and deposit references, reversal date, disputed amount, current customer-balance treatment, evidence owner, response deadline if observed, next review date, and final outcome. Keep sensitive payment credentials out of the forecast file.
Determine the receivables state from the source
If the approved accounting workflow restores a valid customer balance, show that amount as disputed AR rather than assuming recovery. If the books use a different treatment, preserve the bank reversal in the cash view and obtain accounting guidance before changing the invoice population.
The disputed-invoice guide explains why disputed balances require separate timing assumptions. The returned-payment guide covers the source lineage when a failed receipt reopens an invoice.
Separate dispute workflow from expected cash
Reduce observed bank cash for the reversal when it occurs. Do not place the disputed amount into a collection week because a response was submitted or a processor status changed. Use an explicit scenario with amount, status, evidence, owner, and next review date.
If the chargeback resolves in the business's favor and cash returns, record that later movement as observed. If the dispute is resolved but the invoice remains open, use the resolved-dispute framework to determine whether the amount changed and what fresh timing evidence exists.
Decision rule
Preserve the original collection, add the actual reversal, and forecast only a separately supported recovery. Keep the bank event, accounting receivable, dispute status, and timing assumption as distinct fields.
AR Pulse analyzes an authorized receivables export and keeps material exceptions tied to source rows and human owners. It does not submit chargeback responses, change accounting records, or promise recovery. Apply for an AR Pulse review when chargeback events need a traceable invoice-level treatment.