Loading converter...
Loading converter...
QBO (QuickBooks® Web Connect) is an XML-based file format built on the OFX standard, used to import bank and credit card transactions into QuickBooks® Desktop, QuickBooks® Online, and Quicken.
QBO files are the most widely accepted format for importing bank transactions into QuickBooks®. The format is based on the Open Financial Exchange (OFX) specification, an XML standard originally developed by Microsoft, Intuit®, and CheckFree in the late 1990s. When a bank offers a "Web Connect" download for QuickBooks®, the resulting file is a QBO file.
Unlike IIF files, which are tab-delimited text files designed for QuickBooks® Desktop only, QBO files use structured XML that can be read by multiple financial applications. This makes QBO the go-to format for users who need to bring bank statement data into their accounting software without manual entry.
The QBO format carries more than just transaction data. Each file includes financial institution identification, account information, date ranges, and a running balance. QuickBooks® uses this metadata to match the import to the correct bank account and prevent duplicate transactions from being imported.
Because QBO is built on OFX, it benefits from the same broad ecosystem support. Over 7,000 financial institutions worldwide generate OFX-compatible feeds, and any application that understands OFX can parse a QBO file with minimal adjustment. The only meaningful difference between a .qbo file and a .ofx file is the file extension itself — QuickBooks® specifically looks for the .qbo extension when using the Web Connect import workflow.
QBO files use well-formed XML markup, making them structured, self-describing, and easy for software to parse without ambiguity.
Built on Open Financial Exchange (OFX), the industry standard maintained by a consortium of banks and financial software vendors since 1997.
Works with QuickBooks® Desktop (Pro, Premier, Enterprise), QuickBooks® Online, and Quicken — no other single format covers all three.
Designed specifically for importing bank and credit card transactions with full metadata including dates, amounts, payees, check numbers, and memo fields.
A QBO file is structured XML following the OFX specification. It contains headers identifying the format version, a sign-on response, and the bank statement data itself. Here is a simplified example showing the core elements:
<?xml version="1.0" encoding="UTF-8"?>
<?OFX OFXHEADER="200" VERSION="220"
SECURITY="NONE" OLDFILEUID="NONE"
NEWFILEUID="NONE"?>
<OFX>
<SIGNONMSGSRSV1>
<SONRS>
<STATUS><CODE>0</CODE><SEVERITY>INFO</SEVERITY></STATUS>
<DTSERVER>20260215120000</DTSERVER>
<LANGUAGE>ENG</LANGUAGE>
<FI>
<ORG>MyBank</ORG>
<FID>12345</FID>
</FI>
</SONRS>
</SIGNONMSGSRSV1>
<BANKMSGSRSV1>
<STMTTRNRS>
<TRNUID>0</TRNUID>
<STATUS><CODE>0</CODE><SEVERITY>INFO</SEVERITY></STATUS>
<STMTRS>
<CURDEF>USD</CURDEF>
<BANKACCTFROM>
<BANKID>999888777</BANKID>
<ACCTID>123456789</ACCTID>
<ACCTTYPE>CHECKING</ACCTTYPE>
</BANKACCTFROM>
<BANKTRANLIST>
<DTSTART>20260201</DTSTART>
<DTEND>20260215</DTEND>
<STMTTRN>
<TRNTYPE>DEBIT</TRNTYPE>
<DTPOSTED>20260203</DTPOSTED>
<TRNAMT>-45.99</TRNAMT>
<FITID>20260203001</FITID>
<NAME>Office Supply Store</NAME>
</STMTTRN>
<STMTTRN>
<TRNTYPE>CREDIT</TRNTYPE>
<DTPOSTED>20260210</DTPOSTED>
<TRNAMT>1500.00</TRNAMT>
<FITID>20260210001</FITID>
<NAME>Client Payment - Invoice 1042</NAME>
</STMTTRN>
</BANKTRANLIST>
<LEDGERBAL>
<BALAMT>8234.56</BALAMT>
<DTASOF>20260215</DTASOF>
</LEDGERBAL>
</STMTRS>
</STMTTRNRS>
</BANKMSGSRSV1>
</OFX>Key elements: The BANKACCTFROM block identifies the bank and account. Each STMTTRN element represents one transaction with a unique FITID that QuickBooks® uses to prevent duplicate imports.
When you import a QBO file into QuickBooks®, the software reads the financial institution ID and account number to match it against your existing bank accounts. If no match is found, QuickBooks® prompts you to select or create the target account.
Each transaction's FITID (Financial Institution Transaction ID) acts as a unique fingerprint. QuickBooks® stores these IDs and compares them on subsequent imports, automatically skipping any transaction it has already recorded. This duplicate detection is one of the key advantages of QBO over simpler formats like CSV.
In QuickBooks® Desktop, imported transactions appear in the bank register for review. In QuickBooks® Online, they land in the Banking tab's "For Review" queue, where you can match them to existing records or categorize them before accepting.
QBO files are supported by all major QuickBooks® editions and several other financial applications:
Pro, Premier, Enterprise
All plans
Deluxe, Premier, Home & Business
Tip: If QuickBooks® doesn't recognize an .ofx file during import, simply rename it to .qbo. The internal format is identical — QuickBooks® just expects the .qbo extension for its Web Connect workflow.
IIF is a tab-delimited format for QuickBooks® Desktop only and supports lists, journal entries, and other record types. QBO is XML-based, works across Desktop and Online, but handles only bank/credit card transactions.
CSV files are universal but lack metadata like bank IDs and transaction fingerprints. QBO includes duplicate detection via FITID, making repeated imports safe without manual deduplication.
QFX is Quicken's proprietary extension of OFX. Both QBO and QFX are OFX-based, but QFX targets Quicken while QBO targets QuickBooks®. The structural differences are minimal.
Use our free tool to convert your bank CSV files to QBO format instantly.
Start Converting Free