Swift retires MT900/910/940/942/950 statement and notification messages in the 2027-2028 coexistence window, and receive-capability for the camt.052/053/054 equivalents is mandated from November 2027 (dated observation, source below). Swift itself provides no MT-to-ISO 20022 conversion tool, so the translation burden lands on the corporate or treasury receiving the message. Paste an MT9xx tag-line message below; this tool maps it to a camt-shaped JSON object field by field and, more importantly, runs a fidelity report: truncation findings, unmappable tags, and (for MT940/950/942) a 60F + Σ61 = 62F balance-consistency check. The kernel emits JSON only; camt XML is serialized from that JSON in your browser, never on the wire.
Paste tag-line fields (:20:, :25:, :28C:, :60F:, :61:, :86:, :62F:, or :32A:/:72: for a notification). A demo below is already loaded.
| MT tag | camt path | value | transform |
|---|
It does not decode structured ?nn subfields inside :86: narrative text; those pass through as raw text with a flag. It does not reconcile the mapped statement against a ledger or a second source; see tools/565 for that. It carries no Swift endorsement and issues no compliance-deadline guarantee.
MT tag → camt element path mappings are reused from tools/402, the Swift MT/MX field decoder. This tool composes that vocabulary into a full-message mapper with a fidelity report; it does not maintain a second, divergent field table.