Are the records kept for Bitcoin transactions good enough if HMRC asks for evidence? For many taxpayers the worrying part is not the tax rate but proving when a disposal happened, what the cost basis was and why numbers match HMRC's expectations. This guide concentrates solely on Recordkeeping & Evidence for Bitcoin tax in England: what HMRC expects, how to store and reconstruct records, how blockchain evidence can be used, how to document disposals, gifts and airdrops, and how to prepare for an HMRC crypto tax audit.
Key takeaways: what to know in one minute
- HMRC expects dated, GBP‑valued records for every crypto transaction including date, action and value. No vague summaries.
- Keep originals and exports: wallet receipts, exchange statements and on‑chain hashes are primary evidence. Screenshots alone are weak.
- Reconstructing history is possible: use on‑chain explorers, CSV exports and third‑party tools to rebuild missing data. Document every assumption.
- Different events need different evidence: disposals, gifts, swaps, staking rewards and airdrops require tailored records. Note tax triggers.
- Be audit ready: compile a clear package, index files, and include a reconciliation worksheet showing cost basis and gains in GBP.
What records HMRC expects for crypto transactions
HMRC guidance on cryptoassets requires records that allow calculation of gains or losses and verification of income. Specifically, HMRC expects:
- Date and time of each transaction (UTC recommended).
- Type of transaction (dispose, acquire, transfer, swap, income, airdrop).
- Amount and type of cryptoasset (e.g. 0.75 BTC).
- Counterparty or platform (wallet address, exchange name).
- Value in GBP at the time of the transaction (exchange rate and source).
- Fees and costs directly attributable to the transaction.
- Purpose (sale, gift, exchange, staking reward).
Evidence should allow a third party to reconstruct the taxable event. The official HMRC policy is available at HMRC: Tax on cryptoassets.
Why exact timestamps and GBP conversions matter
Timing affects which tax year a gain falls into and which exchange rate should be used. For disposals, the cost basis requires converting the acquisition GBP value and the disposal GBP value using a reputable rate source. Record the source (for example, XE or an exchange's UTC tick) and keep a snapshot of the rate used.
Keeping records for capital gains on Bitcoin
Capital gains records for Bitcoin must show how the base cost was calculated, especially given pooling rules and the same‑day/30‑day rules that HMRC applies to cryptoassets.
What to record at acquisition
- Date and precise time.
- Acquisition amount in BTC and GBP.
- Fees or commissions in BTC or GBP.
- Source of funds (bank transfer, card) and any reference IDs.
- Wallet address or exchange account ID.
What to record at disposal
- Disposal date and time.
- Disposal proceeds in BTC and GBP.
- Fees paid for the disposal.
- Method of disposal (sale to fiat, swap for another crypto, payment for goods).
- Counterparty details if known (wallet address, exchange trade ID).
How to document cost basis and pooling
For Bitcoin held as part of a pool, maintain a running ledger that shows:
- Opening pool balance and GBP cost.
- Each acquisition added to the pool (date, BTC amount, GBP cost).
- Each disposal removed by the HMRC matching rules (same‑day, 30‑day, then pooled).
A reconciliation worksheet should show calculations step‑by‑step so an auditor can follow how the taxable gain was reached.
Storing wallet receipts and exchange statements securely
Physical or raw screenshots are useful but fragile. Evidence strength increases when records are exportable, timestamped, verifiable and stored redundantly.
Recommended storage strategy
- Primary archive: encrypted cloud storage (e.g. provider with UK/EU data controls) for CSVs and PDF statements.
- Secondary archive: offline encrypted backup (hardware encrypted drive) stored separately.
- Change log: a short plain‑text index describing each file and the hashing checksum used (SHA‑256).
Include an audit index.csv that lists each stored file, its hash, date captured and a brief description.
File types to keep
- Exchange CSV exports (trades, deposits, withdrawals, fees).
- Bank statements that show fiat transfers to/from exchanges.
- Wallet export files (addresses, transaction IDs).
- Official PDF statements when provided by services.
- Screenshots only where no export exists—but pair with explorer URLs for verification.
Security and privacy considerations
- Encrypt archives using well‑supported algorithms (e.g. AES‑256).
- Limit metadata exposure: do not store private keys alongside evidence.
- Follow guidance from the NCSC and the ICO for data protection and secure storage.
Using blockchain evidence to support tax calculations
On‑chain evidence is powerful when combined with off‑chain statements. Transaction hashes (txids) provide immutable proof of a transfer and, when linked to a timestamp, can confirm dates and amounts.
What to capture from the blockchain
- Transaction hash/ID.
- Block timestamp (UTC) and block height.
- From/to addresses involved.
- Amount moved and any miner fee displayed.
- Explorer URL snapshot (e.g. Blockchain.com, mempool.space).
How to use on‑chain data for GBP valuation
- Use the block timestamp to choose an exchange rate at that moment.
- Record the source of the rate and a snapshot URL or exported CSV showing the rate.
- Include calculation cells in the reconciliation worksheet showing conversion steps.
Handling non‑standard events (DeFi, layer‑2, mixers)
- For layer‑2 and DeFi transactions, capture both the asset movement and the bridging transaction to/from mainnet.
- When mixers are involved, document why funds are believed to be the taxpayer's (wallet histories) and record any uncertainties as assumptions.
On‑chain evidence workflow
🔎 Step 1
Capture the txid and block timestamp →
📥 Step 2
Export exchange rate or use a reputable price source at that timestamp →
🧾 Step 3
Record GBP conversion and store CSV/PDF evidence →
✅ Result
Auditable line item linking on‑chain txid to GBP value and fees.
Documenting disposals, gifts and airdrops for HMRC
Different events require different depth of evidence. The record set should reflect the event type.
Disposals (sales, swaps, payments)
- Proof of transfer to exchange or buyer (txid or trade ID).
- Exchange trade record showing proceeds and fees.
- Bank receipt showing fiat received, if applicable.
- Calculation of gain/loss using the HMRC matching rules, with references to each matched acquisition.
Gifts and transfers between personal wallets
- Reason for transfer (gift to named individual, moving between personal wallets).
- Evidence of recipient (wallet address, declaration if given to another person).
- If gift to spouse/partner qualifies for reliefs, retain documents that show relationship and date.
Airdrops and staking rewards
- Evidence of the event (project announcement, token distribution txids).
- Fair market value in GBP at the time of receipt and the source.
- If tokens are later disposed of, the acquisition value for CGT purposes is the GBP value recorded when received—keep the snapshot.
Practical examples and a worked example
Worked example: sale of 0.5 BTC acquired in three lots
- Acquisition 1: 0.3 BTC on 2020‑01‑15 for £2,400 (fees £10).
- Acquisition 2: 0.2 BTC on 2021‑07‑10 for £6,000 (fees £20).
- Disposal: 0.5 BTC sold on 2024‑09‑20 for £15,000 (fees £50).
Reconciliation sheet should show how same‑day and 30‑day rules apply, any pooling applied and how £15,000 less allowable costs produces the taxable gain. Include formula cells and links to the CSVs and txids that prove dates and GBP values.
Reconstructing history when an exchange disappears
- Export whatever is available: bank receipts for fiat transfers, emails, and screenshots.
- Use blockchain txids to show transfers to/from the exchange wallet.
- Use archived exchange URLs (Wayback Machine) or third‑party records.
- Document every assumption and include a final reconciliation that flags unverifiable items.
| Source |
Evidence strength |
Notes |
| Exchange CSV / Trade export |
High |
Includes trade IDs, fees; preferred evidence |
| Blockchain txids + block timestamp |
High (immutable) |
Must be paired with GBP rate evidence |
| Bank statements |
High for fiat flows |
Show money in/out; essential for conversions |
| Screenshots / email confirmations |
Medium |
Use only when exports unavailable; capture txid and URL |
Advantages, risks and common errors
✅ Benefits / when to apply
- Strong evidence reduces audit friction.
- Structured records speed up self‑assessment filings.
- On‑chain proof provides immutable timestamps for disputes.
⚠️ Errors to avoid / risks
- Relying solely on screenshots without txids or CSVs.
- Not recording GBP values or rate sources.
- Mixing personal and business wallets without clear documentation.
- Failing to encrypt or back up records; losing proof when an exchange disappears.
Preparing records for an HMRC crypto tax audit
An audit package should be concise, indexed and defensible.
Contents of a compact audit pack
- Reconciliation workbook (CSV or spreadsheet) showing each disposal, acquisition, GBP conversion, fees and gain/loss calculations.
- Index file linking each line in the workbook to raw evidence (CSV, txid, bank statement).
- Copies of exchange exports and bank statements.
- On‑chain evidence list with txids and explorer links.
- A short narrative explaining reconstruction steps and any assumptions.
Practical tips for interacting with HMRC
- Respond within deadlines and attach the compact audit pack.
- Where calculations are complex, provide the spreadsheet with formula cells visible.
- Record all communications and file them with the audit pack.
For procedural queries, consult HMRC guidance: HMRC.
Frequently accepted evidence and its limitations
- Exchange CSVs: accepted but may be questioned if missing KYC ties.
- Bank receipts: essential for fiat flows; strongly persuasive.
- On‑chain txids: immutable timestamps but require GBP rate evidence.
- Email announcements (airdrops): support existence but need valuation snapshot.
Checklist before filing a self‑assessment
- Ensure every disposal has an associated acquisition recorded or pooled.
- Create a single reconciliation spreadsheet with live links to evidence.
- Encrypt and back up the archive; retain for at least five years and 22 months as HMRC guidance suggests for providers and taxpayers.
- Accounting aggregators (CSV importers): automate much of the heavy lifting but costs vary.
- Blockchain explorers: free and definitive for timestamps.
- Manual spreadsheets: flexible and transparent for auditors.
Questions users often ask
How long must records be kept?
HMRC expects records to be kept for the periods that support the tax position; typically at least five years after the 31 January tax return deadline, with variations depending on circumstances. See HMRC guidance on record keeping.
Can screenshots be used as evidence?
Yes, but only as a last resort. Screenshots should be accompanied by txids, CSV exports or explorer links; otherwise they are weak when challenged.
What if exchange rate sources disagree?
Record the chosen source and show the conversion calculation. If rates vary slightly, documenting the methodology reduces dispute likelihood.
Are DeFi rewards taxable and how to record them?
DeFi rewards are typically taxable as income on receipt and must be recorded with a GBP valuation at the time received. Keep event announcements, txids and rate sources.
What happens if a service deletes my history?
Reconstruct using bank statements, blockchain txids and cached exports. Document every assumption in the reconciliation workbook.
Preguntas frecuentes
What records should I keep for crypto transactions?
Keep dated transaction records, txids, exchange CSVs, wallet exports, fees, and GBP valuations with rate source. These items let HMRC verify gains.
How should Bitcoin gains be calculated and evidenced?
Calculate gains using HMRC matching rules, keep a running pool record, and attach supporting CSVs and on‑chain links for each disposal line.
Use CSV for tables, PDF for statements, and SHA‑256 hashed archives stored encrypted (AES‑256). Keep an index with hashes.
How to prove airdrop or staking income to HMRC?
Provide project announcement links, distribution txids, and a GBP valuation snapshot at the time of receipt.
What to include in an audit pack for HMRC?
A reconciliation workbook, linked raw evidence, bank statements, on‑chain txids and a short explanation of reconstruction steps.
Next steps
- Export all exchange trades and bank statements, then create a single reconciliation workbook linking each line to raw evidence.
- Encrypt and back up two copies of the archive (cloud + offline) and generate a file index with checksums.
- If gaps exist, reconstruct using txids and public explorers, document every assumption and note rate sources used.
Legal notice: This content is general information and not personalised tax advice. For decisions affecting tax positions consult a regulated adviser or HMRC. See FCA and HMRC.
