Skip to content
statement2sheets

Bank file won’t import into QuickBooks? Fixes for QBO, QFX and OFX errors

· 6 min read

You downloaded a .QBO, .QFX or .OFX file from your bank, pointed QuickBooks at it, and got an error instead of transactions. The messages aren't much help, but the causes are usually one of a handful, and most can be found by looking inside the file.

The errors you might be seeing

QuickBooks Desktop's own help lists these for Web Connect imports, the way Desktop reads .QBO files:

  • "QuickBooks found an error. We can't read the file [your bank] sent."
  • "An error occurred while processing your online banking data."
  • "Your data was not imported into QuickBooks."
  • "QuickBooks is unable to verify the Financial Institution information for this download."

On a Mac it can show up as error OL-222. In QuickBooks Online, people report "The uploaded file isn't a valid Web Connect file" when using Upload from file.

Start by looking inside the file

These files are plain text, so the fastest way to find the problem is to open one up. The free OFX and QFX viewer reads .OFX, .QFX and .QBO files in your browser, lists anything likely to stop an import and how many transactions it affects, and shows every transaction. It doesn't upload the file anywhere. Then match what it finds to the fixes below.

Wrong file type for your version of QuickBooks

QuickBooks Desktop's Web Connect only reads .QBO files, according to Intuit. If your bank gave you a .QFX (made for Quicken) or a plain .OFX, Desktop may refuse it even though the transactions inside are fine. Look for a "QuickBooks" or "Web Connect" option on your bank's download page.

QuickBooks Online is more flexible. Its Upload from file accepts .QBO, .QFX, .OFX, .CSV and .TXT, so if one format fails there, another often works.

"Unable to verify the Financial Institution"

This one is about INTU.BID, a code inside .QBO and .QFX files that tells QuickBooks which bank the file came from. If it's missing, or QuickBooks doesn't recognise it, the import stops. Intuit's suggested fixes for Desktop are:

  1. Download the file directly from your bank's website again, as .QBO.
  2. Switch Bank Feeds to Classic mode (Banking → Change Bank Feeds Mode → Classic mode) and import again.
  3. Try importing into a new test company file. If that works, disconnect and reconnect the account in your real file.
  4. On a Mac, update QuickBooks' list of financial institutions (the error OL-222 fix).

If none of that works, Intuit's advice is to contact your bank, since the bank produces the file. The viewer shows whether the file has an INTU.BID at all, which is useful to know before you call.

A bare "&" in a payee name

OFX files are a kind of markup, where "&" has a special meaning and should be written "&". When a bank writes a payee like AT&T with a bare "&", some importers stop reading the file at that point. A common fix in QuickBooks community answers is to open the file in a text editor and replace the "&" with "and". The viewer flags this, and its repaired OFX escapes every "&" properly.

The file is too big

QuickBooks Online's Upload from file takes files up to 350 KB and 1,000 transactions. A year of a busy account can go over that. Download a shorter date range and import it in parts.

The download was cut off

A file that stops partway through, often from a dropped connection or a download that timed out, can't be read at all. The viewer reports sections that are never closed. Download it again, ideally for a shorter period.

Transactions missing, or skipped as duplicates

Every transaction in an OFX file carries an ID called the FITID, and importers use it to avoid importing the same transaction twice. If two transactions share an ID, one can be skipped as a "duplicate". If IDs are missing, the importer may skip those transactions or import them again next time. The viewer counts both, and its repaired OFX gives each transaction a unique ID while keeping the original wherever it was already unique, so transactions you imported before are still recognised.

The repaired file is plain OFX, not .QBO. It suits QuickBooks Online's Upload from file. QuickBooks Desktop's Web Connect needs a .QBO with a valid INTU.BID, which only your bank can provide.

When the file just won't go in

Two fallbacks get the transactions into QuickBooks Online anyway:

  • Use CSV. The viewer can export the transactions in the three-column layout QuickBooks Online expects. There's more in how to import a bank CSV into QuickBooks Online.
  • Start from the PDF statement. If your bank's downloads are the problem, the statement converter reads the PDF statement in your browser, checks the transactions against its closing balance, and exports OFX or CSV.

More from the blog