Import CSV Bank Transactions Into QuickBooks Desktop

Quick Answer: QuickBooks Desktop has no import for bank transactions in CSV or Excel form. Its Excel import handles lists (customers, vendors, items, chart of accounts), and its bank import reads only .QBO Web Connect files. To get a bank CSV in, convert it to .QBO, turn it into an IIF file, paste it into Batch Enter Transactions (Accountant and Enterprise only), or use a third-party importer.

If you have a CSV or Excel file of bank transactions and QuickBooks Desktop will not take it, nothing is wrong with your file. Desktop simply does not offer a CSV path into the banking module, and the "Import Excel" command most people find is meant for lists, not transactions. The fix is choosing one of the routes Desktop does support.

Why does QuickBooks Desktop reject a bank CSV?

Two separate import features exist in Desktop, and neither reads a bank CSV:

• Bank Feeds and Web Connect read only the .QBO format. A support reply on Intuit's QuickBooks community, answering a user with a folder of bank CSVs, confirmed that CSV uploads of banking transactions are not a Desktop capability and pointed to .QBO as the supported file.
• The Excel and CSV import imports list records. Intuit's article on importing Excel files into Desktop names Customers, Vendors, Items and the Chart of Accounts, and states that the Add/Edit Multiple List Entries window cannot be used to import transactions such as invoices or bills.

That is the opposite of QuickBooks Online, whose bank upload takes a CSV directly. Advice written for Online is a common source of confusion here.

What does QuickBooks Desktop's Excel import actually cover?

The first three are the ones labelled "Excel". Use them to set up a customer list or chart of accounts; they will not take a bank statement.

Which route should you use for bank transactions?

Route 1: convert the CSV to .QBO

This is the only route that sends transactions through the Bank Feeds Center, where QuickBooks matches them to checks and deposits you already entered. It is the safest choice for an account you keep current in QuickBooks.

You need a converter that writes Web Connect files. If the CSV came from your bank, first look in online banking for a QuickBooks download for the same dates; a bank-issued .QBO avoids conversion entirely. If you are working from PDF statements, QuickBankConvert can produce the .QBO straight from the statement PDF on its Plus plan and above, so you skip the CSV step. Either way, run the file through the QBO file checker before importing, then follow the Web Connect steps in importing bank transactions into QuickBooks Desktop.

Route 2: build an IIF file

IIF (Intuit Interchange Format) is a tab-delimited text format Desktop has imported for decades. Intuit's IIF article lists checks, deposits, general journal entries and other transactions among what it can bring in, with the path File > Utilities > Import > Import IIF on Windows, signed in as admin.

The trade-offs are real:

• Back up the company file first. Intuit says so explicitly, because IIF imports post directly and there is no bulk undo.
• Transactions go straight into registers, bypassing the Bank Feeds Center, so there is no matching against what is already there.
• Imported transactions are not linked to related records automatically; a deposit will not be applied to an open invoice.
• Each line needs an account name that exists in your chart of accounts.

IIF suits loading history into an account that has nothing in it yet. The guide to converting an Excel file to IIF shows the layout.

Route 3: Batch Enter Transactions

Intuit's batch entry article says only QuickBooks Enterprise and QuickBooks Accountant Desktop support batch entering transactions from Excel or CSV into bank, credit card, receivable and payable registers. Open Accountant > Batch Enter Transactions, pick the transaction type and account, arrange your spreadsheet in the same column order the window shows, copy the rows and paste into the first date field. Payees or accounts that QuickBooks does not recognize turn red; set them up or Quick Add them, then select Save Transactions.

It is fast and free if you already have one of those editions. Like IIF, it bypasses bank feed matching.

Route 4: a third-party importer

Paid importer apps read CSV and Excel files and create Desktop transactions with their own column-mapping screens. They make sense for recurring bulk imports of mixed transaction types. The Transaction Pro importer comparison looks at one well-known option.

What you see when you try the wrong door

These are the usual dead ends, and what each one means:

• The Excel import opens a formatted sheet asking for customer or vendor details. You are in the Standard Import, which only builds lists. Close it; there is no transaction tab to find.
• Advanced Import lets you map columns, but the only targets are list types. Same limitation, different screen.
• Import Web Connect Files will not accept the file at all. The file is CSV, QFX or QIF rather than .QBO. Renaming a CSV to .qbo does not help; the content has to be in Web Connect format.
• Batch Enter Transactions is nowhere to be found. You are probably on an edition other than Enterprise or Accountant, which Intuit says are the only ones that support it.
• An IIF import reports errors on every line. Check that the file kept its tab-delimited structure and header rows; saving it from Excel as a comma CSV breaks both.

Once the transactions are in by any route, reconcile the account against the bank statement for the same period. That is the check that proves nothing was skipped or duplicated.

How do you choose?

Fixing the CSV before any route

Bank CSVs need cleanup regardless of where they end up:

• Delete header blocks, running balance columns and totals rows.
• Use one signed amount column, or the separate debit and credit layout your target expects.
• Put dates in one format throughout.
• Remove currency symbols and thousands separators if the tool is strict.
• Keep payee names consistent so QuickBooks can learn them.

A CSV that started life as a copied PDF table often has merged rows and stray page headers. Converting the original statement, or downloading a fresh export from the bank, is usually quicker than repairing it.

Related guides

• Desktop's .QBO import from start to review
• Building an IIF file from a spreadsheet
• A bulk importer reviewed
• What a QuickBooks-ready QBO looks like