Convert an MT940 bank statement to ISO 20022 camt.053 - locally in the browser, with no upload; the bank data never leaves your device.
Running locally on your device ...
0%
Your files never left your device
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
MT940 is the classic SWIFT FIN format for the electronic account statement: a line-based format with tags like :20: (reference), :25: (account/IBAN), :28C: (statement number), :60F: and :62F: (opening and closing balance), :61: (entry line) and :86: (remittance information). Many banks still deliver statements as MT940. The ISO 20022 successor camt.053 (camt.053.001.08) carries the same information as structured XML that modern accounting and treasury systems read directly.
Drop your MT940 file; the tool reads the tags and builds a camt.053 XML with the account, opening and closing balance and one entry per :61: line (amount, debit/credit, booking date, remittance from :86:). You can drop several files at once, each becomes its own camt.053. Everything runs entirely locally in the browser - pure JavaScript, no server, no foreign library from a foreign CDN.
Honest about the MT-to-MX switch: the mapping is not lossless. The unstructured :86: remittance text and the SWIFT X character set cannot be fully mapped onto the structured camt fields (such as structured debtor/creditor details or purpose codes). The tool carries the remittance into RmtInf/Ustrd as best it can and the posting text into AddtlNtryInf; whatever cannot be derived in a structured way is lost in this conversion - that is a property of the format switch, not a fault of the tool.
| Input formats | STA, MT940, TXT |
|---|---|
| Output format | XML |
| Batch processing | Yes |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: Converts an MT940 bank statement (SWIFT FIN) to ISO 20022 camt.053 (camt.053.001.08): account/IBAN from :25:, opening balance (:60F:) as OPBD, closing balance (:62F:) as CLBD and one entry per :61: line (amount, debit/credit, booking date, remittance from :86: into RmtInf/Ustrd, posting text into AddtlNtryInf). The MT-to-MX mapping is NOT lossless: the unstructured :86: text and the SWIFT X character set do not fully map onto the structured camt fields. It is a format conversion for data exchange, not a replacement for the original camt your bank delivers; verify the result against a bank-specific schema with your software.
No. Reading the MT940 and building the camt.053 run entirely locally in the browser (pure JavaScript, no server); the statement never leaves your device.
ISO 20022 camt.053.001.08 (Bank-to-Customer Statement) with the account, OPBD/CLBD balance and one entry per :61: line.
No. The unstructured :86: remittance and the SWIFT X charset do not fully map onto the structured camt fields; the text is carried best-effort into RmtInf/Ustrd. That is a property of the MT-to-MX switch.
Yes. Drop several MT940 files at once; each becomes its own camt.053 XML.
Yes, each :61: line (with its following :86:) becomes its own entry (Ntry) in the camt.053 with amount, debit/credit and remittance.