Stripe CSV 1,000-Row Limit: Why QuickBooks Splits Your Import (and How to Fix It)

TL;DR

• QuickBooks Online caps manual bank CSV imports at roughly 1,000 rows per file. Larger files fail silently or import partially.
• Stripe balance exports for busy months easily exceed this — a store doing 50 transactions a day hits 1,500+ rows in a 30-day export.
• PayoutPrep splits your file automatically into sequential batches (e.g. payout-1.csv, payout-2.csv), each under 999 rows, with correct headers, CRLF line endings, and no BOM.
• Import batches in numbered order into the same QuickBooks bank/clearing account. Don’t skip or reorder them.

---

Why the 1,000-Row Limit Exists

QuickBooks Online’s bank import was designed for monthly bank statements, not payment-processor firehoses. A typical business bank statement has 50–200 lines. Stripe, on the other hand, generates one row per balance transaction — charges, refunds, fees, transfers, adjustments — and a healthy e-commerce store can produce thousands per month.

Intuit never published an exact number, but in practice imports above ~1,000 rows either:

1. Fail outright with a generic “something went wrong” error, or
2. Import partially — the worst outcome, because you don’t notice the missing rows until reconciliation day.

Either way, the fix is the same: split the file before importing.

How to Split a Stripe CSV Manually (The Painful Way)

If you’re doing it by hand in Excel or Google Sheets:

1. Open the Stripe balance export.
2. Count the data rows (excluding the header).
3. Copy rows 2–1000 into a new file, save as batch-1.csv.
4. Copy rows 1001–2000 into another file, save as batch-2.csv.
5. Repeat until done.
6. Critical: every file must keep the exact same header row (Date,Description,Amount), use CRLF line endings, and contain no BOM — otherwise QuickBooks rejects the batch.

This works, but it’s error-prone. One missed row in the middle and your books are off by a transaction you’ll spend an hour hunting down.

The Automatic Way: PayoutPrep Batch Splitting

Upload your Stripe CSV to PayoutPrep and the splitter runs before anything else:

• Files over 999 data rows are divided into sequential batches automatically.
• Each batch gets the identical header row, CRLF endings, and UTF-8 without BOM.
• Filenames are numbered (stripe-qbo-1.csv, stripe-qbo-2.csv, …) so import order is obvious.
• The summary screen tells you exactly how many batches were created and how many rows are in each.

You then import each batch into QuickBooks Online in order: Banking → Upload from file → select batch 1 → map columns → confirm → repeat for batch 2.

Tips for Clean Multi-Batch Imports

• Use a dedicated Stripe clearing account in QuickBooks (see our clearing account guide). Importing batches into your main operating account makes it harder to spot a missing batch.
• Import in order, same day. Don’t import batch 1 on Monday and batch 2 on Friday — date-sorted views in QuickBooks will look fine, but your future self reconciling will thank you for the clean sequence.
• Keep the original export. If a batch fails, re-export from Stripe rather than editing a batch file by hand. Hand-edited CSVs are where encoding gremlins (BOM, LF endings, smart quotes) sneak in.
• Verify row counts. After importing, QuickBooks shows how many transactions were added. Compare against the batch summary from PayoutPrep. They should match exactly.

What About the Free Tier?

PayoutPrep’s free tier covers files up to 30 transactions — enough to test the full workflow end to end. Larger files (the ones that actually need splitting) use paid credits: $5 for a single conversion or $29 for a 10-pack. Either way, splitting itself is free — it’s part of every conversion, not an add-on.