Best Practices for Reconciling Chargebacks, Disputes and Payment Holds

Chargebacks, payment disputes, and processor holds are the parts of e-commerce reconciliation that most often sit unrecorded for months, because they do not arrive as tidy single transactions. A chargeback is debited from a future payout, a dispute can freeze funds for weeks before resolving either way, and a payment hold can lock up a percentage of every deposit indefinitely. Each one needs a deliberate accounting treatment, not a write-off when someone finally notices the bank balance does not reconcile.

This piece sits inside [the payment gateway and reconciliation pillar](/guides/payment-gateway-multi-channel-sales-reconciliation/) and covers the ledger mechanics for chargebacks, disputes, and held funds. The two companion pieces in this Week 2 series cover [consolidating omni-channel revenue across Shopify, Etsy, TikTok Shop and Amazon](/blog/consolidating-omni-channel-revenue-shopify-etsy-tiktok-amazon/) and [gross vs net revenue recognition and the payout accounting trap](/blog/gross-vs-net-revenue-recognition-payout-accounting-trap/).

Chargebacks, disputes, and holds are three different things

These three terms get used interchangeably by sellers, but they behave differently in the ledger. A chargeback is a customer asking their card issuer to reverse a payment, which the processor then claws back from the seller, usually with a fee. A dispute is the open case that may or may not become a chargeback, during which the disputed amount is often held. A payment hold (or rolling reserve) is the processor withholding a percentage of every payout as security against future chargebacks, regardless of any specific transaction.

• Chargeback: a completed reversal. The sale revenue is reversed, the goods are usually gone, and a chargeback fee (typically £10-£20 with UK processors) is charged on top.
• Dispute: an open case. Funds may be temporarily withheld pending the outcome. The seller submits evidence; the case resolves in the seller or buyer favour.
• Payment hold / rolling reserve: a standing percentage (commonly 5%-10%) of payout volume held by the processor for a fixed period (often 90-180 days), then released on a rolling basis.

How a chargeback hits the books

When a chargeback completes, three things happen at once: the original sale is reversed, the goods are typically lost (the customer keeps them), and a chargeback fee is levied. In Xero or QuickBooks the cleanest treatment is to reverse the revenue (a debit to sales, or to a dedicated chargeback losses account if you want the gross sales figure to stay intact for analysis), recognise the chargeback fee as a separate expense, and write down any inventory that will not be returned.

A worked example for a single £120 order lost to a chargeback, with a £15 fee and £40 of cost of goods that will not be recovered:

The total cost of the lost order is not the £120 sale value, it is the £120 plus the £15 fee plus the £40 of goods you no longer have, less any margin you never actually banked. This is why a high chargeback rate erodes profit far faster than the headline sale values suggest, and why categories with high fraud or "item not received" rates need a realistic chargeback provision rather than ad-hoc write-offs.

Provisioning a dispute reserve

For a brand with a predictable chargeback rate, accruing a provision matches the expected loss to the period the sales were made, rather than letting losses land randomly whenever a chargeback completes months later. The provision is an estimate based on your own historical chargeback rate applied to current-period sales. It is a debit to a chargeback expense and a credit to a provision liability on the balance sheet; when an actual chargeback completes, it is charged against the provision rather than hitting the P&L again.

Under UK GAAP, FRS 102 Section 21 covers provisions: you recognise one when there is a present obligation from a past event, an outflow is probable, and the amount can be estimated reliably. A consistent chargeback history gives you the reliable estimate. The provision should be reviewed each period and trued up against actual experience, so it does not drift away from reality.

Accounting for held and frozen funds

When a processor holds funds, either a rolling reserve or a freeze pending a dispute, that money is still the seller asset. It belongs on the balance sheet as a receivable (often called a "processor reserve" or "funds held by payment provider" account), not netted out of revenue or ignored. The mistake we see most often is brands treating the net deposit as the whole story, so the held portion silently vanishes from the books and the bank reconciliation never balances.

• Record the full gross settlement, then move the held portion to a "funds held by processor" receivable account.
• When the processor releases the reserve, clear it from the receivable into the bank.
• Reconcile the receivable balance against the processor reserve report each period; a growing unexplained balance usually means releases are not being matched.
• For Amazon specifically, the account-level reserve appears on the settlement report and must be tracked the same way: a receivable, not a reduction in sales.

Treating held funds as a receivable also keeps the cash flow forecast honest. A growing reserve looks like healthy sales on the P&L while quietly starving the bank account, which is a classic cause of profitable e-commerce brands hitting a cash wall. Forecasting the reserve build and release alongside the sales line prevents that surprise.

The VAT position on refunds and chargebacks

When a sale is reversed by a refund or a chargeback, the output VAT originally charged on that sale should also be reversed. If you accounted for VAT on a £120 standard-rated sale (£20 of output VAT), and the sale is charged back, you reduce your output VAT by that £20 in the period the reversal occurs. The mechanism is a VAT credit note or a reduction in the relevant VAT return box, depending on your software. Failing to reverse the VAT means you over-pay HMRC on sales that never completed.

Note the distinction: the chargeback fee charged by the processor is a separate supply. Whether you can recover input VAT on it depends on whether the processor issues a proper VAT invoice, and many payment processor fees are exempt financial services with no VAT to recover. Check the processor documentation rather than assuming the fee carries recoverable VAT.

Building a chargeback and dispute log

A simple log, maintained monthly, turns chargebacks from an accounting nuisance into a managed process. The log should capture the order reference, the disputed amount, the reason code, the date raised, the outcome, and the date funds were finally settled or released. Reconciling this log against the processor dispute report each month is what catches the dispute that was won but never had its held funds released back, which is surprisingly common.

When a dispute is won

If a dispute resolves in the seller favour, any funds held during the case are released and the original sale stands. The accounting is to clear the held-funds receivable back to the bank when the release lands, and reverse any provision you raised for that specific case. The chargeback fee may or may not be refunded depending on the processor; record the fee as an expense if it is retained, or reverse it if refunded.

How do I reduce chargebacks rather than just account for them?

• Clear billing descriptors so the customer recognises the charge on their statement and does not raise a "fraud" dispute on their own purchase.
• Responsive customer service so refund requests come to you directly rather than through the card issuer.
• Accurate product descriptions and delivery tracking to defeat "item not received" and "not as described" claims with evidence.
• Fraud screening tools (3D Secure, address verification) for high-risk categories and order values.
• A defined refund policy applied consistently, so genuine grievances are resolved before they escalate to the card network.

Should chargeback losses sit in cost of sales or below the line?

There is no single mandated treatment, but consistency matters. Many e-commerce brands keep a dedicated "chargeback and fraud losses" account in operating expenses so the figure is visible and trackable as a percentage of revenue, rather than burying it inside cost of sales where it distorts gross margin. The key is to pick a treatment, apply it every period, and ensure the management accounts surface the chargeback rate as a monitored KPI rather than an invisible leak.

What records does HMRC expect for reversed sales?

For VAT purposes, you need to evidence why output VAT was reduced: the chargeback notification or refund record, the original sale, and the link between them. Under Making Tax Digital, these adjustments should flow through your accounting software rather than being made as manual overrides on the return. A clean chargeback log plus the processor reports is normally sufficient evidence; the weakness HMRC looks for is output VAT reductions with no supporting documentation behind them.