Účtování Chargebacků: Spor od prvního e-mailu po konečný zápis

A refund is money you gave back. A chargeback is money that was taken. Your books have to know the difference — because the cash, the fees, and the timeline all behave differently.

---

The email subject line is some version of "A customer has disputed a charge." You open it and learn three things in one paragraph: an order from five weeks ago is being contested, the money has already been pulled from your next payout, and there's a fee on top — charged to you, for the privilege of being disputed.

You never heard from this customer. No support ticket, no refund request, nothing. The jacket shipped, tracking says delivered, and now the bank has clawed back the full amount while you're given a deadline and a form to argue your case.

If your first instinct was to book it the way you book a refund — negative sale, move on — you've just planted a reconciliation error that will surface at month-end. Because the intuition here is a specific, common lie: "A chargeback is just a refund the customer forced. Same thing, different door."

It isn't. A refund is money you voluntarily returned, on your timeline. A chargeback is money seized — pulled by the customer's bank before anyone asks your side, with a fee attached and an outcome unknown for weeks. Nobody teaches store owners chargeback accounting because most stores meet their first dispute by surprise. This post is the end-to-end version: the ops lifecycle, the cash mechanics, and the exact entries for both outcomes.

We covered the refund side in how to account for refunds and returns. That post flagged chargebacks as a different species in two paragraphs. This is the full anatomy.

The Dispute Lifecycle: Inquiry to Outcome

The exact screens differ by processor, but the lifecycle is the same everywhere, because it's defined by the card networks, not by Shopify or Stripe or PayPal. Four stages:

1. Inquiry (sometimes). Some disputes open as an inquiry or retrieval request — the bank asking for information before formally reversing anything. No money moves yet. Respond fast, because an inquiry you resolve never becomes a chargeback. Not every dispute gives you this warning shot; many skip straight to stage two.

2. Chargeback. The customer's bank formally reverses the charge. This is the moment money moves: the disputed amount is withdrawn from your processor balance immediately, and a dispute fee is charged alongside it. You are now out the cash regardless of who's right.

3. Evidence (representment). You get a window — typically a couple of weeks, and the deadline is hard — to submit evidence: the order details, proof of delivery, customer communication, your refund policy, IP and address matches. Miss the deadline and you lose by default, no matter how strong your case was.

4. Outcome. The bank rules. Weeks later — often 60 to 75 days after the dispute opened. If you win, the disputed amount comes back in a future payout. If you lose, nothing further happens; the money that left in stage two is simply gone. Either way, the fee usually stays paid — some processors return it when you win, and your agreement is the only place that answer actually lives.

[IMAGE: Timeline diagram of the four dispute stages — inquiry, chargeback, evidence, outcome — with a cash icon showing money leaving at stage 2 and conditionally returning at stage 4]

The detail that matters for your books: the cash leaves at stage two, but the answer arrives at stage four. Those can be in different months. A chargeback is an open question that sits on your books for weeks — which is exactly why it can't share an account with refunds, where the story is over the moment you click the button.

The Cash Mechanics: What Leaves, and What Might Come Back

Follow the money through both endings, generically across processors:

• When the chargeback lands: the full disputed amount (product, tax, shipping — everything the customer paid) is withdrawn from your payout balance, plus a dispute fee, commonly in the $15 range. On your payout report, this shows up in the adjustments line — the same line where payout reconciliation tends to break, because a payout carrying a chargeback will never match "sales minus refunds minus fees."
• If you lose: no further movement. The withdrawal from stage two was the whole event.
• If you win: the disputed amount is redeposited in a later payout — often the third payout to carry a piece of this one transaction, months after the original sale. The fee may or may not come back with it, depending on your processor's terms.

Notice what never happens: the goods don't come back. In a return, you get a jacket you might resell. In a chargeback, the customer typically keeps the merchandise and the bank takes the money. That asymmetry shows up in the entries below.

Chargeback Accounting: The Entries for a Loss and a Win

Time for a clearly fictional order. In February, a customer bought a jacket for $180 total: $168 product, $12 sales tax. Your processor's fee on the sale was $5.40. The jacket cost you $60, sitting in COGS. In March, the customer disputes the charge. The bank withdraws $180 from your payout plus a $15 dispute fee.

First, the structure: create a dedicated "Chargebacks" contra-revenue account, separate from "Refunds and Returns," and a "Dispute fees" expense account (or a clearly labeled line under merchant fees). This is the whole trick. Refunds and chargebacks in one bucket means your refund rate is polluted, your dispute rate is invisible, and a win has no clean account to reverse against.

The entry when the dispute lands

Book the withdrawal when the cash moves — don't wait for the outcome:

Část	Účet	Má dáti	Dal
Disputed revenue	Chargebacks (contra-revenue)	$168.00
Daň z obratu	Daň z obratu k úhradě	$12.00
Výplata hotovosti	Zúčtovací účet platebního procesora		$180.00
Dispute fee	Dispute fees (expense)	$15.00
Výplata hotovosti	Zúčtovací účet platebního procesora		$15.00

Three things to notice, all different from a refund:

• No inventory leg. The customer kept the jacket. Your $60 stays in COGS — the true cost of a transaction that earned you nothing. (In a return, a sellable jacket would reverse that $60. Here there's no jacket.)
• The sales tax reversal still happens. The $12 was seized along with everything else, so the liability comes off your books. If you'd already remitted that tax to the state, the recovery is a filing question — worth a note to your CPA rather than an improvised entry.
• The fee is an expense the moment it's charged. Not a receivable, not "pending." If your processor returns it on a win, that's a pleasant credit later — not something to book in advance.

One refinement for accrual purists: if disputes are material, you can park open disputes in a receivable-style "chargebacks pending" account until the outcome. For most stores the simple method above is better — it matches the cash, and the win entry below cleanly undoes it. Either way, choose once and stay consistent.

If you lose

You already made the entry. That's the quiet brutality of the simple method: losing requires no bookkeeping at all. The $168 sits in Chargebacks, the $15 in dispute fees, the $60 in COGS, and your P&L tells the truth — this order cost you $75 in real money plus $168 in reversed revenue, and there is no jacket.

If you win

In May, the bank rules for you. $180 shows up in a payout. The entry mirrors the original:

Část	Účet	Má dáti	Dal
Cash in	Zúčtovací účet platebního procesora	$180.00
Recovered revenue	Chargebacks (contra-revenue)		$168.00
Daň z obratu	Daň z obratu k úhradě		$12.00

The Chargebacks account nets to zero for this order, the tax liability is restored (you owe it again — the sale stands), and the clearing account explains why May's payout is $180 bigger than May's sales predict. If your processor returned the $15 fee, credit the dispute-fee expense; if not, the $15 remains the permanent cost of winning.

That's the full arc: one February sale, a March seizure, a May recovery — three payouts, three months, five ledger touches. Now multiply by every dispute, and you see why "just book it as a refund" collapses.

Reserves: When Disputes Start Holding Your Cash

If your dispute rate climbs and stays there, processors respond with a reserve account: a percentage of incoming sales held back — rolling, for a set number of days — as a cushion against future chargebacks. The specifics vary by processor and agreement, but the accounting principle doesn't.

Reserve holdbacks are not an expense. The money is still yours — you just can't touch it yet. Book reserves to their own asset account (a "processor reserve" or restricted-cash account, fed from the clearing account), and release it back as the processor does. Treat it as an expense and you'll understate profit; leave it lumped in the clearing account and reconciliation drifts every payout.

A reserve is also a message. Which brings us to the ops side.

Prevention: Cheaper Than Winning

Every dispute you win still costs you the fee, the evidence hours, and weeks of uncertainty. The better math is preventing the dispute, and most prevention is unglamorous operations:

• Billing descriptors. A meaningful share of disputes are pure confusion — a customer sees a name on their statement they don't recognize. Make your descriptor match the brand they bought from.
• Delivery proof by default. Tracking on everything; signature confirmation above a value threshold you choose. "Product not received" disputes live and die on this.
• Answer inquiries like they're on fire. Stage one is the only stage where fast support can make the whole thing disappear before money moves.
• Refund the borderline cases. A refund costs you the processing fee. A lost chargeback costs the same money plus $15, plus a mark on your dispute rate. When a case is genuinely ambiguous, the refund is usually the cheaper ending — one more reason refunds and chargebacks need separate accounts: you can't compare costs you can't see.
• Watch your rate, not just your count. Card networks and processors run monitoring programs that kick in at sustained dispute rates — added fees, mandatory reduction plans, reserves, and eventually termination. The exact thresholds live in your processor agreement, and that's where to check them; the practical rule is that a dispute rate trending upward for consecutive months is an operational alarm, not an accounting footnote.

Your dedicated Chargebacks account is what makes that last bullet possible. If disputes hide inside refunds, the trend is invisible until the processor emails you about it.

Where the Books Meet the Payout

Everything above is doable by hand — the entries aren't complicated. What's punishing is that they arrive inside payouts, tangled with that week's sales, refunds, and fees, across three different months for a single disputed order.

This is clearing-account territory. If each payout is broken into its components — sales, refunds, fees, adjustments — before it's compared to the bank deposit, a chargeback is just a labeled line, and the full method is in our guide to reconciling Shopify payouts in QuickBooks. It's also where a sync tool earns its keep: LedgerPort posts per-payout journal entries with fees and refunds already broken out (payout journals ship on the Scale plan), and maintains the clearing account those entries flow through — so when a payout arrives $195 light, the gap is a visible adjustment line, not a mystery you reverse-engineer from a CSV.

One honest boundary: no bookkeeping tool fights the dispute for you. The evidence, the deadlines, the descriptor fix, the judgment call on whether to refund preemptively — that's operations, and it stays yours. What good structure removes is the second disaster, where a dispute you lost in March is still breaking reconciliations in June.

The Dispute Rate Is a Number Now

Here's what changes when chargebacks get their own accounts: nothing about the disputes, everything about your visibility. The $15 fees stop vanishing into "merchant fees, miscellaneous." Wins actually reverse instead of double-counting against refunds. Reserves read as held cash instead of phantom losses. And your dispute rate becomes a line on a report you check monthly — the same discipline that runs the rest of your e-commerce accounting.

The jacket order above touched your books five times across three months. If your current system would have recorded it as "refund, $180" and moved on, the structure in this post is the fix — a Chargebacks account, a dispute-fee line, and a clearing account that expects adjustments. Start free with LedgerPort and let the payout side book itself →