Coinbase Tax UK — Why Your Coinbase Report Isn't Enough for HMRC
Coinbase uses FIFO. HMRC requires Section 104 pooling. If you've ever used DeFi or another exchange, Coinbase's tax report gives you the wrong number. Here's exactly how to get it right.
From 1 January 2026, Coinbase reports your full transaction history to HMRC under CARF (Crypto-Asset Reporting Framework). That means HMRC already knows what you bought, sold, and earned. The question is whether your Self Assessment return matches what they have.
Here is the problem: Coinbase's own tax report uses FIFO (first in, first out). HMRC does not accept FIFO. They require Section 104 pooling — a weighted average cost basis method. If you have ever used another exchange or interacted with DeFi, Coinbase's numbers will be wrong because it only sees trades on its own platform.
This guide explains exactly how Coinbase transactions are taxed under HMRC rules, why Coinbase's tax report falls short, and how to file correctly — especially if you also use DeFi.
Does Coinbase report to HMRC?
Yes. Under CARF, which came into effect on 1 January 2026, UK-based crypto exchanges must collect and report user transaction data to HMRC. The first data exchange is expected in May 2027, covering the 2026 calendar year. Coinbase, as an FCA-registered business, is fully in scope.
What HMRC receives includes your name, address, tax identification number, and a full record of acquisitions, disposals, and income events. This is not a summary — it is transaction-level data. If your Self Assessment does not match what Coinbase reported, HMRC has the tools to flag the discrepancy.
CARF applies to 2026 onwards
CARF reporting covers transactions from 1 January 2026. Earlier tax years (2024/25, 2023/24) are not covered by automatic exchange reporting, but HMRC has already sent over 100,000 warning letters to crypto holders using data obtained directly from exchanges.
Why Coinbase's tax report doesn't work for UK investors
Coinbase generates a tax report that shows your gains and losses for the year. The problem is that it uses FIFO — matching each sale against your earliest purchase. HMRC requires Section 104 pooling, which uses a weighted average cost basis across all your holdings of a given token.
FIFO and Section 104 produce different gains. Sometimes significantly different. If you bought ETH at £500, then at £2,000, then at £1,500, and sold some, FIFO always uses the £500 purchase first. Section 104 uses the average of all three. Depending on market conditions, FIFO can overstate or understate your gain by hundreds or thousands of pounds.
Worse, Coinbase can only see trades on Coinbase. If you also bought ETH on Binance, received ETH as staking income from Lido, or swapped USDC for ETH on Uniswap — all of those acquisitions should be in the same Section 104 pool. Coinbase has no visibility into any of that.
Section 104 pools are per-asset, not per-platform
This is the single most important concept for UK crypto tax, and it is the reason no single exchange can give you the right number on its own.
Under HMRC rules, you maintain one Section 104 pool per token. Not per exchange, not per wallet — per token. Every acquisition of ETH, regardless of where it happened, goes into the same ETH pool.
Worked example
Buy 2 ETH on Coinbase at £1,500 each = £3,000 total cost
Receive 0.5 ETH staking income on Lido at £2,000 each = £1,000 cost basis
Pool: 2.5 ETH, total cost £4,000, average cost £1,600 per ETH
Sell 1 ETH on Coinbase for £2,500
Gain = £2,500 − £1,600 = £900
Coinbase thinks your pool is 2 ETH at £1,500 avg and would report a gain of £1,000. The correct gain is £900.
The £100 difference in this simple example grows with every additional source of the same token. DeFi users with multiple acquisition sources — swaps, staking rewards, LP removals, airdrops — can see much larger discrepancies.
What Coinbase transaction types mean for HMRC
Coinbase uses its own terminology for transaction types. Here is how each one maps to HMRC tax treatment:
| Coinbase type | HMRC classification | Tax treatment |
|---|---|---|
| Buy | Acquisition | Enters S104 pool. No tax event. |
| Sell | Disposal (Capital Gain) | CGT at 18% basic / 24% higher |
| Convert | Disposal + Acquisition | Two events: dispose of token A, acquire token B |
| Coinbase Earn | Income | Miscellaneous income at 20/40/45% |
| Learning Reward | Income | Miscellaneous income at 20/40/45% |
| Staking Income | Income | Miscellaneous income at FMV on receipt date |
| Send | Transfer (usually) | Non-taxable — unless sent to a third party as payment |
| Receive | Transfer (usually) | Non-taxable — unless received as income |
How to export your Coinbase CSV
To get your full transaction history from Coinbase:
- Log in to Coinbase on desktop (not the mobile app)
- Go to Reports (under your profile menu)
- Select Transaction History
- Click Generate Report
- Choose your date range (use "All time" for complete history)
- Download the CSV file
The CSV includes columns for Timestamp, Transaction Type, Asset, Quantity, Spot Price, Total, and Fees. This is the file you upload to ChainTax.
Coinbase Earn and Learning Rewards
Coinbase Earn rewards and Learning Rewards are classified as miscellaneous income by HMRC — not capital gains. They are taxed at your income tax rate (20%, 40%, or 45%) depending on your total income for the year.
Importantly, these rewards also enter your Section 104 pool as acquisitions at fair market value (FMV) on the date received. This means they increase your pool's total cost basis, which reduces your capital gain when you eventually sell.
Income from crypto goes on SA100 (your main tax return) under "Other income" — not on SA108. This is a common mistake. For more detail, see how to report staking rewards to HMRC.
Convert transactions — the hidden disposal
When Coinbase shows "Converted 0.5 ETH to 1,000 USDC", it looks like one event. For HMRC, it is two:
- Disposal of 0.5 ETH at the GBP market value at the time of the conversion. Capital gains tax applies to the difference between proceeds and your S104 cost basis for ETH.
- Acquisition of 1,000 USDC at the same GBP value. This enters your USDC Section 104 pool.
This is identical to how HMRC treats DeFi token swaps. Every token-to-token conversion is a disposal of the outgoing token, even without touching GBP. Many Coinbase users have dozens of Convert transactions without realising each one is a taxable disposal.
What if I also use DeFi?
This is where most crypto tax tools break. If you buy ETH on Coinbase and then deposit it into Aave, swap it on Uniswap, or bridge it to Arbitrum, your Section 104 pool needs to reflect all of that activity — not just what happened on Coinbase.
The same-day and Bed & Breakfast rules also apply across platforms. If you sell ETH on Coinbase on Monday and buy ETH via a Uniswap swap on Wednesday, the B&B rule matches those transactions — even though they happened on different platforms. No single-platform tool can detect this.
Why single-platform reports fail
Coinbase only sees Coinbase. Your DeFi wallet only sees on-chain activity. But HMRC treats all your crypto as one unified picture. Section 104 pools, same-day matching, and B&B rules all operate across every platform and wallet you use. You need a tool that sees everything.
How ChainTax handles Coinbase + DeFi together
ChainTax is designed for exactly this scenario. Here is how it works:
- Import your Coinbase CSV. Upload the CSV file from Coinbase. ChainTax auto-detects the format, parses every transaction type (Buy, Sell, Convert, Earn, Staking), and classifies each one for HMRC.
- Connect your DeFi wallets. Add your Ethereum, Arbitrum, Optimism, Base, or Polygon wallet addresses. ChainTax scans your full on-chain history and classifies every transaction using 28 protocol-specific classifiers.
- Unified Section 104 calculation. Coinbase trades and DeFi activity are merged into a single S104 pool per token. Same-day and B&B matching applies across all sources.
- 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.
You can also import from Binance and Kraken alongside Coinbase. All sources feed the same tax engine.
See your Coinbase gains in 30 seconds
Import your Coinbase CSV, connect your DeFi wallets, and get a unified HMRC-ready report with correct Section 104 pooling. Every disposal shows full working. Free for up to 75 transactions.
This article is for informational purposes only and does not constitute tax, legal, or financial advice. Tax rules can change, and individual circumstances vary. Always consult a qualified tax adviser before filing your Self Assessment return. HMRC guidance referenced: CRYPTO22100 (disposals), CRYPTO22200 (same-day and B&B matching), CRYPTO61100 (DeFi staking income), s104 TCGA 1992. CGT rates and annual exempt amounts from GOV.UK (2024/25 and 2025/26 tax years).
Related articles
SA108 Crypto 2024/25 — Boxes 13.1 to 13.8 and Box 51 Explained
2024/25 is the first year with dedicated crypto boxes on SA108 — and it's a split year for CGT rates. Every box explained with worked examples, including the Box 51 adjustment that nobody else covers.
CEX vs DeFi — How Your Crypto Is Taxed Differently in the UK
HMRC doesn't care where you traded — all disposals of the same token share one Section 104 pool. But exchange trades and DeFi activity create very different classification challenges. Here's why you need one tool for both.
Do I Need to Report Crypto to HMRC? The Complete Checklist
Sold, swapped, staked, or earned crypto? You probably need to report it — even if you lost money. Here's exactly when HMRC requires a Self Assessment return, what triggers reporting, and the thresholds that catch most DeFi users.