Merchants should keep unresolved disputes in accounts receivable until the outcome is known, because the amount may still be recovered if the cardholder claim is overturned. If the dispute is won, the reversal restores the receivable. If the merchant loses, misses the response deadline, or does not respond, the amount should be reclassified as bad debt expense.
How unresolved chargebacks should be recorded
Keep the disputed amount in accounts receivable while the case is unresolved, because the merchant still has a valid claim to recovery until the card network process reaches a final result. That means the accounting entry should reflect a receivable, not an immediate loss, until the dispute is decided or the response window closes without action.
This treatment preserves the economic reality of the dispute: the balance is still potentially collectible. If the chargeback is overturned, the receivable remains recoverable. If the merchant loses, or the deadline passes without a response, the balance stops being a collectible claim and should be moved out of receivables.
What changes when the dispute outcome is known
The accounting treatment changes at the decision point, not when the chargeback is first received. A successful dispute reverses the tentative loss and restores the amount as collectible. An unsuccessful dispute, or one that is abandoned by missing the filing deadline, should be recognised as bad debt expense because recovery is no longer expected.
For finance teams, the key distinction is between a temporary contested balance and a confirmed loss. Unresolved chargebacks belong in receivables because they are still subject to reversal. Once the network process resolves against the merchant, the bookkeeping should reflect the final economic outcome rather than the initial transaction value.
Risk and Threat Considerations
Chargebacks create a timing and classification risk if merchants write them off too early, or leave them in receivables after the dispute is no longer recoverable. Either error can distort working capital reporting, overstate expected recovery, or delay recognition of a real loss.
Failure mechanism: The dispute is treated as settled before the card network outcome is final, or the response deadline is missed and the accounting team fails to reclassify the balance once recovery is no longer possible.
Impact: Receivables become unreliable, loss reporting is misstated, and management may make decisions on a balance that no longer reflects collectible value.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST CSF 2.0 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | GV.RM-03 — Risk Management Strategy | Unresolved chargebacks affect loss recognition and recovery timing. |
| Recommendation — Track dispute aging and reclassify balances when recovery becomes unlikely. | ||
| CIS Controls v8 | 8.3 — Audit Log Management | Chargeback status changes need traceable records for dispute handling and reconciliation. |
| Recommendation — Retain evidence for dispute dates, deadlines, and final outcomes. | ||
Practitioner Guidance
What to verify: Tie each unresolved chargeback to the network deadline, dispute status, and recovery likelihood so the balance only remains in receivables while there is still a live path to reversal.
Decision rule: If the dispute is still open and the response window remains active, keep it in receivables; if the merchant loses, withdraws, or misses the deadline, reclassify promptly to bad debt expense.
Practitioner takeaway: The control objective is not to predict the dispute outcome, it is to make sure the ledger changes when the recovery right changes.
