“The importer reports an unexpected end of file”
OFX nests its data in aggregates that must each be closed, and a file missing even one closing tag fails as a whole. The error message points at the end of the file because that is where the parser gave up, not where the fault is.
Symptoms
The importer reports an unexpected end of file or a parse error The file opens as readable text and looks complete The last transaction in the file is the one that appears truncated
What actually causes it
The download was interrupted
A connection dropped during export produces a file that ends mid-structure. Everything up to that point is valid, which is why the file looks normal until a parser reaches the end and finds aggregates still open.
The bank omits closing tags for simple elements
OFX 1.x permits leaving simple elements unclosed, and many banks do. Importers written against the stricter XML form of OFX 2.x reject those files even though they are legal in the older version.
An editor added or removed a line
Manual edits are the most common way a valid file becomes unclosed, because the nesting is easy to break and impossible to see at a glance in a file with no line breaks.
How to fix it
- Drop the file into the tool below — it closes every aggregate left open, not only the outermost one, which is where partial fixes usually fall short.
- Compare the file size against a previous download; a much smaller file points to an interrupted download rather than a formatting difference.
- If the download was interrupted, re-export rather than repair: a truncated file is missing transactions, and closing its tags will not bring them back.
- Check the repaired file’s transaction count against what you expect before importing.
Related import problems
Skip the manual edit — fix it automatically
The repair closes all open aggregates rather than just the outer one, and reports the transaction count so truncation cannot pass as a formatting fault. Free, no signup, no upload.
Open the fixer