Choose your bank export
Select a UTF-8 .ofx, .qfx or .qbo file up to 2 MB.
Review an OFX bank statement, then export transactions to CSV with account context, exact decimal amount, transaction ID and original timestamp columns.
The CSV keeps signed amount semantics as separate direction and amount fields, with formula-like text safely prefixed.
Choose a file, then use Download CSV to save the result.
Also with this file: View transactions · Download Excel · Download JSON
Select a UTF-8 .ofx, .qfx or .qbo file up to 2 MB.
Inspect bank or credit-card statement rows, dates, amounts, references and balances.
Download CSV, Excel or JSON from the same in-memory parsed statement.
Open an OFX-family statement without importing it into accounting software.
Move FITIDs, exact amounts and date strings into a spreadsheet for your own analysis.
Download the normalized JSON model while retaining source timestamp details.
The details that matter before you use OFX File Viewer.
This version reads UTF-8 OFX 1.x SGML and OFX 2.x XML bank or credit-card statement messages. QFX and QBO files with those structures use the same parser.
No. Investment, bill payment, authentication and other non-statement messages are outside this viewer's tested scope.
No. The table shows the date portion and exports include the original posting timestamp. JSON preserves the supplied time and explicit offset.
A supplied ledger balance is shown if present. No opening balance is inferred and transactions are not reconciled against that balance.
XLSX cells are text. Formula-like CSV values receive a protective apostrophe; JSON retains raw semantic values.
This product reads QBO input and exports CSV, Excel or JSON. It does not generate a QBO import file or certify software-specific compatibility.
No. Parsing and exports run locally. Files, filenames, account identifiers and transaction descriptions are excluded from analytics.