Choose your CSV
Open a transaction export from your bank, bookkeeping platform, or spreadsheet. Quoted cells and comma, semicolon, tab, and pipe delimiters are supported.
Convert CSV transactions to QBO
Map a bank or accounting CSV, review every amount, and create a QBO file for a QuickBooks import workflow. The CSV is read and converted entirely in your browser.
Files stay on your device Review before download Real structured output
Local-only workspace No upload endpoint
Drop a CSV export here
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.
How it works
CSV in, QBO out—without an upload
The complete workflow runs in the active browser tab, with a visible transaction preview between input and download.
Map and review columns
Match date, description, amount—or separate debit and credit columns—then check the normalized transaction preview.
Download QBO
Add the account identifiers and currency you want in the file, then generate the QBO locally and review its import preview in QuickBooks.
Built for financial files
Conversion you can inspect
Flexible CSV mapping
Use a single signed amount column or separate debit and credit columns without rewriting the source file.
Accounting-safe output
Descriptions are escaped, transactions receive stable identifiers, and rows are ordered before the QBO file is created.
Private by architecture
There is no upload step or conversion API. Your source data remains inside the active browser tab.
What the converter maps into QBO
StatementForge turns each valid CSV row into a bank transaction record. Dates are normalized, debit values become negative amounts, credit values become positive amounts, and the selected account details are written into the QBO statement header.
DateDescriptionAmountDebitCreditBalanceAccount IDCurrency
Before importing into QuickBooks
- Confirm that ambiguous numeric dates use the correct month/day order.
- Check that withdrawals are negative and deposits are positive in the preview.
- Use an account ID that consistently identifies the destination account.
- Always review the QuickBooks import preview for duplicates before posting.
Questions
Before you convert
Does my CSV get uploaded?
No. The browser reads the CSV and generates the QBO locally. StatementForge does not receive the file or transaction rows.
Which CSV columns are required?
You need a date, description, and either one signed amount column or at least one debit or credit column. Balance is optional.
Will every QBO file import into every QuickBooks version?
No converter can guarantee that. QuickBooks versions and account configurations apply different import rules, so review the import preview before posting.
Can I use separate withdrawal and deposit columns?
Yes. Map withdrawal or debit as money out and deposit or credit as money in. StatementForge combines them into signed QBO transaction amounts.
Related workflows