CoinTracker Portfolio Performance Guide: Reported Balances, Calculated Returns and Data Mismatch Troubleshooting

A CoinTracker portfolio can show a believable current balance while its historical chart or return looks wrong. That is possible because not every number comes from the same source. Some values are reported by connected exchanges and wallets; others are calculated from the transaction history CoinTracker has reconstructed. This guide explains that distinction and provides a careful workflow for diagnosing balance, pricing and performance mismatches without turning one visible problem into a tax-data problem.

Last reviewed: October 22, 2026. CoinTracker can change its interface, supported integrations, plan features, pricing sources and calculation methods. Connected providers can also change their APIs. Confirm current behaviour in your account and the linked official documentation before editing important records. This independent guide is educational only and is not affiliated with CoinTracker. It is not tax, legal, accounting or investment advice.

Why two CoinTracker numbers can disagree without being the same error

CoinTracker distinguishes between reported values and calculated values. A reported value generally comes from the current balance supplied by a connected exchange or wallet. A calculated value is reconstructed from transactions—buys, sells, sends, receives, trades, fees and manual changes—known to the CoinTracker account.

These numbers answer different questions. A reported balance asks what the connected source says it holds now. A calculated history asks how the portfolio arrived at its current state. If an old acquisition, wallet or transfer is missing, the present balance can remain correct while cost basis, historical charts and returns are wrong.

Where reported and calculated values appear

The exact interface can change, but the diagnostic principle remains useful: identify the origin of the number before trying to correct it.

Current value is not the same as historical performance

Current value is broadly the quantity presently held multiplied by the applicable current market price. Historical performance attempts to explain changes over time. That explanation requires more than the current quantity: it needs acquisition dates, acquisition values, transfers, disposals, fees and historical prices.

Imagine an exchange reports that an account holds one bitcoin. CoinTracker can display that reported balance even if the original purchase was never imported. But without the acquisition, it cannot reliably calculate what the asset cost, how long it was held or the return since purchase. The top-line value can therefore look normal while the performance graph and tax figures remain incomplete.

Portfolio value, cost basis and return answer different questions

• Portfolio value estimates what tracked holdings are worth at the relevant market price.
• Cost basis generally describes the recorded acquisition value adjusted under applicable rules.
• Unrealized return reflects change associated with assets still held.
• Realized return relates to completed disposals, based on the lots and values used.
• Total return can combine realized and unrealized components according to the product’s methodology.

A positive market movement is not automatically equal to taxable income, and a taxable gain is not simply the amount withdrawn to a bank. Use the portfolio metrics for monitoring, then review the relevant jurisdictional tax report separately.

A deposit is not automatically investment profit

If cash or crypto enters a tracked account, portfolio value can rise because new capital was added. That does not mean the portfolio earned that amount. A performance calculation must distinguish contributions from returns. Similarly, moving your own crypto from one wallet to another should not create investment profit merely because the receiving address appears for the first time.

If CoinTracker sees only the receiving side, the arrival can look like a new acquisition or unknown receipt. If it sees only the sending side, the departure can look like a disposal. Connect both sides and classify the event based on what actually happened before interpreting the chart.

A withdrawal is not automatically a loss

When an asset leaves an exchange for a self-custody wallet, the value has not necessarily left the person’s portfolio. It moved between locations. If the destination wallet is missing, calculated holdings may fall on the withdrawal date even though the owner still holds the asset.

Conversely, a genuine payment, gift, loss or transfer to another owner should not be forced into an internal-transfer classification just to make the chart look smoother. Portfolio presentation must follow the economic event, not the desired graph shape.

Start by identifying the symptom precisely

“My CoinTracker balance is wrong” is too broad for efficient troubleshooting. Record the exact asset, wallet, date, currency and screen. Determine whether the issue affects:

• only the current total;
• one wallet’s current balance;
• the historical chart;
• unrealized or realized return;
• cost basis;
• one transaction or the whole portfolio;
• web, mobile or both.

Take a screenshot that excludes API secrets, tax IDs and private information. Also note the time of the last successful sync. A precise symptom prevents unnecessary edits across unrelated years.

Find the first date the history becomes wrong

Do not begin with the most recent number if the error started years earlier. Move backward through the historical graph or transaction list until the calculated value last agreed with reliable source records. Then inspect the first date or event after that point.

A sudden unexplained jump often indicates an unmatched receive, duplicate import or incorrect price. A sudden decline can indicate an untracked destination wallet, taxable send classification or missing trade side. A gradual divergence can result from repeated rewards, fees or partial integration coverage.

Sync before manually changing transaction history

Use CoinTracker’s current sync controls first. An API connection may simply be behind, and a blockchain transaction may still be pending or awaiting indexing. Verify the connection has not expired and still has the documented read-only permissions.

After sync, allow the recalculation to finish before comparing values. Repeatedly editing while data continues to import makes it difficult to know which action changed the result.

When re-import can help

CoinTracker documents re-import as a troubleshooting option for refreshing wallet history while preserving supported manual work. Use the live instructions for the integration because behaviour can vary. Export important source records and understand what the operation will affect before starting.

Re-import is not a substitute for adding a missing account. Refreshing Exchange A cannot discover transactions that exist only at Exchange B or in a self-custody wallet CoinTracker does not know about.

Build a complete inventory of every location

List every exchange, software wallet, hardware wallet, blockchain address and imported CSV used during the entire relevant history—not only those still active. Include closed or defunct accounts where records can be obtained. An asset sold this year may have been acquired many years earlier on a platform no longer used.

For UTXO-based assets, one visible address may not represent the full wallet history. Follow CoinTracker’s integration guidance for supported extended public keys or account-level imports where applicable. Never provide a seed phrase or private key merely to improve tracking.

Old and closed exchanges still matter

Removing an exchange from daily use does not remove its acquisitions from cost basis history. If an asset was bought there and later transferred elsewhere, omitting the old source can make the new wallet appear to receive an asset with unknown origin.

Use official CSV exports, statements and transaction IDs where API access no longer exists. Preserve the untouched source file before transforming it into an import format.

API coverage can be narrower than an account statement

An exchange API may omit older periods, certain products, rewards, distributions, delisted assets or activity from a retired sub-platform. A green connection indicator confirms access; it does not necessarily prove complete lifetime history.

Compare earliest and latest imported dates, major deposits, large trades and ending quantities with exchange statements. If API and CSV cover the same events, importing both without reconciliation can create duplicates.

Duplicate imports can make a portfolio look richer than it is

A duplicate can occur when the same exchange is connected through API and CSV, when an import is repeated or when a manual transaction duplicates an automatic record. Match candidate duplicates using timestamp, asset, amount, fee, order ID and transaction hash. Similar amounts alone are not enough.

Do not delete the first row that looks repeated. Complex trades and DeFi interactions can legitimately generate multiple records. Establish which record represents the source event and retain supporting evidence for any removal or ignored classification.

Ignored transactions still deserve review

CoinTracker’s troubleshooting documentation recommends reviewing transactions marked ignored. Ignoring a record can remove it from calculations while the provider continues reporting the corresponding asset balance. That can create an apparent gap between reported and calculated values.

Filter ignored records and document why each one is excluded. Spam can be a valid reason; an inconvenient gain or an unexplained transfer is not.

Manual transactions can repair or create history

A manual entry is appropriate when reliable activity cannot be imported automatically and the user has evidence for the missing event. It becomes dangerous when used only to force the current total to match. A balancing entry with no real-world source can distort acquisition dates, basis and future disposals.

For every manual record, preserve the exchange statement, wallet transaction, bank evidence or calculation that supports it. Add a consistent private note where the product permits. Revisit manual records after integrations improve so they do not later coexist with newly imported duplicates.

Pending transactions may not be part of current calculations

A pending exchange order or blockchain transaction is not the same as a completed transfer. CoinTracker notes that pending activity may be excluded from current market value until completion. Check the source platform or block explorer before creating a replacement record.

If the transaction later completes, sync again. A manual copy made during the pending state can become a duplicate when automatic history catches up.

Transfer matching depends on both sides

An internal transfer normally includes an outgoing side, an incoming side and possibly a network fee. Times and amounts may differ slightly because exchanges batch withdrawals or deduct fees. CoinTracker needs enough evidence to associate the sides appropriately.

When a transfer is unmatched, inspect transaction hashes, assets, networks, dates, sent quantity, received quantity and fee. Confirm both locations belong to the same taxpayer before treating the event as internal.

Fees can explain small quantity differences

If one wallet sends 1.0 unit and another receives 0.999 units, the gap may be a network or withdrawal fee rather than missing crypto. Different chains charge fees in different assets, and an EVM transaction may use the native gas token separately from the transferred token.

Do not round both sides until they match. Record the actual quantities and fee structure shown by the exchange and blockchain.

Wrapped assets and bridges can break visual continuity

A bridge can lock or burn an asset on one network and create or release a related asset on another. A wrapper can exchange one token representation for another. If CoinTracker sees only part of the sequence, value may appear to disappear, reappear as income or be counted twice.

Trace the complete transaction group using explorer records and protocol documentation. Determine whether the user retained economic ownership, received a distinct asset or entered a new position. Tax treatment can be uncertain and jurisdiction-specific, so consult a qualified professional for material cases.

Staking, interest and rewards can change both quantity and basis

Repeated small rewards gradually increase holdings. If an API excludes them, reported quantity and calculated quantity can drift apart. If they are imported but incorrectly classified, return and income views can also be misleading.

Compare reward statements by period rather than checking only one day. Confirm asset, quantity, date and source. Do not manufacture a single annual receipt if local rules and actual distribution records require transaction-level detail.

Spam and dust tokens can distort the portfolio

Public addresses can receive unsolicited tokens. Some carry misleading names or manipulated prices designed to make a wallet appear valuable. Do not visit a URL embedded in a token name, approve a contract or pay a fee to “claim” the displayed value.

Verify the contract address and market independently. Use CoinTracker’s current spam or ignore controls only after confirming the asset is unsolicited and irrelevant to the real portfolio.

How CoinTracker sources historical prices

CoinTracker states that it uses third-party market-data providers for supported cryptoassets and describes a daily opening price at 12:00 AM UTC for relevant calculations. It also documents direct API pricing for selected platforms. The method can explain why a historical value differs from an intraday trade price or another website’s chart.

Price is only one part of the calculation. Quantity, category, timestamp and currency must also be correct. Changing a historical price should be a documented correction, not a way to produce a preferred return.

Missing price history can have a large effect

A low-liquidity token, NFT or unsupported asset may lack reliable historical pricing. Depending on the transaction, missing value can affect cost basis or proceeds. CoinTracker’s documentation describes workflows for confirming a zero value or entering supported missing data in applicable products.

Zero is not a neutral placeholder. It can create an artificially large future gain or eliminate proceeds incorrectly. Before accepting or entering zero, search transaction evidence, contemporaneous market data, protocol records and professional valuation guidance where material.

Delisted and renamed assets need identity checks

An exchange may delist a token while its historical trades remain relevant. Token migrations, symbol reuse and contract changes can cause the wrong market-price series to be associated with an asset. Match by contract or authoritative asset identity rather than ticker alone.

Preserve migration ratios and transaction evidence. Do not merge two unrelated assets simply because they share a symbol.

Fiat currency settings can change the displayed story

A portfolio viewed in USD can show a different percentage path from the same holdings viewed in EUR or GBP because exchange rates change. Ensure the account’s base currency matches the intended analysis and that imported fiat transactions use the correct currency.

A bank deposit labelled as USD when it was CAD does not become correct through conversion. Fix the source denomination based on evidence, then let CoinTracker recalculate.

Compare CoinTracker with the right source

Never use a blockchain explorer to verify an exchange’s internal trade ledger, and never use a current exchange balance to prove how an asset was acquired years earlier.

A safe portfolio-mismatch workflow

1. Record the incorrect metric, screen, asset, currency and date.
2. Determine whether the value is reported or calculated.
3. Sync all connected wallets and exchanges once.
4. Wait for recalculation and check provider or CoinTracker incidents.
5. Identify the first historical point where the result diverges.
6. Inventory every account and address used before and after that date.
7. Compare source records, transaction hashes and imported entries.
8. Review missing, duplicate, ignored, pending and manual transactions.
9. Check transfer pairs, fees, asset identity and historical price.
10. Make the smallest evidence-backed correction.
11. Sync or recalculate, then verify balance, chart, returns and tax warnings.
12. Keep a correction log for future review.

Symptoms, likely causes and next checks

Scenario: a missing self-custody wallet

A user buys ETH on an exchange and later withdraws it to a hardware wallet. Only the exchange is connected. The exchange reports no current ETH, and calculated history may treat the withdrawal as value leaving the tracked portfolio. Adding the correct public wallet can provide the receiving side and restore continuity.

The safe fix is not a fabricated manual deposit into the exchange. Confirm the transaction hash, destination ownership, amount and network, then add the actual wallet using the supported public-data method.

Scenario: API and CSV cover the same year

A user connects an exchange API and imports a full-year CSV because recent activity appeared late. The same trades now exist twice, increasing quantities and distorting returns. The correct response is to identify overlapping records using order IDs, timestamps, assets and amounts—not delete an entire year blindly.

Preserve the source CSV and document which import was removed or ignored. Then compare beginning and ending balances with the exchange statement.

Scenario: a token has no reliable historical price

A received DeFi token shows zero value on the transaction date but a meaningful value later. Before entering a price, verify the contract, acquisition route and market that actually existed at that time. A later price or a different token with the same symbol is not valid evidence by itself.

For a material tax position, retain the valuation method and seek professional advice. A manual price affects more than the chart; it can affect basis, proceeds and tax output.

Scenario: a bridge looks like a disposal and new income

CoinTracker sees the token leaving Network A and another representation arriving on Network B, but it does not associate the actions. The portfolio can dip and rise while the tax view shows two unrelated events. Trace the bridge transaction and linked messages across both chains, then use the current supported classification workflow.

Do not assume every bridge is tax-neutral or taxable. The legal result depends on facts and jurisdiction; the data task is to preserve the complete event.

What not to do when returns look wrong

• Do not add a fictional opening balance merely to match today’s total.
• Do not change an acquisition price to obtain a preferred gain.
• Do not ignore every unexplained transaction.
• Do not import the same CSV repeatedly while troubleshooting.
• Do not delete a wallet before preserving its history and manual edits.
• Do not classify a transfer as internal unless both locations share ownership.
• Do not enter a seed phrase or private key into a portfolio tracker.
• Do not treat a smooth chart as proof that tax records are correct.

Verify the correction across more than one screen

After a change, check the affected transaction, wallet quantity, total portfolio, historical chart, realized and unrealized returns, cost-basis alerts and tax summary. A correction that improves one metric but creates a new warning elsewhere may be incomplete.

Also compare the next transaction involving the same asset. An incorrect acquisition can remain hidden until a later disposal selects that lot.

Keep a portfolio correction log

Record the date, affected account, transaction ID, original problem, source evidence, change made and result. This is especially useful when APIs re-import history or when a tax professional reviews the account later.

The log does not need to contain API secrets or private keys. Store it with protected financial records and keep original statements unchanged.

CoinTracker portfolio review checklist

1. Confirm base currency and account settings.
2. Sync every active connection.
3. List current and historical exchanges, wallets and addresses.
4. Compare reported balances with source platforms.
5. Check the first and last dates in every imported history.
6. Review ignored, pending and manual transactions.
7. Investigate duplicate imports and unmatched transfers.
8. Verify fees, bridges, wrapped assets and rewards.
9. Review missing prices and asset identity.
10. Recheck charts, returns, basis and tax warnings after changes.
11. Export source data and maintain a correction log.

Frequently asked questions

Why is my CoinTracker balance correct but performance wrong?

The current balance can be reported directly by a connected provider, while performance is calculated from transaction history. Missing acquisitions, transfers, prices or old wallets can therefore affect performance without changing the provider’s current balance.

Should I add a manual transaction to make the totals match?

Only when a genuine event is missing and reliable evidence supports the entry. Do not create a balancing transaction merely to force agreement, because it can distort future returns and tax reports.

Why did a transfer create a gain or loss?

CoinTracker may not know the receiving wallet, original acquisition or relationship between the outgoing and incoming sides. Trace both sides and verify ownership before changing classification.

Why does CoinTracker show a different historical price from an exchange chart?

Pricing sources and time conventions can differ. CoinTracker documents its market-data sources and daily price methodology. An exchange chart may show an intraday last trade rather than the value used by CoinTracker.

Can I remove an old exchange after transferring everything out?

Its historical acquisitions and trades may still be necessary for cost basis and performance. Preserve and verify the history before removing any connection.

Does a corrected portfolio graph prove my tax report is accurate?

No. It is a useful consistency check, but tax accuracy also depends on complete records, classifications, lot methods, jurisdictional rules and report settings.

Official CoinTracker references

Use these first-party CoinTracker resources to confirm current behaviour before changing portfolio or tax data:

• CoinTracker Blog — official product news, crypto-tax explanations and workflow updates.
• CoinTracker Support — Reported and Calculated Values — explains which portfolio numbers come from providers and which are reconstructed from transaction history.
• CoinTracker Support — Troubleshoot Portfolio Tracking Issues — sync, re-import, ignored records, transfer mismatches and wallet-specific checks.
• CoinTracker Support — Ensure Transaction History Is Complete — a checklist for exchanges, public wallets, cold storage and earlier transaction history.
• CoinTracker Support — Cryptocurrency Pricing Data — official information about market-data sources and historical price methodology.
• CoinTracker Support — Troubleshoot Missing Price History — guidance for unsupported historical values and affected cost basis or proceeds.
• CoinTracker Pricing — current plan availability for performance tracking, tax lots and related tools.
• CoinTracker Product Changelog — recent interface, portfolio and calculation updates.

A trustworthy performance view begins with an explainable history. The goal is not to make every chart look smooth; it is to make each material change traceable to a real deposit, trade, transfer, fee, reward, price or withdrawal. Once the source data is complete, reported balances and calculated performance become useful cross-checks instead of competing numbers.