How Many Transactions Can You Import into QuickBooks at Once?

Short answer: QuickBooks Online accepts up to 1,000 transactions per uploaded file, and the file itself must be 350 KB or smaller. Whichever limit you hit first is the one that stops the import. Accepted formats are CSV, QBO, QFX, and OFX, and a CSV must be either 3 columns (Date, Description, Amount) or 4 columns (Date, Description, Credit, Debit). If you have more than 1,000 transactions, split the file, usually by month or by quarter, and upload the pieces in date order.

Those two numbers explain most failed imports. A file that is too big does not tell you it is too big in plain language; QuickBooks just refuses it, or throws a vague message about missing information. Once you know the caps, the fix takes two minutes.

QuickBooks import limits at a glance

Note the two different format rows. QuickBooks Online is flexible about what you upload. QuickBooks Desktop is not: its Web Connect import reads .qbo files and nothing else, so a QFX, a QIF, or a CSV will not go into a bank account there at all.

Why does QuickBooks limit imports to 1,000 transactions?

The cap keeps a single upload from timing out while QuickBooks parses, deduplicates, and stages every line into the For review tab. It is a processing limit, not a licensing one, and there is no setting or plan tier that raises it. A busy business checking account can easily run 150 to 400 lines a month, so a full year lands somewhere between roughly 1,800 and 4,800 transactions. That is three to five files, not one.

What happens if you go over the limit?

The import fails, and the error message rarely names the real cause. The most common symptoms are a file that appears to upload and then produces nothing, a message that says some info may be missing from your file, or a spinner that never resolves. Before you start rewriting headers, check the row count and the file size. If either is over, nothing else you change will help.

The 350 KB ceiling bites sooner than people expect, because it counts characters, not rows. Long transaction descriptions, the kind card processors and ACH lines produce, can push a file past 350 KB well before it reaches 1,000 rows. If your file is under 1,000 transactions and still rejected, size is the likely culprit.

How to split a large import correctly

Splitting is simple, but the order matters if you want the reconciliation to work afterward.

1. Split on statement boundaries, not arbitrary row counts. One file per month, or per quarter for a quiet account, keeps each file aligned to a statement you can reconcile against.
2. Check the boundary date first. Open the register and note the oldest transaction QuickBooks already has, so your import only adds what is missing and does not duplicate what is there.
3. Upload oldest first. Ending balances chain together, so importing in date order lets you reconcile each month in sequence instead of untangling them later.
4. Keep one account per file. QuickBooks maps an upload to a single account. Merging checking and savings into one CSV will not work.
5. Reconcile as you go. Reconcile each month right after it imports. Catching a problem in one month is far easier than finding it after a year is loaded.

Can I import a full year of bank transactions into QuickBooks?

Yes, but not in one file, and not through the bank feed. The feed only backfills about 90 days on a new connection, so it will never produce a year on its own. To load a full year you download the statements covering it, convert them into QuickBooks-ready files, and upload them in sequence, staying under 1,000 transactions and 350 KB each. A bank statement converter for QuickBooks handles the conversion and lets you keep each statement as its own file, which lines the imports up with the statements you will reconcile against anyway.

This is the standard workflow for a bookkeeping catch-up, a QuickBooks migration, or an audit lookback. It is also why the PDF statement matters so much: it is usually the only place a year of history still exists, since most banks stop letting you download raw transaction data somewhere between 90 days and 18 months back.

Does QuickBooks Desktop have the same limits?

Desktop is different in kind rather than in degree. There is no published 1,000-line cap on a Web Connect import, but there is a much harder constraint: the file must be a .qbo. Desktop's bank feed will not import a CSV into a bank or credit card account, and it will not read a QFX or a QIF there either. In practice, very large QBO files can also fail or slow the file to a crawl, so splitting by statement is still the sane approach. Import through File, Utilities, Import, Web Connect Files, and deactivate any active bank feed on the account first so the two sources do not duplicate transactions.

What about the CSV column rules?

Row count and file size are only half the story. QuickBooks Online is strict about shape, and most rejected CSVs fail here rather than on size:

• Use either 3 columns (Date, Description, Amount, with money out as a negative number) or 4 columns (Date, Description, Credit, Debit, with each row using only one of the two).
• Do not add a category column. QuickBooks ignores categories on import and errors on files with more than four columns.
• Strip dollar signs, commas, and percent symbols out of the amount column. Plain numbers with two decimals, like 1042.50.
• Keep one consistent date format throughout, MM/DD/YYYY being the safest for US files.
• Delete opening balance, closing balance, account number, and summary rows. QuickBooks wants transaction lines only.

The same limits apply to any spreadsheet you build yourself, wherever the numbers came from. If the rows you are importing came off invoices or receipts rather than a bank statement, they still have to be turned into clean spreadsheet rows before QuickBooks will look at them, and they are subject to the same 1,000-line ceiling.

Frequently asked questions

How many transactions can QuickBooks Online import at once?

Up to 1,000 transactions in a single uploaded file, and the file must be 350 KB or smaller. If your data exceeds either limit, split it into multiple files, typically one per month, and upload them in date order starting with the oldest.

Why is my QuickBooks import failing with no clear error?

Check the row count and file size first, since QuickBooks rarely says outright that a file is too large. After that, check the shape: 3 or 4 columns only, no category column, no currency symbols in the amounts, one consistent date format, and no balance or summary rows.

Can QuickBooks import more than 1,000 transactions in one file?

No. The 1,000-line ceiling on QuickBooks Online is fixed and no plan raises it. The workaround is to split the data across several files. Splitting on statement boundaries is best, since it keeps each import aligned with the statement you will reconcile against.

Does the 350 KB limit include the header row?

It applies to the whole file, header included. Because it measures characters rather than rows, long transaction descriptions can push a file over 350 KB even when it holds well under 1,000 transactions. Trimming description text or splitting the file both fix it.

The short version

Plan every QuickBooks import around two numbers: 1,000 transactions and 350 KB. Split anything larger on statement boundaries, upload oldest first, keep one account per file, and reconcile each month as it lands. Do that and a full year of history goes in cleanly, which the bank feed alone will never manage. If the statements are still PDFs, converting them to a QBO Web Connect file produces exactly the shape QuickBooks expects, one statement at a time, and sidesteps the column rules entirely.