How to upload a bank statement to QuickBooks Online

The short answer: in QuickBooks Online, go to Transactions → Bank transactions, open the dropdown next to Link account and choose Upload from file. Drop in a CSV, QBO, QFX or OFX file, tell QuickBooks which account it belongs to, map the columns if it's a CSV, and the transactions land in For Review. Nothing reaches your books until you add or match them there. If the statement only exists as a PDF, convert it to a .qbo file first — QuickBooks' own PDF reading is hit and miss.

Step by step

1. Get the right file. If your bank offers a QuickBooks (.qbo / Web Connect) download, use it — it skips the column-mapping step entirely. Otherwise download CSV. Most banks only offer downloads for the last 90 days to two years; older months have to come from the PDF statements.
2. Open the upload. Transactions → Bank transactions, then the small dropdown arrow beside Link account → Upload from file. (Menu labels shift a little between QuickBooks Online versions; the Upload from file option has stayed put.)
3. Select the file. Drag it in or browse to it.
4. Choose the QuickBooks account. Pick the bank or credit card account from your chart of accounts — or add it there if it doesn't exist yet. A credit card file belongs in a credit card account, not a bank account.
5. Map the columns (CSV only). Tell QuickBooks which column is the date, the description and the amount — either one signed amount column or separate money-in and money-out columns — and which date format the file uses. QBO, QFX and OFX files skip this step.
6. Confirm the import. QuickBooks shows the transactions it found; select them and continue.
7. Work through For Review. Match transactions to ones already in QuickBooks, or pick an account and add them. Categorizing them well here is what saves the cleanup later.

Which file to upload

A .qbo file is the better upload whenever you can get one: it arrives like a bank feed, with nothing to map and no date format to guess. What a QBO file actually is — and why its transaction IDs matter — has its own guide.

Why uploads fail

• Size. QuickBooks Online caps CSV uploads at 350 KB and struggles past about 1,000 rows. Split a long history into one file per statement period.
• Layout. CSVs have to be a clean 3-column (Date, Description, Amount) or 4-column (Date, Description, Credit, Debit) file with one header row. The full list of CSV rejection rules covers the rest.
• Dates. A day-first file read as month-first swaps days and months, or collapses every date to 1/1/1970.
• "Different financial institution." A .qbo file carries a bank ID; if it doesn't match the account, QuickBooks refuses it. The fix is to re-create the file with the bank ID QuickBooks names in its error message.
• Wrong account type. A credit card file uploaded into a bank account, or the reverse, imports with the signs backwards.

When all you have is a PDF

This is the common case for anything older than your bank's download window. QuickBooks Online can read some PDF statements on its own, but it regularly fails on scans, combined checking-and-savings statements and smaller banks. The reliable route is to convert the PDF to a .qbo file with the PDF to QBO converter and upload that. It checks the conversion against the statement's printed opening and closing balances before you download, so a misread number shows up before it's in your books rather than at reconciliation.

Already have a spreadsheet the bank exported, but QuickBooks won't take it? The CSV to QBO converter turns it into a .qbo so the mapping step and its rules disappear. On QuickBooks Desktop instead of Online, the path is different — Desktop imports Web Connect files through File → Utilities → Import.

After the upload

Once the transactions are added, reconcile the account against the same statement you uploaded from — it is the check that proves nothing was dropped or doubled. The steps, and what to do when the difference won't reach zero, are in how to reconcile a bank statement in QuickBooks Online.