The QuickBooks Online bank upload limit is 350 KB per file and 1,000 lines per file, with one transaction on each line. A file over either cap is refused. The fix is to shorten the date range: split a long history into monthly or quarterly files, upload them oldest first, and make sure no two files share a date.
What is the QuickBooks Online bank upload limit?
The QuickBooks Online bank upload limit has two parts, and a file must pass both. Intuit's help article on manually uploading transactions says the file must be 350 KB or less, hold no more than 1,000 lines, and be in English.
Those two caps measure different things. The kilobyte cap is about the weight of the file on disk. The line cap is about how many transactions sit inside it. A small business checking account with a few dozen payments a month will never come near either number in a single month. A busy account, or a download that covers several years, can pass one of them without warning.
The same article covers the three file types the upload treats as lists of transactions: QBO, QFX and CSV. A CSV needs either three columns (date, description, amount) or four (date, description, credit, debit). The caps apply whichever of those you send.
Which cap you hit first
For a plain three-column CSV, the line cap almost always bites before the size cap. A typical row such as 03/14/2026,Hardware store,-42.18 takes well under a hundred characters, so 1,000 of them weigh far less than 350 KB. A QBO or QFX file is different. Each transaction is wrapped in labelled tags for its type, date, amount, ID and name, so every line costs several times more space. A long QBO file can therefore hit the size cap while it still holds fewer than 1,000 transactions.
Why a full year of statement lines trips the upload limit
A full year usually trips the upload limit because banks will happily export more than QuickBooks will take. The download screen at your bank has no idea where the file is going. It gives you every transaction in the range you picked, and a year of card purchases, transfers and fees can run well past 1,000 lines.
The failure is easy to misread. The file opens in a spreadsheet, the columns look right and the dates make sense. Nothing about the content is wrong. Only the size is. People then spend time changing date formats or column headers when the real answer is to cut the file in two.
There is also a quieter cause. Some exports include more than transactions: a block of account details at the top, a summary of totals at the bottom, or pending items. Those rows add lines without adding real activity. Delete them before you count, because the upload treats every line as a transaction and a summary row would also confuse the column mapping.
Splitting a year of transactions into upload-sized files
Split by date, not by row number. Intuit's own advice for larger uploads is to shorten the date range and download in smaller batches. Cutting at a month boundary means each file starts on the first of a month and ends on the last day, which makes gaps and overlaps easy to see.
Here is a worked example. The line counts below are made up for illustration. They show a business whose busy season pushes some months well above the others.
| Months | Lines per month (example) | Lines in the file | File name |
|---|---|---|---|
| January to March | 180, 160, 210 | 550 | checking-2026-01-01-to-2026-03-31 |
| April to June | 290, 330, 340 | 960 | checking-2026-04-01-to-2026-06-30 |
| July to September | 410, 395, 280 | 1,085 | too many: split again |
| July and August | 410, 395 | 805 | checking-2026-07-01-to-2026-08-31 |
| September to December | 280, 220, 190, 240 | 930 | checking-2026-09-01-to-2026-12-31 |
Quarters work until a quarter runs over. In the example, July to September comes to 1,085 lines, so it becomes July and August in one file, with September joining the last quarter instead. Every file still begins on the first day of a month and ends on the last, so the chain of dates has no holes.
Upload the files in date order, oldest first. Before each upload, check the earliest and latest date in the file against its name. After each upload, compare the number of rows waiting for review with the line count in the table. The full upload walkthrough is in the guide to importing bank transactions into QuickBooks Online.
If your history only exists as PDF statements, you can build one file per statement and group them the same way. SimpleBankConvert is being built to turn each PDF statement into a CSV or QBO file. It hasn't opened accounts yet, and the get started page takes your name for the first invitations.
Do PayPal and Venmo exports reach the upload limit sooner?
Payment app exports often reach the upload limit sooner, because they list more rows per sale than a bank statement does. A single customer payment can appear as the payment, a fee and a transfer to your bank, three lines where the bank shows one deposit.
That changes how you split. A month of PayPal activity can be several times longer than the matching month of checking activity. Count the lines after you have removed the rows you don't plan to import, then decide on the date ranges. The post on importing PayPal transactions into QuickBooks Online explains which PayPal rows belong in the file and which only describe money moving between your own accounts.
Venmo statements come one month at a time, which helps. A single month rarely holds a thousand lines for a small business, though personal and business payments mixed in one account inflate the count. The guide to importing Venmo transactions into QuickBooks Online covers sorting those apart before you upload.
Upload limit workarounds that leave gaps or duplicates
The common mistakes with the upload limit come from splitting a file by hand in a spreadsheet. Cutting at row 1,000 instead of at a date usually separates transactions from the same day, and it is easy to copy a row into both halves or leave one out.
Watch for these patterns:
- Overlapping files. Two files that both contain the 30th of June will bring that day's transactions in twice. Intuit's article says to start the next download on the day after your last transaction in that account.
- A day dropped between files. If one file ends on the 30th and the next starts on the 2nd, the 1st never arrives. The bank balance in QuickBooks will drift from the statement by exactly that day's activity.
- Header rows lost on the second half. When a CSV is split by hand, the second file often has no header row. Either add the header back or tell the mapping screen the first row is data.
- Turning bank lines into journal entries to dodge the cap. Some people try a different import to get around the row limit. Journal entries skip the bank review step entirely, and the post on when to import journal entries into QuickBooks Online explains why they are a poor stand-in for bank lines.
If you keep a second set of books in Xero, its statement import has its own rules, and the account has to exist first. The guide to adding a bank account in Xero before importing covers that side.