CSV to QFX Converter

A CSV in, a Quicken-ready QFX out. Quicken is the strictest thing you are likely to import into — it checks the file's structure before it looks at a single transaction — so the output is written to the 1.0.2 specification rather than renamed from something close to it.

Quicken will not import a CSV. QFX is the format it was built to read.

Written for Quicken, not adapted

QFX is OFX with Intuit's own extensions, and Quicken refuses a file missing them. It is not enough to rename an OFX.

Dates that survive the crossing

Quicken reads dates as YYYYMMDD and nothing else. Whatever order your CSV wrote them in is worked out from the file and converted once.

Encoded the way the header claims

The file declares CHARSET:1252 and is written in it, so an accented payee arrives as itself. Writing UTF-8 under that declaration is how a name turns into mojibake inside Quicken.

Related guides

• OFX, QFX, QBO and QIF: Which Format Does Your Software Want?
• Why QuickBooks Rejects Your QBO File
• Why Your QIF Import Lands a Month Out
• How to Convert a CSV to QBO for QuickBooks
• Bank Feeds vs Statement Conversion: When You Need Each
• Bank Statement Converter vs Manual Data Entry: A Real Comparison
• Why Your Converted Bank Statement Doesn't Balance
• The Bank Statement Date Format Problem (DD/MM vs MM/DD)