“The app says the OFX version is not supported”
OFX comes in two shapes that share a name and almost nothing else. Version 1.x is SGML, where tags are opened and never closed; version 2.x is XML, where everything closes. Software that reads one may refuse the other outright, and the error rarely says which one it got.
Symptoms
An explicit complaint about the OFX version or header The file opens in one program and is refused by another A converter produced the file and nothing will accept it
What actually causes it
The app only reads OFX 1.x
Many desktop importers were written for the SGML form and never updated. Given an XML document with an <?xml declaration and closing tags on every element, they fail at the first line rather than reporting a version problem clearly.
The header contradicts the body
A file can declare OFXHEADER:100 while its body is written as XML, or the reverse. Whichever the importer trusts first, the other half fails — and files produced by conversion tools show this mismatch surprisingly often.
The version number is unusual
Values such as 103, 200 and 211 are all legitimate, but individual products accept a narrow subset and reject the rest without explaining which they wanted.
How to fix it
- Drop the file into the fixer below: it reports which form the file actually is, which is the fact the error message withholds.
- If the header and body disagree, repair it here — that mismatch alone breaks the import regardless of which version your app prefers.
- If the file is genuinely the version your app cannot read, ask the bank for the other flavour; many offer both under labels like "Quicken" and "Money".
- Where no alternative exists, CSV import avoids the version question entirely.
Related import problems
Skip the manual edit — fix it automatically
The fixer identifies the real format from the content rather than the extension, which settles version arguments quickly. Free, no signup, no upload.
Open the fixer