What is a QBO file?

What’s inside a .qbo file

A .qbo file is plain text. Open one in a text editor and you’ll see a short header, then tags in angle brackets for:

• The bank’s Intuit ID (INTU.BID), which QuickBooks Desktop uses to know which bank the file is from.
• The account: its number, whether it’s a checking, savings or credit card account, and its currency.
• Each transaction: the date, the amount (negative for money out), the payee, sometimes a memo or check number, and an ID of its own (FITID).
• The ending balance and the date it’s as of (LEDGERBAL).

A shortened example, with one transaction:

OFXHEADER:100
DATA:OFXSGML
VERSION:102
ENCODING:USASCII
CHARSET:1252
...
<INTU.BID>12345
...
<STMTTRN>
<TRNTYPE>DEBIT
<DTPOSTED>20261001
<TRNAMT>-4.50
<FITID>20261001-0001
<NAME>COFFEE SHOP
</STMTTRN>
...
<LEDGERBAL>
<BALAMT>1520.75
<DTASOF>20261031
</LEDGERBAL>

The transaction IDs are what make Web Connect safer than a CSV: when QuickBooks sees an ID it already has, it skips that transaction instead of adding it again, so overlapping downloads don’t double up.

QBO, QFX and OFX

All three are OFX, the format banks have used for downloads since the late 1990s. The difference is who they’re labelled for:

• .qbo is for QuickBooks (Desktop and Online).
• .qfx is for Quicken. Quicken checks the bank ID the same way QuickBooks Desktop does.
• .ofx is the plain version, usually without Intuit’s bank ID, that Xero, GnuCash, Moneydance and many other apps import. QuickBooks Online takes it too.

So when a bank offers a Quicken download but not a QuickBooks one, the data is already there: convert QFX to QBO or OFX to QBO, which keeps every transaction ID.

How to import one

• QuickBooks Online: Bank transactions, then Upload from file, then pick the account. Step by step in importing bank statements into QuickBooks Online.
• QuickBooks Desktop: File › Utilities › Import › Web Connect Files, then choose the account or create one.

How to open one as a table

Excel doesn’t read .qbo files. Any text editor will open one, as above, but to see the transactions in rows, convert it: QBO to Excel gives a workbook with real dates and numbers, and QBO to CSV a plain table for any other app.

“The uploaded file isn’t a valid Web Connect file”

That’s QuickBooks Online’s message for a .qbo file it won’t read. In our tests in a QuickBooks Online sandbox (October 2026), two things caused it:

• No ending balance. A file without the <LEDGERBAL> block was refused, even though every transaction in it was fine. OFX requires one; a converter that leaves it out when the statement has no closing balance produces exactly this error. BankToRows always writes it, as 0.00 if the balance isn’t known, which QuickBooks shows as the bank balance without touching the transactions.
• A UTF-8 header. A file declaring ENCODING:UTF-8 was refused too. Web Connect files declare ENCODING:USASCII.

Two more things worth a look when a file won’t import: whether it starts with OFXHEADER at all (a page saved from the browser starts with <html> instead), and whether it’s complete, ending with </OFX>.

Accents that turn into question marks

In the same tests, QuickBooks Online showed every accented or non-English letter in a .qbo file as “?”, whatever the file said its character set was. So the files BankToRows writes spell such text plainly (Café becomes Cafe, € becomes EUR). Excel and CSV downloads keep the original text.

Making a .qbo file

If your bank only gives you PDF statements or a CSV, convert them: PDF statement to QBO or CSV to QBO. Every transaction gets an ID that stays the same if you convert the file again, so importing a statement twice doesn’t duplicate it.