StatementJet

Guides

Import Bank Transactions into QuickBooks Desktop: QBO File Import Guide

QuickBooks Desktop imports bank and credit card transactions from Web Connect files, which use the .qbo extension. Many banks offer this download, often labeled “QuickBooks Web Connect” or something similar. If your bank only gives you a CSV or Excel file, you’ll need to convert it first, which is covered at the end of this guide.

The steps below are for QuickBooks Desktop for Windows (Pro, Premier, and Enterprise). Menu names can vary slightly by version.

Before you import

  • Download the .qbo file from your bank. Start the date range the day after your last import so the files don’t overlap.
  • Update QuickBooks with Help > Update QuickBooks Desktop.
  • Back up your company file, especially before your first import.
  • Know which account in your chart of accounts the transactions belong to.

How to import a QBO file into QuickBooks Desktop

  1. Open your company file.
  2. Go to File > Utilities > Import > Web Connect Files. Recent versions also offer Banking > Bank Feeds > Import Web Connect Files.
  3. Select the .qbo file and click Open.
  4. In the Select Bank Account window, choose an existing account or create a new one (see below), then click Continue.
  5. When QuickBooks says the data has been read, open Banking > Bank Feeds > Bank Feeds Center.
  6. Review the downloaded transactions and add or match each one to your register.

After the first import, QuickBooks links that bank account to the QuickBooks account you chose, so later files from the same account go there without asking.

Linking to an existing account vs creating a new one

  • Use an existing QuickBooks account if the account is already in your chart of accounts. This is the right choice almost every time. The list only shows accounts of the matching type, so a credit card file won’t offer your checking account.
  • Create a new QuickBooks account only if the account isn’t in QuickBooks yet. Choosing this for an account you already track creates a second register and splits its history.

If a file goes to the wrong account, you may need to deactivate bank feeds for that account (in its Edit Account window, under Bank Feed Settings) and import again.

Bank Feeds modes: Express vs Classic

QuickBooks Desktop gives you more than one way to review downloaded transactions:

  • Express Mode shows downloads in a Transactions List where you add or match them in batches. QuickBooks creates renaming rules for payees automatically.
  • Classic Mode, also called Register Mode, is the older layout. Downloads appear next to the account register and you match them one at a time, using aliases instead of rules.
  • Advanced Mode, available in recent versions, also uses the Transactions List and gives you more control over rules and matching.

To switch, go to Edit > Preferences > Checking > Company Preferences and choose a mode under Bank Feeds. Intuit recommends updating QuickBooks and switching to single-user mode first. Rules created in Express or Advanced Mode don’t carry over to Classic Mode, and Classic aliases don’t carry over the other way.

Why a QBO import fails

Wrong file type. Web Connect accepts .qbo files. A CSV, Excel, QFX, or OFX file won’t import, and renaming the extension doesn’t change what’s inside the file.

Unsupported or discontinued version. Intuit stops online services, including bank feeds, for each QuickBooks Desktop version roughly three years after its release. If your version is past that date, or your subscription has lapsed, imports may stop working. Installing the latest release can also clear up other import errors.

Malformed file. Missing headers, bad dates, special characters, or a file that was opened and re-saved in another program can all cause errors. If QuickBooks says it can’t verify the financial institution information, the bank ID in the file may not be recognized. Download a fresh copy, or contact your bank or the tool that created the file.

Wrong account type. A credit card file can’t go into a checking account, or the reverse.

How to avoid duplicate transactions

Every transaction in a .qbo file carries an ID called a FITID (financial institution transaction ID). QuickBooks remembers the FITIDs it has imported into each account and skips repeats, so importing the same file twice normally won’t create duplicates.

Duplicates usually come from somewhere else:

  • Overlapping files from different sources. A direct bank feed and a converted file covering the same dates will have different IDs for the same transactions. Pick one source per period.
  • Transactions you entered by hand. Checks you wrote or bills you paid in QuickBooks have no FITID. In the Bank Feeds Center, match them to the downloaded transaction instead of adding them again.

Reconcile after each import to catch anything that slipped through. Our guide on how to reconcile a bank statement walks through it.

Converting CSV or Excel to QBO first

QuickBooks Desktop doesn’t import bank CSV or Excel files into bank feeds, so convert them to .qbo first:

Then import the .qbo file using the steps above, and compare the transaction count and total against your bank’s records. Our converter gives each transaction a stable FITID, so importing the same converted file twice won’t double it up. Converting overlapping date ranges can, so start each new file where the last one ended.

Not sure which download to pick from your bank? See our comparison of QBO vs QFX vs OFX vs QIF vs CSV.