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.
First, make sure you are importing it the right way
Half of "it won’t import" is the file going in through the wrong door. Each edition has one correct route.
| Edition | Where to import | Accepts |
|---|---|---|
| QuickBooks Online | Bank transactions → Link account → Upload from file (or the account tile → Upload from file) | QBO, QFX, CSV; English PDF or image statements; 350 KB and 1,000 transactions per file |
| QuickBooks Desktop (Windows) | File → Utilities → Import → Web Connect Files, or Banking → Bank Feeds → Import Web Connect File | .qbo only |
| QuickBooks Desktop for Mac | File → Import → From Web Connect | .qbo only |
In QuickBooks Online, a PDF dropped onto the general upload area rather than into Upload from file can end up in Receipts, where it waits as a document instead of becoming bank transactions. In Desktop, double-clicking a .qbo also works, but only if Windows has associated the extension with QuickBooks.
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.
1. Is it actually a Web Connect file?
Open it in a text editor — Notepad or TextEdit, not Word or Excel. The first line of a genuine .qbo is a header, not markup:
OFXHEADER:100
DATA:OFXSGML
VERSION:102If 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. QuickBooks Online reports this as "The uploaded file isn’t a valid Web Connect file".
2. Does it have a bank ID?
Search the file for INTU.BID. Missing, empty, or an obvious placeholder means Desktop will reject it — usually as OL-301, sometimes as "unable to verify the Financial Institution information". A number copied from a Quicken QFX file is a quieter version of the same fault: banks often use a different ID for each product.
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 (CHECKING, SAVINGS, CREDITLINE), or whether it uses a credit-card block, against the type in your chart of accounts. QuickBooks Online says so outright: "The uploaded file is of a different type than these 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 either succeeds and duplicates or — when the transaction IDs match — imports nothing at all and reports the account as up to date.
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 it within QuickBooks Online’s limits?
Intuit caps uploads at 350 KB and up to 1,000 transactions per file. A year of a busy account can exceed that, and QuickBooks Online answers with "The uploaded file is too large". A .qbo cannot be split safely by hand; download or convert shorter date ranges instead — a quarter or a month at a time. Intuit also rejects any transaction amount of 12 digits or more, reported as invalid transaction amount information.
8. Is your QuickBooks Desktop version still supported?
Intuit retires connected services for each Desktop release roughly three years after launch, on 31 May; Desktop 2023 lost bank feeds, payroll and live support after 31 May 2026. A retired version still opens your company file, but online banking stops and Web Connect imports commonly fail with OL- errors or "unable to verify". This is the explanation behind most "QuickBooks Desktop 2020 (or 2021) no longer imports QBO" threads. The workarounds are to upgrade, or to import IIF, which needs no online services.
9. Is the problem at the QuickBooks end?
If the file passes every check above, the remaining causes are environmental.
- Not on the current release. Update (Help → Update QuickBooks Desktop) 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, or an inactive account still has online banking on. In the Chart of Accounts tick Include Inactive, and for any account with a lightning-bolt icon use Edit Account → Bank Feed Settings → Deactivate All Online Services. Back up first.
- In QuickBooks Online, a parent account and its sub-account cannot both be connected; Intuit’s workaround is to disconnect one temporarily, upload, then reconnect.
Which error means which
QuickBooks reports several distinct problems through a small set of messages, which is why the same message sends different people down different paths. Roughly:
| Message | Where | Usually means | Start at |
|---|---|---|---|
| OL-301 | Desktop | The file, usually its bank ID | Checks 1, 2, 8 |
| OL-249 | Desktop | The pairing between file and account | Checks 3, 4, 9 |
| Unable to verify the Financial Institution information | Desktop | Bank ID not recognised, or retired version | Checks 2, 8 |
| Nothing imported / no new transactions | Desktop | These transaction IDs were already imported | Check 5 |
| The uploaded file isn’t a valid Web Connect file | Online | Structure or format | Checks 1, 6 |
| The uploaded file is of a different type than these accounts | Online | Account type mismatch | Check 4 |
| The uploaded file is too large | Online | Over 350 KB | Check 7 |
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 refusedBoth 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.
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. QuickBooks Online takes a three- or four-column CSV (Date, Description, Amount, or separate Credit and Debit columns) without a bank ID, and now also reads English-language PDF statements directly. IIF imports into Desktop. CSV and IIF both lose ID-based duplicate detection, which means importing each period exactly once and checking the range before you do.