Any OFX importer
“The download was cut off — truncated statement file”
When a statement download is interrupted — flaky Wi-Fi, a bank session timeout, a browser hiccup — the file ends mid-transaction and the closing </OFX> tag never arrives. Importers respond with generic "invalid file" errors that give no hint the file is simply incomplete.
Symptoms
The file is noticeably smaller than last month's download The last line of the file ends mid-word or mid-tag Every importer rejects it, each with a different generic error
What actually causes it
Cause 1
Interrupted transfer
The bank server closed the connection before the file finished. The structure is valid up to the cut point and garbage-free — just incomplete.
Cause 2
Bank-side generation timeout
Large date ranges can time out server-side, producing a file that ends after N transactions without any closing tags.
How to fix it
- First, simply re-download the file — a clean download is always better than a repaired truncation.
- If re-downloading is not possible (closed account, expired session), drop the file into the fixer below.
- The fixer detects the missing </OFX> structure and closes the file so the intact transactions import; the transaction that was cut off mid-record is dropped rather than guessed.
- Compare the imported transaction count against your online statement to see what the truncation cost you.
Related import problems
Skip the manual edit — fix it automatically
Repairing truncation recovers the transactions that made it into the file — it cannot invent the ones that did not. Free, no signup, no upload.
Open the fixer