A Web Connect file not opening in QuickBooks Desktop usually has one of four causes: Windows sends the .qbo file to the wrong program, your Desktop release is out of support, the bank changed its ID details, or the download is damaged or not a QBO at all. Start by importing it from inside QuickBooks rather than double-clicking.
Why is the Web Connect file not opening at all?
A Web Connect file is a .qbo download from your bank that QuickBooks Desktop reads to add transactions. When it will not open, the symptom points to the cause. Nothing happening, or the wrong program opening, is a computer setting. An error message from QuickBooks means it reached the file and disliked what it found.
Use the table below to sort your case before you change anything. The fixes in the last column are explained in the sections that follow.
| What you see | Likely cause | First thing to try |
|---|---|---|
| Double-clicking does nothing | File not linked to QuickBooks | Import from inside QuickBooks |
| The file opens in Quicken, a browser or a text editor | Wrong program set for .qbo files | Import from inside QuickBooks, then fix the link |
| "We can't read the file" your bank sent | Incomplete or wrong-format file | Download again from the bank's website |
| "Unable to verify the Financial Institution information" | Bank details changed, or bank dropped Web Connect | Check bank messages, then test in a new company file |
| QuickBooks keeps asking you to pick an account | A company file settings problem | Test the file in a new company file |
| A request to sign in with your Intuit account | Advanced bank feeds mode | Sign in, or switch to Classic mode |
The error texts in the table come from Intuit's guide to fixing Web Connect import errors in QuickBooks Desktop. Its first advice before any fix is to back up your company file, and that is worth doing now.
File association that sends a QBO file to the wrong program
File association is the Windows setting that decides which program opens a file when you double-click it. If the .qbo extension is linked to Quicken, a browser or nothing at all, the Web Connect file never reaches QuickBooks. The file itself is often fine.
This happens most after installing Quicken, moving to a new computer, or reinstalling QuickBooks. It also happens when a browser offers to "open" a download instead of saving it.
The quick way round it
Skip the double-click. Save the .qbo file to a folder you can find, such as Downloads. Open QuickBooks Desktop and the company file you want, then use the import command for Web Connect files under the Banking menu's Bank Feeds options. Browse to the file and open it. Importing from inside QuickBooks does not depend on the file association at all.
Fixing the association for next time
If you want double-clicking to work again, right-click any .qbo file in File Explorer, choose Open with, then Choose another app. Pick QuickBooks and tick the option to always use it for .qbo files. If QuickBooks is not in the list, the import route above is the dependable fallback.
Keep QuickBooks open with the right company file before you open the download. If Desktop is closed, or a different company is open, the file can land somewhere you did not expect, which the last section covers.
An unsupported Desktop release that refuses Web Connect files
An old QuickBooks Desktop release can stop accepting Web Connect files even though nothing else has changed. Intuit's Web Connect error guide asks you to confirm you are on a supported version before trying any other fix. Bank services, including file imports, depend on Intuit's servers, and Intuit stops those services for older releases.
Check your version under Help, then About QuickBooks, and compare the year with Intuit's current list of supported releases. If yours has retired, an upgrade is the real fix. Desktop downloads after the version's support ends explains what keeps working and what stops.
Advanced mode and the Intuit sign-in
A newer requirement can look like a version problem. Intuit's guide says that importing .qbo files requires signing in to your Intuit account inside QuickBooks Desktop, and that Advanced Mode in bank feeds may need that sign-in or a mode switch. If QuickBooks asks you to sign in when you open the file, do so.
If the sign-in does not help, try the mode switch Intuit describes. Go to Banking, hover over Bank Feeds and select Change Bank Feeds Mode. Choose Classic mode, also called Register mode, then import the file again.
Is the download a QFX or a damaged QBO file?
The file can be the wrong type or cut short, and both stop it opening. Intuit's article on downloading bank feed transactions in QuickBooks Desktop says Web Connect only works with .qbo files, and that QFX and QIF Quicken files won't work.
Checking the file type
Banks often list several download choices with similar names: QuickBooks, Quicken, Microsoft Money, spreadsheet. A Quicken download ends in .qfx, and renaming it .qbo does not always make it acceptable. Go back to the bank's download page and pick the option marked for QuickBooks or Web Connect.
Checking for damage
A damaged or incomplete file usually produces Intuit's "we can't read the file" message. You can look inside a QBO file with Notepad, since it is plain text. A healthy one starts with a short header and contains tags in angle brackets. A file that is empty, shows a web page, or ends abruptly mid-line did not download properly.
The fix Intuit gives is to download the file again directly from the bank's website, not from inside QuickBooks, and confirm it is a .qbo file. If the bank's download itself fails, Intuit says the problem is likely with the bank.
Files you made yourself
A QBO file built by a converter or by hand can fail for different reasons, such as a missing account ID or a malformed date. SimpleBankConvert is being built to turn PDF statements into QBO files, the format Desktop opens. Accounts are not open yet, and you can get started to join the list.
A changed bank ID inside the Web Connect file
Every Web Connect file carries identifying details for the bank and the account. When a bank changes those details, or stops supporting Web Connect, QuickBooks can no longer match the file to what it knows. Intuit's guide lists both as causes, and the message is often "QuickBooks is unable to verify the Financial Institution information for this download."
Start at the bank, not in QuickBooks. Intuit's guide says to sign in to the bank's website, read any messages, and follow instructions such as confirming your identity. If the bank says it no longer offers Web Connect, disconnect the account in QuickBooks and use a different route for the transactions.
The OL errors that come with bank changes
Bank-side problems often show up as numbered OL errors instead of a plain message. If QuickBooks shows a code, the code is the better guide. What QuickBooks error OL-301 means and how to fix it and the fixes for QuickBooks error OL-222 each take one code from start to finish. Follow the post for your code instead of guessing at the file.
Disconnect and reconnect
When the bank is still on Web Connect but its details changed, Intuit's guide describes a reset. Disconnect the problem account, set it up again, then import the file. Link it to the same QuickBooks account as before so history stays in one place.
Testing the Web Connect file in a test company file
A test company file is a blank QuickBooks company you make only to try the import. It tells you whether the problem lives in your real company file or in the bank's download. Intuit's Web Connect error guide uses it as its main diagnostic step, and it takes about ten minutes.
Follow Intuit's steps:
- Select File, then New Company.
- Choose Express Start or Start Setup, fill in the fields, and add "Test" to the company name.
- Select Start Working.
- Import the .qbo file into the test company, using the same bank account as in your main file.
If the test import works
The bank file is fine and something in your company file is in the way. Intuit's guide says to open your original company file, disconnect the problem account, reconnect it, and import the file again.
If the test import fails
The file or the bank's setup is at fault. Intuit's guide says to get your Bank Log files before calling the bank, then speak with a representative who knows QuickBooks Bank Feeds. Ask them to confirm your accounts are set up for Web Connect. If needed, ask them to open a case through the Open Financial Exchange and note the case number.
Delete the test company afterwards, or at least name it clearly, so nobody enters real work in it.
A Web Connect file that opens into the wrong company file
Sometimes the Web Connect file opens fine but lands in a company you did not mean. This is a mistake of timing, not a broken file. Desktop imports into whichever company file is open, so a file opened while last year's archive or a client's company is open goes there.
Before you open any Web Connect file, check the company name in the QuickBooks title bar. If the file went into the wrong company, stop before you add or match the lines. Lines still waiting in review are easy to delete. Undoing an import that went into the wrong QuickBooks company walks through the clean-up once lines have posted.
Why opening the same file again may bring in nothing
There is a catch after a wrong import. Intuit's article on the "nothing imported" Web Connect error written for QuickBooks for Mac, explains that each transaction in a .qbo file has a unique ID, and QuickBooks will not import the same ID twice. Its first suggested fix is to restore a backup made before the earlier import, then import the file again. That is one more reason to back up before every Web Connect import.