If you’ve ever connected a new account and watched only three months of activity appear, you’ve hit the bank feed 90 day limit. Most banks only hand QuickBooks Online or Xero 90 days of history through the feed — sometimes less. That’s fine for ongoing work, but it’s a wall for catch-up and cleanup jobs, where you need historical transactions going back six, nine, or twelve months. The fix is straightforward: stop fighting the feed and do a pdf statement backfill instead.
Why the 90-day wall exists
The bank feed 90 day limit isn’t a QuickBooks bug — it’s the bank. Aggregators and direct connections are designed to pull recent activity, and most institutions cap the initial pull at roughly 90 days. There’s no setting to flip and no support ticket that extends it. When you need to import older than 90 days, QuickBooks isn’t going to get it from the feed, so the data has to come from somewhere the bank does keep full history: the statements.
The fix: backfill from statements
Statements don’t have a 90-day cap. You can download a pdf, csv, or excel bank or credit-card statement for any month the account was open. So the fix is a clean backfill:
1. Find the gap. Note the oldest date your feed pulled, and the date you actually need to start from. 2. Download every statement in the gap. One pdf/csv/excel statement per month, no missing periods. 3. Categorize the transactions. Read each statement and assign accounts so the history comes in coded, not raw. 4. Import the backfill. Push the coded months in as a QuickBooks “batch transactions import file” or a Xero “precoded import file.” (Walkthrough here: Import Bank Statements into QuickBooks: 3 methods.) 5. Reconcile each backfilled month to its statement ending balance.
This gives you continuous history right up to where the live feed takes over — no gap, no duplicates if you mind the seam date.
Watch the seam
The one place a pdf statement backfill goes wrong is the overlap between your imported history and the live feed. Pick a clean cutoff: let the imported statements cover everything through a given date, and let the feed own everything after it. If the feed already pulled some of the period you’re backfilling, exclude those dates from your import so you don’t double-book the seam.
Make the backfill fast
Reading and coding nine months of historical transactions by hand is the part that turns a quick fix into a slog, so this is where I lean on Bookmonstic. It reads a pdf/csv/excel bank or credit-card statement, categorizes every transaction, and exports a QuickBooks “batch transactions import file” or a Xero “precoded import file” — no rules to build, no API, and crucially no bank feed, which is the entire reason you’re here. (Disclosure: I’m a CPA and Bookmonstic is my own tool.)
The benefit for this specific problem is reach: the feed stops at 90 days, but a statement-based backfill goes back as far as the account has statements, so you can rebuild a full year of historical transactions in one pass.
Frequently asked questions
Why does QuickBooks only show 90 days of bank feed history? The limit comes from the bank, not QuickBooks. Most institutions only expose about 90 days through the feed connection, and there’s no setting to extend it.
How do I import older than 90 days into QuickBooks? Download the older statements as pdf, csv, or excel, categorize the transactions, and bring them in as a batch transactions import file. Statements have no 90-day cap, so you can go back as far as they exist.
Will the backfill create duplicates with my live feed? Only if the date ranges overlap. Pick a clean cutoff date — statements cover everything through it, the feed covers everything after — and exclude any overlapping dates from your import.
Can I do a pdf statement backfill on a closed account? Yes. Since the backfill works straight from the statement, a closed or non-connected account is no problem at all — that’s exactly where it shines.
Written by the founder of Bookmonstic, a practicing CPA. Bookmonstic turns PDF/CSV/Excel bank statements into AI-categorized, import-ready files for QuickBooks and Xero — no rules to build, no API. Try it free →
Leave a Reply