QuickBooks won’t import my .qbo file: 7 things to check

7 September 20268 min read

A .qbo that will not import fails for one of a small number of reasons. Worked in this order, the list finds most of them within a few minutes — it starts with what is cheapest to check, not with what is most likely to be interesting.

1. Is it actually a Web Connect file?

Open it in a text editor. The first line of a genuine .qbo is a header, not markup:

OFXHEADER:100
DATA:OFXSGML
VERSION:102

If you see HTML, JSON, or a login page, the download failed and the extension is the only thing that is right about the file. If you see <?xml, it is OFX version 2, which some QuickBooks builds will not read even though it is valid OFX.

If the file came from a converter and the checks below point at its contents, it is usually quicker to convert the statement again with the right settings than to edit a Web Connect file by hand.

2. Does it have a bank ID?

Search the file for INTU.BID. Missing, empty, or an obvious placeholder means QuickBooks will reject it — usually as OL-301, sometimes as "not from a supported financial institution".

3. Does the account number match?

Find the ACCTID tag and compare it with the account number on the QuickBooks account. A mismatch typically produces OL-249. Masked digits in one place and full digits in the other count as a mismatch.

4. Does the account type match?

A credit-card file will not import into an account QuickBooks holds as a bank account. Check ACCTTYPE in the file against the type in your chart of accounts.

5. Is the date range sane?

DTSTART and DTEND bracket the statement period. Two things go wrong here: a range in the future, which QuickBooks refuses, and a range that overlaps a period already imported, which succeeds and duplicates.

Dates are formatted YYYYMMDD, optionally with a time and timezone. A date that is not eight digits is a converter bug.

6. Is the file complete?

Scroll to the bottom. It should end with closing tags, </OFX> last. An interrupted download or an editor that truncated on save leaves a file QuickBooks reports as an online banking failure rather than as an incomplete file.

7. Is the problem at the QuickBooks end?

If the file passes all six checks, the remaining causes are environmental.

Not on the current release. Update and try again before anything else.
Company file in multi-user mode. Switch to single-user.
File on a network drive or synced folder. Copy it to a local disk.
Account has stale bank feed state. Deactivate online services for the account, back up first, and import again.

If none of it works

Some banks simply are not enrolled for Web Connect, and no valid file can be produced for them. At that point the format is the problem, not the file. CSV imports into QuickBooks Online without a bank ID; IIF imports into Desktop. Both lose duplicate detection, which means importing each period exactly once and checking the range before you do.

Which error means which

QuickBooks reports several distinct problems through a small set of codes, which is why the same code sends different people down different paths. Roughly:

OL-301 — the file, and usually its bank ID. Start at check 1 and 2.
OL-249 — the pairing between file and account. Start at check 3 and 4.
"Not from a supported financial institution" — the bank ID is not on Intuit’s list at all. Check 2.
"The file cannot be read" or nothing at all — structural. Check 1 and 6.

None of this mapping is documented by Intuit and none of it is absolute. It is a starting order, not a diagnosis.

The OFX version trap

OFX exists in two forms. Version 1.x is SGML — the header block at the top of the file, tags that need not be closed. Version 2.x is XML, and starts with an XML declaration.

OFXHEADER:100        <- version 1, what QuickBooks wants
<?xml version="1.0"?>  <- version 2, frequently refused

Both are valid OFX. QuickBooks’ Web Connect import has historically expected the first, and a file in the second form fails in ways that look like everything else on this list. If a file opens in a browser as a tidy XML tree, that is a warning sign rather than a good sign.