Convert a Spreadsheet CSV to a Quicken Web Connect QFX

Why Quicken rejects a regular CSV

You would think a CSV of transactions would drop straight into Quicken, but it does not. Quicken for Windows accepts only one very specific CSV layout, the Mint-formatted export, and every other CSV has to be converted before Quicken will take it. A bank's CSV, a spreadsheet you built, or an app's export in any other column order simply is not recognized. What Quicken does read is a QFX Web Connect file, so the path for an arbitrary CSV is to turn it into a QFX first. That conversion re-packages your rows into the Web Connect format Quicken expects, so the same transactions import cleanly instead of being rejected.

Converting the CSV to QFX

The conversion maps your columns into the QFX structure. Starting from a CSV with clear headers on the first line, date, amount, payee, and memo, lets the converter assign each column correctly, and you can review the mapping before exporting if a column is ambiguous. The converter also writes the Web Connect identifiers a QFX needs, which is what separates a real QFX from a renamed CSV that Quicken would refuse. The result is a file carrying your exact transactions in the format Quicken imports, whether the CSV came from a bank that only exports spreadsheets or from your own records.

Importing the QFX into Quicken

Once you have the QFX, the import is quick. In Quicken for Windows choose File, then Import, then Web Connect file, and select the QFX you created. Quicken reads it and asks whether to create a new account or link to an existing one; pick Link and choose the matching account so the transactions post to the right register. Review the register afterward and delete any duplicates where the imported set overlaps transactions already present. This is the same Web Connect path Quicken uses for a file downloaded from a bank, so a converted CSV behaves just like a native download once it is in QFX form.

Categories: what QFX carries

One thing to know going in is that a QFX does not carry categories. Quicken assigns them after import using your renaming and memorized-payee rules, so the transactions arrive uncategorized and Quicken tags them by payee. If preserving categories from the source data matters more than a clean Web Connect import, a QIF file is the alternative, since QIF is the one common format that includes categories. For most CSV-to-Quicken jobs, though, QFX is the right target: it imports through the standard Web Connect route and lets Quicken's rules do the categorizing.

Accuracy and privacy

Because the conversion re-packages your rows rather than re-deriving them, the amounts, dates, and payees that import match the CSV you started from, and every transaction is reviewable before export so nothing is misread. The CSV holds real account activity, so it is processed to build the QFX and then deleted automatically, with nothing retained on a server afterward. For anyone converting a file on behalf of someone else, that automatic deletion keeps the account data from lingering in a third-party tool once the QFX is in Quicken.

Frequently Asked Questions