If you've ever opened your bank's export menu and seen an option called OFX sitting next to CSV and PDF, it's easy to skip past it without knowing it's usually the best one to pick. Open Financial Exchange (OFX) is a file format purpose-built for moving transaction data between banks and personal finance software - which means it tends to import more cleanly, with fewer surprises, than anything meant to be read by a human first.
What "Open Financial Exchange" actually means
Open Financial Exchange is a data-exchange specification, not a product - it was created in the late 1990s by Intuit, Microsoft, and CheckFree specifically so banks could send account and transaction data to personal finance software in one agreed-upon shape, instead of every bank inventing its own layout.
That's the key difference from a format like CSV: a CSV export is just rows and columns, and every bank arranges those columns differently. An OFX file follows a fixed structure - defined fields for transaction date, amount, type, payee, and a unique transaction ID - so software built to read OFX can recognize any bank's file without being taught that bank's particular layout first.
You'll also see QFX mentioned alongside it. QFX is Intuit's own branded variant of OFX, used mainly for Quicken and QuickBooks - functionally almost identical, and treated the same way on import by software that supports OFX.
What's actually inside an OFX file
An OFX file is structured text (modern versions are XML-based), built around a few key elements for every transaction:
- A transaction type - a deposit, withdrawal, card payment, transfer, or similar, marked explicitly rather than guessed from the description
- The posted date and the amount, as clean machine-readable values rather than text that needs to be parsed from a sentence or a table cell
- A payee or memo field describing who the transaction was with or what it was for
- A unique transaction ID (FITID) that your bank assigns once and never reuses - this is what lets finance software recognize a transaction it has already imported and skip it automatically on your next import
- Account-level details - account number, routing or sort code, and statement balance - carried in the same file as the transactions themselves
Why that unique transaction ID matters more than it sounds
The FITID is the detail that quietly makes OFX worth choosing over CSV or PDF when it's available. Since every transaction carries a bank-assigned ID that never changes, software can tell the difference between "a new transaction" and "a transaction I've already seen" without comparing dates, amounts, and descriptions and hoping nothing matches by coincidence.
With CSV or PDF, duplicate detection has to rely on that kind of fuzzy matching, which occasionally gets it wrong - two separate $12.00 coffee purchases on the same day can look identical. OFX sidesteps the problem entirely, which is part of why it's treated as one of the formats that imports automatically, with no bank-specific setup step.
Which banks offer it, and where to find it
OFX export is common among larger banks and credit unions, usually sitting in the same export menu as CSV and PDF on your statements or transaction history page - sometimes labeled "OFX," sometimes "Quicken (QFX)," and occasionally "Money (OFX)." Any of those work the same way.
If your bank doesn't offer OFX at all, that's not a dead end - CSV works just as well once its column layout is mapped, and that mapping only has to happen once per bank.
Common questions about OFX files
Is OFX the same as QFX?
Almost. QFX is Intuit's own variant of the OFX standard, created for Quicken and QuickBooks. The underlying structure is close enough that software built to read OFX can read QFX too - you don't need to convert between them.
Is an OFX file safe to download and import?
Yes - it's a plain data file, not an executable, and it only ever contains the transaction data your bank already shows you in your account. Download it the same way you would a CSV or PDF statement, directly from your bank's own site.
Can I convert a PDF statement to OFX?
Not reliably on your own - a PDF has no structured data to extract, only a printed layout. If your bank doesn't offer OFX or CSV, the practical path is importing the PDF directly with software that includes a parser built for that bank's specific statement layout.
Why did my OFX import show zero new transactions?
That usually means it worked correctly - if every transaction in the file carries an FITID your software has already seen, it's recognizing them as duplicates on purpose rather than failing to import them. Downloading an OFX file for a date range you've already imported will look like this every time.
See whether your bank's OFX export is supported
Check the full list of automatically recognized formats and banks, or start a free trial and import your first OFX file in under a minute.
Check supported formats