How to Find Missing Transactions in Your Crypto Tax Report

Overview

A tax report with missing transactions does not announce itself. It produces a number, and the number looks plausible, and it is wrong.

The failure mode is nearly always the same and nearly always in the same direction. What goes missing is the acquisition — the purchase, the transfer in, the reward that arrived. Disposals are easier to capture because they usually happen somewhere obvious. So a report with gaps tends to show proceeds with no cost behind them, which overstates the gain and therefore the tax.

This article works through the causes in rough order of how often they turn out to be the culprit.

Start With the Symptom

Different gaps produce different symptoms, and the symptom narrows the search considerably.

What you see	Usual cause
Balance reads zero but the wallet holds coins	Bitcoin-style wallet imported by address instead of extended public key
An asset appears from nowhere and is then sold	The source it came from was never connected
Coins leave and never arrive anywhere	The destination wallet was never connected
History stops on a particular date	Exchange export window, or a source you stopped importing
A whole year is thin	A network or account you forgot you used
Rewards missing but trades present	Income events not captured, or a staking source not connected
Outgoing transactions with no fee	Zero-movement transactions dropped by the import

Cause One: A Source You Never Connected

This is the answer most of the time, and it is worth being systematic rather than relying on memory.

Write down every venue you have ever used. Not the ones you use now — the ones you have ever used. Exchanges you signed up to for a single trade, a wallet you abandoned, an exchange that no longer exists, the app a friend recommended in 2021.

CryptoTaxBridge connects eleven exchanges by API, and ten of those also accept a CSV export. Blockchain wallets are covered separately across twenty-two networks. For a venue outside that list — a closed exchange, a small local platform, a peer-to-peer trade — the history will not import itself, and you will need to assemble those records another way before the chain of acquisitions is complete.

The test is not whether a venue still holds a balance. It is whether anything you later sold ever passed through it.

Cause Two: One Network Out of Many

An 0x address is the same string on every EVM network, which makes it easy to import Ethereum, see a sensible-looking history, and stop.

If you have ever bridged to an L2, claimed an airdrop, minted anything, or used a protocol because the fees were cheaper, that activity lives on a different network under the same address and needs its own import. Importing MetaMask across every network lists what to check.

The same applies within a wallet. Additional accounts are different addresses. A hardware wallet connected through a browser wallet adds more. Ledger Live's per-chain accounts each have their own.

Connect another source

Cause Three: Bitcoin Imported as an Address

This one deserves separating out because the symptom is so distinctive: a handful of transactions, then nothing, and a balance of zero on a wallet you know holds coins.

Bitcoin wallets send change to a newly generated address every time you spend. After your first outgoing payment, your funds are on addresses you have never been shown. Importing the address in your wallet interface captures the beginning of the story and none of the rest.

The fix is to import the extended public key — the string starting xpub, ypub or zpub — which derives every address in the account. It is read-only and cannot move funds. The full explanation is here, and the same applies to Litecoin and Dogecoin.

Cause Four: The Exchange Only Gave You Part of It

Exchange exports have limits that are not always signposted.

• Date windows. Many exchanges cap a single export at three months, or a year. Requesting "everything" quietly returns the most recent window.
• Report types. Trades, deposits, withdrawals, conversions, staking rewards and earn products are frequently separate exports. Downloading the trade history alone misses the rest.
• Retention. Some platforms do not keep older history available for download at all.
• Sub-accounts. Futures, margin, funding and earn accounts can each hold history the spot account does not show.

An API connection avoids most of this, which is the main argument for it over manual files. API import and CSV upload compared covers what each approach misses.

If you have any suspicion that an exchange will not keep your history forever, export it now and keep the file, regardless of what tool you use.

Cause Five: Transactions That Move Nothing

Some transactions have no asset movement at all, and simpler import tools skip them because there is nothing to record.

Approvals, failed transactions, and self-transfers all fall into this group. None of them transfers a token to a new owner, but all of them cost a fee — and that fee is both a cost of transacting and a small disposal of the coin used to pay it.

If your outgoing transactions show no fees, or your history has no failed transactions in a year when you know at least one failed, they were dropped. CryptoTaxBridge imports them deliberately, which means the history contains rows that appear to do nothing. That is intentional. What is and is not deductible explains why they are worth keeping.

Cause Six: You Deleted Them

Worth checking before assuming anything is broken.

Reviewing imported data means deleting things — spam tokens, duplicates, transactions that turned out to be noise. It is easy to over-delete on a first pass, particularly with unfamiliar tokens.

Deleted transactions can be restored. If a gap appeared after your review rather than after the import, look there first.

Review your transactions

Working Through It

A method that works better than staring at a list:

1. Pick the asset with the largest reported gain. That is where a missing cost basis costs you most.
2. Trace it backwards. Follow the disposal to where the asset arrived, and that arrival to where it came from. Keep going until you reach an original purchase with fiat.
3. Note where the chain breaks. The break is the missing source.
4. Connect it and re-check. Then repeat for the next asset.

Most portfolios have two or three breaks, not twenty. Fixing them in order of size means the report converges quickly.

Once the chain is intact for your largest positions, compare imported balances against what each wallet and exchange actually shows. That comparison catches the remainder, and a mismatch has its own short list of causes.

Conclusion

Missing transactions are the most common reason a crypto tax report is wrong, and the most common reason it is wrong in the taxpayer's disfavour. Proceeds without cost basis produce a gain that never happened.

Almost all of it comes down to sources. Every exchange you ever used, every network your address touched, every account inside every wallet, imported completely rather than partially. The rest is checking that fees and rewards survived the import, and that your own review did not remove something you needed.

Do it once, properly, well before a deadline. Tracking as you go is what stops it from becoming an annual archaeology project.

Import your full history

Official Resources

• HMRC: record keeping for cryptoassets (CRYPTO10400)
• HMRC: pooling and matching rules (CRYPTO22200)
• GOV.UK: how long to keep your records
• IRS: digital assets

This article provides general information and is not tax advice. Exchange export limits and API capabilities change; check the platform's own documentation.