“My statement file is too large to open or import”
A file holding several years of transactions can exceed what a spreadsheet will display or an importer will hold in memory. Splitting it is straightforward, but the obvious way to split it is also the way that quietly corrupts it.
Symptoms
The spreadsheet stops at a row limit and the rest is missing The importer freezes or closes without a message Opening the file takes minutes and scrolling is unusable
What actually causes it
Spreadsheet row limits truncate silently
Spreadsheets stop at a fixed number of rows and load what fits. Saving after that writes only the loaded portion, so a file inspected in a spreadsheet can come out permanently shorter than it went in.
Importers hold the whole file in memory
Many importers parse the entire file before writing anything, so memory use scales with file size rather than staying constant. Beyond a certain size the program stops responding rather than reporting a limit.
Splitting by line count breaks quoted fields
A description containing a line break spans two physical lines inside one quoted field. Cutting a CSV every so many lines can land in the middle of one, leaving two files that are each individually invalid.
How to fix it
- Re-export in shorter periods from the bank instead of splitting locally — a file that was never too large needs no repair.
- If you must split, cut only at record boundaries and check each part with the tool below before importing it.
- Never open a large CSV in a spreadsheet and save it; the row limit truncates without warning.
- Import the parts in date order into the same account so running balances stay meaningful.
Related import problems
Skip the manual edit — fix it automatically
The checker validates each part after a split and reports records broken across the cut, which is the fault hand-splitting introduces most often. Free, no signup, no upload.
Open the fixer