Import Older Transactions into QuickBooks Past the 90 Day Feed Limit
No account needed for your first conversions. We never store your bank login.
Short answer: Import older transactions into QuickBooks by uploading a file rather than relying on the bank feed. A connected feed pulls roughly the last 90 days and will not reach further back, but a file import has no date restriction at all. Download the older activity from your bank as a CSV, convert it to a QuickBooks Web Connect (.qbo) file, and import it. QuickBooks Online takes it under Bank transactions, Upload from file. QuickBooks Desktop takes it under File, Utilities, Import, Web Connect Files.
This is the single most common wall in catch up bookkeeping. You connect the bank in January to clean up last year's books, three months of transactions appear, and the other nine months are simply not there. Nothing is broken. The feed is doing what feeds do.
How far back does a QuickBooks bank feed go?
About 90 days for most banks. When you first connect an account, QuickBooks requests an initial batch of history from the bank, and the great majority of US banks cap that initial pull at 90 days. A handful allow more, up to about 24 months, but you do not get to choose and there is no setting to change it. After the initial pull the feed only brings in new activity going forward.
That is a bank side limit, not a QuickBooks side limit. Reconnecting the account, disconnecting and relinking, or contacting Intuit support will not extend it. The transactions were never sent.
Is there a date limit on importing a file into QuickBooks?
No. There is no time restriction on importing bank statement files, whether .qbo, .qfx, .ofx, or CSV. You can import a statement from any date, including several years back. This is the part most people miss, and it is what makes file imports the standard tool for cleanup, catch up work, and opening a new company file mid year. If your bank still lets you download the period, QuickBooks will still let you import it.
How do I import older transactions into QuickBooks Online?
Start at the bank rather than at QuickBooks. Sign in to online banking on a desktop browser, open the account, and export the date range you need. Most banks let you export a custom range going back a year or more, often well past what the feed pulled. Save it as a CSV.
Then convert the CSV to a .qbo using the converter at the top of this page, and in QuickBooks Online go to Transactions, Bank transactions, Link account, Upload from file. Choose the .qbo, select the account it belongs to, and confirm. The transactions land in the For review tab exactly as feed transactions do, dated correctly, ready to categorize.
You can upload a raw CSV instead, but QuickBooks will ask you to map the columns on every single upload, and if you are rebuilding a year across four accounts that is a dozen mapping screens and a dozen chances to get the date format wrong. A .qbo carries its own field structure, so there is no mapping step.
How do I import older transactions into QuickBooks Desktop?
Desktop has no native CSV transaction import, so a converted .qbo is not optional here. Open the company file, go to File, Utilities, Import, Web Connect Files, and select the .qbo. When Desktop asks, point it at the existing bank account rather than creating a new one. The transactions appear in the Bank Feeds Center for review. The full sequence is in importing a QBO file into QuickBooks.
Why does QuickBooks only show 90 days of transactions?
Because that is all the bank sent when the connection was established. QuickBooks displays what it received. The fix is not in QuickBooks at all. Go back to the bank, export the missing months as a CSV, convert them, and import them. Once imported, older transactions behave identically to feed transactions for categorization, reconciliation, and reporting.
Can I import transactions from a prior year?
Yes. Prior year imports are routine, and they are the reason cleanup engagements are possible at all. The only real constraints are on your side of the books: make sure the account's opening balance and reconciliation status match the period you are importing into, and be careful not to import across a closed period without checking with whoever closed it. QuickBooks itself will accept a transaction dated three years ago without complaint.
How many transactions can I import at once?
QuickBooks Online caps a single upload at 1,000 lines and 350 KB, with one transaction per line. A busy checking account crosses that in a quarter, which is why annual cleanups fail as one giant file. Split the year into ranges the bank is willing to export, usually 90 days or a month at a time, and convert and import each one. A .qbo file has no equivalent size cap of its own, but the QuickBooks upload limit still applies to what you hand it.
If you are working through several accounts and many date ranges at once, the bulk CSV to QBO converter converts them in one pass instead of one at a time, and importing multiple CSV files into QuickBooks covers the order to import them in.
Will importing older transactions create duplicates?
It will if the imported range overlaps what the feed already pulled. QuickBooks matches on date, amount, and description, and a description that differs by even a few characters will not match, so the transaction lands twice. The safest approach is to import strictly up to the day before the feed's earliest transaction, then check the register at the seam.
Intuit's own guidance is to use one method per account rather than both. If duplicates do appear in the For review tab, exclude them rather than accepting them, because excluding leaves the register clean while accepting creates a real transaction you then have to delete.
Do imported categories carry over?
No. Categories are assigned inside QuickBooks, not carried in the file. If you reimport a range you previously categorized, the transactions come back uncategorized and you will need to recategorize them. That is one more reason to get the date ranges right the first time rather than importing a wide range and cleaning up afterward. Bank rules help: set them up before you import a large backlog and most of the categorization happens automatically as transactions arrive.
What if my bank only goes back 18 months?
Then you have hit the real limit, and it is the bank's export window rather than QuickBooks. Most US banks keep somewhere between 18 months and two years of transaction detail available for download, while statements go back much further, often seven years. When the transaction export runs out, the statements are what remain, and those arrive as PDFs. You can turn a PDF statement into a QuickBooks file directly, which covers the years the CSV export no longer reaches.
Does the date format matter on older imports?
Very much. This is where prior year imports quietly go wrong. A file exported with day first dates will import with the day and month swapped for any transaction before the thirteenth of the month, and the ones after the thirteenth will error out. Because you are importing months you no longer remember transaction by transaction, nobody catches it until reconciliation. Converting to .qbo normalizes the dates before QuickBooks ever sees them, and the QuickBooks CSV import date format guide covers what to check if you upload a CSV directly.
What is the fastest way to catch up a full year of books?
Work account by account, not month by month across accounts. For each account: export the full year from the bank in whatever ranges it allows, convert every CSV to a .qbo, import them oldest first, then reconcile against the year end statement before moving to the next account. Reconciling as you go catches a bad import while you still remember which file it came from.
Set your bank rules before the first import so categorization keeps pace, and leave the account disconnected from the live feed until the backlog is in. Reconnect afterward, and the feed will pick up from the current date without touching the history you just built.
Importing older transactions: the short version
The 90 day wall belongs to the bank feed, not to QuickBooks. File imports ignore dates entirely. Download the older ranges as CSV, convert each to a .qbo, import them oldest first with the feed disconnected, and reconcile as you go. Nothing about a transaction from 2023 makes QuickBooks treat it differently once it is in the register.
For the mechanics, see how to convert CSV to QBO, the platform specific paths on CSV to QuickBooks Online and CSV to QuickBooks Desktop, the layout rules in the QuickBooks CSV import template, what to do when a feed fails outright in QuickBooks bank feed not working, and how to hand the finished file over in sending a QBO file to your accountant. If you are choosing a tool, the best CSV to QBO converter roundup compares the real options.