Importing from Degiro

Download your Degiro transactions as a CSV file and import them to build your portfolio records.

Last reviewed

Downloading your data from Degiro

Download your transactions as a CSV file for your trade history. Dividends, fees and cash movements are not part of that list; for those, also download the account statement for the same dates.

What to look for

  1. Sign in to Degiro in a web browser
  2. Look for the Activity menu, then Transactions
  3. Set the start and end dates to cover the period you want
  4. Look for an Export option and choose CSV
  5. For dividends and fees, look for Account statement under the same menu and export it as CSV too
Steps written on 17 October 2026 and not checked against a live Degiro account, so they say what to look for rather than which button to press.

How your file is read

There is no dedicated Degiro reader yet. Your file is first checked against the brokers we do have readers for and then, when none matches, read by AI extraction on our own servers, which works out what each column means. Your financial documents never leave our servers without your approval.

You check every row in the review step before anything is saved, and the review step offers “Fix column mapping” if a column was read as the wrong thing. See importing from another broker for how AI extraction works.

Step-by-step import

  1. Open Import statements in the sidebar, under Estate & assets → Portfolio
  2. Upload the transactions CSV first
  3. Review the rows, fix the column mapping if needed, and confirm
  4. Upload the account statement CSV the same way for dividends

Screenshot, for illustration only

The broker statement importer on the first of its three steps, upload, review and confirm, asking what kind of statement is being imported, whose it is and which account it belongs toThe broker statement importer on the first of its three steps, upload, review and confirm, asking what kind of statement is being imported, whose it is and which account it belongs to
The broker statement importer on the first of its three steps, upload, review and confirm, asking what kind of statement is being imported, whose it is and which account it belongs toThe broker statement importer on the first of its three steps, upload, review and confirm, asking what kind of statement is being imported, whose it is and which account it belongs to
The importer on its first step, upload, where you say what kind of statement it is, whose it is and which account it belongs to.

Cost line-item extraction

Because the file is read by AI rather than a dedicated reader, check each trade’s costs in the review step: transaction and exchange fees can sit in their own columns or in the account statement.

See Understanding investment costs (opens in a new tab) for how each cost affects cost basis in each supported jurisdiction.

Common issues

Semicolons and decimal commas

Depending on your language setting, a Degiro CSV can separate fields with semicolons and write numbers with a decimal comma. Both are recognised; see Number and date formats below for how numbers are read.

Several currencies

Degiro trades on many exchanges, so one file can hold several currencies. Each row keeps its own currency; see Currencies below.

Before you import

AI reading: there is no dedicated Degiro reader, so your file is read by AI document reading on our own servers. You check every row in the review step before anything is saved.

These parts of the Statement import guide apply to every broker:

Related pages

Can’t find what you’re looking for?

Our support team is here to help. Contact us and we’ll get back to you as soon as possible.

Contact us

We use cookies to improve your experience. See our Cookie policy (opens in a new tab) for details.