Convert OFX to CSV for Spreadsheets & Analysis

Your bank gave you an OFX file but you need a spreadsheet. Convert it to clean CSV with proper columns — date, description, amount, type — ready for Excel, Google Sheets, or any accounting tool.

Works with OFX and QFX files from any bank. Both SGML and XML versions supported. Free online — no signup.

Bank-grade security - Files encrypted in transit, never stored
Files encrypted in transitNo files storedFree forever — no limits

How It Works

1

Upload Your OFX File

OFX or QFX file from your bank's online portal. Both OFX 1.x (SGML, no closing tags) and OFX 2.x (XML) formats are auto-detected and parsed correctly.

2

Fields Extracted & Mapped

Date, description, amount, transaction type, reference ID, and check number — all extracted from OFX tags and mapped to clean, labeled CSV columns automatically.

3

Download CSV

Standard comma-separated file that opens in Excel, Google Sheets, LibreOffice, Numbers, or imports into any software that accepts CSV.

What's Inside Your OFX File

OFX files contain structured transaction records. Here's how each field maps to your CSV columns.

DTPOSTEDDate

20260315 → 03/15/2026

NAME + MEMODescription

Payee name & transaction details

TRNAMTAmount

-45.99 (neg = debit)

TRNTYPEType

DEBIT, CREDIT, POS, ATM

FITIDReference ID

Unique per transaction

CHECKNUMCheck #

If check transaction

OFX 1.x (SGML) vs OFX 2.x (XML)

Most US banks still export OFX 1.x, which uses SGML — not XML. This trips up many converters and parsers. Ours handles both.

OFX 1.x (SGML)

OFXHEADER:100
DATA:OFXSGML
VERSION:102

<STMTTRN>
<TRNTYPE>DEBIT
<DTPOSTED>20260315
<TRNAMT>-45.99
<FITID>2026031500012
<NAME>AMAZON MKTPL
  • No closing tags (valid SGML)
  • Plain text header, not XML
  • Used by most US banks today
  • Breaks standard XML parsers

OFX 2.x (XML)

<?xml version="1.0"?>
<?OFX OFXHEADER="200"?>

<STMTTRN>
  <TRNTYPE>DEBIT</TRNTYPE>
  <DTPOSTED>20260315</DTPOSTED>
  <TRNAMT>-45.99</TRNAMT>
  <FITID>2026031500012</FITID>
  <NAME>AMAZON MKTPL</NAME>
</STMTTRN>
  • Proper closing tags on every element
  • Standard XML declaration header
  • Newer banks and fintech exports
  • Parseable by any XML library

Don't know which version you have? Upload it — we detect and parse both automatically.

OFX

What is OFX?

Open Financial Exchange

Banking industry standard for financial data exchange. OFX 1.x uses SGML, OFX 2.x uses XML. Each transaction is a STMTTRN block with date, amount, payee, and a unique FITID. Used by QuickBooks, Quicken, and most financial software.

CSV

What is CSV?

Comma-Separated Values

Plain text with one transaction per row, separated by commas. Opens in Excel, Google Sheets, and any spreadsheet. Human-readable, editable, and universally compatible for analysis and reporting.

Why This Tool

OFX 1.x & 2.x Support

Both SGML-based OFX 1.x (no closing tags, used by most US banks) and XML-based OFX 2.x are parsed correctly. No need to know which version your bank uses.

All Transaction Fields Preserved

Date, description (NAME + MEMO), amount, transaction type, FITID reference, and check number all mapped to clean CSV columns. Nothing dropped.

QFX Files Included

QFX is Intuit's branded OFX format for Quicken. Same internal structure, different extension. Upload either .ofx or .qfx — both work.

Transaction Types Decoded

OFX encodes types as DEBIT, CREDIT, POS, ATM, XFER, CHECK, etc. These are preserved as a readable column in your CSV for easy filtering.

Proper Date Formatting

OFX stores dates as YYYYMMDDHHMMSS (e.g., 20260315120000). Converted to clean MM/DD/YYYY in CSV — no manual date parsing needed.

UTF-8 Output

Payee names with accented characters, currency symbols, or international text come through correctly. No encoding issues when opening in Excel or Google Sheets.

When to Use This

Spreadsheet Analysis

Sort, filter, and build pivot tables from your bank transactions in Excel or Google Sheets. OFX files can't do that — CSV can.

Multi-Bank Consolidation

Download OFX from each bank, convert to CSV, and combine into one spreadsheet for unified cash flow analysis across all accounts.

Software Migration

Moving from QuickBooks/Quicken to software that only accepts CSV (Xero, Wave, FreshBooks, custom tools). OFX-to-CSV bridges the gap.

Where Your CSV Works

Spreadsheet Apps

  • Microsoft Excel
  • Google Sheets
  • LibreOffice Calc
  • Apple Numbers

Accounting Software

  • Xero (bank feed CSV)
  • Wave Accounting
  • FreshBooks
  • Zoho Books

Personal Finance

  • YNAB (CSV import)
  • Monarch Money
  • PocketSmith
  • Custom budgeting tools

OFX-to-CSV Issues & Fixes

OFX file won't parse — "invalid format" or "unexpected token" error

Your file may be truncated (missing the closing </OFX> tag) or corrupted during download. Re-download from your bank's portal. If the file opens in Notepad and ends abruptly, it's incomplete.

CSV has fewer transactions than expected

Check the date range in your OFX file — banks often default to 30 or 90 days. Download a wider date range from your bank portal. The OFX header contains DTSTART and DTEND tags showing the exact range.

Description column is blank but Memo column has data (or vice versa)

Some banks use the NAME field for descriptions, others use MEMO, and some use both. Our CSV includes both columns. If one is empty, the transaction data is in the other column.

Amounts have wrong signs — credits showing as negative

OFX standard uses negative for debits and positive for credits. If your bank reverses this convention (rare but it happens), amounts will appear flipped. Check a known deposit to verify the sign convention.

Date shows as a long number (20260315120000) instead of a readable date

This is the raw OFX date format (YYYYMMDDHHMMSS). Our converter formats this to MM/DD/YYYY automatically. If you see raw dates, the file may not have parsed correctly — try re-uploading.

Frequently Asked Questions

Q

What's the difference between OFX and QFX files?

QFX is Intuit's branded version of OFX, used by Quicken. The internal format is identical — same STMTTRN blocks, same fields. Our converter handles both file extensions.

Q

My OFX file has no closing tags — is it broken?

No. OFX version 1.x uses SGML syntax where closing tags are optional. A line like <TRNAMT>-1250.00 with no </TRNAMT> is perfectly valid OFX 1.x. Our parser handles both SGML (1.x) and XML (2.x) formats.

Q

What columns does the CSV contain?

Date, Description (from NAME and MEMO fields), Amount, Transaction Type (DEBIT, CREDIT, POS, ATM, etc.), Reference ID (FITID), and Check Number (if present). All fields from the OFX are preserved.

Q

Can I open the CSV in Google Sheets?

Yes. Upload to Google Drive and open, or use File > Import in Google Sheets. The CSV uses UTF-8 encoding and standard comma delimiters — no special handling needed.

Q

My bank exports both OFX and CSV — why would I convert OFX to CSV?

Bank-exported CSVs often have inconsistent formats, missing fields, or encoding issues. OFX is a standardized format — converting from OFX gives you a cleaner, more predictable CSV with all transaction fields preserved.

Q

Does it preserve the FITID (transaction reference)?

Yes. The FITID (Financial Institution Transaction ID) is included as a column in the CSV. This unique identifier is useful for deduplication if you import the same date range multiple times.

Q

Can I convert multiple OFX files at once?

Upload one file at a time. Each converts in seconds. For merging multiple months, convert each OFX separately and combine the CSVs in Excel.

Q

ofxconverter.com limits free users to 1 file per day. Is this really free?

Yes. No daily limits, no signup, no file count restrictions. Convert as many OFX files as you need.

Q

Is my data secure?

Encrypted in transit via TLS, processed in memory, never stored. Your OFX file is deleted immediately after conversion.