Binance Tax UK — How to Report Your Binance Trades to HMRC

Binance is the world's largest crypto exchange by trading volume, and millions of UK investors use it. From 1 January 2026, exchanges operating in the UK must report your full transaction history to HMRC under CARF (Crypto-Asset Reporting Framework). That means HMRC will know what you traded. The question is whether your Self Assessment return matches what they have.

The problem is that Binance's own tax reports are not designed for HMRC. They use FIFO (first in, first out), not Section 104 pooling. They only see trades on Binance. And the CSV export format is notoriously difficult to work with — splitting a single trade across multiple rows.

This guide explains how Binance transactions are taxed under HMRC rules, why Binance's own reports fall short, and how to file correctly — especially if you also trade on other exchanges or use DeFi.

Does Binance report to HMRC?

Yes. Under CARF, which came into effect on 1 January 2026, crypto exchanges with UK users must collect and report transaction data to HMRC. The first automatic data exchange is expected in May 2027, covering the 2026 calendar year.

What HMRC receives includes your name, address, tax identification number, and a full record of acquisitions, disposals, and income events. This is transaction-level data, not a summary.

Even before CARF, HMRC has been proactive. They have already sent over 100,000 warning letters to UK crypto holders using data obtained directly from exchanges. Binance has cooperated with HMRC data requests in the past. The era of under-the-radar crypto trading is over.

Why Binance's own reports don't work for UK tax

Binance generates tax reports and profit/loss summaries, but they have two fundamental problems for UK investors:

1. FIFO, not Section 104. Binance uses FIFO cost basis matching — assigning each sale to your earliest purchase. HMRC requires Section 104 pooling, which uses a weighted average cost basis across all your holdings of a given token. These methods produce different gains, sometimes by thousands of pounds.
2. Single-platform blindness. Binance can only see trades on Binance. If you also bought ETH on Coinbase, received staking rewards from Lido, or swapped tokens on Uniswap, those acquisitions belong in the same Section 104 pool. Binance has no visibility into any of that, so its cost basis calculation is incomplete.

Binance transaction types mapped to HMRC

Binance uses its own terminology in statements and CSV exports. Here is how each type maps to HMRC tax treatment:

The multi-row problem — why Binance CSVs are hard to parse

Unlike Coinbase, which puts one trade per row, Binance's "Generate All Statements" CSV splits a single trade across multiple rows. A typical spot trade produces three separate lines:

1. Buy row — the token you received (e.g. "Buy 0.5 ETH")
2. Transaction Related row — the token you spent (e.g. "Transaction Related −750 USDT")
3. Fee row — the fee deducted (e.g. "Fee −0.0005 BNB")

If you try to process these rows individually, you will double-count transactions or miss the cost basis entirely. The rows must be reconstructed into a single trade event by matching on timestamp and account.

How to export your Binance CSV

To get your full transaction history from Binance:

1. Log in to Binance on desktop
2. Go to Orders → Transaction History
3. Click Generate All Statements
4. Select your date range (use the full range for complete history)
5. Choose CSV format and download

The file includes columns for UTC_Time, Account, Operation, Coin, Change, and Remark. This is the file you upload to ChainTax. Do not use the "Tax Report" export — that uses FIFO and produces incorrect figures for HMRC.

Staking Rewards, Savings Interest, and Distributions

Binance offers several earn products — Locked Staking, Flexible Savings, Launchpool, and promotional distributions. All of these generate tokens that HMRC classifies as miscellaneous income, not capital gains.

Income from crypto is taxed at your income tax rate (20%, 40%, or 45%) based on fair market value at the time of receipt. It goes on SA100 (your main Self Assessment return) under "Other income" — not on SA108. For more detail, see how to report staking rewards to HMRC.

Crucially, income events also enter your Section 104 pool as acquisitions at fair market value. This means staking rewards on Binance increase your pool's total cost basis, reducing the capital gain when you eventually sell. If your tax tool does not classify these correctly, you will overpay CGT.

What if I also use other exchanges or DeFi?

This is where most single-platform reports break down. Under HMRC rules, you maintain one Section 104 pool per token — not per exchange, not per wallet. Every acquisition of ETH, whether on Binance, Coinbase, Kraken, or via a Uniswap swap, goes into the same ETH pool.

The same-day and Bed & Breakfast rules also apply across platforms. If you sell ETH on Binance and buy ETH on Coinbase within 30 days, those transactions are matched — even though they happened on different exchanges. No single-platform tool can detect this.

How ChainTax handles Binance

ChainTax is designed for exactly this scenario:

1. Import your Binance CSV. Upload the "Generate All Statements" CSV. ChainTax auto-detects the Binance format and reconstructs multi-row trades — grouping Buy + Transaction Related + Fee rows by timestamp and account into single events.
2. Import other exchanges too. Upload CSVs from Coinbase, Kraken, or Koinly. All exchange trades feed into the same tax engine.
3. Connect DeFi wallets. Add your Ethereum, Arbitrum, Optimism, Base, or Polygon wallet addresses. On-chain activity is classified using protocol-specific classifiers for Uniswap, Aave, Lido, Curve, and 20+ other protocols.
4. Unified Section 104 calculation. Binance trades, other exchange trades, and DeFi activity are merged into a single S104 pool per token. Same-day and B&B matching applies across all sources.
5. SA108 boxes auto-filled. Boxes 13.1–13.8 are computed directly from the unified calculation. Every disposal shows the matching rule used and the full gain working.

Binance vs Coinbase vs Kraken — does it matter?

From HMRC's perspective, it does not matter which exchange you used. All disposals of the same token share the same Section 104 pool. The difference is in how each exchange exports data:

• Coinbase — one row per event, relatively straightforward CSV format
• Binance — multi-row trades requiring reconstruction, different column names and date formats
• Kraken — paired ledger entries by reference ID, asset names that need normalisation (XXBT → BTC, ZEUR → EUR)

Each format has its own quirks, but they all need to end up in the same place: a unified, HMRC-compliant tax calculation. If you use multiple exchanges, you need a tool that understands all of them. Read more about the differences in CEX vs DeFi tax treatment.