Pick the app the file came from
- Venmo statementVenmo CSV to OFX
- PayPal activity downloadPayPal CSV to OFX
- Stripe balance transactionsStripe CSV to OFX
- Wise balance statement CSVWise CSV to OFX
- MT940 bank statementConvert an MT940 file to OFX
- camt.053 bank statement (ISO 20022 XML)Convert a camt.053 file to OFX
From a bank CSV
Bank CSV exports differ from bank to bank: some use one signed amount, some separate debit and credit columns, dates may be day-first or month-first, and many add header or total rows. Choose "Bank CSV" as the source (it is picked automatically when the file is not from a known app).
- In your online banking, find Download or Export transactions.
- Choose CSV (sometimes called Excel CSV or Comma separated).
- Pick the date range and download.
- We look for the header row even if the file starts with account details.
- We map Date, Description and Amount, or separate Debit and Credit columns, automatically, and show the result in the preview.
- We work out whether dates are month/day or day/month and whether "," or "." is the decimal point from the file itself; when the file cannot tell, we ask you instead of guessing. Dotted dates (31.01.2025) are read day first.
- Card exports that show purchases as positive numbers can be flipped with the "invert sign" option.
What Xero, Wave, GnuCash, Moneydance, MS Money and others requires
- Plain OFX 1.0.2 SGML with no Intuit extensions.
- One account and one currency per file.
- Stable transaction ids: the same row in two overlapping exports gets the same id.
How to import it
- In your accounting software open the bank account and choose Import statement (or File > Import > OFX).
- Choose this .ofx file.
- Review and confirm the transactions.
Questions
- Which programs accept OFX files?
- Xero, Wave, GnuCash, Moneydance and many desktop finance programs offer an OFX import. QuickBooks prefers .qbo and Quicken prefers .qfx; use those variants for Intuit products.
- What happens with overlapping exports or repeated rows?
- Each transaction gets an id built from its date, amount, description and platform id, so the same row in two overlapping exports gets the same id. Whether your software uses that id to skip a repeat is up to the software, so avoiding overlapping date ranges is still the safest habit. Within one file, exact repeats of the same platform transaction are dropped and the notes say how many.