QuickBooks Bank Feed Setup

The feed is genuinely useful for keeping current. Where people get caught out is the edges: older months it won't fetch, a bank that isn't on the list, or a connection that quietly stops sending data. This guide covers the setup, what the feed actually does, where it falls short, and how to fill those gaps without pretending a file upload is something it isn't.

How to set up a QuickBooks bank feed

The connection itself takes a couple of minutes. The order matters, so here's the sequence as it runs in QuickBooks Online:

1. From the left menu, open Transactions > Bank transactions (some accounts still label this Banking).
2. Select Link account — top right if you've connected accounts before, centre-screen on a fresh company file.
3. Search for your bank by name and pick the right entry. Larger banks list several variants (personal, business, a specific card product); choose the one that matches the account you actually hold.
4. Sign in with the credentials you use for that bank's website or app. QuickBooks routes this through its aggregator, so you may get a verification code from the bank.
5. Choose which accounts to bring in, and tell QuickBooks which one each maps to in your chart of accounts — checking, savings, or a credit card.
6. Confirm, and the feed starts pulling transactions into the For review tab.

After that, new transactions land automatically, usually within a day. You still review each one — categorise it, match it to an invoice or bill, and add it to your books. The feed delivers the data; it doesn't do the bookkeeping for you.

What a live bank feed actually does

A connected feed in QuickBooks does one job well: it keeps a linked account current. Each day it checks with the bank, pulls anything new, and drops those lines into For review so you can sort them. That's it — recent activity, on a rolling basis.

It's worth being precise about what that is and isn't. The feed reads transactions; it doesn't reconcile them for you, and it doesn't go back and fill in history. The bank decides how far back the first pull reaches, and in most cases that's around 90 days. Anything older than the feed's window simply never arrives. So the feed is a forward-looking tool — great for the months ahead, no help at all for the year behind you.

The limits people hit

This is the part the setup screens don't spell out. Three gaps come up again and again.

History stops at roughly 90 days. When you first link an account, QuickBooks fetches only what the bank hands over — typically the last 90 days or so. If you're starting QuickBooks mid-year, or catching up on a backlog, everything before that window is missing. The feed will not retrieve it later, no matter how long you wait.

Some banks and accounts aren't supported. Plenty of smaller banks, building societies, regional institutions and certain business or card products either don't appear in the list or won't hold a stable connection. If your bank isn't there, the feed isn't an option for that account, full stop.

Feeds drop and need reconnecting. Connections break. A password change, a new security step at the bank, an expired authorisation, or the bank updating its login flow can all stop the feed without much warning. When that happens, transactions quietly stop arriving until you go back into Bank transactions and reconnect the account — and you may find there's now a gap covering the days it was down.

Filling the gaps the feed can't reach

When the feed can't cover something — older months, an unsupported bank, or a stretch lost while a connection was down — QuickBooks has a separate path: Upload from file, under the same Transactions > Bank transactions screen, in the dropdown next to Link account. You give it a CSV (or Excel, QBO or OFX), map the Date, Description and Amount columns, and the transactions go into For review just like feed data.

Be clear about what this route is: a manual file import you run yourself. It is not a live feed, and nothing here pushes data into QuickBooks through a bank-feed API. It's the deliberate, one-off way to get history in when the automatic connection can't.

The catch is the file. Most of those gap-filling transactions live in PDF statements — last year's months, a closed account, a bank QuickBooks doesn't connect to. QuickBooks can't read a PDF as transactions, so the PDF has to become a clean CSV first. And a CSV is only safe to import if it's *complete*; a single dropped line and your QuickBooks balance won't tie out to the statement later.

That completeness check is where Export Bank Statement earns its place. It converts the PDF — including scanned or photographed statements, via OCR — into a CSV or Excel file, then runs a reconciliation check: it recomputes opening balance plus money in, minus money out, against the statement's printed closing balance, and flags any statement that doesn't reconcile. So a missing or misread transaction surfaces *before* it ever reaches QuickBooks, not three weeks later when reconciliation refuses to balance. It also writes the file in QuickBooks' native bank-import CSV format, so the columns arrive shaped the way the upload screen expects.

What it doesn't do — and won't claim to — is replace the bank feed. There's no live API sync here, and it isn't a bookkeeping service. You convert the statement, confirm it reconciles, and upload it yourself. Use the feed for the months ahead; use a converted, checked CSV for everything the feed leaves behind.

For the full upload walkthrough, see how to import PDF statements into QuickBooks. If an upload throws an error, how to fix QuickBooks import errors matches each message to its cause, and can QuickBooks import PDF bank statements? settles the PDF question first. There's a wider set of US accounting guides too.