By Frido · Updated: 2 September 2026 · 6 min read

Exporting Your Bank Statement as CSV: Getting Hold of Your Own Data

Your transactions belong to you, and every bank in Germany hands them over. The route there is just rarely prominent. This article shows the pattern that works at practically any institution, and the four pitfalls that follow.

The general pattern

Per-bank click paths are deliberately absent here — online banking interfaces get rebuilt several times a year, and a walkthrough that was accurate last year will mislead you today. The pattern underneath is stable:

1. Log in through a browser, not the banking app. Many mobile apps lack the export entirely.
2. Open the transactions of the account you want — not the portfolio or card overview.
3. Set the period. Be generous: a few duplicate transactions are better than a gap.
4. Find the export function. Depending on the institution it reads “Export”, “Download”, “Umsatzliste speichern”, or hides behind a download icon above or below the transaction list.
5. Choose CSV as the format. PDF and CAMT are often offered too — PDF is for filing, CAMT is a payments-processing standard; for importing into a finance app, CSV is the usual route.

If you find nothing, the online banking search function with the word “Export” usually helps. Some institutions file it under “Umsatzanzeige” or in the account settings.

The four pitfalls

1. The period that no longer exists

How far back you can export is your bank’s decision — anywhere from 90 days to several years. People who start tracking their wealth two years in often find that the first months are simply no longer retrievable.

Consequence: export early and then regularly, even when you do not need the data. One file a month in a folder costs nothing and cannot be back-filled later.

2. Excel

The most common cause of a “broken” file is not the bank but the double-click. Open a CSV in a spreadsheet and save it again, and dates get rewritten, leading zeros vanish and the character encoding changes.

Consequence: download the file and pass it to your app unchanged. If you want to look inside, use a preview that saves nothing.

3. Separators, encoding, date format

German banks often separate with semicolons rather than commas, do not always deliver UTF-8 (which turns umlauts into gibberish) and write dates as DD.MM.YYYY. Amounts differ too: sometimes one field with a sign, sometimes separate debit and credit columns.

Consequence: this is not a fault, it is the normal state. A usable finance app recognises these variants — and lets you correct the mapping when it guesses wrong. That is exactly how you spot a good import.

4. The second import

The first time goes fine. It gets interesting in month two, when periods overlap. Without duplicate detection, every transaction then sits in the analysis twice, and every figure built on it is wrong.

Consequence: overlap the periods deliberately — but test first, with a small export, whether your app catches duplicates.

Portfolios export differently

Securities positions do not live in the current account’s transaction list. They usually have their own export in the portfolio view — and often a different format. Expect to handle them separately.

What happens next

Once the file is imported, the analysis does the rest: categories, recurring items, fixed costs, and out of those the budget and your wealth trend. The export is the only action that stays with you.

Whether that action is worth doing without an automatic connection is a trade-off — laid out in full in finance app without a bank connection.

Frequently asked questions

Where do I find the CSV export in online banking?

Almost always in the browser rather than the banking app, on the transactions view of the account in question. Depending on the institution the button reads “Export”, “Download”, “Umsatzliste speichern” or shows only a download icon. Pick a period there and CSV as the format.

How far back can I export transactions?

Your bank decides; anywhere between 90 days and several years is common. If you want a longer history, export early and regularly rather than trying later to reach a period the bank no longer keeps.

Why does my CSV look broken in Excel?

Usually the separator or the character encoding. German banks often separate with semicolons and do not always deliver UTF-8, which mangles umlauts. For importing into a finance app none of that matters — better not to open the file in Excel at all, and pass it on unchanged.

What is the difference between CSV and CAMT?

CSV is a simple table that every bank structures slightly differently. CAMT is a standardised XML format from payments processing. CSV is more widely supported and is the usual route into a finance app.

The interface is in German and I am not. Does that matter?

Not much. The export usually sits on the transactions view, and the German labels are worth knowing: “Umsätze” means transactions, “Zeitraum” means period, “Exportieren” or “Herunterladen” means export or download. Many banks also offer an English interface in the settings.

Read on

• Finance app without a bank connection: a deliberate choice
• Finance apps compared: what each category is built for

Sources

• Own survey of export routes in browser banking; as of September 2026. Per-institution click paths are deliberately not documented, because they change several times a year.