“My CAMT.053 file will not import”
CAMT.053 is XML, which means it either parses or it does not — there is no partial reading. When software rejects one, the cause is almost always a version or namespace it was not built for, rather than damage to the file itself.
Symptoms
The software reports an unsupported or unknown XML schema The file opens in a browser as valid XML but imports as empty Some banks’ CAMT files import and others do not
What actually causes it
Several CAMT.053 versions are in use at once
Banks ship version 02, 04 or 08 depending on their platform, and each declares a different namespace. Software that matches the namespace exactly rejects every version but the one it knows, even though the content is nearly identical.
Optional elements your software requires
The schema marks many elements optional, so a valid file may omit related-party names or structured references. An importer that assumes those elements exist reads a compliant file as containing no usable transactions.
The file was re-saved and lost its declaration
Editing the file in a text editor can drop the XML declaration or add a byte order mark before it. Strict parsers refuse to read anything before the declaration, and the file fails on its very first byte.
How to fix it
- Check which CAMT version your bank ships and which your software supports; where the bank offers a choice, select the supported one at export.
- Run the file through the tool below to rule out damage before investigating schema support.
- Do not open and re-save the XML in a text editor — a byte order mark added there is enough to break parsing entirely.
- If no version matches, request an MT940 or CSV export from the same online banking screen as an interim route.
Related import problems
Skip the manual edit — fix it automatically
The tool reports byte order marks and structural damage in XML statement files, the faults that make a schema-valid file fail on the first byte. Free, no signup, no upload.
Open the fixer