Convert N26 Bank Statement PDF to OFX

N26 CSV activity report or monthly PDF?

N26 offers monthly balance statements as PDF and custom-date account activity reports as PDF or CSV. If you need spreadsheet rows, try its native CSV first. On the web, choose the account or Space, open Downloads, then choose the period under Account Activity. The official N26 statement guide covers these options.

Use PDF conversion when you are working from a monthly PDF or cannot obtain the needed CSV. Keep each account or Space separate during review. Match the IBAN/account and period to the source document; check transfers between your own accounts before combining rows, so internal transfers are not mistaken for new income.

Compare the first and last transaction dates, debit and credit direction, and closing balance. See the illustrative Excel output and reconciliation example before using the workbook. This guide does not certify every N26 statement layout.

Review the PDF before exporting

1. Use the original digital PDF and unlock it before uploading. Include all transaction pages.
2. Check extracted dates, descriptions and debit/credit amounts against the PDF. Compare totals and balances rather than assuming a completed conversion is correct.
3. Choose OFX only if the destination accepts it. Review the account, currency and date range before importing.

What to check in the OFX file

• Signs: TRNAMT is negative for a debit and positive for a credit. For example, a synthetic debit of 125.50 becomes -125.50; a synthetic credit of 1000.00 becomes 1000.00. Check these against actual money out and money in.
• Dates: DTPOSTED uses YYYYMMDD. Confirm ambiguous dates and missing years in the preview. The exporter can fall back to the current date when a date cannot be parsed: resolve warnings before importing.
• Account and currency: CURDEF is USD; ACCTTYPE is CHECKING; BANKID is 999999 and ACCTID is 999999999. These are placeholders, not extracted bank details. Use another export if your importer cannot resolve a mismatch safely.
• Balances: LEDGERBAL contains 0.00, not the statement's verified closing balance. Reconcile against the original PDF.
• Overlapping transactions: FITID is generated from transaction fields and row position. It is not a bank transaction ID. Compare overlapping statements and feeds manually.
• Descriptions: NAME is limited to 32 characters; longer descriptions also go into MEMO. Check how the destination displays references.

These examples describe the exporter, not a live bank-to-accounting import test. We have not certified a Capitec or Barclays OFX import. See Excel review examples or Xero CSV mapping.

Frequently asked questions