How Many Transactions Can You Import into QuickBooks Online?

QuickBooks Online imports up to 1,000 transactions per file, and the upload file has to be 350 KB or smaller. That single-file cap is the same whether you upload a QBO (Web Connect) file, a QFX, an OFX, or a plain CSV. There is no limit on how many transactions you can hold in QuickBooks overall, only on how many arrive in one upload, so a year with thousands of lines just gets split into a few files by date range.

If you have hit a wall importing a big statement, this is almost always why. Below is the exact limit, the errors it throws, and the fastest way to get a full year of history in.

How many transactions can you import into QuickBooks Online at once?

You can import up to 1,000 lines per file, where each line is one transaction. The file also has to be 350 KB or less and in English. Both limits apply to every manual bank upload format QuickBooks Online accepts: QBO, QFX, OFX, and CSV. Hit either ceiling and the upload is rejected or truncated, so a heavy checking account often trips the 350 KB size cap before it even reaches 1,000 rows.

So the practical ceiling most people run into is 1,000 transactions and 350 KB per file. Everything else about the account, how many years of history it holds, how many accounts you track, is unaffected.

Why does QuickBooks reject my file?

Almost every failed bank import comes down to one of a short list of causes. The most common is size: the file is over 350 KB or over 1,000 lines. After that it is usually formatting, a header row that does not match, dates in a format QuickBooks cannot read, or amounts that carry dollar signs and commas. QuickBooks reads a rejected file as unusable rather than telling you which row is wrong, so trimming the file down is the first fix to try.

• Over the limit. More than 1,000 lines or larger than 350 KB. Split it.
• Wrong column count. A CSV needs exactly the 3-column or 4-column layout, with one clear header row.
• Unreadable dates. Mixed or ambiguous date formats. Pick one, such as MM/DD/YYYY, for the whole file.
• Formatted amounts. Dollar signs, thousands separators, or amounts stored as text instead of numbers.
• Blank or merged cells. Empty rows, merged header cells, and running-balance columns QuickBooks does not expect.

How do I import more than 1,000 transactions into QuickBooks Online?

Split the data into batches that each stay under 1,000 lines and 350 KB, then upload them one after another. The cleanest way to batch is by date range: import January through March in one file, April through June in the next, and so on. QuickBooks matches on the account, dates, and amounts, so uploading several files in sequence lands every transaction without creating duplicates, as long as the ranges do not overlap.

A quarter of activity is a safe batch size for most checking accounts. High-volume accounts, like a busy retail operation or a payment-heavy business account, may need to go month by month to stay under 350 KB. If you export from your bank as CSV, most spreadsheet tools let you filter by date and save each range as its own file before upload.

QBO file vs. CSV: which handles large imports better?

A QBO (Web Connect) file is the better default because QuickBooks treats it like a real bank download: the account, dates, and signed amounts are already mapped, and duplicate detection is built in. The 1,000-line cap still applies, but you avoid the column-mapping and formatting errors that sink CSV uploads. CSV is the right choice when you want to review or edit the rows in a spreadsheet first, or when you need to sidestep the QBO structure for an odd account. If a bank CSV is all you have and you just want it in Web Connect form, you can turn that CSV into a QuickBooks file directly. Either way, the batching rule is identical.

If your statements are PDFs, skip the manual CSV cleanup entirely. You can convert bank statements to a QBO file that imports like a bank feed, and split the output by date range if a period runs past 1,000 lines. For a specific bank, the PNC statement to QBO converter and the general bank statement to QBO converter produce the file in the exact shape QuickBooks expects. When you would rather keep raw rows, the same upload also exports a clean Excel or CSV file you can filter into batches.

Why does the bank feed only pull 90 days?

When you first connect a bank to QuickBooks Online, the feed downloads about 90 days of history and then keeps current from that point forward. It does not backfill years. That is a separate limit from the 1,000-line upload cap, and it is why prior-year cleanups and catch-up bookkeeping almost always run through manual file uploads rather than the live feed. For the older months, you download or request the statements, convert them, and upload the files in batches. Bookkeepers doing a full-year cleanup lean on this workflow constantly, since it is the only way to load history the feed will not reach.

Does the 350 KB limit or the 1,000-line limit hit first?

It depends on the account. A simple personal checking account with short descriptions can fit close to 1,000 lines under 350 KB. A business account with long payee names, memos, and reference numbers often crosses 350 KB at 600 to 800 lines. When in doubt, treat 350 KB as the real ceiling and batch by quarter or month so neither limit is a surprise mid-import.

Frequently asked questions

The short answers below match what QuickBooks support documents and the behavior finance teams see in practice. Batch by date range and both limits stop being a problem.

Is there a maximum number of transactions QuickBooks Online can hold?

No. There is no fixed cap on the total number of transactions in a QuickBooks Online company file. The 1,000-line and 350 KB limits apply only to a single import file, not to the account overall. You can load years of history by uploading many batches over time.

How many rows can a CSV bank import have?

Up to 1,000 rows per CSV, and the file must be 350 KB or less. The CSV also needs a 3-column layout (Date, Description, Amount) or a 4-column layout (Date, Description, Credit, Debit) with a single header row. Split anything larger into multiple CSVs by date range.

Do QBO and QFX files have the same 1,000-transaction limit as CSV?

Yes. The 1,000-line and 350 KB per-file limits apply to QBO, QFX, OFX, and CSV uploads alike. The advantage of a QBO or QFX file is the built-in account mapping and duplicate detection, not a higher ceiling.

Will splitting a file into batches create duplicate transactions?

Not if the date ranges do not overlap. QuickBooks matches on account, date, and amount, so sequential batches with clean date boundaries import once each. Overlapping ranges are the usual cause of duplicates, so cut each batch at a clear day boundary.