Bank statement PDF to QFX for Quicken
Quicken users hit this wall when rebuilding a file after a crash, importing an old account, or bringing in a bank that Quicken cannot connect to directly. The statements exist as PDFs; Quicken wants QFX or a mapped CSV.
Drop a PDF statement to start
Drop your PDF statement here
or click to browse · 10MB max · nothing is stored
The two routes into Quicken
Recent Quicken versions accept a CSV import with column mapping, which is the shortest path from a converted statement. The alternative is generating a QFX file from the verified rows, which is worth the extra step only if your version refuses CSV.
Mapping columns in Quicken
During import, map date to date, description to payee, and the signed amount to amount. Leave the balance column unmapped: Quicken maintains its own running balance and importing one can create reconciliation noise.
Avoiding duplicate transactions
Quicken matches on date, amount and payee. If the account is also connected for downloads, import the statement period only up to the point where downloads begin, then let the connection handle everything after that.
Reconciling after import
Run a reconcile against the statement's closing balance immediately after importing. If it matches, the period is finished and you can move to the next statement with confidence.
Frequently asked questions
+Can Quicken import CSV?
Recent Quicken releases support CSV import with column mapping. Older versions may require QFX or QIF.
+Should I import the balance column?
No. Let Quicken calculate the running balance and use the statement's closing figure only to reconcile.
+Does this work for credit card accounts in Quicken?
Yes, with purchases negative and payments positive, which matches how Quicken treats a liability account.