Bulk CSV to QBO Importer for QuickBooks

One import file from many CSV exports

QuickBooks is happy to import bank transactions from a file — it is the repetition that wears people down. A business with three bank accounts and a credit card, catching up on a quarter, is looking at a dozen separate exports. Imported one at a time, each file means the same routine: upload, check which column QuickBooks thinks is the amount, fix it, review, repeat. The mapping work is identical every time because the files all came from the same bank in the same format.

The bulk importer removes the repetition. Add every CSV to one batch, confirm a single column mapping, and the tool merges all of the transactions — every account, every month — into one standard import file. One upload, one review pass in QuickBooks, and the batch is in your books. The transactions themselves are copied exactly as your bank exported them: dates, descriptions, and signed amounts are not re-typed, cleaned up, or re-calculated, so the merged file ties back to the exports it came from.

QBO or IIF — which file do you need?

QuickBooks Online and QuickBooks Desktop accept different import files, and the right choice depends only on which product you use. Both files are built from the same merged transactions; nothing about your data changes between them.

One caution belongs to the IIF side: Desktop IIF imports write directly into the company file and cannot be undone in bulk, so make a backup of the company file before importing a large batch — File → Create Backup takes a minute and turns a mistake into a restore instead of a cleanup. QBO imports into QuickBooks Online are gentler: uploaded transactions wait in the banking review tab until you add or exclude them, so a wrong file can simply be left un-added.

What this tool does — and deliberately does not do

This tool prepares a file. It does not connect to QuickBooks, it does not ask for your Intuit login, and it cannot post, edit, or delete anything inside your company. That boundary is deliberate. Tools that work inside your live books need broad access to your accounting data; a file-based importer needs nothing but the CSVs you choose to give it, and you stay the person who decides what enters the books, because the import happens in QuickBooks under your own review.

Getting the mapping right

Almost every failed import traces back to the mapping, not the file. Two checks catch most problems before you build. First, the amount shape: if your export has one amount column, deposits should be positive and payments negative — if the bank exported them the other way around, map the debit and credit columns instead and the tool will sign them correctly. Second, the date format: exports in month/day/year and day/month/year look identical in a preview row like 03/04/2026, so if your bank is outside the US, scan a few preview rows against a transaction you recognize. The mapping is saved in your browser, so next month's batch from the same bank starts already mapped.

Working the other direction? The QBO to CSV converter turns a Web Connect file back into a spreadsheet, and the CSV to QBO converter handles a single CSV with a running-balance check when you do not need the bulk merge.