Bank Feeds vs Manual Import in QuickBooks: Which to Use

Neither one wins outright. A bank feed is best for a live account you own and reconcile every month, because it pulls new activity automatically. Manual file import is more accurate for older history, catch-up work, and any account where the feed drops, duplicates, or won't connect. Most bookkeepers run both, and lean on import whenever the feed leaves a gap.

Last updated July 2026.

What a bank feed is and how it connects

A bank feed is a standing connection between QuickBooks and the account, so new transactions flow into the Banking (or Transactions) tab without anyone downloading a file. It sounds simple, but there are four different plumbing methods behind that one word, and they fail in different ways.

• Direct Connect. You enroll the account for online services with the bank itself, and QuickBooks talks to the bank directly. The bank sets the terms, and some charge for it while others don't, so confirm with them before you assume anything. It's the most stable of the four when a bank supports it.
• Web Connect. Not a live feed in the automatic sense. You log into online banking, download a .qbo (Web Connect) file yourself, and import it. This is really manual import wearing a feed's clothing, and it's the fallback when a live connection isn't available.
• Express Web Connect and Express Web Connect+. An aggregator sits between QuickBooks and the bank, either screen-scraping the login or holding an OAuth token. Convenient when it works, fragile when the bank changes its login flow. This is the layer that throws connection errors like 102, 103, 105 and 350 when the connector breaks or needs re-authorization.

The takeaway: "the feed" is not one thing. Two clients at two banks can have wildly different reliability depending on which method their bank uses. For the deeper split, see Direct Connect vs Web Connect in QuickBooks.

What manual file import is

Manual import means you bring the transactions in as a file instead of relying on a connection. In QuickBooks Online you go to Banking, then Upload from file, and hand it a QBO, QFX or CSV. Intuit recommends QBO. The file has to be 350 KB or less and can hold up to 1,000 lines, one transaction per line, so a busy account gets split by statement period rather than dumped in as one annual file.

QuickBooks Desktop is stricter: its Web Connect import reads only .qbo. And no version of QuickBooks reads a PDF statement, so if all you have is a PDF, something has to convert it first. That's the gap a converter fills, and we'll come back to it. For the mechanics of a clean upload, see importing a bank statement into QuickBooks Online.

Bank feed vs manual import, compared

Here is how the two approaches actually stack up on the things a bookkeeper cares about: setup effort, how much history you get, how they break, and what each is genuinely best for.

Read the table and the pattern is clear. Feeds win on ongoing convenience. Import wins on control and coverage. The accuracy question isn't feed versus import in the abstract, it's which one you can actually verify against a source document, and import gives you that anchor every time.

Which is more accurate and reliable

People assume a live feed is the accurate one because it's automatic. Automatic is not the same as correct. A feed can silently drop a few days of activity during an outage, or double-post a batch after a re-connect, and nothing flags it. You find out at reconciliation, when the balance is off and you're hunting for the cause. See fixing duplicate bank transactions for how that plays out.

A converted statement is accurate in a way you can prove. Every transaction on it also appears on a document the bank issued, and it ends at a printed closing balance. Import the month, pull the register balance as of the statement end date, and confirm it matches. If it ties, the data is complete. That closing-balance handshake is the single most useful accuracy control in bookkeeping, and feeds don't give it to you.

When bookkeepers should prefer each

Reach for the bank feed when the account is live, you (or the client) own the login, the bank connects cleanly, and you only need activity from the point of connection forward. For a well-behaved operating account that reconciles every month, a feed saves real time and there's no reason to fight it.

Reach for manual import when any of these are true:

• You need history older than the feed pulled on first connect.
• A catch-up client arrives with months or years of PDFs and no connection in place.
• The feed keeps erroring out, and you're spending more time re-authorizing it than the data is worth. If that's you, the common bank feed error codes explain what each one means.
• You don't want the client sharing banking credentials with an aggregator, which is a reasonable position to hold.
• You need one clean, verifiable set of transactions per statement period rather than a rolling stream.

Plenty of engagements use both on the same client: a feed for current months, import to backfill the history the feed never had. That's not a compromise, it's just using each tool where it's strong. When you're onboarding a batch of clients at once, converting statements in bulk keeps the setup phase from stalling.

How converting PDF statements to .qbo fills the gaps

The most common gap is the same one every time: the client has PDF statements, and QuickBooks won't read a PDF. Converting each statement to a .qbo Web Connect file closes that gap and gives you the best of the import approach without the CSV headaches.

A .qbo file is the same container QuickBooks uses for feed data, so it carries the financial institution and account identifiers plus standard fields (date, amount, description, transaction type, reference). Practically, that means:

• No column-mapping dialog, because the file already declares its structure. CSVs make you map columns on every client, every file.
• Transactions land in For Review, so your bank rules and matching behave exactly as they would with feed data.
• Debits and credits carry their own sign, so you don't post a month of income as expenses because a bank exported everything as positive numbers.
• Each file ties to the statement's closing balance, giving you the verification a feed can't.

So the practical division of labor looks like this: let the feed handle the live months where it's reliable, and convert statements for everything the feed can't reach or can't be trusted on. Once the books are reconciled against every statement, you can turn the cleaned books into board-ready financial statements with confidence that the underlying data actually ties out. To see what the format holds, try the QBO converter.

Frequently asked questions

Is a bank feed or manual import more accurate in QuickBooks?

Manual import is easier to verify. A converted statement ties to the bank's printed closing balance, so you can prove the month is complete. Feeds are convenient but can silently drop or duplicate transactions, and you often don't catch it until reconciliation. For accuracy you can confirm, import against a source document wins.

Why does my QuickBooks bank feed keep disconnecting?

Usually the connection type. Express Web Connect and Express Web Connect+ rely on an aggregator that screen-scrapes or holds a token, and those break when the bank changes its login flow, throwing errors like 102, 103, 105 or 350. Re-authorizing helps temporarily. If it's chronic, importing statement files sidesteps the connection entirely.

Can I upload a PDF bank statement into QuickBooks?

Not directly. QuickBooks Online's Upload from file accepts QBO, QFX and CSV only, and QuickBooks Desktop Web Connect reads only .qbo. A PDF has to be converted first. Converting to .qbo is the cleanest route because the file carries bank and account identity, so QuickBooks treats it like feed data with no column mapping.

How far back does a QuickBooks bank feed go?

It depends on the bank. On first connect QuickBooks pulls whatever the institution exposes, commonly around 90 days, though some banks provide more. You don't get to choose. For anything older, Intuit's own advice is to bring it in by manual upload, which is where converting older PDF statements becomes the practical path.

When should a bookkeeper use manual import instead of the feed?

Use manual import for old history the feed never pulled, catch-up clients with a folder of PDFs, accounts where the feed keeps erroring, and any client who shouldn't be sharing banking credentials with an aggregator. Many bookkeepers run both: a feed for current months and import to backfill everything before the connection existed.