SWIFT MT → MX (ISO 20022) Mapping Reference
SWIFT MT → MX (ISO 20022) Mapping Reference
Standard: MT = ISO 15022 (tagged text) · MX = ISO 20022 (XML)
Migration: SWIFT completed cross-border MT payment message decommission on 22 November 2025.
All cross-border payment instructions (MT 103, MT 202, etc.) must now use ISO 20022 MX equivalents.
1. Message-Level Mapping (MT → MX)
| MT Message | MT Name | MX Equivalent | MX Full Name |
|---|---|---|---|
| MT 101 | Request for Transfer | pain.001 | CustomerCreditTransferInitiation |
| MT 103 | Single Customer Credit Transfer | pacs.008 | FIToFICustomerCreditTransfer |
| MT 103 STP | Straight-Through Processing variant | pacs.008 (STP) | FIToFICustomerCreditTransfer_STP |
| MT 202 | General FI Transfer | pacs.009 | FinancialInstitutionCreditTransfer |
| MT 202 COV | Cover Payment | pacs.009 (COV) | FinancialInstitutionCreditTransfer_COV |
| MT 204 | Financial Institution Direct Debit | pacs.010 | FinancialInstitutionDirectDebit |
| MT 192 / 292 | Cancellation Request | camt.056 | FIToFIPaymentCancellationRequest |
| MT 196 / 296 | Answers to Cancellation | camt.029 | ResolutionOfInvestigation |
| MT 210 | Notice to Receive | camt.057 | NotificationToReceive |
| MT 900 | Confirmation of Debit | camt.054 (DEBIT) | BankToCustomerDebitCreditNotification |
| MT 910 | Confirmation of Credit | camt.054 (CREDIT) | BankToCustomerDebitCreditNotification |
| MT 940 | Customer Statement | camt.053 | BankToCustomerStatement |
| MT 942 | Interim Transaction Report | camt.052 | BankToCustomerAccountReport |
2. Field-Level Mapping: MT 103 → pacs.008
MT 103 = Single Customer Credit Transfer (most common cross-border payment message)
MX equivalent = pacs.008.001.09
| MT 103 Field | MT Field Name | MX XML Element | MX Element Name |
|---|---|---|---|
| Field 20 | Transaction Reference | <MsgId> / <EndToEndId> |
Message ID / End-to-End ID |
| Field 23B | Bank Operation Code | <SvcLvl><Cd> |
Service Level Code |
| Field 23E | Instruction Code | <InstrCd> |
Instruction Code |
| Field 32A (date) | Value Date | <IntrBkSttlmDt> |
Interbank Settlement Date |
| Field 32A (currency + amount) | Currency / Amount | <IntrBkSttlmAmt> |
Interbank Settlement Amount |
| Field 33B | Currency / Instructed Amount | <InstdAmt> |
Instructed Amount |
| Field 50K / 50F | Ordering Customer (Debtor) | <Dbtr> + <DbtrAcct> |
Debtor + Debtor Account |
| Field 52A / D | Ordering Institution | <DbtrAgt> |
Debtor Agent (BIC) |
| Field 53A / B | Sender’s Correspondent | <InstgRmbrsmntAgt> |
Instructing Reimbursement Agent |
| Field 54A / B | Receiver’s Correspondent | <InstdRmbrsmntAgt> |
Instructed Reimbursement Agent |
| Field 55A / B | Third Reimbursement Institution | <ThrdRmbrsmntAgt> |
Third Reimbursement Agent |
| Field 56A / D | Intermediary Institution | <IntrmyAgt1> |
Intermediary Agent 1 |
| Field 57A / D | Account with Institution | <CdtrAgt> |
Creditor Agent (BIC) |
| Field 59 / 59A | Beneficiary Customer | <Cdtr> + <CdtrAcct> |
Creditor + Creditor Account |
| Field 70 | Remittance Information | <RmtInf><Ustrd> |
Unstructured Remittance Info |
| Field 71A | Details of Charges | <ChrgBr> |
Charge Bearer (DEBT / CRED / SHAR) |
| Field 71F | Sender’s Charges | <ChrgsInf> |
Charges Information |
| Field 72 | Sender-to-Receiver Info | <InstrForNxtAgt> / <InstrForCdtrAgt> |
Instruction for Next / Creditor Agent |
3. Field-Level Mapping: MT 202 → pacs.009
MT 202 = General Financial Institution Transfer
MX equivalent = pacs.009.001.09
| MT 202 Field | MT Field Name | MX XML Element | MX Element Name |
|---|---|---|---|
| Field 20 | Transaction Reference | <MsgId> |
Message Identification |
| Field 21 | Related Reference | <InstrId> |
Instruction Identification |
| Field 32A (date) | Value Date | <IntrBkSttlmDt> |
Interbank Settlement Date |
| Field 32A (currency + amount) | Currency / Amount | <IntrBkSttlmAmt> |
Interbank Settlement Amount |
| Field 52A / D | Ordering Institution | <InstgAgt> |
Instructing Agent |
| Field 53A / B | Sender’s Correspondent | <InstgRmbrsmntAgt> |
Instructing Reimbursement Agent |
| Field 54A / B | Receiver’s Correspondent | <InstdRmbrsmntAgt> |
Instructed Reimbursement Agent |
| Field 56A / D | Intermediary | <IntrmyAgt1> |
Intermediary Agent 1 |
| Field 57A / D | Account with Institution | <CdtrAgt> |
Creditor Agent |
| Field 58A / D | Beneficiary Institution | <Cdtr> + <CdtrAcct> |
Creditor + Creditor Account |
| Field 72 | Sender-to-Receiver Info | <InstrForNxtAgt> |
Instruction for Next Agent |
4. Key Structural Differences: MT vs MX
| Concept | MT Approach | MX Approach | Migration Note |
|---|---|---|---|
| Identifiers | Single Field 20 (max 16 chars) | Separate <MsgId>, <InstrId>, <EndToEndId>, <UETR> |
MX supports multiple IDs; UETR is new |
| Addresses | Free-text lines (fields 50K, 59) | Structured: <StrtNm>, <TwnNm>, <Ctry> |
Town + Country minimum now mandatory |
| Charges | Field 71A: OUR / SHA / BEN | <ChrgBr>: DEBT / CRED / SHAR |
Simple code rename |
| Remittance info | Field 70 (max 140 chars, 4 lines) | <Ustrd> (140 chars) or fully structured <Strd> |
MX can carry full structured invoice data |
| BIC format | 8 or 11-char BIC | <BICFI> 11 chars enforced |
Pad 8-char BICs with “XXX” |
| Amount | Implicit in Field 32A | Explicit <Ccy> attribute on amount element |
No behaviour change, different structure |
| Correspondent chain | Fields 53 / 54 / 55 (limited) | Full agent chain elements with sub-elements | MX supports richer routing detail |
5. MX Message Namespace Reference
| MX Message | Namespace (latest version) | File Name Convention |
|---|---|---|
| pain.001 | urn:iso:std:iso:20022:tech:xsd:pain.001.001.09 |
pain.001.001.09.xml |
| pain.002 | urn:iso:std:iso:20022:tech:xsd:pain.002.001.10 |
pain.002.001.10.xml |
| pain.007 | urn:iso:std:iso:20022:tech:xsd:pain.007.001.09 |
pain.007.001.09.xml |
| pain.008 | urn:iso:std:iso:20022:tech:xsd:pain.008.001.09 |
pain.008.001.09.xml |
| pacs.002 | urn:iso:std:iso:20022:tech:xsd:pacs.002.001.10 |
pacs.002.001.10.xml |
| pacs.003 | urn:iso:std:iso:20022:tech:xsd:pacs.003.001.09 |
pacs.003.001.09.xml |
| pacs.004 | urn:iso:std:iso:20022:tech:xsd:pacs.004.001.10 |
pacs.004.001.10.xml |
| pacs.008 | urn:iso:std:iso:20022:tech:xsd:pacs.008.001.09 |
pacs.008.001.09.xml |
| pacs.009 | urn:iso:std:iso:20022:tech:xsd:pacs.009.001.09 |
pacs.009.001.09.xml |
| pacs.010 | urn:iso:std:iso:20022:tech:xsd:pacs.010.001.05 |
pacs.010.001.05.xml |
| camt.052 | urn:iso:std:iso:20022:tech:xsd:camt.052.001.10 |
camt.052.001.10.xml |
| camt.053 | urn:iso:std:iso:20022:tech:xsd:camt.053.001.10 |
camt.053.001.10.xml |
| camt.054 | urn:iso:std:iso:20022:tech:xsd:camt.054.001.10 |
camt.054.001.10.xml |
| camt.056 | urn:iso:std:iso:20022:tech:xsd:camt.056.001.09 |
camt.056.001.09.xml |
| camt.029 | urn:iso:std:iso:20022:tech:xsd:camt.029.001.10 |
camt.029.001.10.xml |
6. Translation Approaches
Like-for-Like
Map only what exists in MT. No new MX fields populated beyond the MT equivalent.
Used during coexistence when downstream counterparties still translate MX back to MT.
Avoids data truncation in reverse translation.
Enhanced
Populate additional MX-native fields not available in MT:
- Structured postal addresses (
<PstlAdr>) - Legal Entity Identifier (
<LEI>) - Extended remittance (
<Strd>with invoice references) - Purpose codes (
<Purp><Cd>)
Recommended once all counterparties are fully ISO 20022 capable.
7. Quick Reference: Charge Bearer Codes
| MT 71A Code | MX <ChrgBr> Code |
Meaning |
|---|---|---|
| OUR | DEBT | All charges paid by ordering customer (debtor) |
| SHA | SHAR | Shared — sender pays own bank, receiver pays their bank |
| BEN | CRED | All charges paid by beneficiary (creditor) |
Reference: SWIFT CBPR+ Usage Guidelines · ISO 20022 Message Definition Reports · MAS MEPS+ Technical Specifications