How to Upload Manual Bank Transactions From CSV or Excel in QuickBooks Online Easily 2026

QuickBooks Online's importer expects a simple, consistent structure: one row per transaction, with clear columns for date, description, and amount. Keep dates in a single consistent format throughout the file rather than mixing styles, and decide up front whether your amounts will sit in one column (positive for deposits, negative for withdrawals) or split across separate spend and receive columns — you'll be asked to specify this during import, so it's easier to structure the file correctly the first time than to fix it mid-upload.

From the left-hand menu under Accounting, open Bank transactions. Each connected or manually tracked account shows as its own tile — Salary, Uncategorized Asset, and so on — with a running pending and posted transaction count. Select the account you're uploading into, then use the Link account dropdown in the top right; alongside connecting a live bank feed, it includes the option to upload transactions from a file, which is the entry point into the import wizard.

After selecting your file, the wizard first confirms basic file details — whether the first row is a header, how many columns hold amounts, and what date format the file uses. Step 2 is the important part: match each QuickBooks field (Date, Description, Amount, and an optional Check number) to the correct column from your file using the dropdowns provided. QuickBooks usually guesses correctly if your headers are named sensibly, but it's worth checking every row in this table before clicking Continue, since a swapped Date/Amount mapping is hard to spot until transactions land with nonsense values.

Once the import finishes, the transactions land in the Bank transactions list for that account, sitting under a Pending tab alongside anything already there from a connected feed. Each row shows the date, description, and amount as imported, with columns for assigning a customer or vendor and a category before you post it. Scroll through the full batch and compare the count against your source file — a mismatch usually means a formatting issue skipped a row rather than QuickBooks silently dropping data.

For each row, use the "Select customer" or "Select vendor" field and the category dropdown to classify the transaction, then click Post. Batch-select several rows with matching categories when you can, using the checkboxes on the left, since posting one at a time gets slow once you're working through a file with dozens of rows. Leaving transactions sitting in Pending without posting them means they won't show up correctly in reports, so don't treat the import itself as the finish line.

If transactions come in with the wrong sign, missing amounts, or garbled dates, the fix is almost always back in the column mapping or the source file's date format rather than anything on the QuickBooks side. Duplicate transactions usually mean the same file — or an overlapping date range — got uploaded twice; check the Excluded tab, since QuickBooks sometimes flags likely duplicates there instead of adding them outright. When in doubt, delete the bad batch from Pending and re-run the import rather than trying to hand-correct dozens of rows individually.

After posting a clean batch of imported transactions, run a reconciliation for that account against your actual statement to confirm the ending balance matches. This is the real verification step — a smooth-looking import can still hide an error that only shows up once you check the account's balance against reality, so don't skip it just because the upload itself went without errors.