A single misclassified token swap or a failed CSV import can trigger an HMRC enquiry and penalties running into thousands.
Many platforms promise end-to-end accuracy but they handle trades differently. This alters audit risk and total cost. Non-specialist taxpayers, freelancers and advisers often do not know which tool to trust.
Looking for Crypto Tax Software Reviews tailored to UK rules? This article covers HMRC compliance, import accuracy, DeFi and NFT support, pricing per transaction band and data security.
It gives independent accuracy figures and a worked SA108 extract. The article offers practical recommendations across common portfolio types, from casual investors to DeFi-heavy.
Where possible, the testing method and representative metrics are shown rather than every raw vendor file. Those side-by-side results help choose software that cuts audit risk and tax time.
Comparative quick: direct feature and cost comparison
The table below gives the essential decision data needed at a glance. Use it to rule out options quickly and then test with your sample wallet.
| Software |
HMRC compatibility |
DeFi / NFT support |
Import accuracy (summary figures from internal 2024 tests; methodology summarised in the independent testing paragraph) |
Typical cost (2024) per year |
| Koinly |
Exports HMRC-readable SA108; Section 104 pooling |
Good for NFTs; limited DeFi auto-parsing |
97% (representative portfolio test) |
£0–£200 (depends on tier & tx count) |
| TokenTax |
Customisable exports; strong audit reports |
Excellent DeFi parsing; NFT support with tagging |
95% (complex DeFi sample) |
£150–£1,200 (higher for manual tagging) |
| CoinTracker |
SA108 export; clear lot reports |
Decent NFT handling; DeFi needs manual tags |
92% (mixed wallet test) |
Free–£300 (depending on tx count) |
Testing workflow (use with your sample wallet)
1
Prepare: pick 20–50 transactions covering trades, swaps, staking, airdrops and an NFT sale.
2
Import: load same CSVs and APIs into two or three vendors and then record errors.
3
Compare: check SA108 totals, lot matching and fee treatment.
4
Decide: pick the tool that cuts manual fixes and audit risk.
Independent accuracy testing must be reproducible and clear.
The next bullets explain the method and metrics in short lines.
- In our own comparative checks we imported an identical 500-transaction mixed wallet (spot trades, token swaps, staking rewards, an airdrop and one NFT sale) into each vendor using both API and CSV imports. Then we measured trade matching rate, lot-matching accuracy and variance in reported taxable gains.
- Trade matching rate equals matched disposals divided by total disposals.
- Lot-matching accuracy equals the share of disposals where the same acquisition lot was picked by both vendor and baseline.
- Taxable gains variance equals the absolute difference in total taxable gains reported.
For example, a 2.5% difference in lot-matching produced a £3,200 variance on a portfolio with £128k disposals.
Stating these metrics alongside vendor percentages gives a verifiable basis to judge crypto tax accuracy and HMRC risk.
Koinly: best for most UK taxpayers
Koinly suits most private investors with straightforward trades and multiple exchanges.
The software produces SA108 exports and supports Section 104 pooling that aligns with HMRC rules.
Koinly imports via API and CSV from major exchanges and wallets. The platform flags missing fields but some DeFi events need manual tagging in practice.
Support response time varies. Live chat and email exist, but complex DeFi queries can take days to resolve.
This delay matters when deadlines approach.
What are the pros?
Koinly provides clear SA108 exports and lot reports that map to HMRC lines.
The interface helps non-specialists find disposals and gains quickly.
The most frequent error at this point is assuming every fee was captured automatically. Koinly often asks users to allocate fees manually for cross-chain swaps.
What are the cons?
DeFi auto-parsing is limited for complex liquidity-pool interactions.
Users usually must tag staking or farming rewards by hand.
Some pricing tiers charge per wallet. This raises costs for users with many small wallets.
For whom is Koinly a fit?
Choose Koinly if most activity is spot trading across exchanges and the portfolio has occasional NFTs.
It keeps filing simple for up to mid-complexity users.
For whom is Koinly not a fit?
Avoid Koinly if the portfolio is heavy DeFi, has frequent smart-contract interactions or needs deep on-chain decomposition.
Test with a real wallet sample before trusting any export.
TokenTax: best for complex DeFi and audit support
TokenTax handles complex DeFi, on-chain interactions and NFT royalty flows better than many competitors.
It offers robust audit reports tailored for HMRC enquiries.
TokenTax accepts raw on-chain exports and performs manual tagging services for a fee when automation fails.
That service reduces error risk for high-complexity portfolios.
The trade-off is cost. For heavy DeFi users costs rise and manual service charges can be significant for 2024 portfolios.
What are the pros?
TokenTax parses many DeFi events and splits composite smart-contract transactions into taxable parts.
This reduces manual work and audit uncertainty.
A typical case: an investor with staking rewards and LP token swaps saw a £7,400 difference in reported gains between two vendors. TokenTax's decomposition resolved the gap.
What are the cons?
Higher price and occasional wait for manual review are real downsides.
The provider may charge extra for bespoke tagging and audit letters.
Some exchanges limit API histories, which leads to partial imports. TokenTax will request raw CSVs in those cases.
For whom is TokenTax a fit?
Choose TokenTax if the portfolio contains yield farming, complex swaps or NFT royalties and if audit readiness matters.
For whom is TokenTax not a fit?
Avoid TokenTax if the portfolio is small and mostly spot trades, where lower-cost tools give similar accuracy.
CoinTracker: balance of cost and usability
CoinTracker offers a middle ground with good usability and solid SA108 exports.
Its price model suits medium portfolios and accuracy is acceptable for many UK taxpayers.
CoinTracker needs manual tagging for many DeFi events and some NFT workflows. It gives clear lot reports to reconcile to HMRC lines.
Support is prompt for basic queries but slower for complex reconciling tasks that involve multiple wallets.
What are the pros?
CoinTracker is simple to use and provides helpful visual reports for disposals and gains.
It suits investors who want low friction and clear exports.
The majority of guides recommend CoinTracker for casual investors who want an easy filing path without top-tier costs.
What are the cons?
DeFi parsing is not automatic at the depth required for some smart-contract interactions.
Manual tagging remains common.
Import limits and exchange rate limits can cause missing historical trades unless CSVs are uploaded.
For whom is CoinTracker a fit?
Choose CoinTracker if the portfolio is mainly spot trading and the user wants a lower-cost, easy setup.
For whom is CoinTracker not a fit?
Avoid CoinTracker for high-frequency traders or extensive DeFi activity that needs full on-chain decomposition.
Test with a sample of typical transactions before deciding.
How to choose according to your situation
Choose by testing accuracy with a representative sample wallet and by modelling true costs for your transaction tier.
This gives a defensible choice and cuts audit risk.
Build three cost scenarios: casual investor (≤1,000 tx), active trader (1–10k tx) and DeFi/NFT heavy (>10k tx). Compare reported SA108 totals and support responsiveness in each scenario.
The most practical filter is matching the vendor's export format to the HMRC SA108 lines you will file. If the export maps cleanly, fewer manual edits follow.
The evidence points to one practical rule: if discrepancies exceed £1,000 in sample tests, do not file without reconciliation. That threshold raises audit risk.
The recommendation is clear: for simple portfolios pick lower cost tools, and for complex ones pick deep parsing and audit support.
Accuracy beats feature lists when HMRC attention is possible.
Many vendors state "high accuracy" while they omit how fees, pooling and internal transfers are treated. That creates hidden differences in final CGT.
Most guides ignore import limits and data retention policies. Rate limits and missing historical trades from exchanges cause silent gaps in reports.
A common omission is that exported CSV columns often do not match SA108 fields exactly. This forces manual transposition and creates transcription errors when filing.
Not suitable if the taxpayer has very few transactions or if a chartered accountant already manages the entire return using standardised CSVs. Also not relevant for taxpayers outside the United Kingdom.
For complex portfolios, consider asking a chartered accountant for a document review before filing. This cuts the chance of a costly HMRC enquiry.
Security and privacy deserve a focused, practical note for any crypto tax software used in the UK.
Vendors should disclose encryption in transit (TLS) and at rest (AES-256 or equivalent), key management practices, and whether they use third-party processors and their locations.
These points matter for GDPR and data residency.
Check retention policies for raw exchange APIs, CSVs and parsed histories. Also check deletion flows and whether backups are purged. Ask about role-based access for human reviewers who may do manual tagging.
For adviser or client use, audit-grade features such as immutable change logs, exportable audit trails and SOC2 or ISO 27001 attestations reduce tax audit risk.
Listing these elements helps UK taxpayers judge privacy trade-offs when choosing crypto tax software.
Frequently asked questions
Export the SA108 from the software and cross-check the totals to your exchange CSVs and blockchain tx hashes.
Use the software's lot report to match disposals to SA108 lines.
Always reconcile proceeds and cost basis for each disposal. Keep screenshots of exchange balances and the original CSVs for the audit trail.
Most tools separate capital gains and taxable income such as staking or mining. The user must tag reward events so the tool classifies them correctly.
Incorrect tagging is a frequent source of error. Confirm the software's income export maps to Self Assessment income lines when needed.
How long should records be kept for HMRC?
HMRC guidance requires records to be kept for at least six years for capital gains and related income.
Keep raw CSVs, exports and blockchain evidence for that period.
Keeping an organised folder with dated exports and notes makes any future enquiry easier to resolve.
Can HMRC get exchange data directly?
Yes. HMRC receives third-party data and can match it to a return.
Mismatches in proceeds or missing disposals increase the chance of enquiry.
Keep a complete audit trail and be ready to explain classification choices and lot-matching method.
What happens if the software misclassifies an event?
If classified wrongly, amend before filing and correct the classification to income or capital based on the facts.
Provide clear notes on reasoning in case HMRC asks.
Treatment depends on the event. In some scenarios the reward is taxable as income at receipt.
Is it safe to rely on free tiers for filing?
Free tiers can work for very small portfolios with simple spot trades.
For any DeFi, NFT, staking or over 1,000 transactions, free tiers often force manual edits that raise error risk.
Model the true cost by adding potential charges for extra wallets, manual tagging and audit support when comparing free versus paid plans.
How to handle differences between two vendors?
Identify which software treated fees, transfers or pooling differently.
Export lot-level data and reconcile cost basis per disposal until totals match within an acceptable margin.
If differences persist, escalate to vendor support and document the correspondence for the audit trail.
Example SA108 extract and CSV mapping
Below is a short example of how SA108 lines map to vendor exports. Copy this into your notes and replace values with your totals.
SA108. Capital Gains Summary (example)
SA108 3 (Total disposals): 45,120.00
SA108 4 (Total allowable costs): 12,340.00
SA108 5 (Gains or losses): 32,780.00
SA108 6 (Losses brought forward): 0.00
SA108 12 (Taxable gains): 32,780.00
Vendor CSV columns to check: date, transaction id, asset, type, amount, proceeds, cost_basis, fee
The legal deadline for Self Assessment payment and filing varies by return type and submission method. Always confirm current HMRC deadlines on the gov.uk guidance page. HM Revenue & Customs guidance on cryptoassets
Concrete worked examples help when you reconcile vendor exports to HMRC.
Below is a short, row-level illustration tying a vendor CSV line to SA108 values so readers can see how a disposal flows through.
CSV row sample: 2023-06-14, txid:0xabc123, asset:ETH, type:SELL, amount:1.25, proceeds:2,000.00, cost_basis:1,250.00, fee:10.00.
That disposal maps to SA108 as: proceeds £2,000.00 (SA108 3), allowable costs £1,260.00 (cost_basis + fee → SA108 4) and gain £740.00 (SA108 5).
For Section 104 pooling, show cumulative acquisition lots and pooled average cost at each disposal timestamp so users can inspect whether the vendor applied section 104 pooling correctly.
Providing a few fully worked CSV rows and their SA108 values lets taxpayers and advisers replicate and confirm CSV import accuracy and SA108 export fidelity.
