How UK Crypto Tax Calculators Work (and Why FIFO Fails)
A FIFO crypto tax calculation can misstate a UK gain because UK CGT needs Section 104 pooling. Learn what a UK calculator must do differently.
Searching for a crypto tax calculator is the easy part: there are many options. The important part is checking the method and the source history behind the total. A tool can look polished, import quickly, and still use a cost-basis method that does not match UK rules.
The single thing that separates a UK-correct calculator from a US-built one is the cost-basis method. HMRC requires Section 104 pooling: a weighted-average cost per token. FIFO (first in, first out) is a different method used in other jurisdictions. Run FIFO on UK disposals and your gain is mis-stated from the first sale.
This guide is about choosing and sanity-checking the tool, not re-teaching the rule. It covers why so many calculators default to FIFO, what that does to your number, the checklist a UK-correct calculator has to satisfy, and the red flags that tell you a tool isn't ready for an HMRC return. For the mechanics of the pooling rule itself, we'll point you to the deep-dive rather than repeat it.
Why FIFO is the wrong baseline for UK CGT
Some crypto tax calculators support several jurisdictions and cost-basis methods. Under US rules, individuals can use FIFO or specific identification to choose which lot they are selling. So the default cost-basis engine in those tools is FIFO, and the UK is handled, if at all, as a regional setting bolted on afterwards.
The UK does not work that way. HMRC treats cryptoassets as fungible and requires you to pool all your holdings of the same token into a single Section 104 holding at average cost (CRYPTO22200, s104 TCGA 1992). FIFO and LIFO are not valid methods for individuals. A calculator that quietly applies FIFO (or applies it because nobody flipped it into UK mode) is answering a question HMRC never asked.
Exchange exports and platform reports may also be scoped to one venue or use a method that is not the UK matching order. That is why Coinbase's FIFO report has to be re-pooled for HMRC before it's safe to file. The export is accurate for what it is, just answering the wrong country's rules.
What FIFO vs Section 104 does to your number
The gap isn't academic: the two methods can produce very different gains on the exact same disposal. Here is a deliberately short illustration with two acquisitions and one sale (and no same-day or 30-day matching in play, to keep it clean):
Scenario: two ETH buys, one sale
Jan: buy 1 ETH at £1,000
Jun: buy 1 ETH at £3,000
Later: sell 1 ETH for £3,500
Section 104 (HMRC-correct):
Pool average cost = (£1,000 + £3,000) ÷ 2 = £2,000/ETH
Gain = £3,500 − £2,000 = £1,500
Chargeable gain: £1,500
FIFO (US default, wrong for the UK):
Matches the oldest lot: cost £1,000
Gain = £3,500 − £1,000 = £2,500
Chargeable gain: £2,500
Same sale, £1,000 more gain under FIFO: roughly £240 of extra CGT at the 24% higher rate you don't actually owe. (In a falling market FIFO swings the other way and understates, which is just as wrong.) Across hundreds of disposals the drift compounds.
That is the whole point of pooling: one average cost, not a guess about which coin you sold. The full rule is more involved than this illustration: HMRC checks a same-day rule and a 30-day Bed & Breakfast rule before the pool, and gets the London-timezone day boundary right near 5 April. We cover all of that, with worked examples, in the Section 104 pooling rule explained and the same-day & 30-day Bed & Breakfast rules. For choosing a calculator, the takeaway is simpler: if it runs FIFO, it's running the wrong rule.
What a UK-correct crypto tax calculator must do
Pooling is necessary but not sufficient. A calculator you can file from has to handle the whole HMRC pipeline, not just the average cost. Hold any tool against this checklist:
- Section 104 pooling at average cost: one pool per token, weighted average cost basis. Not FIFO, not LIFO.
- Same-day then 30-day Bed & Breakfast matching: applied in HMRC's exact priority order before the pool is consulted, with the tax-year boundary computed in the Europe/London timezone.
- Qualifying transaction fees: directly associated acquisition or disposal fees can affect pool cost or gain under CRYPTO22150. Failed, income-related, or unrelated fees should not be included automatically.
- Cross-platform pooling: HMRC pools the same token across every exchange and wallet you use, so your Coinbase ETH and your on-chain ETH share one pool. A tool that calculates each platform in isolation gets the cost basis wrong on anything you moved between them.
- SA108 boxes 13.1–13.8: the dedicated cryptoasset boxes introduced for 2024/25. The output has to map onto them, not just give you a single headline number.
- Box 51 for the 2024/25 split year: disposals before 30 October 2024 are taxed at 10%/20% and those from 30 October at 18%/24%. The calculator has to apportion by disposal date and fill Box 51, or you over- or under-pay on that year.
- Show Working per disposal: the matching rule used, the pool snapshot before and after, the cost basis and the price source. Without it, neither you nor your accountant can check the number.
That last point is the one investors skip and accountants insist on. A figure with no derivation is impossible to defend in an HMRC enquiry. This checklist is exactly what a UK crypto tax calculator built for HMRC should do for you automatically: pooling, matching, gas, the SA108 boxes and the split-year adjustment, with the working shown for every line.
Red flags that a calculator isn't UK-ready
You can usually spot a tool that will let you down before you pay for it. Watch for these:
| Red flag | Why it matters for HMRC |
|---|---|
| FIFO by default, no UK mode | Wrong cost-basis method: the gain is mis-stated from the first disposal |
| No 30-day or same-day matching | Skips the anti-avoidance rules that override the pool, so loss harvesting and rebuys come out wrong |
| No Box 51 / split-year handling | Can't apply the 30 October 2024 rate change correctly on a 2024/25 return |
| Per-platform only | Won't pool the same token across exchanges and wallets, so transfers corrupt the cost basis |
| No per-disposal working | A black-box total you can't verify or defend in an enquiry |
Bridging and wrapping are a useful tell too. HMRC says cross-ledger treatment depends on the facts, while retaining beneficial ownership is central to whether a disposal occurs. ChainTax applies disclosed basis-carry treatment to supported same-owner, same-asset routes, while mismatched assets or incomplete evidence need review. If you want to see how the main UK tools line up on exactly these points, we maintain a side-by-side breakdown: Best Crypto Tax Software UK.
How ChainTax calculates UK crypto tax
ChainTax starts from HMRC's manual, not a US default. When you scan a wallet or import an exchange CSV, the engine:
- Pools at average cost, never FIFO. Every token gets one Section 104 pool, built across all your wallets and exchanges, so a transfer between platforms never corrupts the cost basis. Categorised as a disposal only when there is a genuine change of beneficial ownership.
- Applies the matching rules in order. Same-day, then the 30-day Bed & Breakfast rule, then the pool, with the day boundary in the Europe/London timezone so disposals near 5 April land in the right tax year.
- Classifies DeFi correctly. Deterministic detectors for Uniswap, Aave, Lido, Curve, 1inch and more read each transaction's intent, so LP adds, bridges, wraps and staking rewards are handled as a disposal, transfer or income as the rules require, with unresolved cases left visible for review.
- Fills SA108 and Box 51. Results map straight onto boxes 13.1–13.8, and the 2024/25 split-year rate adjustment is computed for you: the part nearly every other tool leaves you to apportion by hand.
- Shows the working on every disposal. The matching rule, the pool before and after, the cost basis and the price source with a confidence rating: the audit trail an accountant can sign off, and the kind of detail a single cross-platform pool needs to reconcile.
You can calculate your crypto CGT free for up to 200 transactions, including classifications, review checks, and a preview of the report structure. You only pay when you download the PDF and CSV reports with reviewable working.
Related reading
See your gain calculated the HMRC way
Section 104 pooling, same-day and 30-day matching, gas as an allowable cost, SA108 boxes and the 2024/25 split-year adjustment, with the working shown on every disposal. Free for up to 200 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: s104 TCGA 1992 (pooling), s106A TCGA 1992 (Bed & Breakfast), CRYPTO22200 (Section 104 pooling), CRYPTO22150 (allowable costs). CGT rates: 18% basic / 24% higher from 30 October 2024 (Autumn Budget 2024); 10%/20% before. Annual exempt amount £3,000 for 2024/25 and 2025/26.
Related articles
Negligible Value Claims: Tax Relief for Worthless Crypto
A rugged token still in your wallet may be worth a capital loss. How negligible value claims work under s.24 TCGA 1992, what qualifies, and the backdating trap.
eToro Tax UK: Crypto, CFDs and HMRC Reporting
Learn how eToro real crypto and CFDs are taxed differently in the UK, why USD statements need GBP conversion, and how HMRC matching applies across accounts.
Uphold Tax UK: XRP Trades, Staking and HMRC Reporting
CARF obligations began in 2026, with first reports due in 2027. Why Uphold’s anything-to-anything trades can create missed disposals and how Section 104 applies.