N26 statement to Excel
N26 gives you a CSV with more columns than most banks — payee, account number, transaction type and payment reference — and a PDF that prints far fewer. The CSV path keeps all of it; the PDF path reconstructs what it can.
What the CSV export contains
One row per transaction, with the reference kept in its own column instead of buried in the description.
| CSV column | What it holds | Kept in the sheet |
|---|---|---|
| Date | Booking date, ISO format | Yes |
| Payee | Merchant or counterparty | Yes |
| Payment reference | Your note or transfer reference | Yes |
| Amount | Signed amount in account currency | Yes |
| Amount (Foreign Currency) | Original currency amount | No — informational |
| Type | Card payment, transfer, direct debit | Optional column |
Why the CSV is the better input
The PDF export collapses the reference into the description and drops the foreign amount column. If you have the CSV, upload it: nothing needs reconstructing and there are no wrapped rows to repair.
Pending authorisations
If your export includes card authorisations that have not settled, they appear as ordinary rows. Remove them before you reconcile, otherwise the balance will not tie to your statement closing figure.
Questions
Which N26 export should I use?
CSV first, PDF as the fallback. The CSV carries the reference column and the original currency amount that the PDF drops.
Are foreign currency purchases converted?
Rows stay in your account currency, which is what your statement settles in. The original amount is informational and is not used in the totals.
Does it work for N26 Business?
Yes. Business exports use the same column set, with counterparty details in the payee and reference columns.
Other banks
Try it on your own statement
No account, no card, no email. Convert one file and check the rows against the original.
Open the converter