Swift ISO 20022 Migration & MX Messaging 2 — Questions and Answers
Question 1: What does the 'camt' message category handle in ISO 20022?
- Credit card authorization transactions
- Cash Management reporting and notifications (Correct answer)
- Currency and Money Transfer instructions
- Counterparty Management agreements
Correct answer: Cash Management reporting and notifications
'camt' stands for Cash Management, covering messages for account balance reporting, transaction notifications, and statements (e.g., camt.053 replaces MT 940).
Question 2: What does the 'pain' message category represent in ISO 20022?
- Payment Authorization and Identification
- Payment Initiation (Correct answer)
- Payment Accounting and Invoicing Network
- Post-Authorization Instruction Notification
Correct answer: Payment Initiation
'pain' stands for Payment Initiation, covering messages from corporates or individuals initiating payment instructions to their financial institution.
Question 3: Which ISO 20022 message replaces the MT 202 financial institution credit transfer?
- pacs.002
- pacs.004
- pacs.009 (Correct answer)
- pacs.010
Correct answer: pacs.009
The pacs.009 (Financial Institution Credit Transfer) is the ISO 20022 replacement for the MT 202, used for bank-to-bank transfers not involving customer funds.
Question 4: What is the primary purpose of the Business Application Header (BAH) in ISO 20022 MX messages?
- To encrypt the body of the message payload
- To provide routing, identification, and business context for the message (Correct answer)
- To define the currency conversion rate applied
- To specify charge bearer and fee allocation codes
Correct answer: To provide routing, identification, and business context for the message
The BAH provides essential routing and identification metadata — sender, receiver, message type — that frames the core business payload of the MX message.
Question 5: In ISO 20022, the 'UltimateDebtor' field identifies:
- The sending financial institution initiating the transfer
- The party that ultimately owes the funds, which may differ from the instructing debtor (Correct answer)
- The debtor's correspondent or intermediary bank
- The final beneficiary recipient of the payment
Correct answer: The party that ultimately owes the funds, which may differ from the instructing debtor
The UltimateDebtor field identifies the original party on whose behalf the payment is being made, enabling full transparency in multi-party payment chains.
Question 6: What is the purpose of the LEI (Legal Entity Identifier) in ISO 20022 messages?
- To encrypt sensitive payment data fields during transmission
- To uniquely identify legal entities involved in financial transactions (Correct answer)
- To specify the payment routing path through correspondent banks
- To indicate message processing priority level
Correct answer: To uniquely identify legal entities involved in financial transactions
The LEI is a 20-character alphanumeric code used in ISO 20022 to unambiguously identify legal entities, improving transparency and regulatory compliance.
Question 7: What advantage does ISO 20022's enhanced remittance information capability provide over MT messages?
- Significantly faster processing speeds on SWIFT endpoints
- Ability to carry more detailed, structured invoice and payment purpose data (Correct answer)
- Automatic currency conversion applied between parties
- Built-in message encryption for all sensitive fields
Correct answer: Ability to carry more detailed, structured invoice and payment purpose data
ISO 20022 allows structured remittance information with invoice-level detail, enabling automated reconciliation that is not possible with MT's limited free-form remittance fields.
Swift ISO 20022 Migration & MX Messaging 2
What does the 'camt' message category handle in ISO 20022?