QBO, OFX, QFX: A Guide to Financial File Formats
If you work with bank data, you’ve seen these file extensions: .qbo, .ofx, .qfx, .qif. They all contain financial transactions, but each format was built for different software. Here’s what they are, how they differ, and when to use each one.
The Formats at a Glance
| Format | Full Name | Created By | Used By | File Type |
|---|---|---|---|---|
| OFX | Open Financial Exchange | Intuit, Microsoft, CheckFree (1997) | Many financial apps | XML |
| QBO | QuickBooks Web Connect | Intuit | QuickBooks Desktop & Online | XML (OFX variant) |
| QFX | Quicken Financial Exchange | Intuit | Quicken | XML (OFX variant) |
| QIF | Quicken Interchange Format | Intuit (1988) | Legacy Quicken, some tools | Plain text |
OFX — Open Financial Exchange
OFX is the open standard that started it all. Developed in 1997 by Intuit, Microsoft, and CheckFree, it was designed as a universal format for exchanging financial data between banks, financial institutions, and personal finance software.
Structure: XML-based. Each file contains a header with bank identification, followed by a list of transactions with dates, amounts, descriptions, and transaction types.
Who uses it: OFX is supported by a wide range of financial software — GnuCash, Moneydance, Microsoft Money (legacy), and many banking portals. It’s the most universal format in this list.
When to use it: When you need a format that works across multiple applications, or when your software doesn’t specifically require QBO or QFX.
QBO — QuickBooks Web Connect
QBO is Intuit’s proprietary version of OFX, tailored for QuickBooks. Technically, a QBO file is an OFX file with specific headers and formatting that QuickBooks expects.
Structure: Same XML/OFX structure, but with Intuit-specific headers (like the financial institution ID) that QuickBooks uses to identify the bank and match transactions.
Who uses it: QuickBooks Desktop and QuickBooks Online. This is what QuickBooks generates when you download transactions from your bank through the app, and it’s the format QuickBooks prefers for manual imports.
How to open it: In QuickBooks, go to File > Import > Web Connect Files and select the .qbo file. QuickBooks will ask you to map it to an account, then import the transactions.
When to use it: Whenever you’re importing bank transactions into QuickBooks. If you have a choice between OFX and QBO, use QBO — QuickBooks handles it more reliably because the format includes metadata QuickBooks expects.
QFX — Quicken Financial Exchange
QFX is to Quicken what QBO is to QuickBooks — Intuit’s version of OFX customized for the Quicken desktop application.
Structure: Again based on OFX, but with headers specific to Quicken’s import process.
Who uses it: Quicken (all versions — Starter, Deluxe, Premier, Home & Business).
When to use it: When importing transactions into Quicken. Most banks that offer download files for Quicken provide them in QFX format.
QIF — Quicken Interchange Format
QIF is the oldest format on this list, dating back to 1988. Unlike the XML-based formats above, QIF is a simple plain-text format.
Structure: Plain text with line prefixes indicating data type: D for date, T for amount, P for payee, L for category, and ^ as a record separator.
D03/10/2026
T-45.99
POffice Depot
LOffice Supplies
^
D03/09/2026
T-12.50
PStarbucks
LMeals
^
Who uses it: Older versions of Quicken, some legacy banking systems, and various import tools that support it as a fallback format.
When to use it: Generally, don’t — unless your software requires it. QIF lacks transaction IDs, which means duplicate detection doesn’t work well. Intuit officially deprecated QIF in favor of OFX/QFX years ago. Some tools still support it for backward compatibility.
Format Comparison
| Feature | OFX | QBO | QFX | QIF |
|---|---|---|---|---|
| File type | XML | XML | XML | Plain text |
| Transaction IDs | Yes | Yes | Yes | No |
| Duplicate detection | Yes | Yes | Yes | Unreliable |
| Bank identification | Yes | Yes (Intuit-specific) | Yes (Intuit-specific) | No |
| Balance information | Yes | Yes | Yes | No |
| Multi-currency | Yes | Limited | Limited | No |
| Software support | Wide | QuickBooks | Quicken | Legacy |
| Still maintained | Yes | Yes | Yes | Deprecated |
Which Format Should You Use?
- Importing into QuickBooks? Use QBO.
- Importing into Quicken? Use QFX.
- Importing into other financial software? Use OFX — it’s the most widely supported.
- Working with very old software? QIF as a last resort.
If your bank only provides CSV or PDF statements, you’ll need a tool to convert them into one of these formats before importing.
How Talio Creates These Files
Talio is a Google Sheets add-on that imports bank statements (PDF, CSV, XLSX) and exports them in any of these formats. The workflow:
- Import your bank statement into Google Sheets
- Review and clean the transaction data
- Tag and analyze using AI-powered multi-dimensional tagging and P&L reports
- Export clean transaction data as QBO, OFX, QFX, or CSV — one click
This is useful when your bank doesn’t offer direct downloads in the format your accounting software needs, or when you’re working with historical statements that aren’t available through bank feeds.
Get Started
Talio is a free Google Sheets add-on. Install it from the Google Workspace Marketplace and create your first QBO file from any bank statement.
Page bundles start at $29.99 for 60 pages. No subscription.
Questions? Book a free 15-minute call or email talio@fastforward.nl.