Documentation

Getting your data in

Fortunest reads the transaction-history CSV files your platforms already let you download. Drop them in; the format is detected automatically and the whole portfolio is rebuilt from the raw transactions.

What's supported

Connecting an account instead of uploading

A CSV is a snapshot you repeat by hand. With a Fortunest account you can link the account itself and let it keep up with you. ⚙ Settings → Data → Connect an account opens one searchable list of every platform, each marked with how it can be brought in — some carry two marks, and then they are alternatives, not steps:

• Direct API — a read-only key you create at the platform yourself, with nobody in between: Kraken, Binance, Coinbase, Coinmate, Trading 212 and Interactive Brokers (a Flex query). The connect form walks you through making the key, and gives you the IP address to whitelist where the platform offers one. The key is checked live and nothing is stored unless it works; a refusal appears in red under the Connect button, saying which of three things went wrong.
• SnapTrade — you sign in at your broker through a read-only partner: Schwab, Fidelity, Robinhood, Questrade, E-Trade, eToro and others. Platforms with a direct connector are deliberately not offered this way — the direct key reaches further back, syncs faster and hands nobody else access. Brokerages already connected through SnapTrade keep working.
• CSV — the upload described below, which never needed an account at all. Degiro and Trezor are CSV only.

Every connection is read-only. Fortunest can see your positions and transaction history; it cannot place, change or cancel an order, and it cannot move money — there is no order-placing code in the app, and a test asserts it. You never hand over a broker password.

Your keys are encrypted at rest, never sent to your browser, never logged and never passed to a third party. A connected row shows only the public half of the key — eight characters of the identifier, click to read it whole and copy it — because that half authenticates nothing on its own. The secret half is sealed when you save it and cannot be read back by anyone, us included.

Everything you have linked appears under Connected accounts in ⚙ Settings → Data, sorted by platform: the route mark, a health dot, when it last brought anything in — or plainly Never synced — plus an include tick, Sync now and Disconnect (staged until Save, with ↩ to keep it). The first sync fetches as much history as the platform's API will serve; later ones are incremental and run in the background. Disconnecting a direct connection deletes the stored key and the data imported through it; disconnecting a SnapTrade brokerage leaves its transactions in place.

Connecting needs a signed-in account — a key has to outlive the browser session — and a new connection uses one of your plan's account slots, the same three a CSV file uses on the free plan. The desktop app connects directly too: the keys live in its local database and the calls go straight from your machine to the platform. SnapTrade is not part of the desktop build.

Adding & managing files

• To add files: drag them onto the Portfolio value tile (it's a dropzone while the dashboard is still empty) or open ⚙ Settings → Data and drop them on the Data sources card. Dropping a whole folder walks it recursively and picks up every supported CSV inside — unrecognised files are skipped with a notice.
• To temporarily exclude an account: untick the checkbox next to its file. It stays saved but is left out of the portfolio until you tick it again.
• To remove a file: use its remove button — the row is struck through until Save applies it, and ↩ keeps it after all; Remove all files marks the whole set the same way in one click.
• Everything applies on Save. Inside the Settings dialog every data edit is staged: files you drop appear as pending rows and only upload and parse when you press the dialog's Save button, which also applies removals and ticks in a single rebuild (only the accounts that changed are repriced). A freshly connected brokerage imports its data on Save too, and the Other-asset and Market-priced rows stage every change the same way — adds wait as pending rows, value edits arm Save instead of growing per-row buttons, ticks queue, and a ✕'d row is struck through until Save removes it (↩ takes it back). Closing the dialog with staged changes raises an Unsaved settings prompt — Apply or Discard. (The empty-tile dropzone lives outside the dialog and imports immediately.)

Revolut

On invest.revolut.com click your profile icon (top right) and choose Documents:

Select Brokerage account and choose Account statement under Statements:

Then pick the Excel format (it downloads as CSV), set Period to All time and hit Get statement:

Degiro

On trader.degiro.nl open Inbox → Transactions, set the from/to dates to cover your whole history and click the download icon on the right:

In the Export dialog choose CSV:

Interactive Brokers

Create a Flex Query for Trades in IBKR's Client Portal (Performance & Reports → Flex Queries), covering your whole history, and run it as CSV. The dashboard reads the trades keyed by ISIN and folds commissions into the cash amounts; exports with multiple detail levels are de-duplicated automatically.

Kraken

On pro.kraken.com open History → Main, then use Export to create a statement of the Spot ledger for all time and download the generated CSV. The ledger export contains the paired trade rows, rewards, deposits and withdrawals the dashboard expects:

Binance

Open the Data Download Center (profile icon → Export data), set Data Type to Asset History → Transaction History, Coin All, Account All, choose your date range and generate the CSV. Large histories may take a while to prepare — Binance emails you a download link:

Trezor

In Trezor Suite, for each account: open Transaction overview, scroll down to Transactions, click the export icon on the right and choose Export as .csv:

When your history doesn't reach back far enough

Two things are always kept apart. How many units you hold today is known — a connected exchange states it, and the imported history is forced to end on exactly those numbers. When those units arrived, and what they cost, is inferred wherever the record does not contain the purchase. That inference is what you are looking at when the value chart shows a holding on a date you know you didn't own it.

Why the record is incomplete. No source hands over everything you ever did:

• An exchange API serves trades for a limited window back and no further. On one real Binance account it returns nothing before 14 September 2022 — while the same account's deposits, withdrawals and rewards reach back to its first day in 2017.
• A CSV export covers the date range you asked for, and nothing outside it.
• Coins held in an exchange's Earn, staking or locked products sit outside the spot account, so a spot statement never mentions them at all.

So a coin can be in your account today with no purchase anywhere in the record. Rather than drop it or invent a trade, the dashboard writes a correction — a bookkeeping row that credits the units and is flagged in the Portfolio warnings as an assumption. All that is left to decide is its date.

How an unexplained holding gets dated

1. The record mentions the coin at all — the missing units are dated the day before that coin's own first appearance. The coin's, not the account's: any row naming it — a transfer or a reward as much as a trade — is evidence you already held it then.
2. The record never mentions the coin — the units are dated at the last moment they could have arrived unseen: the day before the earliest trade the import can see. If the import's trades begin on 14 September 2022, a coin it never mentions is dated 13 September 2022.
3. The record contains no trades at all — then there is no window to be late to, and it falls back to the account's first day.

The principle is never to claim you held something for longer than the data can support. Units that appear from nowhere are dated as late as the rules allow. Units that vanish into nowhere — where your history implies more than the exchange says you hold — are written off as early as allowed. Both shrink the stretch of time the dashboard is guessing about.

Why it matters. 4 241 LUNC, bought for pocket money on 12 May 2022 as Terra collapsed, used to be dated to the account's opening in 2017. The chart then valued them as pre-crash Terra all the way up: a phantom 10.9 million CZK at the April 2022 peak, for a position worth about 6 CZK today. Dated by rule 2, the same coins can only be wrong by what they were worth over a few weeks.

What an API-only account's early years mean

Before the trade window opens, a connection can only see money moving in and out — never what you traded inside the account. That stretch of your chart is built from deposits, withdrawals and corrections: an approximation of what the account was worth, not a record of it. From the first day the trades reach, it is exact. An export covering the earlier years turns the approximation back into a record.

Closing the gap yourself

• Upload an export that covers the missing years. Once a file contains the purchase, rule 1 applies instead of rule 2 and the coin is dated from its real trade. The Portfolio warnings name the ranges you are missing, split into 12-month windows because that is what a Binance statement export answers at a time — a file starting August 2020 on an account whose first deposit was Christmas 2017 is three requests, and they are spelled out for you.
• Or add the purchase by hand. The Opening-balance lots card on the Taxes tab takes a symbol, a date, a quantity and a unit cost. What you enter there is a fact you supplied rather than an inference, so it wins over every rule above: your sells pair against the real purchase, at the real price, instead of against a lot dated and priced for you. (It is your cost basis it corrects — the quantities you hold still come from the exchange.)
• Some gaps no export can close. Coins in Earn, staking or locked products are outside the spot account a statement covers, so re-exporting will never produce them — the connection is the only thing that sees them, and the warning says so instead of asking you for a file.

Manual assets (what no export covers)

To track real estate, physical gold, collectibles or anything else without a CSV: scroll to Other assets at the end of ⚙ Settings → Data and enter a name, acquisition date, price, currency and an approximate yearly growth rate (APY — use a negative value for depreciating assets).

The asset joins the portfolio valued at its acquisition price compounded daily at that APY. It shows up as its own line under your accounts, as an "Other assets" allocation category and in the portfolio history. Each entry can be edited in place, excluded via its checkbox without deleting it, or removed via its ✕ (which strikes the row through — ↩ takes it back) — every one of these changes is staged and applies when you press Save.

Market-priced assets (search & add)

For a position in something Yahoo Finance can price — a stock, an ETF, crypto, an index fund, a future like gold — you don't need a broker export either: use the Market-priced assets search bar in ⚙ Settings → Data. Type a ticker, a company name or free text ("gold futures"), pick the listing from the results (symbol, name, exchange and type are shown for each), and give the quantity — fractions are fine. Clicking Add only stages the position: it appears as a pending row and joins the portfolio when you press the dialog's Save — the row's ✕ drops it before then, and closing without saving discards it.

The acquisition date and per-unit price are optional: an empty date means today, and an empty price is filled with the market close on the acquisition date, in the instrument's listing currency. Unlike a manual asset, a market-priced asset is then valued from live market data — it appears in the holdings table with real P/L against its cost, daily moves, portfolio weight and risk figures, joins Allocation and the portfolio history, and counts in Explore's "In portfolio" column, exactly like a holding from an uploaded export.

Each entry can be edited (quantity, date, price), excluded via its checkbox without deleting it, or removed via its ✕ (struck through until Save; ↩ takes it back) — like the adds, all of it staged until you press Save. The assistant chat can add these too — from plain text, an attached file or a brokerage screenshot.

Good to know

• Instrument matching is automatic. ISINs and broker tickers resolve to live Yahoo Finance symbols, with curated overrides for tricky cases; ISIN migrations collapse onto one position. Anything unresolvable is valued from its own trade prices and flagged "est." in the UI.
• Crypto specifics: stable coins are valued 1:1 in USD; crypto-to-crypto swaps at the counter-coin's price that day; renamed and redenominated tokens (LUNA→LUNC, MATIC→POL, old→new QUICK/STRAX) are handled so an old price never applies to a new quantity. A coin sold beyond your export window gets an assumed pre-existing balance and is flagged, since its cost is unknown — when your history doesn't reach back far enough explains how such a holding is dated.
• Degiro cash isn't tracked — the Degiro export contains no cash rows. Revolut cash is reconstructed from top-ups, withdrawals, trades and dividends.
• Quotes refresh automatically on a cadence you can set in ⚙ Settings → Data (default: every 10 minutes; the dialog also shows the last-updated time).