Every bookkeeper hits the same wall at month-end: a client banks somewhere QuickBooks can't connect, the bank feed only goes back 90 days, or a credit-card account simply never imports. The transactions exist. You just can't get them into the books without logging in and downloading the statement yourself.
This isn't your setup being wrong. It's a structural coverage gap in how bank data reaches accounting software — and it's getting wider, not narrower. Here's exactly where the gap is, and the options for getting the statement anyway.
QuickBooks Online's bank feed connects roughly 3,000 US institutions, through aggregators like Plaid and Finicity. That sounds like a lot until you serve real small businesses:
And the path that used to cover the long tail — screen-scraping aggregators — is being shut down. Hubdoc retired its standard bank-statement auto-fetch in 2022, stating those connections "are often blocked by banks." Major banks have moved aggregators to OAuth-only API access and hardened against scripted logins. Every bank that tightens auth without shipping a consumer API pushes more accounts back into "manual download only."
Plaid's Statements product — the thing most cloud tools rely on — covers about 40% of US depository accounts, and only depository accounts. Plaid's own documentation recommends pairing it with a fallback for everything else. That fallback is the manual portal download. The entire aggregator stack has a hole, and the vendors know it.
| Option | What it costs you |
|---|---|
| Ask the client every month | The "document logistics" tax — chasing, reminders, half-sent folders, blown deadlines |
| Log into each portal yourself | Real time: 20 clients across 30 institutions is 30 logins a close |
| Automate the login-and-download locally | One-time setup; then it runs on your machine each month |
The first two are what most firms do. The third is the one worth understanding, because there's a right way and a wrong way to do it.
Tools that promise to auto-fetch statements generally do it by storing your client's bank password on their servers and logging in from their cloud. For bank portals that's two problems at once: it's exactly the datacenter-IP, clean-browser pattern banks now device-block, and it often violates the bank's terms. It's also why these tools inherit the same coverage holes — they're aggregator-bound.
The durable approach is the opposite: run the automation locally, in your own browser, on your own machine, riding the login session you already have. To the bank it looks like you — the returning human — because it is. The credential never leaves your computer. And because the run is a fixed, recorded program (no AI improvising clicks on a live bank account), it does the same thing every month and you have a clean log of exactly what it did.
The right mental model: don't try to make an unsupported bank "supported." Just automate the manual fallback the aggregators already told you to keep — and keep it on your machine.
Local automation isn't magic. Two things to know up front:
If a human can log in and download the statement, that download can be automated on your own machine — no API, no aggregator, no password in anyone's cloud. For the small banks, credit unions, and card accounts QuickBooks and Plaid will never cover, that's the only approach that actually reaches them and keeps the credentials where they belong.
We run done-for-you bank-statement retrieval for bookkeepers — on your machine, your logins, nothing in any cloud, no AI. First client free.
Why doesn't QuickBooks fetch my client's bank statements?
QBO's bank feed connects ~3,000 US institutions via Plaid/Finicity; small banks, credit unions, and many business/card accounts without an API aren't covered, so QuickBooks routes you to manual upload. The feed also only backfills ~90 days.
My bank isn't on Plaid — how do I get statements automatically?
Plaid Statements covers ~40% of US depository accounts (depository only) and Plaid recommends a fallback. The fallback is retrieving the PDF from the bank portal — by hand, or automated locally so the login stays on your machine.
How do I get more than 90 days of statements into QuickBooks?
The ~90-day feed window can't backfill older history, so prior-year cleanup needs the statement PDFs from the portal. A recorded local automation pulls each month's PDF so you don't key them by hand.
Is there a tool that pulls statements from a bank with no QuickBooks connection?
Cloud fetchers (Hubdoc, LedgerDocs) are aggregator-bound and inherit the same holes. For an unsupported bank, a local deterministic automation logs into the portal in your own browser and downloads the actual PDF — no API, no credentials in a cloud.