The import finished and the portfolio total is nowhere near your broker's. This article covers what goes wrong in that first look - a position that doubled, a wrong symbol, missing rows, a return that won't compute, cash counted twice. If the import itself flagged skipped rows or duplicates, start with Duplicates and re-importing; if the numbers were right at import time and something looks wrong now, pick the symptom from Troubleshooting instead.
My portfolio total doesn't match my broker after an import
Check share quantities first - they must match the broker exactly. If they match and only the value is off, the cause is almost always a wrong symbol. If they don't match, transactions are missing or something is counted twice.
Reading the import summary
The counts tell you how many transactions and assets the import touched - "32 Updated" means 32 assets had their prices updated. Warnings shown during the import expand when you click them. An unsupported transaction type is a common one; send us a sample file and we can usually add it - see Rows with a transaction type that is not supported.
A position shows more than I bought
An Account Balance and a Buy on the same date stack rather than replace each other: when the balance is ordered first, the position shows balance plus buy instead of just the buy. Use one approach per date - the stated balance or the trade, not both - or fix the ordering.
Share counts match but the value is wrong
When quantities agree with your broker and only the value is off, a wrong symbol was matched and the market price is coming from a different security. Edit the asset, open the Prices tab and correct the market symbol.
Choosing between listings for the same ISIN, and what to do when no listing fits, are in Prices, symbols and market data.
Shares are missing, or shares I sold are still there
If quantities don't match your broker, transactions are missing. Corporate actions and transfers are the usual gap - they are often absent from broker exports altogether. If a position shows shares you know you sold, look for a symbol change, conversion or merger behind it rather than a missing sell.
Rows the importer skipped are the other source: Duplicates and re-importing explains why a row is skipped and how to bring it back. When the gap is wide enough to drive a balance negative, see Balances and cash don't match.
Rate of Return shows NaN
NaN on a position right after an import means the position holds dividends but no share transactions. Either the dividend was imported under a different asset than the purchase - look for near-duplicate asset names - or the shares were never imported. With no cost basis, there is no return to compute.
Other causes of NaN, including an MWR solver that does not converge, are in Returns and charts look wrong.
Cash is counted twice after the import
Some presets create Transfer In rows because the broker omits deposits - the Polish treasury bond preset for PKO does this for every bond purchase. When redemption proceeds are rolled into new bonds on the same account, that cash is counted twice. Delete the excess Transfer In rows, or set the broker to sweep sale proceeds to an external account.
The signature is a gap between two filters: All assets is inflated while With Income matches your real holdings, and the gap equals the accumulated redemption cash.
The import fails, or characters come out garbled
Run the import in a Chromium browser - Chrome, Edge, Opera or Arc. Firefox is behind a small family of file-reading failures that look exactly like a broken export: on Windows it sometimes reads a CSV as a SYLK file and rejects the format outright, and Polish characters in eMakler and Bossa exports (Giełda, Wartość) can arrive mangled, so the importer reports columns it does not recognise. A Firefox extension can block the import entirely as well - the same file goes in on a clean Firefox profile.
Nothing about the file changes between browsers, only the reading of it. Re-open the same export in Chrome before you go looking for a fix in the broker's export settings.
Broker-specific problems
A handful of brokers produce most bad imports, and each fails in its own recognisable way: an export that looks complete but isn't, a second file you also need, a symbol the broker never publishes. Those traps have a page of their own - Problems with specific brokers covers Interactive Brokers, Degiro, XTB, Revolut, Trade Republic, Charles Schwab, Bossa, mBank eMakler, PKO BP, Robinhood and the crypto exchanges.
The export steps themselves are never on the website: every import preset carries its own on the import screen, next to the file picker, and you can read them for any broker in the demo project without an account.