How to Export Your Transaction History from Trading 212

Trading 212 builds its CSV from the boxes you tick, and only one of them carries your buying history. Leave Orders unticked and you still get a file. It can list your deposits and dividends, and it holds not one purchase or sale.

This guide gets you the right file over the right period. It covers the CSV that the Trading 212 app exports from a share account, with English column headings. The CFD account has a separate export, which this guide does not cover.

Which Trading 212 file do you need?

You need the trading data export from History, with Orders ticked. Each order row carries the date, the number of shares, the price per share and the currency of that price. Those are the columns that produce a real cost basis and a yield on cost (your annual dividend measured against what you paid, rather than against today's price).

Trading 212 offers several other files, and some of them sound closer to what you want:

• Account activity statement is a PDF confirmation of recently executed trades. It is laid out for reading, not for importing.
• Transaction statement covers deposits, withdrawals and account value. It is a cash record, not a history of your trades.
• Confirmation of holdings lists the positions you hold today. It is a snapshot of one day, with no purchase history behind it.
• Pie info export starts when you press and hold the Holdings pie chart. It describes your Pie, not your trading history.

The three statements live under Documents in the menu. The export you want lives under History, so if you find yourself in Documents, go back one screen.

Step 1: Open the menu, then History

In the Trading 212 app, tap the menu icon (☰), then choose History.

Step 2: Press the export button

On the History screen, press the export button. Trading 212 then asks for two things: the timeframe, and which data to include. Both matter, and the next two steps take them in turn.

Step 3: Set the timeframe back before your first trade

This is the step that quietly breaks an import. A timeframe that starts after your first purchase gives you a file with your recent sales and none of the purchases behind them. Nothing has to go wrong for this to happen. The file can import without a single error and still produce a cost basis that is wrong.

Set the start of the timeframe before the day you opened the account, and leave the end on today. An export that starts too early costs you nothing. One that starts too late costs you your cost basis.

If the app will not cover your whole history in one file, export it in consecutive periods. Keep each file exactly as it downloads, and upload them one at a time rather than merging them in a spreadsheet first. An overlap between two periods is usually fine: a trade whose Trading 212 ID is already in this portfolio is skipped. Check the counts afterwards all the same.

Step 4: Tick Orders

Trading 212 lets you choose which data goes into the file, such as orders, transactions and dividends. Tick Orders. It is the choice that puts your buys and sells in the file, and without it there is nothing for the import to turn into purchases.

Ticking the others as well is fine. We read the buys and the sells and skip the other rows.

The file without Orders is not hypothetical. We have been sent it, which is why the import now recognises it and says so in plain words: "This Trading 212 export has no Orders in it. Export again with Orders ticked, and the trades will be here." If you see that message, nothing is wrong with your account. Go back to step 2 and tick the box.

Step 5: Keep the file exactly as it downloaded

The CSV lands on your device. Trading 212's own help page suggests opening it in a spreadsheet such as Excel or Google Sheets. Looking at it there is fine. Saving it from there is the risk.

The import reads dates in the form Trading 212 writes them, year first (2026-03-14, then a time). A spreadsheet set to a European locale can save them back as 14-3-2026, and it may change the character that separates the columns as well. A date the import can no longer read is rejected, and a changed number may not be caught at all. Upload the file Trading 212 gave you, untouched.

Check you got the right one

To be sure before you upload, open the file in a preview, or in a text editor you close without saving. The first line lists the column headings, in English, which is what the import reads. An export with Orders has all of these among them, in whatever order:

Older exports spell two of these slightly differently: Time without the (UTC), and a lower-case p in the currency heading. Both versions import.

In a file exported without Orders, no row in the Action column is a buy or a sell, and the No. of shares column may be missing altogether. If that is what you see, go back to step 4.

Step 6: Drop it into DividendAtlas

Open the import panel and drag the file onto it, or click to pick it from your downloads folder. We recognise a Trading 212 export from its contents, so you should not need to choose a broker or match columns. A trade whose Trading 212 ID is already in this portfolio is skipped. A trade you entered by hand, or imported into another portfolio, is not recognised, so check the counts afterwards.

What does the import bring in, and what does it leave out?

It brings in market and limit buys and sells, each with its date, quantity, price and currency. A row can still be rejected, for example when its date cannot be read. It can also stay unmatched when we cannot tell which security it is.

Each holding the import matches then shows the dividend history and forward income we hold for it. It also shows its Dividend Health Score where we publish one, and some stocks have no score for reasons that post explains.

The import leaves out four kinds of row, and it is better to know that now than to find a gap later:

• Trading 212's own dividend and withholding-tax rows. The file can carry them, but for Trading 212 we do not yet record them as payments received. We would rather say so here than let you assume your broker's cash record has been reconciled.
• Order types other than market and limit. Any other kind of row is left out rather than guessed at.
• Deposits, withdrawals and other cash movements. They change your cash balance, not your shares.
• Shares that arrived without a buy, such as a transfer from another broker. There is no order row behind them, so there is nothing to import. If you want them in this portfolio, add the original purchases by hand, with their original dates, quantities and prices where you have them, and check they are not already here from another broker's file.

What if the result does not look right?

• Sales with no matching purchases. Usually the timeframe started too late, so export again from before your first trade and upload the new file. Shares that arrived by transfer cause it too, because they are not booked.
• A holding you expected is missing. Check whether those shares came in by transfer rather than by a buy. If they did, add the purchase by hand, unless another broker's import already put it in this portfolio.
• Some rows were not imported. The import result says how many and why. Do not edit the file to swap an unfamiliar ISIN for a ticker you guessed, because a wrong match is worse than a missing one.
• The file will not upload at all. Check that it is the CSV and not a PDF or a workbook. Renaming a file does not convert it.

Using other brokers too? Where to find your transaction history names the file to take from each broker we import. The guides for DeGiro, Interactive Brokers, Saxo, Trade Republic, Lightyear, Revolut and Nordnet cover theirs step by step.

New to this and want the wider picture first? Start with a beginner's guide to dividend investing in Europe, or read how a dividend health score is calculated before you rely on one.