Import Older Bank Transactions into QuickBooks Online

Quick Answer: QuickBooks Online's bank connection only pulls roughly the last 90 days, so anything older has to be uploaded by hand. Get the missing months from your bank as a CSV or .QBO file (or convert the PDF statements into one), then use Link account > Upload from file on the Bank transactions page. Start the file the day after the last transaction already in QuickBooks so nothing doubles up.

Older bank transactions get into QuickBooks Online through a manual file upload, not the bank connection. Intuit states that transactions older than 90 days can't be downloaded and must be added manually. You export or rebuild the missing period as a .QBO, QFX or CSV file, upload it into the same bank account, then review and categorize those rows like any other downloaded transaction.

Why does QuickBooks stop at 90 days?

When you connect a checking or card account, QuickBooks asks the bank for recent posted activity. Intuit's help page on bank errors says it plainly: "Transactions older than 90 days can't be downloaded. You'll need to add them to QuickBooks Online manually." The limit comes from the connection, not from your subscription, so upgrading does not lift it.

That leaves a gap in three common situations:

• You started your books mid-year. You connected the account in September, the feed reached back to June, and January through May is empty.
• You are catching up a client. A bookkeeper takes over a file that has been untouched for a year. The feed fills the latest quarter only.
• The connection broke for a while. A password change or bank outage stopped downloads, and by the time you reconnected, the oldest missed days had aged past the window.

In each case the fix is the same: supply the missing period as a file.

What file can you upload for older transactions?

QuickBooks Online accepts two kinds of upload, according to Intuit's manual upload article:

Intuit lists QBO first among the transaction-list formats. It carries dates, amounts, payee names and the bank's own transaction IDs, so there is no column mapping step and less room for sign errors. CSV works too, but it needs either three columns (Date, Description, Amount) or four (Date, Description, Credit, Debit), and you map them during the upload.

Where to get the file

1. Your bank's activity export. Many banks let you choose a date range and download CSV or "QuickBooks Web Connect" (.QBO). Check how far back the export goes; some stop at 12 or 18 months even though statements go back years.
2. Your PDF statements. Banks keep monthly statements much longer than they keep downloadable activity. If the export cannot reach the months you need, the statements are your source.
3. A converted statement. Turning a PDF statement into a .QBO or CSV is the usual route for anything the export cannot reach. QuickBankConvert reads statement PDFs and writes QBO on paid plans, while CSV and Excel are on the free account.

How do you upload old transactions step by step?

These steps follow Intuit's current menu names for a CSV, QBO or QFX list:

1. Go to All apps > Accounting > Bank transactions.
2. Select the Link account dropdown, then Upload from file.
3. Choose Drag and drop or select files and pick your file.
4. In the QuickBooks account dropdown, select the bank or card account the history belongs to. Pick the existing connected account, not a new one, or you will end up with two registers for one bank account.
5. Select Continue. For a CSV, match each column to the QuickBooks field and confirm the date format.
6. Select Continue again, tick the transactions to import, then Continue, Yes and Done.

The rows land in the For review tab. Nothing hits your books until you categorize, match or add each one.

If your history spans more than 1,000 transactions or the file passes 350 KB, split it. One file per statement month is easy to track and easy to redo if a single month goes wrong.

How do you avoid duplicates with what the feed already pulled?

Duplicates are the main way a history import goes wrong. Intuit's date-range rules give the logic:

• Brand-new account in QuickBooks: go back as far as you need.
• Existing account with no transactions yet: start from the opening balance date.
• Existing account that already has transactions: start the file the day after the last transaction already there.

In practice, open the account register (or the Categorized tab) and find the earliest date the feed delivered. Your upload should end the day before that. If the feed's first day was 14 June, your file covers 1 January to 13 June.

A few habits stop the overlap that still slips through:

• Trim the boundary day by hand. Banks and QuickBooks can disagree about which day a late-evening transaction belongs to. Look at the two days either side of your cut-off before uploading.
• Upload once per period. If an upload fails halfway, check For review before trying again; part of it may already be there.
• Use the Excluded tab for strays. If a transaction appears twice, exclude the copy rather than deleting a categorized entry.

What about the opening balance?

Uploading history changes what your register should show. If you set up the account with an opening balance on 1 June and then import January to May, the balance now counts those months twice: once in the opening entry and once in the transactions.

The tidy fix is to move the opening balance back. Make the opening balance the ending balance of the statement before your first imported month (for a January start, the 31 December balance), dated that day. After the upload, the register's balance on any statement date should equal the statement. If it doesn't, compare month by month until you find the one that is off.

Reconciling each imported month against its statement is the real proof the history is complete. The QuickBooks Online reconciliation guide walks through that screen; old months reconcile the same way as new ones.

When is the PDF statement the only source?

Banks usually limit downloadable activity far more than statement history. If you need two or three years back for a tax catch-up, a loan file or a client clean-up, the PDFs are often all there is.

You have three options for those months:

1. Upload the PDF to QuickBooks itself. The account statement upload uses AI to read the document and shows a side-by-side comparison you edit before saving. It suits a few statements; check every row against the PDF.
2. Retype it. Fine for a quiet account with ten transactions a month, painful for a busy one.
3. Convert the PDF into a transaction file first. You get a CSV or QBO you can inspect in a spreadsheet before it goes near QuickBooks, which makes boundary trimming and duplicate checks easier. For a stack of statements, check the page and monthly limits on pricing before you start; a one-time 7-day pass exists for one-off catch-ups.

Whichever you pick, scanned or photographed statements are read less accurately than bank-generated PDFs, so budget review time.

How do you check the file before uploading it?

A five-minute look at the file saves a messy clean-up in For review:

• Dates run continuously from your start to your cut-off with no missing month.
• Signs are right: payments out negative, deposits positive. In a four-column CSV, debits and credits are in their own columns with blank cells instead of zeros.
• Descriptions do not start with long reference numbers; Intuit suggests removing numbers from the description column.
• Row count per month roughly matches the statement.
• Totals for each month equal the statement's deposits and withdrawals.

For QBO files, the free QBO file checker shows whether the file is well formed and what account details it carries before QuickBooks sees it.

Related guides

• Import bank transactions into QuickBooks Online for the regular monthly upload.
• Import bank statements into QuickBooks for statement-based workflows across QuickBooks versions.
• QuickBooks not downloading bank transactions if recent activity is missing as well as old.
• QuickBooks integration overview for how converted files fit into QuickBooks.