Overview: what you're doing and why
If your bank stopped downloading into Quicken — or only gives you PDF statements — the usual workaround is to export a CSV and hand-map the date, payee and amount columns on every import. It works, but it's slow and error-prone. Converting straight to a .QFX file removes that step: Quicken reads the structured Web Connect file directly. For the full product workflow, see bank statement to Quicken.
By the end of this guide you'll have a clean, balance-validated .QFX ready to import — and you'll know how to do a single statement or a whole year at once.
Before you start
- Your PDF bank statement(s) — digital or scanned, any bank.
- A working copy of Quicken for Windows or Mac.
- Knowing which Quicken account each statement belongs to.
There's nothing to install and no per-bank template to configure. Start from the bank statement converter or go straight to the PDF to QFX converter.
Step-by-step: PDF statement → .QFX
Step 1 — Upload the PDF
Open the converter and drop your statement. Digital and scanned PDFs both work, and multi-page statements are handled automatically.
Step 2 — Let the AI build the file
FlowParse extracts every transaction, normalises debits and credits into one signed amount, validates the running balance, and writes a valid .QFX (with .QBO and .OFX available too).
Step 3 — Review the preview
Check the editable preview. The validation report flags low-confidence fields, possible duplicates and any balance break so you can fix them before export.
Step 4 — Download the .QFX
Choose .QFX (Quicken), .QBO (QuickBooks) or .OFX and download. The file carries the account number, currency and a unique ID per transaction.
Importing the .QFX into Quicken
| Version | Steps |
|---|---|
| Quicken for Windows | File → File Import → Web Connect File (.QFX) → choose the file → link to the account → review and accept. |
| Quicken for Mac | File → Import → Bank or Brokerage File (OFX/QFX) → choose the .QFX → pick the account. |
Prefer QuickBooks? See PDF to QBO converter and bank statement to QuickBooks; for the generic format, PDF to OFX.
Worked examples
| Scenario | What to do |
|---|---|
| One monthly statement | Convert it directly to .QFX and import — under a minute end to end. |
| A full year, one account | Upload all 12 PDFs, consolidate with Smart Merge, then export the bank-feed file. |
| Several accounts & banks | Convert each account's statements separately so each .QFX links to the right Quicken account. |
| Bank dropped Direct Connect | Download the PDF statement instead and convert it to .QFX — Quicken stays current. |
Consolidating a year? Use Smart Merge and read how to consolidate a year of statements in minutes.
Common mistakes
- Exporting to CSV and hand-mapping columns when a .QFX imports automatically.
- Importing overlapping date ranges from a CSV and creating duplicates (no FITID to catch them).
- Skipping the balance check — always confirm opening + transactions = closing.
- Linking a multi-account statement to the wrong Quicken account.
- Downloading a .QBO when your software is Quicken — use the .QFX variant instead.
Best practices
- Always review the preview and resolve flagged fields before exporting.
- Keep one .QFX per account so each links cleanly to a Quicken register.
- Rely on the FITID for duplicate safety — re-imports are safe.
- Validate balances on every file; a reconciled statement is a trustworthy import.
- For a year of catch-up, consolidate first, then export — fewer files, fewer mistakes.
Convert your statement to QFX now
Upload a PDF and get a Quicken-ready .QFX in seconds — balance-validated, duplicate-safe, no column mapping.