Use one file per account
Do not combine activity from different real-world accounts in one conversion. A QBO Web Connect file declares an account type and identifiers for the whole file, so every transaction in it should belong to the same checking, savings, or money-market register. For credit-card activity, create a separate normalized CSV and use a current manual-upload workflow that accepts CSV.
- Checking, savings, money-market, and credit-card activity each get their own source and output file.
- For QBO output, enter the explicit bank and account identifiers required by the Web Connect format.
- Confirm the destination account in QuickBooks before continuing.
Choose the date window
Find the latest transaction already present in the QuickBooks register, then export a period that begins after that date. If you deliberately include an overlapping day, review it line by line. Pending transactions can change their dates or amounts after posting, so use posted rather than pending activity whenever possible.
A monthly workflow is easier to reconcile than one very large historical file. Keep a simple log of the account, first date, last date, row count, and import date.
Run four control checks
Compare the converted preview with the bank export before importing.
| Control | Expected result |
|---|---|
| Transaction count | Matches actual transaction rows, excluding headings and totals |
| Date range | Earliest and latest dates match the export |
| Signs | Purchases/withdrawals are negative; deposits/payments are positive |
| Spot check | At least three amounts and descriptions match exactly |
Reconcile after import
Imported transactions are not a substitute for reconciliation. Compare the register with the bank statement’s ending balance and investigate the difference before processing the next period. A difference equal to a familiar transaction amount often indicates a duplicate or omission; a doubled difference can indicate a reversed sign.
Bank2QBO produces a file for manual import and does not connect to, inspect, or modify your QuickBooks company. The final review and categorization remain under your control.
Example import log
A simple control record makes the next import safer. For a fictional operating account, record: source file operating-2026-07.csv; period July 1–31; 86 transaction rows; QBO created July 25; test import July 1–3; full import completed after review. Do not record a full account number or attach the financial file to the log unless your storage policy permits it.
Before the next period, use the log to identify the last completed date and avoid accidentally processing July again. The log does not prove that the register is correct; reconciliation against the bank statement remains the final control.
| Log field | Useful value | Avoid |
|---|---|---|
| Account | Nickname + last four digits | Full account credentials |
| Period | First and last posted date | Vague labels such as “recent” |
| Rows | Actual transaction count | Counting headings or totals |
| Result | Tested, completed, or needs review | Assuming download means imported |
Sources and review notes
John Moores reviewed this guide against the following first-party product documentation on August 12, 2026. QuickBooks features and menus can change; use the linked documentation to confirm the current workflow for your product and region. Our methodology explains how examples, converter tests, and limitations are documented.
- Manually upload transactions into QuickBooks Online — Intuit QuickBooks Support
- Format CSV files in Excel to get bank transactions into QuickBooks — Intuit QuickBooks Support
- Download bank feed transactions in QuickBooks Desktop — Intuit QuickBooks Support