CSV to QBO converter
Turn a CSV or Excel transaction file into a .qbo Web Connect file that QuickBooks imports as a bank feed — no column-mapping wizard, no 1,000-row limit, and it works in QuickBooks Desktop, which can't import a CSV at all. Your CSV is converted inside your own browser: it never gets uploaded.
Drop a CSV or Excel file here
CSV files are converted in your browser — they never reach our servers.
Your columns, your call
We guess the mapping from your headers and the shape of the data, then show you exactly what we guessed. Separate debit/credit columns, day-first dates and inverted signs are all one click.
Checked against the balance
If the file carries a running balance, every row is verified against it before you download — a hand-edited spreadsheet with a typo in it gets caught here.
Converted in your browser
CSV and TSV never leave your machine. Nothing is uploaded, so there is nothing for us to keep.
How to convert a CSV to QBO
Upload the file
Drop your CSV, TSV or Excel transaction file onto the converter.
Map the columns
Confirm which columns are the date, the description and the amount (or the separate debit and credit columns).
Check the balance chain
If the file has a running balance, confirm the reconciliation badge before downloading.
Download the .qbo file
Choose QuickBooks (.qbo) and import it into QuickBooks.
Questions people ask
- How do I convert a CSV file to QBO?
- Drop the CSV above, confirm the column mapping we guessed (date, description, amount or debit/credit), and download the .qbo file. Then import it in QuickBooks Online under Transactions → Bank transactions → Upload from file, or in QuickBooks Desktop under File → Utilities → Import → Web Connect Files.
- Why convert a CSV to QBO instead of importing the CSV?
- QuickBooks' CSV import is strict and lossy: three- or four-column layouts only, a 1,000-row limit per file, a 350KB size cap, and date formats it silently misreads. A .qbo file avoids all of that — it arrives as a bank feed with structured dates, amounts and memos, and QuickBooks Desktop accepts it too.
- Can I convert an Excel file (.xlsx) to QBO?
- Yes. Drop the .xlsx in and we read the sheet that holds the transactions. Unlike CSV, Excel workbooks are parsed on our server rather than in your browser, because the workbook parser is too large to ship to the browser — they're processed in memory and never stored.
- My bank exports debits and credits in separate columns. Does that work?
- Yes — map one column as "Debit / money out" and the other as "Credit / money in" and the signs are worked out for you. If your file has a single amount column where withdrawals are positive numbers, tick "flip signs" instead.
- My dates are DD/MM/YYYY. Will they import wrong?
- No. We detect day-first files automatically when any day is above 12, and there's a checkbox to force it when the file is ambiguous. Getting this wrong is what produces transactions dated in the wrong month, so we make it an explicit setting rather than a guess.
- How do I know the converted file is right?
- If your file carries a running balance column, we check every row against it — previous balance plus the amount must equal the printed balance — and flag the rows that break the chain. The reconciliation badge tells you whether the file closes before you import anything.
- Is my CSV uploaded anywhere?
- No. CSV and TSV files are parsed by JavaScript running in your own browser; the file never reaches our servers. Only .xlsx workbooks are sent to the server, and those are read in memory and never written to storage.
Only have the statement as a PDF? Use the PDF to QBO converter instead, or start from the bank statement converter.