Fix "This is not a valid Web Connect file" in QuickBooks Desktop
QuickBooks Desktop rejects a .QBO when the file's header data doesn't match what it expects: a missing or wrong bank ID, a mismatched INTU.BID, malformed XML, or an expired QuickBooks version. The good news is the fix is almost always a small edit to the file's header or a switch to QuickBooks Online's upload screen, not a rebuild from scratch.
What the error actually means
When QuickBooks Desktop shows "This is not a valid Web Connect file", or throws an OL-301 / OL-249 style banking error during File > Utilities > Import > Web Connect Files, it is not saying your transactions are wrong. It is saying the header block at the top of the .QBO file failed validation.
Every Web Connect file is really an OFX document with a few QuickBooks-specific tags wedged into the header. QuickBooks reads those tags first, before it ever looks at a single transaction. If any of them are missing, blank, or don't match an entry in Intuit's internal financial-institution directory, the import is refused outright. Think of it as a bouncer checking ID at the door, the transactions inside never get a chance to be counted.
The usual culprits
- Missing or wrong
<BANKID>/ routing number. The header needs a bank routing/ID value. A blank or fictional one fails validation. - Mismatched
INTU.BID(the Intuit branding ID). This is the single most common cause of OL-301 / OL-249. TheFIDandINTU.BIDin the file must correspond to a financial institution QuickBooks recognizes. If your bank or converter wrote a value QuickBooks doesn't have on file, it is rejected. - Malformed or truncated XML/OFX structure. A missing closing tag, a stray character, or a file that got cut off mid-download will not parse.
- Wrong encoding or extension. A file saved as
.qbo.txt, UTF-16, or with a byte-order mark can trip the parser. - An expired QuickBooks version. Intuit sunsets bank-feed services on older Desktop years. Once your version is past its service date, Web Connect imports stop working regardless of how clean the file is.
If you built the .QBO yourself from a spreadsheet, the most likely issue is the bank-ID/branding header, which is exactly what a good converter lets you set.
Fix 1, Set the right bank ID and branding when you convert
The cleanest fix is to generate the .QBO with valid header values in the first place. When you use QBO Maker to turn your bank's CSV or Excel export into a .QBO, you control the BANKID, account number, account type, and the Intuit branding ID, so the file passes Desktop's header check on the first try.
- Export your transactions from your bank as CSV or Excel.
- Open the converter, map your date, description, and amount columns.
- Enter your routing/bank ID and account number, and pick an account type that matches (checking, savings, or credit card).
- Download the .QBO and import it through File > Utilities > Import > Web Connect Files.
Everything runs in your browser, your statement data is never uploaded. If your goal is Quicken or another app instead of QuickBooks Desktop, see CSV to QFX and CSV to OFX.
Fix 2, Edit the header of a .QBO your bank gave you
If the bank handed you a .QBO that QuickBooks rejects, you can repair the header in a plain text editor. Make a backup copy first.
- Right-click the .QBO and open it with Notepad (Windows) or TextEdit in plain-text mode (Mac), not Word.
- Near the top, find the lines containing
<FID>,INTU.BID, and<BANKID>. - Replace the rejected values with ones QuickBooks accepts. A widely used safe fallback is a generic institution ID such as
3000, or you can match your bank's published FID from Intuit's financial-institution directory. - Save the file without changing the extension, keep it as
.qbo, encoded as plain ANSI/UTF-8 with no BOM. - Re-import through Web Connect.
This works, but it is fiddly and easy to corrupt the XML. If you are doing it more than once, it is faster to regenerate the file from your CSV with the correct header baked in. You can also confirm a file's structure with the OFX/QBO validator before you import.
Fix 3, Skip Desktop and upload to QuickBooks Online
QuickBooks Online does not use the Web Connect header validation the same way Desktop does, so a file that fails on Desktop will often import cleanly online. If you use QBO Online (or you are open to it), this sidesteps the OL-301 / OL-249 problem entirely.
- In QuickBooks Online, go to Transactions > Bank transactions.
- Choose the account, then Upload from file (you can upload .QBO/.OFX, and QBO also accepts CSV directly).
- Map the columns if prompted, then review and accept the transactions.
For a full walkthrough of going straight from a spreadsheet into QuickBooks Online, see Import CSV into QuickBooks Online.
When it's the QuickBooks version, not the file
If every Web Connect file you try fails, including known-good ones, the problem is probably your QuickBooks Desktop year rather than any single file. Intuit discontinues bank-feed and Web Connect services for older Desktop versions on a rolling schedule. Once a version is past its sunset date, the only paths forward are upgrading Desktop to a supported year, or moving your bank imports to QuickBooks Online. A converted .QBO with a perfect header still won't import into a version whose bank feeds have been switched off.
Frequently asked questions
Does OL-301 mean my .QBO file is corrupted?
Not necessarily. OL-301 and OL-249 most often point to a header mismatch, typically the FID / INTU.BID not matching a financial institution QuickBooks recognizes, rather than damaged transaction data. Editing the header or regenerating the file with correct IDs usually clears it.
What value should I use for INTU.BID?
Use the official ID that matches your bank from Intuit's financial-institution directory when you can. If you can't find it, a common generic fallback that QuickBooks accepts is 3000. When you build the file with QBO Maker, you set the bank/branding values up front so you avoid guessing entirely.
Can QuickBooks import a PDF or scanned statement this way?
No. Web Connect import expects a structured .QBO/OFX file, not a PDF. QBO Maker converts CSV or Excel exports into .QBO, so if you only have a PDF you'll first need a CSV/Excel version of the same statement from your bank.
Will editing the .QBO in Notepad change my transaction amounts?
It shouldn't, as long as you only touch the header lines (FID, INTU.BID, BANKID) and save as plain text with the .qbo extension. Always keep a backup copy in case a stray edit breaks the XML structure.
I fixed the header but QuickBooks still won't import. Now what?
Run the file through the validator to confirm the OFX structure is intact, then check your QuickBooks Desktop year, expired versions have bank feeds turned off and will reject any Web Connect file. If your version is sunset, upload to QuickBooks Online instead.