Convert a CSV to QuickBooks Online the reliable way: turn any bank or card CSV into a .qbo Web Connect file that imports cleanly, no column mapping or errors.
No account needed for your first conversions. We never store your bank login.
QuickBooks Online does let you upload a CSV, but it forces your file into a strict three-column or four-column layout, a single US date format, and clean number formatting, and it rejects the whole file on the first row it cannot read. Converting the CSV to a .qbo Web Connect file skips all of that: you upload the .qbo and QuickBooks imports it as a standard bank feed. The converter at the top of this page does that conversion in one pass.
Drop in a CSV or Excel export from any US bank, credit card, or accounting tool. You get back a .qbo file that imports into QuickBooks Online (and QuickBooks Desktop), plus Excel and CSV copies. Every transaction keeps its date, description, and amount, and the converter checks the parsed total against your original file before you export, so nothing is silently dropped.
Built for the CSV and Excel exports US banks and cards actually send, checked before it exports.
The converter adds up the transactions it parsed and matches that to your file total before you export, so nothing is silently dropped.
Valid OFX 1.02 with QuickBooks Web Connect headers. Online and Desktop import it as a standard bank feed.
Date, description, and amount are detected for you, so you skip QuickBooks' strict 3-column and 4-column CSV layout.
Bulk upload for catch-up and cleanup work. Each file gets its own reconciliation check and its own exports.
Mixed date formats, currency symbols, and stray commas that break a raw CSV import are cleaned up before the .qbo is built.
One conversion, three files: the .qbo for QuickBooks, an XLSX to review, and a CSV for everything else.
Three steps. No column-mapping wizard.
Drag in a CSV, XLS, or XLSX export from your bank, credit card, or accounting tool. Any column order is fine.
Every transaction is parsed and checked against your file total. You see the rows before exporting.
Download the .qbo and import it as a Web Connect bank feed. Excel and CSV are in the same download.
The specifics that decide whether the import is clean. If your case is not here, message us in chat.
In QuickBooks Online, go to Transactions, then Bank transactions, choose the account, and select Upload from file. Pick your CSV, map the date, description, and amount columns, then review and import. If QuickBooks rejects the layout, convert the CSV to a .qbo file first and upload that instead, which removes the column-mapping step entirely.
QuickBooks Online accepts a CSV with either three columns (Date, Description, Amount) or four columns (Date, Description, Credit, Debit), in English, under 350 KB. Dates must be one consistent format and amounts plain numbers with no dollar signs or commas. Anything outside that fails, which is why a converted .qbo file imports far more reliably.
Yes. QuickBooks Online imports CSV bank and credit card transactions through Upload from file, and it also imports .qbo Web Connect files. The CSV route works when your file already matches the strict format. The .qbo route works with any source file, because the converter reformats the data into the exact structure QuickBooks expects.
The usual causes are a wrong column count, mixed or non-US date formats, dollar signs or commas inside amount cells, blank rows, and files over 350 KB. QuickBooks reads the file row by row and stops at the first line it cannot parse, so one bad cell blocks the whole upload. Converting to .qbo removes these failure points before you import.
Download the transactions from your bank as a CSV, then either upload that CSV under Transactions, Bank transactions, Upload from file, or convert it to a .qbo first and upload the .qbo. The .qbo imports as a Web Connect bank feed, so QuickBooks routes every transaction straight into the review queue for categorizing and matching.
A CSV is a plain spreadsheet of rows and columns with no fixed structure, so two banks export wildly different CSVs. A .qbo file is a QuickBooks Web Connect file in OFX format with a defined layout QuickBooks reads natively. Converting CSV to QBO turns an unpredictable spreadsheet into the precise file QuickBooks was built to accept.
Yes. Credit card CSVs convert the same way as bank CSVs. Export the activity from your card account, convert it to a .qbo, and import it into the matching credit card account in QuickBooks Online; the credit card CSV to QuickBooks guide covers the sign convention in full. Charges need to import as negative and payments as positive, which the converter sets correctly when it builds the .qbo file.
A CSV upload is capped at 350 KB, roughly a thousand rows depending on description length, so long histories often have to be split into several files. A .qbo import is not held to that 350 KB CSV limit, so converting lets you bring a full year of transactions into QuickBooks in a single file.
QuickBooks Desktop will not take a raw CSV for bank transactions, but it imports .qbo Web Connect files directly. Convert your CSV to a .qbo, then in Desktop go to File, Utilities, Import, Web Connect Files; the CSV to QuickBooks Desktop guide walks through it. The same converted file works for both QuickBooks Online and Desktop, so you only convert once.
Upload your CSV or Excel export in the converter above. The tool detects the date, description, and amount columns, normalizes the dates to MM/DD/YYYY, strips currency symbols and commas from the amounts, and checks the running total against your file. Download the .qbo and import it under Transactions, Bank transactions, Upload from file. The whole pass takes under a minute, with no mapping wizard to fight.
A manual import means hand-fixing your file to every QuickBooks rule: exactly three or four columns, one consistent date format, amounts with no dollar signs or thousands commas, expenses as negatives, no blank rows, and no commas inside descriptions. Miss one and the upload fails. Converting to .qbo applies all of that for you, so the file QuickBooks receives is already correct.
Bookkeepers and accountants doing catch-up work rely on it most, because clients hand over a year of bank and card CSVs that never match QuickBooks formatting. Small business owners use it to import accounts QuickBooks cannot connect by bank feed, and anyone cleaning up a bad import uses it to replace transactions that came in wrong the first time.
A live bank feed in QuickBooks Online usually pulls only the last 90 days, and it skips closed accounts and the gap before you connected. Your bank still lets you download those older months as a CSV. Convert each CSV to a .qbo and you can backfill any period into QuickBooks, well beyond what the feed alone would ever import.
Upload a CSV or Excel export, get a QuickBooks-ready .qbo back in seconds. No card to try it.
Yes, and that check is the whole point. Before the .qbo downloads, the converter sums every transaction it parsed and compares it to the total in your CSV. If a row is missing or misread, you catch it in the preview instead of discovering it weeks later during reconciliation. You export only once the parsed rows match your file. Working from a spreadsheet instead? Use the Excel to QBO converter to turn an .xls or .xlsx file into the same import-ready file, convert any CSV to QBO from the home page, read the full guide to importing bank statements into QuickBooks, compare the best CSV to QBO converters on price and features, batch many statements at once with the bulk CSV to QBO converter, or learn what a .qbo file is and why QuickBooks needs it.
For the solo bookkeeper running a monthly close in QuickBooks.
USD / month
billed $288 yearly
For a firm or finance team converting across many clients and currencies.
USD / month
billed $888 yearly
For multi-bookkeeper firms managing many client books at scale.
USD / month
billed $2,988 yearly
