Bank Statement Import Limits by Accounting Software (QuickBooks, Xero, Wave, Sage, FreshBooks, NetSuite)

Short answer: QuickBooks Online accepts up to 1,000 transactions and 350 KB per uploaded file. Xero accepts 1,000 statement lines per CSV bank statement import. FreshBooks caps a bank reconciliation CSV at 500 transactions. Wave's CSV upload starts failing well before that, and roughly 100 rows per file is the batch size that reliably works. NetSuite's bank statement parser handles up to 10,000 transactions per import, with the CSV Import Assistant capped at 25,000 records or 50 MB per job. Sage 50 publishes no per-file transaction cap.

Every one of those numbers is a hard stop that shows up at the worst possible moment: you have a year of statements converted, the file is ready, and the upload dies with an error that does not say why. The limits are real, they are enforced silently, and they are the single most common reason a bank statement import fails. Here they all are in one place.

Bank statement import limits, side by side

Two patterns jump out. The small business tools cap low, in the hundreds, because they assume you are uploading a month at a time. The ERP caps high, in the thousands, because it assumes a treasury team is loading a full bank file. And nearly every one of them counts rows, not months, so a busy operating account can blow past the limit inside a single statement period.

How many transactions can you import into QuickBooks at once?

QuickBooks Online enforces two limits on every manual upload: a maximum of 1,000 transactions and a maximum file size of 350 KB. Whichever you hit first stops the import. A file with 1,200 lines fails even at 200 KB, and a file with 400 verbose descriptions can fail on size while sitting comfortably under the row count. Split the file by month or by quarter and upload the parts one at a time.

QuickBooks Desktop is a different animal. Web Connect imports only .qbo files, publishes no transaction cap, and will happily take a large one, but it maps a single QBO file to a single account, so multi-account files have to be split anyway. There is more detail in our breakdown of how many transactions QuickBooks accepts at once.

What is the Xero bank statement import limit?

Xero accepts 1,000 statement lines per CSV bank statement import. That is the cap on the bank feed side specifically. Xero also enforces a broader ceiling of 100,000 rows on any import CSV, and rejects PDF and Excel files outright on the statement import path, which is why a converted CSV or OFX is the only workable route for a PDF statement. Our Xero import limits guide covers the field rules, including the 255-character reference field.

Why does my CSV import keep failing?

Row count is the first suspect, but it is rarely the only one. In practice, four things kill a bank statement import:

• Too many rows or too many kilobytes. The caps above, enforced without a useful error message.
• Extra columns. Wave wants date, description, and amount, and chokes when a running balance column tags along. FreshBooks wants the same three. QuickBooks accepts a 3-column or 4-column layout and nothing wider.
• Formatting inside the amounts. Dollar signs, thousands commas, and parentheses for negatives all cause rejections. Plain signed numbers pass.
• Summary and header junk. Bank-generated total rows, page footers, and a second header line in the middle of the file will each break the parse.

The fix for all four is the same: produce a clean, single-header, three or four column file per account per period, then split it to sit under the cap. That is a tedious job by hand and a fast one when the bank statement converter writes the file for you, because it strips the balance column, signs the amounts, and formats the dates on the way out.

What is the file size limit for a bank statement upload?

QuickBooks Online is the strict one at 350 KB per uploaded file, and it is the limit most people trip over, because a 350 KB CSV is smaller than it sounds once descriptions get long. NetSuite allows 50 MB per import job across all files in a multi-file upload. Xero, Wave, Sage, and FreshBooks do not publish a size cap, which in practice means the row limit binds first. If you are anywhere near a boundary, split by month. A month per file is never wrong and always imports.

How do I split a bank statement file for import?

Split on the statement period, not on an arbitrary row number. Take the converted CSV, sort it by date, and cut it at the month boundaries, keeping one account per file. Then import the parts oldest first so the running balance in the register builds in the right order, and let each import finish before starting the next one. FreshBooks in particular takes up to 15 minutes to process a file and wants transactions in chronological order.

Two habits save time here. Name the files with the account and the period, like operating-2026-03.csv, so a failed import is easy to retry. And check the transaction count in each part against the statement itself before uploading, because a missing line found at the reconciliation stage costs far more to chase down than one found now.

Do the limits apply to QBO and OFX files too?

They do, and this is the detail that surprises people. QuickBooks Online applies the same 1,000 transaction and 350 KB caps to a QBO, QFX, or OFX upload, not just to CSV. The file format changes what the software can read, not how much it will take in one bite. The advantage of a QBO file is not a bigger cap: it is that the dates, descriptions, and signs are already mapped, so nothing has to be matched by hand and the signs cannot land backwards. Our guide to converting bank statements to QuickBooks QBO walks through that path in both QuickBooks versions.

What about importing years of history?

This is where the limits stop being an annoyance and start shaping the project. A bank feed in QuickBooks Online typically reaches back only about 90 days on first connect, so a multi-year cleanup was never going to come from the feed. It comes from statements, which means a stack of PDFs, which means a converted file per account per month, each one under the cap. Twenty-four statements is twenty-four files, and each imports in seconds once it is in the right shape.

Teams doing this at volume tend to build the same small pipeline: convert the statement PDFs to CSV or QBO, split by month, import oldest first, then reconcile each period against the statement's closing balance before moving on. The same pipeline handles the other paperwork that piles up in a catch-up engagement, and if the stack in front of you is supplier bills rather than statements, running them through an invoice data extractor gets those into a spreadsheet the same way.

Which accounting software has the highest import limit?

NetSuite, by a wide margin, at 10,000 transactions per bank statement import and 25,000 records per CSV Import Assistant job. Sage 50 publishes no cap at all, which in practice means large files usually work. At the other end, Wave is the most restrictive in real use, and FreshBooks is the strictest documented limit at 500 transactions per file. QuickBooks Online and Xero land in the middle at 1,000, which for most small businesses is a comfortable month and a tight quarter.

None of these limits is a reason to pick one package over another. They are a reason to plan the import: know the cap before you start, convert the statements into the accepted layout, split by month, and the whole thing goes from a frustrating afternoon to twenty minutes of clicking.