“GnuCash cannot parse this OFX file”
GnuCash reads OFX through a strict parser, so files that other apps tolerate can stop it dead. The error text is usually generic, but the underlying causes are a short and checkable list.
Symptoms
An "unable to parse" or "not a valid OFX file" message on import The import assistant runs but the transaction list is empty The file works in Quicken or a bank viewer but not in GnuCash
What actually causes it
Structural defects the parser refuses
An unescaped "&" in a payee name, a missing declaration header, or a truncated download will each stop the parse at that point. These are silent in editors and obvious to a parser.
Invalid dates
Dates must be YYYYMMDD, optionally with a time and timezone. ISO or locale-formatted dates make records fail individually or reject the file.
No account matching step completed
GnuCash asks you to map the file's account to a GnuCash account. Skipping or mis-answering that step produces a successful-looking import with nothing in it.
Everything was filtered as a duplicate
GnuCash matches on transaction id and date. Re-importing an overlapping period leaves nothing new to show, which looks identical to a failed import.
How to fix it
- Drop the file into the fixer below. Escaping, header, date and truncation problems are all reported and repairable in place.
- Download the repaired file and re-run File → Import → Import OFX/QFX.
- Work through the account-matching screen carefully rather than accepting defaults.
- If the transaction list is still empty, widen the date range at the bank and re-export — the file may genuinely cover a period you already imported.
Related import problems
Skip the manual edit — fix it automatically
The fixer enforces the same structural rules GnuCash does, so a file that comes out clean here has no parser-level reason left to fail. Free, no signup, no upload.
Open the fixer