How to Import Bank Transactions into QuickBooks Online

To import bank transactions into QuickBooks Online by hand, go to All apps, then Accounting, then Bank transactions, and choose Upload from file. Drop in the bank's CSV, QBO or QFX file, pick the QuickBooks account, match the file's columns to Date, Description and Amount, select the rows to import, and review them on the For review tab.

Where the QuickBooks Online upload-from-file option lives

The QuickBooks Online upload-from-file option lives on the Bank transactions page. Intuit's article Manually upload transactions into QuickBooks Online gives the path: All apps, then Accounting, then Bank transactions. From there, the Link account dropdown holds Upload from file.

The exact button depends on whether the account already has a tile on that page. Intuit's article says to select the account tile if you see one, then open the Link account dropdown and choose Upload from file. If the account is not connected, it says to use Upload from file or the link reading Or upload transactions manually.

Before the first click, Intuit's article lists three preparations:

• Get the file from the bank. A transaction list in .csv, .txt, .qbo or .ofx form, in English, 350 KB or less, and up to 1,000 lines. The same article also names QFX and suggests a QBO file where the bank offers one.
• Check the chart of accounts. Make sure the target account exists once, so the upload does not go to a near-duplicate.
• Set up bank rules if you want them. Rules set beforehand can categorize transactions as they arrive.

The whole click path, from the Bank transactions page to the review list, runs like this for a fictional client, Example Client LLC, with a checking account ending XXXX-4821:

1. Go to All apps, then Accounting, then Bank transactions.
2. Select the account tile, open the Link account dropdown and choose Upload from file.
3. Select Drag and drop or select files, choose the CSV, and select Continue.
4. Choose the QuickBooks account, or Add New for an account that does not exist yet, and select Continue.
5. Match the file's columns to the QuickBooks fields and select Continue.
6. Select the transactions to import and select Continue.
7. Confirm the import and select Done.
8. Open the account's For review tab to categorize or match each new row.

Steps 1 to 7 follow Intuit's manual upload article, which ends step 7 with Yes, then Done. Step 8 uses the tab name from Intuit's duplicate transactions article, cited in the review section below.

Mapping CSV columns on the QuickBooks Online upload screen

Mapping CSV columns on the QuickBooks Online upload screen means telling QuickBooks which column in your file is the date, which is the description and which holds the amount. Intuit's manual upload article states the step plainly: match the columns in the file with the correct fields in QuickBooks, then select Continue.

Intuit's video guide How to upload transactions manually describes what the screen asks for. In words, the mapping screen works through four things:

• Header row. You tell QuickBooks about the file's header columns, so it does not read the header line as a transaction.
• Date format. You choose the date pattern the file uses. Every date in the file has to follow it.
• Column matching. Each QuickBooks field gets a column from your file: Date, Description, and either one Amount column or a Credit column and a Debit column.
• Signs. You confirm that money in and money out show the right way round. If they are reversed, the video says to select Reverse all values.

Here is an example five-row file in the 3-column layout, the one Intuit's article Format CSV files in Excel to get bank transactions into QuickBooks shows with payments as negative amounts and deposits as positive. All names and amounts are examples.

Date,Description,Amount
03/02/2026,Deposit Northgate Media,4200.00
03/04/2026,Card purchase Office Depot,-86.40
03/09/2026,ACH Harbor Insurance,-312.00
03/15/2026,Transfer from savings,1500.00
03/27/2026,Check deposit,950.00

With that file, the mapping is direct: Date to Date, Description to Description, Amount to Amount, and the date pattern set to month, day, year. If the file used separate money-in and money-out columns instead, you would map two amount columns. The post on 3-column versus 4-column CSV layouts explains which layout to use and how to convert between them.

Column layouts and date rules have their own post. For which columns QuickBooks needs and which it ignores, read which columns a QuickBooks Online bank CSV requires.

Which QuickBooks Online account should the uploaded transactions land in?

The uploaded transactions should land in the QuickBooks Online account that matches the bank or card account the file came from: same institution, same account type, same last four digits. QuickBooks asks for the account right after the file is chosen. Pick the existing account, or choose Add New if it does not exist yet.

Naming accounts by bank and last four digits makes the choice hard to get wrong. "Harbor Federal Checking XXXX-4821" leaves no doubt. "Checking 2" does. Before uploading, compare the account number on the bank file or statement with the account name in QuickBooks.

Intuit's article Fix bank upload errors describes one guardrail. The message "The uploaded file is of a different type than these accounts" usually means the wrong account type was selected, such as checking when the file is from savings. Cancel lets you choose again; OK continues anyway. Read that message as a prompt to check, not a step to click through.

Two account situations need extra care:

• Credit cards. Intuit's CSV formatting article says to select the credit card account rather than a bank account when uploading card transactions. It also warns that card files can list transactions in reverse order and show deposits as negative amounts.
• Subaccounts. Intuit's article Common errors for importing bank transactions using CSV says you cannot import transactions into a subaccount. Its alternatives are to connect the subaccount directly to the feed or enter the transactions by hand.

The manual upload article also suggests setting up parent accounts and subaccounts in the chart of accounts before uploading, so you know in advance which account each file belongs to.

Reviewing uploaded transactions in the For review list

The For review list is the tab on the Bank transactions page that holds downloaded and uploaded transactions waiting for action. Each row there needs one decision: categorize it as a new transaction, match it to one already recorded, or exclude it. Work through the list in one pass per file, so nothing from the upload is left waiting.

Intuit's manual upload article says that once the import is done, the next step is to categorize the uploaded transactions so they land in the correct accounts. It also notes that QuickBooks may add details based on recognized descriptions or bank rules. Intuit's article Fix duplicate transactions in QuickBooks Online Desktop bank feeds names the tab: For review, which may be labeled Pending.

A practical order for the review:

1. Sort by date and scan the first and last rows. They should match the first and last transactions in the file.
2. Look for matches. Payments already entered as bills or checks should be matched, not added again.
3. Let rules do the repeat work. Intuit's article Set up bank rules to categorize online banking transactions in QuickBooks Online says rules apply to transactions in the For review tab and can match on the description with Contains, Doesn't contain or Is exactly.
4. Exclude what does not belong. If you exclude the wrong row, Intuit's duplicates article says to open the Excluded tab, select it and choose Undo.

How each row should be categorized is the firm's judgment for that client. This post covers getting the rows in front of you in the right place.

What if QuickBooks Online uploads zero transactions?

When QuickBooks Online uploads zero transactions, or the preview shows no rows, the file has a problem QuickBooks cannot read. Intuit names the causes to check: columns mapped to the wrong fields, dates that do not match the chosen format, amounts with currency symbols or commas, and special characters in the descriptions.

Intuit's common errors article gives these fixes:

• Check the mapping. Delete columns QuickBooks does not need and rename headers to match its field titles. Intuit says QuickBooks requires only Date, Description and Amount.
• Clean the amounts. In Excel, right-click the amount column, choose Format Cells, and change the category from Currency to General.
• Clean the descriptions. Remove special characters; Intuit suggests Ctrl+H to find and replace them.
• Fix the dates. Make sure they match the format chosen during mapping. Intuit suggests setting the column's number format to Short Date in Excel.
• Copy into a blank sheet. Intuit notes that copying the contents into a blank spreadsheet may reveal something you had not seen.

Two cases drop rows rather than the whole file. A file with separate debit and credit columns that holds only money-out rows may fail; Intuit's workaround is to add one positive line and untick it on the final screen. And Intuit's upload errors article says a transaction with 12 or more digits cannot upload and should be removed and entered by hand.

The cleanup steps for a bank file that fails this way are in the post on cleaning a CSV before importing it to QuickBooks.

Manual transaction uploads on an account that also has a feed

A manual transaction upload on an account that also has a bank feed puts two sources into the same For review list. That works only when their date ranges do not overlap. Upload a file for the months the feed does not reach, and leave the feed's months to the feed.

Intuit's duplicates article lists importing a file that overlaps transactions already in the bank feed as a cause of duplicates. For an older period, the file has to stop before the first day the feed downloaded. Intuit's start-date rules for files and feeds are set out in the post on setting an import cutoff date.

An example: Example Client LLC connected its Harbor Federal checking account in October 2026, and the feed pulled from October 1. The firm needs January through September. The upload file should end on September 30, so no row overlaps the feed. Before uploading, open the account's register and confirm the earliest feed transaction date.

The post on what a QuickBooks bank feed pulls and how far back covers the feed side of the overlap. If doubles already landed, the post on why QuickBooks imports create duplicate transactions covers undoing them.

Uploaded months still need to be reconciled against the statements. The bank reconciliation category covers that step for QuickBooks Online and other tools.

When the only source for those older months is a stack of PDF statements, the file has to be built first. Schema CPA reads a client's bank statements, flags any month missing from the run, and gives the firm the transactions as a CSV or Excel file to upload through the steps above; it does not connect to QuickBooks itself. The workflow section of the homepage shows where export sits in the process.