How to Review Imported Bank Transactions in QuickBooks Before Adding

Short answer: Imported bank transactions do not post to your books automatically. They land in the For Review tab in QuickBooks, where you check each one, assign a category and payee, match it to any existing entry, and only then add it to the register. Reviewing before you add is what keeps your reports accurate and your reconciliation clean, so never bulk-accept an import you have not looked at.

Why imported transactions need a review step

When you connect a bank feed or upload a QBO, QFX, or CSV file, QuickBooks does not drop those transactions straight into your books. It stages them in the For Review tab (QuickBooks Online) or the Bank Feeds center (QuickBooks Desktop). That staging area exists for a reason: an import brings in raw bank activity with the bank's own descriptions, and those descriptions rarely match how you want the transaction categorized or who the payee actually is. Reviewing is where raw bank data becomes correct accounting.

Skipping the review and clicking "Accept all" is the fastest way to end up with a pile of Uncategorized Expense entries, duplicate transactions, and a reconciliation that will not balance. A few minutes of review per import saves hours of cleanup later.

How do I review bank transactions before adding them in QuickBooks?

Review transactions in the For Review tab before adding them. In QuickBooks Online, go to Transactions, Bank transactions, and open the For Review tab for the account. For each transaction, confirm the date and amount, set the correct category (account) and payee, decide whether it is a Match to an existing entry or a new Add, then click Add or Match. Nothing hits your books until you do. Repeat per account.

What to check on each transaction:

• Category. QuickBooks may guess based on past rules, but verify it. A payment to a vendor could be an expense, an asset purchase, or a transfer.
• Payee. Bank descriptions are cryptic. Set a clean payee name so reports and vendor totals are usable.
• Match vs Add. If you already recorded an invoice, bill, or transfer, match the bank line to it instead of adding a second copy. Matching is how you avoid duplicates.
• Transfers. Money moving between your own accounts should be recorded as a transfer, not as income or an expense, or you will double-count it.

Catching duplicates during review

Duplicates are the single biggest risk with imports, and review is where you catch them. They happen when the same transaction arrives twice, for example from an overlapping statement date range, or when a bank line is added new even though you had already entered it manually. During review, use Match rather than Add whenever QuickBooks shows a suggested match, and watch for two identical amounts on the same date. If duplicates slip through, our guide on fixing a wrong opening balance after a QBO import covers how to find and remove them.

One clean habit prevents most duplicates: do not import overlapping date ranges. If your last import ended March 31, start the next file on April 1. Converting statements to precise, month-bounded files makes this easy.

Why file quality makes review faster

The cleaner the import file, the less work the review takes. A well-built .qbo file carries proper dates, amounts, and unique transaction IDs, so QuickBooks can suggest matches and avoid duplicates on its own. A messy CSV with inconsistent columns forces you to fix formatting during review, which is slower and more error-prone.

That is why we build tidy import files from the source statement. Our PDF bank statement to QuickBooks converter reads every transaction straight from the PDF and outputs a .qbo (Web Connect) or .iif file with clean dates and amounts, so your For Review list is accurate before you even open it. For scanned or photographed statements, see converting a scanned bank statement to QuickBooks, and for the .qbo versus .iif choice, which QuickBooks import file to use.

Using bank rules without losing the review

Bank rules in QuickBooks Online can auto-categorize recurring transactions, which speeds up review a lot. Set a rule so that a recognizable description gets the right category and payee every time. But keep rules on "review" rather than fully automatic when you are starting out, so you can confirm the rule is doing the right thing before it posts transactions on its own. Once a rule is proven, letting it auto-add is safe, and it turns a long For Review list into a short one.

Should I categorize transactions before or after importing?

Categorize during review, after importing but before adding. The import brings the transactions in; the review step is where you assign categories and payees; adding is what posts them. Doing it in that order means every transaction is categorized correctly the moment it hits your books, so your profit and loss and balance sheet are right without a later cleanup pass. Trying to categorize before importing, by editing the raw file, is slower and easy to get wrong.

What happens if I add a transaction I should have matched?

If you clicked Add on a transaction that should have matched an existing entry, you now have a duplicate: the original record plus the newly added bank transaction. Fix it by deleting the duplicate you created, then matching the bank line to the correct existing entry. Catching this during review is far easier than after reconciliation, which is the whole argument for reviewing carefully instead of bulk-accepting.

After review: reconcile

Once you have reviewed and added an account's transactions, reconcile it against the statement ending balance to confirm nothing is missing or doubled. Our walkthrough on bank reconciliation from PDF bank statements covers the full month-end process. If transactions seem to be missing from the feed rather than the import, see why the QuickBooks bank feed is missing transactions.

If you prefer to eyeball everything in a spreadsheet first, a PDF bank statement to Excel converter gives you a reviewable workbook before anything reaches QuickBooks. And when your data starts life as a CSV export, a CSV to QBO converter turns it into a clean import file so your review list stays tidy.

The bottom line

Never let an import post itself. Imported transactions wait in For Review so you can set the right category and payee, match instead of duplicate, and flag transfers before anything touches your books. Start with a clean import file, review deliberately, then reconcile. That order is what keeps QuickBooks reports you can trust.