How to import bank statements into QuickBooks

There are four ways transactions get into QuickBooks, and picking the wrong one is how people end up doing an afternoon of work that should have taken ten minutes.

Here they are in the order worth trying.

1. The bank feed, if your bank is supported

Connect the account once and transactions arrive on their own, usually daily, with the ids that stop duplicates.

In QuickBooks Online: Transactions, then Bank transactions, then Link account, then find your bank and sign in. In Desktop: Banking, then Bank Feeds, then Set Up Bank Feed for an Account.

Two limits worth knowing before you rely on it. Feeds typically backfill only 90 days, sometimes less, so a feed does not help with last year. And plenty of smaller banks and credit unions are not on the list at all.

If the feed covers you and you only need recent months, stop here. Everything below is for when it does not.

2. CSV, which is the right answer on QuickBooks Online

QuickBooks Online imports CSV directly and it is the easiest route to correct, because you can open the file and fix a description or delete a duplicate before anything reaches your books.

Transactions, then Bank transactions, then the dropdown next to Link account, then Upload from file. Pick the CSV, choose the account, and QuickBooks shows a mapping screen.

The mapping screen wants three things and offers two shapes:

QuickBooks asks	What to give it
Date	The column with the posting date, and the format it is in
Description	The payee text
Amount	Either one column with negatives, or two columns for money in and money out

The format dropdown next to Date is the one to slow down on. Choosing DD/MM/YYYY when your file is MM/DD/YYYY does not cause an error: it silently reads the 3rd of June as the 6th of March for every date that could be either.

QuickBooks Online also has limits on the file itself: a maximum of about 1,000 rows and 350 KB per upload. Split a long year into quarters if it complains.

3. QBO files, which is the answer on Desktop

QuickBooks Desktop does not import CSV in most editions. It wants a Web Connect file.

File, then Utilities, then Import, then Web Connect Files. Choose the .qbo and pick the account. The transactions land in the Bank Feeds centre for review rather than straight in the register, which is deliberate: you categorise them there and add them in a batch.

Where does the .qbo come from? Your bank, if it offers one, and several charge a monthly fee for the privilege because the format is licensed from Intuit. Otherwise convert the free export: CSV to QBO if you have a spreadsheet, or the PDF statement straight to QBO if that is all you have.

4. From a PDF, which always means converting first

QuickBooks reads no PDFs at all, in either product. The transactions have to be extracted first, and then you are back to route 2 or route 3.

The converter here reads the statement in your browser and writes CSV and Excel for Online, or QBO and QFX for Desktop, and checks the running balance so you know nothing was dropped between the page and the file.

Which route for which situation

Situation	Use
Recent months, supported bank, either product	The bank feed
QuickBooks Online, any file	CSV upload
QuickBooks Desktop, any file	Convert to QBO
Older than the feed reaches	CSV or QBO from the statement
Credit card, either product	Same routes, with the account type set to credit card
A closed account	PDF statements converted, since there is no feed to connect

Credit cards need one extra check

The mechanics are identical and the sign convention is not. A credit card account in QuickBooks treats a charge as an increase in what you owe, and a payment as a decrease. Import a card statement into a checking account, or write a QBO with the wrong account type inside it, and every payment reads as a deposit.

When converting, set the account type to credit card before downloading. When uploading a CSV, pick the credit card account on the upload screen rather than relying on the file.

After the import

Three things are worth doing every time, in this order:

Check the count. Whatever tool produced the file reported how many transactions it held. QuickBooks reports how many it accepted. Those two numbers should differ only by transactions it recognised as already present.

Check one known refund. Find a transaction you know was money coming in and confirm it reads that way. If it is inverted, the amount columns were mapped the wrong way round and it is far quicker to undo and re-import than to fix row by row.

Reconcile against the statement. Opening balance plus everything in minus everything out should equal the closing balance the bank printed. This is the check that catches a dropped row, and it is the only one that proves the import is complete rather than merely plausible.

If any of those fail, undo the import rather than patching it. In QuickBooks Online, Bank transactions, then the account, then the arrow next to the imported batch, then Undo. In Desktop, delete the batch from the Bank Feeds centre before adding it to the register.