To import bank transactions into QuickBooks Desktop, download a Web Connect (.qbo) file from the bank, then go to Banking, Bank Feeds, Import Web Connect Files and review the rows in the Bank Feeds Center. Desktop has no CSV upload screen like QuickBooks Online. In Accountant and Enterprise editions, spreadsheet rows can be pasted through Batch Enter Transactions.
Which file types does QuickBooks Desktop take for bank transactions?
QuickBooks Desktop takes bank transactions as Web Connect files, which carry the .qbo extension and come from the bank's own download page. That is the route Intuit documents for bank data. Spreadsheet rows can also be pasted into a bank register in two editions, and IIF files can bring in transactions, but neither goes through the bank feed review screen.
Intuit's article Import and export data in QuickBooks Desktop lists the methods by data type. For bank data, it says to import bank transactions using Web Connect (.qbo) files. It lists Excel and CSV for general transfer of lists and transactions, and IIF for complex data structures.
The .qbo file is the only one the Web Connect import reads. Intuit's article Fix Web Connect import errors says the file must be a .qbo downloaded directly from the bank, and that it is the only type Web Connect can read. If the bank's download page offers several formats, pick the QuickBooks Web Connect option.
Web Connect is one of two ways Desktop talks to a bank. Intuit's article Set up or edit bank accounts for Bank Feeds in QuickBooks Desktop names Direct Connect and Web Connect as the two ways to connect an account. With Web Connect, the file comes from the bank's website and you import it. That article lists the editions it covers as QuickBooks Desktop Premier Plus, Pro Plus, Accountant Desktop Plus and Enterprise.
IIF is the third format a firm meets. An IIF file is a text file in the Intuit Interchange Format that can carry lists and transactions such as checks and deposits. It is covered in the post on what an IIF file is and what QuickBooks Desktop uses it for.
Importing a Web Connect file into QuickBooks Desktop
Importing a Web Connect file into QuickBooks Desktop takes three parts: download the .qbo file from the bank's website for the date range you need, import it through the Banking menu, and choose which QuickBooks account receives it. The rows then wait in the Bank Feeds Center to be added or matched.
Sign in to your Intuit account inside Desktop before importing; that step catches people out. Intuit's Import and export data article says importing Web Connect files requires you to sign in to your Intuit Account within QuickBooks Desktop. If you see a sign-in error while already signed in, the same article suggests switching bank feed modes.
Step list: the Web Connect route
The steps below follow Intuit's Bank Feeds setup article and its Web Connect troubleshooting article. Example values are fictional.
- Back up the company file. Intuit's troubleshooting article lists this as the first step.
- Sign in to the client's bank website and download a Web Connect (.qbo) file for the dates you need, for example March 1 to March 31, 2026, for the checking account ending XXXX-4821.
- In QuickBooks Desktop, go to Banking, select Bank Feeds, then select Import Web Connect Files.
- Select the .qbo file you downloaded.
- Choose the existing QuickBooks account, or choose Create a new QuickBooks account if the account is not in the file yet.
- Go to the Bank Feeds Center to review the transactions.
Pick the date range with the register in view. If the register already holds transactions through March 14, download from March 15. A file that repeats dates already entered by hand will bring in rows that need matching or removal.
Repeated Web Connect files are handled for you. Intuit's article Error: Nothing imported after importing a Web Connect (.qbo) file says each transaction in the file has a unique ID, and QuickBooks will not import the same ID twice. Re-importing the same March file skips the rows QuickBooks already holds.
The same ID rule can block a file you need. QuickBooks skips any transaction ID it has already stored, even when you need those rows brought in again. Intuit's Nothing imported article lists three fixes in order: restore a backup made before the first import and import again, enter a few missing transactions by hand in the register, or, as a careful one-time workaround, download a fresh file and edit its account ID before importing. It warns that the last option can create duplicates.
When a file will not import, Intuit's troubleshooting article gives an order to try: re-download the file straight from the bank, check the bank's site for messages about changes, switch to Classic mode (Register mode) through Banking, Bank Feeds, Change Bank Feeds Mode, and test the file in a new test company. If the test file imports, disconnect and reconnect the account in the real company file.
Can QuickBooks Desktop import bank transactions from Excel?
QuickBooks Desktop has no upload screen that sends an Excel or CSV bank file into the Bank Feeds Center. The spreadsheet route Intuit documents is Batch Enter Transactions, where rows copied from Excel are pasted into a bank or credit card register. Intuit says only Enterprise and Accountant Desktop support it.
Intuit's article Enter transactions by batch in QuickBooks Desktop states the edition limit directly: only Enterprise and Accountant Desktop support batch entering transactions from Excel or CSV files. Those rows go straight into the register, so there is no add-or-match review like the one Web Connect gets.
Step list: the spreadsheet route
These steps follow Intuit's batch entry article. The example file and names are fictional.
- Back up the company file, as Intuit's article says to before starting.
- Open the client's spreadsheet, for example a CSV of Example Bakery Inc.'s March statement for the checking account ending XXXX-4821.
- Go to the Accountant menu and choose Batch Enter Transactions.
- Select the Transaction Type and the Account, for example checks drawn on the checking account.
- Reorder the spreadsheet columns to match the columns in the batch window, then select and copy the rows.
- In the batch window, right-click the first date field and paste.
- Fix anything shown in red. Red means the name or account is not in the company file; select it and use Quick Add or Set Up.
- Select Save Transactions, then Yes on the Confirm Account screen.
Payees are where most red fields come from. A bank export's description column often holds "POS PURCHASE 0314 EXAMPLE SUPPLY" rather than a clean vendor name. Clean the descriptions in the spreadsheet first, or every row turns red and needs a Quick Add.
Split lines are possible. The article says to select the transaction, use the Split button and enter each split on its own line, or to enter separate rows that share one transaction number in the spreadsheet.
The same file layout question comes up in QuickBooks Online, which does have a CSV upload screen. For a card account there, see how to upload a credit card statement to QuickBooks Online.
Matching imported Desktop transactions in the bank feeds center
The Bank Feeds Center is the QuickBooks Desktop screen where downloaded and Web Connect transactions wait to be added to the register or matched to entries already there. Matching pairs a downloaded row with an existing check or deposit, so nothing is entered twice. Adding creates a new entry. Open it from Banking, then Bank Feeds, then Bank Feeds Center.
Intuit's article Add and match Bank Feed transactions in QuickBooks Desktop describes three modes: Express, Classic and Advanced. The buttons differ by mode.
In Express mode, QuickBooks tries to match each downloaded row to an entry already in the account. Accept a match with Add/Approve or Approve. If the match is wrong, select Not a match. When no match is found, Intuit says QuickBooks creates a new transaction for you.
In Advanced mode, matched rows sit on the Recognized tab, where you select Approve or View Details. Unmatched rows sit on the Unrecognized tab, where Add records them and Add More Details lets you split one across accounts. Match to Existing Transactions in the Action column pairs a row by hand. Batch Actions handles many rows at once.
Intuit lists the usual reasons a row will not match: the entry is not in QuickBooks yet, it was entered with a different number, amount, date or name, it sits in the wrong account, or the bank made an error. A downloaded row will also not match an entry that is already reconciled.
Matching is a step before reconciliation, not a substitute for it. The post on how to reconcile a bank statement in QuickBooks Desktop picks up once every row is added or matched.
QuickBooks Desktop bank imports when the bank has no Web Connect
When the bank has no Web Connect download, a QuickBooks Desktop user has three practical routes: paste spreadsheet rows through Batch Enter Transactions in Accountant or Enterprise, build an IIF file for the transactions, or enter them by hand. Each starts from the statement, and none runs through bank feed matching.
Batch entry is the closest to a CSV upload, but only in two editions; Pro and Premier users need another route. The step list above covers it.
IIF needs care. Intuit's IIF guides say to back up the company file before importing and warn that error checking is limited, so test on a copy first. The post on importing an IIF file into QuickBooks Desktop shows the file layout and the error report.
Manual entry is reasonable for a short month. Intuit's Nothing imported article itself suggests adding a few missing transactions directly to the bank or credit card register.
A converter that turns a CSV into a .qbo file is another route some firms use. If you go that way, test the file in a test company first, as Intuit's Web Connect troubleshooting article suggests for any file that misbehaves.
Most of these routes start with the statement as a spreadsheet. The bank statements to Excel category covers converting a PDF statement first. Schema CPA reads checking, savings and card statements a client uploads, ties out balances from month to month, and exports the rows to Excel or CSV, ready for a batch paste or an IIF build; it has no QuickBooks Desktop connection. The document types on the homepage list what it reads.