Trade Republic CSV export: the 2026 guide

For six years, the standard answer to “how do I get my data out of Trade Republic?” was: you don't — you scrape PDFs, install a browser extension, or type everything into a spreadsheet by hand. That answer is now wrong. In mid-April 2026, Trade Republic shipped a native CSV transaction export directly in the app. Most of the top-ranking guides on this topic were written before that release and still describe the workarounds. This guide describes the feature that actually exists, as of July 2026.

What changed in April 2026

With the app release of mid-April 2026 (version 4.2616.2 and later), Trade Republic added a Transaktionsexport — a transaction export — under the account-statements section of the profile menu. It produces a single CSV file covering both the securities account and the cash account: orders, savings-plan executions, dividends, interest, card payments, fees, deposits and withdrawals, including crypto transactions. You choose the period yourself — from one month to the full history since account opening. The release was covered by German finance blogs at the time, for example Aktiengram's write-up of 15 April 2026.

Why does this matter enough to lead with? Because the search results still disagree. Several widely read guides — last refreshed in early April 2026 or before — state that Trade Republic offers no export function at all and route readers to third-party browser extensions or aggregator sign-ups. If a guide tells you to install an extension before showing you the app's own menu path, it predates the feature. You no longer need any of that for a standard transaction history.

The direction of travel is no accident either. Under Article 20 GDPR, EU customers have the right to receive the data they provided to a service in a structured, commonly used, machine-readable format — and a transaction export is what that right looks like in everyday banking practice. The native export replaces the support-ticket detour with self-service.

Step by step: the native CSV export

The app's interface language follows your phone, but many long-time accounts run in German — so both label sets are given here. The path is identical on iOS and Android:

1. Open the Trade Republic app and tap your profile icon in the top-right corner.
2. Tap “Account statements” (German UI: Kontoauszüge).
3. Tap “Transaction export” (Transaktionsexport), then “Share” (Teilen).
4. Choose the period — a start and end date, or the maximum range for the complete history — then tap “Create” (Erstellen). The app generates the CSV, which you can download to the device or pass on via the share sheet — to your email, a cloud drive, or straight into another app.

There is no meaningful wait: even multi-year histories generate in seconds. The export is app-only as of July 2026 — the web interface at app.traderepublic.com shows your history but does not offer the CSV download itself.

What the CSV contains

The file is a plain UTF-8 CSV with one row per booking. Timestamps arrive in ISO 8601 (UTC). Each row carries a transaction type and subtype — a securities order, a savings-plan execution, a dividend, interest on cash, a card payment, a fee — plus the instrument, the quantity and execution price where applicable, the booked EUR amount, and, for non-EUR bookings, the original amount, its currency and the applied exchange rate. Order rows state the order type using the German nouns Kauf and Verkauf — that is, whether the row is an acquisition or a disposal.

If you want to look inside the file before importing it, open it with a plain-text editor or via a spreadsheet's import wizard rather than by double-clicking. The file is UTF-8 encoded; applications that assume a Windows encoding or German number formats can mangle umlauts, dates and decimal points on a direct open. The wizard route lets you set encoding and separator explicitly — and leaves the file itself untouched.

Known quirks

The export is genuinely useful but young, and the early adopters — chiefly the Portfolio Performance community, which built an import how-to within weeks — have mapped its edges. Five are worth knowing before you rely on the file:

• Dividend correction rows. Corrected dividend bookings appear as separate lines (a “cash dividend” row plus a “corrected” row). A tool that imports both without netting them can double-count the payment. Spot-check your dividend totals after import.
• FX detail can be thin. For securities denominated in other currencies, users report rows where the EUR amount is present but the exchange-rate detail is incomplete — some import tools then need the rate supplied manually.
• Fee rows are inconsistent. Card-related and withdrawal fees sometimes import as zero-amount lines or are skipped by import tools entirely. Reconcile fees against your PDF statements if precision matters to you.
• Savings-plan executions come row by row. Every execution is its own line. A three-year ETF savings plan means dozens of rows for one position — correct, but expect volume.
• Do not edit the file in Excel and re-save it. Excel happily rewrites encodings, date formats and decimal separators on save. If you want to look inside, work on a copy and keep the original for imports.

Three checks after the first import

An import is only as reliable as its reconciliation. Three checks, together about ten minutes of work against a second source:

1. Completeness. Do the first and last bookings in the file match the period you chose? If you exported the maximum range, does the file reach back to your account opening? A truncated period shows up immediately here.
2. Dividend totals. Compare the imported dividend total for one completed year against the PDF statements or the tax report for the same year. If it deviates, the correction rows from the section above are almost always the reason.
3. Position quantities. Recompute the share count per position from the imported rows and compare it with what the app currently shows. Differences point at corporate actions or skipped rows — both fixable once you know which position to look at.

The PDF route still exists

The older path has not gone away, and for some purposes it is still the right one. Under the same Kontoauszüge section the app provides monthly account statements as PDFs, per-trade settlement notes (Wertpapierabrechnungen), and the annual tax report (Steuerreport). These documents are the legally authoritative record of your account. The CSV is the machine-readable convenience layer on top; the PDFs are what you archive and what a tax preparer will ask for. If you need transaction data from before your chosen CSV period, or a format a third party will accept as evidence, the PDFs are the answer.

What to do with the file

A transaction CSV on its own is a list of rows. Its value appears when a portfolio tool reads it: then it becomes your cost basis per position, your dividend history, your fee total, your actual time-weighted return. Most established trackers — Portfolio Performance, Parqet and others — added support for the new format within weeks of the release, usually as a dedicated import profile you select when uploading the file.

The general recipe is the same everywhere: export the maximum period once, import it into the tool of your choice, check the three usual error sources (dividend corrections, FX rows, fees) against a PDF statement, and from then on export only the months since the last import. Acutic's CSV portfolio import works from a simple holdings template — symbol, share count, average cost — and the transaction export contains every number you need to fill it. More on the analysis that runs on top of an imported portfolio is on the features page.

FAQ

Transaction export or tax report — which one do I need? They answer different questions. The CSV transaction export is the complete, machine-readable booking history — built for spreadsheets and portfolio tools. The Steuerreport is the annual PDF summarising the tax figures German brokers must report — built for your tax filing. For tracking and analysis, use the CSV; for the tax return, use the report. (General information, not tax guidance.)

Can I export from the browser? As of July 2026, no — the export lives in the mobile app. The share sheet gets the file onto a computer in one step (email it to yourself or drop it into a cloud folder).

Are the column headers English or German? The file's field naming has varied between app versions; import tools handle both. Treat the field groups in the table above as stable and the exact labels as subject to change.

How far back does it go? To the beginning of your account. Choose the maximum period and the file covers every booking since opening.

How often do people re-export? The export does not sync itself; it is a snapshot. A common pattern is a monthly or quarterly export covering only the period since the last one, plus one archived full-history export. Keeping the originals unmodified preserves a provenance trail you can always re-import from scratch.

How large does the file get? Small. It is plain text; even a few thousand rows from years of savings-plan executions remain a file every tool opens instantly.

I cannot find the menu item — why? Check the app version first. The Transaktionsexport shipped with the mid-April 2026 release (4.2616.2); on an older version the entry under “Account statements” simply is not there yet, and it appears after an update. It also lives only in that section — there is no second path to it elsewhere in the app.

Further reading: the self-directed investor’s 2026 stack — where a broker export fits in the toolkit — and portfolio rules you actually keep — what a rules framework does with imported data. Create free account.

Acutic provides investment research and educational analysis under MAR Art. 20 / § 85 WpHG. Acutic does not provide investment advice (Anlageberatung per § 1 Abs. 1a S. 2 Nr. 1a KWG / Art. 4(1)(4) MiFID II), portfolio management, or any other licensed investment service. No content in this article constitutes a personal recommendation.