To record a chargeback, post the amount the processor pulled back as a debit to a chargebacks or disputed funds account, post the dispute fee to merchant fees, and credit the bank or processor account for both. If the client later wins the dispute, record the returned money as a credit to the same chargebacks account.
What does a chargeback look like on a client's bank statement?
A chargeback is money a card processor takes back from a business after a customer disputes a card payment with their own bank. On the client's bank statement it usually appears as a debit from the processor with words such as "CHARGEBACK," "DISPUTE" or "ADJ," or as a deposit that is smaller than the day's sales would predict.
Where the line shows up depends on the processor. Some debit the bank account directly. Others take the chargeback out of the next payout, so the statement shows only a short deposit and the dispute is visible only in the processor's own report. Stripe, for example, describes in its guide to how disputes work that it debits the disputed amount plus a dispute fee from the business's Stripe balance and holds those funds while the dispute is open. For a Stripe client, that means the chargeback lives in the payout detail, not as its own bank line.
Ask for the processor's dispute report whenever a payout looks short. The bank statement alone rarely tells you which sale was disputed.
Recording the chargeback debit and its dispute fee
A chargeback produces two separate amounts: the disputed sale and the processor's fee for handling the dispute. Record them on separate lines. The disputed amount reduces sales or sits in a disputed funds account while the client contests it. The fee is a cost of taking cards and goes to merchant fees.
The choice of account for the disputed amount depends on what the client plans to do:
- The client accepts the dispute. Code the amount to a contra-revenue account such as "Sales returns and chargebacks." Sales for the period then show what the client really kept.
- The client will contest it. Code the amount to a current asset such as "Funds held in dispute." It stays there until the outcome is known, and only then moves to chargebacks or back to cash.
Agree on one approach per client and use it every time. Mixing the two makes the disputed funds account impossible to reconcile.
Worked example: a $480 sale disputed and won
The values below are an example for a fictional client paid through a processor that debits the bank account directly, with an illustrative $15 dispute fee.
| Date | Event | Entry |
|---|---|---|
| April 22 | Sale paid by card | Sales 480.00, already recorded from the payout |
| May 14 | Chargeback and fee debited | Debit funds held in dispute 480.00, debit merchant fees 15.00, credit checking 495.00 |
| July 2 | Dispute won, funds returned | Debit checking 480.00, credit funds held in dispute 480.00 |
After July 2, the disputed funds account is back to zero, sales are untouched and the only lasting cost is the $15 fee.
Recording the chargeback reversal after a won dispute
A chargeback reversal is the processor returning the disputed amount after the card issuer decides in the business's favor. Record it as a deposit that credits the same account the chargeback was debited to. If the chargeback went to funds held in dispute, the reversal clears that balance. If it went to chargebacks, the reversal reduces that contra-revenue account.
Do not code the returned money as new sales. The sale was recorded once in April, and counting it again inflates revenue.
Check whether the fee comes back too. Stripe's dispute guide says its fee for receiving a dispute is not refunded for businesses outside Mexico, while a separate fee for countering a dispute is returned if the business wins. Other processors set their own terms, so read the client's processor statement rather than assuming. If part of a fee is refunded, credit merchant fees for that part.
Disputes can take months. Stripe's guide describes a full cycle of two to three months, so a chargeback debited in one month and reversed in the next quarter is normal. Leave a note on the original line naming the sale and the dispute reference so the reversal can be matched later.
Which disputed lines are not merchant chargebacks?
A disputed line is not a merchant chargeback when the client is the one who disputed a payment, or when the money moved on a system with no card dispute process. These lines look similar on a statement but need different coding.
- The client disputed their own card purchase. A credit from the client's card issuer after they contested a charge is a refund of that expense. Credit the original expense account.
- A disputed ATM withdrawal. If an ATM failed to dispense cash and the bank credits it back, the credit reverses the original withdrawal. The guide to recording ATM withdrawals covers how those withdrawals are coded in the first place.
- Payment app reversals. Zelle and Venmo payments do not run through card networks, so a customer cannot charge them back in the same way. A reversed app payment usually means a failed or returned transfer. The post on categorizing Zelle and Venmo payments explains how to read those lines.
- A returned check. A customer check that bounces comes back as a returned item from the bank, not a chargeback, and it reopens the customer's invoice.
Chargeback tracking for retail and card-heavy clients
Chargeback tracking matters most for clients who take many card payments, such as shops and restaurants. A few open disputes a month can leave sales overstated or a disputed funds balance that nobody can explain. A simple monthly list fixes that.
Keep a small schedule for each card-heavy client with one row per dispute: sale date, amount, dispute reference, date debited, status and date resolved. At month end, the total of open rows must equal the funds held in dispute balance in the books. If it does not, a reversal was coded as sales or a chargeback was coded straight to fees.
Retail clients have their own patterns around card volume, refunds and daily payouts. The guide to retail store bookkeeping shows how those fit with the rest of the month. For the bank side, AutoBankConvert codes a client's processor payouts and dispute debits from rules written once for that client, and sends unfamiliar processor lines to review with a suggested account.