A CSV to QFX converter wraps each spreadsheet row in the tags Quicken expects: a date, an amount, a payee and a unique ID. You need one only if you use Quicken. If your books live in QuickBooks, convert the CSV to a QBO file instead, because QuickBooks Desktop's Web Connect import reads only QBO files.
Who actually needs a CSV to QFX converter?
A CSV to QFX converter is for people who keep their accounts in Quicken and hold transactions in a spreadsheet instead of a bank download. If you use QuickBooks or Xero, you almost certainly do not need QFX at all, and picking it is the most common wrong turn.
QFX is the file type Quicken calls its own. A bank that supports Quicken offers it as a download, and Quicken reads it through a feature known as Web Connect. QuickBooks has a similar feature with a different file type, QBO. The two formats look nearly identical inside, which is why the names get mixed up.
Here is a quick way to decide:
- You open Quicken to see your accounts. QFX is the right target. Keep reading.
- You open QuickBooks Online or QuickBooks Desktop. You want QBO, or a plain CSV upload in Online. Skip to the section on making a QFX for QuickBooks.
- You use Xero. Xero takes a CSV directly, so no QFX is involved.
- You just want to look at the numbers. A CSV already opens in any spreadsheet. No conversion is needed.
Why would anyone have a CSV and need Quicken?
The usual cases are practical. A credit union gives you a spreadsheet export but no Quicken download. A small lender sends monthly payment histories as CSV. You track a side account by hand in Excel and want it inside Quicken with the rest. In each case the data is fine, only the container is wrong.
What a conversion cannot fix
A converter changes the container, not the content. If the CSV has the wrong dates, a flipped sign on the amounts or two rows merged into one, the QFX will carry the same mistakes, and Quicken will import them without complaint. Check the CSV first. Sort it by date, confirm that money going out is negative, and compare the total against the statement.
What fields does a QFX file need that your CSV lacks?
A QFX file needs a handful of fields that a typical bank CSV leaves out: a unique ID for every transaction, a currency, an account type and number, a statement date range, and an institution block that names the bank. A converter has to invent or ask for each one.
A CSV usually holds only four things: date, description, amount and sometimes a balance. QFX is stricter. It stores the file as text tags in the OFX family, with a header, a sign-on block that identifies the institution, an account block and then a list of transactions. Each transaction sits inside its own tag group.
The column to tag map
The table below shows how common CSV columns become QFX tags. The values are examples, not from a real account.
| CSV column | QFX tag | Example value | What to fill in when the CSV lacks it |
|---|---|---|---|
| Date | DTPOSTED | 20260314 | Nothing to invent, but the date must be rewritten as year, month, day with no separators |
| Amount | TRNAMT | -412.80 | Use one signed amount; money out is negative |
| Description | NAME | FLOUR SUPPLY CO | Shorten to the payee if the description is long |
| Memo or detail | MEMO | Invoice 2291 | Leave blank if there is none |
| (none) | FITID | 20260314-0001 | Build one per row, for example the date plus a counter |
| (none) | TRNTYPE | DEBIT | Set DEBIT for negative amounts, CREDIT for positive |
| Check number | CHECKNUM | 1042 | Only for checks; omit otherwise |
Two of those rows matter most. Dates change shape, so a CSV value like 3/14/2026 has to become 20260314. And FITID is the identifier that tells Quicken whether it has seen a transaction before.
Building a FITID when the CSV has none
FITID stands for financial institution transaction ID. Quicken uses it to avoid importing the same transaction twice. When your CSV has no ID, the converter has to create one, and the way it does so decides whether a second import duplicates everything.
A safe pattern is the posting date plus a running number within that date, so the third row dated March 14 gets 20260314-0003. The ID stays the same if you convert the same file again. A bad pattern is a random number or a timestamp from the moment of conversion, because every re-run then looks like a brand-new batch.
Rows that are truly identical, such as two coffees at the same price on the same day, still need different IDs. The counter handles that.
Other header values
Besides the transactions, the file declares the account number, an account type such as checking or credit card, a currency (USD for most US accounts) and the start and end dates of the batch. Set the start and end dates from the first and last transaction in the CSV, or from the statement period if you have it.
Why does Quicken reject a home-made QFX?
Quicken rejects a home-made QFX most often because the institution block does not match a bank it recognizes. The file can be well formed in every other way and still be refused, because Quicken checks who the file claims to come from before it reads a single transaction.
Inside the sign-on part of the file sits an institution block, with a name (ORG), a numeric ID (FID) and, in many Quicken files, an Intuit bank ID. Quicken looks at those values and tries to connect the file to a financial institution it knows. A file that names an institution it has never heard of may be refused, or may open a dialog asking you to pick or set up an account.
Practical ways around the check
You cannot reliably guess the right ID, so the workable options are modest:
- Reuse a real download. Download a QFX from the same bank, even for a different date range, and copy its institution values into the file you generate. This works because Quicken already accepts that bank.
- Import into an account you create by hand. In some Quicken versions you can import a file into a manually added account, so no bank link is needed. Behaviour differs between versions, so check your version's Help.
- Use a converter that asks for the bank. A good converter lets you choose or paste the institution values rather than hiding them.
Test before the full file
Convert a CSV with three rows first and import it into a spare Quicken account. Confirm that three transactions arrive, with the right dates and signs. Then delete the test account and run the whole file. The extra five minutes catches an institution problem before it touches real history. The same advice applies to every format, and the QFX to QBO converter guide shows the idea applied to a QuickBooks file.
Making a QFX for QuickBooks: the wrong target
Giving QuickBooks a QFX is the wrong target because QuickBooks is built around QBO. QuickBooks Desktop's Web Connect import reads only .qbo files, so a QFX is refused there. QuickBooks Online does accept a QFX upload, but QBO is its suggested type, so making a QFX gains you nothing.
The two formats share almost everything, so people assume one can stand in for the other. The difference lies in the institution block and in the file type each program asks for. For Desktop, Intuit's help article on Web Connect import errors is blunt: Web Connect reads .qbo files and nothing else. For Online, Intuit's help on manual uploads puts QBO first and treats QFX and CSV as fallbacks. The full explanation is in why QuickBooks turns away a valid QFX download.
What to do instead
If your destination is QuickBooks, pick the route by version:
- QuickBooks Online: upload the CSV directly through the bank upload screen, or convert to QBO. A CSV needs column mapping, a QBO file does not.
- QuickBooks Desktop: convert to QBO and bring it in through Web Connect.
- Either version, starting from a PDF statement: produce the CSV or QBO from the PDF itself, with no QFX step in between.
Our own product follows that last route. SimpleBankConvert turns a PDF bank statement into a CSV or QBO file, so a QFX is never part of the path to QuickBooks. It is still opening to early users, and you can join the list on the get started page.
A tell-tale sign you picked the wrong file
If a guide tells you to convert your CSV to QFX and then rename the extension to QBO, treat it with caution. Renaming does not change the contents, and the bank ID still points at the wrong software. Edit the header properly or use a tool that writes a QBO.
Can a Mac convert CSV to QFX without extra software?
A Mac can convert CSV to QFX without extra software only in the sense that the QFX is a text file, so a script or a text editor can produce one. There is no built-in Mac command for it, and Excel for Mac does not save to QFX.
Your realistic options on a Mac are these:
- A converter website or app. Several tools take a CSV and write a QFX. Read what each one asks for, particularly the bank values, and do not upload statements you would not want others to see unless the privacy terms are clear.
- Quicken for Mac itself. Quicken for Mac imports certain file types directly. Check the import menu in your version, because the supported formats have changed between releases.
- Build the text by hand. A QFX is plain text. A short script, or a spreadsheet that concatenates the tags into one column, can produce the transaction block. You then paste it between a header and a footer copied from a real download.
The spreadsheet route in outline
If you pick the third option, add a column that joins the fields into one STMTTRN group per row, using the map in the table above. Save the column as plain text, wrap it with the header and closing tags from a genuine download, and save the whole file with a .qfx extension. This is fiddly, and a single missing tag will make Quicken refuse the file, so run the three-row test first.
Where to go next
If you came here because a PDF statement is the real source, converting the PDF to a spreadsheet and then to QFX adds two steps you may not need. See whether to convert a PDF to QFX or to QBO. And if you hold a QuickBooks IIF file rather than a CSV, converting IIF to QBO covers that case. To print a Quicken or QuickBooks download instead, see turning QBO or QFX data into a printable report.