Loading converter...
Loading converter...
A technical guide to QBO and OFX file formats, their structure, and key differences from IIF.
OFX (Open Financial Exchange) is an open standard format for exchanging financial data between financial institutions and financial software. It was developed jointly by Microsoft, Intuit®, and CheckFree in 1997.
OFX files are XML-based and can contain bank statements, credit card transactions, investment portfolio data, and bill payment information. The format is widely supported by banks worldwide and is the foundation for QuickBooks® Web Connect functionality.
Key Point: OFX is an industry standard, not proprietary to any single company. This makes it the most widely supported format for financial data exchange.
QBO files are essentially OFX files with Intuit®-specific headers and formatting. The "QBO" extension stands for QuickBooks® Online, though these files work with both QuickBooks® Online and Desktop versions.
When you download transactions from your bank using the "QuickBooks®" or "Web Connect" option, you typically receive a QBO file. Inside, it contains the same OFX XML structure with additional Intuit® metadata.
.qboapplication/vnd.intu.qbo| Aspect | QBO | OFX | QFX |
|---|---|---|---|
| Full Name | QuickBooks® Online | Open Financial Exchange | Quicken Financial Exchange |
| Developer | Intuit® | Industry Consortium | Intuit® (for Quicken) |
| Structure | OFX + Intuit® headers | Standard XML | OFX + Quicken headers |
| QuickBooks® | Native support | Supported | Partial support |
| Primary Use | QuickBooks® Web Connect | Universal exchange | Quicken software |
Our Converter: We support all three formats (QBO, OFX, QFX) since they share the same underlying structure.
OFX and QBO files use an SGML/XML structure. Here's a simplified view of a typical bank statement:
<?xml version="1.0" encoding="UTF-8"?>
<OFX>
<SIGNONMSGSRSV1>
<SONRS>
<STATUS><CODE>0</CODE></STATUS>
<DTSERVER>20240115</DTSERVER>
<LANGUAGE>ENG</LANGUAGE>
</SONRS>
</SIGNONMSGSRSV1>
<BANKMSGSRSV1>
<STMTTRNRS>
<STMTRS>
<CURDEF>USD</CURDEF>
<BANKACCTFROM>
<BANKID>123456789</BANKID>
<ACCTID>987654321</ACCTID>
<ACCTTYPE>CHECKING</ACCTTYPE>
</BANKACCTFROM>
<BANKTRANLIST>
<DTSTART>20240101</DTSTART>
<DTEND>20240131</DTEND>
<STMTTRN>
<TRNTYPE>DEBIT</TRNTYPE>
<DTPOSTED>20240115</DTPOSTED>
<TRNAMT>-150.00</TRNAMT>
<FITID>202401150001</FITID>
<MEMO>Office Supplies Store</MEMO>
</STMTTRN>
</BANKTRANLIST>
</STMTRS>
</STMTTRNRS>
</BANKMSGSRSV1>
</OFX>Each transaction in an OFX/QBO file contains these key elements:
| Element | Description | Example |
|---|---|---|
| TRNTYPE | Transaction type (DEBIT, CREDIT, etc.) | DEBIT |
| DTPOSTED | Date posted in YYYYMMDD format | 20240115 |
| TRNAMT | Transaction amount (negative for debits) | -150.00 |
| FITID | Financial institution transaction ID | 202401150001 |
| MEMO | Transaction description/memo | Office Supplies |
| CHECKNUM | Check number (if applicable) | 1234 |
| NAME | Payee name | Acme Corp |
While QBO files can be imported directly into QuickBooks®, there are several reasons to convert to IIF:
Specify exact account names before import, rather than relying on QuickBooks®' auto-matching
Assign expense categories before import, saving time on post-import categorization
Some older QuickBooks® Desktop versions have better IIF support than QBO
Edit the IIF file in a text editor or spreadsheet before import
IIF is human-readable plain text, making it easy to verify data before import
Try our free QBO to IIF converter now. Just create a quick free account to get started.
Start Converting Free