What Is a QBO File?

The short answer

A .qbo file is a bank statement written in OFX 1.0.2, with a few Intuit-specific tags added. It holds a list of transactions, the period they cover, a closing balance, and an identifier naming the institution that published it. Banks call this Web Connect.

It is plain text, despite appearing in a program's file dialog as something proprietary. Open one in a text editor and you can read every transaction in it. What makes it awkward to read is not encryption but the markup, which was written for software rather than for people.

QBO the file, QuickBooks Online the product

Two entirely different things are called QBO, and searching for one reliably returns the other. QuickBooks Online is the subscription accounting product. A .qbo file is a statement your bank produces, and it long predates the online product. The name is a coincidence of abbreviation rather than a relationship.

If you are trying to get figures out of QuickBooks Online, that is a report you run inside the product. It does not produce a .qbo file, and nothing on this page applies to it.

What a QBO file looks like inside

Every file opens with a header block of colon-separated pairs, and then switches into markup. This is the shape of it, cut down to one transaction:

OFXHEADER:100
DATA:OFXSGML
VERSION:102

<OFX>
  <BANKTRANLIST>
    <STMTTRN>
      <TRNTYPE>DEBIT
      <DTPOSTED>20260105120000
      <TRNAMT>-24.50
      <FITID>40f6c792fe2eee54c11f
      <NAME>COFFEE SHOP
    </STMTTRN>
  </BANKTRANLIST>
  <LEDGERBAL>
    <BALAMT>1482.19
  </LEDGERBAL>
</OFX>

Note that the inner tags are never closed. OFX 1.x is SGML, not XML, and a value simply runs to the next angle bracket. That is why a .qbo opened in an XML tool is usually reported as malformed when it is nothing of the kind. OFX 2.x is real XML and does close its tags. Both are in circulation.

FITIDs, and why they decide what gets counted twice

The FITID is the most consequential field in the file and the least visible. It is a unique id for each transaction, and importing software uses it to recognise entries it has already seen. That is how you can load two overlapping statements without every shared transaction landing twice.

The failure mode is the interesting one. Two genuine transactions can share an id: two identical coffees on the same day, same amount, same description. One then looks like a duplicate of the other and can be dropped without anything being reported. A statement that is quietly one transaction short is far worse than one that fails loudly.

So the ids in a well-made file are distinct even when the transactions are identical. It is worth checking, because it is invisible until a reconciliation refuses to balance weeks later.

The institution identifier, and where the numbers come from

The tags that make a .qbo more than plain OFX are the ones naming the institution: an INTU.BID in the header and an <FI> block holding an <ORG> and a <FID>. These are not free text. They are numbers registered in Intuit's Financial Institution Directory: the list the software itself consumes, published openly at ofx-prod-filist.intuit.com.

Roughly 6,400 of the directory's 16,500 records describe an institution that publishes a downloadable statement file. The rest do not, which means for those there is no valid identifier to write, because there is no .qbo to write it into. Retired records are still listed and prefixed zzz-, ZZ- or z-.

An identifier is the one part of the format a converter cannot invent. A file carrying a number belonging to a different institution claims to have come from somewhere it did not, which is a worse outcome than carrying none at all.

Web Connect is not Direct Connect

The directory distinguishes two things that sound alike, and the difference decides whether a file exists at all.

This is why some banks offer a .qbo download and others only ever offer CSV. Several large institutions are connected the second or third way and never produce a file, among them ones you would expect to publish one. The bank pages say which is which.

What a QBO cannot tell you

A .qbo is a statement, not a set of books. It carries no categories, no account assignments and no notion of what any transaction was for. A payee string and an amount is the whole of what it knows. Categorisation happens after the file is read, not inside it.

It states one closing balance for the period rather than a running balance per row, so a file that lost transactions somewhere in the middle is still internally consistent. Totalling the transactions and comparing the result against LEDGERBAL is the check worth doing, and it is the one thing the format gives you for free.

And it is a snapshot with no version. Two files covering overlapping periods have no way of describing their relationship to each other beyond the FITID on each transaction. That is why that field carries as much weight as it does.

Frequently asked questions

Is a QBO file the same as QuickBooks Online? No. QuickBooks Online is an accounting product; a .qbo file is a bank statement in Intuit's Web Connect format, produced by your bank. The shared abbreviation is a coincidence, and it is the single most common confusion around the format.

Can I open a QBO file in a text editor? Yes. It is plain text: a header block followed by markup. Reading it is the fastest way to confirm a file holds the period and the transactions you expect. What you should not do is edit one by hand, because the transaction ids and the stated balance have to stay consistent with the transactions above them.

Why does my XML editor say the file is invalid? Because it usually is not XML. OFX 1.x, which is what a .qbo normally contains, is SGML, and its inner tags are never closed. A value runs to the next angle bracket instead. OFX 2.x is genuine XML and will parse, but plenty of banks still publish the older dialect.

What is the difference between a QBO and an OFX file? The Intuit tags. Both are OFX documents carrying the same transaction grammar, and a .qbo adds an institution identifier naming the bank that published it. Strip those and what remains is plain OFX. See what an OFX file is, including the two dialects it comes in.

Does a QBO file contain my account number? It contains an account identifier in the <BANKACCTFROM> block, which for many banks is the account number or a masked form of it, alongside a routing number. It is worth knowing that before emailing one around. A .qbo is not an anonymous file the way a QIF is.