QFX to CSV Converter Online Free | Quicken Bank Export

QFX to CSV Converter

QFX is the Quicken-oriented bank download format you usually get when online banking offers a “Quicken” or Web Connect export. Under the hood it is an OFX-style SGML document: account metadata plus a list of statement transactions with posted dates, amounts, payee names, memos, and financial institution transaction IDs (FITIDs). Spreadsheets and many custom importers do not open QFX natively. This free QFX to CSV converter at /finance-file-converter/qfx-to-csv turns those transactions into a flat table you can open in Excel, Google Sheets, Numbers, or a bookkeeping workflow that expects CSV.

Paste a QFX file or upload a .qfx download from your bank. The tool runs entirely in your browser: it reads the OFX/QFX structure, extracts statement transactions, and emits RFC 4180–compatible CSV with columns such as Date, Description, Amount, Memo, and FITID. Nothing from the conversion step is uploaded to a Convert CSV server just to produce the output.

The sections below explain how QFX relates to OFX, what fields typically land in the CSV, how to import the result cleanly in Excel and Google Sheets, common bank and Quicken export pitfalls, privacy considerations for client-side conversion, and related tools on the Finance File Converter hub (including QFX to XLSX, QFX to OFX, OFX to QFX, and QIF to CSV).

Key features

Parses Quicken-oriented QFX / OFX-style statement downloads in the browser and maps statement transactions to CSV rows.
Extracts the fields people actually reconcile on: Date, Description (payee/name), Amount, Memo, and FITID when present in the file.
Produces comma-separated, quoted CSV suitable for Excel, Google Sheets, Numbers, and most CSV importers.
Accepts paste or .qfx file upload so you can move from a bank download folder to a spreadsheet without a desktop converter.
Runs client-side so transaction contents are not uploaded to a server as part of the conversion step.
Fits the Finance File Converter workflow alongside QFX to XLSX, QFX to OFX, OFX to QFX, and QIF to CSV when you need a different target format.
Keeps conversion practical for everyday monthly downloads rather than requiring Quicken installed just to inspect the same transactions.

About the QFX to CSV format

OFX (Open Financial Exchange) is a structured financial download format. Banks and brokerages use it so desktop and web apps can import statements with typed fields instead of scraping PDF text. A typical OFX/QFX file starts with a short header block (OFXHEADER, DATA, VERSION, ENCODING, and related keys), then an <OFX> body that may include sign-on responses, bank or credit-card message sets, account identifiers, ledger balances, and a list of <STMTTRN> (statement transaction) elements.

QFX is Intuit’s common OFX-based variant used with Quicken and many “download for Quicken” bank menus. In practice the transaction payload looks like OFX: you will see <TRNTYPE>, <DTPOSTED>, <TRNAMT>, <FITID>, <NAME>, and often <MEMO>. Filenames usually end in .qfx. Renaming .qfx to .ofx does not reliably make every app treat the file as generic OFX — some products check Intuit-specific markers or expect a true OFX download. Prefer a dedicated QFX to OFX converter when another system needs OFX, and use this QFX to CSV path when humans need a spreadsheet.

CSV is a flat table: one header row, then one row per transaction, with comma-separated fields and quoting when a value contains commas, quotes, or line breaks. Converting QFX to CSV deliberately discards hierarchical OFX wrappers and keeps the transaction facts that matter for reconciliation and analysis. Account metadata may appear as columns when present, but the primary unit of the output is one statement transaction per row. Keep the original .qfx as the audit artifact; treat the CSV as a working copy for filters, pivots, and shared review.

How it works

The converter reads your QFX text as an OFX-family document. After the optional OFX header lines, it locates the transaction list inside the OFX body — typically <STMTTRN> elements under a bank or credit-card statement response. Each transaction block is treated as one candidate row.

For every transaction it pulls the practical fields: posted date (<DTPOSTED>), amount (<TRNAMT>), description/payee (<NAME> or equivalent), memo (<MEMO> when present), FITID (<FITID>), and related tags such as transaction type when useful for the table. Dates are normalized into a spreadsheet-friendly form; amounts keep the signed OFX convention (debits negative, credits positive, depending on how the bank encoded them).

The tool then writes a header row and one CSV row per transaction. Values that contain commas, quotes, or newlines are escaped per common CSV rules so payee strings like "ACME, INC" stay in one cell. The result is a UTF-8 CSV string you can copy or download as a .csv file and open in Excel or Google Sheets.

Common use cases

Downloading a monthly Quicken/Web Connect .qfx from online banking and reviewing transactions in Excel before posting summaries to the ledger.
Normalizing QFX exports from multiple banks into one CSV schema for a cash dashboard or multi-account reconciliation workbook.
Extracting Date, Description, Amount, Memo, and FITID so a bookkeeper can categorize spend without installing Quicken.
Preparing a shareable transaction list for a client or stakeholder who only works in Google Sheets.
Archiving structured bank history as CSV for long-term storage while retaining the original QFX for re-import into Quicken if needed.
Cleaning payee names and memos in a spreadsheet after conversion, then feeding a custom importer that accepts CSV only.

How to use this tool

Download a .qfx (Quicken / Web Connect) file from your bank or brokerage for the date range you need.
Open /finance-file-converter/qfx-to-csv, then paste the file contents or upload the .qfx.
Review the preview: confirm row count, Date/Description/Amount/Memo/FITID columns, and a few sample payees.
Download or copy the CSV, then open it with Excel’s Text Import / Get Data (UTF-8) or upload it to Google Sheets.
Reconcile totals and keep the original .qfx alongside the CSV; redact account details before sharing the sheet.

Example

Input QFX (excerpt)

OFXHEADER:100
DATA:OFXSGML
VERSION:102
SECURITY:NONE
ENCODING:USASCII
CHARSET:1252
COMPRESSION:NONE
OLDFILEUID:NONE
NEWFILEUID:NONE

<OFX>
<BANKMSGSRSV1>
<STMTTRNRS>
<STMTRS>
<BANKTRANLIST>
<STMTTRN>
<TRNTYPE>DEBIT
<DTPOSTED>20260315
<TRNAMT>-45.99
<FITID>20260315004599
<NAME>CLOUD HOSTING INC
<MEMO>INV-88421
</STMTTRN>
<STMTTRN>
<TRNTYPE>CREDIT
<DTPOSTED>20260318
<TRNAMT>1200.00
<FITID>20260318012000
<NAME>ACME CLIENT PAYMENT
<MEMO>INVOICE 1042
</STMTTRN>
</BANKTRANLIST>
</STMTRS>
</STMTTRNRS>
</BANKMSGSRSV1>
</OFX>

Output CSV

Date,Description,Amount,Memo,FITID
2026-03-15,CLOUD HOSTING INC,-45.99,INV-88421,20260315004599
2026-03-18,ACME CLIENT PAYMENT,1200.00,INVOICE 1042,20260318012000

Tips for best results

Prefer the bank’s Quicken/QFX or OFX download over PDF statements whenever both are offered — structured fields convert more reliably than OCR or PDF table extraction.
Keep the FITID column in the CSV. It is the bank’s unique transaction id and is the best defense against duplicate imports later.
Spot-check the first and last few dates and the sum of Amount against the statement balance or online banking totals before you rely on the sheet.
Import as UTF-8 text in Excel when payee names include accents or non-ASCII characters; double-clicking a CSV can mojibake on some Windows Excel setups.
Format the Amount column as Number (or Accounting) after open, and format Date columns explicitly so regional date guessing does not scramble the month and day.
If you need a native Excel workbook instead of CSV, use the related QFX to XLSX tool on the Finance File Converter hub after you confirm the same transactions look right here.
Redact or truncate account numbers before emailing a converted CSV. QFX files often contain account identifiers that do not belong in a shared spreadsheet.

Common errors and how to fix them

The tool shows no transactions or an empty CSV after I paste a file.: Confirm the file is actually QFX/OFX text with <STMTTRN> (or equivalent statement transaction) blocks, not a PDF renamed to .qfx and not a QIF/IIF export. Open the file in a plain-text editor: you should see OFXHEADER or <OFX> tags. If you only have a PDF statement, use a PDF bank-statement path instead of QFX to CSV.
Payee names look fine in QFX but appear garbled in Excel after download.: This is usually an Excel encoding issue on open, not a missing field in the converter. Import the CSV via Data → From Text / Get Data, choose UTF-8, and set the delimiter to comma. Google Sheets uploads typically handle UTF-8 more gracefully.
Dates show the wrong month or day after I open the CSV.: Spreadsheet apps guess date formats from your locale. Use an explicit import step and set the Date column type, or format the column as Date after verifying a known transaction (for example a paycheck date). Compare against the <DTPOSTED> values in the original QFX if anything looks swapped.
Amounts do not sum to my online banking total.: Check for pending vs posted differences, excluded transfers, and whether the download date range matches the statement. Also verify debit/credit signs: OFX amounts are signed, and some banks encode card purchases differently than checking debits. Filter the CSV to the same window you are reconciling and compare FITID counts to the bank UI when possible.
Memo is blank for many rows even though Description is filled.: Many banks put the readable payee only in <NAME> and leave <MEMO> empty or use memo for reference numbers only. That is a source-data limitation. Use Description for categorization, and treat Memo as optional enrichment when present.
I need OFX for another app, but I only have QFX — or the reverse.: Use the related QFX to OFX or OFX to QFX tools on the Finance File Converter hub rather than renaming extensions. Use this QFX to CSV page when the destination is Excel, Sheets, or a CSV importer — not when the destination is an OFX-only accounting feed.

Best practices

Store the original bank .qfx with your monthly close package; convert a copy to CSV for analysis and sharing.
Reconcile CSV row counts and amount totals to the bank statement before building pivots or category rules on top of the file.
Preserve FITID in any cleaned workbook so later overlapping downloads can be de-duplicated.
Standardize column names across banks (Date, Description, Amount, Memo, FITID) so multi-account workbooks stack cleanly.
Import with explicit UTF-8 and column types in Excel instead of relying on double-click defaults.
Redact account numbers and personal identifiers before sending CSV to clients, contractors, or chat tools.
When a workflow stabilizes (same bank, same columns every month), document the download → convert → reconcile checklist so the next close is repeatable.

What QFX to CSV conversion actually does

QFX files are statement containers: account context plus transactions in OFX-style tags so Quicken-like products can import without retyping. Spreadsheet users need rows instead — when money moved, who it was with, how much, and any memo or reference the bank stored.

Conversion projects that structured download into a table. The converter walks statement transactions, lifts reconciliation fields, and writes CSV. Message-set wrappers are not preserved as nested structure because CSV cannot express them usefully. What you get is a file every spreadsheet and most custom importers understand.

This page covers the everyday job: Quicken/Web Connect download → CSV → categorize or review. It is not a live bank feed and not an accounting system. For monthly spreadsheet work, browser conversion is usually faster than installing desktop utilities just to inspect the same transactions.

QFX vs OFX: what Quicken Web Connect downloads really are

OFX is the broader Open Financial Exchange family. QFX is the variant you typically receive when a bank labels the download for Quicken. Both carry posted dates, amounts, FITIDs, and payee/memo fields, and both are text — unlike PDF statements.

Banks sometimes offer OFX and QFX separately; sometimes only “Quicken” appears. If the file is tagged OFX-like text with a .qfx extension, use this converter for CSV. If another app demands OFX, use QFX to OFX instead of renaming the extension.

Web Connect meant downloading a file from the bank and importing it into Quicken (versus Direct Connect). For conversion, what matters is the file on disk: a QFX statement export for the date range you chose online.

QFX → CSV: spreadsheet review, pivots, shared workbooks.
QFX → OFX: apps that want generic OFX.
OFX → QFX: Quicken-oriented targets that expect .qfx.
QIF → CSV: legacy Quicken Interchange plain-text exports.

Fields extracted: Date, Description, Amount, Memo, and FITID

Date usually comes from <DTPOSTED> (often YYYYMMDD, sometimes with a time). The CSV uses a readable date for sorting and filtering — still verify a known transaction after import because locales can misread ambiguous formats.

Description is typically <NAME> (payee). Memo (<MEMO>) is optional — invoice numbers, bank free-text, or blank. Many institutions fill name only. Amount (<TRNAMT>) is signed; keep conventions consistent across banks and reconcile to the statement.

FITID is the financial institution transaction id. Keep it. When you re-download an overlapping range, FITID is how careful workflows avoid booking the same purchase twice.

Bank Web Connect downloads: getting a clean source file

In online banking, look for Download, Export, or Quicken/Web Connect. Pick the account and a date range that matches the statement. Overlaps are fine if you keep FITIDs; multi-year dumps are harder to review and may stress a browser tab.

Save the .qfx without opening it in Excel. Inspect tags in a plain-text editor — spreadsheets often split tags across cells and can damage the file if you save over it.

If the bank already offers good CSV, you may not need this tool unless the Quicken download has better payee or FITID data. If you only have PDF, use a PDF statement workflow; QFX to CSV cannot invent structure that was never downloaded.

Importing the CSV into Excel and Google Sheets

In Excel, prefer Data → From Text / Get Data over double-clicking. Set comma delimiter, UTF-8, and types for Date and Amount. That avoids one-column imports, scientific notation on long FITIDs, and scrambled dates.

In Google Sheets, File → Import → Upload usually detects comma UTF-8 cleanly. Still check Amount is numeric, dates sort correctly, and long FITIDs are Plain text.

Freeze the header row, add a Category column if you categorize in-sheet, and keep a raw copy of the converter output on another tab so cleanup stays reversible.

UTF-8, special characters, and regional CSV quirks

Treat exports as Unicode. Payee names may include accents or non-Latin scripts; UTF-8 CSV is the right default. Fix import encoding before assuming the QFX was corrupt.

Where Excel expects semicolon “CSV,” a comma file may land in one column — select comma in the import wizard. OFX amounts are usually bare decimals; keep currency in a separate column for multi-currency workbooks.

Privacy: why client-side conversion matters for bank files

Bank downloads include account identifiers, balances, and spending detail. Uploading them to an unknown conversion API is unnecessary risk for a spreadsheet task. This tool converts in your browser so the transform itself does not send transactions to a Convert CSV server.

You still load the site over the network (see the privacy policy for analytics/ads). For sensitive closes, clear the paste buffer when done, delete unneeded Downloads copies on shared machines, and share redacted CSV — not the raw QFX — with collaborators.

Common Quicken and bank export pitfalls

Payee scrubbing varies by bank. CSV reflects whatever landed in the tags; conversion cannot invent a clean merchant master. Pending items may be missing from posted-only downloads — wait for posting if the UI shows more than the file.

Credit cards, brokerage cash, and checking may use different OFX message sets. If row counts look low, confirm the account and inspect <STMTTRN> density in the raw file.

Exports from Quicken can differ from the bank’s Web Connect file (memos, categories, transfers). For bank-truth reconciliation, prefer the bank download.

Reconciliation workflow after conversion

Start with controls: data-row count, amount sum, min/max dates. Compare to the statement for the same window before building category pivots.

Use FITID to catch duplicates when merging overlapping downloads — better than date+amount alone. Categorize in a working column; preserve original Description. Archive the .qfx with the final CSV/XLSX at close.

Row count matches posted transactions in range.
Amount sum matches statement activity (within known exclusions).
FITIDs unique within the account file.
Original QFX retained; shared copies redacted.

QFX to CSV versus QFX to XLSX

CSV is universal interchange: small, script-friendly, and Sheets-friendly. XLSX is better for typed columns or colleagues who will not use an import wizard — use QFX to XLSX on the Finance File Converter hub when that is the goal.

A practical path is convert to CSV here, validate, then upload to Sheets or save as XLSX in Excel. Do not expect heavy spreadsheet edits to round-trip into perfect QFX; keep the bank file if you need to re-import into Quicken.

Related finance tools on Convert CSV

The Finance File Converter hub at /finance-file-converter groups bank transforms: QFX to XLSX, QFX to OFX, OFX to QFX, and QIF to CSV for legacy .qif exports. Use Online CSV Editor or Excel tools afterward if you need column cleanup.

If your only statement is PDF, use the PDF bank-statement path. Site guides on OFX vs QFX vs QIF and bank statement to CSV help when choosing a download type; this page is for when the .qfx is already in hand.

When to use a script instead of the browser tool

The browser tool wins for monthly one-offs and emailed client files — no install, no OFX library setup. Use a script or ETL for scheduled multi-account ingest, strict schema validation, database loads, or huge archives that exceed browser memory.

Many teams validate the column contract here, then automate the same mapping once the bank’s QFX shape is known. The CSV header you standardize becomes the script contract.

Quality checklist before you share or bookkeep from the CSV

Before sharing or posting from pivots: match transaction counts, spot-check FITIDs, scan for account-number leaks, and open the file in the recipient’s spreadsheet app. Name files with bank, account nickname, and statement period.

If the CSV disagrees with the bank UI, trust the bank and re-download — or inspect raw QFX tags — before inventing spreadsheet fixes that hide a bad export.

Dates fall inside the intended statement period.
Amount signs match how you reconcile that account type.
Memo/Description emptiness matches bank behavior, not a parse failure.
No account numbers in files destined for external sharing.
Original .qfx archived with the close.

Practical limits and honest expectations

This tool maps statement transactions to CSV. It does not categorize spend, log into your bank, or replace Quicken matching — and it cannot fix cryptic bank payee strings. Ordinary monthly files convert quickly; split huge multi-year dumps if the tab struggles.

Accuracy starts at the source: prefer OFX/QFX over PDF, keep originals, reconcile totals, and pick related converters when the target is not CSV.

Frequently asked questions

What is the difference between QFX and OFX?

Both are structured bank download formats in the OFX family. QFX is the Quicken-oriented variant you typically get from “download for Quicken” or Web Connect menus. OFX is the more generic label. For spreadsheets, convert QFX to CSV; for apps that demand OFX, use QFX to OFX instead of only renaming the extension.

Does this QFX to CSV converter upload my bank file?

No. Parsing and conversion run in your browser. Transaction contents are not sent to a server as part of the conversion. See the site privacy policy for how the website itself handles analytics and advertising.

Which columns appear in the CSV?

Typical columns include Date, Description, Amount, Memo, and FITID when those fields exist in the QFX. Banks omit optional tags, so Memo may be blank even when Description is present.

What is a FITID and should I keep it?

FITID is the financial institution transaction id. Keep it in your CSV or workbook. It is the most reliable key for detecting duplicate transactions when downloads overlap.

Can I open the CSV in Google Sheets?

Yes. Download the CSV and import or upload it into Google Sheets. Verify Date and Amount types after import, and format long FITIDs as plain text if needed.

Why do dates look wrong in Excel?

Excel often guesses date formats from your regional settings. Use Text Import / Get Data, set UTF-8 and the Date column type explicitly, and spot-check a transaction you know (for example a rent payment date).

My bank only offers Quicken — is that QFX?

Usually yes. A “Quicken” or Web Connect download is typically a .qfx file with OFX-style tags. Open it in a text editor if you need to confirm; you should see OFXHEADER or <OFX> content, not PDF binary data.

How is this different from QIF to CSV?

QIF is an older Quicken Interchange plain-text format with letter codes (D, T, P, and so on). QFX is OFX-based SGML/XML-like tagging. Use QIF to CSV for .qif exports and this tool for .qfx downloads.

When should I use QFX to XLSX instead?

Use QFX to XLSX when you want a native Excel workbook without a CSV import step. Use QFX to CSV when you need universal interchange, Google Sheets upload, or a text file for scripts and importers.

Why are some memos empty?

Many banks leave <MEMO> blank and put the readable payee only in the name/description field. Empty Memo cells usually reflect the source download, not a failed conversion.

Can I convert OFX with this page?

QFX and OFX transaction payloads are closely related, but if your file is labeled OFX or your workflow is OFX-specific, prefer the dedicated OFX-oriented tools on the Finance File Converter hub. Use QFX to CSV for Quicken .qfx downloads destined for spreadsheets.

Is there a file size limit?

There is no fixed server quota because processing is local, but very large multi-year exports can slow or exhaust a browser tab. Convert monthly or yearly chunks if the page becomes unresponsive, or use a scripted pipeline for bulk archives.

For more background on data formats and conversion workflows, read our format guides or browse the converter blog for step-by-step walkthroughs linked to each tool.

QFX to CSV Converter