The fragmented portfolio problem
UK investors are no longer dealing with a single bank account and one annual statement. Today, a typical portfolio can be split across several platforms: stocks on Interactive Brokers, copy-trading activity on eToro, casual investing on Revolut, and a mix of cold storage, exchange accounts and onchain crypto activity.
Each platform provides its own data. None of them sees the full tax picture.
The data trap
This matters because UK tax reporting is becoming more data-driven. Traditional finance has already moved in this direction through broker statements, financial account reporting and cross-border information exchange. With the Crypto-Asset Reporting Framework, known as CARF, crypto is moving into the same logic.
From the 2026 reporting period, in-scope cryptoasset service providers must collect user and transaction data that will be reported to HMRC.
But here is the catch: automatic reporting to HMRC does not mean automatic tax calculation for you.
HMRC may receive more platform data, but it will not reconstruct your full portfolio for you. It may see a crypto withdrawal, but it may not know whether that movement was a taxable disposal, a transfer to your own hardware wallet, a bridge, or a payment. It may receive broker or platform data, but that data may not reflect your full acquisition history, your transfers across accounts, or the correct UK tax-year treatment.
Why clean records matter more in 2026
Whether you use IBKR, eToro, Revolut, Coinbase, Kraken, MetaMask or a hardware wallet, you need records that explain what happened, when it happened, what it was worth in GBP, and how it should be treated for UK tax purposes.
That means tracking acquisition costs, disposal proceeds, income events, fees, FX conversions, internal transfers and supporting evidence across every platform you use.
In this guide, we explain how to bridge the gap between platform reports and a compliant Self Assessment record, why CARF makes clean crypto records more important from 2026, and what UK investors should track across brokers, exchanges and wallets.
You invest. We handle the tax.
Platform data is not the same as a UK tax calculation
Platform reports can help you understand what happened inside one account, but they rarely show your complete UK tax position. A broker, exchange or wallet provider only sees the activity inside its own environment. It may not know where your assets came from, what you originally paid, whether a transfer went to your own account, or how the transaction fits into the UK tax year.
That is why platform data should be treated as source material and not as the final tax result. For Self Assessment, the relevant question is not simply what one platform reported. The relevant question is what your full investment activity produced across brokers, exchanges, wallets and bank accounts during the relevant UK tax year.
This distinction matters more as automatic reporting expands. If HMRC receives data from a broker, exchange or cryptoasset service provider, it may be able to compare that data with your tax return. If the platform data is incomplete or lacks context, you need your own records to explain the difference.
Where tax records break down
Acquisition costs can disappear
If you buy on one platform and sell on another, the selling platform may show the disposal but not the original acquisition cost. Without that cost, you cannot calculate the gain or loss correctly for Self Assessment.
Transfers can lose their context
If you move crypto from an exchange to a hardware wallet, the exchange may record an outgoing movement, but it will not know whether the destination wallet is yours. A similar issue can arise when assets move between brokers or investment accounts: one platform sees the exit, another sees the entry, but neither explains the full reason for the movement.
Final platforms only see the end of the sequence
If you move assets across several exchanges, wallets or brokers before selling, the last used platform may only see the deposit and sale. It may not know where the asset came from, when it was originally acquired, what it cost in GBP, or which fees were paid along the way.
Income can be mixed with capital movements
Dividends, interest, coupons, staking rewards and airdrops should not be treated as ordinary buy/sell movements. They may need a separate income record, with their own GBP value and supporting evidence.
Tax years can be misaligned
Many global platforms default to calendar-year reporting. The UK tax year runs from 6 April to 5 April, so a platform’s January–December summary may include transactions that belong to two different UK tax years.
What to track: from raw data to Self Assessment
A clean tax record answers four questions for every relevant movement: what happened, when it happened, what it was worth in GBP, and how it should be treated for UK tax.
Whether the data comes from IBKR, Revolut, Coinbase or a MetaMask wallet, your records should include:
transaction date and time;
platform, broker, exchange or wallet used;
asset or instrument involved;
quantity bought, sold, exchanged, received or transferred;
GBP value at the relevant date;
acquisition cost;
disposal proceeds;
fees and FX conversion costs;
dividends, interest, coupons, staking rewards, airdrops or other income events;
evidence for transfers between your own accounts or wallets;
CSV exports, broker statements, wallet records and transaction hashes.
The crypto-specific layer: CARF and HMRC platform data
From the 2026 reporting period, CARF adds a new layer to the record-keeping problem. In-scope cryptoasset service providers must collect user and transaction data that will be reported to HMRC from 2027.
This does not mean HMRC receives your full tax calculation. It means HMRC will receive platform-level data that can be compared with your Self Assessment return.
That distinction matters. CARF data may show a sale, swap, withdrawal, transfer or receipt on a reporting platform. It may not show whether the asset was originally bought somewhere else, whether the withdrawal went to your own wallet, whether the transaction belongs to a different UK tax year, or how the UK matching rules apply.
For example, a crypto-to-crypto swap on an exchange may be visible as a platform transaction, but the gain or loss still depends on your acquisition history across all wallets and exchanges. A withdrawal may be visible as an outgoing movement, but the tax treatment depends on whether it was a transfer to your own wallet, a payment, a gift or part of another transaction.
So CARF does not make crypto tax automatic. It makes incomplete records easier to detect.
For the full framework, dates and reporting rules, read our guide to CARF and crypto in the UK.
The TradFi-specific layer: broker reports, foreign platforms and UK tax rules
This is especially important when you use foreign or multi-asset platforms. An account with Interactive Brokers, eToro, Revolut or another investment app may include shares, ETFs, bonds, options, CFDs, foreign currency balances, dividends, interest or other product types. Each item can have a different tax treatment.
The platform report may also follow a calendar year, use a foreign currency, or apply classifications that are not designed around UK Self Assessment. Even when the transaction data is correct, you may still need to convert amounts into GBP, allocate them to the correct UK tax year, separate income from capital disposals and check whether the platform’s summary matches your own records.
This matters because using a foreign broker does not remove UK tax obligations. If you are UK tax resident, your reporting position depends on the UK tax treatment of your gains, income and disposals, not only on the format of the broker statement.
The practical point is the same as for crypto: broker reports are inputs. They help you reconstruct the record, but they do not replace the need to understand what was sold, what income was received, what currency was used, which fees were paid and how the final figures should appear in Self Assessment.
The biggest mismatch risks
Most tax record problems do not come from one missing file. They come from small gaps between what a platform shows and what your Self Assessment needs to explain.
The most common mismatch risks are:
using calendar-year reports instead of the UK tax year;
relying on one platform summary while ignoring assets moved elsewhere;
treating a transfer between your own wallets or accounts as if it were a disposal;
failing to prove that a withdrawal went to another account or wallet you control;
declaring only cash-outs and ignoring crypto-to-crypto swaps;
missing dividends, interest, coupons, staking rewards, airdrops or other income events;
using platform gain/loss figures without checking acquisition costs, fees, FX conversion and UK matching rules;
mixing capital gains and income in the same record;
losing the evidence behind older acquisitions, especially when assets are sold years later.
These errors matter because HMRC does not need to see your full portfolio to spot a potential inconsistency. A platform report, broker statement, bank movement or CARF data point can be enough to raise a question if it does not align with your return.
That does not mean every mismatch is tax evasion. A difference can have a valid explanation: an internal transfer, a different acquisition history, a tax-year timing issue, or a transaction that one platform cannot understand in isolation.
The problem starts when that explanation is not documented. Without a consolidated record, you are left trying to reconstruct the facts after the event, often from incomplete exports, missing wallet links and inconsistent platform histories.
How to build a clean investment tax record with Finbooks
The practical solution is not to wait until each platform gives you a separate annual report. By that point, you may already be working with fragmented exports, missing labels and transactions that no single platform can explain on its own.
A clean investment tax record should be built from the full transaction history across brokers, exchanges and wallets. That means importing the raw data, connecting movements between platforms, separating taxable events from internal transfers, and organising the result by UK tax year.
Finbooks helps you centralise and easily manage this process. You can connect or import data from different platforms, reconstruct your investment activity, track gains and losses, separate income events, and keep a clearer record of how each figure was calculated.
For crypto, this means bringing together exchange activity, wallet movements, swaps, staking rewards, airdrops, fees and transfers into one reviewable history. For traditional investments, it means organising broker data, disposals, dividends, interest, FX conversions and other taxable events in a way that supports your Self Assessment.
The goal is to create a record that can be checked, reviewed and explained. If HMRC receives platform data that does not immediately match your return, you need to show the context behind the difference: where the asset came from, whether a transfer was internal, how the GBP value was calculated, and which tax-year period the transaction belongs to.
With Finbooks, you can turn scattered platform exports into a single investment tax record, ready to support your Self Assessment and easier to review before filing.
Create your free account and organise your broker, exchange and wallet data in one place.
