What is a QBO file?

A QBO file is how QuickBooks Desktop takes in a month of bank transactions. Intuit calls the mechanism Web Connect, which is why the same file gets called a Web Connect file in half the documentation.

It is not a QuickBooks company file. That is a .qbw, and it holds your entire books. A .qbo holds a list of transactions and nothing else, and it is disposable once imported.

What is in it

Underneath, a QBO file is OFX, the same specification behind .qfx and .ofx. Rename it to .txt and it reads like this:

OFXHEADER:100
DATA:OFXSGML
VERSION:102
<OFX>
 <BANKMSGSRSV1><STMTTRNRS><STMTRS>
  <CURDEF>USD
  <BANKACCTFROM><BANKID>021000021<ACCTID>4471...<ACCTTYPE>CHECKING</BANKACCTFROM>
  <BANKTRANLIST>
   <STMTTRN><TRNTYPE>DEBIT<DTPOSTED>20260314<TRNAMT>-62.41
    <FITID>2026031400418822<NAME>HANOVER GROCERY</STMTTRN>
  </BANKTRANLIST>
  <LEDGERBAL><BALAMT>2837.60<DTASOF>20260331</LEDGERBAL>
 </STMTRS></STMTTRNRS></BANKMSGSRSV1>
</OFX>

Note the header lines above <OFX>. They are not tags, they are key and value pairs, and they have to come first, followed by a blank line. Get that wrong and QuickBooks rejects the file before it reads a single transaction.

Note also that value tags never close. OFX 1.x is SGML rather than XML, so <TRNAMT>-62.41 ends when the next tag starts. Anything written by an XML library produces a file that looks correct and imports nowhere.

What makes it a QBO rather than an OFX

Two identifiers, and they cause most of the trouble people have with the format.

Tag	What it holds	What breaks without it
BANKID	The bank’s routing number	QuickBooks cannot match the account
INTU.BID	Intuit’s own id for that bank	The file is rejected as unsupported
ACCTID	Your account number, or a fragment	The import lands on the wrong account
ACCTTYPE	CHECKING, SAVINGS or CREDITLINE	Signs invert on a credit card imported as checking

INTU.BID is a licensing tag. Banks pay Intuit to issue Web Connect files, which is why some banks offer QBO downloads only on business accounts or behind a monthly fee, while CSV is free for everyone. It is also why an .ofx renamed to .qbo gets refused: the branding is not there.

The error everyone hits

QuickBooks is unable to verify the Financial Institution information for this download.

This means the ids in the file do not match the account you are importing into. Three ways out, in the order worth trying:

1. Import into the account the file belongs to. If you have two checking accounts set up, it is easy to pick the wrong one.
2. Create the account fresh and import into it. QuickBooks binds the ids on the first Web Connect import, so a clean account accepts whatever arrives.
3. Edit the ids in the file. They are plain text near the top. This works and is the last resort, because a wrong BANKID in a file you keep will confuse the next import too.

QuickBooks Online does not need this

If you are on QuickBooks Online, a QBO file is usually the harder path. QBO Online imports CSV directly, with a column mapping step, and a CSV is far easier to fix before import: open it, correct a description, delete a duplicate, save.

The case for a QBO file is Desktop, where CSV import is limited, or any situation where you want the transaction type and the per transaction identifiers to survive, because those are what stop a re-import from creating duplicates.

There is more on that decision, including when a CSV is the right answer, in do you need a QBO file. If you have the CSV and want the QBO anyway, convert it here.

Making one from a PDF statement

When the bank will not give you a QBO, or wants a fee for it, the statement PDF has the same transactions in it.

Our converter reads the PDF in your browser and writes a valid .qbo, with the SGML structure and the header block that QuickBooks checks, an account type you choose, and a generated FITID per row so importing twice does not duplicate. The file never leaves your machine, which is the reason it works this way rather than on a server.

Set the account type before you download. A credit card statement written as CHECKING imports with every sign the wrong way round, and unwinding that inside QuickBooks takes longer than converting the file again.