Free OFX to CSV Converter — Online, No Signup

An Open Financial Exchange file — the standard format banks use to hand transaction data to accounting software. It was published in 1997 by Microsoft, Intuit and CheckFree, and it holds the account, the statement period, a closing balance and one tagged block per transaction. Quicken, GnuCash, Moneydance, Sage, Microsoft Money and QuickBooks all read it directly; spreadsheets don't, which is what this converter is for.

Because an .ofx isn't a spreadsheet — it's financial markup written for software, with nested tags instead of rows and columns. Double-clicking it gets you an 'open with' prompt, and forcing it through Excel's text import crams the tags into a single column. There's nothing for a spreadsheet to grab onto until the transactions are pulled out, which is what this converter does.

Windows has simply associated .ofx with a text editor, usually after someone clicked 'always open with' once. It doesn't mean the file is broken or plain text — you're seeing the raw markup. You don't need to change the association to convert it: upload the file here as-is. To fix it properly in Windows, right-click the file, choose Open with → Choose another app, and pick your accounting software instead of Notepad.

Judge it on one thing: whether the CSV matches your file. Most converters get dates and amounts right, so what separates them is the detail — check numbers kept apart from transaction IDs, the account type read rather than assumed, the closing balance taken from the end of the statement period, and memos that don't duplicate the description. Those four are set out above so you can verify them here or anywhere else.

That's the OFX date format — YYYYMMDD, sometimes with a time and timezone appended. It's unambiguous for software but unreadable in a spreadsheet, and pasted raw it sorts as a number rather than a date. The converted CSV gives you 2024-03-05 instead, which Excel and Google Sheets both recognise as a real date.

It's the FITID — the bank's own unique reference for that transaction, carried straight through from the file. It looks like internal plumbing, but it's genuinely useful: if you convert two statements whose date ranges overlap, the transaction ID is how you spot the rows that appear twice.

Yes, in their own Reference column. This is worth checking on any converter you use: a common shortcut is to write the transaction ID into the check-number slot, which silently replaces a real check number like 1043 with a long internal reference. Here CHECKNUM and FITID stay in separate columns.

No. OFX 1.x is SGML, where closing tags are optional, so a line like <TRNAMT>-142.18 with no </TRNAMT> is completely valid. OFX 2.x is proper XML and does close its tags. Both are read here, so it doesn't matter which your bank produced.

Yes, with one small step. QFX and QBO are the same format as OFX — Quicken and QuickBooks branding plus an extra Intuit tag, not a different structure — so the transactions read identically. This page's upload box is set to accept .ofx, so rename your file's extension to .ofx first and it will convert exactly as a QFX to CSV or QBO to CSV conversion would. Renaming changes nothing inside the file.

The dates come out as YYYY-MM-DD, the ISO format, rather than a US or European order. That's deliberate: it's the one format that's unambiguous, sorts correctly as text, and is read as a real date by Excel, Google Sheets and Numbers alike. If you need day-first or month-first, reformat the column once after import — the underlying values are already proper dates.

Not currently — amounts arrive in a single signed column, negative for money out, exactly as the OFX states them. That's the closest match to your file and the format most tools import cleanly. Splitting into separate debit and credit columns is a one-formula step in a spreadsheet if your accounting software insists on it.

Bank CSV exports vary wildly: columns get renamed between banks, check numbers and memos are often dropped entirely, and separate debit and credit columns are common. An OFX is a defined format, so every file states the same fields the same way. Converting from it gives you a predictable seven columns no matter which bank produced it.

It's read from the statement's LEDGERBAL — the balance as of the end of the statement period, not simply whichever transaction happens to be printed last. That distinction matters on newest-first exports, where the last row in the file is the OLDEST transaction and taking its balance would report the opening figure as the closing one.

Yes, and it stays what it is. The file declares its own account type in ACCTTYPE, and that's read verbatim rather than assumed — so a savings, money-market or credit-card statement isn't quietly relabelled as a checking account. That mostly matters when you go on to import elsewhere, but it's also just what the file says.

Yes. The currency is read from the file's own CURDEF field, so a euro, sterling or rupee statement converts exactly like a dollar one. Amounts are never rescaled or re-denominated — the numbers in the CSV are the numbers in your file.

Convert one file at a time, then combine the CSVs in your spreadsheet — each conversion takes a second or two. If you're regularly merging many statements, batch conversion is available on the paid plans.

That error means your accounting software rejected the file, usually because the bank sent a plain OFX where the software expected its own branded variant, or because the download was truncated. Converting to CSV sidesteps it entirely — a CSV imports through the ordinary file-import route rather than the bank-feed one. If your goal is specifically QuickBooks or Quicken rather than a spreadsheet, a QBO or QFX conversion is the closer fix.

No. This is an online converter — it runs in your browser, there's nothing to install, and it works the same on Windows, Mac, Linux, a phone or a tablet. Searches for an 'OFX to CSV converter free download' usually lead to Windows desktop software; you don't need any of it for a one-off conversion.

Free to try with no signup, with a free tier for occasional conversions and paid plans for volume. Uploads are encrypted in transit, the file isn't kept longer than the job needs, and you can convert without creating an account.