“Only part of the file imported”
The first weeks of the month import and the rest does not. That pattern is diagnostic: parsers stop where they break, so the boundary between what arrived and what did not marks the defect almost exactly.
Symptoms
Transactions arrive up to a certain date and then stop The count is consistently short by the same amount on re-import No error appears, or a generic one after partial success
What actually causes it
A parse error partway through
An unescaped character or a malformed value stops the parser at that byte. Everything before it is already processed; everything after is never read, which produces exactly this clean cut-off.
A truncated download
A file cut off in transit contains valid data up to the cut and nothing after it. The import succeeds on what exists and cannot know what is missing.
A duplicate identifier stopping the run
Some importers abort the remainder of a file when they meet a transaction id they have already seen, treating it as the end of new data.
How to fix it
- Note the date of the last transaction that arrived — that is where to look.
- Drop the file into the fixer below: escaping defects, malformed values, duplicate ids and truncation are all reported with line numbers.
- Repair and re-import; compare the resulting count against the statement so you can confirm the whole file made it this time.
- If truncation is the cause, re-download rather than repairing — a repaired truncation recovers what arrived, not what was lost.
Related import problems
Skip the manual edit — fix it automatically
The line number in the report usually lands within a transaction or two of where your import stopped, which confirms the diagnosis immediately. Free, no signup, no upload.
Open the fixer