OFXCSV / Practical guide

Quicken QFX to CSV: retain transaction meaning for another import

Prepare a flat transaction file from bank QFX while preserving IDs, memo fields and correction evidence.

Check which source file you have

To turn a Quicken QFX file into CSV, first confirm that it is actually .qfx bank-statement data. It is different from a Quicken application data file or a full backup. If your bank offers CSV for the same period, that may avoid a converter purchase. If you already use Quicken and it accepts the QFX, its own export may be enough: Quicken for Mac offers File, Export, Register Transactions to CSV File, and Quicken reports offer Export Data, Export to Excel Workbook; inspect the columns and date range before converting a separate file. Keep the original QFX unchanged. Conversion can preserve fields present in that file; it cannot reconstruct categories, attachments or transaction splits that are absent from it.

Specify the receiving system's columns

Before flattening the file, find out what the next importer needs. It may want one description column while the source separates Name and Memo. Keep both in your review table and combine them only in a destination-specific copy if required. Preserve account ID, transaction ID, check number, amount and source statement identity. Do not discard original timestamps just because the destination asks for a calendar date. A plain CSV is useful for transfer, while a separate workbook can hold account snapshots and the decisions you made during preparation.

Preserve identifiers through the spreadsheet

Open CSV through the spreadsheet's text/data import workflow and set identifiers to Text. A long account number, a leading-zero check number or an alphanumeric FITID must remain an identifier rather than a quantity. Check how non-ASCII descriptions and quoted commas appear after import. Do not let a spreadsheet convert a date before you have confirmed its meaning. Compare the source's signed amount rather than assigning a sign from the word payment alone, since a credit-card payment and a bank-account withdrawal describe different sides of related activity.

Handle corrections and overlapping periods

QFX can carry correction references as well as ordinary transaction records. A converter that retains those fields has not necessarily applied their delete or replace meaning. Review them before computing totals or sending the rows to a new importer. Two downloads can overlap, and two legitimate purchases can have identical dates, descriptions and amounts. Compare account and transaction IDs and the source evidence before removing anything. Retain a copy of excluded records with the reason so an unexpected count difference can be explained later rather than guessed from the final spreadsheet.

Verify the transfer at both ends

Count rows by account and statement, check the period boundaries and compare a known charge, refund and payment. Keep currencies separate and treat balance snapshots as context rather than activity. Test a short period in the destination using a backup where possible. After import, compare what was accepted, skipped or marked duplicate with your working file. CSV conversion does not enroll an institution or guarantee a particular application's import behavior. Use the application's own supported workflow and retain the original QFX even after the flat table appears to work.

Decide between a register export and the original QFX

A Quicken register can contain later edits and categorization that a bank-issued QFX never carried. If those decisions are part of the required handoff, inspect Quicken's own export rather than expecting a statement parser to reconstruct them. If you need the bank's original statement facts, retain the QFX as the source and describe the output accordingly. Write down which source supplied each delivery table. A difference between a register row and a bank-file row is a question to investigate; it does not by itself prove that either export failed or that all differences should be removed.

Review a replacement instruction before a second import

Suppose the source includes a transaction and a later record referring to its identifier as a replacement. Flattening both records can preserve the evidence while leaving two visible amounts in the CSV. Inspect the correction action and referenced transaction before calculating activity or importing the rows elsewhere. Make a reviewed delivery copy and keep a note explaining any exclusion or replacement you apply. Do not treat every repeated identifier as an ordinary exact duplicate, and do not assume the next CSV importer understands correction fields. The preserved source and your explicit decision trail are what make the transfer reviewable.

Where OFXCSV fits

OFXCSV preserves a bank/card QFX file's account and statement references, currencies, transaction types, FITIDs, check numbers, separate Name/Memo and original timestamps alongside date text. It retains correction references without applying their instructions. CSV contains transaction rows; the complete XLSX includes Transactions, Accounts and Validation sheets. It cannot extract categories absent from the input or read a Quicken application backup. Limits are one file, 15 MiB, 3,000 transactions and 100 accounts. A no-card account trial provides ten transactions; full output from longer sources requires a new paid upload. Download checked results before their 24-hour expiry.

Try a real free conversion See one-time packs

Written by Zijian Xiao. Examples are synthetic. Review all extracted results against your original source file.