Coinbase Tax UK: Why Your Tax Report Isn't Enough for HMRC
Download Coinbase history for UK tax, check HMRC reporting dates and combine your records for same-day, 30-day and Section 104 matching. CSV checklist included.
From 1 January 2026, in-scope providers collect prescribed customer identity and transaction information under CARF (Crypto-Asset Reporting Framework). Annual reports can give HMRC aggregate acquisition, disposal, exchange, and transfer information to compare with returns and other records.
Check the report's coverage and matching method. A Coinbase-only export does not establish your activity elsewhere. For fungible tokens, UK rules apply same-day and 30-day matching before Section 104 pooling. A FIFO gain/loss summary is not a substitute for that calculation.
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.
How to download Coinbase transaction history for UK tax
- Sign in to Coinbase directly and open its Taxes or statements area. Use the transaction-history export rather than relying only on a gain/loss summary.
- Choose the relevant date range and CSV format where available. Include earlier purchases needed to establish costs, not just the year in which you sold.
- Keep the original file. Separately gather records from other exchanges, wallets and any legacy accounts; a Coinbase export cannot establish your whole history.
Menu names and report formats can vary. Coinbase documents tax-report downloads and custom account statements. Non-US customers can use transaction history to help with local obligations; it is not a completed UK return.
Import the CSV, then check the evidence
Check your Coinbase history free, then upload a supported transaction-history CSV in the Coinbase import flow. If the format is rejected, check the import instructions rather than renaming unrelated report columns to force it through.
- Compare the imported date range and transactions with the original export.
- Bring in other sources and identify transfers between accounts you own.
- Investigate missing purchase costs, unpriced income and unclear activity before relying on a gain or tax estimate.
- Open the working to check same-day, 30-day and Section 104 matching. Confirm your sources only after checking that the history is complete.
Start with up to 200 transaction records free account-wide. See report prices and capacity limits before importing a larger history.
If purchases are still missing, follow our guide to reconstructing missing crypto purchase history to trace older accounts and check the remaining gaps after importing.
Has an HMRC letter mentioned Coinbase?
Use the Coinbase HMRC letter evidence checklist before deciding whether the figures support confirmation, amendment, disclosure, or adviser-led handling.
Does Coinbase report to HMRC?
Coinbase can be within CARF as a reporting cryptoasset service provider. In-scope providers began due diligence, record keeping and collection on 1 January 2026. The first reports, covering the 2026 calendar year, are due to HMRC by 31 May 2027. HMRC has also obtained exchange information through other channels for earlier years.
Reporting scope follows the CARF provider rules, rather than FCA registration alone. HMRC's reporting guidance distinguishes customer identity information from annual transaction totals by asset and transaction category. A CARF report is not necessarily a line-by-line copy of your account history.
A calendar-year CARF total will not necessarily match a UK tax-year gain. Reconcile dates, transfers and purchase costs before comparing the figures; a difference does not by itself establish unpaid tax or guarantee an enquiry. The CARF 2027 readiness page sets out how to prepare and reconcile your records.
CARF applies to 2026 onwards
CARF collection starts with the 2026 calendar year. It does not cover transactions before 1 January 2026. HMRC may still hold earlier exchange information obtained through other powers and has sent crypto warning letters to crypto holders using data obtained directly from exchanges.
What to check before using a Coinbase tax report
A gain/loss summary is only useful if its records and matching method fit your circumstances. FIFO matches sales against the earliest purchases. UK rules instead use same-day and 30-day matching before 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. If no same-day or 30-day matches apply, Section 104 uses the pooled average instead. Depending on market conditions, FIFO can overstate or understate your gain by hundreds or thousands of pounds.
A Coinbase-only export does not include every source. 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 included in the combined matching calculation. Gather those records separately and check that they are represented.
Section 104 pools are per-asset, not per-platform
Using several exchanges does not create a separate pool at each one. Bring relevant records together before applying the matching rules.
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.
How does HMRC tax USDC rewards on Coinbase?
HMRC taxes USDC rewards earned on Coinbase as miscellaneous income at GBP fair market value on each daily payout date. Reported on SA100 under "Other income" rather than SA108, and taxed at your marginal rate (20%, 40%, or 45%). The same USDC also enters your Section 104 pool at receipt-date value, so any later sale or swap is a separate Capital Gains event.
Worked example: you hold 5,000 USDC on Coinbase across 2025/26 and receive £180 of USDC rewards across the year (paid daily, ~50p per day). That £180 goes on your 2025/26 SA100 as miscellaneous income. Each daily payout also enters your USDC Section 104 pool at the GBP rate on the day it was received, so when you eventually sell or swap that USDC, the gain or loss is calculated against the average pooled cost, not against zero. See exactly how that Section 104 pooling works in our UK crypto tax calculator.
Coinbase's built-in tax report does not split this out correctly for HMRC. The daily payout valuations need to use the GBP rate on the date received, with the acquisition recorded for later matching. ChainTax handles the daily valuation automatically when you import your Coinbase CSV.
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 a single-platform history stops being complete. 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 supported on-chain history using 34 protocol-specific classifiers. Unresolved activity remains visible for review.
- 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 bring in your activity from Binance, Kraken, Crypto.com, eToro, Uphold, and Gemini alongside Coinbase. Import support differs by exchange: eToro, Uphold and Gemini crypto records need conversion to the Koinly universal CSV format or manual entry. Check supported activity and the original records before combining the history.
Weighing up your options first? See how ChainTax compares to Koinly, CoinTracker, and Recap.
Check your Coinbase history and see the working
Import your Coinbase CSV, connect your DeFi wallets, and get a combined UK tax calculation with reviewable Section 104 working. Check missing costs, prices and uncertain activity before relying on the result. Start with up to 200 transaction records free account-wide; report downloads require a paid tax-year plan.
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, 2025/26 and 2026/27 tax years).
Related articles
Crypto.com Tax UK: Does It Report to HMRC?
When Crypto.com can fall within CARF, why one exchange export is not enough for an account-wide Section 104 pool, and how staking and card rewards may be taxed.
Kraken Tax UK: How to Report Your Kraken Trades to HMRC
Kraken's Ledgers CSV is the right export, but XXBT, refids, .S staking suffixes and margin trades need careful normalisation. Here's the UK tax treatment.
Binance Tax UK: How to Report Your Binance Trades to HMRC
Binance CSVs and FIFO reports don't fit HMRC rules. Learn the right Section 104 treatment for trades, staking, fees and multiple exchanges.