Convert OFX to CSV

Banks and personal-finance applications commonly provide statements as OFX, while spreadsheets, accounting imports, and data-analysis scripts often require CSV. Converting the statement makes transactions editable and easier to share or process, but can remove account and transaction metadata.

What the OFX format is

OFX (Open Financial Exchange) is a structured format for exchanging bank, credit-card, investment, and other financial data. A statement can contain account details, balances, transaction dates, amounts, payees, memos, transaction types, currencies, and unique identifiers such as FITID.

Online-banking portals commonly offer .ofx downloads. .qfx files use an Intuit-specific version or variation of OFX and may require software that supports QFX imports. Personal-finance applications including GnuCash, Quicken, Moneydance, and Microsoft Money can import some OFX or QFX files.

OFX 1.x is SGML-like and may omit closing tags; OFX 2.x is XML-based. Banks can differ in tags, character encoding, date formats, and optional fields, so an OFX file is intended for software exchange rather than direct spreadsheet editing.

What the CSV format is

CSV (comma-separated values) is plain text arranged as records and fields. A transaction export usually contains columns such as date, amount, payee, memo, account, transaction type, and transaction ID. CSV does not define a single financial schema: one program may use separate debit and credit columns, while another uses one signed amount column.

Excel, LibreOffice Calc, Google Sheets, database tools, and programming languages can open CSV. The format is easy to inspect, edit, filter, and process, but it normally does not preserve OFX balances, account identifiers, bank metadata, currency, transaction types, or duplicate-detection rules unless the converter adds explicit columns.

Convert with GnuCash

1. Install GnuCash from gnucash.org and create or open a GnuCash data file.
2. Use File → Import → Import OFX/QFX, then select the .ofx or supported .qfx file.
3. Assign the import to the correct GnuCash account. Review dates, payees, amounts, currencies, splits, and duplicate-transaction matches before accepting it.
4. Select the account containing the imported transactions and use File → Export → Export Transactions to CSV. Some releases expose the command from the account register or use slightly different menu wording.
5. Choose the filename, account, date range, delimiter, and encoding if the export dialog provides those options; save a file such as transactions.csv.

GnuCash is suitable when the statement needs review, duplicate checking, account mapping, or correction before export. It may represent split transactions differently from the original OFX, so inspect the resulting rows.

Convert with Moneydance

1. Open Moneydance and use its File → Import command for .ofx or .qfx.
2. Choose the destination account and review the imported transactions for duplicates, signs, dates, and categories.
3. Use File → Export, select CSV if that format is available in the installed release, choose the account and date range, and save the file.

Moneydance menu names and available export formats vary by release. If CSV is not offered, export to a supported intermediate format and use a dedicated converter or script, then verify the field mapping.

Use an online converter

Services such as Zamzar and Convertio may accept an OFX file and return CSV. Upload the file, choose CSV, download the result, and open it in a text editor or spreadsheet for inspection. Legacy SGML-style files, unusual encodings, and bank-specific tags may be rejected or converted incorrectly.

Bank statements contain sensitive financial information. Prefer GnuCash or another local application when possible; otherwise check the service's privacy policy, retention period, encryption, and deletion controls, and remove uploaded and downloaded copies after verification.

Automate recurring conversions

For repeat jobs, use an OFX-aware parser rather than splitting text on commas or assuming one transaction per line. The parser must handle SGML and XML variants, escaped characters, multiline memos, optional fields, time-zone offsets, negative amounts, character encodings, and duplicate identifiers.

Define a fixed output mapping, preserve FITID when available, quote fields containing commas or quotation marks, and write UTF-8 CSV with a documented delimiter and date format such as YYYY-MM-DD. A command such as python convert_ofx.py statement.ofx transactions.csv is only an example; the script must implement its own parser, field mapping, validation, and error handling.

Check the converted file

• Verify amount signs and currency. Confirm that deposits, withdrawals, fees, and refunds have the intended signs. Add a currency column if the CSV does not make it unambiguous.
• Check dates and time zones. OFX timestamps can include offsets, and spreadsheet software may display or convert them using the computer's local time zone.
• Preserve identifiers. Keep FITID and account numbers when possible. Import them as text so spreadsheet software does not remove leading zeros or use scientific notation.
• Check delimiters and encoding. A regional spreadsheet installation may expect semicolons instead of commas. Confirm that accented names and symbols remain correct after opening the file.
• Expect field and structure loss. CSV may omit opening and closing balances, account metadata, transaction type, currency, bank references, and split-transaction relationships.
• Reconcile totals. Compare row counts, transaction totals, and available opening or closing balances with the original OFX before archiving or deleting it.