Import your broker statement into a portfolio tracker

A portfolio tracker without a broker connection

Most trackers start by asking for a broker login or an API key. This one starts from a document. The statement your broker already produces — the same file you would keep for your own records — carries everything a tracker needs: holdings, purchases, dividends and fees. Reading that file requires no credentials, works for brokers no aggregator supports, and cannot touch the account it describes.

The trade-off is stated plainly: an import happens when you upload something, not on a nightly sync. For a long-term portfolio that is updated with monthly statements, that is usually a feature rather than a cost — every change to the portfolio is one you reviewed and confirmed. (The one broker that can sync itself is Freedom24, via read-only API keys you generate — optional there too.)

Uploading is itself optional. If sharing a statement at all is more than you're comfortable with — a reasonable privacy preference — you can pick your positions manually instead: search the instrument, enter the quantity, done. The portfolio behaves exactly the same, and no document ever leaves your machine.

Which formats can be uploaded? PDF, CSV, screenshot, text

There is no supported-broker list to check against — the extractor reads the document, not an API. Free accounts get 3 document imports a month, Pro is unlimited.

Interactive Brokers is a good example of how far one file goes: a single multi-month IBKR Activity Statement in PDF or CSV produces current holdings and the contribution history behind them, so the portfolio arrives with months of record instead of starting from today. The IBKR import walkthrough covers that case step by step, and the Interactive Brokers portfolio tracker page shows what the statement becomes once it is in. The same applies to any broker whose statement you can save as a file.

European brokers differ in what their export actually contains, and that difference decides what you get: DEGIRO prints holdings and transactions in one report, Trade Republic issues a holdings statement and separate trade confirmations, and Trading 212 exports a transaction log with no holdings table at all — so the positions are computed from the trades. Each has its own walkthrough.

What gets extracted?

• Positions — ticker, quantity and average price, including fractional quantities. Positions closed during the statement period are not resurrected as holdings.
• Purchases — each buy becomes a contribution, dated, with quantity, price per share and the commission charged on that trade.
• Dividends — payments received during the period, per instrument.
• Statement metadata — broker, period covered and file name, kept so a later upload can be compared against what was already applied.

Anything the extractor reads incorrectly can be edited in review, and holdings can always be added by hand instead — including from the very start, without uploading a statement at all.

What happens when statements overlap?

Overlapping periods are the normal case — most people re-export the whole year rather than trimming to what is new. Two rules keep that safe:

• Transactions already imported are matched and listed as skipped duplicates in the review, with counts shown before you confirm. Re-uploading the same file adds nothing.
• A statement whose period ends earlier than the last one applied does not silently replace newer position quantities — an older document cannot rewind the portfolio.

What does the portfolio look like after an import?

Beyond current holdings, the imported history is used to reconstruct the months the statement covers: contributions grouped by month, dividends received in those months, and a monthly snapshot for each one. That is what makes the contribution record and the split between deposited capital and market growth meaningful from day one rather than after a year of use.

See how contributions are tracked and how contributions are separated from market growth.

What import does not do

• It does not connect to your broker, hold a broker password, or place trades. Import is a one-way read of the file you hand it — the one direct broker connection in the product, Freedom24, is a separate opt-in path, not part of import. What happens to the file itself — what is stored, what is deleted and when — is on the security & data handling page.
• It does not import individual bonds, notes or treasuries. Their prices are quoted per 100 of face value and they carry coupons rather than dividends, so reading them as shares would misstate both the position and the money put in. Rows like these are listed as not imported in the review screen. Bond funds — an ETF, ETN or mutual fund with a ticker — are imported normally.
• It does not invent costs a statement does not show — fund expense ratios and FX spreads are not estimated.
• It does not treat extraction as authoritative: every import passes through a review screen you confirm.

Common questions

Which broker statement formats can BorderFolio read?

PDF statements, CSV exports, plain text, and screenshots or photos of a broker app. The statement does not have to come from a supported broker list — the extractor reads the document itself, and anything it misreads can be corrected during review.

Can I track my portfolio without connecting my broker?

Yes — that is the default path, and it works for every broker. Import reads the statement file you upload (PDF, CSV, text or screenshot), extracts holdings and transactions, and adds nothing until you review and confirm, so it works for brokers no aggregator supports. Uploading is itself optional: positions can be picked manually, with no document involved. A direct connection exists for exactly one broker, Freedom24, and it is opt-in — read-only API keys you generate yourself — never a requirement.

Can BorderFolio import an Interactive Brokers statement?

Yes. An IBKR Activity Statement in PDF or CSV is one example of a statement it reads: positions, purchases, dividends and explicit broker fees are extracted, reviewed by you, and de-duplicated against earlier imports. The same applies to any broker whose statement you can save as a file.

Will uploading overlapping statements create duplicate transactions?

No. Transactions already imported are matched and reported as skipped duplicates in the review screen, and a statement whose period ends earlier than the last one applied does not overwrite newer position quantities.

Does importing a statement require broker credentials?

No. Statement import reads only the file you upload — it never asks for a broker login or key, and it cannot place trades or move money. Separately, Freedom24 accounts can optionally be connected with read-only API keys instead of uploading, but no statement import ever requires a credential.