CSV to QBO Converter
Turn CSV bank & credit-card statements into QuickBooks .QBO files — free, and entirely in your browser.
🔒 Your file never leaves your device. No upload, no account, no watermark.
Drop your CSV statement here
or click to choose a .csv / .txt file
How it works
Upload a CSV export from your bank or credit-card provider. The converter reads it directly in your browser, detects which columns hold the date, description, and amount, and builds a QuickBooks .QBO (Web Connect) file. Review the preview, then download — the file is ready to import into QuickBooks Online or Desktop. Nothing is uploaded to a server at any point — see our privacy policy for how financial files are handled, or browse all ConvertBlink converters.
Supported CSV layouts
Amounts can be a single signed column (-45.00, 2,500.00) or separate Debit and Credit columns — a debit becomes a negative transaction automatically. Currency symbols, thousands separators, and (123.45)-style negatives are cleaned for you. Dates can be US (MM/DD/YYYY), European (DD/MM/YYYY), ISO (YYYY-MM-DD), dotted (DD.MM.YYYY), or month-name formats. When a file contains genuinely ambiguous dates, the tool asks you to confirm the order rather than guessing — a silent date error is the single worst thing a converter can do.
Why QBO instead of the built-in CSV import
QuickBooks Online can import a CSV directly, but that path caps out around 1,000 rows and 350 KB per file, insists on a specific column layout, and frequently mangles dates. A .QBO Web Connect file avoids all of that: it carries proper transaction types, a currency, and stable transaction IDs, so it imports the same way a live bank feed does — a full year of history in one file, matched to the account you choose.
Fixing common QuickBooks import errors
- "We can't read the file" / OL-222 — usually a malformed file: unescaped special characters, non-English characters, or the wrong file format. This tool always emits clean ASCII in the exact OFX 1.02 structure QuickBooks expects.
- "Unable to verify the financial institution" — caused by a missing or unrecognised institution ID. The tool ships a widely-accepted default so the file validates.
- Credit card only offers a liability account — the file was built as a bank account. Set the account type to "Credit card" and the correct structure is used.
- Nothing imports / transactions skipped — QuickBooks remembers transaction IDs it has already seen (even deleted ones). Because IDs here are stable, re-importing the same file will not create duplicates.
- Transactions land on the wrong day — a date-format mix-up. Confirm US vs European order in the mapping panel.
Frequently asked questions
No. The entire conversion runs in your browser using JavaScript. Your CSV is read, parsed, and turned into a .QBO file on your own device — nothing is sent to a server, stored, or logged. You can even disconnect from the internet after the page loads and it still works.
Both. In QuickBooks Online, go to Transactions → Bank transactions → Link account → Upload from file. In QuickBooks Desktop, use File → Utilities → Import → Web Connect Files. The file is generated in the OFX 1.02 (Web Connect) format that both accept.
Yes. Set the account type to "Credit card" before downloading. Credit-card QBO files use a different internal structure (CREDITCARDMSGSRSV1), and getting this wrong is the usual reason QuickBooks only offers to import into a liability account instead of your credit-card account.
No. Each transaction gets a stable, deterministic ID (FITID) derived from its date, amount, and description. The same CSV always produces the exact same IDs, so if you import it twice, QuickBooks recognises the transactions as already seen and skips the duplicates.
Two amount styles: a single signed Amount column (e.g. -45.00 / 2500.00), or separate Debit and Credit columns. Dates can be US (MM/DD/YYYY), European (DD/MM/YYYY), ISO (YYYY-MM-DD), dotted (DD.MM.YYYY), or month-name (Jan 5, 2026). Currency symbols, thousands separators, and parentheses-negatives are cleaned automatically. You can override every column mapping by hand.
The built-in CSV upload in QuickBooks Online is limited to about 1,000 rows and 350 KB per file, is picky about column order and headers, and frequently mis-reads dates. A .QBO (Web Connect) file sidesteps those limits, carries proper transaction types and IDs, and imports the way a real bank feed does.
That is almost always a US-vs-European date mix-up (03/04 meaning March 4th vs 4th March). When your file contains ambiguous dates, this tool refuses to guess and asks you to confirm the order before converting. Pick the correct format in the mapping panel and re-download.
No. QuickBooks matches transactions to whichever account you choose during import, not to the bank name in the file. The tool uses a widely-accepted default financial-institution ID so the file validates; you rarely need to touch it. Advanced users can change it under Advanced options.
Drop your CSV bank statement onto this page, confirm the auto-detected date, description, and amount columns, review the preview, and click Download .QBO. There is no sign-up, no watermark, and no file size charge — the whole conversion is free and runs on your device.
Any bank or fintech that lets you export transactions as CSV — including Chase, Bank of America, Wells Fargo, Citi, Capital One, PNC, and US Bank, as well as Revolut, Wise, and European banks such as Sparkasse. Because you map the columns yourself, an unusual CSV layout is not a problem.
No installation. It runs in any modern browser — Chrome, Safari, Firefox, or Edge — on Mac, Windows, Linux, or ChromeOS. There is no desktop app to buy like MoneyThumb; you just open the page and convert.
This tool converts file formats only and does not provide financial, tax, or accounting advice. Always reconcile the imported transactions against your original statement.