CBPR Plus – Derived data mapping

- Guidance
SWIFT Standards Implementation
team

CBPR+ Derived Mapping

Guidance_ December 2023
 Introduction

The following document has been created to provide guidance to the industry on how to populate information from one messaging standard to the other
subsequent message (next leg of the processing).

Such guidance is described as “derived data mapping” and it is not equivalent to message “translation” for the following reason: some elements in the target
message can either be directly mapped from the source message when other can only be derived. i.e., the value that will be populated in some fields in the
CBPR+ Derived target message might be ONLY derived from back-office business logic associated with the equivalent elements in the source message.
Mapping Guidance_ For example, the “Interbank Settlement Date” in the pacs.008 is derived from the “Requested Execution Date” in the MT101. This date might not be identical
December 2023 if the settlement could not be completed at the date that was requested for example. Indeed, parameters such as the currency settlement type, cut off times
or even the customer insufficient balance have an influence on what will be populated in the pacs.008.

This document must be understood as a guidance to support the community during the coexistence period and is published to ensure common practice
across the industry.

To complement this document, we advised the reader to also refer to the useful documentation that is available (depending on the scenario):

- the Translation rules

- the CBPR plus UHB
- the FIN Reject and return guidelines (in the FIN UHB)

As a general recommendation, the CBPR plus group promotes that for every specific field used in the source and target message, the structured format is
the preferred option.

Important notes:
- this guidance does not cover the Reporting to Corporates (for more information on Bank-to-customer reporting, please refer to the work done by CGI)
- the mappings might include optional elements. Please note that not all optional elements have to be mapped (e.g. camt.053/054)
History Log
Version Date

1.0 May 2023

2.0 September 2023

 Derived Data Mapping Guidance documents (click on hyperlink)
Existing FIN MTs ISO 20022 equivalent Derived data mapping

MT 101 pain.001 MT 101 -> pacs.008

MT 103 pacs.008/pacs.008 STP MT103 -> pacs.008

MT 103 pacs.008/pacs.008 STP pacs.008 -> pacs.004
CBPR+ Derived pacs.008 -> pacs.002
Mapping Guidance_
MT103 -> pacs.004
December 2023
MT 103 pacs.008/pacs.008 STP pacs.008 (embedded MT 103) -> 103 RTN
MT 103 pacs.008/pacs.008 STP Generic MT -> camt.056
Generic pacs -> camt.056
MT 103 pacs.008/pacs.008 STP Generic pacs -> MT n92
Generic pacs -> MT n95
MT103 pacs.008/pacs.008 STP MT103 -> camt.053/054 (Creditor Agent to Creditor)
MT103 -> camt.053/054 (Debtor Agent to Debtor)
MT103 -> camt.053/054 (sent by Intermediary)

MT104 pacs.003 MT104 to pacs.003 new

 Derived Data Mapping Guidance documents (click on hyperlink)

Existing FIN MTs ISO 20022 equivalent Derived data mapping

MT 202/202 COV pacs.009 MT202 to pacs.009

MT202C to pacs.009
MT 202/202 COV pacs.009 pacs.009 -> pacs.004
CBPR+ Derived
Mapping Guidance_ MT 202/202 COV pacs.009 MT 202/202 COV -> pacs.004
December 2023
MT 202/202 COV pacs.009 pacs.009 (embedded MT 202/202 COV)-> MT 202 RTN

MT 202/202 COV pacs.009 Generic MT -> camt.056

Generic pacs -> camt.056

MT 202/202 COV pacs.009 Generic pacs ->MTn92

Generic pacs -> MT n95

MT202 Pacs.009 MT202/202COV -> camt.053

MT202/202COV -> camt.054

MT204 Pacs.010 pacs.010 to MT204

pacs.010 (CCP version) to pacs.009 new
 Derived Data Mapping Guidance documents (click on hyperlink)
Existing FIN MTs ISO 20022 equivalent Derived data mapping

MT 900 camt.054 pacs.008 -> camt.054

MT 910 MT103 -> camt.054 (Creditor Agent to Creditor)
MT103 -> camt.054 (Debtor Agent to Debtor)
MT103 -> camt.054 (sent by Intermediary)

pacs.009 -> camt.054 (Creditor Agent to Creditor)

pacs.009 -> camt.054 (Debtor Agent to Debtor)
CBPR+ Derived
MT202/202COV -> camt.053/camt.054
Mapping Guidance_
December 2023 pacs.004 -> camt.054 (Creditor Agent to Creditor)
pacs.004 -> camt.054 (Debtor Agent to Debtor)

MT103 /RETN/ -> camt.054

MT202 /RETN/ -> camt.054
Pacs.008 -> MT900/910
Pacs.009 -> MT900/910
Pacs.004 -> MT900/910
MT 940 camt.053 pacs.008 -> camt.053
MT 950 MT103 -> camt.053 (Creditor Agent to Creditor)
MT103 -> camt.053 (Debtor Agent to Debtor)
MT103 -> camt.053 (sent by Intermediary)

pacs.009 -> camt.053 (Creditor Agent to Creditor)

pacs.009 -> camt.053 (Debtor Agent to Debtor)
MT202/202COV -> camt.053/camt.054

pacs.004 -> camt.053 (Creditor Agent to Creditor)

pacs.004 -> camt.053 (Debtor Agent to Debtor)

MT103/RETN/ -> camt.053

MT202 /RETN/ -> camt.053
Pacs.008 -> MT940/950
Pacs.009 -> MT940/950
Pacs.004 -> MT940/950

Note: No specific derived data mapping to MT942 has been done - The main difference between the MT940/950 and the MT942 is that the
MT942 does not have any balance fields, otherwise the data content should be the same as a statement.
 Derived Data Mapping Guidance documents
(click on hyperlink)

Existing FIN MTs ISO 20022 equivalent Derived data mapping

MT n91 camt.106 Pacs.008 to MT 191

Camt.106 to pacs.009 new

MT n92 camt.056 Camt.056 to camt.029

camt.057 Camt.056 to MT n96
CBPR+ Derived Camt.057 to MT 292
Mapping Guidance_ MT920 camt.060 Camt.060 to MT920
December 2023

Note: No specific derived data mapping to MT942 has been done - The main difference between the MT940/950 and the MT942 is that the
MT942 does not have any balance fields, otherwise the data content should be the same as a statement.
 Derived Data Mapping Guidance –
Payment Initiation
CBPR+ Derived
Mapping Guidance_
December 2023
 MT 101 high level derived data mapping to pacs.008: Use case description

CBPR+ Derived
Mapping Guidance_
December 2023

The “Request for Transfer” message is sent to the Debtor Agent. It is used to request movement of funds from the
debtor account to a creditor. The Debtor Agent is ISO enabled and will send a pacs.008
 MT 101 high level derived data mapping to
pacs.008
MT ISO

MT Field Name & (Tag option) ISO 20022 message element

CBPR+ Derived
Sequence A – General Information:
Mapping Guidance_ ➢ Credit Transfer Transaction Information / Initiating Party
➢ Sender’s Reference (Field 20) NOT MAPPED ➢
December 2023 ➢ Customer Specified Reference (Field 21R) NOT MAPPED
Credit Transfer Transaction Information / Debtor (& Debtor Account)
➢ Credit Transfer Transaction Information / Debtor Agent (& Debtor Agent Account)
➢ Message Index/Total (Field 28D) NOT MAPPED
➢ Instructing Party (Field 50 C or L) ➢ Interbank Settlement Date *
➢ Ordering Customer (Field 50 F, G or H)
➢ Account Servicing Institution (Field 52 A or C)
➢ Sender Institution NOT MAPPED
➢ Requested Execution Date (Field 30)* ➢ Credit Transfer Transaction Information / Remittance Information (optional where should
➢ Authorisation NOT MAPPED there be available space)

Sequence B – General Information: ➢ Credit Transfer Transaction Information / Category Purpose (for codes CORT or INTC)
➢ Transaction Reference (Field 21) otherwise Credit Transfer Transaction Information / Instruction For Creditor Agent
➢ F/X Deal Reference (Field 21F) NOT MAPPED ➢ Credit Transfer Transaction Information / Interbank Settlement Amount *
➢ Instruction Code (Field 23E) ➢ Credit Transfer Transaction Information / Debtor (& Debtor Account)
➢ Credit Transfer Transaction Information / Debtor Agent (& Debtor Agent Account)
➢ Currency/Transaction Amount (Field 32B) * ➢ Credit Transfer Transaction Information / Intermediary Agent 1 (& Intermediary Agent 1
➢ Ordering Customer (Field 50 F, G or H) Account)
➢ Account Servicing Institution (Field 52 A or C) ➢ Credit Transfer Transaction Information / Creditor Agent
➢ Intermediary (Field 56 A, C or D) ➢ Credit Transfer Transaction Information / Creditor (& Creditor Account)
➢ Account With Institution (Field 57 A, C or D) ➢ Credit Transfer Transaction Information / Payment Identification / End to End Id (for code
➢ Beneficiary (Field 59 no letter, A or F) ROC) otherwise Credit Transfer Transaction Information / Remittance Information
➢ Remittance Information (Field 70) ➢ Credit Transfer Transaction Information / Regulatory Reporting
➢ Credit Transfer Transaction Information / Instructed Amount *
➢ Regulatory Reporting (Field 77B) ➢ Credit Transfer Transaction Information / Charge Bearer
➢ Currency/Original Amount (Field 33B)
➢ Details of Charges (Field 71A) ➢ Credit Transfer Transaction Information / Exchange Rate
➢ Charge Account (Field 25A) ➢ Credit Transfer Transaction Information/ Payment Identification / If available, UETR must be
➢ Exchange Rate (Field 36) mapped from the header of the MT101

Note - various other elements are mandatory in the pacs.008 which are not derived from the payment initiation including for example Message identification, Creation Date Time, Settlement Method.. often these data
elements and potentially other optional elements will be generated by the bank application when creating the payment message.
* Where interbank settlement amount does not equal the field 32 B then the Instructed Amount should be populated in the pacs.008
* May not have a direct relationship but value in source message received will influence the value in target message
* Only applied where fields 33B and 36 are present (i.e., a foreign exchange transaction has been pre-agreed)
 Derived Data Mapping Guidance –
Payment Instruction
CBPR+ Derived
Mapping Guidance_
December 2023
 MT 103 high level derived data mapping to pacs.008: Use case description

CBPR+ Derived
Mapping Guidance_
December 2023

The MT103 is sent from Agent A to Agent B. Agent B is ISO enabled and will send the pacs.008 to the next Agent C in the chain having converted
the MT 103 into a pacs.008 either in their payment engine, middleware or in their SWIFT interfaces.
This pacs.008 has been created using the translation rules (here) only for the appropriate attributes that can be derived from the incoming MT103.
c
Please also refer to the CBPR plus UHB that describes the change of Agent role at different stages of the payment transaction life cycle (CBPR
plus UHB – section “pacs.008 FI to FI Customer Credit Transfer – Previous Instructing Agents versus Intermediary Agents”)
 MT 202 high level derived data mapping to pacs.009: Use case description

Debtor /Instructing Agent Instructed Agent Creditor Agent Creditor

CBPR+ Derived
Mapping Guidance_
December 2023 A B C D

MT202

Pacs.009

This represents a transformation that occurred in the application of Agent B

The MT202 is sent from Agent A to Agent B. Agent B is ISO enabled and will send the pacs.009 to the next Agent C in the chain having converted
the MT 202 into a pacs.009 either in their payment engine, middleware or in their SWIFT interfaces. This pacs.009 has been created using the
translation rules (here) only for the appropriate attributes that can be derived from the incoming MT202.

Please also refer to the CBPR plus UHB that describes the change of Agent role at different stages of the payment transaction life cycle (CBPR
plus UHB – section “pacs.008 FI to FI Customer Credit Transfer – Previous Instructing Agents versus Intermediary Agents”)
 MT 202 COV high level derived data mapping to pacs.009COV: Use case
description

A B C D
CBPR+ Derived
Mapping Guidance_
December 2023

Debtor /Instructing Agent Debtor Agent/ Instructed Agent Creditor Agent Creditor

MT202COV

Pacs.009COV

This represents a transformation that occurred in the application of Agent B

The MT202 COV is sent from Agent A to Agent B. Agent B is ISO enabled and will send the pacs.009 COV to the next Agent C in the chain
having converted the MT 202 COV into a pacs.009COV either in their payment engine, middleware or in their SWIFT interfaces. This pacs.009
has been created using the translation rules (here) only for the appropriate attributes that can be derived from the incoming MT202COV.

Please also refer to the CBPR plus UHB that describes the change of Agent role at different stages of the payment transaction life cycle (CBPR
plus UHB – section “pacs.008 FI to FI Customer Credit Transfer – Previous Instructing Agents versus Intermediary Agents”)
 Derived Data Mapping Guidance –
Payment Return and Payment
CBPR+ Derived
Rejected
Mapping Guidance_
December 2023
 Pacs.008 high level derived data mapping to pacs.004: Use case description -
Payment completed

Debtor Debtor Agent/Instructing Agent Instructed Agent/Creditor Agent Creditor

CBPR+ Derived
Mapping Guidance_ A B
December 2023

INGA
pacs.008 Camt.053
Creditor
does not
recognise
Instructed Agent/Creditor Agent Instructing Agent/Debtor Agent
that credit
INDA
pacs.004

Return &
Reason

The FI to FI Customer Credit Transfer is sent from Agent A to Agent B (and settlement is completed – Settlement Method = INGA). Agent B
will generate a pacs.004 to return the funds.
Derived data mapping principles – For more information on the Return Chain, pls check the section in the UHB

The initiator of the Payment Return becomes the mandatory Debtor in the Return Chain element - the Debtor is the party that owes the money to the party the return is intended for, ie the Creditor. Both Debtor
and Creditor are mandatory in the Return chain and they can be identified as a Party or an Agent.
 Pacs.008 High level derived data mapping to pacs.004 - Payment completed

ISO ISO

ISO 20022 message element ISO 20022 message element

➢ Group Header/ Message Identification ➢ Transaction Information/Original Group Information/Original Message Identification
CBPR+ Derived ➢ Group Header/ Settlement Information/ Settlement Method * ➢ Group Header/ Settlement Information/ Settlement Method *
Mapping Guidance_ ➢ Business Application Header/Message Definition Identifier/pacs.008.001.08* ➢ Transaction Information/Original Group Information/Original Message Name
December 2023 ➢ Credit Transfer Transaction Information/Payment Identification/Instruction Identification/pacs.008.001.08
Identification ➢ Transaction Information/Original Instruction Identification
➢ Credit Transfer Transaction Information/Payment Identification/E2E Identification ➢ Transaction Information/Original E2E identification
➢ Credit Transfer Transaction Information/Payment Identification/UETR ➢ Transaction Information/Original UETR
➢ Credit Transfer Transaction Information / Interbank Settlement Amount ➢ Transaction Information/ Original Interbank Settlement Amount
➢ Credit Transfer Transaction Information / Instructed Agent ➢ Transaction Information/ Instructing Agent
➢ Credit Transfer Transaction Information / Instructing Agent ➢ Transaction Information/ Instructed Agent
➢ Credit Transfer Transaction Information / Debtor ➢ Transaction Information/ Return Chain/Creditor 1
➢ Credit Transfer Transaction Information / Debtor Agent ➢ Transaction Information/ Return Chain/Creditor Agent Provided the payment
➢ Credit Transfer Transaction Information / Creditor Agent ➢ Transaction Information/ Return Chain/Debtor Agent reaches the Creditor
➢ Credit Transfer Transaction Information / Creditor ➢ Transaction Information/ Return Chain/Debtor 1 Agent and is not returned
➢ Transaction Information/Original Transaction Reference2 earlier in the chain

* The “Settlement Method” is mandatory in both pacs.008 and pacs.004

Message Settlement Method

Type

Pacs.008 INDA INGA

Derived data mapping principles – For more information on the Return Chain, pls check the section in the UHB
1 The initiator of the Payment Return becomes the mandatory Debtor in the Return Chain element - the Debtor is the party that owes the money to the party the Pacs.004 INGA INDA
return is intended for, ie the Creditor. Both Debtor and Creditor are mandatory in the Return chain and they can be identified as a Party or an Agent.
2 This section should be used if the Return chain is not identical to the Original payment transaction, otherwise it might be optionally used

* The Message Definition Identifier in the BAH is not validated, however, the Original Message Name Identification in pacs.004 is validated.

Note - various other elements are mandatory in the pacs.004 which are not derived from the payment instruction including for example Return Identification, Creation Date Time, Returned
Interbank Amount, Return Reason Information .. often these data elements and potentially other optional elements will be generated by the bank application when creating the return
message
 Pacs.008 high level derived data mapping to pacs.004: Use case description –
Payment not completed

Debtor Debtor Agent/Instructing Agent Instructed Agent Creditor Agent Creditor

CBPR+ Derived A B C
Mapping Guidance_
December 2023

INGA
pacs.008

Creditor Instructed Agent/Creditor Agent Instructing Agent/Debtor

INDA
pacs.004

Return &
Reason

The FI to FI Customer Credit Transfer is sent from Agent A to Agent B (and settlement is completed – Settlement
Method = INGA). Agent B (Intermediary in the chain) will generate a pacs.004 to return the funds.

Please also refer to the CBPR plus UHB that describes the change of Agent role at different stages of the payment
transaction life cycle (CBPR plus UHB – section “pacs.008 FI to FI Customer Credit Transfer – Previous Instructing Agents
versus Intermediary Agents”)
 Pacs.008 High level derived data mapping to pacs.004 - Payment not completed

ISO ISO

ISO 20022 message element ISO 20022 message element

➢ Group Header/ Message Identification ➢ Transaction Information/Original Group Information/Original Message Identification
CBPR+ Derived ➢ Group Header/ Settlement Information/ Settlement Method * ➢ Group Header/ Settlement Information/ Settlement Method *
Mapping Guidance_ ➢ Business Application Header/Message Definition Identifier* ➢ Transaction Information/Original Group Information/Original Message Name
December 2023 ➢ Credit Transfer Transaction Information/Payment Identification/Instruction Identification/pacs.008.001.08
Identification ➢ Transaction Information/Original Instruction Identification
➢ Credit Transfer Transaction Information/Payment Identification/E2E ➢ Transaction Information/Original E2E identification
Identification ➢ Transaction Information/Original UETR
➢ Credit Transfer Transaction Information/Payment Identification/UETR ➢ Transaction Information/ Original Interbank Settlement Amount
➢ Credit Transfer Transaction Information / Interbank Settlement Amount ➢ Transaction Information/ Instructed Agent
➢ Credit Transfer Transaction Information/Instructing Agent ➢ Transaction Information/ Instructing Agent AND Transaction Information/Return
➢ Credit Transfer Transaction Information/Instructed Agent Chain/Debtor

➢ Credit Transfer Transaction Information / Debtor ➢ Transaction Information/ Return Chain/Creditor 1

➢ Credit Transfer Transaction Information / Debtor Agent ➢ Transaction Information/ Return Chain/Creditor Agent
➢ Credit Transfer Transaction Information / Creditor Agent
➢ Credit Transfer Transaction Information / Creditor
2
➢ Transaction Information/Original Transaction Reference
* The “Settlement Method” is mandatory in both pacs.008 and pacs.004

Message Settlement Method

Type

Pacs.008 INDA INGA

Derived data mapping principles – For more information on the Return Chain, pls check the section in the UHB
1 The initiator of the Payment Return becomes the mandatory Debtor in the Return Chain element - the Debtor is the party that owes the money to the party the Pacs.004 INGA INDA
return is intended for, ie the Creditor. Both Debtor and Creditor are mandatory in the Return chain and they can be identified as a Party or an Agent.
2 This section should be used if the Return chain is not identical to the Original payment transaction, otherwise it might be optionally used
* The Message Definition Identifier in the BAH is not validated, however, the Original Message Name Identification in pacs.004 is validated.
Note - various other elements are mandatory in the pacs.004 which are not derived from the payment instruction including for example Return Identification, Creation Date
Time, Returned Interbank Amount .. often these data elements and potentially other optional elements will be generated by the bank application when creating the return
message
 Pacs.009 high level derived data mapping to pacs.004: Payment completed

Debtor /Instructing Agent Instructed Agent/Creditor

CBPR+ Derived
Mapping Guidance_
A B
December 2023

pacs.009

Creditor/ Instructed Agent Instructing Agent/Debtor

INDA
pacs.004

Return &
Reason

The FI Credit Transfer is sent from Agent A to Agent B (and settlement is completed – Settlement Method = INGA). Agent B
will generate a pacs.004 to return the funds.
Mapping principles – For more information on the Return Chain and the possible use cases, pls check the section in the UHB

The initiator of the Payment Return becomes the mandatory Debtor in the Return Chain element - the Debtor is the party that owes the money to the party the return is intended for, ie the Creditor. Both Debtor and
Creditor are mandatory in the Return chain and they can be identified as a Party or an Agent.
 Pacs.009 High level derived data mapping to pacs.004 - Payment completed

ISO ISO

ISO 20022 message element ISO 20022 message element

➢ Group Header/ Message Identification ➢ Transaction Information/Original Group Information/Original Message

CBPR+ Derived ➢ Group Header/ Settlement Information/ Settlement Method* Identification
➢ Group Header/ Settlement Information/ Settlement Method/*
Mapping Guidance_ ➢ Business Application Header/Message Definition Identifier*
December 2023 ➢ Credit Transfer Transaction Information/Payment Identification/Instruction ➢ Transaction Information/Original Group Information/Original Message Name
Identification Identification/pacs.009.001.08
➢ Credit Transfer Transaction Information/Payment Identification/E2E ➢ Transaction Information/Original Instruction Identification
Identification ➢ Transaction Information/Original E2E identification
➢ Credit Transfer Transaction Information/Payment Identification/UETR ➢ Transaction Information/Original UETR
➢ Credit Transfer Transaction Information / Interbank Settlement Amount ➢ Transaction Information/ Original Interbank Settlement Amount
➢ Credit Transfer Transaction Information / Instructed Agent ➢ Transaction Information/ Instructing Agent 1
➢ Credit Transfer Transaction Information / Debtor ➢ Transaction Information/ Return Chain/Creditor/Agent

➢ Credit Transfer Transaction Information / Instructing Agent ➢ Transaction Information/ Instructed Agent 1
➢ Credit Transfer Transaction Information / Creditor ➢ Transaction Information/ Return Chain/Debtor/Agent

➢ Transaction Information/Return Reason information/ Reason

➢ Transaction Information/Original Transaction Reference 2

* The “Settlement Method” is mandatory in both pacs.009 and pacs.004

Message Settlement Method

Type

Pacs.009 INDA INGA

Mapping principles – For more information on the Return Chain, pls check the section in the UHB
1 The initiator of the Payment Return becomes the mandatory Debtor in the Return Chain element - the Debtor is the party that owes the money to the party the
return is intended for, ie the Creditor. Both Debtor and Creditor are mandatory in the Return chain and they can be identified as an Agent only. Pacs.004 INGA INDA
2 This section should be used if the Return chain is not identical to the Original payment transaction, otherwise it might be optionally used

* The Message Definition Identifier in the BAH is not validated, however, the Original Message Name Identification in pacs.004

Note - various other elements are mandatory in the pacs.004 which are not derived from the payment instruction including for example Return Identification, Creation Date Time, Returned
Interbank Amount .. often these derived data elements and potentially other optional elements will be generated by the bank application when creating the return message
Any reference present in the Original message should be populated in the Return message (for example the “Transaction Identification”, if present in pacs.009 should be populated in the
“Original Transaction Identification” of the pacs.004.
 Pacs.009 high level derived data mapping to pacs.004: Payment not completed

Debtor /Instructing Agent Debtor Agent/ Instructed Creditor Agent Creditor

Agent

A B C D
CBPR+ Derived
Mapping Guidance_
December 2023

INGA
Pacs.009

Creditor/ Instructed Agent Instructing Agent/Debtor

pacs.004

Return &
Reason

The FI Credit Transfer is sent from Agent A to Agent B (and settlement is completed – Settlement Method = INGA). Agent B
(Intermediary in the chain) will generate a pacs.004 to return the funds.
Mapping principles – For more information on the Return Chain and the possible use cases, pls check the section in the UHB

The initiator of the Payment Return becomes the mandatory Debtor in the Return Chain element - the Debtor is the party that owes the money to the party the return is intended for, ie the Creditor. Both Debtor and
Creditor are mandatory in the Return chain and they can be identified as a Party or an Agent.
 Pacs.009 High level derived data mapping to pacs.004: Payment not completed

ISO ISO

ISO 20022 message element ISO 20022 message element

➢ Group Header/ Message Identification ➢ Transaction Information/Original Group Information/Original Message

CBPR+ Derived ➢ Group Header/ Settlement Information/ Settlement Method * Identification
➢ Group Header/ Settlement Information/ Settlement Method *
Mapping Guidance_ ➢ Business Application Header/Message Definition Identifier *
December 2023 ➢ Credit Transfer Transaction Information/Payment Identification/Instruction ➢ Transaction Information/Original Group Information/Original Message Name
Identification Identification/pacs.009.001.08
➢ Credit Transfer Transaction Information/Payment Identification/E2E ➢ Transaction Information/Original Instruction Identification
Identification ➢ Transaction Information/Original E2E identification
➢ Credit Transfer Transaction Information/Payment Identification/UETR ➢ Transaction Information/Original UETR
➢ Credit Transfer Transaction Information / Interbank Settlement Amount ➢ Transaction Information/ Original Interbank Settlement Amount
1
➢ Credit Transfer Transaction Information / Instructing Agent = Debtor ➢ Transaction Information/ Instructed Agent
➢ Transaction Information/ Return Chain/ Creditor
1
➢ Credit Transfer Transaction Information / Instructed Agent = Debtor Agent ➢ Transaction Information/ Instructing Agent
➢ Transaction Information/ Return Chain/Debtor

➢ Credit Transfer Transaction Information / Creditor Agent

➢ Credit Transfer Transaction Information / Creditor NOT MAPPED ➢ Transaction Information/Return Reason information/ Reason
➢ Transaction Information/Original Transaction Reference 2
* The “Settlement Method” is mandatory in both pacs.009 and pacs.004

Message Settlement Method

Type

Mapping principles – For more information on the Return Chain, pls check the section in the UHB Pacs.009 INDA INGA
1 The initiator of the Payment Return becomes the mandatory Debtor in the Return Chain element - the Debtor is the party that owes the money to the party the
return is intended for, ie the Creditor. Both Debtor and Creditor are mandatory in the Return chain and they can be identified as an Agent only.
Pacs.004 INGA INDA
2 This section should be used if the Return chain is not identical to the Original payment transaction, otherwise it might be optionally used

* The Message Definition Identifier in the BAH is not validated, however, the Original Message Name Identification in pacs.004

Note - various other elements are mandatory in the pacs.004 which are not derived from the payment instruction including for example Return Identification, Creation Date Time, Returned
Interbank Amount .. often these derived data elements and potentially other optional elements will be generated by the bank application when creating the return message
Any reference present in the Original message should be populated in the Return message (for example the “Transaction Identification”, if present in pacs.009 should be populated in the
“Original Transaction Identification” of the pacs.004.
 Pacs.008 high level derived data mapping to pacs.002: Use case description –
Payment not completed
Debtor Debtor Agent/Instructing Agent Instructed Agent

A B
CBPR+ Derived
Mapping Guidance_
December 2023
INDA
pacs.008

Instructed Agent Instructing Agent

pacs.002

Reject &
Reason

The FI to FI Customer Credit Transfer is sent from Agent A to Agent B (and settlement is not completed – Settlement
Method = INDA). Agent B can’t settle and will generate a pacs.002 to reject the payment.
U
Note: If instead of PACS002 a MT199/299 must be sent, pls refer to the “Payments Reject/Return Guidelines” in FIN UHB (here)
 Pacs.008 High level derived data mapping to pacs.002

CBPR+ Derived
Mapping Guidance_
December 2023 ISO ISO

ISO 20022 message element ISO 20022 message element

➢ Group Header/ Message Identification ➢ Transaction Information And Status/Original Group Information/Original
➢ Group Header/ Settlement Information/ Settlement Method Message Identification

➢ Business Application Header/Message Definition Identifier 1

➢ Credit Transfer Transaction Information/Payment Identification/Instruction ➢ Transaction Information And Status/Original Group Information/Original
Identification Message Name Identification/pacs.008.001.08
➢ Credit Transfer Transaction Information/Payment Identification/E2E ➢ Transaction Information And Status/Original Instruction Identification
Identification ➢ Transaction Information And Status/Original E2E identification
➢ Credit Transfer Transaction Information/Payment Identification/UETR ➢ Transaction Information And Status/Original UETR
➢ Credit Transfer Transaction Information / Interbank Settlement Amount
➢ Credit Transfer Transaction Information/Instructing Agent ➢ Transaction Information And Status/Instructed Agent
➢ Credit Transfer Transaction Information/Instructed Agent ➢ Transaction Information And Status/Instructing Agent

➢ Transaction Information And Status/Transaction Status/RJCT

➢ Transaction Information And Status/Status Reason Information/Reason

Note - various other elements are mandatory in the pacs.002 which are not derived from the payment instruction including for example Message Identification, Creation Date Time, often these
data elements and potentially other optional elements will be generated by the bank application when creating the reject message
 MT103 high level derived data mapping to pacs.004 : Use case description

Ordering Sender/Ordering Institution Receiver/Account with Institution Beneficiary Customer

customer

A B
CBPR+ Derived
Mapping Guidance_
December 2023
MT103 MT 940

Creditor Instructed Agent/Creditor Agent Instructing Agent/Debtor Agent Debtor

pacs.004

Return &
Reason

The MT103 is sent from servicing Agent A to account owner Agent B before the ISO migration (settlement completed).
Post migration, Agent B can’t apply the funds and generates a pacs.004 to return the funds.

Derived data mapping principles – For more information on the Return Chain, pls check the section in the UHB

The initiator of the Payment Return becomes the mandatory Debtor in the Return Chain element - the Debtor is the party that owes the money to the party the return is intended for, ie the Creditor. Both Debtor
and Creditor are mandatory in the Return chain and they can be identified as a Party or an Agent.
 MT 103 high level derived data mapping to pacs.004

MT ISO

MT Field Name & (Tag option) ISO 20022 message element

CBPR+ Derived
➢ Sender’s Reference (Field 20) ➢
Mapping Guidance_ ➢ Time Indication (Field 13C) ➢
Transaction Information/Original GroupInformation/Original Message Identification OR
Transaction Information/ Original Instruction Identification
December 2023 ➢ Bank Operation code (Field 23B) ➢ Transaction Information/Original GroupInformation/Original Message Name Identification/MT103
➢ NOT MAPPED
Instruction Code (Field 23E) ➢ Transaction Information/Original UETR must be mapped from the header of the MT103
➢ Transaction type Code (Field 26T)

➢ Value Date/Currency/Interbank Settled Amount (Field 32A) ➢ Transaction Information/ Original Interbank Settlement Amount
➢ Transaction Information/ Original Interbank Settlement Date

➢ Currency/Instructed Amount (Field 33B) ➢ Transaction Information/ Original Transaction Reference/Amount/InstructedAmount

➢ Exchange Rate (Field 36)
➢ Ordering Customer (Field 50 A, K or K) ➢ Transaction Information/ Return Chain/Creditor 1
➢ Sending Institution (Field 51A)
➢ Ordering Institution (Field 52 A or D) or Message Sender if F52 not ➢ Transaction Information/ Return Chain/Creditor Agent
present
➢ Sender’s Correspondent (Field 53 A or B or D)
➢ Receiver’s Correspondent (Field 54 A or B or D) NOT MAPPED
➢ Third Reimbursement Institution (Field 55 A or B or D)
➢ 1
Intermediary Institution (Field 56 A or C or D) ➢ Transaction Information/Return Chain/Debtor Agent Provided the payment reaches the Creditor Agent and is
➢ Account With Institution (Field 57 A or B or C or D) ➢ Transaction Information/Return Chain/Debtor not returned earlier in the chain
➢ Beneficiary Customer (Field 59 no letter, A or F)
➢ Transaction Information/Original End to End identification (for code ROC) otherwise Transaction
➢ Remittance Information (Field 70) Information/Original Transaction Reference/Remittance Information

➢ Details of Charges (Field 71A)

➢ Sender’s Charges (Field 71F)
➢ Transaction Information / Original Transaction Reference 2
➢ Receiver’s Charges (Field 71G) NOT MAPPED
➢ Sender To Receiver Information (Field 72)
➢ Regulatory Reporting (Field 77B)
Derived data mapping principles: For more information on the Return Chain, pls check the section in the UHB
1 The initiator of the Payment Return becomes the mandatory Debtor in the Return Chain element - the Debtor is the party that owes the money to the party the
return is intended for, ie the Creditor. Both Debtor and Creditor are mandatory in the Return chain and they can be identified as a Party or an Agent.
2 This section should be used if the Return chain is not identical to the Original payment transaction, otherwise it might be optionally used
Note - various other elements are mandatory in the pacs.004 which are not derived from the payment instruction including for example Return Identification, Creation Date Time, Returned Interbank
Amount, Return Reason information.. often these data elements and potentially other optional elements will be generated by the bank application when creating the return message
 MT202/202COV High level derived data mapping to pacs.004 : Use case description

Remarks:
A B C 1) In both scenario, the pacs.004 will
CBPR+ Derived be identical since the pacs.004
Mapping Guidance_ MT202 does not allow reporting
December 2023 Return & underlying information present in
Scenario 1 pacs.004 Reason the original MT 202 COV

MT103 2) The above is true if Agent B has

the role of an intermediary in the
MT202COV cover Chain. The derived data
Scenario 2 mapping would thus be different
Return & depending on the role an Agent
pacs.004
Reason plays in the cover chain

Scenario 1:
a) The MT202 is sent from Agent A to Agent B before the ISO implementation (settlement completed).
Post ISO implementation, Agent B (ISO enabled) can’t apply the funds and generates a pacs.004 to return the funds
OR
b) Post implementation, Agent A is a MT user and B is ISO enabled
Scenario 2:
a) Agent A sends the MT 103 to Agent C and sends an MT 202 COV to intermediary Agent B before the ISO implementation (settlement completed). Post ISO implementation,
Agent B (ISO enabled) can’t apply the funds and generates a pacs.004 to return the funds
OR
b) Post implementation, Agent A is an MT user and Agent B is ISO enabled
 MT 202 High level derived data mapping to pacs.004 (derived data mapping
identical for MT202 or MT 202COV)

MT ISO

MT Field Name & (Tag option) ISO 20022 message element

CBPR+ Derived
➢
Mapping Guidance_ ➢ Transaction Reference Number (Field 20) ➢
Transaction Information/Original Group Information/Original Message Identification *
Transaction Information/ Original Instruction Identification *
December 2023 ➢ Transaction Information/Original Group Information/Original Message Name Identification/MT202 *
➢ Related Reference Field 21 ➢ Transaction Information/Original UETR must be mapped from the header of the MT202/202COV *
➢ Transaction Information/ Original E2E id*

➢ Transaction Information/ Original Interbank Settlement Amount *

➢ Value Date/Currency/Interbank Settled Amount (Field 32A) ➢ Transaction Information/ Original Interbank Settlement Date *

➢ Ordering Institution (Field 52 A or D) or Message Sender if F52 not

present ➢ Transaction Information/ Return Chain/Creditor/Agent
➢ Sender’s Correspondent (Field 53 A or B or D)
➢ Receiver’s Correspondent (Field 54 A or B or D) NOT MAPPED
➢ Intermediary (Field 56 A or D)
➢ Transaction Information/Return Chain/Debtor Agent 1 Provided the payment reaches the Creditor Agent and is
➢ Account With Institution (Field 57 A or B or D) ➢ Transaction Information/Return Chain/Debtor/Agent 1 not returned earlier in the chain
➢ Beneficiary Institution (Field 58 A or D)
➢ Transaction Information/Original Transaction Reference/Remittance Information (only for code /BNF/
➢ Sender To Receiver Information (Field 72) if present)

➢ Transaction Information/ Return Reason Information/ Reason

➢ Transaction Information / Original Transaction Reference 2
➢ Underlying Customer credit Transfer Details (B) NOT MAPPED

Derived data mapping principles: For more informatin on the Return Chain, pls check the section in the UHB
1 The initiator of the Payment Return becomes the mandatory Debtor in the Return Chain element - the Debtor is the party that owes the money to the party the
return is intended for, ie the Creditor. Both Debtor and Creditor are mandatory in the Return chain and they can be identified as a Party or an Agent.
2 This section should be used if the Return chain is not identical to the Original payment transaction, otherwise it might be optionally used
* In the pacs.004 the Original Message Name Identification only allows to provide the value “MT202” NOT “MT202COV” – The BAH/Related BAH/Message
Definition Identifier allows to provide the information on the related message for example “MT202COV”
Note - various other elements are mandatory in the pacs.004 which are not derived from the payment instruction including for example Return Identification, Creation Date Time, Returned Interbank
Amount, Return Reason information.. often these data elements and potentially other optional elements will be generated by the bank application when creating the return message
 Pacs.008 (embedded MT103) High level derived data mapping to MT 103 RTN
!!!! Use case valid for a receiver that can receive a pacs.008 (multiformat) but can not generate a pacs.004 !!!!

Debtor Agent/Instructing Agent Instructed Agent

A B
CBPR+ Derived
Mapping Guidance_ Pacs.008 +
December 2023 MT 103

MT103 RTN

Return &
Reason

The pacs.008 (multi format) is sent from Agent A to Agent B who is NOT ISO enabled (settlement completed).
Agent B will generate a MT103 RTN to return the funds.
 Pacs.008 (embedded MT103) High level derived data mapping to MT 103 RTN
!!!! Use case valid for a receiver that can receive a pacs.008 (multiformat) but can not generate a pacs.004 !!!!

ISO MT

ISO 20022 message element MT Field Name & (Tag option)

CBPR+ Derived
Mapping Guidance_ ➢ Group Header/ Message Identification
December 2023

➢ Credit Transfer Transaction Information/Payment Identification/UETR ➢ Block3/ Field 121/ Unique EndToEndTransactionReference
➢ Credit Transfer Transaction Information / Interbank Settlement Amount ➢ Value Date/Currency/Interbank Settled Amount (Field 32A)
➢ Currency/Instructed Amount (Field 33B)*

➢ Credit Transfer Transaction Information / Debtor & Debtor Account ➢ Beneficiary Customer (Field 59 no letter, A or F)
➢ 32A is the amount that is returned
Credit Transfer Transaction Information / Debtor Agent ➢ Account With Institution (Field 57 A or B or C or D)
might not be the same as the
➢ Details of Charges (Field 71A) interbank sett amount in pacs.008

➢ Credit Transfer Transaction Information / Creditor ➢ Ordering Customer (Field 50 A, F or K)

➢ Sender To Receiver Information (Field 72) /RETN/99

➢ /ReasonCode/
➢ Credit Transfer Transaction Information/Payment Identification/Instruction Identification ➢ /MREF/
➢ Credit Transfer Transaction Information/Payment Identification/E2E Identification ➢ /TREF/

Note - various other elements are mandatory in the MT103 RTN which are not derived from the payment instruction for example Sender Reference, Bank operation Code .. often these data elements and
potentially other optional elements will be generated by the bank application when creating the return message
* Where interbank settled amount does not equal the pacs.008 interbank settlement amount (received) then the instructed amount (Field 33B) should be populated in the MT103RTN
 Embedded MT103 High level derived data mapping to MT 103 RTN
!!!! Use case valid for a receiver that can receive a pacs.008 (multiformat) but can not generate a pacs.004 !!!!

MT MT
MT Field Name & (Tag option) MT Field Name & (Tag option)
CBPR+ Derived
Mapping Guidance_
December 2023

➢
If the embedded MT 103 is used to instruct the
Block3/ Field 121/Unique EndToEndTransactionReference
➢ Value Date/Currency/Interbank Settled Amount (Field 32A)
return, pls refer to the FIN UHB – Usage ➢ Currency/Instructed Amount (Field 33B)
32A is the amount that is returned might not be the same of the
guidelines for returns ➢ Beneficiary Customer (Field 59 no letter, A or F) interbank sett amount in pacs.008
➢ Account With Institution (Field 57 A or B or C or D)
➢ Details of Charges (Field 71A)

➢ Ordering Customer (Field 50 A, F or K)

➢ Sender To Receiver Information (Field 72) /RETN/99

➢ /ReasonCode/
➢ /MREF/
➢ /TREF/

Note - various other elements are mandatory in the MT103 RTN which are not derived from the payment instruction for example Sender Reference, Bank operation Code .. often these data elements and
potentially other optional elements will be generated by the bank application when creating the return message
 Pacs.009 (embedded MT202) High level derived data mapping to MT 202 RTN – Use case 1
!!!! Use case valid for a receiver that can receive a pacs.009 (multiformat) but can not generate a pacs.004 !!!!

Debtor/Instructing Agent Creditor/Instructed Agent

CBPR+ Derived
Mapping Guidance_ A B
December 2023
Pacs.009 +
MT 202

Beneficiary Institution Ordering Institution

MT202 RTN

Return &
Reason

The pacs.009 (multi format) is sent from Agent A to Agent B who is NOT ISO enabled (settlement completed).
Agent B will generate a MT202 RTN to return the funds.
 Pacs.009 (embedded MT202) High level derived data mapping to MT 202 RTN – Use case 2
(pacs.009 covers the pacs.009 adv)
!!!! Use case valid for a receiver that can receive a pacs.009 (multiformat) but can not generate a pacs.004 !!!!

A D
Pacs.009 ADV
CBPR+ Derived Instructed Agent/ Creditor
Mapping Guidance_
Instructing Agent/ Debtor
December 2023

B C
Debtor/Instructing Agent Instructed Agent/Debtor Agent Creditor Agent Creditor

Pacs.009 + Pacs.009 +
MT 202 MT 202

Beneficiary Institution Ordering Institution

MT202 RTN
MT202 RTN

Return &
Reason

See next slide for the derived data mapping

for this MT 202 RTN

The pacs.009 (multi format) is sent from Agent A to Agent B who is NOT ISO enabled (settlement completed).
Agent B will generate a MT202 RTN to return the funds.
 Pacs.009 (embedded MT 202) High level derived data mapping to MT 202 RTN
!!!! Use case valid for a receiver that can receive a pacs.009 (multiformat) but can not generate
a pacs.004 !!!!

ISO MT

ISO 20022 message element MT Field Name & (Tag option)

CBPR+ Derived
Mapping Guidance_ ➢ Transaction Reference Number (Field 20)
December 2023 ➢ Credit Transfer Transaction Information/Payment Identification/Instruction identification ➢ Related Reference (Field 21)
➢ Credit Transfer Transaction Information/Payment Identification/UETR ➢ Block3/ Field 121/ Unique EndToEndTransactionReference
➢ Credit Transfer Transaction Information / Interbank Settlement Amount ➢ Value Date/Currency/Interbank Settled Amount (Field 32A)

32A is the amount that is returned might not be

➢ Credit Transfer Transaction Information / Instructed Agent = Debtor Agent ➢ Ordering Institution (Field 52 A or D)
the same as the interbank settlement amount in
➢ Credit Transfer Transaction Information / Instructing Agent = Debtor ➢ Beneficiary Institution (Field 58 A or D)
pacs.009
➢ Credit Transfer Transaction Information / Creditor
➢ Credit Transfer Transaction Information / Creditor Agent
➢ Sender To Receiver Information (Field 72) /RETN/99
➢ /ReasonCode/
➢ Credit Transfer Transaction Information/Payment Identification/Instruction Identification ➢ /MREF/
➢ Credit Transfer Transaction Information/Payment Identification/E2E Identification ➢ /TREF/

Block 3: T121: Original UETR

Block 4:
:20: Transaction reference Number - M
:21: Related Reference – M
: 32A: Value Date, Currency Code, Amount – M
: 52a: Credit Transfer Transaction Information / Creditor - O
: 58a: Credit Transfer Transaction Information / Debtor
: 72:/RETN/99 - M
/reason Code/ - M
/MREF/Credit Transfer Transaction Information/Payment Identification/Instruction Identification - M
/TREF/Credit Transfer Transaction Information/Payment Identification/E2E Identification - O

Note - various other elements are mandatory in the MT202 RTN which are not derived from the payment instruction for example Transaction reference Number.. often these derived data elements and potentially
other optional elements will be generated by the bank application when creating the return message
 Pacs.009 (embedded MT202 COV) High level derived data mapping to MT 202 RTN (pacs.009 cov to cover the
pacs.008)
!!!! Use case valid for a receiver that can receive a pacs.009 (multiformat) but can not generate a pacs.004 !!!!

CBPR+ Derived
Mapping Guidance_
December 2023

The pacs.009 (multi format) is sent from Agent A to Agent B who is NOT ISO enabled (settlement completed).
Agent B will generate a MT202 RTN to return the funds.
 Pacs.009 (embedded MT202 COV) High level derived data mapping to MT 202 RTN
!!!! Use case valid for a receiver that can receive a pacs.009 (multiformat) but can not generate a pacs.004 !!!!

MT 202 RTN

ISO MT B A
ISO 20022 message element MT Field Name & (Tag option)
CBPR+ Derived
Mapping Guidance_ ➢ Transaction Reference Number (Field 20)
December 2023 ➢ Credit Transfer Transaction Information/Payment Identification/Instruction identification ➢ Related Reference (Field 21)
➢ Credit Transfer Transaction Information/Payment Identification/UETR ➢ Block3/ Field 121/ Unique EndToEndTransactionReference
➢ Credit Transfer Transaction Information / Interbank Settlement Amount ➢ Value Date/Currency/Interbank Settled Amount (Field 32A)
32A is the amount that is returned might not be
the same as the interbank settlement amount in
➢ Credit Transfer Transaction Information / Instructed Agent = Debtor Agent ➢ Ordering Institution (Field 52 A or D) pacs.009
➢ Credit Transfer Transaction Information / Instructing Agent = Debtor ➢ Beneficiary Institution (Field 58 A or D)
➢ Credit Transfer Transaction Information / Creditor
NOT MAPPED
➢ Credit Transfer Transaction Information / Creditor Agent
➢ Sender To Receiver Information (Field 72) /RETN/99
➢ /ReasonCode/
➢ Credit Transfer Transaction Information/Payment Identification/Instruction Identification ➢ /MREF/
➢ Credit Transfer Transaction Information/Payment Identification/E2E Identification ➢ /TREF/

Block 3: T121: Original UETR

Block 4:
:20: Transaction reference Number - M
:21: Related Reference – M
: 32A: Value Date, Currency Code, Amount – M
: 52a: Credit Transfer Transaction Information / Creditor - O
: 58a: Credit Transfer Transaction Information / Debtor
: 72:/RETN/99 - M
/reason Code/ - M
/MREF/Credit Transfer Transaction Information/Payment Identification/Instruction Identification - M
/TREF/Credit Transfer Transaction Information/Payment Identification/E2E Identification - O

Note - various other elements are mandatory in the MT202 RTN which are not derived from the payment instruction for example Transaction reference Number.. often these derived data elements and potentially
other optional elements will be generated by the bank application when creating the return message
 Embedded MT202 or MT 202 Cov High level derived data derived data mapping to MT 202
RTN !!!! Use case valid for a receiver that can receive a pacs.009 (multiformat) but can not generate a
pacs.004 !!!!

MT MT
MT Field Name & (Tag option) MT Field Name & (Tag option)
CBPR+ Derived
Mapping Guidance_
December 2023

➢
If the embedded MT 202 or MT 202 COV is used
Transaction Reference Number (Field 20)
➢ Related Reference (Field 21)
to instruct the return, pls refer to the FIN UHB – ➢ Block3/ Field 121/ Unique EndToEndTransactionReference
Usage guidelines for returns ➢ Value Date/Currency/Interbank Settled Amount (Field 32A)
32A is the amount that is returned might not be the same of the
interbank settlement amount in pacs.008
➢ Ordering Institution (Field 52 A or D)
➢ Beneficiary Institution (Field 58 A or D)

➢ Sender To Receiver Information (Field 72) /RETN/99

➢ /ReasonCode/
➢ /MREF/
➢ /TREF/

Note - various other elements are mandatory in the MT202 RTN which are not derived from the payment instruction for example Sender Reference, Bank operation Code .. often these derived data elements and
potentially other optional elements will be generated by the bank application when creating the return message
 Derived Data Mapping – Direct
Debit
CBPR+ Derived
Mapping Guidance_
December 2023
 MT104 high level derived data mapping to pacs.003 : Use case description

Debtor/ Ordering Debtor Agent /Ordering Creditor Agent /Account with Institution Creditor / Beneficiary Customer
customer Institution

CBPR+ Derived
Mapping Guidance_
A B
December 2023

MT104

pacs.003

The MT104 is sent by the Beneficiary Customer to the Creditor Agent. It is used to collect funds from a Debtor account.
Creditor Agent that is ISO enabled sends to Debtor Agent the pacs.003
•(& Creditor Agent Account)

MT 104 High level derived data mapping to pacs.003

MT ISO

MT Field Name & (Tag option) ISO 20022 message element

General Information
➢ Sender’s Reference (Field 20)
October 24th & 31st ➢ Customer Specified Reference (Field 21R) ➢ Direct Debit Transaction Information/End To End Identification
➢ Instruction Code (Field 23E)
➢ Registration Reference (Field 21E) ➢ Direct Debit Transaction Information/ Requested Collection Date
➢ Requested Execution Date (Field 30) ➢ Direct Debit Transaction Information/Interbank Settlement Date

➢ Sending Institution (Field 51A)

➢ Instructing Party (Field 50a)
➢ Creditor (Field 50a)
➢ Creditor’s Bank (Field 52a) NOT MAPPED
➢ Transaction Type Code (Field 26T)
➢ Regulatory Reporting (Field 77B)
➢ Details of Charges (Field 71A)
➢ Sender to Receiver Information (Field 72)
Transaction Details
➢ Transaction Reference (Field 21) ➢ Direct Debit Transaction Information/Payment Identification/ Transaction Identification
➢ Instruction Code (Field 23E)
➢ Mandate Reference (Field 21E) ➢ Direct Debit Transaction Information/Direct Debit Transaction/Mandate Related Information/Mandate
➢ Direct Debit Reference (Field 21D) Identification
NOT MAPPED
➢ Registration Reference (Field 21E)
➢ Currency and Transaction Amount (Field 32B) ➢ Direct Debit Transaction Information/Transaction Information/ Interbank Settlement Amount
➢ Instructing Party (Field 50a)
➢ Creditor (Field 50a) ➢ Direct Debit Transaction Information/Creditor (& Creditor Account)
➢ Creditor’s Bank (Field 52a) ➢ Direct Debit Transaction Information/Creditor Agent (& Creditor Agent Account)
➢ Debtor’s Bank (Field 57a) ➢ Direct Debit Transaction Information/Debtor Agent (& Debtor Agent Account)
➢ Debtor (Field 59a) ➢ Direct Debit Transaction Information/Debtor (& Debtor Account)
➢ Remittance Information (Field 70) ➢ Direct Debit Transaction Information/Remittance Information/Unstructured
➢ Transaction Type Code (Field 26T) NOT MAPPED
➢ Regulatory Reporting (Field 77B) ➢ Direct Debit Transaction Information/Regulatory Reporting
➢ Currency/Original Ordered Amount (Field 33B) ➢ Direct Debit Transaction Information/Instructed Amount
➢ Details of Charges (Field 71A) ➢ Direct Debit Transaction Information/Charge Bearer
➢ Sender's Charges (Field 71F)
NOT MAPPED
➢ Receiver's Charges (Field 71G)
➢ Exchange Rate (Field 72) ➢ Direct Debit Transaction Information/Exchange Rate
Settlement Details
➢ Currency and Settlement Amount (Field 32B)
NOT MAPPED
➢ Sum Of Amounts (Field 19)
➢ Sum of Sender's Charges (Field 71F)
➢ Sum of Receiver's Charges (Field 71G)
➢ Sender's Correspondent (Field 53a) ➢ Direct Debit Transaction Information/Intermediary1
 Derived Data Mapping – Payment
Cancellation Request
CBPR+ Derived
Mapping Guidance_
December 2023
 derived data mapping - Payment Cancellation Request

Index

CBPR+ Derived High level MT payment basic derived data mapping to the camt.056
Mapping Guidance_ High level legacy MT n92 Request for Cancellation basic derived data mapping from a pacs message
December 2023 High level camt.056 Payment Cancelation Request basic derived data mapping from a pacs message
 High level MT payment basic derived data mapping to the camt.056 : Use case
description

CBPR+ Derived A B
Mapping Guidance_
December 2023

MT

Camt.056

The camt.056 Payment Cancelation Request message can be used to request the cancelation of legacy MT payments.
Which may be more relevant during the period which follows the initial implementation of ISO 20022 payments. i.e. MT
Payment send last week, now live sending ISO 20022 messages.
 High level MT payment basic derived data mapping to the camt.056

CBPR+ Derived MT ISO

Mapping Guidance_
December 2023
MT Field Name & (Tag option) ISO 20022 message element

Camt.056 Payment Cancelation Request

Underlying/Transaction Information
Original Group Information
➢ Sender’s Reference (Field 20) ➢ Original Instruction Identification (should be copied in
Original Message Identification)
➢ Message type: MT 103, MT 202 etc. ➢ Original Message Name Identification
➢ Payment application Creation Date Time of MT payment

➢ Remittance Information (Field 70) code /RFB/* or /ROC/ ➢ Original End To End Identification
else default is “NOT PROVIDED”
➢ Block 3 tag 121: UETR ➢ Original UETR
➢ Currency/Interbank Settlement Amount (Field 32A) ➢ Original Interbank Settlement Amount
➢ Value Date (Field 32A) ➢ Original Interbank Settlement Date
* Use of /RFB/ follow by up to 16 characters is associated is not associated with the MT 202 which does not have a Field 70

Note - various other elements are mandatory in the camt.056 which are not derived from the payment instruction including; Assigner (although commonly this is the MT sender),
Assignee (although commonly this is the MT receiver), Assignment/Identification, Assignment/Creation Date Time, Case/Identification, Case/Creator, Cancelation Reason
Information/Reason/Code. Often these data elements and potentially other optional elements will be generated by the bank application when creating the Payment Cancelation
Request message.
 High level camt.056 Payment Cancelation Request basic derived data mapping from a
pacs message : Use case description

CBPR+ Derived A B
Mapping Guidance_
December 2023

pacs

camt.056
 New slide since last iteration

High level camt.056 Payment Cancelation Request basic derived data mapping
from a pacs message.

ISO ISO

ISO 20022 message element MT Field Name & (Tag option)

CBPR+ Derived
Mapping Guidance_
December 2023
Camt.056 Payment Cancelation Request
pacs payment message
Underlying/Transaction Information
Original Group Information
➢ Original Message Identification
➢ Group Header/Message Identification
➢ Original Message Name Identification
➢ pacs message type*

➢ Original End To End Identification

➢ Payment Identification/End To End Identification ➢ Original UETR
➢ Payment Identification/UETR ➢ Original Instruction Identification
➢ Payment Identification/Instruction Identification ➢ Original Interbank Settlement Amount
➢ Payment Identification/Interbank Settlement Amount, ➢ Original Interbank Settlement Date
➢ Payment Identification/Interbank Settlement Date

* eg, pacs.008, pacs.009 , pacs.010

Note - various other elements are mandatory in the camt.056 which are not derived from the payment instruction including; Assigner (although commonly this is the MT sender), Assignee
(although commonly this is the MT receiver), Assignment/Identification, Assignment/Creation Date Time, Case/Identification, Case/Creator, Cancelation Reason
Information/Reason/Code. Often these data elements and potentially other optional elements will be generated by the bank application when creating the Payment Cancelation Request
message.
 High level legacy MT n92 Request for Cancelation basic derived data mapping from a
pacs message : Use case description

CBPR+ Derived A B
Mapping Guidance_
December 2023

pacs

MT n92

It is highly recommended that instructed pacs messages, which are requested to be cancelled, should be done so by using
the camt.056 Payment Cancelation Request messages.
 High level legacy MT n92 Request for Cancelation basic derived data mapping
from a pacs message.

ISO MT

ISO 20022 message element MT Field Name & (Tag option)

CBPR+ Derived
Mapping Guidance_
December 2023

pacs payment message. MT n92 Cancelation Request

➢ Payment Identification/Instruction Identification ➢ Related Reference (Field 21)

➢ pacs message type equivalent in MT* + Group Header/Creation Date ➢ MT and Date of the Original Message* (Field 11S)
➢ See Note + Original UETR, Original Interbank Settlement Amount, Original ➢ Narrative Description of the Original Message (Field 79)
Interbank Settlement Date

* pacs.008 = 103, pacs.009 = 202, pacs.010 = 204

Note - the legacy MT n92 Transaction Reference Number (Field 20) commonly the requestor’s point to point Case reference is not derived from the payment instruction, this together with
Narrative Description of the Original Message (Field 79) which must contain the Narrative description of the transaction to be cancelled will be generated by the bank application when
creating the Payment Cancelation Request message. In addition to the Original UETR, Original Interbank Settlement Amount and Original Interbank Settlement Date other data from the
original payment may be provided. However it is not recommended to copy ISO 20022 xml into the legacy MT message, where narrative description is instead recommended.
 High level legacy MT n95 Queries basic derived data mapping from a pacs message :
Use case description

CBPR+ Derived A B
Mapping Guidance_
December 2023

pacs

MT n95
 High level legacy MT n95 Queries basic derived data mapping from a pacs
message.

ISO MT

ISO 20022 message element MT Field Name & (Tag option)

CBPR+ Derived
Mapping Guidance_
December 2023

pacs payment message. MT n95 Queries

➢ Payment Identification/Instruction Identification ➢ Related Reference (Field 21)

➢ Queries (Field 75)
➢ pacs message type equivalent in MT* + Group Header/Creation Date ➢ MT and Date of the Original Message* (Field 11a)
➢ See Note + Original UETR, Original Interbank Settlement Amount, Original ➢ Narrative Description of the Original Message (Field 79)
Interbank Settlement Date
Block 3 T121: UETR
:20: sender’s instruction id
:21: Payment Identification/Instruction Identification
:11R:103 Interbank Settlement Date
:79: see guidance below

* pacs.008 = 103, pacs.009 = 202, pacs.010 = 204

Note - the legacy MT n92 Transaction Reference Number (Field 20) commonly the requestor’s point to point Case reference is not derived from the payment instruction, this together with
Narrative Description of the Original Message (Field 79) which must contain the Narrative description of the transaction to be cancelled will be generated by the bank application when
creating the Payment Cancelation Request message. In addition to the Original UETR, Original Interbank Settlement Amount and Original Interbank Settlement Date other data from the
original payment may be provided. However it is not recommended to copy ISO 20022 xml into the legacy MT message, where narrative description is instead recommended.
 Derived Data Mapping Guidance –
MT to Bank to Customer Statement
CBPR+ Derived
Mapping Guidance_
December 2023
 MT 103 High level Derived data mapping to camt.053/054 (Creditor Agent to Creditor):
Use case description

Debtor Agent/Instructing Agent Instructed Agent Creditor Agent Creditor

CBPR+ Derived
Mapping Guidance_
December 2023 A B

MT 103

camt.054

camt.053

The MT103 is sent from Agent A to Agent B that is the agent servicing the account of the Creditor (settlement completed).
Agent B sends optionally a camt.054 and a camt.053 to the Creditor who is the account owner
 MT 103 High level derived data mapping to camt.054 (Creditor Agent to Creditor)
These 3 elements might impact the code populated in the
element “bank transaction code”

MT ISO

MT Field Name & (Tag option) ISO 20022 message element

➢ Sender’s Reference (Field 20)
➢ Time Indication (Field 13C) NOT MAPPED ➢ Notification / Entry/EntryDetails/TransactionDetails/References/ UETR must be mapped from the
CBPR+ Derived ➢ Bank Operation code (Field 23B) header of the MT103
➢ Notification / Entry/EntryDetails/TransactionDetails/References/Instruction Identification
Mapping Guidance_ ➢ Instruction Code (Field 23E) NOT MAPPED
➢ Transaction type Code (Field 26T)
December 2023 ➢ Value Date/Currency/Interbank Settled Amount (Field 32A)

➢ Currency/Instructed Amount (Field 33B) ➢ Notification / Entry/ Amount *

➢ Exchange Rate (Field 36) ➢ Notification / Entry/EntryDetails/TransactionDetails/Amount *
➢ Ordering Customer (Field 50 A, F or K)* ➢ Notification /Entry/ Value Date *
➢ Sending Institution (Field 51A) NOT MAPPED ➢ Notification /Ntry/NtryDtls/TxDtls/AmtDtls/InstdAmt
➢ Ordering Institution (Field 52 A or D) or Message Sender if F52 not present ➢ Notification /Ntry/NtryDtls/TxDtls/AmtDtls/InstdAmt/CcyXchg/XchgRate
➢ Sender’s Correspondent (Field 53 A or B or D) ➢ Notification / Entry/EntryDetails/TransactionDetails/ Related Parties/Debtor & Debtor Account
➢ Receiver’s Correspondent (Field 54 A or B or D)
➢ Third Reimbursement Institution (Field 55 A or B or D) NOT MAPPED ➢ Notification / Entry/EntryDetails/TransactionDetails/Related Agents/Debtor Agent
➢ Intermediary Institution (Field 56 A or C or D)
➢ Account With Institution (Field 57 A or B or C or D)

➢ Beneficiary Customer (Field 59 no letter, A or F)

➢ Remittance Information (Field 70)

➢ Details of Charges (Field 71A) ➢ Statement / Entry/EntryDetails/TransactionDetails/ Related Parties/Creditor & Creditor Account *
➢ Sender’s Charges (Field 71F) ➢ Notification / Entry/ EntryDetails/ TransactionDetails/ Remittance Information/Unstructured
Or Notification / Entry/EntryDetails/TransactionDetails/References/E2E id (if 70//ROC/)
➢ Receiver’s Charges (Field 71G) NOT MAPPED ➢ Notification / Entry/ EntryDetails/TransactionDetails/Charges/Record/Bearer
➢ Notification / Entry/ EntryDetails/TransactionDetails/Charges/Record/Amount
➢ Sender To Receiver Information (Field 72) NOT MAPPED
➢ Regulatory Reporting (Field 77B)

Note - various other elements are mandatory in the camt.054 which are not derived from the payment instruction including; Message Identification, Creation Date Time, Notification
Identification, Account, Entry Reference, Credit Debit Indicator, Status, Bank Transaction Code, Related Dates.. often these data elements and potentially other optional elements
will be generated by the bank application when creating the reporting message

* May not have a direct relationship but value in source message received will influence the value in target message
* Mapping done if the beneficiary customer name (F59) is NOT the same as the name registered for the account
 MT 103 High level derived data mapping to camt.053 (Creditor Agent to Creditor)
These 3 elements might impact the code populated in the
element “bank transaction code”

MT ISO

MT Field Name & (Tag option) ISO 20022 message element

➢ Sender’s Reference (Field 20)
➢ Time Indication (Field 13C) NOT MAPPED ➢ Statement / Entry/EntryDetails/TransactionDetails/References/UETR must be mapped from the
CBPR+ Derived ➢ Bank Operation code (Field 23B) header of the MT103
➢ Statement / Entry/EntryDetails/TransactionDetails/References/Instruction Identification
Mapping Guidance_ ➢ Instruction Code (Field 23E) NOT MAPPED
➢ Transaction type Code (Field 26T)
December 2023 ➢ Value Date/Currency/Interbank Settled Amount (Field 32A)

➢ Currency/Instructed Amount (Field 33B) ➢ Statement / Entry/ Amount *

➢ Exchange Rate (Field 36) ➢ Statement / Entry/EntryDetails/TransactionDetails/Amount *
➢ Ordering Customer (Field 50 A, F or K) ➢ Statement/Entry/ Value Date *
➢ Sending Institution (Field 51A) NOT MAPPED ➢ Stmt/Ntry/NtryDtls/TxDtls/AmtDtls/InstdAmt
➢ Ordering Institution (Field 52 A or D) or Message Sender if F52 not present ➢ Stmt/Ntry/NtryDtls/TxDtls/AmtDtls/InstdAmt/CcyXchg/XchgRate
➢ Sender’s Correspondent (Field 53 A or B or D) ➢ Statement / Entry/EntryDetails/TransactionDetails/ Related Parties/Debtor & Debtor Account
➢ Receiver’s Correspondent (Field 54 A or B or D)
➢ Third Reimbursement Institution (Field 55 A or B or D) NOT MAPPED ➢ Statement/ Entry/EntryDetails/TransactionDetails/Related Agents/Debtor Agent
➢ Intermediary Institution (Field 56 A or C or D)
➢ Account With Institution (Field 57 A or B or C or D)

➢ Beneficiary Customer (Field 59 no letter, A or F) NOT MAPPED

➢ Remittance Information (Field 70)

➢ Details of Charges (Field 71A)

➢ Sender’s Charges (Field 71F) ➢ Statement/ Entry/ EntryDetails/ TransactionDetails/ Remittance Information/Unstructured
Or Statement / Entry/EntryDetails/TransactionDetails/References/E2E id (if 70//ROC/)
➢ Receiver’s Charges (Field 71G) NOT MAPPED ➢ Statement/ Entry/ EntryDetails/TransactionDetails/Charges/Record/Bearer
➢ Statement/ Entry/ EntryDetails/TransactionDetails/Charges/Record/Amount
➢ Sender To Receiver Information (Field 72) NOT MAPPED
➢ Regulatory Reporting (Field 77B)

Note - various other elements are mandatory in the camt.053 which are not derived from the payment instruction including; Message Identification, Creation Date Time,
Statement Identification, Statement Pagination, Balance, Credit Debit Indicator, Status, Bank Transaction Code.. often these data elements and potentially other optional
elements will be generated by the bank application when creating the reporting message
* May not have a direct relationship but value in source message received will influence the value in target message
 MT 103 High level Derived data mapping to camt.053/054 (Debtor Agent to Debtor): Use
case description

Debtor Debtor Agent/Instructing Agent Instructed Agent Creditor Agent

CBPR+ Derived
Mapping Guidance_
December 2023
A B

MT 103
camt.054

camt.053

The MT103 is sent from Agent A to Agent B. Agent A is the agent servicing the account of the Debtor (settlement
completed). Agent A sends optionally a camt.054 and a camt.053 to the Debtor who is the account owner
 MT 103 High level derived data mapping to camt.054 (Debtor Agent to Debtor)
These 3 elements might impact the code populated in the
element “bank transaction code”

MT ISO

MT Field Name & (Tag option) ISO 20022 message element

➢ Sender’s Reference (Field 20)
➢ Time Indication (Field 13C) NOT MAPPED ➢ Notification / Entry/EntryDetails/TransactionDetails/References/ UETR must be mapped from the
CBPR+ Derived ➢ Bank Operation code (Field 23B) header of the MT103
➢ Notification / Entry/EntryDetails/TransactionDetails/References/Instruction Identification
Mapping Guidance_ ➢ Instruction Code (Field 23E) NOT MAPPED
➢ Transaction type Code (Field 26T)
December 2023 ➢ Value Date/Currency/Interbank Settled Amount (Field 32A)

➢ Currency/Instructed Amount (Field 33B) ➢ Notification / Entry/ Amount *

➢ Exchange Rate (Field 36) ➢ Notification / Entry/EntryDetails/TransactionDetails/Amount *
➢ Ordering Customer (Field 50 A, F or K) ➢ Notification /Entry/ Value Date *
➢ Sending Institution (Field 51A) ➢ Notification /Ntry/NtryDtls/TxDtls/AmtDtls/InstdAmt
➢ Ordering Institution (Field 52 A or D) NOT MAPPED ➢ Notification /Ntry/NtryDtls/TxDtls/AmtDtls/InstdAmt/CcyXchg/XchgRate
➢ Sender’s Correspondent (Field 53 A or B or D)
➢ Receiver’s Correspondent (Field 54 A or B or D)
➢ Third Reimbursement Institution (Field 55 A or B or D) NOT MAPPED
➢ Intermediary Institution (Field 56 A or C or D)
➢ Account With Institution (Field 57 A or B or C or D)
➢ Beneficiary Customer (Field 59 no letter, A or F)
➢ Remittance Information (Field 70)
➢ Notification / Entry/ EntryDetails/ TransactionDetails/ Related Agent/Creditor Agent
➢ Details of Charges (Field 71A) ➢ Notification / Entry/ EntryDetails/ TransactionDetails/ Related Parties/Creditor
➢ Sender’s Charges (Field 71F) ➢ Notification / Entry/ EntryDetails/ TransactionDetails/ Remittance Information/Unstructured
Or Notification / Entry/EntryDetails/TransactionDetails/References/E2E id (if 70/ROC/)
➢ Receiver’s Charges (Field 71G) ➢ Notification / Entry/ EntryDetails/TransactionDetails/Charges/Record/Bearer
➢ Notification / Entry/ EntryDetails/TransactionDetails/Charges/Record/Amount
➢ Sender To Receiver Information (Field 72) NOT MAPPED
➢ Regulatory Reporting (Field 77B) NOT MAPPED

Note - various other elements are mandatory in the camt.054 which are not derived from the payment instruction including; Message Identification, Creation Date Time, Notification Identification, Account
Currency, Entry Reference, Credit Debit Indicator, Status, Bank Transaction Code, Related Dates.. often these data elements and potentially other optional elements will be generated by the bank
application when creating the reporting message

* May not have a direct relationship but value in source message received will influence the value in target message
 MT 103 High level derived data mapping to camt.053 (Debtor Agent to Debtor)
These 3 elements might impact the code populated in the
element “bank transaction code”

MT ISO

MT Field Name & (Tag option) ISO 20022 message element

➢ Sender’s Reference (Field 20)
➢ Time Indication (Field 13C) NOT MAPPED ➢ Statement / Entry/EntryDetails/TransactionDetails/References/UETR must be mapped from the
CBPR+ Derived ➢ Bank Operation code (Field 23B) header of the MT103
➢ Statement / Entry/EntryDetails/TransactionDetails/References/Instruction Identification
Mapping Guidance_ ➢ Instruction Code (Field 23E) NOT MAPPED
➢ Transaction type Code (Field 26T)
December 2023 ➢ Value Date/Currency/Interbank Settled Amount (Field 32A)

➢ Currency/Instructed Amount (Field 33B) ➢ Statement / Entry/ Amount *

➢ Exchange Rate (Field 36) ➢ Statement / Entry/EntryDetails/TransactionDetails/Amount *
➢ Ordering Customer (Field 50 A, F or K) ➢ Statement/Entry/ Value Date *
➢ Sending Institution (Field 51A) ➢ Statement / Entry / EntryDetails /TxDtls/AmtDtls/InstdAmt
➢ Ordering Institution (Field 52 A or D) ➢ Statement / Entry / EntryDetails /TxDtls/AmtDtls/InstdAmt/CcyXchg/XchgRate
➢ Sender’s Correspondent (Field 53 A or B or D) NOT MAPPED
➢ Receiver’s Correspondent (Field 54 A or B or D)
➢ Third Reimbursement Institution (Field 55 A or B or D)
➢ Intermediary Institution (Field 56 A or C or D)
➢ Account With Institution (Field 57 A or B or C or D)

➢ Beneficiary Customer (Field 59 no letter, A or F)

➢ Remittance Information (Field 70) ➢ Statement / Entry/ EntryDetails/ TransactionDetails/ Related Agent/Creditor Agent

➢ Details of Charges (Field 71A) ➢ Statement / Entry/ EntryDetails/ TransactionDetails/ Related Parties/Creditor
➢ Sender’s Charges (Field 71F) ➢ Statement/ Entry/ EntryDetails/ TransactionDetails/ Remittance Information/Unstructured
Or Statement / Entry/EntryDetails/TransactionDetails/References/E2E id (if 70/ROC/)
➢ Receiver’s Charges (Field 71G) NOT MAPPED ➢ Statement/ Entry/ EntryDetails/TransactionDetails/Charges/Record/Bearer
➢ Statement/ Entry/ EntryDetails/TransactionDetails/Charges/Record/Amount
➢ Sender To Receiver Information (Field 72) NOT MAPPED
➢ Regulatory Reporting (Field 77B)

Note - various other elements are mandatory in the camt.053 which are not derived from the payment instruction including; Message Identification, Creation Date Time, Statement Identification,
Statement Pagination, Balance, Credit Debit Indicator, Status, Bank Transaction Code.. often these data elements and potentially other optional elements will be generated by the bank application when
creating the reporting message

* May not have a direct relationship but value in source message received will influence the value in target message
 MT 103 High level Derived data mapping to camt.053/054 (Intermediary to Creditor
Agent): Use case description

Debtor Debtor Agent/Instructing Agent Instructed Agent/Intermediary Creditor Agent Creditor

CBPR+ Derived
Mapping Guidance_
December 2023 A B C

INGA
MT 103 Pacs.008

camt.054

camt.053

The MT103 is sent from servicing Agent A to Intermediary Agent B (settlement completed).

Agent B sends optionally a camt.054 and a camt.053 to the Creditor Agent who is the account owner and ISO enabled
(credit confirmation). The reporting messages will be derived from the original MT received.
 MT 103 High level derived data mapping to camt.054 (Intermediary to Creditor Agent)
These 3 elements might impact the code populated in the
element “bank transaction code”

MT ISO

MT Field Name & (Tag option) ISO 20022 message element

➢ Sender’s Reference (Field 20)
➢ Time Indication (Field 13C) NOT MAPPED ➢ Notification / Entry/EntryDetails/TransactionDetails/References/ UETR must be mapped from the
CBPR+ Derived ➢ Bank Operation code (Field 23B) header of the MT103
➢ Notification / Entry/EntryDetails/TransactionDetails/References/Instruction Identification
Mapping Guidance_ ➢ Instruction Code (Field 23E) NOT MAPPED
➢ Transaction type Code (Field 26T)
December 2023 ➢ Value Date/Currency/Interbank Settled Amount (Field 32A)

➢ Currency/Instructed Amount (Field 33B) ➢ Notification / Entry/ Amount *

➢ Exchange Rate (Field 36) ➢ Notification / Entry/EntryDetails/TransactionDetails/Amount *
➢ Ordering Customer (Field 50 A, F or K)* ➢ Notification /Entry/ Value Date *
➢ Sending Institution (Field 51A) NOT MAPPED
➢ Ordering Institution (Field 52 A or D) ➢ Notification /Ntry/NtryDtls/TxDtls/AmtDtls/InstdAmt
➢ Sender’s Correspondent (Field 53 A or B or D) ➢ Notification /Ntry/NtryDtls/TxDtls/AmtDtls/InstdAmt/CcyXchg/XchgRate
➢ Receiver’s Correspondent (Field 54 A or B or D) ➢ Notification/Account/Identification
NOT MAPPED
➢ Third Reimbursement Institution (Field 55 A or B or D)
➢ Intermediary Institution (Field 56 A or C or D)
➢ Account With Institution (Field 57 A or B or C or D)

➢ Beneficiary Customer (Field 59 no letter, A or F)

➢ Remittance Information (Field 70)
➢ Notification / Entry/ EntryDetails/ TransactionDetails/ Related Agent/Creditor Agent
➢ Details of Charges (Field 71A)
➢ Sender’s Charges (Field 71F) ➢ Notification / Entry/ EntryDetails/ TransactionDetails/ Related Parties/Creditor
➢ Notification / Entry/ EntryDetails/ TransactionDetails/ Remittance Information/Unstructured
Or Notification / Entry/EntryDetails/TransactionDetails/References/E2E id (if 70/ROC/)
➢ Receiver’s Charges (Field 71G) ➢ Notification / Entry/ EntryDetails/TransactionDetails/Charges/Record/Bearer
➢ Notification / Entry/ EntryDetails/TransactionDetails/Charges/Record/Amount
➢ Sender To Receiver Information (Field 72) NOT MAPPED
➢ Regulatory Reporting (Field 77B) OR
➢ Statement/ Entry/ EntryDetails/TransactionDetails/Charges/Record/Amount

Note - various other elements are mandatory in the camt.054 which are not derived from the payment instruction including; Message Identification, Creation Date Time, Notification Identification,
Notification Pagination, Account Currency, Entry Reference, Credit Debit Indicator, Status, Bank Transaction Code, Related Dates.. often these data elements and potentially other optional elements
will be generated by the bank application when creating the reporting message

* May not have a direct relationship but value in source message received will influence the value in target message
 MT 103 High level Derived data mapping to camt.053 (Intermediary to Creditor Agent)
These 3 elements might impact the code populated in the
element “bank transaction code”

MT ISO

MT Field Name & (Tag option) ISO 20022 message element

➢ Sender’s Reference (Field 20)
➢ Time Indication (Field 13C) NOT MAPPED ➢ Statement / Entry/EntryDetails/TransactionDetails/References/UETR must be mapped from the
CBPR+ Derived ➢ Bank Operation code (Field 23B) header of the MT103
➢ Statement / Entry/EntryDetails/TransactionDetails/References/Instruction Identification
Mapping Guidance_ ➢ Instruction Code (Field 23E) NOT MAPPED
➢ Transaction type Code (Field 26T)
December 2023 ➢ Value Date/Currency/Interbank Settled Amount (Field 32A)

➢ Currency/Instructed Amount (Field 33B) ➢ Statement / Entry/ Amount *

➢ Exchange Rate (Field 36) ➢ Statement / Entry/EntryDetails/TransactionDetails/Amount *
➢ Ordering Customer (Field 50 A, F or K)* ➢ Statement/Entry/ Value Date *
➢ Sending Institution (Field 51A) NOT MAPPED ➢ Stmt/Ntry/NtryDtls/TxDtls/AmtDtls/InstdAmt
➢ Ordering Institution (Field 52 A or D) ➢ Stmt/Ntry/NtryDtls/TxDtls/AmtDtls/InstdAmt/CcyXchg/XchgRate
➢ Sender’s Correspondent (Field 53 A or B or D) ➢ Statement / Entry/EntryDetails/TransactionDetails/ Related Parties/Debtor & Debtor Account
➢ Receiver’s Correspondent (Field 54 A or B or D)
➢ Third Reimbursement Institution (Field 55 A or B or D)
➢ Intermediary Institution (Field 56 A or C or D) NOT MAPPED
➢ Account With Institution (Field 57 A or B or C or D)

➢ Beneficiary Customer (Field 59 no letter, A or F)

➢ Remittance Information (Field 70) ➢ Statement / Entry/ EntryDetails/ TransactionDetails/ Related Agent/Creditor Agent

➢ Statement / Entry/ EntryDetails/ TransactionDetails/ Related Parties/Creditor

➢ Details of Charges (Field 71A) ➢ Statement/ Entry/ EntryDetails/ TransactionDetails/ Remittance Information/Unstructured
➢ Sender’s Charges (Field 71F) Or Statement / Entry/EntryDetails/TransactionDetails/References/E2E id (if 70/ROC/)

➢ Statement/ Entry/ EntryDetails/TransactionDetails/Charges/Record/Bearer

➢ Receiver’s Charges (Field 71G) ➢ Statement/ Entry/ EntryDetails/TransactionDetails/Charges/Record/Amount

➢ Sender To Receiver Information (Field 72) NOT MAPPED OR

➢ Regulatory Reporting (Field 77B) ➢ Statement/ Entry/ EntryDetails/TransactionDetails/Charges/Record/Amount

Note - various other elements are mandatory in the camt.053 which are not derived from the payment instruction including; Message Identification, Creation Date Time, Statement Identification,
Statement Pagination, Balance, Credit Debit Indicator, Status, Bank Transaction Code.. often these data elements and potentially other optional elements will be generated by the bank application when
creating the reporting message
* May not have a direct relationship but value in source message received will influence the value in target message
 MT202/202COV High level derived data mapping to camt.053/054: Use case description

Debtor/Instructing Agent Instructed Agent * Creditor

CBPR+ Derived A B C
Mapping Guidance_
December 2023 MT202
camt.054
Scenario 1
camt.053

MT103

MT202COV
Scenario 2
camt.054

camt.053

Scenario 1:
The MT202 is sent from Agent A to Agent B (settlement completed). - Agent C is ready to receive the reporting messages in ISO format.

Scenario 2:
Agent A sends the MT 103 to Agent C and sends an MT 202 COV to intermediary Agent B (settlement completed). Agent C is ready to receive the reporting
messages in ISO format.

* To simplify, Debtor Agent and Creditor Agent are same institution

 MT 202 High level derived data mapping to camt.053

MT ISO

MT Field Name & (Tag option) ISO 20022 message element

➢ Statement / Entry/EntryDetails/TransactionDetails/References/ UETR must be mapped from the

CBPR+ Derived ➢ Transaction Reference Number (Field 20) header of the MT202
➢ Statement / Entry/EntryDetails/TransactionDetails/References/Instruction Identification
Mapping Guidance_
December 2023
➢ Related Reference Field 21
➢ Notification / Entry/EntryDetails/TransactionDetails/References/End-To-End Identification
➢ Value Date/Currency/Interbank Settled Amount (Field 32A)
➢ Statement / Entry/ Amount *
➢ Statement / Entry/EntryDetails/TransactionDetails/Amount *
➢ Statement /Entry/ Value Date *

➢ Ordering Institution (Field 52 A or D) or Message Sender if F52 not

present ➢ Statement / Entry/EntryDetails/TransactionDetails/Related Agents/Debtor Agent
➢ Sender’s Correspondent (Field 53 A or B or D)
➢ Receiver’s Correspondent (Field 54 A or B or D) NOT MAPPED

➢ Intermediary (Field 56 A or D)
➢ Statement / Entry/EntryDetails/TransactionDetails/Related Agents/IntermediaryAgent1
➢ Account With Institution (Field 57 A or B or D)
➢ Beneficiary Institution (Field 58 A or D) NOT MAPPED

➢ Sender To Receiver Information (Field 72)

➢ Statement / Entry/ EntryDetails/ TransactionDetails/ Remittance Information/Unstructured (if 72/BNF/
or /TSU/)

* May not have a direct relationship but value in source message received will influence the value in target message
 MT 202 High level derived data mapping to camt.054

MT ISO

MT Field Name & (Tag option) ISO 20022 message element

➢ Notification / Entry/EntryDetails/TransactionDetails/References/ UETR must be mapped from the

CBPR+ Derived ➢ Transaction Reference Number (Field 20) header of the MT202
➢ Notification / Entry/EntryDetails/TransactionDetails/References/Instruction Identification
Mapping Guidance_
December 2023
➢ Related Reference Field 21
➢ Notification / Entry/EntryDetails/TransactionDetails/References/End-To-End Identification
➢ Value Date/Currency/Interbank Settled Amount (Field 32A)
➢ Notification / Entry/ Amount *
➢ Notification / Entry/EntryDetails/TransactionDetails/Amount *
➢ Notification /Entry/ Value Date *

➢ Ordering Institution (Field 52 A or D) or Message Sender if F52 not

present ➢ Notification / Entry/EntryDetails/TransactionDetails/Related Agents/Debtor Agent
➢ Sender’s Correspondent (Field 53 A or B or D)
➢ Receiver’s Correspondent (Field 54 A or B or D) NOT MAPPED

➢ Intermediary (Field 56 A or D)
➢ Notification / Entry/EntryDetails/TransactionDetails/Related Agents/IntermediaryAgent1
➢ Account With Institution (Field 57 A or B or D)
➢ Beneficiary Institution (Field 58 A or D) ➢ Notification / Entry/EntryDetails/TransactionDetails/Related Agents/Creditor Agent
➢ Notification / Entry/EntryDetails/TransactionDetails/Related Parties/Creditor/Agent
➢ Sender To Receiver Information (Field 72)
➢ Notification / Entry/ EntryDetails/ TransactionDetails/ Remittance Information/Unstructured

* May not have a direct relationship but value in source message received will influence the value in target message
 MT 202 COV High level derived data mapping to camt.054

MT ISO

MT Field Name & (Tag option) ISO 20022 message element

➢ Notification / Entry/EntryDetails/TransactionDetails/References/ UETR must be mapped from the

CBPR+ Derived ➢ Transaction Reference Number (Field 20) header of the MT202COV
➢ Notification / Entry/EntryDetails/TransactionDetails/References/Instruction Identification
Mapping Guidance_
December 2023
➢ Related Reference Field 21
➢ Notification / Entry/EntryDetails/TransactionDetails/References/E2E id
➢ Value Date/Currency/Interbank Settled Amount (Field 32A)
➢ Notification / Entry/ Amount *
➢ Notification / Entry/EntryDetails/TransactionDetails/Amount *
➢ Notification /Entry/ Value Date *

➢ Ordering Institution (Field 52 A or D) or Message Sender if F52 not

present ➢ Notification / Entry/EntryDetails/TransactionDetails/Related Agents/Debtor Agent
➢ Sender’s Correspondent (Field 53 A or B or D)
➢ Receiver’s Correspondent (Field 54 A or B or D)
NOT MAPPED
➢ Intermediary (Field 56 A or D)
➢ Notification / Entry/EntryDetails/TransactionDetails/Related Agents/IntermediaryAgent1
➢ Account With Institution (Field 57 A or B or D)
➢ Beneficiary Institution (Field 58 A or D)
NOT MAPPED
➢ Sender To Receiver Information (Field 72)
➢ Notification / Entry/ EntryDetails/ TransactionDetails/ Remittance Information/Unstructured (if
72/BNF/ or /TSU/)

* May not have a direct relationship but value in source message received will influence the value in target message
 MT 202 COV High level derived data mapping to camt.053

MT ISO

MT Field Name & (Tag option) ISO 20022 message element

➢ Statement / Entry/EntryDetails/TransactionDetails/References/ UETR must be mapped from the

CBPR+ Derived ➢ Transaction Reference Number (Field 20) header of the MT202COV
➢ Statement / Entry/EntryDetails/TransactionDetails/References/Instruction Identification
Mapping Guidance_
December 2023
➢ Related Reference Field 21
➢ Statement / Entry/EntryDetails/TransactionDetails/References/E2E id
➢ Value Date/Currency/Interbank Settled Amount (Field 32A)
➢ Statement / Entry/ Amount*
➢ Statement / Entry/EntryDetails/TransactionDetails/Amount *
➢ Statement /Entry/ Value Date *

➢ Ordering Institution (Field 52 A or D) or Message Sender if F52 not

present ➢ Statement / Entry/EntryDetails/TransactionDetails/Related Agents/Debtor Agent
➢ Sender’s Correspondent (Field 53 A or B or D)
➢ Receiver’s Correspondent (Field 54 A or B or D) NOT MAPPED

➢ Intermediary (Field 56 A or D)
➢ Statement / Entry/EntryDetails/TransactionDetails/Related Agents/IntermediaryAgent1
➢ Account With Institution (Field 57 A or B or D)
➢ Beneficiary Institution (Field 58 A or D) NOT MAPPED

➢ Sender To Receiver Information (Field 72)

➢ Statement / Entry/ EntryDetails/ TransactionDetails/ Remittance Information/Unstructured

* May not have a direct relationship but value in source message received will influence the value in target message
 Derived Data Mapping Guidance –
pacs.008 to reporting messages
CBPR+ Derived
Mapping Guidance_
December 2023
 Pacs.008 High level derived data mapping to camt.053 (Creditor Agent to Creditor): Use
case description

Debtor Debtor Agent/Instructing Agent Instructed Agent / Creditor Agent Creditor

CBPR+ Derived A B
Mapping Guidance_
December 2023

Pacs.008

camt.054

camt.053

The pacs.008 is sent from servicing Agent A to Agent B, that is the account servicing of C (settlement completed).
Agent B sends optionally the camt.054 and the camt.053 to C who is the account owner
 Pacs.008 High level derived data mapping to camt.053 (Creditor Agent to Creditor)

ISO ISO

ISO 20022 message element ISO 20022 message element

➢ Group Header/ Message Identification ➢ Statement / Entry/EntryDetails/TransactionDetails/References/Message Identification

CBPR+ Derived ➢ Credit Transfer Transaction Information / Creditor Account ➢ Statement/ Account / Identification *
Mapping Guidance_ ➢ Credit Transfer Transaction Information/Interbank Settlement Date ➢ Statement /Entry/ValueDate *
December 2023 ➢ Statement / Entry/EntryDetails/TransactionDetails/References/Instruction Identification
➢ Credit Transfer Transaction Information/Payment
Identification/Instruction Identification ➢ Statement / Entry/EntryDetails/TransactionDetails/References/E2E identification
➢ Credit Transfer Transaction Information/Payment Identification/E2E ➢ Statement / Entry/EntryDetails/TransactionDetails/References/UETR
Identification ➢ Statement / Entry/ Amount * AND Statement /
➢ Credit Transfer Transaction Information/Payment Identification/UETR Entry/EntryDetails/TransactionDetails/Amount
➢ Credit Transfer Transaction Information / Interbank Settlement Amount ➢ Statement /Entry/NtryDtls/TxDtls/AmtDtls/InstdAmt/Amount
➢ Credit Transfer Transaction Information / Instructed Amount (if present) ➢ Statement /Entry/NtryDtls/TxDtls/AmtDtls/InstdAmt/Currency Exchange
➢ Credit Transfer Transaction Information / Exchange Rate (if present) ➢ Statement/ Entry/ EntryDetails/TransactionDetails/Charges/Record/Bearer
➢ Credit Transfer Transaction Information/Charge Bearer ➢ Statement/ Entry/ EntryDetails/TransactionDetails/Charges/Record/Amount
➢ Credit Transfer Transaction Information/Charge Information/Amount ➢ Statement/ Entry/ EntryDetails/TransactionDetails/Charges/Record/Agent (if available)
➢ Credit Transfer Transaction Information/Charge Information/Agent

➢ Statement / Entry/EntryDetails/TransactionDetails/ Related Parties/Debtor

➢ Credit Transfer Transaction Information / Debtor ➢ Statement/ Entry/EntryDetails/TransactionDetails/Related Agents/Debtor Agent
➢ Credit Transfer Transaction Information / Debtor Agent ➢ Statement/ Entry/EntryDetails/TransactionDetails/Related Parties/ Ultimate Debtor
➢ Credit Transfer Transaction Information / Ultimate Debtor (if present) ➢ Statement/ Entry/EntryDetails/TransactionDetails/Related Parties/ Ultimate Creditor
➢ Credit Transfer Transaction Information / Ultimate Creditor (if present)
➢ Credit Transfer Transaction Information / Creditor Agent
➢ Statement/ Entry/EntryDetails/TransactionDetails/Remittance Information
➢ Credit Transfer Transaction Information / Remittance Information ❑ Structured
❑ Structured ❑ Unstructured
❑ Unstructured
Note - various other elements are mandatory in the camt.053 which are not derived from the payment instruction including; Message Identification, Creation Date Time, Statement Identification,
Statement Pagination, Account, Balance, Status = BOOK, Bank Transaction Code.. often these data elements and potentially other optional elements will be generated by the bank application when
creating the reporting message

* May not have a direct relationship but value in source message received will influence the value in target message
* Derived from the registered account information
 Pacs.008 High level derived data mapping to camt.054 (Creditor Agent to Creditor)

ISO ISO

ISO 20022 message element ISO 20022 message element

➢ Group Header/ Message Identification ➢ Notification / Entry/EntryDetails/TransactionDetails/References/Message Identification

CBPR+ Derived ➢ Credit Transfer Transaction Information / Interbank Settlement Date ➢ Notification /Entry/ Value Date *
Mapping Guidance_ ➢ Credit Transfer Transaction Information / Creditor Account ➢ Notification / Account / Identification *
December 2023
➢ Credit Transfer Transaction Information/Payment ➢ Notification / Entry/EntryDetails/TransactionDetails/References/Instruction Identification
Identification/Instruction Identification ➢ Notification / Entry/EntryDetails/TransactionDetails/References/E2E identification
➢ Credit Transfer Transaction Information/Payment Identification/E2E ➢ Notification / Entry/EntryDetails/TransactionDetails/References/UETR
Identification ➢ Notification / Entry/ Amount * AND Notification
➢ Credit Transfer Transaction Information/Payment Identification/UETR /Entry/EntryDetails/TransactionDetails/Amount *
➢ Credit Transfer Transaction Information / Interbank Settlement Amount ➢ Notification /Entry/NtryDtls/TxDtls/AmtDtls/InstdAmt/Amount
➢ Credit Transfer Transaction Information / Instructed Amount (if present) ➢ Notification /Entry/NtryDtls/TxDtls/AmtDtls/InstdAmt/Currency Exchange
➢ Credit Transfer Transaction Information / Exchange Rate (if present) ➢ Notification / Entry/ EntryDetails/TransactionDetails/Charges/Record/Bearer
➢ Credit Transfer Transaction Information/Charge Bearer ➢ Notification / Entry/ EntryDetails/TransactionDetails/Charges/Record/Amount
➢ Credit Transfer Transaction Information/Charge Information/Amount ➢ Notification / Entry/ EntryDetails/TransactionDetails/Charges/Record/Agent (if available)
➢ Credit Transfer Transaction Information/Charge Information/Agent
➢ Notification / Entry/EntryDetails/TransactionDetails/ Related Parties/Debtor
➢ Credit Transfer Transaction Information / Debtor ➢ Notification / Entry/EntryDetails/TransactionDetails/Related Agents/Debtor Agent
➢ Credit Transfer Transaction Information / Debtor Agent ➢ Notification / Entry/ EntryDetails/ TransactionDetails/ Related Parties/ Ultimate Debtor
➢ Credit Transfer Transaction Information / Ultimate Debtor (if present) ➢ Notification / Entry/ EntryDetails/ TransactionDetails/ Related Parties/ Ultimate Creditor
➢ Credit Transfer Transaction Information / Ultimate Creditor (if present)
➢ Credit Transfer Transaction Information / Creditor Agent
➢ Credit Transfer Transaction Information / Creditor ➢ Notification / Entry/EntryDetails/TransactionDetails/Remittance Information
➢ Credit Transfer Transaction Information / Remittance Information ❑ Structured
❑ Structured ❑ Unstructured
❑ Unstructured

Note - various other elements are mandatory in the camt.054 which are not derived from the payment instruction including; Message Identification, Creation Date Time, Notification Identification,
Account, Entry Reference, Credit Debit Indicator, Status, Bank Transaction Code, Related Dates.. often these data elements and potentially other optional elements will be generated by the bank
application when creating the reporting message

* May not have a direct relationship but value in source message received will influence the value in target message
* Derived from the registered account information
 Pacs.008 High level derived data mapping to MT 900/910: Use case description

Debtor Debtor Agent/Instructing Agent Instructed Agent / Creditor Agent Creditor

CBPR+ Derived
Mapping Guidance_
December 2023 A B

INGA
Pacs.008
MT 900

MT 910

The pacs.008 is sent from servicing Agent A to Agent B, that is the account servicer of the Creditor (settlement completed).
Agent A sends the MT 900 (a debit notification) to the debtor and Agent B sends the MT 910 (a credit notification) to the creditor
 Pacs.008 High level derived data mapping to MT 900 (Debtor Agent to Debtor)

ISO MT

ISO 20022 message element MT Field Name & (Tag option)

CBPR+ Derived
Mapping Guidance_
December 2023 ➢ Group Header/ Message Identification NOT MAPPED
➢ Transaction Reference Number (Field 20)

➢ Related Reference (Field 21)

➢ Credit Transfer Transaction Information/Payment Identification/Instruction ➢ Account identification (Field 25P) *
Identification
➢ Credit Transfer Transaction Information / Debtor and Debtor Account ➢ Value Date, Currency Code, Amount (Field 32A) *
➢ Value Date, Currency Code, Amount (Field 32A) *
➢ Credit Transfer Transaction Information / Interbank Settlement Amount
➢ Credit Transfer Transaction Information / Interbank Settlement Date

➢ Credit Transfer Transaction Information / Remittance Information

NOT MAPPED
❑ Structured
❑ Unstructured

Note Various elements are mandatory in the MT900 which are not derived from the payment instruction - often these data elements and potentially other optional elements will be generated by
the bank application when creating the reporting message (Back office application will identify the value for those fields), for example the Transaction Reference Number

* May not have a direct relationship but value in source message received will influence the value in target message
* Derived from the registered account information
 Pacs.008 High level derived data mapping to MT 910 (Creditor Agent to Creditor)

ISO MT

ISO 20022 message element MT Field Name & (Tag option)

CBPR+ Derived
Mapping Guidance_ ➢ Transaction Reference Number (Field 20)
December 2023 ➢ Group Header/ Message Identification NOT MAPPED

➢ Related Reference (Field 21)

➢ Account identification (Field 25P) *
➢ Credit Transfer Transaction Information/Payment Identification/E2E Identification
➢ Credit Transfer Transaction Information / Creditor and Creditor Account ➢ Value Date, Currency Code, Amount (Field 32A) *
➢ Value Date, Currency Code, Amount (Field 32A) *
➢ Credit Transfer Transaction Information / Interbank Settlement Amount
➢ Credit Transfer Transaction Information / Interbank Settlement Date ➢ Ordering Customer (Field 50 A, F or K)
➢ Ordering Institution (Field 52 A or D)
➢ Credit Transfer Transaction Information / Debtor
➢ Credit Transfer Transaction Information / Debtor Agent ➢ Sender To Receiver Information (Field 72)

➢ Credit Transfer Transaction Information / Remittance Information

❑ Structured
❑ Unstructured

Note Various elements are mandatory in the MT910 which are not derived from the payment instruction - often these data elements and potentially other optional elements will be generated by
the bank application when creating the reporting message (Back office application will identify the value for those fields), for example the Transaction Reference Number

* May not have a direct relationship but value in source message received will influence the value in target message
* Derived from the registered account information
 Pacs.008 High level derived data mapping to MT 940/950 (Creditor Agent to Creditor):
Use case description

Debtor Debtor Agent/Instructing Agent Instructed Agent / Creditor Agent Creditor

CBPR+ Derived
Mapping Guidance_ A B
December 2023

Pacs.008

MT 940
MT 950

The pacs.008 is sent from servicing Agent A to Agent B, that is the account servicing of C (settlement completed).
Agent B sends the MT 940/950 to C who is the account owner
 Pacs.008 High level derived data mapping to MT 940/ 950 (Creditor Agent to Creditor)

ISO MT

ISO 20022 message element MT Field Name & (Tag option)

CBPR+ Derived
Mapping Guidance_ ➢ Transaction Reference Number (Field 20)*
December 2023 ➢ Credit Transfer Transaction Information / Creditor and Creditor Account ➢ Account Identification (Field 25P) *
➢ Statement Number/Sequence Number (Field 28C)*
➢ Opening Balance (Field 60a)
➢ Sequence
➢ Statement Line (Field 61)
➢ Credit Transfer Transaction Information / Interbank Settlement Date ❑ Value Date *
❑ Debit/Credit Mark /C*
➢ Credit Transfer Transaction Information / Interbank Settlement Amount ❑ Amount *
❑ Transaction Type *1
❑ Identification Code * 1
➢ Credit Transfer Transaction Information / Payment Identification/E2E ❑ Reference For the Account owner*
Identification
➢ Information to Account Owner (Field 86)*
➢ /ORDP/ (for credit item) or
➢ Credit Transfer Transaction Information / Debtor ➢ /REMI/
➢ Credit Transfer Transaction Information / Remittance Information
❑ Closing Balance (Field 62a)

derived data mapping for MT950 is equivalent

(without field 86)
* Various elements are mandatory in the MT940 which are not derived from the payment instruction - often these data elements and potentially other optional elements will be generated by the
bank application when creating the reporting message (Back office application will identify the value for those fields)
1 Subfield 6 in field 61 should take the value S108 (when and if necessary)

* For more information on the field 86 usage, pls refer to the FIN UHB (for example to populate exchange rate)
* May not have a direct relationship but value in source message received will influence the value in target message
* Derived from the registered account information
 Derived Data Mapping Guidance –
pacs.009 to reporting messages
CBPR+ Derived
Mapping Guidance_
December 2023
 Pacs.009 High level derived data mapping to camt.053/054: Creditor Agent to Creditor

Debtor/Instructing Agent Instructed Agent Creditor

CBPR+ Derived A B C
Mapping Guidance_
December 2023

Pacs.009

camt.054

camt.053

The pacs.009 is sent by a Debtor Financial Institution – Agent A - to a Creditor Financial Institution (Agent C), directly or through other agents (for example
Agent B) and/or a payment clearing and settlement system.
It is used to move funds from a debtor account to a creditor, where both Debtor and Creditor are Financial Institutions.

Servicing Agent B sends optionally the camt.054 and camt.053 to C who is the account owner.

* To simplify, Debtor Agent and Creditor Agent are same institution.

 Pacs.009 High level derived data mapping to camt.054

ISO ISO

ISO 20022 message element ISO 20022 message element

➢ Group Header/ Message Identification ➢ Notification / Entry/EntryDetails/TransactionDetails/References/Message

CBPR+ Derived ➢ Credit Transfer Transaction Information / Creditor Account Identification
Mapping Guidance_ ➢ Notification / Account / Identification *
December 2023

➢ Credit Transfer Transaction Information/Payment

Identification/Instruction Identification ➢ Notification / Entry/EntryDetails/TransactionDetails/References/Instruction
➢ Credit Transfer Transaction Information/Payment Identification
Identification/E2E Identification
➢ Credit Transfer Transaction Information/Payment ➢ Notification / Entry/EntryDetails/TransactionDetails/References/E2E
Identification/UETR identification
➢ Credit Transfer Transaction Information / Interbank Settlement ➢ Notification / Entry/EntryDetails/TransactionDetails/References/UETR
Amount ➢ Notification / Entry/ Amount *AND Notification /
➢ Credit Transfer Transaction Information / Interbank Settlement Entry/EntryDetails/TransactionDetails/Amount *
Date ➢ Notification /Entry/ Value Date *

➢ Credit Transfer Transaction Information / Debtor ➢ Notification / Entry/EntryDetails/TransactionDetails/ Related Parties/Debtor

➢ Credit Transfer Transaction Information / Remittance Information /Agent
❑ Unstructured ➢ Notification / Entry/EntryDetails/TransactionDetails/ Remittance Information
❑ Unstructured

Note - various other elements are mandatory in the camt.054 which are not derived from the payment instruction including; Message Identification, Creation Date Time, Notification Identification, Entry
Reference, Credit Debit Indicator, Status, Bank Transaction Code, Related Dates.. often these data elements and potentially other optional elements will be generated by the bank application when
creating the reporting message

* May not have a direct relationship but value in source message received will influence the value in target message
* Derived from the registered account information
 Pacs.009 High level derived data mapping to camt.053

ISO ISO

ISO 20022 message element ISO 20022 message element

➢ Group Header/ Message Identification ➢ Statement / Entry/EntryDetails/TransactionDetails/References/Message

CBPR+ Derived ➢ Credit Transfer Transaction Information / Creditor Account Identification
Mapping Guidance_ ➢ Statement/ Account / Identification *
December 2023
➢ Credit Transfer Transaction Information/Payment
Identification/Instruction Identification ➢ Statement / Entry/EntryDetails/TransactionDetails/References/Instruction
➢ Credit Transfer Transaction Information/Payment Identification
Identification/E2E Identification
➢ Credit Transfer Transaction Information/Payment ➢ Statement / Entry/EntryDetails/TransactionDetails/References/E2E id
Identification/UETR ➢ Statement / Entry/EntryDetails/TransactionDetails/References/UETR
➢ Credit Transfer Transaction Information / Interbank Settlement ➢ Statement / Entry/ Amount * AND Statement /
Amount Entry/EntryDetails/TransactionDetails/Amount *
➢ Credit Transfer Transaction Information / Interbank Settlement ➢ Statement/Entry/ Value Date *
Value

➢ Credit Transfer Transaction Information / Debtor ➢ Statement / Entry/EntryDetails/TransactionDetails/ Related Parties /Debtor /Agent
➢ Credit Transfer Transaction Information / Remittance Information ➢ Statement / Entry/EntryDetails/TransactionDetails / Remittance Information
❑ Unstructured ❑ Unstructured

Note - various other elements are mandatory in the camt.053 which are not derived from the payment instruction including; Message Identification, Creation Date Time, Statement Identification,
Statement Pagination, Account, Balance, Reference, Credit Debit Indicator, Status, Bank Transaction Code.. often these data elements and potentially other optional elements will be generated by the
bank application when creating the reporting message

* May not have a direct relationship but value in source message received will influence the value in target message
* Derived from the registered account information
 Pacs.009 High level derived data mapping to camt.053/054: Debtor Agent to Debtor

Debtor/Instructing Agent Instructed Agent Creditor

A B C
CBPR+ Derived
Mapping Guidance_
December 2023

Pacs.009

camt.054

camt.053

The pacs.009 is sent by a Debtor Financial Institution – Agent A - to a Creditor Financial Institution (Agent C), directly or through other agents (for example
Agent B) and/or a payment clearing and settlement system.
It is used to move funds from a debtor account to a creditor, where both Debtor and Creditor are Financial Institutions.

Servicing Agent B sends optionally the camt.054 and camt.053 to A who is the account owner.

* To simplify, Debtor Agent and Creditor Agent are same institution.

 Pacs.009 High level derived data mapping to camt.054

ISO ISO

ISO 20022 message element ISO 20022 message element

➢ Group Header/ Message Identification ➢ Notification / Entry/EntryDetails/TransactionDetails/References/Message

CBPR+ Derived ➢ Credit Transfer Transaction Information / Debtor Account Identification
Mapping Guidance_ ➢ Notification / Account / Identification *
December 2023
➢ Credit Transfer Transaction Information/Payment
Identification/Instruction Identification ➢ Notification / Entry/EntryDetails/TransactionDetails/References/Instruction
➢ Credit Transfer Transaction Information/Payment Identification/E2E Identification
Identification ➢ Notification / Entry/EntryDetails/TransactionDetails/References/E2E
➢ Credit Transfer Transaction Information/Payment Identification/UETR identification
➢ Credit Transfer Transaction Information / Interbank Settlement Amount ➢ Notification / Entry/EntryDetails/TransactionDetails/References/UETR
➢ Credit Transfer Transaction Information / Interbank Settlement Date ➢ Notification / Entry/ Amount *AND
Notification/Entry/EntryDetails/TransactionDetails/Amount *
➢ Credit Transfer Transaction Information / Creditor ➢ Notification /Entry/ Value Date *
➢ Credit Transfer Transaction Information / Remittance Information
❑ Unstructured ➢ Notification / Entry/EntryDetails/TransactionDetails/ Related
Parties/Creditor/Agent
➢ Notification / Entry/EntryDetails/TransactionDetails/ Remittance Information
❑ Unstructured

Note - various other elements are mandatory in the camt.054 which are not derived from the payment instruction including; Message Identification, Creation Date Time, Notification Identification,
Account, Entry Reference, Credit Debit Indicator, Status, Bank Transaction Code, Related Dates.. often these data elements and potentially other optional elements will be generated by the bank
application when creating the reporting message

* May not have a direct relationship but value in source message received will influence the value in target message
* Derived from the registered account information
 Pacs.009 High level derived data mapping to camt.053

ISO ISO

ISO 20022 message element ISO 20022 message element

➢ Group Header/ Message Identification ➢ Statement / Entry/EntryDetails/TransactionDetails/References/Message

CBPR+ Derived ➢ Credit Transfer Transaction Information / Debtor Account Identification
Mapping Guidance_ ➢ Statement/ Account / Identification *
December 2023
➢ Credit Transfer Transaction Information/Payment
Identification/Instruction Identification ➢ Statement / Entry/EntryDetails/TransactionDetails/References/Instruction
➢ Credit Transfer Transaction Information/Payment Identification/E2E Identification
Identification ➢ Statement / Entry/EntryDetails/TransactionDetails/References/E2E identification
➢ Credit Transfer Transaction Information/Payment Identification/UETR ➢ Statement / Entry/EntryDetails/TransactionDetails/References/UETR
➢ Credit Transfer Transaction Information / Interbank Settlement Amount ➢ Statement / Entry/ Amount *AND Statement /
➢ Credit Transfer Transaction Information / Interbank Settlement Date Entry/EntryDetails/TransactionDetails/Amount*
➢ Statement/Entry/ Value Date *
➢ Credit Transfer Transaction Information / Creditor
➢ Credit Transfer Transaction Information / Remittance Information ➢ Statement / Entry/EntryDetails/TransactionDetails/ Related Parties
❑ Unstructured /Creditor/Agent
➢ Statement / Entry/EntryDetails/TransactionDetails / Remittance Information
❑ Unstructured

Note - various other elements are mandatory in the camt.053 which are not derived from the payment instruction including; Message Identification, Creation Date Time, Statement Identification,
Statement Pagination, Account, Balance, Credit Debit Indicator, Status, Bank Transaction Code.. often these data elements and potentially other optional elements will be generated by the bank
application when creating the reporting message

* May not have a direct relationship but value in source message received will influence the value in target message
* Derived from the registered account information
 Pacs.009 High level derived data mapping to MT 900/910 : Use case description

Debtor /Instructing Agent Instructed Agent * Creditor

CBPR+ Derived B C
A
Mapping Guidance_
December 2023

Pacs.009

MT 900
MT 910

The pacs.009 is sent from servicing Agent A to Agent B, that is the account servicing of A and C (settlement completed).
Agent B sends the MT 900 (a debit notification) to the Debtor (Agent A) and sends the MT 910 (a credit notification) to the Creditor (Agent C).
* To simplify, Debtor Agent and Creditor Agent are same institution.
 Pacs.009 High level derived data mapping to MT 900 (Debtor Agent to Debtor)

ISO MT

ISO 20022 message element MT Field Name & (Tag option)

CBPR+ Derived
Mapping Guidance_ ➢ Transaction Reference Number (Field 20)
➢ Credit Transfer Transaction Information/Payment Identification/Instruction
December 2023
Identification
➢ Credit Transfer Transaction Information/Payment Identification/E2E Identification ➢ Related Reference (Field 21)
➢ Credit Transfer Transaction Information / Debtor & Debtor Account ➢ Account identification (Field 25P) *

➢ Credit Transfer Transaction Information / Interbank Settlement Amount ➢ Value Date, Currency Code, Amount (Field 32A) *
➢ Credit Transfer Transaction Information / Interbank Settlement Date ➢ Value Date, Currency Code, Amount (Field 32A) *

➢ Credit Transfer Transaction Information / Remittance Information ➢ Sender To Receiver Information (Field 72)
❑ Unstructured

Note Various elements are mandatory in the MT900 which are not derived from the payment instruction - often these data elements and potentially other optional elements will be generated by
the bank application when creating the reporting message (Back office application will identify the value for those fields), for example the Transaction Reference Number

* May not have a direct relationship but value in source message received will influence the value in target message
* Derived from the registered account information
 Pacs.009 High level derived data mapping to MT 910 (Creditor Agent to Creditor)

ISO MT

ISO 20022 message element MT Field Name & (Tag option)

CBPR+ Derived
Mapping Guidance_
➢ Credit Transfer Transaction Information/Payment Identification/Instruction ➢ Transaction Reference Number (Field 20)
December 2023
Identification
➢ Credit Transfer Transaction Information/Payment Identification/E2E Identification ➢ Related Reference (Field 21)
➢ Credit Transfer Transaction Information / Creditor & Creditor Account ➢ Account identification (Field 25P) *

➢ Credit Transfer Transaction Information / Interbank Settlement Amount ➢ Value Date, Currency Code, Amount (Field 32A) *
➢ Credit Transfer Transaction Information / Interbank Settlement Date ➢ Value Date, Currency Code, Amount (Field 32A) *

➢ Credit Transfer Transaction Information/Debtor ➢ Ordering Customer

➢ Credit Transfer Transaction Information/Debtor Agent ➢ Ordering Institution
➢ Credit Transfer Transaction Information / Remittance Information ➢ Sender To Receiver Information (Field 72)
❑ Unstructured

Note Various elements are mandatory in the MT910 which are not derived from the payment instruction - often these data elements and potentially other optional elements will be generated by
the bank application when creating the reporting message (Back office application will identify the value for those fields), for example the Transaction Reference Number

* May not have a direct relationship but value in source message received will influence the value in target message
* Derived from the registered account information
 Pacs.009 High level derived data mapping to MT 940/950 : Use case description

Debtor /Instructing Agent Instructed Agent Creditor

CBPR+ Derived C
Mapping Guidance_ A B
December 2023

Pacs.009

MT 940
MT 950

The pacs.009 is sent from servicing Agent A to Agent B, that is the account servicing of C (settlement completed).
Agent B sends the MT 940/950 to C who is the account owner
* To simplify, Debtor Agent and Creditor Agent are same institution.
 Pacs.009 High level derived data mapping to MT 940/950 (Creditor Agent to Creditor)

ISO MT

ISO 20022 message element MT Field Name & (Tag option)

CBPR+ Derived
Mapping Guidance_
➢ Group Header/ Message Identification ➢ Transaction Reference Number (Field 20)*
December 2023
➢ Account Identification (Field 25a) *
➢ Credit Transfer Transaction Information / Creditor Account ➢ Statement Number/Sequence Number (Field 28C)*
➢ Opening Balance (Field 60a)
➢ Sequence
➢ Statement Line (Field 61)
❑ Value Date *
➢ Credit Transfer Transaction Information / Interbank Settlement Date ❑ Debit/Credit Mark /C*
❑ Amount *
➢ Credit Transfer Transaction Information / Interbank Settlement Amount ❑ Transaction Type * 1
❑ Identification Code * 1
❑ Reference For the Account owner *
➢ Credit Transfer Transaction Information/Payment Identification/E2E
Identification ➢ Information to Account Owner (Field 86)
➢ /ORDP/ (for credit item) or
➢ /REMI/
➢ Credit Transfer Transaction Information / Debtor
➢ Credit Transfer Transaction Information / Remittance Information ❑ Closing Balance (Field 62a)
❑ Unstructured

• * Various elements are mandatory in the MT940 which are not derived from the payment instruction - often these data elements and potentially other optional elements will be generated by
the bank application when creating the reporting message (Back office application will identify the value for those fields)
• 1 Subfield 6 in field 61 should take the value S109 (when and if necessary)

• For more information on the field 86 usage, pls refer to the FIN UHB (for example to populate exchange rate)
* May not have a direct relationship but value in source message received will influence the value in target message
* Derived from the registered account information
 Derived Data Mapping Guidance –
MT103 RETN to reporting messages
CBPR+ Derived
Mapping Guidance_
December 2023 Derived Data Mapping Guidance –
MT202 RETN to reporting messages

Derived Data Mapping Guidance –

pacs.004 to reporting messages
 MT 103 RETN High level Derived data mapping to camt.054/ camt.053 (Creditor
Agent to Creditor): Use case description

Debtor Debtor Agent/Instructing Agent Instructed Agent Creditor Agent Creditor

CBPR+ Derived
Mapping Guidance_ A B
December 2023

MT 103 camt.054

camt.053

Creditor does
not recognise
that credit
MT 103 RETN
camt.054

camt.053

The MT103 is sent from servicing Agent A to Agent B, that is the Agent servicing the account of the Creditor (settlement completed). Agent B sends optionally
the camt.054 and the camt.053 to the Creditor who is the account owner

Agent B needs to return the funds to the Agent A. Agent B will send optionally the camt.054 followed by the end of day statement, camt.053
 MT103 RETN High level derived data mapping to camt.054

MT ISO

MT Field Name & (Tag option) ISO 20022 message element

➢ Block3/ Field 121/Unique EndToEndTransactionReference ➢ Notification/ Entry/EntryDetails/TransactionDetails/References/UETR must be mapped from the
CBPR+ Derived ➢ Sender Reference (Field 20) header of the MT103
➢ Notification/ Entry/EntryDetails/TransactionDetails/References/Message Identification
Mapping Guidance_ ➢ Bank Operation code (Field 23B) NOT MAPPED

December 2023 ➢ Value Date/Currency/Interbank Settled Amount (Field 32A)

➢ Notification / Entry/ Amount *
➢ Notification / Entry/EntryDetails/TransactionDetails/Amount *
➢ Currency/Instructed Amount (Field 33B) ➢ Notification /Entry/ Value Date *
➢ Notification / Entry /NtryDtls/TxDtls/AmtDtls/InstructedAmt
➢ Beneficiary Customer (Field 59 no letter, A or F)
➢ Account With Institution (Field 57 A or B or C or D) ➢ Notification / Entry/ EntryDetails/ TransactionDetails/ Related Parties/Creditor
➢ Details of Charges (Field 71A) ➢ Notification / Entry/ EntryDetails/ TransactionDetails/ Related Agent/Creditor Agent
➢ Notification / Entry/ EntryDetails/TransactionDetails/Charges/Record/Bearer
➢ Notification / Entry/ EntryDetails/TransactionDetails/Charges/Record/Amount

➢ Ordering Customer (Field 50 A, F or K)

➢ Notification / Entry/ EntryDetails/ TransactionDetails/ Related Parties/Debtor
➢ Sender To Receiver Information (Field 72) /RETN/99
➢ /ReasonCode/
➢ /MREF/ ➢ Notification / Entry/ EntryDetails/ TransactionDetails/ Return Information/Reason
➢ /TREF/ ➢ Notification / Entry/EntryDetails/TransactionDetails/References/Instruction Identification
➢ Notification / Entry/EntryDetails/TransactionDetails/References/EndToEnd Identification

Note - various other elements are mandatory in the camt.054 which are not derived from the payment instruction including; Message Identification, Creation Date Time, Notification Identification,
Account, Entry Reference, Credit Debit Indicator, Status, Bank Transaction Code, Related Dates.. often these data elements and potentially other optional elements will be generated by the bank
application when creating the reporting message

* May not have a direct relationship but value in source message received will influence the value in target message
* Derived from the registered account information
 MT103 RETN High level derived data mapping to camt.053

MT ISO

MT Field Name & (Tag option) ISO 20022 message element

➢ Block3/ Field 121/Unique EndToEndTransactionReference ➢ Statement / Entry/EntryDetails/TransactionDetails/References/UETR must be mapped from the
CBPR+ Derived ➢ Sender Reference (Field 20) header of the MT103
➢ Statement / Entry/EntryDetails/TransactionDetails/References/Message Identification
Mapping Guidance_ ➢ Bank Operation code (Field 23B) NOT MAPPED

December 2023 ➢ Value Date/Currency/Interbank Settled Amount (Field 32A)

➢ Statement / Entry/ Amount *
➢ Statement / Entry/EntryDetails/TransactionDetails/Amount *
➢ Currency/Instructed Amount (Field 33B) ➢ Statement/Entry/ Value Date *
➢ Statement / Entry /NtryDtls/TxDtls/AmtDtls/InstructedAmt
➢ Beneficiary Customer (Field 59 no letter, A or F)
➢ Account With Institution (Field 57 A or B or C or D) ➢ Statement / Entry/ EntryDetails/ TransactionDetails/ Related Parties/Creditor
➢ Details of Charges (Field 71A) ➢ Statement / Entry/ EntryDetails/ TransactionDetails/ Related Agent/Creditor Agent
➢ Statement/ Entry/ EntryDetails/TransactionDetails/Charges/Record/Bearer
➢ Statement/ Entry/ EntryDetails/TransactionDetails/Charges/Record/Amount

➢ Ordering Customer (Field 50 A, F or K)

➢ Notification / Entry/ EntryDetails/ TransactionDetails/ Related Parties/Debtor
➢ Sender To Receiver Information (Field 72) /RETN/99
➢ /ReasonCode/
➢ /MREF/ ➢ Statement / Entry/ EntryDetails/ TransactionDetails/ Return Information/Reason
➢ /TREF/ ➢ Statement / Entry/EntryDetails/TransactionDetails/References/Instruction Identification
➢ Statement / Entry/EntryDetails/TransactionDetails/References/EndToEnd Identification

Note - various other elements are mandatory in the camt.053 which are not derived from the payment instruction including; Message Identification, Creation Date Time, Statement Identification,
Statement Pagination, Account, Balance, Value Date, Status, Bank Transaction Code.. often these data elements and potentially other optional elements will be generated by the bank application when
creating the reporting message

* May not have a direct relationship but value in source message received will influence the value in target message
 MT 202 RETN High level Derived data mapping to camt.054/ camt.053 (Creditor
Agent to Creditor): Use case description

Debtor /Instructing Agent Instructed Agent * Creditor

CBPR+ Derived A B C
Mapping Guidance_
December 2023
MT202
camt.054

camt.053

Creditor does
Creditor/Instructed Agent Instructing Agent * not recognise
that credit
MT 202 RETN
camt.054

camt.053

The MT202 is sent from Agent A to Agent B, that is the Agent servicing the account of the Creditor (settlement completed). Agent B sends optionally the
camt.054 and the camt.053 to the Creditor who is the account owner

Agent B needs to return the funds to the Agent A. Agent B will send optionally the camt.054 followed by the end of day statement, camt.053
* To simplify, Debtor Agent and Creditor Agent are same institution
 MT202 RETN High level derived data mapping to camt.054

MT ISO

MT Field Name & (Tag option) ISO 20022 message element

➢ Block3/ Field 121/Unique EndToEndTransactionReference ➢ Notification/ Entry/EntryDetails/TransactionDetails/References/UETR must be mapped from the
CBPR+ Derived ➢ Transaction Reference Number (Field 20) header of the MT202
➢ Notification/ Entry/EntryDetails/TransactionDetails/References/Message Identification
Mapping Guidance_
December 2023 ➢ Value Date/Currency/Interbank Settled Amount (Field 32A)
➢ Notification / Entry/ Amount *
➢ Notification / Entry/EntryDetails/TransactionDetails/Amount *
➢ Currency/Instructed Amount (Field 33B) ➢ Notification /Entry/ Value Date *
➢ Notification / Entry /NtryDtls/TxDtls/AmtDtls/InstructedAmt
➢ Beneficiary Institution (Field 58 A or D)
➢ Account With Institution (Field 57 A or B or D) ➢ Notification / Entry/ EntryDetails/ TransactionDetails/ Related Parties/Creditor
➢ Notification / Entry/ EntryDetails/ TransactionDetails/ Related Agent/Creditor Agent

➢ Sender To Receiver Information (Field 72) /RETN/99

➢ /ReasonCode/
➢ /MREF/ ➢ Notification / Entry/ EntryDetails/ TransactionDetails/ Return Information/Reason
➢ /TREF/ ➢ Notification / Entry/EntryDetails/TransactionDetails/References/Instruction Identification
➢ Notification / Entry/EntryDetails/TransactionDetails/References/EndToEnd Identification

Note - various other elements are mandatory in the camt.054 which are not derived from the payment instruction including: Message Identification, Creation Date Time, Notification Identification,
Account, Bank Transaction Code.. often these data elements and potentially other optional elements will be generated by the bank application when creating the reporting message.

* May not have a direct relationship but value in source message received will influence the value in target message
 MT202 RETN High level derived data mapping to camt.053

MT ISO

MT Field Name & (Tag option) ISO 20022 message element

➢ Block3/ Field 121/Unique EndToEndTransactionReference ➢ Statement / Entry/EntryDetails/TransactionDetails/References/UETR must be mapped from the
CBPR+ Derived ➢ Transaction Reference Number (Field 20) header of the MT202
Mapping Guidance_
December 2023 ➢ Value Date/Currency/Interbank Settled Amount (Field 32A)
➢ Statement / Entry/ Amount *
➢ Statement / Entry/EntryDetails/TransactionDetails/Amount *
➢ Currency/Instructed Amount (Field 33B) ➢ Statement/Entry/ Value Date *
➢ Statement / Entry /NtryDtls/TxDtls/AmtDtls/InstructedAmt
➢ Beneficiary Institution (Field 58 A or D)
➢ Account With Institution (Field 57 A or B or D) ➢ Statement / Entry/ EntryDetails/ TransactionDetails/ Related Parties/Creditor
➢ Statement / Entry/ EntryDetails/ TransactionDetails/ Related Agent/Creditor Agent

➢ Sender To Receiver Information (Field 72) /RETN/99

➢ /ReasonCode/
➢ /MREF/ ➢ Statement / Entry/ EntryDetails/ TransactionDetails/ Return Information/Reason
➢ /TREF/ ➢ Statement / Entry/EntryDetails/TransactionDetails/References/Instruction Identification
➢ Statement / Entry/EntryDetails/TransactionDetails/References/EndToEnd Identification

Note - various other elements are mandatory in the camt.053 which are not derived from the payment instruction including; Message Identification, Creation Date Time, Statement Identification,
Statement Pagination, Account, Balance, Value Date, Status, Bank Transaction Code.. often these data elements and potentially other optional elements will be generated by the bank application when
creating the reporting message

* May not have a direct relationship but value in source message received will influence the value in target message
 Pacs.004 high level derived data mapping to camt.053/054: Use case description -
(Creditor Agent to Creditor)

CBPR+ Derived
Mapping Guidance_
December 2023

The FI to FI Customer Credit Transfer is sent from Agent A to Creditor Agent C (Through another Agent B) (and settlement is completed – Settlement Method =
INDA). Agent C as Account Servicer of Creditor will send optionally a credit notification followed by an end of day statement.

On the next day, Agent C must return the funds (following a request from Creditor) and will send optionally a debit notification followed by the end of day
statement to the Creditor.
Note : Corporates are not covered by CBPR plus guidelines
 Pacs.004 High level derived data mapping to camt.054/Debit

ISO ISO

ISO 20022 message element ISO 20022 message element

➢ Group Header/Message Identification ➢ Notification / Entry/EntryDetails/TransactionDetails/References/Message

CBPR+ Derived ➢ Transaction Information/Original Group Information/Original Identification
Mapping Guidance_ Message Name Identification/pacs.008.001.08 (for example) NOT MAPPED
December 2023 ➢ Transaction Information/ Interbank Settlement Date
➢ Transaction Information/Original Instruction Identification ➢ Notification /Entry/ Value Date *
➢ Transaction Information/Original E2E Identification ➢ Notification / Entry/EntryDetails/TransactionDetails/References/Instruction
➢ Transaction Information/Original UETR Identification
➢ Transaction Information/ ReturnedInterbank Settlement ➢ Notification / Entry/EntryDetails/TransactionDetails/References/E2E
Amount Identification
➢ Transaction Information/ Returned Instructed Amount (if ➢ Notification / Entry/EntryDetails/TransactionDetails/References/UETR
present) ➢ Notification / Entry/ EntryDetails/TransactionDetails/Amount *
➢ Transaction Information/ Exchange Rate (if present) ➢ Notification /Entry/NtryDtls/ TransactionDetails /AmtDtls/ Instructed Amount /
➢ Transaction Information/Charge Bearer Amount
➢ Transaction Information/Charge Information/Amount ➢ Notification / Entry/EntryDetails/TransactionDetails/ AmtDtls / Instructed Amount
➢ Transaction Information/Charge Information/Agent /Currency Exchange
➢ Transaction Information/ Return Chain/Creditor ➢ Notification / Entry/ EntryDetails/TransactionDetails/Charges/Record/Bearer
➢ Transaction Information/ Return Chain/Creditor Agent ➢ Notification / Entry/ EntryDetails/TransactionDetails/Charges/Record/Amount
(Optional) ➢ Notification / Entry/ EntryDetails/TransactionDetails/Charges/Record/Agent (if
➢ Transaction Information/Return Reason Information/ Reason available)
➢ Notification / Entry/EntryDetails/TransactionDetails/ Related Parties/Creditor
➢ Transaction Information/Original Transaction Reference (If ➢ Notification / Entry/EntryDetails/TransactionDetails/Related Agents/Creditor
present) NOT MAPPED Agent
➢ Notification / Entry/ EntryDetails/ TransactionDetails/ Return Information/Reason

Note - various other elements are mandatory in the camt.054 which are not derived from the payment instruction including: Message Identification, Creation Date Time, Notification Identification,
Account, Bank Transaction Code, Amount.. often these data elements and potentially other optional elements will be generated by the bank application when creating the reporting message.

* In the camt.054 Debit, the amount on the statement will be derived from either the “Returned Instructed Amount” (where present) otherwise the “Returned Interbank Settlement Amount.
* May not have a direct relationship but value in source message received will influence the value in target message
 Pacs.004 High level derived data mapping to camt.053/Debit

ISO ISO

ISO 20022 message element ISO 20022 message element

➢ Group Header/Message Identification ➢ Statement / Entry/EntryDetails/TransactionDetails/References/Message

CBPR+ Derived ➢ Transaction Information/Original Group Information/Original Identification
Mapping Guidance_ Message Name Identification/pacs.008.001.08 (for example) NOT MAPPED
December 2023 ➢ Transaction Information/ Interbank Settlement Date
➢ Transaction Information/Original Instruction Identification ➢ Statement/Entry/ Value Date *
➢ Transaction Information/Original E2E Identification ➢ Statement / Entry/EntryDetails/TransactionDetails/References/Instruction
➢ Transaction Information/Original UETR Identification
➢ Transaction Information/ Returned Interbank Settlement ➢ Statement / Entry/EntryDetails/TransactionDetails/References/E2E Identification
Amount * ➢ Statement / Entry/EntryDetails/TransactionDetails/References/UETR
➢ OR Transaction Information/ Returned Instructed Amount * ➢ Statement / Entry/EntryDetails/TransactionDetails/Amount
(if present)

➢ Transaction Information/Charge Bearer ➢ Statement/ Entry/ EntryDetails/TransactionDetails/Charges/Record/Bearer

➢ Transaction Information/Charge Information/Amount ➢ Statement/ Entry/ EntryDetails/TransactionDetails/Charges/Record/Amount
➢ Transaction Information/Charge Information/Agent ➢ Statement/ Entry/ EntryDetails/TransactionDetails/Charges/Record/Agent (if
➢ Transaction Information/ Return Chain/Creditor available)
➢ Transaction Information/ Return Chain/Creditor Agent ➢ Statement / Entry/ EntryDetails/ TransactionDetails/ Related Parties/Creditor
(Optional) ➢ Statement / Entry/ EntryDetails/ TransactionDetails/ Related Agents/Creditor
➢ Transaction Information/Return Reason Information/ Reason Agent
➢ Statement / Entry/ EntryDetails/ TransactionDetails/ Return Information/Reason
➢ Transaction Information/Original Transaction Reference (If
present) NOT MAPPED

Note - various other elements are mandatory in the camt.053 which are not derived from the payment instruction including; Message Identification, Creation Date Time, Statement Identification,
Statement Pagination, Account, Balance, Amount, Status, Bank Transaction Code.. often these data elements and potentially other optional elements will be generated by the bank application when
creating the reporting message

* In the camt.053 Debit, the amount on the statement will be derived from either the “Returned Instructed Amount” (where present) otherwise the “Returned Interbank Settlement Amount.
* May not have a direct relationship but value in source message received will influence the value in target message
 Pacs.004 high level derived data mapping to camt.053/054: Use case description -
(Debtor Agent to Debtor)

Debtor Agent/Instructing Agent Instructed Agent Creditor Agent Creditor

Debtor

CBPR+ Derived A B C
Mapping Guidance_
December 2023
Creditor does
INGA not recognise
pacs.008 pacs.008 that credit
camt.054 (Debit)

Camt.053 (Debit)

Creditor Agent Instructed Agent Instructing Agent/Debtor Agent

camt.054 (Credit) INDA

pacs.004 Next Busines day
pacs.004
Camt.053 (Credit) Return & Return &
Reason Reason

The FI to FI Customer Credit Transfer is sent from Agent A to Creditor Agent C (Through another Agent B) (and settlement is completed – Settlement Method =
INGA). Agent A as Account Servicer of the Debtor will send optionally a debit notification followed by an end of day statement.

On the next day, Agent C must return the funds (following a request from Creditor) – Agent A will receive the funds and will optionally send a credit notification
followed by an end of day statement.
Note : Corporates are not covered by CBPR plus guidelines
 Pacs.004 High level derived data mapping to camt.054/Credit

ISO ISO

ISO 20022 message element ISO 20022 message element

➢ Group Header/Message Identification ➢ Notification / Entry/EntryDetails/TransactionDetails/References/Message

CBPR+ Derived ➢ Transaction Information/Original Group Information/Original Identification
Mapping Guidance_ Message Name Identification/pacs.008.001.08 (for example) NOT MAPPED
December 2023 ➢ Transaction Information/ Interbank Settlement Date
➢ Transaction Information/Original Instruction Identification ➢ Notification /Entry/ Value Date *
➢ Transaction Information/Original E2E Identification ➢ Notification / Entry/EntryDetails/TransactionDetails/References/Instruction
➢ Transaction Information/Original UETR Identification
➢ Transaction Information/ ReturnedInterbank Settlement ➢ Notification / Entry/EntryDetails/TransactionDetails/References/E2E
Amount Identification
➢ Transaction Information/ Returned Instructed Amount (if ➢ Notification / Entry/EntryDetails/TransactionDetails/References/UETR
present) ➢ Notification / Entry/ EntryDetails/TransactionDetails/Amount *
➢ Notification /Entry/NtryDtls/ TransactionDetails /AmtDtls/ Instructed Amount /
➢ Transaction Information/Charge Bearer Amount
➢ Transaction Information/Charge Information/Amount
➢ Transaction Information/Charge Information/Agent ➢ Notification / Entry/ EntryDetails/TransactionDetails/Charges/Record/Bearer
➢ Transaction Information/ Return Chain/Debtor ➢ Notification / Entry/ EntryDetails/TransactionDetails/Charges/Record/Amount
➢ Transaction Information/ Return Chain/Debtor Agent ➢ Notification / Entry/ EntryDetails/TransactionDetails/Charges/Record/Agent (if
(Optional) available)
➢ Transaction Information/Return Reason Information/ Reason ➢ Notification / Entry/EntryDetails/TransactionDetails/ Related Parties/Debtor
➢ Notification / Entry/EntryDetails/TransactionDetails/Related Agents/Debtor Agent
➢ Transaction Information/Original Transaction Reference (If ➢ Notification / Entry/ EntryDetails/ TransactionDetails/ Return Information/Reason
present) NOT MAPPED

Note - various other elements are mandatory in the camt.054 which are not derived from the payment instruction including: Message Identification, Creation Date Time, Notification Identification,
Account, Amount, Bank Transaction Code.. often these data elements and potentially other optional elements will be generated by the bank application when creating the reporting message.

* May not have a direct relationship but value in source message received will influence the value in target message
* In the camt.054 Credit, the amount on the statement will be derived from the “Returned Interbank Settlement Amount” - the Instructed Amount on the statement will only be derived from the “Returned
Instructed Amount "if present in pacs.004
 Pacs.004 High level derived data mapping to camt.053/Credit

ISO ISO

ISO 20022 message element ISO 20022 message element

➢ Group Header/Message Identification ➢ Statement / Entry/EntryDetails/TransactionDetails/References/Message

CBPR+ Derived ➢ Transaction Information/Original Group Information/Original Identification
Mapping Guidance_ Message Name Identification/pacs.008.001.08 (for example) NOT MAPPED
December 2023 ➢ Transaction Information/ Interbank Settlement Date
➢ Transaction Information/Original Instruction Identification ➢ Statement/Entry/ Value Date *
➢ Transaction Information/Original E2E Identification ➢ Statement / Entry/EntryDetails/TransactionDetails/References/Instruction
➢ Transaction Information/Original UETR Identification
➢ Transaction Information/ Returned Interbank Settlement ➢ Statement / Entry/EntryDetails/TransactionDetails/References/E2E Identification
Amount * ➢ Statement / Entry/EntryDetails/TransactionDetails/References/UETR
➢ OR Transaction Information/ Returned Instructed Amount * ➢ Statement / Entry/EntryDetails/TransactionDetails/Amount *
(if present) ➢ Statement /
Entry/EntryDetails/TransactionDetails/AmountDetails/InstructedAmount/Amount
➢ Transaction Information/Charge Bearer
➢ Transaction Information/Charge Information/Amount ➢ Statement/ Entry/ EntryDetails/TransactionDetails/Charges/Record/Bearer
➢ Transaction Information/Charge Information/Agent ➢ Statement/ Entry/ EntryDetails/TransactionDetails/Charges/Record/Amount
➢ Transaction Information/ Return Chain/Debtor ➢ Statement/ Entry/ EntryDetails/TransactionDetails/Charges/Record/Agent (if
➢ Transaction Information/ Return Chain/Debtor Agent available)
(Optional) ➢ Statement / Entry/ EntryDetails/ TransactionDetails/ Related Parties/Debtor
➢ Transaction Information/Return Reason Information/ Reason ➢ Statement / Entry/ EntryDetails/ TransactionDetails/ Related Agents/Debtor
Agent
➢ Transaction Information/Original Transaction Reference (If ➢ Statement / Entry/ EntryDetails/ TransactionDetails/ Return Information/Reason
present) NOT MAPPED

Note - various other elements are mandatory in the camt.053 which are not derived from the payment instruction including: Message Identification, Creation Date Time, Statement Identification,
Statement Pagination, Account, Balance, Amount, Status, Bank Transaction Code.. often these data elements and potentially other optional elements will be generated by the bank application when
creating the reporting message.

* May not have a direct relationship but value in source message received will influence the value in target message
* In the camt.053 Credit, the amount on the statement will be derived from the “Returned Interbank Settlement Amount” - the Instructed Amount on the statement will only be derived from the “Returned
Instructed Amount "if present in pacs.004
 Pacs.004 high level derived data mapping to MT 940/950: Use case description - Creditor
does not
Payment completed recognise
that credit
Debtor Agent/Instructing Agent Instructed Agent Creditor Agent Creditor
Debtor

CBPR+ Derived A B C
Mapping Guidance_
December 2023

INGA INDA
pacs.008 pacs.008
MT 940/950

Creditor Agent Instructed Agent Instructing Agent/Debtor Agent

INDA Next Busines day

pacs.004
Return &
Reason
MT 940/950

The FI to FI Customer Credit Transfer is sent from Agent A to Creditor Agent C (Through another Agent B) (and settlement is completed – Settlement Method =
INDA). Agent C as Account Servicer of Creditor will send a Customer Statement message (or a Statement Message)
On the next day, Agent C must return the funds (following a request from Creditor) and will send a Customer Statement message (or a Statement Message).

Note : Corporates are not covered by CBPR plus guidelines

 Pacs.004 High level derived data mapping to MT 940/950

ISO MT

ISO 20022 message element MT Field Name & (Tag option)

CBPR+ Derived
Mapping Guidance_ ➢ Transaction Information/Original Group Information/Original Message
December 2023 Identification
NOT MAPPED

➢ Transaction Information/Original Group Information/Original Message Name ➢ Transaction Reference Number (Field 20) *
Identification/pacs.008.001.08 (for example) NOT MAPPED ➢ Account Identification (Field 25a) *
➢ Statement Number/Sequence Number (Field 28C) *
➢ Opening Balance (Field 60a)
➢ Transaction Information/ Interbank Settlement Date ➢ Sequence
➢ Statement Line (Field 61)
➢ Transaction Information/ Returned Interbank Settlement Amount ❑ Value Date *
❑ Debit/Credit Mark /RC *
❑ Amount *
❑ Transaction Type* 1
❑ Identification Code * 1
❑ Reference For the Account owner
➢ Transaction Information/ Return Chain/Creditor
➢ Transaction Information/Original Transaction Reference/Remittance ➢ Information to Account Owner (Field 86)
Information ➢ /BENM/ (for debit item)
➢ /REMI/
➢ Transaction Information/Return Reason Information/ Reason

❑ Closing Balance (Field 62a)

Derived data mapping for MT950 is equivalent (without field 86)
• * Various elements are mandatory in the MT940 which are not derived from the payment instruction - often these data elements and potentially other optional elements will be generated by
the bank application when creating the reporting message (Back office application will identify the value for those fields)
• 1 Subfield 6 in field 61 should take the value S104 (when and if necessary)
• For more information on the field 86 usage, pls refer to the FIN UHB (for example to populate exchange rate)
* May not have a direct relationship but value in source message received will influence the value in target message
* Derived from the registered account information
 Pacs.004 high level derived data mapping to MT 900/910: Use case description - Creditor
does not
Payment completed recognise
that credit
Debtor Agent/Instructing Agent Instructed Agent Creditor Agent Creditor
Debtor

CBPR+ Derived A B C
Mapping Guidance_
December 2023

INDA INDA
pacs.008 pacs.008

MT 900 MT 910

Creditor Agent Instructed Agent Instructing Agent/Debtor Agent

INDA
Next Busines day
pacs.004
Return &
Reason
MT 910 MT 900

The FI to FI Customer Credit Transfer is sent from Agent A to Creditor Agent C (Through another Agent B) (and settlement is completed – Settlement Method =
INDA). Agent C as Account Servicer of Creditor will send a Confirmation of Debit to Agent B and a Confirmation of Credit to Creditor

On the next day, Agent C must return the funds (following a request from Creditor) and will send a Confirmation of Debit to the Creditor and a Confirmation of
Credit to Agent B
Note : Corporates are not covered by CBPR plus guidelines
 Pacs.004 High level derived data mapping to MT 900

ISO MT

ISO 20022 message element MT Field Name & (Tag option)

CBPR+ Derived
Mapping Guidance_ ➢ Transaction Information/Original Group Information/Original Message
December 2023 Identification NOT MAPPED

➢ Transaction Information/Original Group Information/Original Message ➢ Transaction Reference Number (Field 20)
Name Identification/pacs.008.001.08 * NOT MAPPED
➢ Transaction Information/Return Identification

➢ Related Reference (Field 21)

➢ Account identification (Field 25P) *
➢ Transaction Information/ Interbank Settlement Date
➢ Transaction Information/ Returned Interbank Settlement Amount
➢ Value Date, Currency Code, Amount (Field 32A) *
➢ Value Date, Currency Code, Amount (Field 32A) *
➢ Transaction Information/Return Reason Information/ Reason

➢ Sender To Receiver Information (Field 72)

Note Various elements are mandatory in the MT900 which are not derived from the payment instruction - often these data elements and potentially other optional elements will be generated by
the bank application when creating the reporting message (Back office application will identify the value for those fields), for example the Transaction Reference Number

* May not have a direct relationship but value in source message received will influence the value in target message
* Derived from the registered account information
 Pacs.004 High level derived data mapping to MT 910

ISO MT

ISO 20022 message element MT Field Name & (Tag option)

CBPR+ Derived
Mapping Guidance_ ➢ Transaction Information/Original Group Information/Original Message
December 2023 Identification
NOT MAPPED

➢ Transaction Information/Original Group Information/Original Message ➢ Transaction Reference Number (Field 20)
Name Identification/pacs.008.001.08 * NOT MAPPED
➢ Transaction Information/Original End to End Identification

➢ Related Reference (Field 21)

➢ Transaction Information/ Interbank Settlement Date ➢ Account identification (Field 25P) *
➢ Transaction Information/ Returned Interbank Settlement Amount
➢ Value Date, Currency Code, Amount (Field 32A) *
➢ Transaction Information/Return Reason Information/ Reason ➢ Value Date, Currency Code, Amount (Field 32A) *

➢ Sender To Receiver Information (Field 72)

Note Various elements are mandatory in the MT910 which are not derived from the payment instruction - often these data elements and potentially other optional elements will be generated by
the bank application when creating the reporting message (Back office application will identify the value for those fields), for example the Transaction Reference Number

* May not have a direct relationship but value in source message received will influence the value in target message
* Derived from the registered account information
 Derived Data Mapping Guidance –
Cancellation Request
CBPR+ Derived
Mapping Guidance_
December 2023
 Mapping Guidance - Payment Cancellation Request

❑ Pls refer to the derived data mapping completed for batch 1 and covering:
CBPR+ Derived
Mapping Guidance_ ✓ High level MT payment basic derived data mapping to the camt.056
December 2023
✓ High level legacy MT n92 Request for Cancellation basic derived data mapping from a pacs message

✓ High level camt.056 Payment Cancelation Request basic derived data mapping from a pacs message

❑ See below slides for the derived data mapping covering:

✓ High level camt.056 Payment Cancelation Request basic derived data mapping camt.029

✓ High level legacy MT 292 Request for Cancellation basic derived data mapping from camt.057
 Camt.056 High level derived data mapping to camt.029: Use case description

Debtor Agent/Instructing Agent Intermediary Agent Creditor Agent Creditor

Debtor

CBPR+ Derived
Mapping Guidance_ A B C
December 2023
Pacs.008

Pacs.002
Pacs.008

Camt.056
Camt.056

Camt.029
Camt.029
See next slide for the derived data mapping
for camt.029

The pacs.008 is sent from servicing Agent A to Agent B. Agent B sends optionally a pacs.002 to provide the payment transaction status and sends the
pacs.008 to the next agent.

Agent A then needs to cancel the payment and sends the cancellation request with a reason code. Agent B after investigation responds to Agent A using the
camt.029
 Camt.056 High level derived data mapping to camt.029

ISO ISO

ISO 20022 message element ISO 20022 message element

➢ Assignment ➢ Assignment
CBPR+ Derived ➢ Identification NOT MAPPED
Mapping Guidance_ ➢ Assigner ➢ Assignee
December 2023 ➢ Assignee ➢ Assigner
➢ Creation Date NOT MAPPED

➢ Underlying/Transaction Information ➢ Cancellation Details/ Transaction Information And Status

➢ Case ➢ Resolved Case
➢ Identification ➢ Identification
➢ Creator ➢ Creator

➢ Original Group Information ➢ Original Group Information

➢ Original Message Identification (could also be present in ➢ Original Message Identification (could also be present in Original Instruction
Original Instruction Identification) Identification)
➢ Original Message Name Identification ➢ Original Message Name Identification

➢ Original End To End Identification ➢ Original End To End Identification

➢ Original UETR ➢ Original UETR
➢ Cancellation Reason Information NOT MAPPED

Note - various other elements are mandatory in the camt.029 which are not derived from the payment cancellation Request including: Assignement /Identification, Assignement/Creation Date Time,
Status, Cancellation Status Identification, Cancellation Status Reason Information often these data elements and potentially other optional elements will be generated by the E&I application when
creating the E&I message
 Camt.056 High level derived data mapping to MT196: Use case description

Debtor Agent/Instructing Agent Intermediary Agent Creditor Agent Creditor

Debtor

CBPR+ Derived
Mapping Guidance_ A B C
December 2023
Pacs.008

Pacs.002
Pacs.008

Camt.056
Camt.056

MT196
MT196
See next slide for the derived data mapping
for MTn96

The pacs.008 is sent from servicing Agent A to Agent B. Agent B sends optionally a pacs.002 to provide the payment transaction status and sends the
pacs.008 to the next agent.

Agent A then needs to cancel the payment and sends the cancellation request with a reason code. Agent B after investigation responds to Agent A using the
MT196
 Camt.056 High level derived data mapping to MT 196

ISO MT

ISO 20022 message element MT Field Name & (Tag option)

CBPR+ Derived
Mapping Guidance_ ➢ Assignment
December 2023 ➢ Identification
NOT MAPPED

➢ Assigner
➢ Assignee ➢ MT and Date of the Original Message* (Field 11S)
➢ Creation Date NOT MAPPED
➢ Transaction Reference Number (Field 20)
* camt.056

➢ Underlying/Transaction Information
➢ Case
➢ Identification
➢ Creator

➢ Original Group Information

➢ Original Message Identification (could also be present in Original
Instruction Identification) ➢ Related Reference (Field 21)
➢ Original Message Name Identification ➢ Narrative (Field 77A)

➢ Original End To End Identification ➢ Narrative Description of the Original Message (Field 79)
➢ Original UETR
➢ Cancellation Reason Information NOT MAPPED

Note - the legacy MT 196 Transaction Reference Number (Field 20) commonly the requestor’s point to point Case reference is not derived from the camt.056. The Narrative Description of
the Original Message (Field 79) to which the answer relates (the camt.056) will enable the Receiver to identify that message.
 Camt.057 High level derived data mapping to MT 292: Use case description

Debtor Debtor Agent Creditor Agent Creditor

CBPR+ Derived
Mapping Guidance_
camt.057
December 2023
B MT 292
A

Creditor is expecting to receive a payment from the Debtor. As the Account Owner sends a Notification to Receive to Agent C as Account Servicer.

Creditor then sends a Cancellation Request to the Creditor Agent.

 Camt.056 High level derived data mapping to MT 9196

ISO MT

ISO 20022 message element MT Field Name & (Tag option)

CBPR+ Derived
Mapping Guidance_
December 2023 ➢ Notification/Identification
➢ Transaction Reference Number (Field 20)
➢ Item/Identification ➢ Related Reference (Field 21)
➢ Item/Amount ➢ MT and Date of the Original Message* (Field 11S)
➢ Narrative Description of the Original Message (Field 79)

* camt.057=210

Note - the legacy MT n92 Transaction Reference Number (Field 20) commonly the requestor’s point to point Case reference is not derived from the original notification camt.057. This together
with Narrative Description of the Original Message (Field 79) which must contain the narrative description of transaction to be cancelled, will be generated by the bank application when
creating the Request For Cancellation message.
In addition to the Item/identification and Item/Amount, other data from the original camt.057 may be provided. However it is not recommended to copy ISO 20022 xml into the legacy MT
message, where narrative description is instead recommended.

This mapping is only valid until camt.058 is available (Nov 2023)

 Derived Data Mapping Guidance –
Charges
CBPR+ Derived
Mapping Guidance_
December 2023
 Mapping Guidance - Charges

✓ High level basic derived data mapping pacs.008 to MT 191

CBPR+ Derived
Mapping Guidance_
December 2023
 Pacs.008 High level derived data mapping to MT 191

Debtor Agent/Instructing Agent Instructed Agent / Creditor Agent Creditor

Debtor

CBPR+ Derived
Mapping Guidance_
December 2023 A B

Pacs.008

MT 191

The pacs.008 is sent from servicing Agent A to Agent B with additional instructions to complete the payment instruction.
The Agent B will then request the payment of charges, interest and/or other expenses which were previously unknown to the receiver, using the MT 191
 Pacs.008 High level derived data mapping to MT 191 (Creditor Agent to Debtor Agent)

ISO MT

ISO 20022 message element MT Field Name & (Tag option)

CBPR+ Derived
Mapping Guidance_ ➢ Group Header/ Message Identification ➢ Transaction Reference Number (Field 20)
December 2023 ➢ Credit Transfer Transaction Information/Payment
Identification/Instruction Identification ➢ Related Reference (Field 21)
➢ Credit Transfer Transaction Information/Payment
Identification/UETR

➢ Value Date, Currency Code, Amount (Field 32A)

➢ Details Of Charges (Field 71B)
➢ Sender To Receiver Information (Field 72)

Note - various other elements are mandatory in the MT 191 which are not derived from the payment often these data elements and potentially other optional elements will be generated by the
bank application when creating the Request for Payment Of Charges message
 Camt.106 High level derived data mapping to pacs.009

Debtor Debtor Agent/Instructing Agent Instructed Agent / Creditor Agent Creditor

CBPR+ Derived
Mapping Guidance_
December 2023 A B

Pacs.008

Camt.106

Pacs.009

Following the receipt of a pacs.008, the Agent B requests the payment of charges, interest and/or other expenses which were previously unknown to the
receiver, using the camt.106.
Agent A sends the pacs.009 for the payment of the requested amount of charges.
 Camt.106 High level derived data mapping to pacs.009 for end of December

ISO ISO

ISO 20022 message element ISO 20022 message element

CBPR+ Derived
Mapping Guidance_
December 2023

➢ Charges/PerTransaction/ChargeIdentification ➢ Credit Transfer Transaction Information/Payment Identification/E2E Identification

➢ Credit Transfer Transaction Information/Payment Identification/UETR *
➢ Charges/PerTransaction/ Record/Total Charges Per Record/Total Charges ➢ Credit Transfer Transaction Information / Interbank Settlement Amount
Amount
➢ Credit Transfer Transaction Information / Instructing Agent
➢ Credit Transfer Transaction Information / Instructed Agent

➢ Group Header/ Charge Requestor ➢ Credit Transfer Transaction Information / Creditor (=Creditor Agent)

* New UETR will be populated in pacs.009

 Derived Data Mapping Guidance –
Account Reporting Request
CBPR+ Derived
Mapping Guidance_
December 2023
 High level mapping camt.060 to MT 920

ISO MT

ISO 20022 message element MT Field Name & (Tag option)

CBPR+ Derived
Mapping Guidance_ ➢ Group Header / Message Identification ➢ Transaction Reference Number (Field 20)
December 2023 ➢ Group Header / Creation Date Time
NOT MAPPED

➢ Report Request / Requested Message Name Id ➢ Message Request (Field 12)

➢ Report Request / Account Owner
➢ Account Identification (Field 25)
 Derived Data Mapping Guidance –
Direct Debit
CBPR+ Derived
Mapping Guidance_
December 2023
 MT104 high level derived data mapping to pacs.003 : Use case description

Debtor/ Ordering Debtor Agent /Ordering Creditor Agent /Account with Institution Creditor / Beneficiary Customer
customer Institution

CBPR+ Derived
Mapping Guidance_
A B
December 2023

MT104

pacs.003

The MT104 is sent by the Beneficiary Customer to the Creditor Agent. It is used to collect funds from a Debtor account.
Creditor Agent that is ISO enabled sends to Debtor Agent the pacs.003
 MT 104 High level derived data mapping to pacs.003
New
MT ISO

MT Field Name & (Tag option) ISO 20022 message element

General Information
➢ Sender’s Reference (Field 20) ➢ Group Header/ Message Identification
CBPR+ Derived ➢ Customer Specified Reference (Field 21R) ➢ Direct Debit Transaction Information/End To End Identification
Mapping Guidance_ ➢ Instruction Code (Field 23E)
➢ Registration Reference (Field 21E) ➢ Direct Debit Transaction Information/ Requested Collection Date
December 2023 ➢ Requested Execution Date (Field 30) ➢ Direct Debit Transaction Information/Interbank Settlement Date

➢ Sending Institution (Field 51A)

➢ Instructing Party (Field 50a)
➢ Creditor (Field 50a)
➢ Creditor’s Bank (Field 52a) NOT MAPPED
➢ Transaction Type Code (Field 26T)
➢ Regulatory Reporting (Field 77B)
➢ Details of Charges (Field 71A) ➢ Direct Debit Transaction Information/Payment Identification/ Instruction Identification
➢ Sender to Receiver Information (Field 72)
Transaction Details ➢ Direct Debit Transaction Information/Direct Debit Transaction/Mandate Related Information/Mandate
➢ Transaction Reference (Field 21) Identification
➢ Instruction Code (Field 23E)
➢ Mandate Reference (Field 21E) NOT MAPPED
➢ Direct Debit Reference (Field 21D) ➢ Direct Debit Transaction Information/Transaction Information/ Interbank Settlement Amount
➢ Registration Reference (Field 21E)
➢ Currency and Transaction Amount (Field 32B) ➢ Direct Debit Transaction Information/Creditor
➢ Instructing Party (Field 50a) ➢ Direct Debit Transaction Information/Creditor Agent
➢ Creditor (Field 50a) ➢ Direct Debit Transaction Information/Debtor Agent
➢ Creditor’s Bank (Field 52a) ➢ Direct Debit Transaction Information/Debtor
➢ Debtor’s Bank (Field 57a) ➢ Direct Debit Transaction Information/Remittance Information/Unstructured
➢ Debtor (Field 59a)
➢ Remittance Information (Field 70) ➢ Direct Debit Transaction Information/Instructed Amount
➢ Transaction Type Code (Field 26T) NOT MAPPED ➢ Direct Debit Transaction Information/Charge Bearer
➢ Regulatory Reporting (Field 77B)
➢ Currency/Original Ordered Amount (Field 33B) ➢ Direct Debit Transaction Information/Exchange Rate
➢ Details of Charges (Field 71A) NOT MAPPED
➢ Sender's Charges (Field 71F)
➢ Receiver's Charges (Field 71G)
➢ Exchange Rate (Field 72)
Settlement Details
➢ Currency and Settlement Amount (Field 32B)
NOT MAPPED
➢ Sum Of Amounts (Field 19)
➢ Sum of Sender's Charges (Field 71F)
➢ Sum of Receiver's Charges (Field 71G)
➢ Sender's Correspondent (Field 53a)
 High level mapping pacs.010 to MT 204

ISO MT

ISO 20022 message element MT Field Name & (Tag option)

CBPR+ Derived
Mapping Guidance_ Sequence A – Reimbursement Details
➢ Group Header / Message Identification
December 2023 ➢ Transaction Reference Number (Field 20)
➢ Group Header / Creation Date Time NOT MAPPED

➢ Group Header/ Number of Transactions NOT MAPPED

➢ Credit Instruction / Credit Identification ➢ Value Date (Field 30)

➢ Credit Instruction / Instructing Agent NOT MAPPED
➢ Credit Instruction / Instructed Agent NOT MAPPED
➢ Credit Instruction / Creditor ➢ Beneficiary Institution (Field 58a)

➢ Direct Debit Transaction Information / Payment Identification Sequence B – Transaction Details

➢ Direct Debit Transaction Information / Interbank Settlement ➢ Transaction Reference Number (Field 20)
Amount ➢ Transaction Amount (Field 32B) & Sum of Amounts (Field 19)
➢ Direct Debit Transaction Information / Interbank Settlement Date
➢ Direct Debit Transaction Information / Debtor ➢ Debit Institution (Field 53a)
➢ Beneficiary Institution (Field 58a)
➢ Direct Debit Transaction Information / Instruction for Debtor
Agent ➢ Sender to Receiver Information (Field 72)
➢ Direct Debit Transaction Information / Remittance Information /
Unstructured
 * The “Settlement Method” is mandatory in both pacs.009

High level mapping pacs.010 (CCP – Margin Collection) to pacs.009 Message

Type
Settlement Method

New Pacs.009 INDA INGA

Pacs.004 INGA INDA

ISO ISO

ISO 20022 message element ISO 20022 message element

CBPR+ Derived
Mapping Guidance_ ➢ Group Header / Message Identification Group Header/ Message Identification
December 2023 ➢ Group Header / Creation Date Time Group Header/ Settlement Information/ Settlement Method *
NOT MAPPED
➢ Group Header/ Number of Transactions

➢ Credit Instruction / Credit Identification

➢ Credit Instruction / Instructing Agent
➢ Credit Instruction / Instructed Agent NOT MAPPED
➢ Credit Instruction / CreditorAgent Credit Transfer Transaction Information / Creditor Agent = Instructed Agent
➢ Credit Instruction / Creditor (CCP) Credit Transfer Transaction Information / Creditor (CCP)

➢ Direct Debit Transaction Information / Payment Identification/E2EId Credit Transfer Transaction Information/Payment Identification/E2EIdentification
➢ Direct Debit Transaction Information / Payment Identification/UETR Credit Transfer Transaction Information/Payment Identification/UETR *
➢ Direct Debit Transaction Information / Interbank Settlement Amount Credit Transfer Transaction Information / Interbank Settlement Amount (New value)
➢ Direct Debit Transaction Information / Interbank Settlement Date
➢ Direct Debit Transaction Information / Debtor Credit Transfer Transaction Information / Debtor
➢ Direct Debit Transaction Information / DebtorAgent Credit Transfer Transaction Information / Debtor Agent = Instructing Agent

* The UETR in pacs.009 is inherited from pacs.010 the value