Supported MT to MX mappings
| SWIFT MT source | ISO 20022 target | Business purpose |
|---|---|---|
MT101 | pain.001.001.09 | Customer credit transfer initiation |
MT103 | pacs.008.001.08 | Customer credit transfer |
MT202 / MT202 COV | pacs.009.001.08 | FI transfer and cover payment |
MT103/202 REJT | pacs.002.001.10 | Payment rejection status |
MT103/202 RETN | pacs.004.001.09 | Payment return |
MT900 / MT910 | camt.054.001.08 | Debit or credit notification |
MT942 | camt.052.001.08 | Intraday account report |
MT940 / MT950 | camt.053.001.08 | Account statement |
How conversion targets are selected
FinMessage detects the application-header type. For MT103 and MT202, a :72: value containing REJT selects pacs.002 and RETN selects pacs.004. MT202 messages carrying underlying debtor and creditor fields are treated as MT202 COV.
How to convert a SWIFT MT message
- Paste the complete message or upload an MT file.
- Select Convert to MX.
- Review the mapping warnings and generated elements.
- Copy or download the XML and validate it for the destination scheme.
Why MT to MX is not one-to-one
MT fields often combine values that ISO 20022 separates into parties, accounts, agents, identifiers and structured elements. FinMessage exposes defaults and missing-data decisions as warnings.
Common MT to MX conversion issues
- Input has only field lines: include the complete SWIFT FIN header and block 4 so the source MT type can be detected.
- The MT variant is unsupported: check the list of supported conversion mappings and review MT103 structure before retrying.
- The XML has mapping warnings: missing parties or structured addresses may require enrichment before network use.
- You need schema validation: the generated XML is a mapping draft; check its business structure with the pacs.008.001.08 checker where applicable, then validate it with authoritative XSD and usage guidelines.
Try an MT103 to pacs.008 example
Choose the safe MT103 example above, convert it, then compare with the MT103 vs pacs.008 guide. To focus on that mapping alone, open the dedicated converter.
Data handling
Successful message actions are saved to history. Review or delete saved entries in the workspace. Use authorized data and redact sensitive values when a representative sample is sufficient.