Connect With Us

You are at:

Why Your Crypto Portfolio Tracker Balance Is Wrong

Person using a calculator and laptop with financial charts while investigating an incorrect portfolio balance

When a portfolio tracker disagrees with the wallet or exchange, editing the final balance is the fastest way to hide the cause.

The discrepancy usually comes from one of six layers. Check them in order; the earlier layers affect everything calculated after them.

1. The account list is incomplete

A tracker cannot follow assets through a wallet it does not know belongs to you. One missing exchange, hardware-wallet account, change-address branch or chain can turn an ordinary transfer into a disposal on one side and unexplained income on the other.

Start with an inventory of every venue and wallet used, including closed accounts and addresses with a current balance of zero. Historical accounts still carry acquisition records.

2. The connection is live but the history is partial

An API can authenticate successfully and still return only part of the record. CoinTracker lists incomplete exchange history as a cause of insufficient-quantity and negative-balance errors. Check the earliest and latest imported transactions against the exchange’s own history.

If the gap is historical, obtain an exchange-specific export. Do not create one manual opening balance unless you also preserve the date, source and acquisition evidence behind it.

3. The same activity was imported twice

Mixing API and CSV data is a common source of duplicate trades. Exact duplicate detection may not catch records with different timestamps, rounding or fee treatment. Koinly documents that an order file and a trade-fill file can describe the same event differently enough to survive deduplication.

Filter by asset and time. Look for pairs that are economically identical even when the rows are not textually identical.

4. The quantity is right but the price is not

A dashboard balance is quantity multiplied by a chosen market price. Thin tokens, wrapped assets and identically named contracts can break either side.

Verify the contract address and chain before changing a price. A spam token with a copied symbol is not the asset you intended to track. For legitimate illiquid assets, compare the tracker’s methodology with an actual market that had executable volume at the timestamp.

5. A transfer was treated as two unrelated events

Transfers between owned wallets should preserve the asset’s history, subject to local rules and fee treatment. Matching can fail when one account is missing, timestamps differ, network fees reduce the received quantity or a bridge changes the token representation.

Koinly says it matches transfers after wallets are added. CoinTracker warns that send and receive records should be checked so owned-wallet movements are not mistaken for unrelated events.

Repair the pair, not the portfolio total.

6. DeFi and staking changed the form of the asset

Depositing 100 units into a staking or lending protocol can remove the original token and create a receipt token, internal balance or claim. A generic tracker may show the outgoing asset as gone without recognizing what replaced it.

CoinTracker’s missing-balance guidance highlights staking, lending and liquidity histories as frequent causes. The evidence needed is the contract transaction and protocol accounting, not a guess that “the money is still there.”

A reconciliation that does not destroy evidence

  1. Record the expected quantity from the wallet, exchange or protocol.
  2. Check the exact account and network in the tracker.
  3. Find the first date on which expected and calculated balances diverge.
  4. Inspect the transaction immediately before and after that point.
  5. Correct the source record, classification or missing account.
  6. Recalculate and confirm that downstream balances change coherently.
  7. Keep a note explaining every manual correction and its source.

If a correction fixes today’s total but creates a negative balance in an earlier year, it is not a correction. It is a new inconsistency.

The parent explanation is what portfolio trackers know, guess and miss. For a broken historical acquisition, continue to missing cost basis. If imports overlap, compare address, API and CSV evidence.

If the software repeatedly hides rather than explains discrepancies, return to the portfolio tracker decision guide.

Primary sources

Leave a Comment

Your email address will not be published. Required fields are marked *