How do I import a bank statement into QuickBooks?

Convert the statement to a QBO file or CSV, then in QuickBooks Online go to Transactions, Bank transactions, Upload from file, select the account, and upload. A QBO file maps automatically; a CSV requires you to match the date, description, and amount columns before reviewing and categorizing.

What is the difference between a QBO file and a CSV in QuickBooks?

A QBO (Web Connect) file is QuickBooks's native import format and maps every field automatically, reducing errors. A CSV is a plain spreadsheet you must map column by column, which is more flexible but more prone to mismatched or misdated transactions.

Why can't QuickBooks pull older bank transactions?

The automatic bank feed in QuickBooks Online generally reaches back only about 90 days. To bring in transactions older than that, such as a prior fiscal year, you import them from a QBO or CSV file instead of relying on the feed.

How do you reconcile a bank statement in QuickBooks?

After importing and categorizing transactions, open Reconcile, select the account, and enter the statement's ending balance and date. Tick each transaction that appears on the statement until the difference reaches zero, which confirms the QuickBooks balance matches the bank.

Can I upload a bank statement to QuickBooks Desktop?

Yes. For a QBO file use File, Utilities, Import, Web Connect Files, which maps automatically. CSV import in Desktop uses the bank-statement import tooling and is stricter about column layout, so a QBO file is usually the easier route.

Why did my CSV import into QuickBooks fail?

The most common cause is a date format QuickBooks does not recognize, followed by extra header rows or columns mapped to the wrong fields. Converting to a QBO file avoids these issues because the format encodes dates and amounts unambiguously.

How to Import Bank Statements Into QuickBooks

You can import bank statements into QuickBooks in two ways: upload a QBO file (also called Web Connect), which QuickBooks reads automatically because the format already labels each field, or upload a CSV, where you match the columns to QuickBooks fields by hand. Both work in QuickBooks Online and QuickBooks Desktop. The reason this comes up so often is the bank feed: QuickBooks Online's automatic feed typically pulls only about the last 90 days of transactions, so anything older has to be imported from a file.

Two import formats: QBO (Web Connect) maps fields automatically; CSV requires you to match columns manually.
The 90-day limit: the automatic bank feed in QuickBooks Online generally reaches back about 90 days, so older transactions need a file upload.
Online and Desktop both accept uploads, but the menus and the CSV column rules differ between them.
Importing is not reconciling. After transactions land, you still categorize them and run a separate reconciliation against the statement balance.
QBO beats CSV for accuracy because the file format prevents column-mapping mistakes that cause duplicate or misdated entries.

QBO file versus CSV upload

The choice comes down to how much manual mapping you want to do and how clean you need the result. A QBO file is the native QuickBooks import format and maps date, description, and amount automatically, so there is nothing to match and far less to go wrong. A CSV is more flexible and works when you only have a spreadsheet, but you map every column yourself, which is where errors creep in.

Factor	QBO (Web Connect)	CSV upload
Column mapping	Automatic, fields are pre-labeled	Manual, you match each column
Error risk	Low, format is structured	Higher, mismatched columns cause bad entries
Date format issues	Handled by the format	Common source of failed imports
Works in Desktop	Yes, via Web Connect import	Yes, with the three-column or four-column layout
Best when	You want a clean, fast, accurate import	You only have a spreadsheet of transactions

If you are starting from a PDF, you can convert the statement to a QBO file for the automatic route, or to QBO from PDF directly, and skip the manual column matching entirely.

Importing into QuickBooks Online

In QuickBooks Online, file uploads live under the banking area. Go to Transactions, then Bank transactions, and choose Upload from file. You select the QuickBooks account the statement belongs to, attach your QBO or CSV file, and confirm. A QBO file imports straight through; a CSV stops at a mapping screen where you tell QuickBooks which column is the date, which is the description, and which is the amount.

Open Transactions, then Bank transactions.
Click Upload from file (or the dropdown next to Link account).
Browse to your QBO or CSV file and select it.
Choose the QuickBooks bank account the transactions belong to.
For a CSV, map the date, description, and amount columns; for a QBO file, this is automatic.
Review the transactions in the For Review tab, then accept, categorize, or match them.

QuickBooks Online accepts a single-amount CSV or a separate debit-and-credit CSV, but the date format and a single header row both have to be correct or the upload is rejected.

Importing into QuickBooks Desktop

QuickBooks Desktop handles the same two formats but through different menus. For a QBO file you use File, then Utilities, then Import, then Web Connect Files. For a CSV you typically need the bank-statement import tooling, because Desktop is stricter about the exact column layout than Online is. The practical advantage in Desktop is the same as Online: a QBO file removes the mapping step.

File type	Desktop path	Notes
QBO (Web Connect)	File, Utilities, Import, Web Connect Files	Maps automatically; the cleanest Desktop route
CSV	Bank-statement import tooling	Strict column layout; more setup than a QBO file

Because Desktop is less forgiving with CSV layouts, converting straight to a QBO file is usually the lower-effort path. Our PDF to QBO converter produces a Web Connect file you can import through the Utilities menu.

The bank-feed history limit and why you import files

QuickBooks Online's automatic bank feed pulls only recent transactions, generally about the last 90 days, so when you connect an account you do not get its full history. That gap is the single most common reason people import statements from a file: to bring in transactions older than the feed reaches, such as the start of a fiscal year you are only now catching up on.

Situation	Best method	Why
Recent transactions, last few weeks	Connected bank feed	Pulls automatically within the lookback window
Transactions older than about 90 days	QBO or CSV file upload	The feed cannot reach back that far
Catching up a full prior year	QBO file per statement	Clean mapping across many months, fewer errors
Bank not supported by feeds	QBO or CSV file upload	File import works regardless of feed support

This is why many bookkeepers convert each monthly PDF to a QBO file when onboarding a client: it backfills history the feed will never provide.

What trips up QuickBooks imports

Date format is the top failure. A CSV with mixed or non-standard dates is the most frequent reason an upload is rejected or imports transactions on the wrong day. A QBO file sidesteps this because the format encodes the date unambiguously.
Duplicates from overlap. If you import a file covering dates the bank feed already pulled, QuickBooks can create duplicate transactions you then have to exclude. Import only the gap the feed did not cover.
Importing is not reconciling. Bringing transactions in does not match them to your books. Reconciliation is a separate step that confirms the QuickBooks balance equals the statement's closing balance.

After import: categorize and reconcile

Importing transactions only puts them in QuickBooks; it does not finish the job. Once they land in the For Review area, you assign each to a category or match it to an existing entry, then run a reconciliation so the QuickBooks balance ties to the statement's closing balance. Reconciliation in QuickBooks works the same way it does anywhere: you confirm the recorded balance equals the bank's, accounting for anything outstanding.

Open the For Review tab and assign a category or payee to each transaction.
Accept matches QuickBooks suggests for transactions already in your books.
Go to Reconcile, select the account, and enter the statement's ending balance and date.
Tick each transaction that appears on the statement until the difference reaches zero.

For the underlying logic of that final step, see our guide on how to reconcile a bank statement.

One workflow detail saves a lot of cleanup: when you are backfilling history with file uploads and also have a live feed connected, import files only up to the day before the feed's window begins. If a file and the feed both cover the same dates, QuickBooks shows the overlap as potential duplicates in the For Review tab, and you have to exclude each one by hand before reconciling. Matching the file's end date to the feed's start date avoids that entirely. The same care applies when you import several monthly QBO files in sequence: import them oldest first and confirm each month reconciles before loading the next, so an error in an early month does not silently carry forward into every period after it.

Why a QBO file imports more cleanly than a CSV across bank layouts

From converting statements across hundreds of bank templates into QuickBooks-ready files, the difference in import success between QBO and CSV traces to two layout problems CSV inherits from the source statement. First, banks split debits and credits inconsistently: some use one signed amount column, others use two separate columns, and a CSV forces the importer to guess which the file uses, which is where amounts land with the wrong sign. A QBO file resolves the direction in the format itself, so a debit is unambiguously a debit. Second, descriptions wrap differently across layouts, and a CSV exported from a messy PDF can break one transaction across two rows, doubling the count. The QBO format binds each transaction's fields together as one record, so a wrapped description cannot split into a phantom second line. In practice this is why the same statement imports clean as a QBO file but needs cleanup as a CSV.

From PDF statement to a QuickBooks-ready file

The friction is almost always the starting format: a locked PDF that QuickBooks cannot read. Converting it to a QBO file gives you the automatic-mapping import that avoids column errors, while a CSV route works when you only need a spreadsheet. Either way, getting the statement out of PDF is the step that makes the import, categorization, and reconciliation that follow straightforward.