Guide4 min read

How to Import a Bank Statement Into QuickBooks Online (2026 Guide)

QuickBooks Online connects to most banks directly, and when the connection holds there is nothing to do. The trouble starts at the edges: a client sends PDFs rather than granting access, the bank connection drops and takes a fortnight of transactions with it, the account was closed before anyone thought to link it, or the books need backfilling further than the connection reaches. In every one of those cases the way in is an upload, and what you upload decides how much work follows.

This guide covers the whole route: getting a clean file out of a PDF statement, picking between QBO and CSV, uploading it, and not creating duplicates on the way.

Step 1: Turn the PDF into a file QuickBooks accepts

QuickBooks Online cannot read a PDF. It accepts CSV, and it accepts three banking formats: QBO (its own dialect of OFX), QFX and OFX. Retyping a statement is slow and introduces exactly the errors a reconciliation later has to hunt for, so convert it instead.

Drop the statement onto PivotBank and every transaction is extracted in a few seconds, with the running balance recomputed line by line so a page that failed to parse is visible immediately rather than after the import. The conversion happens inside your browser, so a client’s statement never leaves your machine, which is the part that matters if you handle client data under GDPR.

Step 2: Choose QBO over CSV, and why

Both work. They are not equal.

A CSV import asks you to map columns every time, confirm a date format, and agree a sign convention. Get the date format wrong and a 03/04 transaction lands in March instead of April, silently.
A QBO file carries all of that inside the file: typed transactions, unambiguous YYYYMMDD dates, signed amounts, and the account identifiers QuickBooks expects. There is no mapping screen because there is nothing left to map.
QBO also carries a stable ID per transaction, which is what lets QuickBooks recognise a line it has already seen. CSV has no such field, so duplicate detection falls back to guesswork across date and amount.
CSV is still the right answer when you need to edit the rows before they land, or when you are importing into something other than QuickBooks. Excel and CSV come out of the same conversion.

Step 3: Upload it in QuickBooks Online

In QuickBooks Online, open Transactions, then Bank transactions. Choose Link account if the account is not there yet, or select the existing account and use Upload from file. Pick your .qbo file, confirm which QuickBooks account it belongs to, and QuickBooks reads it straight in. A CSV takes the same route but stops at a mapping screen first, where you match Date, Description and Amount to your columns.

Uploaded transactions arrive in the For review tab rather than the ledger. Nothing is posted until you categorise and accept them, so an upload is safe to inspect before it becomes part of the books.

Avoiding duplicates

Duplicates are the one genuine risk in a manual upload, and they come from overlap rather than from the file itself:

Import whole statement periods and never overlap date ranges. Two files covering the same week will present that week twice.
Check what the bank connection already pulled before uploading the same period by hand. This is the common case after a connection breaks and then backfills on its own.
Do not re-upload a file to "make sure it worked". Look in For review instead, which is where it will be.
If duplicates do land in For review, exclude them there rather than deleting them after they are posted.

QuickBooks Desktop, and older files

QuickBooks Desktop reads QBO as well, and also takes QIF, which is the older format the desktop ledgers have always understood. If you are working in Desktop rather than Online, QIF is often the path of least resistance, and the same conversion produces it.

Doing this at volume

One statement is a two minute job. A year of statements for a dozen clients is a week, unless it is batched. Batch mode converts a stack of PDFs in a single pass and returns them as a ZIP, named by statement period rather than by whatever the client called the file, which is the difference between a morning and a fortnight during tax season. Accountants and bookkeepers working across many clients get the most out of the Pro plan here, since the daily page cap is what bites first.

The same statement also converts to OFX for Xero if some of your clients are on the other platform, so a mixed practice does not need two tools.