To reconcile chargebacks, find each disputed amount and its fee in the processor report and on the bank statement, move the disputed amount to a dispute receivable instead of cancelling the sale, and expense the fee. If the dispute is won, the money returns and clears the receivable. If it is lost, write the receivable off against revenue.
Where a chargeback shows up: processor report and bank statement
A chargeback reaches the bank in one of two ways. The disputed amount either comes out of the processor balance, so it lowers the next payout, or it is debited from the bank account on its own. The processor report names the dispute; the bank shows only a smaller deposit or a bare debit.
Stripe's documentation on how card disputes work describes the usual pattern: when a cardholder disputes a charge, the disputed amount plus a dispute fee is debited from the merchant's balance and held while the dispute runs. The same page notes that the full cycle can take two to three months, which means an open dispute often crosses a month-end.
That delay is the whole reconciliation problem. The cash left in one month, and the answer arrives in another. Your books need a place to hold the amount in between.
Chargeback journal entries while the dispute is open
While a dispute is open, the disputed amount is money the business may still get back, so it belongs in a receivable, not in expenses and not as a cancelled sale. The dispute fee is a cost of the dispute and goes to expense when it is charged. Both entries happen on the date the processor takes the funds.
Here is a worked example with invented figures. A customer paid 300.00 by card on March 10. On April 5 the processor opens a dispute and deducts 300.00 plus a 15.00 fee from the April 6 payout.
| Date (example) | Account | Debit | Credit |
|---|---|---|---|
| Apr 5 | Chargebacks receivable | 300.00 | |
| Apr 5 | Dispute fee expense | 15.00 | |
| Apr 5 | Processor clearing | 315.00 |
The April 6 payout is 315.00 smaller than its charges would suggest, and the processor report shows exactly why. The clearing account ties, the receivable shows 300.00 at risk, and March revenue is untouched.
Keep a short list behind the receivable: customer, original charge date, dispute date, amount, reason and the date evidence was sent. At each month-end the list should foot to the receivable balance.
What happens to the chargeback entry when the dispute is won?
When a dispute is won, the processor returns the disputed amount, usually inside a later payout. Record it by debiting processor clearing and crediting the chargebacks receivable. The dispute fee often stays lost: Stripe, for one, says the fee for receiving a dispute is not refunded for businesses outside Mexico, though a separate countered fee comes back on a win.
Continuing the example, suppose the dispute is decided in the merchant's favour on June 12:
| Date (example) | Account | Debit | Credit |
|---|---|---|---|
| Jun 12 | Processor clearing | 300.00 | |
| Jun 12 | Chargebacks receivable | 300.00 |
The receivable is back to zero for this customer, and the 15.00 fee remains an April expense. Check the payout that carried the reversal: it should be 300.00 larger than its charges, and the processor report should show a dispute reversal line.
A lost chargeback and the receivable write-off
A lost chargeback means the cardholder keeps the money, so the original sale did not stand. Close the receivable against a revenue contra account, such as "chargebacks lost", or against bad debt, according to your policy. Do it in the month the dispute is decided, not the month the sale was made.
If the example dispute had been lost on June 12, the entry would be:
| Date (example) | Account | Debit | Credit |
|---|---|---|---|
| Jun 12 | Chargebacks lost (contra revenue) | 300.00 | |
| Jun 12 | Chargebacks receivable | 300.00 |
No cash moves on that date, because the processor took the money back in April. That surprises people: the bank statement in June shows nothing, yet a 300.00 entry is posted.
ACH payments have a parallel problem, with return codes instead of disputes and much shorter windows. ACH return reconciliation and return codes covers reversing those receipts and re-presenting them.
Chargeback mistake: reversing the original sale on day one
The common chargeback mistake is reversing the original sale the moment the dispute opens. That understates revenue in a month when nothing was decided, and if the dispute is won, a second entry has to re-create the sale months later. Revenue jumps around, and the trail between the two entries is hard to follow.
A related slip is booking the whole 315.00 debit as fees. The ledger then shows an inflated fee expense, no receivable, and a won dispute later appears as unexplained income. The dispute receivable avoids both problems and gives a reviewer one account to look at.
Not every dispute arrives through a card network. Business customers paying by check often deduct a disputed amount from their payment instead. In a lockbox, that shows up as a short-paid invoice rather than a chargeback; lockbox reconciliation from bank file to receivables covers recording those deductions.
Does an open chargeback change the bank reconciliation?
An open chargeback does not normally create a reconciling item on the bank reconciliation. The processor already took the money, so the bank and the books both show the lower amount once the entries above are posted. It becomes a reconciling item only if the processor debited the bank and nobody recorded it yet.
That case is easy to spot on a bank statement: a debit from the processor with no payout and no ledger entry behind it. Record it against the dispute receivable, not as a fee, and it clears. In Sage 300, for example, it is matched in bank reconciliation like any other withdrawal once the entry exists; Sage 300 bank reconciliation covers that screen.
A bank statement that foots and matches line by line to the ledger makes these debits stand out. PreciseBankFlow lists every statement line that clears nothing in your register, so an unrecorded chargeback debit reaches the exception report instead of hiding in the month. Request early access to run it on your own statements.