What HMRC Will Receive From Crypto Platforms for 2026

Updated 17 October 2026

General information only, not tax advice. We are not HMRC and are not affiliated with it. Check GOV.UK and your platform. Last checked against GOV.UK: 17 October 2026. Anything marked expected should be re-checked; we plan to re-check the CARF pages on 1 December 2026. Examples use made-up figures or GOV.UK's own examples. Do not enter personal identifiers (National Insurance number, UTR, name, date of birth) on this site.

This page contains no affiliate links.

Short answer: GOV.UK says providers must collect details of all users but only need to report users who are tax resident in the UK or another country signed up to CARF. They report these users' details and a summary of their transactions; if there's nothing to report in a year they don't submit a report. The report is an XML file submitted through an online service that isn't live yet.

What providers collect and report (GOV.UK, read 17 October 2026)

• Individual users, collected: name, date of birth, home address, country of residence; for UK residents a National Insurance number or UTR; for non-UK residents a TIN and issuing country (no TIN needed if none can be issued).
• Reported to HMRC (IEIM8000515): name, address, jurisdiction(s) of tax residence, TIN(s) and date of birth, plus transaction information per cryptoasset: the full name of the asset and details of the transactions. Fungible units of one asset are aggregated by type; NFTs are separate types.
• Collected for each transaction: value, type of cryptoasset, type of transaction and number of units.
• Buy or sell for fiat (IEIM8000530): the platform reports the total paid or received for each type of cryptoasset, after taking out fees. Where amounts are in several fiat currencies, one currency is used, converted at the time of each transaction and applied consistently. If the platform only sees one side and doesn't know the fiat value, it reports a transfer instead.
• Crypto-for-crypto (IEIM8000540): both sides are reported, the disposal and the acquisition, at fair market value at the time of the trade, after fees, in one fiat currency; if one asset is hard to value, the value of the other is used to estimate.
• Wrapping and liquid staking (IEIM8000555): for CARF these are exchange transactions, because one relevant cryptoasset is swapped for another. This is a reporting rule only; it does not tell us how HMRC treats them for CGT.
• Transfers (IEIM8000590): fair market value at the time, in one fiat currency, using a reasonable consistent method: first the platform's own trading data, then internal accounting book values, then third-party price aggregators, then its most recent internal valuation, and as a last resort a reasonable estimate; if one of the alternative methods is used, the platform must say so in the XML report.
• Reports are XML files for each calendar year; the first covers 1 January to 31 May 2027 for 2026 (see key dates).

What GOV.UK does not say

• Other transaction types in the IEIM8000500 index (retail payments, collateral, transfers to external wallets; IEIM8000560 to 8000585 were not read).
• Whether the platform provides cost, pooled cost or gain figures. HMRC's page on selling cryptoassets says exchange reports are not tax calculations and will not keep track of your pooled costs, so you must keep your own records.

How HMRC may use it

HMRC says it uses the information to link your cryptoasset activity to your tax record. If you live in the UK but use a non-UK provider in a CARF country, that country's tax authority will share your information with HMRC (GOV.UK).

What you can do

Keep your own records (reconcile); check whether you must report gains (CGT page). HMRC's Cryptoasset Disclosure Service exists for unpaid tax from earlier years (GOV.UK).

FAQ

Will HMRC see my wallet? The pages read say providers report; nothing about self-custody wallets.

Is a penalty automatic? GOV.UK says "may charge" penalties for providers; and up to 100% of tax due plus interest where unpaid tax is found.

What we could not verify

The CARF Readiness Checker runs in your browser. It does not store what you enter and it does not ask for personal identifiers.