Free online OFX to CSV converter

A bank or personal-finance program may provide transactions as OFX when a spreadsheet, tax system, or accounting import requires CSV. Converting the statement produces editable rows for filtering, reconciliation, analysis, or archiving, but may discard financial metadata.

What the OFX format is

OFX (Open Financial Exchange) is a structured format for exchanging financial information between banks, credit-card providers, investment services, and personal-finance or accounting software. Bank portals commonly offer .ofx downloads for checking, savings, credit-card, loan, and investment accounts.

An OFX statement can contain account identifiers, posted and transaction dates, amounts, payees, memos, transaction types, currencies, balances, and bank transaction identifiers such as FITID. OFX 1.x uses SGML-like syntax and may omit closing tags; OFX 2.x is XML-based. Both versions represent structured financial data rather than a document intended for direct spreadsheet editing.

.qfx files are an Intuit-related OFX variant used by some banks and financial programs. Software may support .ofx but not every .qfx file, so the file extension alone does not guarantee import compatibility.

What the CSV format is

CSV (comma-separated values) is plain text containing tabular records and fields. A transaction file may contain columns for date, description, debit, credit, signed amount, currency, account, balance, transaction type, and transaction ID.

Excel, LibreOffice Calc, databases, scripts, tax software, and accounting applications can process CSV. Its text structure makes transactions easy to inspect, filter, categorize, deduplicate, reconcile, and edit. CSV has no universal financial schema: one importer may require separate debit and credit columns, while another expects one signed amount column, a specific date format, semicolons as delimiters, or a particular column order.

Convert using 101convert

1. Open the OFX-to-CSV converter on 101convert.com. It can be used free without installing desktop software.
2. Select the .ofx file with the upload control.
3. Choose CSV as the output format and start the conversion.
4. Download the resulting .csv file.
5. Open the CSV in a text editor or spreadsheet and check its columns, first and last transactions, dates, amount signs, character encoding, and row count.

Keep the original OFX as the authoritative copy. Bank statements contain account and transaction information, so review the converter's current privacy and retention terms before uploading a file. Use a local application instead when the statement cannot be sent to a third party.

Convert with desktop accounting software

GnuCash can import many OFX files and lets you review transactions before producing a CSV. The exact menu wording varies by release:

1. Open or create a GnuCash data file.
2. Use File → Import → Import OFX/QFX, if that command is available, and select the statement.
3. Assign the import to the correct account. Review dates, payees, currencies, amounts, categories, splits, and duplicate-transaction matches before accepting it.
4. Select the account containing the imported transactions and use the account-register or report export command for CSV. Recent releases may expose a command such as File → Export → Export Transactions to CSV; other releases require exporting a transaction report.
5. Choose the account and date range, then set the delimiter and encoding when the export dialog provides those options.

Importing into GnuCash is useful when transactions need account mapping, duplicate checking, categorization, or reconciliation before export. Split transactions may become multiple rows or otherwise differ from the original OFX, so inspect the output.

Moneydance, Quicken, and other personal-finance applications can also import some OFX or QFX files and may offer CSV export. Their supported extensions, export fields, and menu paths vary by version. If a program has no CSV export, do not rename the file extension; use an OFX-aware export function or a parser that maps the imported data to the required CSV schema.

Automate recurring conversions

For repeated conversions, use an OFX parser or library rather than splitting the source text at commas or line breaks. The parser must account for SGML-like and XML-based OFX, escaped characters, multiline memos, optional fields, date-time offsets, negative amounts, character encodings, and bank-specific fields.

Define the destination schema before writing the output. Preserve FITID or an equivalent transaction ID, use UTF-8, quote fields containing commas or quotation marks, and document the delimiter, date format, and amount convention. A command such as python ofx_to_csv.py statement.ofx transactions.csv is only an example; the script must provide its own parser, field mapping, validation, and error handling.

Check compatibility and data quality

• Verify signs and columns. Confirm that deposits, withdrawals, fees, refunds, and transfers retain their intended direction. Check whether the result uses one signed amount or separate debit and credit fields.
• Check dates. OFX may contain posted dates, transaction dates, and time-zone offsets. A conversion can retain only one date or shift a timestamp when software applies the computer's local time zone. Use an unambiguous format such as YYYY-MM-DD when the receiving program permits it.
• Preserve identifiers as text. Keep FITID, account identifiers, and other bank references when needed. Import identifier columns as text so spreadsheet software does not remove leading zeros or display long values in scientific notation.
• Check currency and balances. Make the currency explicit if it is not included in the CSV. Compare opening or closing balances and summed transactions with the original statement.
• Check delimiters and encoding. Valid CSV quotes descriptions containing commas, quotation marks, or line breaks. Regional spreadsheet settings may expect semicolons instead of commas. Confirm that accented names and currency symbols remain intact after opening the file.
• Expect structural loss. CSV normally does not preserve OFX account metadata, connection information, balance sections, investment-specific records, transaction-type hierarchies, split relationships, or duplicate-detection behavior unless the converter writes them into dedicated columns.
• Reconcile before deletion or import. Compare row counts, transaction totals, dates, and available balances with the OFX file. A CSV that opens correctly can still omit unsupported records or map fields incorrectly.