Import Client Bank Statements Into QuickBooks Online

A firm cannot connect a client's bank feed on the client's behalf. Intuit is explicit that accountants can't connect a bank account for their clients, so the client has to do it from their own login. That leaves file import as the route you control, and QuickBooks Online's manual upload accepts QBO, QFX and CSV, capped at 350 KB and 1,000 lines per file. Converting each PDF statement to a .qbo Web Connect file gives you a bank-identified, month-sized import that lands like feed data and ties to the statement's closing balance.

Last updated July 2026.

Why bank feeds don't solve this for a firm

Bank feeds are built for the account owner, not the accountant. Three things break the moment you're running many client files.

• You can't set them up. Per Intuit's connection help, the client must enter their own online banking credentials. You can walk them through it on a call, but you can't do it for them, and plenty of clients won't hand logins to a third party (nor should they).
• History is short. On first connect, QuickBooks pulls what the bank exposes. That's commonly around the last 90 days, and while some banks hand over more (up to 24 months in some cases), you don't get to choose. For older history, Intuit's own advice is to upload it manually.
• Catch-up clients arrive after the fact. The client who shows up in July needing last year closed has no feed. They have a folder of PDFs. Connecting a feed today does nothing for January.

The practical question isn't "how do I connect the bank." It's "what's the fastest repeatable path from a PDF statement to reviewed transactions." More on the limits in how far back QuickBooks can import bank transactions.

"Can I connect my client's bank feed from QuickBooks Online Accountant?"

No. QuickBooks Online Accountant gives you access to the client's books, but the bank connection must be authorized from the client's side with their own banking credentials. Your options: coach the client through connecting it themselves, or bring the transactions in by file upload. Most firms do both.

The four routes to get client transactions into QuickBooks Online

How the realistic options compare when you're the one on the hook for the close.

The last row is what changes a firm's economics: the only route fully in your hands, working for any period, producing a file QuickBooks already understands.

"What formats does QuickBooks Online actually accept on upload?"

QuickBooks Online's manual upload takes QBO (Web Connect), QFX and CSV. Intuit recommends QBO. The file must be 350 KB or less and can hold up to 1,000 lines, one transaction per line. A busy operating account's full year blows through both limits, so you import by month or by statement, never as one annual dump.

Note what's missing from that list: PDF. QuickBooks won't read a statement PDF, so something has to convert it first, which is what a PDF to QBO converter does. If you're weighing a heavier document-capture platform for this, see whether accountants need enterprise OCR.

"Why does my client's CSV keep failing on the date column?"

Because bank exports aren't import files. QuickBooks needs a 3-column layout (Date, Description, Amount) or a 4-column layout (Date, Description, Credit, Debit), one consistent date format throughout, and clean numbers. Failure points Intuit calls out include mixed or unrecognized dates, the day of the week sitting inside the date cell, and currency formatting on amounts.

None of that is hard. It's hard every time, for every client, because every bank exports differently. Five minutes of Excel surgery times forty client files a month is a headcount problem. A Web Connect file carries the account identity and standard fields inside it, so there's no mapping screen.

"How many transactions can I upload at once?"

Up to 1,000 lines, in a file of 350 KB or less. The size cap usually bites first, on wide CSVs with long descriptions. For firms the clean answer is one file per statement period: it stays under both limits and gives you a checkpoint. See how many transactions QuickBooks imports at once.

Why .qbo beats CSV once you're doing this at volume

A .qbo file is Web Connect, the same container QuickBooks uses for feed data. It carries financial institution and account identifiers plus standard fields (date, amount, description, transaction type, reference), so QuickBooks knows what it's looking at. Practically:

• No column mapping dialog, on any client, ever.
• Transactions land in For Review, so your bank rules and matching behave normally.
• Debits and credits carry their own sign, so you don't get a month of income posted as expenses because a bank exported everything positive.

The tradeoff: you need something to produce the .qbo from the PDF. That's a QBO converter step of a couple of minutes per statement, against reformatting CSVs or keying lines by hand. Format detail: what a .qbo file actually contains.

The catch-up workflow: 12 months of PDFs, one client, no feed

This is the process we'd hand a new staff member. It's boring on purpose: the control that keeps reconciliation from exploding is doing the same check twelve times.

1. Collect every statement before you convert anything

Ask for all twelve PDFs per account up front, downloaded from online banking rather than scanned. Check the sequence: statement 3's opening balance should equal statement 2's closing balance. Find the gap now, not in month nine.

2. Set up the account in QuickBooks first

Create or confirm the bank or credit card account, and set the opening balance to the closing balance of the last reconciled period (or statement 1's opening balance if you're starting cold). Getting this wrong is the most common reason a catch-up ends with a discrepancy nobody can trace.

3. Convert one statement at a time, one file per month

Convert each PDF to its own .qbo and name the files so a human can sort them: ClientName_Checking_2025-01.qbo. One month per file keeps you inside the 1,000-line and 350 KB limits without thinking about it, and a bad month can be redone in isolation.

4. Import in date order, oldest first

Banking, then Upload from file, select the target account, January before February. Date order matters because the running balance stays meaningful, and because if you have to back out a month, it's the last one rather than one buried mid-year.

5. Tie every month to the statement's printed closing balance

This is the control. Once a month is accepted into the register, pull the account balance as of the statement end date and compare it to the closing balance printed on the statement. It matches or you stop. Don't import February until January ties. A doubled transaction caught in January costs two minutes. Caught in December, under eleven months of stacked activity, it costs an afternoon.

6. Categorize, then reconcile month by month

With the year in and every month tied, run categorization (bank rules earn their keep here) and reconcile each month against its statement. Reconciliation is a formality now, because you already proved the balances. Full walkthrough: converting a year of statements for catch-up bookkeeping.

7. Handle the rest of the shoebox

Catch-up clients rarely stop at statements. The same client usually turns up with a folder of vendor bills that need to hit AP, and you can extract those to a spreadsheet rather than keying them line by line. Statements give you the money movement. The bills give you the detail behind it.

"What do I tell a client who won't share their bank login?"

Tell them they shouldn't, and that you don't need it. Ask for PDF statements from online banking, or a read-only accountant view if their bank offers one, and handle the rest on your side. It's a better answer than most firms give, and it takes a liability out of your engagement.

It also removes a dependency. Feeds break, banks switch aggregation partners, MFA prompts go unanswered for a week. When your process starts from statements the client already has, your close calendar doesn't hinge on a connection you don't own. More: importing bank transactions without connecting the bank.

What this saves per client file

Run the arithmetic on your own numbers. A year for one operating account is twelve documents. Keying them by hand costs hours and produces typos you'll find during reconciliation. Reformatting twelve bank CSVs costs tens of minutes plus a mapping pass. Converting twelve PDFs to .qbo and importing them in order costs minutes per statement with no mapping, and the closing-balance check at each step turns the final reconciliation into a confirmation, not an investigation. Multiply by the catch-up clients on your board this quarter. For the cost side, see what statement conversion costs; for upload mechanics, importing a bank statement into QuickBooks Online.

Frequently asked questions

Can an accountant connect a client's bank feed in QuickBooks Online Accountant?

No. Intuit's connection guidance states that accountants can't connect a bank account for their clients, and the client must do it themselves from their own login with their own banking credentials. Your firm's route is file import: upload QBO, QFX or CSV files into the client's Banking tab.

How far back does a QuickBooks bank feed pull transactions?

It depends on the bank. On first connection QuickBooks pulls what the institution exposes, commonly around the last 90 days, though some banks provide more. Anything older has to be brought in by manual upload, which is Intuit's own recommendation for older history.

Can I upload a PDF bank statement to QuickBooks Online?

Not directly. The manual upload accepts QBO, QFX and CSV only, so a PDF has to be converted first. Converting to .qbo (Web Connect) is the cleanest option for a firm because the file carries bank and account identity, so QuickBooks treats it like feed data with no column mapping.

What are the file limits on QuickBooks Online bank imports?

Each upload must be 350 KB or less and can contain up to 1,000 lines, with one transaction per line. That's why a year of a busy account gets split by statement period. One file per month keeps you inside both limits and gives you a checkpoint against each statement's closing balance.