Worried an HMRC audit will turn a year of trades into a months-long scramble for receipts? Small UK traders filing via Self Assessment or as sole traders often lack time or tax knowledge and struggle to compile audit‑proof records. A practical bookkeeping tool can stop the panic by producing exportable proofs and reconciled transaction histories that reduce queries and keep costs clear.
Traders facing HMRC audits should choose a bookkeeping tool that exports auditable, transaction-level reports. The tool must reconcile wallets and exchanges and support DeFi and NFT adjustments. Koinly, CoinTracking and Recap cover most needs. Pay for a tier that unlocks raw CSV exports, hash and timestamp proofs and continuous reconciliation. These features minimise HMRC queries. Read on for HMRC-ready CSV templates, a step-by-step checklist and short case studies that show how to prepare evidence quickly.
Tools must export raw transaction history with txids and timestamps for HMRC.
The most important feature is a reproducible, transaction-level record.
Summaries or screenshots usually fail an HMRC enquiry.
What HMRC actually looks for
HM Revenue & Customs asks for transaction timestamp, transaction identifier (txid), counterparty or wallet address, fiat value at the time and fees.
The legal frameworks involved include Capital Gains Tax and Income Tax rules applied via Self Assessment.
Making Tax Digital for VAT began in April 2019 and applies to businesses that meet VAT registration thresholds under standard VAT rules. This includes businesses supplying crypto-related services if they are VAT-registered. MTD does not automatically apply to private capital gains. It also does not apply to sole traders who are not VAT-registered. Clarify VAT registration status first before treating MTD obligations as applicable.
Audit-ready features to prioritise
Raw CSV or JSON export with txid and timestamp is essential.
Proof hashes or blockchain-anchored timestamps give cryptographic immutability; a generic PDF export is useful as a readable record but is not tamper-proof by itself. Where possible, produce a SHA-256 checksum for each export file and store the checksum in the index spreadsheet. For greater assurance, anchor a timestamped hash to a third-party timestamping service or the blockchain. This makes the audit pack contain verifiable, reproducible proofs.
Reconciliation logs that show how each trade maps to ledger entries save time in an enquiry.
Why HMRC asks for transaction-level proof
HMRC requires verifiable records so gains and income can be checked against returns.
On-chain events and exchange records let HMRC reproduce valuations and detect omissions.
Providing complete evidence reduces the chance of a formal assessment.
HMRC guidance and sources
Refer to the HMRC Cryptoassets Manual on GOV.UK for detailed expectations.
HMRC guidance stresses transaction-level data and cost basis disclosure.
The evidence HMRC requests includes original exchange exports and bank receipts.
Common triggers for HMRC enquiries
Large unexplained deposits or frequent crypto-to-crypto trades often trigger checks.
Third-party data matches and AML flags also prompt enquiries.
The most frequent error at this point is relying on exchange summaries instead of raw exports.
Preparing an HMRC-ready audit pack
Follow the checklist below to assemble an audit pack within 48-72 hours.
Start by exporting raw files from every exchange and wallet used.
Then build a signed index and a changelog to document who did what and when.
Keep a clear folder and naming system so files are easy to find.
Exporting the right files
Export raw CSV or JSON from each exchange and wallet, including API dumps where available.
Download on-chain proofs or record block explorer links with txid and block timestamp for each on-chain event.
Export the crypto tax tool's reconciliation report and save it as PDF and CSV.
Organising files and signing off
Create a folder structure: Exchanges, Wallets, Tax Reports, Bank Statements, Contracts and Reconciliations.
Produce an index spreadsheet listing file name, source, export date, preparer and checksum.
The taxpayer or preparer should sign a short statement confirming methods used and the accuracy of exported files.
Example index CSV template
csv
File name,Source,Export date,Prepared by,Checksum/SHA256,Notes
binance_trades_2023.csv,Binance,2024-03-12,Preparer Name,abc123...,Contains all trade rows with txid
wallet_dump_ethereum.json,MetaMask,2024-03-12,Preparer Name,def456...,Includes staking rewards
koinly_recon_2023.csv,Koinly,2024-03-12,Preparer Name,ghi789...,Reconciliation mapping to ledgers
A practical HMRC-ready transaction CSV should use consistent, explicit columns so an auditor can reproduce valuations and trace every disposal. A recommended header set for disposals is: Date (UTC), Time (UTC), Asset, Amount, Counterparty/Exchange, Wallet/Address, Transaction type (buy/sell/swap/stake/airdrop), TxID, Block number, Fiat value at disposal (GBP), Fiat exchange rate source, Fees (asset + GBP), Cost basis method (FIFO/HIFO), Acquisition date(s) and Notes.
Example row: 2024-03-12, 14:12:23, BTC, 0.15000000, Binance, 1A2b…, sell, 0xabc123..., 17123456, 3,456.78, CoinGecko@2024-03-12T14:12, 12.34, FIFO, linked bank payment and withdrawal.csv.
Save as filenames like binance_disposals_2024-03.csv and include a companion recon file (koinly_recon_2024.csv) that maps each disposal row to ledger entries and the SHA-256 checksum of the source export. These concrete CSV layouts make CSV export for HMRC requests and audit-ready crypto reports straightforward to deliver.
Choose tools by audit features not only by price or user interface.
Paid tiers often unlock proof exports and deeper API access.
Free plans frequently block the files needed in an audit.
Critical feature checklist
Raw CSV or JSON export with txid and timestamp.
Proof receipts or timestamped PDFs for reports.
Reconciliation logs and the ability to attach source files to transactions.
HTML comparison table
| Tool |
Raw export |
Proof hash |
Reconciliation log |
DeFi/NFT support |
Accounting integrations |
| Koinly |
Yes (CSV/JSON) |
PDF receipts (paid) |
Yes |
Good |
Xero, QuickBooks, FreeAgent |
| CoinLedger (CoinLedger.io) |
Yes (CSV) |
Timestamped export (paid) |
Yes |
Good |
Xero |
| CoinTracking |
Extensive exports |
Limited |
Yes |
Moderate |
CSV export to accounting |
| Accointing |
Yes |
Paid receipts |
Yes |
Good |
Xero, QuickBooks |
Typical paid plans cost between a360 and a3300 per year depending on trade volume and DeFi support.
If more than 200 trades per year occur, a paid tier usually pays for itself by saving accountant time and providing audit proofs.
Not all audit-oriented features are equally necessary for every small trader. Free tiers can be acceptable for low-volume, fiat-only disposals where bank statements link directly to exchange withdrawals. On-chain activity, staking rewards reporting or NFT sales need stronger proofs.
The critical audit functions are: transaction-level export with txid and timestamp, an attached source file or exchange export for each transaction, a verifiable checksum or hash for each export file (SHA-256) and on-chain proof links like block explorer URLs and block numbers.
For DeFi or NFTs expect to supply contract addresses, pool snapshots and reward histories.
A practical decision rule is: if you have more than 200 trades, multiple wallets or DeFi and NFT activity, pay for a plan that gives continuous reconciliation, deep API access and timestamped proof exports. For simple traders, a basic paid plan that unlocks CSV export plus manual SHA-256 checksums may be sufficient for robust crypto tax accounting and HMRC crypto audits.
MTD and sole trader reporting with crypto
Sole traders should keep a parallel ledger in an accounting package for Self Assessment reconciliation.
Accounting platforms help produce MTD-style summaries and file VAT where needed.
Linking the crypto tool to Xero or FreeAgent makes the Self Assessment workflow smoother.
Making tax digital notes
MTD for VAT started in April 2019 and affects businesses that must report VAT digitally.
MTD for Income has had pilots and wider rollout discussions as of 2026.
Sole traders must still keep accurate records for Self Assessment even if MTD does not yet apply.
Self assessment steps for crypto traders
Export the tax tool report showing disposals and gains as a CSV.
Reconcile that CSV into the accounting ledger or attach it to the return as supporting evidence.
Prepare a summary schedule for HMRC showing total disposals, allowable costs and net gains.
For sole traders, integrate Making Tax Digital and Self Assessment by treating crypto bookkeeping as a source ledger feeding your accounting package. Export exchange transaction files and on-chain JSON or CSV weekly. Import them into your accounting app as a staging ledger line per disposal. Tag each row with ‘CGT disposal’ or ‘Income - staking’ and run a crypto reconciliation weekly so your codes reflect disposals, fees and realised gains.
If VAT registration is required, use the accounting package's MTD VAT submission flow with a labelled VAT control account. Otherwise continue to produce a Self Assessment crypto schedule annually showing total disposals, allowable costs and net gains.
This consistent flow, regular crypto bookkeeping, documented reconciliations and clear exportable Self Assessment summaries reduce friction when HMRC requests a self assessment crypto breakdown.
DeFi, staking and NFT audit rules
DeFi, staking and NFTs often need extra provenance and manual notes.
Automated calculations can misclassify these events as simple trades.
Annotate each DeFi interaction with contract address and the reason for classification.
Evidence for on-chain events
Record txid, block timestamp, contract address and a link to a block explorer for each event.
Save pool share snapshots, staking reward records and any smart contract logs used for valuation.
If the tax tool cannot attach proofs, export raw JSON and create a manual annotation CSV.
Classification advice
Treat staking and mining as likely Income Tax unless material evidence shows different treatment.
Treat disposals of NFTs as capital events for CGT unless held as trading stock.
This works in theory but, in practice, automated rules often miss provenance and need manual correction.
Costs, trade-offs and when to pay for software
Paid software is worth it when audit risk or tax exposure exceeds the cost of the plan.
Free tools may save money short term but increase risk and accountant fees later.
Set a simple rule: if exposures exceed a31,000 to a32,000, budget for a paid plan.
When paid tiers are justified
More than 200 trades per year, multiple wallets, DeFi or NFT activity usually require paid plans.
Paid plans unlock proof exports, API depth and accountant reports.
A paid accountant plan can cost more but gives direct accountant access and audit support.
Budget bands
Low activity: free or basic plan under a360 per year.
Moderate activity: a360 to a3150 per year buys raw exports and basic proofs.
High complexity: a3150 to a3300 per year or an accountant plan for full audit resilience.
Audit-ready templates and brief case studies
Use the templates below to create an HMRC Audit Pack without waiting for requests.
Two short case studies show how audit features change outcomes.
Each case highlights a single lesson small traders can apply immediately.
Audit pack file checklist
-
Raw exchange CSV or JSON exports from each platform.
-
On-chain proof list with txid and block explorer links.
-
Crypto tax tool reconciliation CSV and PDF receipt.
-
Bank statements linking fiat movements to disposals.
-
Signed index and changelog CSV.
Signed statement template
text
I confirm that the attached records are complete and accurate to the best of my knowledge.
Taxpayer name: [Full name]
UTR: [Unique Taxpayer Reference]
Date: [YYYY-MM-DD]
Method for cost basis: [FIFO/HIFO/LIFO]
Prepared by: [Name or 'Self']
Signature: [Digital or typed name]
Short case studies
Case 1: Small sole trader, 350 trades across three exchanges.
A paid tool produced raw exports and reconciliation logs and the enquiry closed with no adjustments.
Case 2: DeFi heavy trader, staking and LPs.
An automated report misclassified rewards; manual contract proofs and notes reduced HMRC's proposed adjustments by most of the amount originally proposed.
Case 3: Low volume trader using free tier.
Relying on screenshots led to expensive reconstitution by an accountant. The cost exceeded one year of paid software.
This advice does not apply if no crypto trades occurred, if a professional accountant already maintains audited records end-to-end, if bespoke institutional accounting systems are in place, or if tax obligations lie outside the United Kingdom.
If urgent audit support is needed, prepare the HMRC Audit Pack using the templates above and share it with a tax advisor for a rapid review.
Frequently asked questions
Pick a tool that exports raw transaction CSVs, timestamps and reconciliation logs.
Koinly and CoinLedger are widely used in the UK. CoinTracking and Accointing are alternatives for deep raw exports.
Selection depends on trade volume and DeFi or NFT needs.
How should crypto trades be recorded for tax?
Record date, txid, exchange or wallet, counterparty or address, asset, amount, fees, fiat value and cost basis.
Export raw files and reconcile them with bank statements and ledger entries.
Can screenshots be used as evidence?
Screenshots are weak evidence compared with raw CSVs, JSON exports and timestamped receipts.
HMRC often requests native exports and reconciliation logs in an enquiry.
Do I need a paid plan for an audit?
A paid plan is usually necessary if the audit requires proofs, API exports or large raw datasets.
Free tiers commonly block these features and force manual reconstitution.
How to handle DeFi and staking records?
Record txid, block timestamp, contract address and an explanatory note for each DeFi interaction.
Attach pool snapshots, reward histories and any smart contract evidence used for valuations.
Your next step
Create the HMRC Audit Pack folder now: export raw CSVs, produce the index CSV and sign the statement.
Consult HMRC guidance on GOV.UK if detailed rules are needed.
HMRC Cryptoassets Manual
Koinly official site
Will HMRC know if I sell crypto?
HMRC can obtain data from exchanges and perform on-chain analysis to match activity.
Undeclared disposals can surface through third-party reporting and bank reconciliations.
Keep complete records to reduce risk.
