QuickBooks Web Connect Import Error: Causes and Fixes
No account needed for your first conversions. We never store your bank login.
A QuickBooks Web Connect import error means QuickBooks could not read or verify the .qbo file you tried to import. The usual causes are a file that is not really a valid Web Connect file (often a renamed QIF), a bank or account that does not match the one named in the file, duplicate transactions QuickBooks has already seen, or dates it cannot parse. Fix the file and the account it targets, and the import goes through. Below is each cause with the exact steps to clear it.
If you built the .qbo by converting a QIF export, the converter at the top of this page writes a valid Web Connect file: correct OFX headers, a unique ID on every transaction so QuickBooks does not double count, and the D and T tags cleaned into clean dates and amounts before export. That removes the most common reasons a converted file gets rejected. The rest of this guide covers the errors you might still hit and how to fix them.
Common Web Connect import errors at a glance
Most import failures fall into a handful of buckets. Find your symptom in the table, then read the matching section below for the full fix.
| What you see | What it means | Fix |
|---|---|---|
| "The financial institution information in the file does not match..." | The bank or account named in the .qbo does not match how the QuickBooks account is set up for bank feeds | Import into the matching account, or edit the account's Bank Feeds setup and re-import |
| QuickBooks could not read the file, or nothing imports | The file is not valid Web Connect: a renamed QIF, broken OFX, or the wrong extension | Use a real .qbo with valid Web Connect headers, not a QIF renamed to .qbo |
| "These transactions have already been downloaded" | QuickBooks deduplicates on each transaction's unique ID, and it has seen these before | Import a non-overlapping date range; each transaction needs its own unique ID |
| Some transactions are missing after import | Future-dated or out-of-range dates, or a date format QuickBooks read wrong | Correct the dates in the source, or use a converter that normalizes them |
| QuickBooks Online: "we can't read this file" | The file is over the size limit or is not a valid .qbo | Keep it under the limit and confirm the extension and format are .qbo |
| Error OL-301 or OL-393 | A Direct Connect bank-feed connection error, not a manual file import | A login or connection issue with the bank feed; manual Web Connect import avoids it |
Why am I getting a Web Connect import error in QuickBooks?
You get a Web Connect import error because QuickBooks rejected something about the .qbo file or the account it was aimed at. The four frequent triggers are an invalid file (a QIF renamed to .qbo rather than a real Web Connect file), a financial institution name that does not match the account's bank feed setup, transactions QuickBooks has already imported, and dates it cannot parse. The error text usually points to which one, and each has a specific fix below.
What does "the financial institution information does not match" mean?
It means the bank identity written inside the .qbo does not line up with how that account is configured for bank feeds in QuickBooks. Every Web Connect file names a financial institution, and QuickBooks matches it to an account already set up for that bank. If the account was set up for a different bank, or for direct online services, the import stops. Import the file into the correct account, or in QuickBooks Desktop open the account, edit the Bank Feeds setup, deactivate the existing online service, then import again.
How do I fix a QuickBooks Web Connect import error?
Work through four checks in order. First, confirm the file is a genuine .qbo (open it in a text editor; valid Web Connect files start with OFX headers, not column commas). Second, import it into the exact account that matches the bank named in the file. Third, import a date range you have not imported before so QuickBooks does not flag duplicates. Fourth, make sure the dates are real and not in the future. If the file itself is the problem, rebuild it from your source data with a converter that writes valid Web Connect output.
Why won't my .qbo file import into QuickBooks?
The most common reason a .qbo will not import is that it is not actually a Web Connect file. Renaming a QIF to .qbo does not change what is inside it, and QuickBooks reads the contents, not the extension. A QIF is tagged text (D, T, P lines separated by carets), while a real .qbo is OFX text with Web Connect headers, a financial institution block, and a unique ID per transaction. Convert your QIF into that format with the tool above instead of changing the file name, and the import works.
What is QuickBooks error OL-301 and OL-393?
OL-301 and OL-393 are Direct Connect bank-feed errors, not manual import errors. They show up when QuickBooks tries to connect live to your bank and the login, the account status, or the bank's server blocks it. Because they involve the live connection, they are separate from importing a .qbo by hand. If your bank's Direct Connect keeps failing, exporting transactions as a QIF and importing a converted .qbo through Web Connect sidesteps the connection entirely.
How do I import a Web Connect (.qbo) file into QuickBooks Desktop?
In QuickBooks Desktop go to File, then Utilities, then Import, then Web Connect Files, and pick your .qbo. QuickBooks asks whether to use an existing account or create a new one, then drops the transactions into the Bank Feeds center for review. If you see the financial-institution mismatch error here, the account you chose is tied to a different bank setup; either select the right account or clear its bank feed setup first.
How do I upload a .qbo file to QuickBooks Online?
In QuickBooks Online open Transactions, then Bank transactions, select the account, click the dropdown next to Link account, and choose Upload from file. Add the .qbo and QuickBooks Online reads it as a bank feed, no column mapping needed. If it says it cannot read the file, the .qbo is invalid or too large; rebuild it from your QIF source with a converter and keep each file to a single account and a reasonable date range.
Can a bad QIF cause a Web Connect import error?
Yes, indirectly. If you convert a messy QIF, problems in the source carry into the .qbo: stray characters on the T amount line, ambiguous dates on the D line, missing caret separators, or reversed credit card signs. A converter that validates and reconciles the tags before it writes the file catches these first. The QIF to QuickBooks Online converter checks the parsed total against your file, and the credit card QIF to QuickBooks page handles the sign reversal that trips up card imports.
How do I avoid Web Connect import errors?
Start from clean transaction data and build a proper Web Connect file. Export your activity as a QIF rather than PDF, convert it to a real .qbo, import a date range once, and aim each file at the right account. If your data is locked in a PDF statement instead of a QIF, convert the PDF statement straight to a .qbo, or first turn the PDF bank statement into Excel or CSV and reshape it into QIF for converting here. Starting from a bank's full statement? A bank statement to QuickBooks converter covers that source.
For more on the format itself, read what a .qbo file is and why QuickBooks needs it, see the guide to importing bank statements into QuickBooks, or compare the best QIF to QBO converters if you are choosing a tool. To convert a file now, head to the QIF to QuickBooks Online or QIF to QBO converter.