GOBLIXOIdentify the number before fixing it
Your wallet and portfolio tracker disagree. Before reconnecting everything, ask what differs: the number of tokens, their displayed market value, or the recorded cost of acquiring them. Those figures describe different things. Changing one to make a dashboard look tidy can conceal the real problem.
Begin with one asset in one account at a recorded time. Compare like with like: the same network, token identity and account scope. A portfolio total across several wallets is not directly comparable with the balance shown for a single address. This narrow check gives you something concrete to investigate.
Check the underlying quantity
For an onchain account, Phantom documents how an explorer can show balances and transaction activity using an address or transaction identifier. You do not need to connect the wallet just to read that public information. Select an explorer for the relevant network.
In an illustrative example, a wallet shows 2 units while a tracker shows 1.5. Look for the missing 0.5 in the transaction history before editing a balance. Was an account omitted? Is the relevant transfer visible? Record the transaction identifier and what each screen reports. A precise discrepancy is easier to investigate than “my portfolio is wrong.”
A matching balance can hide incomplete history
CoinStats explains that some exchange or wallet APIs do not provide complete transaction history. In those cases, its system can create a fill transaction to reconcile a balance. That entry is not the same evidence as an original exchange trade record.
The practical distinction is important: a dashboard may show the expected current quantity while still lacking the full sequence that produced it. If you find a fill entry, inspect what the integration supplied and compare it with your original records. Do not assume a balanced total proves every historical transaction was imported.
Acquisition history is a separate calculation
CoinLedger distinguishes calculated holdings from holdings with known cost basis. Its documentation explains that missing imports or classifications can leave some assets without a known acquisition cost, even when those assets appear in the tracker.
Imagine 1 unit with a recorded purchase and another 0.5 transferred from an account you have not imported. Seeing 1.5 units does not explain what the additional 0.5 cost. The next useful step is tracing its earlier records. It is not choosing an arbitrary purchase price so the performance chart looks plausible.
Reconcile one discrepancy at a time
Keep a short reconciliation note: account, network, asset, time checked, quantity expected, quantity displayed and the relevant transaction identifiers. Add the original exchange export or receipt where available. Keep recovery phrases and private keys out of that evidence bundle.
If quantities agree but displayed values differ, investigate the valuation inputs and timestamp separately. If history is incomplete, inspect the integration’s documented coverage before importing another file. Preserve your starting records so that a correction remains explainable rather than becoming an undocumented adjustment.
Know when the mismatch is resolved
A useful resolution explains the discrepancy, not merely its disappearance. You should be able to say which account or transaction was missing, what evidence supported the correction, and whether the result changed quantities, valuation or acquisition history.
Portfolio cleanup and tax reporting are related but different tasks. A tracker’s performance figure is not a personal tax conclusion. If records will support a filing, check the rules for your jurisdiction with an appropriate adviser. Start with a reliable transaction history; do not ask a polished chart to stand in for one.
Save the source evidence before making a correction. A good note of what changed, why it changed and which record supports it is more useful than a dashboard total that only looks right.