MT940 Viewer & Converter → camt.053
Open an MT940 statement, see balances and transactions, and export camt.053 — entirely in your browser, nothing uploaded.
What is MT940 and how does it relate to camt.053?
MT940 is the legacy SWIFT text-based "Customer Statement Message" format used for decades to deliver electronic bank statements. Its ISO 20022 replacement is camt.053, an XML format; SWIFT retired MT940 for cross-border use in November 2025. This free tool reads an MT940 file locally, extracts the account, balances and transactions, and converts it to a camt.053 statement — no data ever leaves your browser.
About the MT940 viewer & converter
MT940 is the SWIFT "Customer Statement Message": a tag-based text format (:20: reference, :25: account, :60F: opening balance, :61: statement line, :86: remittance info, :62F: closing balance) that banks have used for decades to deliver end-of-day account statements to ERP and treasury systems. It is compact but rigid, with limited structured data compared with the modern ISO 20022 XML statement, camt.053.
ValidateFin parses every tag locally in your browser: it reads the opening and closing balances, every :61: transaction (value date, debit/credit mark including RC/RD reversals, amount, SWIFT transaction type and reference) and the attached :86: description, then checks that the opening balance plus the sum of movements equals the stated closing balance. It can then export a valid camt.053.001.02 statement carrying the real balances and mixed debit/credit entries — the exact input treasury and ERP systems now expect after the ISO 20022 migration. No MT940 file is ever uploaded to a server.
Why the MT940 to camt.053 migration matters
- The end of MT9xx coexistence is closing after SWIFT's November 2025 ISO 20022 cut-over, so banks are switching statement feeds to camt.053.
- ERP and treasury systems — SAP S/4HANA, SAP Business One, Sage — increasingly import camt.053 only, leaving finance teams to convert their MT940 feeds.
- camt.053 carries far richer structured data (nearly 1,600 possible fields) than MT940's rigid tags, with an official ISO 20022 XSD to validate against.
- A converter is only useful if the camt.053 keeps the real balances and both debit and credit entries — an MT940 mixes them, unlike a payment-initiation file.
- Because a bank statement is sensitive data, converting locally in the browser avoids emailing account numbers and counterparties to a third-party service.
Frequently asked questions
What is an MT940 file?
MT940 is the SWIFT "Customer Statement Message", a legacy tag-based text format used to deliver electronic bank statements. Each statement contains a reference, an account, opening and closing balances, and one line per transaction.
What replaces MT940?
The ISO 20022 XML statement camt.053 replaces MT940. SWIFT retired MT940 for cross-border messaging in November 2025, and most ERP and treasury systems now import camt.053 instead.
Can I convert MT940 to camt.053 here?
Yes. After reading the file, click "Export camt.053" to download a valid camt.053.001.02 statement generated from the MT940, with the real balances and debit/credit entries. Everything runs in your browser.
Is my bank statement uploaded anywhere?
No. The MT940 file is read, parsed and converted entirely in your browser using JavaScript. No statement data is ever sent to a server.
How does the tool know the file is consistent?
MT940 has no schema, so the integrity check is arithmetic: the opening balance plus the net of all :61: movements must equal the closing balance in :62F:. A mismatch is flagged as a warning.
Does it handle reversals (RC/RD)?
Yes. A reversed credit (RC) is counted as a debit and a reversed debit (RD) as a credit, and the transaction type is prefixed with REV: so the reversal stays visible.