QuickBooks Web Connect import errors

You have a .QBO file, QuickBooks Desktop refuses it, and the message tells you almost nothing. Before you start rebuilding company files, there are two requirements that catch people out and are easy to check in a minute.

1. You have to be signed in to your Intuit Account

This is the one that wastes afternoons, because nothing about the error points at it. Intuit's own support article states it plainly:

"Import of web connect files (.qbo) requires you to sign in to your Intuit Account within QuickBooks Desktop."

— Fix Web Connect import errors, QuickBooks Support

Signed out, the import can simply fail. If you have recently reinstalled, changed machine, or been signed out by an update, check this first — it costs nothing to rule out.

2. It must genuinely be a .qbo file

The same article is unambiguous about the format: a ".qbo file, the only type Web Connect can read."

A file is not a QBO because it has been renamed to .qbo. Changing the extension on a CSV, an OFX or a QFX does not change what is inside, and Web Connect reads what is inside. This matters because renaming is advice you will find in forum threads, and it does not work — a QBO is OFX data with an Intuit-specific header, so the header has to actually be there. What a QBO file contains goes through it.

What Intuit lists as the causes

Beyond those two, the support article points at:

An incomplete file or an incompatible format — the file itself is not what QuickBooks expects.
Changes at your bank, which can alter what the download contains.
Settings in your company file.
A problem with the .qbo your bank produced, in which case Intuit's advice is to go back to the bank about it.

Their suggested fixes run from switching Bank Feeds to Classic mode (from Banking, hover Bank Feeds and select Change Bank Feeds Mode), to testing the import in a brand-new company file to see whether the problem follows the file or stays with the company, to disconnecting and reconnecting the account.

Testing in a new company file is the most useful of those, because it answers the only question that matters at that point: is the file bad, or is this company file bad? If a fresh company file accepts it, stop blaming the download.

When the file really is the problem

If the bank's own .QBO is malformed, you are waiting on the bank, and that can take a while. The practical way around it is to stop using their QBO: download a CSV export instead and build your own QBO from it, which puts the file under your control rather than theirs.

🔒 Convert a CSV or PDF statement to QBO — free, runs in your browser, nothing uploaded.

Two things worth knowing if you go that route:

The institution tags matter. QuickBooks checks FID and INTU.BID in the header and can refuse a file whose values it does not like, with an error that says nothing about why. The converter lets you change them.
A second import of the same file can look like it did nothing. That is not an error: QuickBooks remembers transaction ids it has already seen and skips them silently. See why a re-import gets skipped.

Importing into QuickBooks Online instead?

Web Connect is a QuickBooks Desktop feature, so none of the above applies to QuickBooks Online — it takes CSV directly. See the CSV format requirements, and if your upload is being rejected with a vague message, "Some info may be missing from your file" covers what actually triggers it.

Build a QBO from your statement — free

Sources

Fix Web Connect import errors — QuickBooks Support, source for the Intuit Account requirement, the .qbo-only statement, the listed causes and the suggested fixes.