Getting transactions into Quicken when your bank has no Web Connect

What Quicken actually accepts

Checked on Quicken's own support pages on 12 September 2026. Formats change between versions, so if yours behaves differently, believe your copy rather than this page.

• .QFX, which Quicken calls a Web Connect file. Downloaded from your bank's own site. Imported with File, then File Import, then Quicken Transfer Format (.QFX) File.
• .QIF, the old Quicken Interchange Format. Still imported, with a restriction that is worth its own section below.
• .CSV, in a layout Quicken specifies down to the column order.
• .QXF, which is for moving data between Quicken files, not for bank statements.

And the line that sends most people here in the first place, from Quicken's Windows import page: "Quicken cannot import Excel (.xls), QuickBooks, PDF, or OFX files."

That matters because plenty of banks outside the United States will happily hand you an OFX file and nothing else. OFX is the open standard. QFX is the same format with Intuit's own identifier added, and Quicken checks for it.

Check whether your bank hides a QFX download

Before converting anything, look again at the download options in online banking. Banks label this badly and the QFX option is often there under a name nobody would guess.

Things to look for: Quicken, Web Connect, Download to Quicken, or a dropdown of formats next to the date range. Sometimes it only appears once you have chosen a date range, and sometimes it lives on the statements page rather than the transactions page. Quicken's help describes QFX as the format used when a bank does not support the live connection methods, which is the situation most people are in when they start searching.

If the QFX is there, use it. It carries a unique ID per transaction, so Quicken can tell a repeat import from a new one.

The free route: Quicken's own CSV import on Windows

Quicken for Windows will import a CSV of transactions, and it is specific about the shape. From Quicken's help page, the menu is File, then File Import, then Banking Transactions, then From (.CSV) File, and the columns must appear in this order:

1. Date
2. Payee
3. FI Payee
4. Amount
5. Debit/Credit
6. Category
7. Account
8. Tag
9. Memo
10. Chknum

Date, Payee, Amount and Account have to contain values. The others can be empty but the columns still have to be there. On dates, the help page is blunt: "Date values must follow the Quicken mm/dd/yyyy format. Leading zeros are optional for single-digit months and days."

Two limits it states outright, both worth knowing before you import rather than after. CSV import does not detect or create transfers, so money moving between two of your own accounts arrives as two unrelated transactions. And CSV imports do not match against what is already in the register, so importing the same file twice gives you everything twice.

So the job is: open your bank's CSV, move the columns into that order, insert the empty ones, rewrite the dates as month first, save as CSV, import. For one month that is fifteen minutes. For two years of a business account it is an evening, mostly spent on the date column.

On a Mac it is a different menu item with different rules

Quicken for Mac does not have the same CSV import. Its route is File, then Import, then Mint.com File (CSV), and the column list is its own: Date, Payee, Category, Amount, Debit/Credit, Notes, Labels, Account. Date, Amount and Account need values, the rest can be blank but must exist as columns.

Two things Quicken's Mac page says that catch people out. The Debit/Credit column wants the words in lower case. And the import "will always create a new account with the same name as the imported file", so you cannot aim it at the account you already have. People work around that by importing, then moving the transactions, which is fine for a one-off and miserable as a monthly habit.

Worth noting: the Mac page gives the acceptable date format as day first, while the Windows page demands month first. I am not going to pretend to reconcile that. Open the help page for your own platform and version before you rewrite a date column to match the wrong one.

QIF, and why Quicken's own pages disagree about it

QIF is the oldest route and the one with the most folklore attached.

Quicken's Windows import page says QIF import "is available only for asset and liability accounts (including house and vehicle) and cash accounts", and not for checking, savings or credit card accounts, nor for 401(k) or brokerage accounts, with an exception for accounts payable and invoice accounts in Quicken Business & Personal.

Quicken's own QIF help page, on a different site it also runs, says the opposite: "While older versions of Quicken did not have this capability, you can now import any account type using QIF."

Both were live on 12 September 2026. I cannot tell you which applies to your build, and anyone who tells you confidently is guessing. The test takes two minutes: make a QIF with one transaction in it and see whether the account you care about appears in the destination list.

Back up first, because none of this undoes cleanly

Quicken has no single undo for an import. A QIF or CSV import that lands in the wrong account, or with every date a month out, leaves you deleting transactions by hand unless you have a file to go back to.

So: back up the Quicken file, import one month rather than two years, then compare the closing balance against the real statement. The balance is the one number that catches a missing transaction, a duplicate and a sign error at once. If it is out, restore the backup rather than patching the register.

What this site makes, and what it does not

This site does not produce QFX and will not. A QFX needs an INTU.BID value, a key into Intuit's directory of banks registered for Quicken Web Connect. I have no registration, and an invented value either gets refused on import or quietly labels your file as coming from a bank that is not yours.

What is here is a converter that reads a bank CSV, QIF or OFX and writes a clean OFX, which is the right file for GnuCash, Xero, YNAB and QuickBooks Online. It is not the right file for Quicken, for the reason quoted at the top.

The one that helps a Quicken user is the spreadsheet converter, because the hard part of the CSV route is getting your export into a sheet where the dates are real dates and the amounts are real numbers. Once they are, rearranging ten columns is mechanical. It will not hand you a file Quicken imports untouched.

Questions, answered.