A Quicken QFX import error almost always traces to one of four things: the bank ID inside the file, an account already linked to another bank, a file Quicken can no longer authorise, or Quicken itself being out of date or unsubscribed. Find which one applies, fix that part, and import the same file again with a backup in hand.
Sorting a Quicken QFX import error by its cause
A Quicken QFX import error comes from the file, the Quicken account, Quicken's own status or the computer. The message wording varies by version, so sort by what you see rather than by the exact text. The table below groups the common symptoms; the sections after it explain each fix.
| What you see | Likely cause | First fix |
|---|---|---|
| Quicken names the wrong bank, or refuses the institution | The bank ID in the file is not one Quicken recognises | Download again from the bank in the Quicken format |
| Quicken will not link the file to your usual account | The account is set to download from a different institution | Change or turn off the account's online services, then link |
| A file that worked last year now fails | The bank stopped supporting Web Connect, or the file was converted | Ask the bank for a fresh download |
| Quicken says it cannot download or validate | Subscription lapsed or version unsupported | Renew, or update Quicken |
| Error OL-221 on Windows | Wrong system date and time | Correct the Windows clock |
| Double-click opens another program or nothing | Broken file association | Reset .qfx to open with Quicken, or use the File menu |
| The import finishes with nothing in it | The file is empty | Contact the bank, which supplies the file |
Quicken's Web Connect troubleshooting page for Windows is the source for the last five rows. Quicken for Mac has its own Web Connect troubleshooting page, which covers the empty file, converted files, subscription status and OL-221, but not the Windows file association.
One thing to rule out first: a QFX is a bank download, not a Quicken data file. If what you are trying to open ends in .qdf, that is a whole Quicken data file, and converting a QDF file to QFX explains why the two are not interchangeable.
Is the bank ID inside the QFX file the problem?
The bank ID is the first thing to check when Quicken refuses the institution or names the wrong bank. A QFX is built on the OFX standard, and the OFX 2.2 specification from the Financial Data Exchange describes a sign-on block that can carry an FI aggregate: the institution's name, in ORG, and its ID, in FID.
A Quicken download usually adds an Intuit line, INTU.BID, near the same spot. Quicken reads these to decide which bank sent the file and whether that bank is set up for Web Connect.
To look without changing anything:
- Copy the QFX file and work on the copy.
- Open the copy in Notepad or TextEdit.
- Near the top, find the lines starting
<ORG>,<FID>and<INTU.BID>. - Note the values. They should belong to the bank you downloaded from.
If the values name a different bank, or are missing, the file came from somewhere other than a normal bank download. A bank that recently merged or changed its online banking provider can also start issuing a new ID. Either way, the fix belongs with the bank: download again in the Quicken format, and ask the bank if the problem returns.
Editing the bank ID by hand to force a file through is a workaround some users try. Quicken does not support it, and a typo can make the whole file unreadable. Avoid it on your real data. The structure of OFX and QFX files in general is covered in how Quicken handles OFX files.
QFX downloads aimed at an account linked to another bank
Quicken ties each account's downloads to one financial institution. When a QFX file comes from a different institution than the one an account is set to download from, Quicken may refuse to link the two, or offer to create a new account instead. This often follows a bank merger or switching an account between connection methods.
The account side is where to look. In Quicken, open the account's details and find its online services or download settings. The institution named there should match the bank in your QFX. If it names an older bank, or a connection method you no longer use, the file and the account disagree.
The general fix has three steps:
- Back up the Quicken data file.
- Turn off, or deactivate, the account's current online services in its account details.
- Import the QFX again and choose Link with the existing account when asked.
Do not take the offer of a new account to get past the error. The transactions would land in a separate account, and your real register would miss them. Merging two accounts afterwards takes far longer than resetting the link.
If two Quicken accounts both point at the same bank account, deactivate the one you no longer use. Two links to one account make every future import ask the question again.
Old or converted QFX files that Quicken will not authorise
A QFX file that worked before can fail later because Quicken checks it online. Quicken's Mac troubleshooting page says Web Connect files need online services to validate the file and its transactions. The Windows page adds that a file cannot be authorised once the bank no longer supports Web Connect in Quicken.
That explains the most confusing case: an old download sitting in a folder, or a fresh one from a bank that has just changed its systems, fails even though nothing in it is damaged. The file is fine; the permission behind it has gone.
Files made by conversion tools
Both Quicken troubleshooting pages say Quicken does not support QFX files created by third-party conversion software. That covers tools that turn a PDF, CSV or spreadsheet into QFX. Some of these files import; others fail at the authorisation step. Quicken support will not help with them either way.
If the file came from a converter, ask the bank for a genuine Quicken download for the same dates. If the bank cannot provide one, use a route Quicken does support for that data, such as a spreadsheet import, rather than repeatedly converting the file.
Empty files
A QFX of 0 KB, or one with no transactions, is a bank problem. Both troubleshooting pages say only the financial institution can fix it. Check the date range you asked for first; a range with no activity can produce an empty file honestly.
Does Quicken's subscription or update status block a QFX import?
Quicken's own status can block a QFX import before the file is even read. Both troubleshooting pages say you cannot download a Web Connect file if your subscription has expired or your version of Quicken is unsupported. Because Web Connect validates online, Quicken has to be current and connected for the import to work.
Check these inside Quicken:
- Subscription. Sign in to your Quicken account and confirm the membership is active.
- Version. Install the latest update for your version. On Windows, Help has a check for updates option.
- Connection. Make sure Quicken can reach the internet. A firewall or VPN that blocks Quicken can look like a file error.
If your plan lapsed and you renew, import the same file again. You do not need a new download unless the bank has changed something in the meantime.
Some people hit this wall while they are deciding whether to stay with Quicken. If the business side is moving to QuickBooks Online, bank history is only one part. Lists such as open quotes come across separately, which importing estimates into QuickBooks Online covers.
Windows date and file settings behind a QFX import error
Two Windows settings cause QFX import errors that look like file problems. Quicken's Windows troubleshooting page says error OL-221 may be caused by the system date and time, and that a wrong or damaged file association can break the Web Connect session. Neither involves the file itself.
For OL-221, open Control Panel, then Clock, Language, and Region, then Date and Time, and set the correct date and time. Then import again. The Windows page says that if the error continues, the file may be at fault and you should contact the bank.
For the file association, Windows needs to know that .qfx files open with Quicken. The Windows page points to Default Programs in Windows 10 and to choosing defaults by file type in Windows 11. While you sort that out, you can skip the association entirely: in Quicken, open File, then File Import, then Web Connect (.QFX) File, and pick the download.
One more Windows detail from the same page: QIF files do not work with Web Connect. If your bank's download ends in .qif, the QFX import route will never accept it, whatever the settings.
Retrying a failed QFX import without creating duplicates
A retry is safe when nothing from the failed attempt reached the register. Some failures stop at the first screen; others bring in part of a file. Before importing again, check the account register for lines from the file's date range, and back up the data file so you can return to this point.
Work through this checklist before the retry:
- A fresh backup of the Quicken data file exists.
- The register shows no lines from the failed attempt, or you have deleted them.
- You know which fix you applied: bank ID, account link, subscription, update or Windows setting.
- The file is the original bank download, not a copy saved from Excel or a word processor.
- The date range starts the day after the last bank transaction already in the register.
If the retry brings in lines you already had, review them before accepting and delete true repeats. If it fails with the same message twice after a real fix, stop retrying and contact the bank with the message text and the date range. Repeated attempts with a broken file only add clean-up.
When the transactions you need are only in PDF statements and your books are in QuickBooks Online or Xero rather than Quicken, SimpleBankConvert is being built to make an import-ready CSV or QBO file from the PDF. Get started to hear when it opens.