MT940 to CAMT.053 converter
Your bank still delivers MT940, but your accounting package wants ISO 20022. Upload the SWIFT file and download schema-valid CAMT.053 — validated against the official XSD.
Upload your MT940 file →2 free conversions · no credit card required
MT940 to CAMT.053 in 3 steps
-
Upload your MT940.
.sta,.940,.mt940and.txtare recognised. Account number, currency and the:60F:/:62F:balances are read from the file. - Check the reconciliation. Opening balance plus movements must equal the closing balance. If it does not, StatementBridge says so before the export rather than letting your package reject the file later.
-
Download the CAMT.053.
You get a
camt.053.001.02or001.08file, depending on what your package asks for. Both are validated against the official ISO 20022 XSD.
What MT940 lacks and CAMT.053 has
MT940 dates from the telex era: 65 characters per line, with all
counterparty details crammed into the free-text :86: field.
CAMT.053 is XML with named elements. The conversion extracts what is
present in the MT940 — no converter can do more, and anything that
claims otherwise is inventing data.
What carries over
Date, value date, amount, debit/credit, counterparty account, name and description — structured into the correct ISO elements.
What is derived
SWIFT transaction codes are mapped to the closest ISO 20022 BkTxCd domain codes.
What stays empty
Fields MT940 does not have, such as structured remittance information, are left empty rather than filled with guesswork.
The reverse works too
Bank delivering CAMT.053 while your package wants MT940? That direction works just as well.
Is your bank migrating from MT940 to CAMT.053?
Then a converter is a bridge, not a destination. The transition from MT940 to CAMT.053 covers what that migration involves. If you are unsure which format you actually need, MT940 vs CAMT.053 explains the differences.
Frequently asked questions
Which CAMT.053 version do I get?
Either camt.053.001.02 or camt.053.001.08, whichever your package asks for. Both are validated against the official ISO 20022 XSD before download.
Is any information lost in the conversion?
Nothing that exists in the MT940 is dropped. The reverse is the real constraint: CAMT.053 has structured fields that MT940 never carried, such as separated remittance information. Those stay empty rather than being filled with guesswork.
How are SWIFT transaction codes handled?
MT940 transaction type codes are mapped to the closest ISO 20022 BkTxCd domain and family codes. Where no confident mapping exists, a neutral code is used instead of an incorrect specific one.
My bank is switching to CAMT.053. Do I still need this?
Only for the transition period and for historical files. Once your bank delivers CAMT.053 directly, use that — it always carries more detail than a converted MT940 can.
What if the balances do not reconcile?
You are told before the export, with the difference shown. That is deliberate: an unbalanced statement is usually an incomplete download, and finding out here is better than having your package reject it.