Bank statement to QBO
The QuickBooks format. Importing it takes one extra click, and this page explains why we will not remove it.
QBO is QuickBooks’ own flavour of OFX: the same transaction data, plus a few extra tags that Intuit’s software looks for. If you use QuickBooks Desktop or QuickBooks Online’s file upload, this is the export to take.
Why you have to pick the account yourself
When you import our .qbo file, QuickBooks will ask you which account it belongs to instead of
matching one automatically. That is because we leave the Intuit bank ID blank on purpose.
Intuit assigns every participating bank a number. We are not a bank and we have not been assigned one. We could put someone else’s number in the file — it is a short number, they are not secret, and it would make the extra prompt go away.
We will not, and the reason is worth a sentence: if that file lands in a QuickBooks account that already has a connection to the bank whose number we borrowed, your transactions can be filed against the wrong account, and untangling a mis-filed import is far more work than one dropdown. A single click is a very bad trade for that risk.
So: import the file, choose the right account when QuickBooks asks, and the transactions land where you meant them to.
What is in the file
Everything the OFX export contains — dates, signed amounts, descriptions as printed, derived transaction types, the masked account number — in the same OFX 1.0.2 SGML the importers actually accept. The QBO file is that file plus the Intuit tags.
If part of your PDF could not be read, the warning is carried inside this file too, not only shown on screen.
How the QBO file differs from the OFX one
By exactly one tag. The .qbo we write is the same generator’s output as the
OFX export, plus the Intuit bank ID tag in the sign-on block — the tag
discussed above, written empty. The transactions, the dates, the amounts, the descriptions and the
duplicate-detection identifiers are identical in both files.
That has a practical use. If your software takes plain OFX, there is no reason to hand it the QBO file, and nothing is gained by converting again — download the OFX from the same conversion. QBO is for the places that will not accept anything else, which in practice means QuickBooks.
The CSV route, and when to take it instead
QuickBooks Online also accepts a CSV upload, and Intuit publishes a specific set of rules for it: a size ceiling, a line-count ceiling, and a fixed choice of three or four columns. A file that breaks any of them fails at the column-mapping step, with a message that names a column rather than the rule you actually broke. We have written those rules out in full, with links to Intuit’s own pages, in Importing bank statements into QuickBooks Online.
The short version: the QBO file is not subject to either ceiling, so a busy year that would have to be uploaded as several CSV batches goes in as one file. Take the CSV route when you want to review or edit the transactions before they land in QuickBooks — which is a good reason, just not a formatting one.
If QuickBooks refuses the file
Two things are worth checking before you assume the conversion is broken.
QuickBooks Desktop expects Web Connect files to be imported through File → Utilities → Import → Web Connect Files, not by opening them. And some versions refuse a file whose date range overlaps transactions already imported — that is a duplicate guard, not a format error.
If it still will not import, take the CSV or Excel export and use QuickBooks’ own column mapping. Every conversion produces all five formats, so switching costs you nothing.