Why Does QuickBooks Only Import 90 Days of Transactions? The Bank Feed Limit, Explained

Short answer: QuickBooks cannot download bank transactions older than 90 days through a bank connection. Intuit states that transactions older than 90 days cannot be downloaded and have to be added manually from a file. A first connection typically pulls somewhere between 30 and 90 days depending on the institution, and no setting, reconnection, or support ticket extends it. Older history has to come in through a file upload: QBO, QFX, OFX, or CSV.

This one limit is behind a startling share of bookkeeping frustration. It is the reason a catch-up engagement stalls in week one, the reason a new QuickBooks file shows three months of a five-year-old business, and the reason people spend an afternoon disconnecting and reconnecting a bank feed that was never going to behave differently.

Why does QuickBooks only import 90 days of transactions?

Because the bank feed was designed to keep an already-reconciled ledger current, not to build one from scratch. Intuit's guidance is explicit: transactions older than 90 days cannot be downloaded through a bank connection and must be added to QuickBooks Online manually. The exact amount you get on a first connect depends on the bank and commonly lands between 30 and 90 days.

Notice who the limit belongs to. It is not your bank being stingy. Your bank may well keep seven years of statements online and let you download eighteen months of transaction data directly from its own website. QuickBooks still will not pull more than 90 days of it through the feed. The two ceilings are separate, they are set by different parties, and confusing them is what sends people down the wrong troubleshooting path.

What each connection type actually backfills

This is the table to keep. Every route into QuickBooks has a different reach, and choosing correctly takes about ten seconds once you can see them side by side.

Two things jump out of that table. The first is that every automated route shares the same 90-day ceiling, including the modern API integrations that feel like they should be smarter. The second is that only the file routes go further back, and only one of them works without a bank login, which is the entire reason outside bookkeepers live on converted statements.

Does reconnecting the bank feed bring in older transactions?

No, and it is the most common wasted hour in bookkeeping. Disconnecting an account and reconnecting it does not reach backward through your history. It opens a brand new 90-day window from the reconnection date. You end up with exactly the same range you had, and if the old transactions are still sitting in For review you can end up with duplicates as well.

The same goes for reauthorizing a connection, updating credentials, or asking QuickBooks support to extend the range. There is no hidden setting. The 90-day boundary is a property of the download path itself, and the only supported way around it is the one Intuit points to: add the older transactions from a file.

How do I import bank transactions older than 90 days into QuickBooks?

Through a file. QuickBooks Online accepts QBO, QFX, OFX, and CSV on the upload path, and QuickBooks Desktop Web Connect accepts .qbo. You have three practical sources for that file, in descending order of convenience.

Download it from the bank. If your bank offers a Web Connect or QuickBooks download and the period you need is inside its export window, this is the cleanest path. Many banks cap that window at 18 months, and some at 90 days, which is often how people discover they have a second ceiling to worry about.

Export a CSV and map it. Works for any period the bank lets you export. You will be matching columns to Date, Description, and Amount by hand, and QuickBooks Online caps each upload at 1,000 transactions and 350 KB.

Convert the statement PDF. This is the only route with no window and no login requirement. Statements typically stay available for around seven years, far longer than any download tool reaches, and a converted statement produces the same .QBO file a bank download would. If the statements are headed into QuickBooks specifically, a dedicated bank statement to QuickBooks converter handles the PDF to QBO step across every institution you deal with. Then import it under Transactions, Bank transactions, Upload from file.

Why does my bank show 18 months but QuickBooks only 90 days?

Because those are two different limits, set by two different companies, and they have nothing to do with each other.

Your bank decides how much transaction history it exposes on its own website. U.S. Bank publishes 18 months of transaction history online and six months on mobile. Wells Fargo's activity screen shows roughly 60 to 90 days. Meanwhile most large US banks keep about seven years of statement PDFs available. Intuit separately decides how much QuickBooks will download through a feed, and that answer is 90 days regardless of what your bank offers.

So when your bank happily shows you 18 months and QuickBooks stubbornly imports three, nothing is broken. You are simply looking at the smaller of two independent numbers. The bank-side figures, institution by institution, are collected in how far back you can download bank transactions.

Does the 90-day limit apply to fintech accounts too?

Yes, and this surprises people who assume a modern API integration must be better than an old bank feed. It is not, because the constraint lives on the QuickBooks side.

Brex documents it in its own support material: transactions older than 90 days will not sync. Mercury's QuickBooks integration syncs forward from the start date you choose during setup and does not rebuild what came before it. Both are good integrations. Both stop at the same wall, for the same reason. Converting the statements is how you get behind it, whether the account is at a Brex or Mercury style fintech or a traditional bank.

When the 90-day limit actually bites

Four situations, and if you are reading this you are almost certainly in one of them.

Catch-up bookkeeping. A business runs for a year or three without books, then needs them. The feed hands over one quarter. Everything else is in the statement archive, and the rebuild runs month by month from PDFs. The full sequence is in catch-up bookkeeping in QuickBooks.

A new accountant or a new QuickBooks file. The company is not new, the file is. QuickBooks still only pulls 90 days into it, so the prior-year comparatives have to be imported.

A closed account. There is no connection left to make. Saved or requested statements are the only record, and they convert like any other.

A migration or a dropped feed. A bank moves customers to a new platform, or a connection breaks for six weeks before anyone notices. The reconnected feed starts fresh and never backfills the gap.

Related reading

If your feed is not just short but broken, see what to do when the QuickBooks bank feed stops working and why bank transactions go missing in QuickBooks Online. Before you upload a heavy year, check how many transactions QuickBooks accepts at once. And to turn any statement PDF into the file QuickBooks will actually take, use the bank statement to QBO converter.