To import bank transactions into QuickBooks Desktop, save your bank's transactions as a Web Connect (QBO) file, then choose File > Utilities > Import > Web Connect Files and open it. Desktop asks which account the file belongs to, loads the lines into the Bank Feeds Center, and you accept them into the register.
Is Web Connect the only bank file QuickBooks Desktop takes?
For bank transactions, Web Connect is the file route QuickBooks Desktop is built around. A Web Connect file has the extension .qbo. Desktop does not read a plain CSV as a bank file, and a Quicken QFX file is usually refused until it is changed into a QBO file. Other routes exist, but they work differently.
The two ends of the confusion are worth separating. QuickBooks Online has an upload screen that accepts a CSV and lets you map its columns. Desktop has no such screen for bank lines. If you start from a spreadsheet, importing a CSV of bank transactions into QuickBooks Desktop explains the three routes and what each one gives up.
What a QBO file does that a CSV cannot
A QBO file is a bank file with a fixed layout. It names the bank, the account, a date range and a list of transactions, and each transaction carries a unique ID. Desktop uses that ID to avoid bringing the same line in twice. A CSV is only rows of text, so Desktop would have to guess what each column means. The format is covered in what QBO files are and how QuickBooks reads them, and this post stays on the import itself.
Where QFX and OFX files fit
Banks that serve Quicken customers often offer a QFX file. Many banks also offer a file called OFX. These are close relatives of QBO, but Desktop is picky about which one it accepts. When a bank offers a choice, pick the one labelled for QuickBooks. If the bank only offers QFX, the file may need to be converted first, and a converter should be tested on one month before you rely on it.
What the file cannot do
A Web Connect import brings in transactions. It does not bring in a PDF, a scanned page or an image of a statement. If all you have is a PDF, read importing PDF bank statements into QuickBooks Desktop, which covers turning the PDF into a QBO file first.
Linking the Web Connect file to a Desktop bank account
Desktop links the file to a QuickBooks account the first time you open it. It asks whether to use an existing account or make a new one, and that choice decides where every line lands. Make it deliberately, because an import cannot be undone from the file menu.
Before you start
Two preparation steps save the most trouble. First, make a backup of the company file. Intuit's guide to importing and exporting data in QuickBooks Desktop states that you cannot undo an import and advises a backup before any import. Second, be signed in to your Intuit Account inside Desktop, which the same page lists as a requirement for importing Web Connect files.
Also confirm that the account already exists in your chart of accounts. If you plan to link to an existing account, know its name. Lists with several similar names, such as "Checking," "Checking 2" and "Business Checking," are where most mislinks begin.
The import steps
The steps below match the Web Connect import described by Intuit. Menu wording can differ a little between versions, so read each prompt before you click.
- Close any open dialogs and open the company file you want to import into.
- Choose File > Utilities > Import > Web Connect Files.
- Browse to the saved .qbo file and choose Open.
- At the prompt that asks which account to use, choose Use an existing QuickBooks account and pick your bank account from the list. Choose Create a new QuickBooks account only if this really is a new account.
- Choose Continue. Desktop reads the file and reports how many transactions it brought in.
- Choose OK on the success message. Desktop opens the Bank Feeds Center, where the lines wait for review.
An example of the choice at step 4: you have a checking account named "Business Checking (4417)" in the chart of accounts, and the file is from that same account. You choose the existing account. If you choose to create a new one by accident, QuickBooks makes a second account that has no history, and the new lines have nothing to match against.
The prompt that asks for an account
The account prompt is the one that matters most, so it helps to know what is behind it. After you link a file to an account, Desktop remembers the link between the bank named in the file and that QuickBooks account. The next file from the same account usually goes straight to the right place, but a file from a different bank account may open the prompt again. Read it each time rather than pressing Continue by habit.
When the file belongs to a credit card
A credit card file asks for a credit card account, not a bank account. If the card is missing from the list, the account type is wrong or the file is the wrong type of file for a card. Setting up the card correctly is the subject of downloading credit card transactions into QuickBooks Desktop.
Reviewing imported transactions in the Desktop Bank Feeds center
After the import, the lines are not yet in your books. They sit in the Bank Feeds Center as items to review, and nothing reaches the register until you add or match each one. This review step is where you decide what each line is.
What you see
Each imported line shows a date, a payee or description, and a payment or deposit amount. For each line, Desktop either finds a match among transactions already in the register, suggests a category, or leaves it for you to fill in.
Accepting, matching and adding
A line can end up in one of three states:
- Matched. Desktop found an existing transaction with the same amount and a close date, such as a check you already wrote. Accepting the match marks that transaction as cleared and adds nothing new.
- Added. There was nothing to match, so the line becomes a new transaction. You choose the payee and the account, and Desktop adds it to the register.
- Excluded. The line should not become a transaction, for example a duplicate you already entered by hand. You can leave it out instead of accepting it.
Matching depends on the lines being close. A check written on March 3 for 412.80 and a bank line on March 6 for 412.80 will usually match. A line whose amount differs by a few cents will not, and you will see it as a new item next to the original. Compare the two before you accept both.
A short review routine
Work through the list in this order, and the review stays short:
- Sort by date and scan for lines outside the period you meant to import.
- Accept the matched lines first. They are the safest.
- Handle each unmatched line: pick the payee, pick the account, add it.
- Look for pairs of lines with the same amount, which can be a double.
- When the list is empty, compare the register balance to the bank's balance for the last date.
Step 5 is the proof that the import is complete. Open the account register and compare the ending balance to the balance printed on your statement or shown by your bank for the same date. If the two differ, the gap is usually one missing line, one extra line, or an opening balance that was never entered.
Why importing twice is a risk
Desktop skips transactions it has seen before by their IDs, but a file made from a PDF or a spreadsheet may have IDs that change from run to run. Importing two overlapping files from such a source can bring in the same lines twice. Keep the date ranges separate, and write down which month each file covered.
Desktop import errors such as an unsupported bank
When Desktop refuses a file, the message usually points at the file itself, the bank named in it, or the state of your Intuit sign-in. Most failures come down to a handful of causes, and checking them in order is faster than retrying the same file.
The file will not open at all
If double-clicking the file does nothing, or it opens in the wrong version of QuickBooks, the .qbo extension may be linked to a different program. Open QuickBooks first and use File > Utilities > Import > Web Connect Files instead. Starting from inside Desktop removes the question of which installation should respond.
A message about the bank or the file format
A message saying the bank is not supported, or that QuickBooks cannot read the file, usually means the bank identification inside the file did not pass Desktop's checks. Banks are identified by an ID in the file header, and files made by hand or by a generic tool can carry an ID that Desktop does not recognize. The line is explained in the bank ID line Desktop checks. If your file came from a converter, the usual fix is to convert again with the converter's setting for your bank, not to edit the file.
Transactions that were skipped
If the import succeeds but fewer lines appear than you expected, the missing ones were probably recognized as duplicates. That is Desktop doing its job when you have imported the same period before. If you never imported that period, check the date range in the file itself. A file that covers only part of a month will only bring in that part.
The account type does not match
A checking file linked to a credit card account, or the reverse, breaks the signs of the amounts. If you see deposits where purchases should be, the file is probably linked to the wrong kind of account. Undoing that means deleting the imported transactions one at a time or restoring the backup, which is why the backup in the first section pays for itself here.
When to stop and ask for a better file
If a file fails twice, stop trying variations. Ask the bank for a fresh QBO download, or rebuild the file from the original statement. Each retry of a damaged file adds the chance of a partial import that is harder to clean up than a clean failure.
Which QuickBooks Desktop versions stop accepting Web Connect files?
Intuit retires each Desktop version after a set period, and a retired version loses online services. That affects downloads and may affect importing a file, so check your exact version before you plan around it. An old version that still opens your data is not the same as one Intuit still supports.
Intuit's service discontinuation policy for QuickBooks Desktop 2023 says that QuickBooks Desktop 2023 products, including Pro Plus, Premier Plus and Enterprise 23.0, stop getting support after May 31, 2026. It also says that after discontinuation you cannot download transactions, and that uploading transactions will be discontinued. The page does not name Web Connect, so it does not tell you whether a file import still works on a retired version. Treat that as open and test it.
How to check your own version
Press F2 while a company file is open to see the product information window, which lists the product and release. Compare the product year against Intuit's list for your version. Because policies change, read the current Intuit page for your version instead of relying on a blog post, including this one.
What to do on an unsupported version
The choices are to upgrade, or to keep entering transactions by hand, which needs no Intuit service. They are weighed in what happens to Desktop downloads after a version's support ends.
Using SimpleBankConvert for the file
If the bank only gives you a PDF, SimpleBankConvert is being built to turn a statement into a QBO file with import steps written in plain words; accounts are not open yet. For a bank that already offers a QBO download, use that file; it needs no conversion.