Import Bank Statements into QuickBooks Online

TL;DR: QuickBooks Online imports bank transactions from files through its upload option in the banking area. Use a QBO (Web Connect) file when you can, because it needs no column mapping and carries transaction IDs; use a three- or four-column CSV otherwise. Imported transactions land in For Review, where you match or categorize them, and then you reconcile against the statement's closing balance.

Bank feeds are the default way transactions get into QuickBooks Online, and when they work, they're great. But there are plenty of reasons to import files instead: the bank isn't supported, the feed only pulled a limited history when you connected, it broke for a few weeks, you're setting up a new company with past months, or a client handed you PDFs.

This is our end-to-end process for importing statements into QuickBooks Online and making sure the result is right. If you've already hit an error, jump to our QuickBooks Online CSV import errors guide.

Before you import: three decisions

1. Which bank account in QuickBooks?

Each import goes into one account in your chart of accounts. Make sure the account exists, has the right type (bank or credit card), and, for a new account, has the correct opening balance as of the day before your first imported transaction.

2. Which file format?

Format	Pros	Cons
QBO (Web Connect)	No mapping, transaction IDs reduce duplicates, behaves like a bank feed	You need a QBO file; banks offer them for recent activity, converters produce them from PDFs
CSV	Universal, easy to edit	Column mapping each time, no IDs, more formatting pitfalls

We default to QBO. Our comparison of QBO vs IIF vs CSV has the details. IIF is a Desktop format and doesn't apply to QuickBooks Online.

3. What date range?

If the account has a live bank feed, decide a cutoff date: files for everything before it, the feed for everything after. Overlapping ranges are the number one cause of duplicates.

Getting the file

From your bank: many banks let you download recent activity as QBO, QFX or CSV. Use the statement period dates so the file lines up with the statement.

From PDF statements: convert them. SheetStatement's bank statement to QuickBooks converter produces a QBO file or a QuickBooks-ready CSV from PDFs, including scans, and checks that each statement balances first.

Whichever route, verify before importing: opening balance + all transactions = closing balance. Importing incomplete data just moves the problem into QuickBooks.

Step-by-step: uploading the file

QuickBooks Online's menus are updated from time to time, so labels may differ slightly, but the flow is consistent:

1. Go to the banking area (often labeled Banking or Transactions > Bank transactions).
2. Find the upload option. Look for something like Upload transactions or Link account > Upload from file. It may sit under a dropdown next to the button for connecting accounts.
3. Choose your file (QBO, QFX, OFX or CSV).
4. Select the QuickBooks account the transactions belong to.
5. For CSV only: map the columns. Tell QuickBooks which column is the date, the description and the amount (or credit and debit), whether the first row is a header, and the date format.
6. Review the preview and confirm.
7. Wait for the import to finish. Transactions appear in the For Review tab of that account.

Mapping a CSV correctly

A clean three-column CSV:

Date,Description,Amount
03/03/2026,OFFICE SUPPLY CO,-84.12
03/05/2026,CLIENT PAYMENT ABC,2400.00

On the mapping screen:

• Date → Date column, with the matching format (here, MM/dd/yyyy).
• Description → Description column.
• Amount → "One column" option, pointing to Amount. Negative values are money out.

For a four-column file (Date, Description, Credit, Debit), choose the two-column amount option and map money in and money out carefully. Swapping them is easy.

Reviewing imported transactions

Nothing is in your books yet. For Review is a staging area, and how you handle it decides the quality of the result.

Check a sample first

Pick three transactions: a deposit, a withdrawal, and one dated after the 12th. Confirm date, amount and direction. If they're right, the import is right.

Match before you add

If you've already recorded invoices, bills, expenses or transfers for the period, QuickBooks suggests matches. Matching links the bank line to the existing record. Adding creates a new transaction. Add something that should have been matched and you've doubled it.

Use rules for recurring items

Create bank rules for transactions that repeat: payroll, rent, subscriptions, utilities, processor payouts, fees. Rules save time on every future import.

Handle transfers as transfers

A transfer to savings or a payment to a credit card should be recorded as a transfer between the two accounts in QuickBooks, not as an expense. If both accounts are imported, match the two sides to the same transfer.

Exclude genuine duplicates here

If a transaction is in For Review but already in the books (for example, from a feed), exclude it. Excluding from For Review is far easier than deleting later.

What the For Review actions actually do

The buttons in For Review have consequences that aren't always obvious, so here's how we think about them.

Action	What it does	When to use it
Add / Categorize	Creates a new transaction in the books using the category you choose	The bank line has no existing record in QuickBooks
Match	Links the bank line to a transaction already in the books	You've already entered the invoice payment, bill payment, expense or transfer
Transfer	Records movement between two of your own accounts	Card payments, savings transfers, moving money between accounts
Exclude	Removes the line from For Review without adding anything to the books	Duplicates, personal items in a business account that you handle separately, test lines
Split	Divides one bank line across several categories	One payment that covers more than one kind of expense

The difference between Add and Match is the most important one. If an invoice payment from a customer was already recorded when you received it, the deposit on the bank statement should be matched to it. Adding it would count the income twice: once from the invoice payment, once from the deposit.

Undoing a mistake

If you add or match a transaction incorrectly, you can usually undo it from the reviewed or categorized tab of the banking screen. Undo sends the line back to For Review, where you can handle it properly. Excluded lines can similarly be restored or deleted from the excluded tab.

If a whole import was wrong, for example the signs were reversed, the cleanest fix is often to exclude or delete everything from that batch while it's still in For Review, correct the file, and import again. Once transactions are accepted and reconciled, cleanup is slower, which is another reason to check a sample before accepting anything.

Several accounts, one month at a time

Businesses with several bank and card accounts get the best results by working month by month across all accounts, rather than account by account across all months. Import January for checking, savings and each card; handle transfers between them while both sides are in front of you; reconcile all of them; then move to February.

The reason is transfers. A card payment appears in checking and on the card. If you import checking for the whole year first, you'll categorize those payments without the card side available, and it's easy to record them as expenses by mistake. Working month by month keeps both sides of every transfer visible at the same time.

Working with an accountant

If an accountant or bookkeeper also works in the company file, agree on who imports what. Two people importing the same statement on different days is a reliable way to create duplicates. A shared log, even a simple spreadsheet listing account, period, file name, who imported it and whether it's reconciled, prevents that. It also makes handovers painless when someone else picks up the books.

Reconciling after import

Once a month's transactions are accepted, reconcile:

1. Open the reconcile tool for the account.
2. Enter the statement ending date and ending balance.
3. Tick off the transactions that appear on the statement.
4. The difference should be zero.

If it isn't, our guide to finding reconciliation discrepancies has a systematic approach. The usual culprits after an import are duplicates (feed overlap), a wrong opening balance, or a transaction added instead of matched.

Importing historical months for a new company

When you're setting up QuickBooks Online and want past months in it:

1. Set a start date for your books.
2. Create each bank and card account with its opening balance on that date (from the statement).
3. Import statements month by month, oldest first.
4. Reconcile each month before importing the next.
5. Connect the bank feed last, and if it offers a start date, set it to the day after your last imported statement.

This order keeps every month reconcilable. Connecting the feed first and then backfilling with files almost guarantees duplicates.

Importing credit card statements

The same process applies, with one difference: the account must be a credit card account in QuickBooks. After import, check that a purchase increased the card balance and a payment decreased it. If a CSV came from an issuer that writes purchases as positive numbers, QuickBooks may interpret them backwards; flip the signs and re-import if needed. A QBO file avoids the ambiguity because it carries the account type. Our credit card statement converter produces card QBO files.

When the bank feed and the statement disagree

After importing statements alongside a live feed, you may notice the feed's version of a transaction looks different from the statement's: a slightly different description, a different date, or (rarely) a different amount. Descriptions and dates often differ because feeds and statements are produced by different systems at the bank. That's normal, and the amounts should still agree.

When an amount differs, trust the statement for the period it covers. It's the bank's official record. The feed may have captured a pending amount (a restaurant bill before the tip, a hotel hold) that later posted differently. Correct the transaction in QuickBooks to the posted amount and reconcile to the statement.

A worked example

A bookkeeper takes on a new client in April who wants the books started from January 1. The client's bank feed was connected in March and pulled transactions from mid-February onward.

1. Cutoff: she sets the cutoff at February 14, the day before the feed's first transaction.
2. Files: the client sends January and February PDFs. She converts them to QBO, verifying that each balances.
3. Opening balance: she checks the checking account in QuickBooks has the December 31 statement balance as its opening balance. It doesn't (it was set to zero when the feed connected). She corrects it.
4. Import January: uploads the QBO file, checks three transactions, matches two existing invoices, creates rules for 12 recurring payees, and accepts the rest.
5. Reconcile January: zero difference.
6. Import February: the QBO file covers the whole month, so she excludes everything from February 15 onward in For Review, because the feed already has it.
7. Reconcile February: zero difference.

Two months of history, imported and reconciled, without retyping a single line, and with no duplicates.

Tips from experience

• Import a month, reconcile a month. It catches problems early.
• Keep the PDFs. QuickBooks has the transactions; the PDFs are your evidence.
• Name your files with account and period so you can see at a glance what's been imported.
• Don't edit reconciled transactions without a very good reason. It breaks future reconciliations.
• Review rules periodically so they don't miscategorize new vendors with similar names.
• Check the file size before uploading a long period. Very large files can fail; splitting by month avoids it and makes each batch easier to review.
• Keep descriptions as the bank wrote them. Rules and auditors both work better with the original text than with descriptions you've rewritten.

Our take

Importing statements into QuickBooks Online is straightforward when the inputs are right: a verified file, the correct account, a clear cutoff, and patience in For Review. Use QBO files when possible, CSV when needed, and reconcile every month as you go. The result is books that match the bank exactly, built in a fraction of the time manual entry would take.

Troubleshooting after the upload

Transactions went to the wrong account. Exclude them from For Review in that account, then upload the file again to the correct one. If you've already accepted them, undo or delete them first.

Matches are suggested to the wrong transactions. QuickBooks suggests matches by amount and date. If a suggested match is wrong, choose to add the transaction as new or find the correct match manually. Don't accept matches in bulk without checking.

Bank rules miscategorize. Review rules that use short keywords; they may match more payees than intended. Make conditions more specific, and order rules from specific to general.

The reconciliation beginning balance doesn't match. Something in a previously reconciled period changed. See our guide to opening balance mismatches.

Uploaded transactions disappear from For Review. They may have been excluded or accepted by someone else. Check the Excluded tab and the account register.

A second worked example: a gap in the bank feed

A client's bank feed disconnected from August 10 to August 28. The bookkeeper downloaded the August statement, converted it, trimmed the file to August 10 through August 27 (the 28th was already in from the reconnected feed), uploaded it to the account, and reviewed the 47 transactions. Two had already been entered manually by the client; she matched those instead of adding them. The August reconciliation balanced first time.

Mini checklist before uploading

1. Correct account selected.
2. Dates in the file don't overlap the feed or previous uploads.
3. Signs and dates checked on a few known transactions.
4. Bank rules reviewed for anything too broad.
5. Month reconciled after review.

FAQ

Can QuickBooks Online import bank statements?

Yes. In the banking area, use the option to upload transactions from a file. It accepts formats such as QBO, QFX, OFX and CSV, and imported transactions go to For Review.

Can I upload a PDF bank statement to QuickBooks Online?

The bank upload expects a transaction file rather than a PDF. Convert the PDF to QBO or CSV first, verify it balances, then upload.

Should I use CSV or QBO for QuickBooks Online?

QBO is usually better: no column mapping and transaction IDs that help prevent duplicates. CSV works well when the file is clean and correctly mapped.

How do I avoid duplicates with a bank feed connected?

Pick a cutoff date. Import files only for dates before the feed's first transaction, and exclude any overlapping lines in For Review.

Why doesn't my account reconcile after importing?

Common causes are duplicates from feed overlap, an incorrect opening balance, transactions added instead of matched, or an incomplete source file.

Can I import credit card statements the same way?

Yes. Import into a credit card account in QuickBooks and check that purchases increase the balance and payments decrease it.