What's inside an OFX file
Open Financial Exchange was created in the late 1990s so banks could send statements to personal finance and accounting software in one agreed format. An OFX file is plain text. It starts with a header that states the version, then a sign-on block, then one or more statements. Each transaction is a STMTTRN block with a type, a posting date, an amount, a unique ID and a payee name.
That structure is great for software and awkward for people. Converting to CSV turns each STMTTRN into a row so you can read, sort and total the transactions.
How the conversion handles OFX quirks
- Unclosed tags (OFX 1.x): values run until the next tag, and empty tags such as a blank
<MEMO>don't swallow the following fields. - Dates with time zones: values like
20260115120000.000[-5:EST]are read as the calendar date the bank intended, January 15, with no shift from your own time zone. - Encoded characters:
&becomes "&" again, so "AT&T" reads correctly. - Long payee names: OFX 1.x limits
NAMEto 32 characters. When the full name is in the memo, the full version is used. - Credit cards: statements in a
CCSTMTRSsection are labeled as credit card accounts, and money spent stays negative.
Using the CSV in a spreadsheet
The CSV opens directly in Excel, Google Sheets or Numbers. Dates are written as MM/DD/YYYY and amounts as plain numbers, so formulas work straight away. If you plan to work in Excel, choose the Excel download: dates and amounts arrive as typed cells, there's an autofilter on the header row, and a Summary sheet totals money in and money out.
A quick check before you rely on the numbers:
- Compare the number of transactions with your online banking for the same period.
- Check that the ending balance in the summary matches the bank's statement.
- Keep the Transaction ID column. It's the bank's own identifier and the easiest way to find duplicates if you later combine several downloads.
Need QBO instead of CSV?
If you want to import an OFX file into QuickBooks and it's being refused, the issue is almost always the missing Intuit tags rather than the transactions. Converting OFX to QBO rewrites the file in the Web Connect format QuickBooks expects, with a valid header, the INTU.BID tag and unique transaction IDs.