The table below contains an overview of how elements from a Customer Credit Transfer Initiation (pain.001) sent by an initiating party to its bank would be logically mapped to the subsequent MT 103, which can be the message used by the bank receiving the pain.001 to transfer the funds to the next bank party in the chain.
For detailed translation information, please consult the pacs.008.001.02 to MT 103 (and vice versa), and the pain.001.001.03 to MT 101 translation rules available through swift.com (Support/documentation/UHB on-line). These rules contain exhaustive explanations on how to translate components, elements and data types from the ISO 20022 messages to and from their equivalent FIN MT messages.
The mapping below follows the logic followed in these translation rules, but only provides a high-level view of where ‘Customer Credit Transfer Initiation’ data logically can be included in the MT 103.
Note : the table below does not include all elements (contained in a complex type) of certain ‘reusable’ components (such as customer identification or financial institution
identification). These components are marked with a “+”. The translation rules for these elements can be found in the detailed translation information referred to above. Conventions
If an element is identified as a ‘point-to-point’ element in the table below, it means it does not have to be mapped to the interbank chain.
If an element is identified as ‘cannot be mapped’, it means the MT 103 does not cater for this element.
For all other elements, a placeholder in the MT 103 is indicated.
pain.001.001.03 MT 103
Message item
Occur
rence Type
Group Header [1..1] Component
Message Identification [1..1] Max35Text
Point-to-point element, so not transported in interbank chain
Creation DateTime [1..1] ISODateTime
Point-to-point element, so not transported in interbank chain
Authorisation [0..2] Max128Text
Point-to-point element, so not transported in interbank chain
Number of Transactions [1..1] Max15NumericText
Point-to-point element, so not transported in interbank chain
Control Sum [0..1] DecimalNumber
Point-to-point element, so not transported in interbank chain
Initiating Party [1..1] Component + Cannot be mapped
Forwarding Agent [0..1] Component + Cannot be mapped
Payment Information [1..n] Component Payment Information
Identification [1..1] Max35Text
Point-to-point element, so not transported in interbank chain
Payment Method [1..1] Code
Point-to-point element, so not transported in interbank chain.
CHK will result in issuance of cheque, TRF may result in a.o. actual creation of MT 103.
BatchBooking [0..1] Indicator
Point-to-point element, so not transported in interbank chain
Number of Transactions [0..1] Max15NumericText
Point-to-point element, so not transported in interbank chain
Control Sum [0..1] DecimalNumber
Point-to-point element, so not transported in interbank chain
Payment Type Information [0..1] Component
Instruction priority [0..1] Code
Point-to-point element, so not transported in interbank chain
Service Level or [0..1] Choice Component Cannot be mapped
Code or [1..1] Code Cannot be mapped
Proprietary [1..1] Max35Text Cannot be mapped
Local Instrument [0..1] Component Cannot be mapped
Code or [1..1] Code Cannot be mapped
Proprietary [1..1] Max35Text Cannot be mapped
Category Purpose [0..1] Choice Component
Code or [1..1] Code
Codes CORT and INTC will be mapped to 23E of MT 103: Instruction Code CORT and INTC. Other codes will not be mapped.
Proprietary [1..1] Max35Text Cannot be mapped
Requested Execution Date [1..1] ISODate
Not mapped – but used to determine subfield 1 of 32A ( the interbank settlement date)
Pooling Adjustment Date [0..1] ISODate
Point-to-point element, so not transported in interbank chain
Debtor [1..1] Component +
Field 50 – Ordering Customer.
Please see translation rules PACS 008– MT 103.
Debtor Account [1..1] Component
Field 50 – Ordering Customer
Please see translation rules PACS 008 – MT 103.
Id [1..1] Component +
Field 50 – Ordering Customer
Please see translation rules PACS 008 – MT 103.
Type [0..1] Component Cannot be mapped
Code or [1..1] Code Cannot be mapped
Proprietary [1..1] Max35Text Cannot be mapped
Currency [0..1] Currency Code Cannot be mapped
Name [0..1] Max70Text Cannot be mapped
Debtor Agent [1..1] Component + Mapped to field 52 Ordering Institution
Please see translation rules PACS 008 – MT 103
Debtor Agent Account [0..1] Component + Not used in pain, so not mapped to MT 103
Ultimate Debtor [0..1] Component + Cannot be mapped
Charge Bearer [0..1] Code
Field 71A Charge Bearer : - DEBT > OUR
- SHAR > SHA - CRED > BEN - SLEV > SHA
Charges Account [0..1] Component +
Point-to-point element, not transported in interbank chain
Charges Account Agent [0..1] Component +
Point-to-point element, not transported in interbank chain
Credit Transfer Transaction [1..n] Component
Information
Payment Identification [1..1] Component
Instruction ID [0..1] Max35Text
Point-to-point element, not transported in interbank chain
End-to-end ID [1..1] Max35Text
Field 70 : /ROC/ (depending on presence of Remittance Identification in Related Remittance Information).
See the detailed translation rules for more information.
Payment Type Information [0..1] Component +
Should not be present on this level according to the Rules set out in this document. Can only be present on Payment Information level. For proposed mapping, see Payment Type Information component above.
Amount [1..1] Choice component
Instructed Amount or [1..1] Currency and Amount Field 33B Instructed Amount
Equivalent Amount [1..1] Component Field 33B Instructed Amount
Amount [1..1] Currency and Amount Field 33B Instructed Amount
Currency of Transfer [1..1] Currency Code Field 33B Instructed Amount
Exchange Rate Information [0..1] Component
Exchange Rate [0..1] BaseOneRate Field 36 Exchange Rate
Rate Type [0..1] Code Cannot be mapped
Contract Identification [0..1] Max35Text
Point-to-point element, not transported in interbank chain
Charge Bearer [0..1] Code
Should not be present on this level according to the Rules set out in this Document, but can only be present on Payment Information level. For proposed mapping, see Charge Bearer element above.
Cheque instruction [0..1] Component +
The entire component of Cheque Instruction is not mapped to the MT 103 : if cheque needs to be issued by debtor agent, the debtor agent will not generate an MT 103
Ultimate Debtor [0..1] Component + Cannot be mapped
Intermediary Agent 1 [0..1] Component +
Receiver of MT 103 (if receiver of the pain.001 message respects/has to respect the route set by the initiating party of the pain.001)
Intermediary Agent 1 Account [0..1] Component +
Not mapped (unless intermediary agent has multiple accounts at the Sender, and the Sender indicates in the MT 103 which account has been used for reimbursement (in field 53B).
Intermediary Agent 2 [0..1] Component +
Field 56a Intermediary (if no intermediary agent 3 is present)
See comment below for Intermediary agent 3.
Intermediary Agent 2 Account [0..1] Component +
Field 56a Intermediary, optional party identifier line. Only Account ID will be mapped. See comment below for Intermediary agent 3.
Intermediary Agent 3 [0..1] Component +
If 3 Intermediary agents are included in the ‘pain’ message, the sender of the MT 103 will have to make a choice which ones to include in the MT 103 (the MT 103 can only contain a receiver and 1 intermediary).
Creditor Agent [0..1] Component +
Mapped to field 57a Account With Institution (when different from the Receiver of MT 103)
Creditor Agent Account [0..1] Component +
Mapped to field 57a Account With Institution (optional account number line). Only Account ID will be mapped.
Creditor [0..1] Component +
Mapped to field 59a Beneficiary Customer. Please see translation rules PACS 008.001.01 – MT 103.
Creditor Account [0..1] Component +
Mapped to field 59a Beneficiary Customer (account number line).
Only the account ID will be mapped.
ID [1..1] Component
Mapped to field 59a Beneficiary Customer (account number line)
Type [0..1] Component Cannot be mapped
Code or [1..1] Code Cannot be mapped
Proprietary [1..1] Max35Text Cannot be mapped
Currency [0..1] Currency Code Cannot be mapped
Name [0..1] Max70Text Cannot be mapped
Ultimate Creditor [0..1] Component + Cannot be mapped
Instruction for Creditor Agent [0..n] Component
Code [0..1] Code
Field 23E Instruction Code. CHQB > will be mapped to CHQB. HOLD > will be mapped to HOLD PHOB > will be mapped to PHOB. TELB > will be mapped to TELB
Instruction Information [0..1] Max140Text
Field 23E Instruction Code/Additional information For details, please see mapping PACS 008– MT 103
Instruction for Debtor Agent [0..1] Max140Text
Point-to-point element, so not transported in interbank chain
Purpose [0..1] Component Cannot be mapped
Code or [1..1] Max3Text Cannot be mapped
Proprietary [1..1] Max140Text Cannot be mapped
Regulatory Reporting [0..10] Component Field 77B Regulatory Reporting
Debit Credit Reporting Indicator [0..1] Code Cannot be mapped
Authority [0..1] Component Cannot be mapped
Name [0..1] Max140Text Cannot be mapped
Country [0..1] ISOCountryCode Cannot be mapped
Details [0..1] Component Field 77B Regulatory Reporting
Type [0..1] Max35Text
Date [0..1] ISODate Cannot be mapped
Country [0..1] ISOCountryCode Cannot be mapped
Code [0..1] Code Cannot be mapped
Amount [0..1] CurrencyAndAmount Cannot be mapped
Information [0..1] Max35Text
Map to 3 lines of field 77B Regulatory reporting. For details, please see mappng PACS 008 – MT 103
Creditor [0..1] Component Cannot be mapped
Tax Id [0..1] Max35Text Cannot be mapped
RegistrationId [0..1] Max35Text Cannot be mapped
Tax Type [0..1] Max35Text Cannot be mapped
Debtor [0..1] Component Cannot be mapped
Tax Id [0..1] Max35Text Cannot be mapped
RegistrationId [0..1] Max35Text Cannot be mapped
Tax Type [0..1] Max35Text Cannot be mapped
Authorisation [0..1] Component Cannot be mapped
AdministrationZone [0..1] Max35Text Cannot be mapped
ReferenceNumber [0..1] Max140Text Cannot be mapped
Method [0..1] Max35Text Cannot be mapped
Total Taxable Base Amount [0..1] CurrencyAndAmount
Cannot be mapped
Total Tax Amount [0..1] CurrencyAndAmount Cannot be mapped
Date [0..1] ISODate Cannot be mapped
SequenceNumber [0..1] Number Cannot be mapped
Record [0..n] Component Cannot be mapped
Related Remittance Information [0..10] Component
Remittance Id [0..1] Max35Text
Map to Field 70, /ROC/, check detailed translation rules PACS 008 – MT 103
Remittance Location Method [0..1] Code Cannot be mapped
Remittance Location Electronic
Adress [0..1] Max2048Text
Cannot be mapped
Remittance Location Postal
Address [0..1] Component
Cannot be mapped
Name [1..1] Max140Text Cannot be mapped
Address [1..1] Component
Cannot be mapped
Remittance Information [0..1] Choice component
Unstructured [0..n] Max140Text
Mapped to field 70 Remittance Details – see detailed translation rules PACS 008- MT 103
Structured [0..n] Component Mapped to field 70 Remittance Details – see
detailed translation rules PACS 008- MT 103
Referred Document Information [0..n] Component
CodeOrProprietary Code or [1..1] Code Proprietary [1..1] Max35Text Issuer [0..1] Max35Text Number [0..1] Max35Text
Related Date [0..1] ISODate
Referred Document Amt [0..1] Choice Component
Due Payable Amtor [0..1] Currency And Amount
Discount Applied Amt
or [0..1] Currency And Amount
Credit Note Amt or [0..1] Currency And Amount
Tax Amount [0..1] CurrencyAndAmount
AdjustmentAmountAndReas
on [0..n] Component
RemittedAmount [0..1] CurrencyAndAmount
Creditor Reference Info [0..1] Component
Type [0..1] Component CodeOrProprietary [1..1] ChoiceComponent Code or [1..1] Code Proprietary [1..1] Max35Text Issuer [0..1] Max35Text Reference [0..1] Max35Text Invoicer [0..1] Component Invoicee [0..1] Component
6 Comparison MT - MX
This section contains a comparison of the SWIFT category 9 messages with the ISO 20022 Bank-to-Customer Account Reportingstandards.
This comparison is not intended to provide a detailed mapping, but rather is aimed at facilitating an understanding of the correspondence between the MT and MX message types.
The following table illustrates the equivalence :
Account Reporting
MT Message Types
MX Message Types
- MT 942 Interim Transaction Report - MT 941 Balance Report
- combination of MT 942 and MT 941
camt.052 (Bank-to-Customer Account Report)
- MT 940 Customer Statement - MT 950 Statement
camt.053 (Bank-to-Customer Statement)
- MT 900 Confirmation of Debit - MT 910 Confirmation of Credit - combination of MT 900 and MT 910
camt.054 (Bank-to-Customer Debit/Credit Notification)
The following comparisons are detailed :
• comparison of MX camt.052 BankToCustomerAccountReport with : − MT 942 Interim Transaction Report (section 5.1)
− MT 941 Balance Report (section 5.2)
• comparison of MX camt.053 BankToCustomerStatement with : − MT 940 Customer Statement (section 5.3)
− MT 950 Statement (section 5.4)
• comparison of MX camt.054 BankToCustomerDebitCreditNotification with : − MT 900 Notification of Debit (section 5.5)
− MT 910 Notification of Credit (section 5.6)
The specific translation rules for the above message types are published as part of the Standards User Handbook.
6.1 Comparison MT 942 to camt.052
The comparison below provides an analysis on the level of correspondence between MT 942 (Interim Transaction Report ) and the MX camt.052 (Bank-to-Customer Account Report). It does not represent the additional information that can be included in the MX message. Points of difference are highlighted in yellow. The target camt.052 fields designated in the Standards Translation Rules are highlighted in blue.
MT 942 MX camt.052
Status Tag Field Name Mult. Message Item Index
M 20 Transaction Reference Number 1..1 Report/Identification 2.1
O 21 Related Reference
(used to answer to a request for Statement message)
Not included
M 25 Account Identification 1..1 Report/Account 2.10
M 28C Statement Number/Sequence Number
0..1 Report/ElectronicSequenceNumber 2.2
0..1 Report/LegalSequenceNumber 2.3 0..1 GroupHeader/MessagePagination 1.4
M 34F Floor Limit Indicator Not required O 34F Floor Limit Indicator Not required
M 13D Date/Time Indication 1..1 Report/CreationDateTime 2.4
O 61 Statement Line (see below) 0..n Report/Entry (see below) 2.76
O 86 Information to Account Owner
Note: If field 86 is formatted according to a predefined structure, the information may be mapped to elements in the Report/Entry/Batch or
Report/Entry/TransactionDetails component, as appropriate. For example in field 86 using codes ‘/EREF/’ with End to End ID, ’/IREF/’ with Instruction ID, ’/PREF/’ with Payment Info ID, ‘/KREF/’ with generic customer reference. 0..1 Report/Entry/AdditionalEntryInformation or Report/Entry/EntryDetails/Batch or Report/Entry/EntryDetails/TransactionDetails 2.314 2.136 2.142
O 90D Number and Sum of Entries 0..1 Report/TransactionsSummary/TotalDebitEntrie s
2.52
O 90C Number and Sum of Entries 0..1 Report/TransactionsSummary/TotalCreditEntri es
2.49
Field 61 Statement line Entry component (2.65 and following)
Status Field Name Mult. Message Item Index
M Value Date (YYMMDD) 0..1 Entry/ValueDate 2.83
O Entry Date (MMDD) 0..1 Entry/BookingDate 2.82
M Debit/Credit Mark : Debit/Credit/
Reversal of Credit(debit entry)/ Reversal of Debit (credit entry)/ Expected Debit/Expected Credit
1..1 Entry/CreditDebitIndicator 2.79
0..1 Entry/ReversalIndicator 2.80
0..1 Entry/Status (booked/pending) 2.81
O Funds Code (3rd character of the currency code, if needed)
Not required
M Amount 1..1 Entry/Amount 2.78
M Transaction Type Identification Code 1..1 Entry/BankTransactionCode 2.91
M* Reference for the Account Owner
Note: Field 86 may be used in a structured form as an extension to field 61. For example in field 61 using code ‘KREF’ to indicate that the associated reference(s) are specified in field 86.
0..1* Entry/EntryDetails/Batch/
(when batch or aggregate booking): Message ID and/or
PaymentInfoID
2.137 2.138 Entry/EntryDetails/TransactionDetails/References (when booking for single transaction :
Instruction ID and/or Transaction ID and/or EndToEndID and/or MandateID and/or ClearingSystemReference and/or ChequeNumber and/or Proprietary 2.147 2.149 2.148 2.150 2.152 2.151 2.153 Entry/EntryDetails/TransactionDetails/RelatedRe mittanceInformation/RemittanceIdentification 2.250 Entry/EntryDetails/TransactionDetails/Remittance Information/Structured/CreditorReferenceInforma tion/CreditorReference 2.277
O Account Servicing Institution's Reference
0..1 Entry/AccountServicerReference 2.143
O Supplementary Details 0..1 Entry/AdditionalEntryInformation and/or Entry/EntryDetails/TransactionDetails/Additional
TransactionInformation
2.314
2.313
* Reference for Account Owner : even though all references in the MX message are optional, a rule in the Bank-to-Customer Cash Management Message Definition Report states that at least one reference must be present.
6.2 Comparison MT 941 to camt.052
The comparison below provides an analysis on the level of correspondence between MT 941 (Balance Report ) and the MX camt.052 (Bank-to-Customer Account Report). It does not represent the additional information that can be included in the MX message.
Points of difference are highlighted in yellow. The target camt.052 fields designated in the Standards Translation Rules are highlighted in blue.
MT 941 MX camt.052
Status Tag Field Name Mult. Message Item Index
M 20 Transaction Reference Number 1..1 Report/Identification 2.1
O 21 Related Reference :
(used to answer to a request for Statement message)
Not included
M 25 Account Identification 1..1 Report/Account 2.10
M 28 Statement Number/Sequence Number
0..1 Report/ElectronicSequenceNumber 2.2
0..1 Report/LegalSequenceNumber 2.3
0..1 GroupHeader/MessagePagination 1.4
O 13D Date/Time indication 1..1 Report/CreationDateTime 2.4
O 60F Opening Balance 0..1 Report/Balance (see below) 2.23
O 90D Number and Sum of Entries 0..1 Report/TransactionsSummary/TotalDebitEntries 2.52
O 90C Number and Sum of Entries 0..1 Report/TransactionsSummary/TotalCreditEntrie s
2.49
M 62F Closing Balance (Booked Funds)
0..1 Report/Balance (see below) 2.23
O 64 Closing Available Balance (Available Balance)
0..1 Report/Balance (see below) 2.23
O 65 Forward Available Balance 0..n Report/Balance (see below) 2.23
O 86 Information to Account Owner 0..1 Report/AdditionalReportInformation 2.330
Balance information in MT Balance information in MX
(Report/Balance/BalanceDetails (repetitive (2.28))
Status Field Name Mult. Message Item Index
O Opening Balance (option F) ***
Opening Booked Balance
(translation default balance type code “PRCD”)
2.25
M Closing Balance (Booked Funds) (option F) ***
Closing Booked Balance
(translation default balance type code “ITBD”)
2.25
O Closing Available Balance Closing Available Balance
(translation default balance type code “CLAV”)
2.25
O Forward Available Balance (repetitive)
Forward Available Balance
(translation default balance type code “FWAV”)
2.25
Balance subfields in MT Balance subfields in MX
Date 1..1 Date 2.36 Currency 1..1 Amount (typed by CurrencyAndAmount) 2.34 Amount 1..1 Amount (typed by CurrencyAndAmount) 2.34
*** in the MT 941, fields 60 and 62 can only be used with option F.
in the MT 940 (see comparison 5.3 below), field 60 and 62 can be used with option F or M. 60F = opening booked balance;
60M = interim opening booked balance;(to be used when there is more than one page belonging to the statement);
62F = final closing booked balance;
62M = interim closing booked balance. (to be used when there is more than one page belonging to the statement);
6.3 Comparison MT 940 to camt.053
The comparison below provides an analysis on the level of correspondence between MT 940 (Customer Statement) and the MX camt.053 (Bank-to-Customer Statement). It does not represent the additional information that can be included in the MX message.
Points of difference are highlighted in yellow. The target camt.053 fields designated in the Standards Translation Rules are highlighted in blue.
MT 940 MX camt.053
Status Tag Field Name Mult. Message Item Index
M 20 Transaction Reference Number 1..1 Statement/Identification 2.1
O 21 Related Reference
(used to answer to a request for Statement message)
Not included
M 25 Account Identification 1..1 Statement/Account 2.10
M 28C Statement Number/Sequence Number
0..1 Statement/ElectronicSequenceNumber 2.2
0..1 Statement/LegalSequenceNumber 2.3 0..1 GroupHeader/MessagePagination 1.4
M 60a Opening Balance (option F or M) *
1..1 Statement/Balance
(translation default balance type code “PRCD”)
2.23
O 61 Statement Line (see below) 0..n Statement/Entry (see below) 2.76 O 86 Information to Account Owner
Note: If field 86 is formatted according to a predefined structure, the information may be mapped to elements in the Report/Entry/Batch or
Report/Entry/TransactionDetails component, as appropriate. For example in field 86 using codes ‘/EREF/’ with End to End ID, ’/IREF/’ with Instruction ID, ’/PREF/’ with Payment Info ID, ‘/KREF/’ with generic customer reference. 0..1 Report/Entry/AdditionalEntryInformation or Report/Entry/EntryDetails/Batch or Report/Entry/EntryDetails/TransactionDetails 2.329 2.136 2.142
M 62a Closing Balance (option F or M) *
1..1 Statement/Balance
(translation default balance type code “CLBD”)
2.23
O 64 Closing Available Balance 0..1 Statement/Balance
(translation default balance type code “CLAV”)
2.23
O 65 Forward Available Balance (rep) 0..n Statement/Balance
(translation default balance type code “FWAV”)
2.23
Field 61 Statement line Entry component (2.65 and following)
Status Field Name Mult. Message Item Index
M Value Date (YYMMDD) 0..1 Entry/ValueDate 2.83
O Entry Date (MMDD) 0..1 Entry/BookingDate 2.82
M Debit/Credit Mark : Debit/Credit/
Reversal of Credit(debit entry)/ Reversal of Debit (credit entry)/ Expected Debit/Expected Credit
1..1 Entry/CreditDebitIndicator 2.79
0..1 Entry/ReversalIndicator 2.80
O Funds Code (3rd character of the currency code, if needed)
Not required
M Amount 1..1 Entry/Amount 2.78
M Transaction Type Identification Code 1..1 Entry/BankTransactionCode 2.91
M** Reference for the Account Owner
Note: Field 86 may be used in a structured form as an extension to field 61. For example in field 61 using code ‘KREF’ to indicate that the associated reference(s) are specified in field 86.
0..1** Entry/Batch/
(when batch or aggregate booking): Message ID and/or
PaymentInfoID
2.137 2.138 Entry/TransactionDetails/References
(when booking for single transaction : Instruction ID and/or Transaction ID and/or EndToEndID and/or MandateID and/or ClearingSystemReference and/or ChequeNumber and/or Proprietary 2.147 2.149 2.148 2.150 2.152 2.151 2.153 Entry/TransactionDetails/RelatedRemittanceInfor mation/RemittanceIdentification 2.228 Entry/TransactionDetails/RemittanceInformation/ Structured/CreditorReferenceInformation/Credito rReference 2.256
O Account Servicing Institution's Reference
0..1 Entry/AccountServicerReference 2.84
O Supplementary Details 0..1 Entry/AdditionalEntryInformation and
Entry/TransactionDetails/AdditionalTransaction Information
2.314
2.313
* For a further breakdown of the balance component, please refer to the comparison included with the MT 941 Balance Report, section 5.2.
** Reference for Account Owner : even though all references in the MX message are optional, a rule in the Bank-to-Customer Cash Management Message Definition Report states that at least one