“Quicken will not let me import a QIF file into my bank account”
This one is not a broken file — it is a removed feature, which is why no amount of editing makes it work. Modern Quicken deliberately refuses QIF import into bank, credit card and investment accounts. The file is fine; the door is closed.
Symptoms
File → File Import → QIF File is greyed out, or your bank account is missing from the account list The import completes but the target account never appears as an option The same QIF file imports without complaint into GnuCash or an older Quicken
What actually causes it
QIF import is restricted by account type, by design
Quicken still accepts QIF for cash, asset, liability and invoice accounts, but not for bank, credit card, brokerage or 401(k) accounts. Intuit and later Quicken Inc. restricted this deliberately to push users toward Web Connect (QFX) and Direct Connect. Nothing about your file causes the refusal.
The file is a QIF that would work elsewhere
Because the restriction is on the destination account type rather than the data, a QIF that Quicken refuses may import perfectly into other software — which is why the file looks blameless when you inspect it.
How to fix it
- Check whether the file is actually valid first: drop it into the fixer below. If it reports structural problems, fix those — otherwise the file is not your obstacle.
- Convert the QIF to QFX only if your bank issues one: a genuine QFX carries a bank identifier that Intuit assigns, so no converter can legitimately manufacture one.
- The supported route is to export CSV from your bank instead, or to use the QIF with an account type Quicken still accepts and transfer the balance.
- If the transactions are historical and few, manual entry is often faster than fighting the restriction.
Related import problems
Skip the manual edit — fix it automatically
The fixer tells you whether the QIF itself is sound, so you can stop suspecting the file and address the real restriction. Free, no signup, no upload.
Open the fixer