Why does QuickBooks Online only import 90 days of bank history?

The bank feed connection pulls what the bank's data provider exposes, which is typically about 90 days of history at first connection. Anything older has to come in by file upload — CSV, QBO, QFX or OFX — through Transactions → Bank transactions → Upload from file.

My bank's online export doesn't go back far enough. Now what?

Banks limit downloadable CSV/QBO exports to somewhere between 90 days and 24 months depending on the bank. Past that window, the only records are PDF statements (downloadable or archived). Convert those PDFs to a CSV or .qbo file and upload — that's the standard path for any catch-up or cleanup engagement.

Should I upload CSV or .qbo to QuickBooks Online?

Both work through the same upload screen. A .qbo (Web Connect) file carries structured dates and amounts so there's no column-mapping step and no date-format ambiguity; CSV lets you review and edit rows in a spreadsheet first. If your CSV imports with wrong dates, that's the date-format issue — see our 1/1/1970 guide.

Will importing old statements create duplicates?

QuickBooks flags rows that look identical to existing transactions during import, but overlapping date ranges are still the main duplicate source. Import statement-by-statement without overlapping periods, and use conversions with stable transaction IDs (.qbo/OFX with deterministic FITIDs) so re-importing the same file can't double up.

How far back can I import into QuickBooks Online?

There's no meaningful date floor on file uploads — years-old transactions import fine. The practical limits are file-based: keep CSVs under the row/size limits (split large files) and import in chronological batches so opening balances reconcile period by period.

Import bank statements older than 90 days into QuickBooks Online

Published August 26, 2026

The short answer: the bank feed won't go back further, but file upload will. Get the missing months as files — bank CSV/QBO export if the window allows, converted PDF statements where it doesn't — then upload via Transactions → Bank transactions → the account's dropdown → Upload from file. The rest of this guide is the detail that keeps that from going wrong.

Step 1 — Find out what the bank will still give you

Before converting anything, check the bank's own export. Online banking typically offers CSV, QBO or OFX downloads for the last 90 days to 24 months, depending on the bank. Native exports are already in import shape — use them for every month they cover.

Step 2 — Convert PDF statements for the months beyond the window

Past the export window, the record that exists is the PDF statement. Converting those is the core of every catch-up job, and the failure mode to avoid is a silent misread — a transposed digit that posts to the books unflagged. Whatever converts your PDFs (here's ours), require it to verify the output: opening balance plus every transaction must equal the printed closing balance, per statement. A conversion that doesn't reconcile should say so, loudly, before you import it — our method flags the exact row that breaks the chain.

Step 3 — Choose the file format

.qbo (Web Connect): structured fields, no column mapping, no date ambiguity, and — done right — stable transaction IDs that make accidental re-imports harmless. PDF to QBO converter.
CSV: editable before import, but subject to QuickBooks' CSV rules — column layouts, row limits, and the date-format trap that turns every date into 1/1/1970 when it goes wrong.

Step 4 — Import in order, reconcile as you go

Import chronologically, oldest statement first, one statement per upload.
Don't overlap date ranges between files — overlap is where duplicates come from.
After each month lands, check the account's ending balance in QuickBooks against the printed closing balance on that statement. Month-by-month verification turns one giant reconciliation problem into thirty small, findable ones.

Doing this for a client who is years behind? That's dozens of statements — batch conversion and a plan where re-runs and failed conversions cost nothing stop the cleanup's tooling bill from becoming its own line item. QuickBooks Desktop instead of Online? The flow differs enough that we wrote it separately: importing statements into QuickBooks Desktop.

Questions people ask

Why does QuickBooks Online only import 90 days of bank history?: The bank feed connection pulls what the bank's data provider exposes, which is typically about 90 days of history at first connection. Anything older has to come in by file upload — CSV, QBO, QFX or OFX — through Transactions → Bank transactions → Upload from file.
My bank's online export doesn't go back far enough. Now what?: Banks limit downloadable CSV/QBO exports to somewhere between 90 days and 24 months depending on the bank. Past that window, the only records are PDF statements (downloadable or archived). Convert those PDFs to a CSV or .qbo file and upload — that's the standard path for any catch-up or cleanup engagement.
Should I upload CSV or .qbo to QuickBooks Online?: Both work through the same upload screen. A .qbo (Web Connect) file carries structured dates and amounts so there's no column-mapping step and no date-format ambiguity; CSV lets you review and edit rows in a spreadsheet first. If your CSV imports with wrong dates, that's the date-format issue — see our 1/1/1970 guide.
Will importing old statements create duplicates?: QuickBooks flags rows that look identical to existing transactions during import, but overlapping date ranges are still the main duplicate source. Import statement-by-statement without overlapping periods, and use conversions with stable transaction IDs (.qbo/OFX with deterministic FITIDs) so re-importing the same file can't double up.
How far back can I import into QuickBooks Online?: There's no meaningful date floor on file uploads — years-old transactions import fine. The practical limits are file-based: keep CSVs under the row/size limits (split large files) and import in chronological batches so opening balances reconcile period by period.

This guide is about file conversion and bookkeeping tooling — it isn't tax, accounting, or legal advice. Verify converted data against the source statement before filing or posting it.