Choose QBO or OFX
Select a text-based financial exchange file from your device. StatementForge detects QuickBooks QBO metadata and standard OFX transactions.
Open QBO or OFX bank transactions as a clean CSV with dates, descriptions, signed amounts, debit and credit columns, transaction types, and FITIDs—all without uploading the file.
or choose a file from your device · up to 15 MB
File reading and conversion happen inside this browser tab. StatementForge never receives the file or its transaction data.
The complete workflow runs in the active browser tab, with a visible transaction preview between input and download.
Select a text-based financial exchange file from your device. StatementForge detects QuickBooks QBO metadata and standard OFX transactions.
Review the detected currency, account details, ledger balance, dates, descriptions, and amount signs before exporting.
Create a spreadsheet-safe CSV containing the original transaction identifiers and separate debit and credit columns.
Original financial transaction IDs are retained so you can trace exported rows back to the source file.
The export includes signed amount, debit, and credit columns for easier filtering and reconciliation.
The tool opens a file you already have. It never asks for bank or QuickBooks credentials.
The converter reads transaction blocks from QBO and OFX 1.x files. It extracts the posted date, payee or memo, signed amount, transaction type, and FITID. Account metadata is shown for review but is not repeated on every spreadsheet row.
Yes. The download is a standard UTF-8 CSV that opens in Excel, Google Sheets, LibreOffice, and most accounting tools.
Yes. QBO is based on the OFX financial exchange structure, so this tool accepts text-based .qbo and .ofx files.
Yes. FITID values are included in the final CSV when the source file contains them.
Yes. Parsing and export happen in the browser. No source file or transaction data is posted to StatementForge.