OFX, CSV, and QIF: Which Bank Statement Export Format Should You Use?
When a bank offers data downloads, you typically see several format options: CSV, OFX, QIF, QFX, QBO. The names look similar, and the underlying data is the same, but the formats behave very differently depending on where you are importing. Picking the right one saves a meaningful amount of cleanup time.
CSV (Comma-Separated Values)
CSV is a plain text file where each row is a transaction and values are separated by commas. Every spreadsheet, database, and accounting tool can read it. Nothing about the format is specific to finance.
That universality is also the limitation. CSV has no financial metadata. There are no account identifiers, no institution codes, and no transaction IDs. Import the same CSV file twice and you get duplicate transactions, because the system has no way to recognize that it has seen those rows before. Most accounting tools also require you to map columns manually on import (matching your file's Date column to their Date field, and so on), which adds a step to every upload.
CSV is the right choice for: Excel, Google Sheets, Power BI, any data analysis workflow, and accounting tools that do not natively support a financial format.
OFX (Open Financial Exchange)
OFX was developed by a consortium that included CheckFree Corporation, Intuit, and Microsoft. The consortium announced the format in January 1997 and published the first specification (version 1.0) in February 1997. The standard is currently maintained by the Financial Data Exchange (FDX). OFX 1.x uses an SGML-based format. OFX 2.x, released in June 2000, moved the body to XML while keeping an SGML-compatible header.
The key feature of OFX is the FITID (Financial Institution Transaction ID). Every transaction in an OFX file carries a unique ID assigned by the bank. When you import an OFX file into an accounting tool that supports it, the software stores those IDs and uses them to block duplicate imports. Import the same file twice, and the system recognizes the FITIDs and skips the rows already in the system.
OFX also contains account metadata: institution name, account number, account type, and statement period. This context travels with the file and reduces the chance of importing data into the wrong account.
OFX is the right choice for: Xero (which accepts OFX natively with no column mapping), Quicken, and any tool that documents OFX support.
QBO and QFX: Intuit's OFX variants
Both QBO and QFX are based on OFX but with Intuit-specific extensions.
QBO (.qbo) is the QuickBooks Online import format. It uses OFX syntax, but QuickBooks requires the file to be labeled as a QBO file to recognize it. When you upload a .qbo file through Transactions > Bank Transactions > File Upload in QuickBooks Online, no column mapping is needed. The import reads the OFX structure directly and maps everything automatically.
QFX (.qfx) is Quicken Financial Exchange, Intuit's variant for Quicken software. It adds a proprietary element for bank identification. QFX is only officially supported by Quicken products.
QIF (Quicken Interchange Format)
QIF was developed by Intuit in the early 1990s. It is a text-based format that uses single-character field prefixes: D for date, T for amount, P for payee, M for memo, and a caret (^) to mark the end of each record.
QIF has no transaction IDs, so there is no built-in deduplication. Import the same QIF file twice and you get duplicates, just as with CSV. The format is also ambiguous about date formats (MM/DD/YYYY vs DD/MM/YYYY), which can cause import errors when regional settings do not match.
QIF is still supported by Quicken, some versions of Xero, and a number of credit unions and smaller banks that have not updated their export options. It is the right choice only when the tool you are importing into accepts nothing else, or when a bank offers it as its only structured export format.
Which format to use for each tool
| Destination | Best format | Notes |
|---|---|---|
| QuickBooks Online | QBO | Direct upload, no column mapping |
| Xero | OFX | No column mapping; also accepts QIF and CSV |
| Quicken | QFX | Native format for Quicken desktop |
| Wave | CSV | Only accepts CSV |
| FreshBooks | CSV | Only accepts CSV |
| Excel / Google Sheets | CSV | Universal; no financial metadata needed |
When you are converting from PDF
When you convert a bank statement PDF using a tool like Statement Pro, you can choose your output format. Choose OFX or QBO when your destination is an accounting tool. Choose CSV when your destination is a spreadsheet or a tool that only accepts CSV.
If you are unsure, CSV is the safe default. It works everywhere, and the only cost is a column mapping step on import and no deduplication protection. For recurring workflows where you import the same account each month, OFX or QBO is worth the slight additional setup because deduplication prevents data quality problems from a mistaken duplicate import.
FAQ
Can I convert a QIF file to OFX?
Not directly with most tools. If you need OFX output, convert the original source PDF to OFX rather than trying to convert between output formats.
Does OFX work with both Xero and QuickBooks?
Standard OFX works with Xero. QuickBooks Online requires the QBO variant. They use the same underlying structure but different file extensions and minor format differences that matter to the import system.
Is OFX more accurate than CSV?
The underlying transaction data is the same. OFX is more reliable in practice because it eliminates the column mapping step (reducing human error) and provides deduplication through FITIDs.