QFX file not importing into Quicken: causes and fixes

What Quicken checks when you import a QFX file

QFX is Intuit’s variant of OFX for Quicken, and it carries an INTU.BID tag naming the financial institution. Quicken uses that tag to look the bank up in Intuit’s directory of participating institutions, and the bank has to be listed there with Web Connect enabled. Answers from Quicken Community moderators describe this as a connected step: Quicken checks the institution online, so a file is not simply read off the disk and trusted.

A file without a valid, Web Connect-enabled BID is not a slightly imperfect QFX. As far as Quicken is concerned it is not a QFX at all, and no amount of retrying changes the answer. The checks happen roughly in this order, and each has its own symptom.

“Unable to verify the financial institution information”

Quicken is currently unable to verify the financial institution information for this download.

This is the commonest QFX failure, and it is about the bank ID rather than your connection. A Quicken moderator summarised it in 2026 as one of two things: the institution does not support downloads into Quicken, or the institution information inside the file is wrong. The causes, most likely first:

• The bank no longer offers Web Connect. Bank of America ended all OFX services on 30 September 2025, so its QFX files are refused and Express Web Connect+ is the only supported connection; Quicken’s announcement on the Community says users trying a QFX import will see an error. Other banks have dropped Web Connect for one account type, often credit cards, while keeping it for checking.
• The INTU.BID is obsolete. After a merger or a website change, a bank sometimes keeps writing an old number that the directory no longer recognises. Quicken’s position is that this can only be corrected by the bank.
• The tag is missing or malformed. A file with no INTU.BID, or with it written without the dot, is really a plain OFX file with a .qfx extension.
• Quicken cannot reach Intuit’s servers, or the subscription has lapsed. Less common, but worth ruling out before editing anything.

1. 1Open the .qfx in a text editor such as Notepad. It is plain text.
2. 2Find the <FI> block near the top and read the <INTU.BID> value. If it is absent, you have an OFX file, not a QFX.
3. 3Compare it with the number in a QFX the same bank issued when imports last worked. A changed number points at the bank.
4. 4Check your bank’s download page for the current options. If Quicken is no longer listed, or only a direct connection is offered, file import has ended for that account.
5. 5If the bank still offers Web Connect and the file still fails, contact the bank and ask for someone familiar with Quicken downloads. The file comes from them, and so does the fix.

OL-221-A and “Unable to read the selected Web Connect file”

Unable to read the selected web connect file. Please contact your financial institution

These are structural rather than identity failures: Quicken could not parse the file far enough to ask who sent it. Quicken’s own Web Connect troubleshooting page gives a surprising first cause for OL-221: the computer’s date and time settings. Correct those before anything else, because it costs nothing.

• A missing element the format requires, such as the BANKID (routing number) on a bank account. Community threads show a file failing with OL-221-A until it was added.
• A file that was edited and saved by a program that changed its encoding or line endings, or added a byte-order mark before the header.
• A file that is empty, 0 KB, or cut short. Quicken’s troubleshooting page says an empty Web Connect file is something only the bank can fix.
• Transactions previously imported under an older bank ID, after a merger. Several threads report OL-221-A in exactly that situation.

Quicken records syntax problems in its connection log, under Help → Contact Quicken Support → Log Files. If the log names a tag, that is the line to look at in the file.

Files Quicken will not import at all

Some failures are not errors in the file but a format Quicken does not take through that route. Quicken’s Windows help states that it cannot import Excel, QuickBooks, PDF or OFX files. The Mac import menu is labelled differently, which is a common source of confusion when following instructions written for the other platform.

Two details matter in that table. Windows CSV import wants Quicken’s fixed columns (Date, Payee, FI Payee, Amount, Debit/Credit, Category, Account) with dates as mm/dd/yyyy. And Quicken’s help says CSV import does not check for existing transactions, so the same file imported twice is added twice.

Converted QFX files and what Quicken says about them

Quicken’s Web Connect troubleshooting page is direct about this: Quicken does not support QFX files created by third-party conversion software, PDF-to-QFX conversion included, and its support team will not help if one does not open. That is worth knowing before you rely on one.

In practice Quicken applies the same checks to every QFX file, wherever it came from. A converted file that carries your own bank’s current, Web Connect-enabled BID, a correct account number and well-formed tags goes through the same path as the bank’s own download. One that borrows another bank’s number to get past the check is a different matter: it misdescribes where the data came from, and it can tie the account to the wrong institution. Use your own bank’s number or a different format.

Transactions import but land in the wrong account

Quicken matches the file to an account by its ACCTID. If that number belongs to a different account than you intended, or the file carries a masked number while Quicken holds a full one, transactions land in the wrong register. Opening a .qfx by double-clicking hands it to Quicken’s Web Connect handler, which links automatically where it can; File → File Import → Web Connect (.QFX) File lets you choose to link to an existing account instead.

1. 1Back up first: File → Backup and Restore → Backup. Quicken’s help recommends this before any import.
2. 2If the transactions are still waiting in the downloaded transactions list, do not accept them. If they are already in the register, delete them or restore the backup.
3. 3Compare the ACCTID in the file with the account number recorded on the Quicken account, in the account details.
4. 4Import again through the File menu and choose Link to the correct existing account rather than accepting the default.

Everything imports twice

Quicken recognises a transaction it has already downloaded by its FITID, exactly as QuickBooks does. A converter that regenerates FITIDs on every run, from a timestamp or a row number, defeats that check entirely. Convert the same statement twice and compare the FITID values; if they differ, re-importing will always duplicate.

The other route to doubles is overlap with a live connection. If the account also downloads through One Step Update, Quicken may already hold transactions for the same period, and the FITIDs in your file will not agree with the bank’s. Import files only for periods the connection does not reach. Where the two must overlap, deactivate downloads for the account first, import, and reconnect afterwards.

Preventing the next failed import

• Keep one QFX the bank issued when imports worked. It is your reference for the right INTU.BID, ACCTID format and account type.
• Back up before every import, and import one account and one period at a time.
• Never edit a QFX in a word processor. Use a plain text editor, and save without changing the encoding.
• Watch your bank’s Quicken page and the Quicken Community alerts board. Discontinued connections are announced there, usually with the date.
• Reconcile the account against the statement’s closing balance after each import, while the period is fresh.

QFX, QIF or CSV, when you have the choice

• QFX carries an institution, so Quicken treats the transactions as bank data, with matching and duplicate detection. It needs a valid, Web Connect-enabled BID.
• QIF has no institution and no FITIDs. It imports into an account that already exists and never deduplicates, so each file must be imported exactly once. Older Quicken releases restricted QIF to cash, asset and liability accounts; Quicken’s current help says any account type now works.
• CSV in Quicken’s own layout is the newest route on Windows. It suits history from a bank that has left Web Connect, with the same caution as QIF about importing twice.