HMRC mistakes on crypto returns often start with the classification, not the numbers. A clean dashboard can still miss bed and breakfasting, misapply share pooling, or leave out income from staking, airdrops, or DeFi. For anyone in England facing a Self Assessment deadline, an HMRC query, or an accountant request, the real test is whether the report matches UK filing rules and can be used without last-minute fixes.
The best crypto tax software in the UK is the one that can import wallets and exchanges, calculate HMRC-style gains and income correctly, and produce a report that the user or accountant can actually use. The right choice depends on transaction volume, DeFi or NFT activity, and whether a free plan, SA108 support, or full HMRC compliance is needed.
Which crypto tax software suits UK filing?
The right platform for UK filing is the one that matches HMRC rules, not just exchange balances. A tool can look tidy on screen and still misstate a disposal if it mishandles pooling, same-day matching, or transfers between wallets.
The best fit usually depends on three things: how many transactions you have, whether you earned staking or mining income, and whether you need accountant-ready exports. The strongest choice is not always the cheapest one.
HMRC taxes cryptoassets by the nature of the activity, not by the platform used to hold them. A disposal can create Capital Gains Tax, while staking rewards or mining receipts may fall under Income Tax.
HMRC rules drive the choice
Crypto tax software for the UK must separate disposals from income items. That matters because a swap, a sale, and a staking reward do not sit in the same box on a return.
The software also needs to handle pool-based cost basis for fungible tokens. If it treats each purchase as isolated, the gain can drift away from HMRC treatment very quickly.
For UK users, the software should support same-day matching, the 30-day rule, and Section 104 pooling. If it does not, the final figures need manual review before filing.
The cheapest plan is not always cheapest
Headline price is only part of the bill. A low-cost plan can become expensive when the transaction count rises and the software pushes you into a higher tier.
That is where many users make the first mistake. They choose the cheapest plan in January, then discover in March that exports, extra wallets, or DeFi history sit behind a higher fee.
A platform that costs more up front can still be cheaper overall if it saves accountant time. That point matters when the return has mixed capital gains and income entries.
How UK crypto tax is actually filed
Filing crypto tax in the UK usually means four steps: gather every transaction, classify each event, calculate gains and income, then transfer the final figures into Self Assessment and SA108. The software does not file for the taxpayer; it prepares the numbers.
The first pass should always be data collection. If deposits, withdrawals, swaps, and transfers are incomplete, the calculation will be fragile before it even starts.
The legal position is set by HMRC guidance on cryptoassets and capital gains. GOV.UK keeps the main framework here: HMRC guidance on cryptoassets.
Build the transaction record first
Start with exchanges, then add wallets, then reconcile internal transfers. Internal movement is not taxable, but it still matters because it explains where the asset came from and where it went.
The export set should normally include trade history, deposit and withdrawal logs, realised gain reports, and any notes for manual corrections. A clean CSV from one venue is rarely enough by itself.
An anonymous case is common here: a trader moved coins across three wallets and two exchanges, then saw six missing cost basis entries. After the transfers were matched, the taxable gain fell sharply because the software had been treating internal moves as disposals.
Complete self assessment and SA108
The final capital figures usually feed into SA108, which sits alongside the Self Assessment return. The software should give disposal proceeds, allowable costs, and realised gains or losses in a form an accountant can read quickly.
If there are staking rewards, mining receipts, airdrops, or some DeFi earnings, those figures may also need Income Tax treatment. That is where many generic tools need review, because the label on screen does not decide the tax result.
The best output is simple: totals by tax year, event type, and asset. Anything less usually creates more work at filing stage.
What the accountant needs from you
An accountant usually needs more than a PDF summary. They need the raw export, the calculation logic, and the assumptions behind manual edits.
Send the transaction files, the realised gains report, the income summary, and a short note for anything unusual. That note should cover lost wallets, bridged assets, manual transfers, and any entries you overrode.
A practical UK filing process starts with gathering every exchange CSV, wallet import, and transfer record, then reconciling missing entries before generating the tax report. Once the transactions are classified, the software should separate disposals from income events and produce year-end figures for Capital Gains Tax and Income Tax. In practice, the final check is whether the report maps cleanly to Self Assessment and SA108: disposal proceeds, allowable costs, and gains must be ready to copy across, while staking rewards, airdrop income, and mining receipts should be clearly separated.
For example, if a user sold ETH, bridged USDC, and received staking rewards in the same tax year, the software output should show those items in different sections so the accountant can file without rebuilding the history from scratch.
Compare software by cost, limits, and output
The best comparison for UK users is not a feature list. It is whether the software can handle your real transaction count, produce usable HMRC-style reports, and stay affordable after plan upgrades.
That means cost needs to be measured at your volume, not at the brochure price. A platform with a low entry plan can still become the most expensive once you cross a few hundred trades.
| Software |
Free plan limit |
HMRC-style gains |
SA108 export |
Income items |
Cost at higher volume |
| Koinly |
Plan-limited |
Yes |
Yes |
Partial, with manual review |
Medium to high |
| CoinLedger |
Plan-limited |
Yes |
Yes |
Partial, with manual review |
Medium |
| Crypto Tax Calculator |
Plan-limited |
Yes |
Yes |
Strong for complex activity |
Medium to high |
| Recap |
Plan-limited |
Yes |
Yes |
More UK-focused reporting |
Medium |
The table makes one point plain: the cheapest plan is rarely the cheapest result. A trader with 50 transactions may stay on a low tier, while a DeFi user with 1,500 events may pay far more than expected.
Price is volume, not headline
The price that matters is the price at your real transaction count. That includes transfers, swaps, liquidity moves, and any wallet imports that count against plan limits.
A user with one exchange and 20 disposals may stay close to the advertised entry price. Someone with four exchanges and a messy wallet history can reach a much higher tier very quickly.
The choice becomes clearer when the accountant asks for exports. A report that looks cheap can still create billing friction if the final files need manual rescue.
Decision path
Few trades, one exchange, no income items
Multiple wallets, transfers, and swaps
DeFi, staking, airdrops, or mixed income
What to prioritise
Low-cost plan with clean CSV export
Accurate transfer matching and pooling
Manual review support and accountant export
Price comparisons only become useful when they are tied to transaction volume. A free plan may look attractive, but many crypto tax software UK providers cap the number of transactions, wallets, or imported records before you must upgrade. A user with 50 trades may stay within a lower tier, while a DeFi trader with hundreds of swaps, LP movements, and wallet imports can move into a much higher annual cost very quickly.
In practice, the total price should include the plan fee, any add-ons for extra wallets or exchanges, and the time spent fixing incomplete exchange integrations. A realistic comparison therefore looks at what the software costs at your actual volume, not at the introductory headline price.
The tax traps software misses
The most frequent errors are not dramatic. They are quiet mismatches that change the final number without looking obvious in the dashboard.
The error most often seen at this stage is trusting the classification screen too much. A platform can label a transaction as a disposal, but HMRC treatment may change once the underlying facts are checked.
Bed and breakfasting changes the gain
Bed and breakfasting is the matching of a disposal against a later repurchase within 30 days. It can shift the gain away from the simple average cost the user expected.
This matters because software must apply matching rules in the right order. Same-day matching comes first, then the 30-day rule, then the Section 104 pool.
A common mistake is to view the pool as the only answer. It is not. The matching order can change the result even when the total holding looks stable.
Share pooling is not optional
Share pooling means identical cryptoassets are grouped for cost basis purposes. Each acquisition can affect the pooled average cost, and each disposal can draw from that pool.
This is where generic portfolio trackers often fall short. They show holdings, but they do not always produce a tax pool that matches HMRC logic.
The data points to a simple pattern: once a user has repeated buys, sells, and transfers, pooling affects almost every later disposal. That is why the output has to be checked before filing.
Section 104 pooling is easiest to understand with a simple example. If you bought 0.5 BTC at £20,000, then another 0.5 BTC at £30,000, your pooled cost basis is £25,000 for 1 BTC, before any matching rules are applied. If you later sell 0.4 BTC for £18,000, same-day acquisitions are matched first, then any coins bought in the next 30 days under the 30-day bed and breakfasting rule, and only the remainder comes from the pool. That order can materially change the gain or loss.
A taxpayer who sells at a loss and repurchases the same asset within 30 days may find the loss deferred or reduced by matching, which is why a crypto tax calculator needs to explain the calculation clearly rather than simply showing one final figure.
Losses, bed and breakfasting, and pooling
Losses can reduce a tax bill, but only if the records are clean and the disposals are correctly classified. A missing transfer or wrong wallet link can wipe out a genuine loss claim.
HMRC expects the taxpayer to preserve the trail. The software can help, but it cannot replace evidence when the figures are questioned later.
For reference, HMRC’s own cryptoasset guidance sits within the broader Self Assessment framework on GOV.UK, and the return deadline remains 31 January following the tax year end. See the filing rules here: Self Assessment guidance.
Tax loss harvesting only works
Tax loss harvesting means realising a loss so it can offset gains where the rules allow. It only works when the disposal is genuine and documented.
If a wallet transfer was really an internal move, it is not a loss event. If a sale was followed by a near-term buyback, the matching rules may change the claim.
A practical warning: many reports show losses that look helpful but fail once the transaction history is cleaned up. That is why the export matters more than the headline tax summary.
Example pattern to check
Sell at a loss, buy back within 30 days, then check the matching outcome before filing. The disposal may not land where the user expects, and the pool cost can move too.
This is where manual review pays off. A small correction can change both the current year figure and the cost basis carried forward.
If the software cannot explain why the number changed, the user should not file on trust alone. The report needs to be defensible.
Evidence and audit trails HMRC may ask for
An HMRC enquiry usually starts with evidence, not with a technical debate over the formula. The first question is whether the taxpayer can show the source of the numbers.
A clean audit trail covers exchange CSV files, wallet addresses, screenshots of missing transactions, and a short note for each manual adjustment. That is what turns a calculation into a file that can be defended.
The FCA publishes clear consumer warnings on crypto risk, while HMRC focuses on tax treatment. Those are separate issues, but both point in the same direction: records matter. The FCA’s crypto guidance is here: FCA cryptoasset guidance.
Keep a defence file
A defence file is simply the set of records that explains every number in the return. It should let another person follow the trail without guesswork.
Include transaction exports, notes on transfers, receipts for fees, and evidence for any disposals that were reversed or corrected. Keep it organised by tax year.
The image attached to the article would make this easier to follow, because a simple flow from exchange export to final SA108 figure is easier to verify than a long spreadsheet note.
DeFi and mixed income need manual checks
DeFi, staking, airdrops, and some NFT activity can produce tax treatment that software cannot classify cleanly on its own. That is the point where manual review becomes sensible.
This works well in theory, but in practice the labels vary by platform and chain. A reward that looks like capital growth on screen may need Income Tax treatment after review.
The safest rule is plain: if the activity was not a simple buy, sell, or transfer, it deserves a second look before filing.
What to choose and what to send
For most users in England, the best choice is the platform that gives the cleanest HMRC-style report for the least total cost at their real transaction volume. If the activity is simple, a lower-cost plan can be enough; if the history is messy, accuracy matters more than the entry price.
The practical decision is this: choose software that supports pooling, same-day matching, and accountant exports, then test it with one tax year before committing to a full review. If the tax year includes DeFi or income items, expect at least one manual pass.
When the lower-cost option is enough
A lower-cost option works when the user has a small number of transactions, one or two exchanges, and no complicated income events. The report still needs to show gains clearly and export cleanly.
If the user only wants a portfolio tracker, a tax platform may be overkill. If the accountant already runs the full process in-house, the software choice may be secondary.
What to send to an accountant
Send the raw transaction exports, the realised gains report, the income summary, and a short note on manual edits. Add any wallet addresses, exchange names, and dates for missing transfers.
A good handover saves time. It also reduces the risk of the accountant rebuilding the whole history from scratch.
This guidance does not apply if there were no taxable crypto transactions in the UK tax year, if the user only needs a portfolio tracker, or if an accountant already controls the full calculation process.
Frequently asked questions
What is the best crypto tax software in the UK?
The best option is the one that produces HMRC-style gains and usable exports. For many users, that means checking support for pooling, same-day matching, and accountant handover files before looking at price.
The right choice depends on volume and complexity. A simple trader and a DeFi user should not use the same selection criteria.
Does free crypto tax software work for UK self
It can work for very small histories. Free plans often cap transactions or block the final export you need for filing.
That makes them useful for testing, not always for final submission. If the return needs SA108 figures or income review, the free tier may be too limited.
How do i fill in SA108 for crypto gains?
Use the realised gains figures from the software and place them into the Capital Gains section of Self Assessment. The key fields are disposal proceeds, allowable costs, and the gain or loss for the tax year.
If you also had staking or mining income, that may sit elsewhere on the return. The software should separate those items, but the taxpayer should still check them.
Can crypto losses reduce my tax bill?
Yes, if the losses are realised and correctly recorded. The software must show the disposal and match it under HMRC rules.
A paper-thin loss claim fails quickly if transfers are missing or the wallet trail is unclear. Keep evidence for the disposal and the original cost basis.
Does bed and breakfasting still matter for crypto
Yes, it still matters. A buyback within 30 days can change which acquisition matches the disposal.
That can alter the gain even when the holding looks almost unchanged. Good software should apply the rule automatically, but the output still deserves a check.
What should i give my accountant instead of just
Send the CSV exports, realised gains report, income summary, and notes for manual changes. A PDF alone is not enough if HMRC asks how the figure was built.
The accountant needs the trail, not just the result. That saves time and makes later review far easier.
The safest choice for filing now
The safest choice is the software that fits the history you actually have, not the one with the lowest advertised price. For straightforward activity, a cheaper plan may be enough; for pooled assets, DeFi, or staking, the better report usually saves money later.
Use one tax year as a test, check the SA108 output, and compare the final cost at your true transaction count. If the software cannot explain the numbers cleanly, the final filing needs manual review before it goes anywhere near HMRC.
