HMRC can reject Bitcoin records that look tidy on the surface but do not actually prove what happened. If you are trying to file a Self Assessment, answer an HMRC letter, or rebuild a messy crypto history, missing links between wallets, unclear GBP values, or mixed-up transfers can turn a “complete” spreadsheet into weak evidence.
For HMRC, the safest approach is to keep a full audit trail for every Bitcoin transaction: date and time, asset, amount, GBP value, wallet addresses, exchange statements, fees, and the purpose of each transfer. You should be able to prove your cost basis, any disposal, and whether a movement was internal. Keep records organised by transaction type and retain them for at least the HMRC requirement period.
What HMRC expects you to keep
Keep the record set complete enough to show what happened, when it happened, and why it matters for tax. HMRC does not need a narrative; it needs evidence that supports the numbers in your return.
A complete file should let you trace each Bitcoin unit from acquisition to disposal, or show clearly that a movement was internal and not taxable.
Exact records HMRC can ask for
Keep the date and time, asset, quantity, GBP value, fees, and the exchange or wallet used. Keep the transaction hash or tx ID for on-chain movements.
Keep the contract note, trade confirmation, CSV export, or statement where the trade happened. For custody transfers, keep both the sending and receiving wallet addresses.
A closing balance tells HMRC what you held at the end of the period. It does not show acquisition cost, disposal proceeds, or the reason for a wallet movement.
That matters because Capital Gains Tax records depend on transaction history, not just holdings. A balance screenshot cannot support pooling rules, allowable costs, or fee treatment.
A taxable disposal can happen when you sell Bitcoin for GBP, swap it for another cryptoasset, or spend it on goods or services. Moving coins between wallets you control is usually not a disposal, but it still needs proof.
Evidence of control means you can show both wallets were yours at the same time. That usually means address records, exchange withdrawal history, and a clear link to the same person or entity.
As Alan White, with over 12 years of experience guiding individuals and businesses through cryptocurrency taxation in the UK, this author provides practical, real-world advice on managing crypto taxes confidently, I have seen cases where clients kept only final balances and no trade history, and HMRC then had no way to accept the figures without a rebuild.
Build a bitcoin record-keeping system
Set up one master log first, then attach source files to each line.
Your goal is not just storage. Your goal is a chain of proof that can be followed from source to return.
Minimum fields for every transaction
Use the same fields for every event so your records stay consistent. The minimum set is small, but each field matters when HMRC asks for proof.
| Field |
What to record |
Why HMRC needs it |
| Date and time |
Exact timestamp in UK time or clear exchange time |
Fixes the tax point and GBP value timing |
| Transaction type |
Buy, sell, swap, spend, transfer, fee, reward |
Separates disposal from internal movement |
| Asset and quantity |
BTC amount and any paired asset |
Supports pooling and cost basis |
| GBP value |
Sterling value at the event time |
Used for gain or income calculations |
| Fees |
Exchange fee, network fee, gas fee |
May affect allowable costs |
| Source and destination |
Wallet address, exchange name, account label |
Shows ownership and movement path |
| Transaction hash |
Tx ID for on-chain transfers |
Proves the transfer happened |
| Purpose |
Trade, storage, payment, rebalance, reward |
Shows whether the event was taxable |
The fastest way is to use one spreadsheet tab for transactions and one for source documents.
Use this exact line structure for each row in your own file.
| Date |
Type |
Asset |
Quantity |
GBP value |
Fees |
From |
To |
Tx ID |
Purpose |
| 2026-01-14 13:22 |
Buy |
BTC |
0.25 |
£9,850 |
£24 |
Bank / Exchange |
Wallet A |
Exchange ref |
Initial purchase |
| 2026-02-03 09:10 |
Transfer |
BTC |
0.10 |
£0 |
£1.80 |
Wallet A |
Wallet B |
0x... |
Internal storage move |
Use one row per event, not one row per day. If you batch records, you will lose the link between the transaction and the price used.
Keep exchange exports in one folder and wallet records in another. Then create one reconciliation sheet that links both.
As Alan White, with over 12 years of experience guiding individuals and businesses through cryptocurrency taxation in the UK, this author provides practical, real-world advice on managing crypto taxes confidently, I have seen cases where the exchange data was perfect but the wallet side was missing, and that left the client unable to prove which transfers were internal.
Use the transaction hash as the anchor for any on-chain movement. It is the cleanest proof that a transfer happened and that it happened at a specific moment.
HMRC wants evidence that can be traced, not just evidence that looks complete.
Record each trade and transfer correctly
Treat each type of transaction differently.
Record a purchase as cost basis proof
A purchase needs the date, BTC quantity, sterling amount, and fee. It also needs the exchange statement and bank transfer if cash came from your account.
This is your cost basis evidence. Without it, later gains can be overstated because you cannot show what the coins cost you.
Record a sale as disposal proof
A sale needs the sale time, quantity sold, GBP value received, and fee paid. Keep the disposal confirmation and the receiving bank statement if cash was withdrawn.
This is disposal proof. It is the record HMRC will look at when checking whether the gain reported matches the transaction.
Record a swap or spend as a taxable event
A swap between cryptoassets is usually a disposal of the asset given up. Spending Bitcoin at a merchant can also trigger a disposal, because you have exchanged it for goods or services.
Keep the merchant receipt or exchange ticket, the GBP value at the time, and the wallet address used. If the merchant invoices in pounds, store that sterling amount as well.
Record an internal transfer as non-disposal proof
An internal transfer needs both wallet addresses, the tx hash, the time, and a note that the wallets belong to the same beneficial owner. Keep the exchange withdrawal record too if the move started on-platform.
Record fees where they actually arise
Record exchange fees, maker-taker fees, withdrawal fees, and gas fees on the same line as the transaction they belong to. If you split them out later, your totals will drift.
Record rewards, staking and airdrops separately
Staking rewards, airdrops, and similar receipts often need both income-style records and later disposal records. Keep the date received, amount, GBP value, and source wallet or platform.
For HMRC, the same asset can create two records: one when acquired or received, and one when disposed of later.
A practical Bitcoin record keeping system works best when you log each scenario in a slightly different way. A purchase should show the source of funds, the trade confirmation, the GBP valuation at execution, and the opening cost basis for the pool. A sale should show the disposal proceeds, exchange statements, the bank credit if fiat was withdrawn, and the exact transaction hash where the coins left your control. A swap needs both sides of the transaction because HMRC will usually see it as a disposal of the asset given up and an acquisition of the new coin. A transfer between your own wallets needs internal transfer proof such as matching wallet addresses, tx ID, and exchange withdrawal records.
Spending Bitcoin in a shop needs the merchant receipt and the sterling value at the point of payment so you can evidence the capital gains tax calculation. In each case, the goal is not just to store data, but to preserve a clean HMRC audit trail from source to return.
It also helps to separate three different proof categories in your crypto record keeping. Cost basis proof is the evidence that shows what the Bitcoin originally cost you, such as buy confirmations, bank payments, exchange statements and fees, because that figure feeds into the gain calculation. Disposal proof shows that you actually disposed of the asset and what you received in return, so it should capture the disposal proceeds, date, time, GBP valuation and the receiving account or merchant. Internal transfer proof is different again: it does not create a taxable event, but it shows that coins moved between wallets you control, which is why the tx ID, wallet addresses and platform withdrawal history matter so much.
If those three categories are kept separate in the same spreadsheet or folder structure, it becomes much easier to answer Self Assessment questions and explain why a movement was not a sale.
Keep records for the right period
Keep crypto records for at least the HMRC retention period that applies to your filing position.
Keep exchange exports, CSV files, wallet screenshots, contract notes, and receipts together. If a platform lets you export multiple years, save the export immediately.
Start with the tax year in question and sort transactions by type. Then attach the source document to each line and check that the GBP value is present for every disposal.
The Chartered Institute of Taxation and ICAEW both emphasise good source records for tax support, and HMRC’s own Cryptoassets Manual is built around traceability rather than guesses.
This checklist is not enough if you only hold Bitcoin and never bought, sold, swapped, spent, or moved it.
HMRC record keeping is not just about saving everything indefinitely; it is about keeping the right evidence for long enough. In practice, many crypto taxpayers keep their Bitcoin transaction history, exchange statements, wallet addresses, transaction hash records and GBP valuation support for at least five years after the 31 January filing deadline for the relevant tax year, and longer where they are in a more complex position or expect an HMRC review. For example, if you filed a 2024/25 Self Assessment return by 31 January 2026, the safest approach is to keep the underlying crypto tax records until at least 31 January 2031.
That period should cover cost basis evidence, disposal proceeds, and any internal transfer proof that links one wallet to another. If a later enquiry asks why a gain was calculated in a certain way, the original trade confirmation and chain data are far more persuasive than a summary spreadsheet alone.
Your questions answered about bitcoin tax UK
Do you have to declare bitcoin to HMRC?
Yes, if you have disposals, taxable income events, or reportable gains, you need records that support the figures on your return.
How to record bitcoin on taxes?
Record each transaction with date, type, quantity, GBP value, fee, wallet or exchange, and tx ID.
Can HMRC access hidden bitcoin?
HMRC cannot read a private key from nowhere, but it can ask for records, exchange data, and bank trails.
How to sell bitcoin without paying tax in the UK?
You cannot assume a sale is tax-free just because the proceeds are small.
Bitcoin records matter most when you have already traded, swapped, spent, or moved coins. If you have not done any of those, your file may be very small, but it should still be complete where relevant.
What if i only have exchange screenshots?
Screenshots help, but they are not enough on their own if they do not show the full trail.
What if i used five different wallets?
Use one master log that shows every movement between wallets and the reason for each transfer.
What if my exchange closed or deleted history?
Rebuild the history from emails, bank statements, chain data, and any downloaded exports you still hold.
What if i have staking or airdrop records too?
Keep them in a separate section, but use the same fields for date, amount, GBP value, source, and later sale.
Close your file before HMRC asks
A good Bitcoin file is not a pile of statements. It is a clean trail that shows acquisition, disposal, transfer, and fee treatment in one place.
If you build it now, you can answer Self Assessment questions faster and with less risk of missing a key event. If you wait until a letter arrives, the rebuild is usually slower and less complete.
The practical standard is simple: one event, one line, one source trail. Keep that rule, and your records will do the work when HMRC wants proof.
