My bank’s CSV uses semicolons and decimal commas. Can you read it?

Yes. The delimiter (comma, semicolon, tab, or pipe) is sniffed per file, and amounts written the continental-European way ("1.500,00") are detected and parsed correctly. Ambiguous files stay conservative rather than guessing.

Is the output safe to open in Excel?

Yes, deliberately. Descriptions come off a statement — text a counterparty chose — so every cell that could start a formula is neutralized before it is written. A malicious "=HYPERLINK(…)" in a transaction description stays text instead of executing.

What columns do I get?

Date, Description, Category, Direction, a single signed Amount (money out negative, money in positive), and Currency. Fields containing commas, quotes, or newlines are quoted per RFC 4180.

Bank Statement to CSV — RFC 4180 Converter

Any bank statement, as clean CSV.