Financial Statement Converter
Inspect OFX, QFX, and QBO statement structure and export transactions to a documented CSV or JSONL schema.
Private offline parsing
Convertr never asks for credentials, performs OFX Direct Connect, categorizes spending, identifies merchants, enriches counterparties, or sends statement content to another service.
Fidelity stays explicit
Dates retain their source strings and offsets. Naive dates are marked. Decimal strings, signs, order, and duplicates are preserved. Unsupported tax, bill-pay, profile, and loan message sets are reported instead of silently exported.
Stable transaction schema
Schema version 1.0 is shared by CSV and JSONL. Empty optional values remain empty strings. CSV text cells that could execute as spreadsheet formulas receive a leading apostrophe; JSONL retains decoded source text.
| Field group | Fields |
|---|---|
| Statement | schema_version, section_id, statement_type, account_type, currency, transaction_order, transaction_kind |
| Dates | posted_at, posted_at_raw, posted_timezone, available_at, available_at_raw, available_timezone |
| Cash transaction | amount, transaction_type, fitid, check_number, reference_number, server_transaction_id, correction_fitid, correction_action, name, memo |
| Investment | security_id_type, security_id, units, unit_price, commission, fees, taxes, total |
Financial Statement Converter
Inspect supported OFX or QFX statements and export normalized transaction data.
- Input
- One supported OFX or QFX statement file.
- Output
- A transaction preview and complete CSV or JSONL export.
- Real limitations
- The utility does not reconcile accounts, calculate tax, provide financial advice, or invent missing balances and transaction fields.
- Privacy and data handling
- one supported OFX or QFX statement file is uploaded to a compatible Convertr worker only after you start the operation. Processing is automated, and temporary source and result files are deleted automatically after processing rather than retained as permanent storage.
How to use this tool
- Choose one supported OFX or QFX statement file and wait for the page to validate it.
- Set the available output or inspection options, then start processing.
- Review the reported result and download a transaction preview and complete CSV or JSONL export before the temporary link expires.
Common failure modes
Malformed SGML/XML, an unsupported statement variant, invalid dates, or no transaction section produces a parsing error.
Useful example
Upload a QFX checking statement and export its posted transactions, amounts, identifiers, and memo fields to CSV.