If I find my holding quantity doesn't match, but I've already connected every source I remember, what else could be causing it?
Beyond an unconnected source, another common cause is an airdrop or hard fork — if you've ever automatically received an airdrop or forked coin because you held a certain token, these tokens sometimes don't appear in standard "buy/sell transaction" records. Some software requires additional configuration or manual entry to correctly recognize this kind of passively acquired asset, causing a holding quantity gap that isn't actually due to a missing transfer record.
Another easily overlooked possibility is that the token itself went through a contract upgrade or token swap (for example, a project converting an old-version token into a new-version one). If the software doesn't correctly recognize this as a continuation of the same underlying asset, it may treat the old and new tokens as two entirely separate positions, causing the quantity to look off when you look at just one version alone. If you run into this, it's advisable to first check whether this token has any official fork, airdrop, or token migration history.
In a situation where cost basis got misjudged as reset, how do I manually correct it?
Most tax software lets users manually edit individual transaction records. The core correction logic is to find the transaction where this batch of tokens "first" entered your asset scope (perhaps a purchase on an exchange, or a staking reward credited), and apply that record's cost basis and acquisition date to every subsequent movement record belonging to the same batch of assets, canceling out the reset point the software incorrectly created.
The more tedious part of this correction process is that if this batch of tokens went through multiple cross-platform moves, you need to compare the quantity and timestamp before and after each individual move, to identify exactly where the software's misjudgment began — rather than only fixing the last place you noticed the problem. If the misjudgment actually occurred somewhere in the middle, fixing only the final step leaves the earlier gap still in place, and it could resurface the same problem the next time this asset moves again.
If I genuinely can't find any raw on-chain record for a certain time period to cross-reference against, what should I do?
Most blockchains' historical transaction records are theoretically permanently queryable — entering your wallet address into a block explorer usually surfaces the complete historical record, even for transactions from a long time ago. If you can't find it, a common cause is using the wrong wallet address (for example, you have multiple wallets and queried an unrelated one), or the transaction happened on a chain you're less familiar with, requiring a different block explorer that supports that specific chain.
If you've confirmed both the address and the chain are correct and genuinely still can't find any record at all, this is relatively rare and may indicate the asset change didn't happen through an on-chain transaction at all (for example, some centralized platforms' internal bookkeeping adjustments leave no on-chain trace). In this situation, it's advisable to directly contact that platform's support team and request the internal transaction record from that time as supporting documentation.
After checking through these common gaps, how do I confirm my data reconciliation is "complete enough" to comfortably file?
There's no absolute standard that guarantees "100% complete," but a more practical check is to take the ending holdings the software calculated and cross-verify them one by one against every source you actually control (the balance each exchange account currently shows, the on-chain balance each wallet address shows). If every item matches, that typically indicates your data reconciliation has reached a trustworthy level.
For any assets involving a particularly large amount or a particularly complex path, even if they check out correctly, it's advisable to additionally keep the raw supporting evidence for these key points (transaction hashes, screenshots, reconciliation records) — not because the software's calculation is untrustworthy, but because if you're ever asked to substantiate the reasonableness of your filing numbers down the line, the more complete the concrete evidence you can provide, the easier that explanation becomes.
If your crypto assets have only ever stayed on a single exchange, tax software can typically produce fairly reliable calculations. But once an asset has crossed two or more platforms — withdrawn to your own wallet, deposited into a DeFi protocol, or moved between multiple exchanges — the number the software produces has a real chance of being built on an incomplete data foundation, and this kind of error often comes with no obvious warning sign. This article covers a few common signs of data gaps, helping you run a check before filing.
If the token holding quantity your software displays for a given moment doesn't match the balance you actually see in your wallet or exchange account, this typically means the software has missed a transfer record somewhere. A common cause is that this batch of tokens moved between sources the software hasn't connected to, causing the software's internal record to diverge from the actual on-chain or account state. When you spot this kind of discrepancy, the first step is to confirm whether every relevant source (exchanges, wallet addresses) has actually been fully connected.
If you move a token from one platform to another, the cost basis should in theory carry over untouched, since a transfer itself doesn't constitute a disposition. But if the software shows the cost basis as zero after this batch of tokens arrives at the new platform, or restarts it at the fair market value on arrival, this means the software misread the transfer as a new acquisition rather than a relocation of an existing asset. This kind of misjudgment causes the gain calculated when this batch is eventually sold to be severely overstated.
If you've staked, provided liquidity, or lent through a decentralized protocol, but the software's transaction records show nothing related, it's likely that the software failed to correctly recognize this kind of smart contract interaction, or your wallet address is connected but the software's support for this specific protocol is incomplete. This kind of gap is more concealed, since the software won't proactively tell you "I don't understand this protocol" — you need to cross-reference a block explorer's records yourself to confirm whether the software genuinely covers all the interactions.
When parsing certain kinds of on-chain interactions (such as complex multi-step contract calls), some software may break a single operation into several small transactions of unclear meaning, rather than correctly recognizing it as one single event. If you see a sudden cluster of numerous, fragmented, seemingly illogical transaction records around a particular point in time, this typically indicates the software's parsing of that specific contract interaction went wrong, requiring you to manually confirm what actually happened by cross-referencing the raw on-chain record.
What these signs have in common is that the software typically won't flag "there's a problem here" with an obvious red warning — it will confidently produce a number that looks normal, while that number is built on data with a gap in it. Taking the time to check against these signs before filing, especially for assets involving larger amounts or more complex paths, substantially reduces the risk of being asked to pay back taxes or penalties afterward — that time cost is typically far more worthwhile than the cost of fixing an incorrect filing after the fact.
⚠️ This article was researched against the most current regulations and official guidance available at the time of writing, but tax rules change frequently, and the applicable rules can vary by jurisdiction and individual circumstance. This content is intended to help you understand concepts and general direction — it does not constitute formal tax or legal advice. Before filing, please verify current rules directly with the official tax authority in your jurisdiction, or consult a qualified tax professional.