CHAPS Enhanced to Like-for-like Additional Technical Guidance

CHAPS Enhanced to Like-for-like Additional Technical Guidance September 2021

In accordance with the Memorandum of Understanding (MOU), Direct Participants MUST follow the CHAPS Enhanced to Like-for-Like Additional Technical Guidance (“Guidance”) and White label communications | Risk of data truncation in CHAPS messages in order to provide consistent, effective transparent approach to manage the truncation risk outlined in the MoU. The

Guidance is directly applicable for CHAPS DPs of the MOU and valid up to the end of the Interim Period, as defined in the MoU in case extended data is received - when CHAPS can only accept payment messages that contain Like-for-like data.

In keeping with applicable law or market level industry standards related to compliance duties, including but not limited to anti-money laundering (AML) and Counter Terrorism Financing (CTF) analytics or embargo & sanctions checking, this Guidance:

I. Sets out how Direct Participants shall convert GBP wire payment instructions containing enhanced data into Like-for-like messages that can be transmitted through CHAPS. This includes how to prioritise the transmission of information most relevant to controls such as relevant sanctions and anti-money laundering screening within the constraints of the Like-for-like message. The Guidance can therefore result in certain less critical information being truncated or overwritten, even where it was provided within a field that can be mapped into a Like-for-like message, where a higher priority use of the limited message space requires.

II. Informs Direct Participants when and how to use a bilateral message (MT199) between the sending CHAPS Direct Participant and the receiving CHAPS Direct Participant, when it is not possible to fully convert the message and truncated data is requested.

This document is publically available on the Bank’s website. For more detail on this, and how enhanced data shall be encouraged from February 2023, see the Bank’s webpage [LINK].

The Guidance

Until the end of the interim period, CHAPS participants shall discourage clients that use ISO20022 messages from using the extended data elements such as; ultimate creditor, ultimate debtor and structured remittance data that do not have equivalent fields in the CHAPS via the like-for-like messages. Appropriate use of structured data for other fields, such as creditor and debtor address fields may however add value and can be accommodated. This will help enable some of the benefits of using structured data to be realised from the outset.

Direct Participants shall use the Guidance alongside the MOU and Whitelabel communications. The Guidance has primarily been designed for payments that have been received by the sending Direct Participant the SWIFT correspondent banking network (CBPRplus), however shall also be used by Direct Participants as guidance for all payments where the Debtor uses an enhanced ISO20022 message for payment initiation (including pain.001).

Please be aware that SWIFT recently amended the CBPR+ translation rules for mapping a Structured Address into Unstructured Address to bring it in line with the PMPG guidance. The change is to prioritise the Country Sub Division above the Town Location name. The tables in this Technical Guidance document reflect the prioritisation before this change was made.

Section (I): Converting GBP payment instructions containing enhanced data into Like-for-like messages:

Identifying the use of enhanced data

- First, the sending Direct Participant must identify whether a payment instruction has enhanced data included in the pacs.008, pacs.009 and pacs.009COV message it receives over CBPRplus

Converting enhanced data to Like-for-like in a CHAPS message

- Second, the sending Direct Participant must ensure where possible that maximum data is included in the Like-for-like message by:

Translating the CBPRplus and the non-correspondent banking enhanced message to Like-for-like ISO 20022 using RTGS Renewal Programme ISO 20022 Technical Guidance Like-for-like (Sections 13 & 14) LINK.

- Where applicable, the sending Direct Participant shall follow:

Annex 1 “Market Guidance against CBPRplus to CHAPS L4L mapping”, which sets out market guidance on mapping of fields known to be “problematic” in the messages.

Annex 2 Remittance information translation (from CBPRplus) Where applicable use “+” at the end of the translated information to indicate truncated data on element level. This requirement will not be applicable for all instances where data may be dropped but will apply for specific fields, where dropping data presents a higher level of risk, as an additional safeguard to be applied by the

https://www.bankofengland.co.uk/-/media/boe/files/memoranda-of-understanding/memoranda-of-understanding/mou-for-the-handling-of-temporary-data-truncation-issues-during-the-chaps-iso-20022-migration.pdf

2

Direct Participant when following the defined mapping and prioritisation criteria for those fields. This is clarified further within Annex 1.

- The sending Direct Participant must not contradict or diverge from the guidance set out in these documents. - The guiding principles set out in this document can be applied to the pacs.008, pacs.009 and pacs.009COV messages

Section (II) Providing any truncated data upon request

- Sending and receiving Direct Participants must apply compliance duties in line with their legal, regulatory and internal requirements (such as embargo and Sanctions screening against the full data received). In addition, both direct Participants shall be guided by the Wolfsberg Group’ Payment Transparency Standard [LINK]

- Sending Direct Participant must provide directly to the receiving Direct Participant all payment details available in the full enhanced message upon request. Unless otherwise agreed bilaterally, the requested data must be provided to the extent requested by the means of an MT199

3

Annex 1. Market Guidance against CBPRplus to CHAPS L4L mapping Key:

Beige rows – truncation possible, data insignificant Pink rows - truncation possible, data potentially significant Red text - CBPRplus fields not present in CHAPS L4L Green text – data could be mapped to Remittance Information using MX/MT mapping rules & codewords Purple text – data could be mapped to Instruction For Next Agent or Instruction For Creditor Agent using MX/MT mapping rules & codewords

pacs.008 fields (For reference only) MT

equivalent CBPRplus / L4L Differences

Significance to compliance/ AML /

sanctions Truncation

M <GrpHdr><MsgId> Message Identification none n/a Point to Point (P2P) none

M <GrpHdr><CreDtTm> Creation Date Time none n/a (P2P) none

M <GrpHdr><NbOfTxs> Number of Transactions none n/a none

M <GrpHdr><SttlmInf> <SttlmMtd>

Settlement Method none n/a (P2P) none

M <GrpHdr><SttlmInf> <ClrSys>

Clearing System none n/a (P2P) none

M <PmtId><InstrId> Instruction Identification Field 20 - Transaction Reference Number

n/a (P2P) none

M <PmtId><EndToEndId> End To End Identification Field 70 - Remittance Information, preceded by codeword /ROC/

No difference, CHAPS currently 16 but will be changed to 35

none

O <PmtId><TxId> Transaction Identification none n/a no significance - optional reference superseded by UETR

drop

M <PmtId><UETR> UETR Field 121 - UETR No difference None

O <PmtTpInf><InstrPrty> Instruction Priority none n/a (P2P) no significance Drop

O <PmtTpInf><SvcLvl> Service Level Field 111 – Service Type Identifier Field 23E – Instruction Code code /SDVA/

Code or Proprietary allowed. L4L is Code only. Additional CBPRplus values may be used which cannot be mapped to CHAPS, except using Field 72 codeword

no significance Values that are available for CHAPS L4L can be mapped over. If any other values are sent then these values can be dropped.

4





O <PmtTpInf><LclInstrm> Local Instrument Field 23B - Bank Operation Code

Code or Proprietary allowed. L4L is Proprietary only. Additional CBPRplus values may be used which cannot be mapped to CHAPS, except using Field 72 codeword

low significance

Values that are available for CHAPS L4L can be mapped over. If any other values are sent then these values can be dropped.

O <PmtTpInf><CtgyPurp> Category Purpose Field 23E – Instruction Code codes /CORT/, /INTC/

Code or Proprietary allowed. L4L is Code only Additional CBPRplus values may be used which cannot be mapped to CHAPS, except using Field 72 codeword

low significance Values that are available for CHAPS L4L can be mapped over. If any other values are sent then these values can be dropped.

M <IntrBkSttlmAmt> <Ccy>

Interbank Settlement Amount, Currency

Field 32A - Amount, Currency Code No difference

none

M <IntrBkSttlmDt> Interbank Settlement Date Field 32A – Value Date No difference

none

O <SttlmPrty> Settlement Priority Field 113 – Banking Priority n/a (P2P) none

O <SttlmTmReq> Settlement Time Request Field 13C – Time Indication n/a (P2P) CLSTIME codeword never used in MT103

no significance drop

O <InstdAmt><Ccy> Instructed Amount, Currency Field 33B – Currency/Instructed Amount

No difference

none

O <XchgRate> Exchange Rate Field 36 – Exchange Rate No difference

none

M <ChrgBr> Charge Bearer Field 71A – Details of Charges No difference

none

O <ChrgsInf><Amt><Ccy> Charges Information Amount Field 71F – Sender’s Charges Field 71G – Receiver’s Charges

No difference

none

O <ChrgsInf><Agt> Charges Information Agent none Limited Agent formatting Additional data is only supplementary

If BIC present, map BIC and optional Clearing System Member Id - Otherwise follow mapping instruction for “Agent Mapping 1”. Truncation should be indicated with a “+” as the last character of the truncated element

O <PrvsInstgAgt1> Previous Instructing Agent 1 Field 72 – Sender to Receiver Information, preceded by codeword /INS/

Limited Agent formatting Additional data is only supplementary


5





O <PrvsInstgAgt1Acct> Previous Instructing Agent 1 Account

none n/a no significance











M <InstgAgt> Instructing Agent Sender n/a Additional data is only

supplementary Only BIC permitted

M <InstdAgt> Instructed Agent Receiver n/a Additional data is only

supplementary Only BIC permitted

O <IntrmyAgt1> Intermediary Agent 1 Field 56a - Intermediary

Limited Agent formatting

Additional data is only supplementary


O <IntrmyAgt1Acct> Intermediary Agent 1 Account Field 56a – Intermediary Account Number subfield

Limited Account formatting Additional data is only supplementary

In L4L Account fields only the account identification is allowed, either in a free format Identification element or as an IBAN. Other elements should be dropped in line with instruction for “Account Mapping”. No truncation sign applied

O <IntrmyAgt2> Intermediary Agent 2 Field 72 – Sender to Receiver Information, preceded by codeword /INTA/

n/a Low Significance

Follow instruction specified for: “Mapping Into Instructions For Next Agent” using the related code word /INTA/

O <IntrmyAgt2Acct> Intermediary Agent 2 Account none n/a no significance

6





O <IntrmyAgt3> Intermediary Agent 3 Field 72 – Sender to Receiver Information, preceded by codeword /INTA/

n/a Low Significance

Follow instruction specified for: “Mapping Into Instructions For Next Agent” using the related code word /INTA/

O <IntrmyAgt3Acct> Intermediary Agent 3 Account none n/a no significance

O <UltmtDbtr> Ultimate Debtor Field 70 - Remittance Information, preceded by codeword /ULTD/

n/a Significant

Follow mapping instruction for : “Mapping Into Unstructured Remittance Information” using the related code word /ULTD/

O <InitgPty> Initiating Party none n/a No Significance Drop

M <Dbtr> Debtor Field 50a - Ordering Customer Limited formatting Additional data is only supplementary

Follow instruction for: “Debtor Party Mapping”. Truncation should be indicated with a “+” as the last character of the truncated element

O <DbtrAcct> Debtor Account Field 50a - Ordering Customer Account Number subfield



M <DbtrAgt> Debtor Agent Field 52a - Ordering Institution Limited Agent formatting Additional data is only supplementary


O <DbtrAgtAcct> Debtor Agent Account Field 52a - Ordering Institution Account Number subfield



M <CdtrAgt> Creditor Agent Field 57a – Account With Institution Limited Agent formatting Additional data is only supplementary


7





O <CdtrAgtAcct> Creditor Agent Account Field 57a – Account With Institution Account Number subfield



M <Cdtr> Creditor Field 59a – Beneficiary Customer Limited formatting Additional data is only supplementary

Follow instruction for: “Creditor Party Mapping”. Truncation should be indicated with a “+” as the last character of the truncated element

O <CdtrAcct> Creditor Account Field 59a – Beneficiary Customer Account Number subfield


Follow instruction for: “Creditor Party Mapping”. Truncation should be indicated with a “+” as the last character of the truncated element

O <UltmtCdtr> Ultimate Creditor Field 70 - Remittance Information, preceded by codeword /ULTC/

n/a Significant

Follow mapping instruction for : “Mapping Into Unstructured Remittance Information” using the related code word /ULTB/

O <InstrForCdtrAgt> Instruction For Creditor Agent

Field 23E – Instruction Code codes /CHQB/, /HOLD/, /PHOB/, /TELB/ Field 72 – Sender to Receiver Information, preceded by codeword /ACC/

No difference for pacs.008 Element not available in the Underlying Credit Transfer of Pacs.009COV.

Significant Possibly none, unless other fields mapped here too. Note when mapping a pacs.009COV CBPR to pacs.009COV CHAPS L4L, the Instruction for creditor agent information in the underlying customer credit transaction cannot be mapped and should be dropped completely.

O <InstrForNxtAgt> Instruction For Next Agent Field 72 – Sender to Receiver Information, preceded by codeword /REC/

none

Significant None, unless subject to mapping prioritization following instruction for: “Mapping Into Instructions For Next Agent”

O <Purp> Purpose Field 26T - Transaction Type Code

Code or Proprietary allowed. L4L is Proprietary only Additional CBPRplus values may be used which cannot be mapped to CHAPS, except using /PURP/ codeword

low significance If code is present, follow mapping instruction for : “Mapping Into Unstructured Remittance Information” using the related code word /PURP/

O <RgltryRptg> Regulatory Reporting Field 77B - Regulatory Reporting

All elements allowed, up to 10 instances. L4L is single instance of Details 3x35 chars

Significant Map to RgltryRptg. Truncation should be indicated with a “+” as the last character of the truncated element

O <RltdRmtInf> Related Remittance Information Field 70 - Remittance Information, preceded by codeword /RELID/

n/a Significant

Follow mapping instruction for : “Mapping Into Unstructured Remittance Information” using the related code word /RELID/

8





O <RmtInf> Remittance Information

Field 70 - Remittance Information Unstructured preceded by codeword /URI/ Structured preceded by codeword /SRI/+

Structured or Unstructured. L4L is Unstructured only.

Significant

In case Structured Remittance Information is used, follow mapping instruction for : “Mapping Into Unstructured Remittance Information” using the related code word /SRI/ If Unstructured Remittance Information is used; Possibly no truncation, unless other fields mapped here too

The following pages show the mappings that are expected to be used for the major Parties, Agents and Elements

9

Debtor Party Mapping

Elements CBPR+ Chaps

LFL Field & Priority

Mapping

Name 140 66 Map across. If CBPR+ length > 66 characters, then put + in the last character

Postal Address

Department 70 2/ 7

If the unstructured Address Lines are used, they should map across unchanged. If the Structured Address is used and only includes Street Name, Town Name & Country, then these elements should be mapped across, possibly with truncation. If any element in red is used, then the structured address must be mapped into the unstructured Address Lines following the PMPG guidelines. The resulting address will look like an address in Tag 50F with 2/ or 3/ to indicate if the address detail relates to Street or Country & Town Truncation should be indicated with a + in the last character of the truncated element

Sub Department 70 2/ 8

Street Name 70 66 2/ 1

Building Number 16 2/ 2

Building Name 35 2/ 3

Floor 70 2/ 4

Post Box 16 2/ 5

Room 70 2/ 6

Post Code 16 3/ 3

Town Name 35 30 3/ 2

Town Location Name 35 3/ 4

District Name 35 3/ 6

Country Sub Division 35 3/ 5

Country 2 2 3/ 1

Address Line 35 x 3 35 x 3

Identification

Organisation Id

AnyBIC Map Across

LEI drop

Other

Id 35

drop Scheme Name

Issuer 35

Private Id

Date & Place Of Birth

Birth Date map across

Province Of Birth 35 drop

City Of Birth 35 30 map across

Country Of Birth 2 2 map across

Other

Id 35 35

map across Scheme Name

Issuer 35 35

Country Of Residence 2 Map to Regulatory Reporting / Information with code word /ORDERRES/

Creditor Party mapping

10



Mapping

Name 140 66 Map across. If CBPR+ length > 66 characters, then put + in the last character

Postal Address

Department 70 2/ 7

If the unstructured Address Lines are used, they should map across unchanged. If the Structured Address is used and only includes Street Name, Town Name & Country, then these elements should be mapped across, possibly with truncation. If any element in red is used, then the structured address must be mapped into the unstructured Address Lines following the PMPG guidelines. The resulting address will look like an address in Tag 59F with 2/ or 3/ to indicate if the address detail relates to Street or Country & Town Truncation should be indicated with a + in the last character of the truncated element

Sub Department 70 2/ 8

Street Name 70 66 2/ 1

Building Number 16 2/ 2

Building Name 35 2/ 3

Floor 70 2/ 4

Post Box 16 2/ 5

Room 70 2/ 6

Post Code 16 3/ 3

Town Name 35 30 3/ 2

Town Location Name 35 3/ 4

District Name 35 3/ 6

Country Sub Division 35 3/ 5

Country 2 2 3/ 1


Identification

Organisation Id

AnyBIC Map Across

LEI drop

Other

Id 35

drop Scheme Name

Issuer 35

Private Id

Date & Place Of Birth

Birth Date

drop Province Of Birth 35

City Of Birth 35

Country Of Birth 2 drop

Other

Id 35

drop Scheme Name

Issuer 35

Country Of Residence 2 Map to Regulatory Reporting / Information with codeword /BENEFRES/

Mapping Into Unstructured Remittance Information

11

A number of enhanced elements should map into the unstructured remittance information following the below priority

The intent is to follow the CBPR+ translation rules for mapping into Tag 70. It is not necessary to follow the CBPR+ translation exactly, because the End2End Identification exists in its own right in Chaps Like For Like.

Each element that is mapped into Unstructured Remittance should utilise an Identifier.

Priority of Data Mapping

Data Source Identifier Detail

1

Ultimate Creditor Information /ULTB/

Various options are supported in CBPR+ Use the first of these after the identifier (a) Name + Country + TownName (b) Name + Other Id (c) Name only (d) Other Id only

2

Ultimate Debtor Information /ULTD/

Various options are supported in CBPR+ Use the first of these after the identifier (a) Name + Country + TownName (b) Name + Other Id (c) Name only (d) Other Id only

3 Purpose /PURP/

If the Purpose in CBPR+ message is a code, or a proprietary value which does not conform to the Like For Like format, then use the Code or Proprietary after the identifier

4 Unstructured Remittance Information /URI/ Use Remittance Information / Unstructured Remittance after the identifier

5 Related Remittance Information /RELID/

Use the first occurrence of Related Remittance / Remittance Identification after the identifier.

6 Structured Remittance Information /SRI/+

No data should be copied from Remittance Information / Structured Remittance. Just include the literal /SRI/+

If the only data to be included comes from Unstructured Remittance, then do not include the Identifier /URI/

Where there is more than 1 Identifier being used, then use // before the new identifier

If there is more than 140 characters to include, then data will be truncated, use + in the 140th character.

Mapping Into Instructions For Next Agent A number of enhanced elements should map into the Instructions For Next Agent element of the Chaps Like For Like message.

These will be similar to the mappings for CBPR+ into Tag 72 of the MT103, but not identical, because the Chaps message includes some of the elements such as Previous Instructing Agents.

12

Data Source Identifier Detail

Intermediary Agent 2 & 3 /INTA/

It would be unusual for there to be more intermediary Agents required on the outbound message, but if so, include each Intermediary Agent with a Separate Identifier. The data to include for the Agent would depend upon the options received (a) BIC (b) Name, Country & Town (c) Clearing System Member Id

Instruction For Next Agent /REC/ If it is necessary to pass some Instructions to the Next Agent, then these have the lowest priority in CBPR+.

The aim should be to best utilise the available space in the Instruction For Next Agent, so the data should be concatenated together rather than starting each line with a code word. // should be used to signify the end of the data for a code word prior to the next code word.

Account Mapping

Most parties and Agents have an associated Account Element. In L4L Account fields only the account identification is allowed, either in a free format Identification element or as an IBAN. Other elements should be dropped.

Elements Mapping

Identification

IBAN Map across

Other

Identification Map Across

Scheme Name drop

Issuer drop

Type drop

Currency drop

Name drop

Proxy Type drop

Identification drop

Agent Mapping 1: Debtor Agent, Intermediary Agent 1 , Creditor Agent , Charges Information Agent

Most Agent fields present in Like-for-like are subject to the rule: “Either BIC or (Name and Address) must be present, but not both



Mapping

BICFI Map Across

13

Clearing System Member Id Clearing System Id Map across

Member Id Map across

LEI Drop

Name 140 70 If the BICFI is populated, then drop the Name Otherwise, Map across - Truncation may occur and should be indicated with a + in the last character

Postal Address

Department 70 2 - 7

If the BICFI is populated, then do not populate the Postal Address - drop any Postal Address data. If the unstructured Address Lines are used, they should map across unchanged. If the Structured Address is used, then the structured address must be mapped into the unstructured Address Lines following the CBPR+ translation rules. Truncation should be indicated with a + in the last character of the truncated element

Sub Department 70 2 - 8

Street Name 70 2 - 1

Building Number 16 2 - 2

Building Name 35 2 - 3

Floor 70 2 - 4

Post Box 16 2 - 5

Room 70 2 - 6

Post Code 16 3 - 3

Town Name 35 3 - 2

Town Location Name 35 3 - 4

District Name 35 3 - 6

Country Sub Division 35 3 - 5

Country 2 3 - 1


There is one special case not represented in this table that is probably unlikely to occur. CBPR+ allows the use of just the Clearing System Member Id without BIC, Name & Postal Address. This should only occur if all of the Agent banks are in the UK.

If this scenario occurs then the mapping should be

Direct Participant to enrich the Agent with BIC or Name & Address

Direct Participant to reject the payment back to client.

14

Agent mapping 2: Previous Instructing Agents

The Previous Instructing Agents 1, 2 & 3 are even more restrictive in Chaps Like For Like because they do not allow the Clearing System Member Id element to be used. The mappings for these from CBPR+ to LFL, and also mapping of the inbound Instructing Agent into the outbound Previous Instructing Agent are



Mapping

BICFI Map Across

Clearing System Member Id Clearing System Id Drop

Member Id Drop

LEI Drop

Name 140 70 If the BICFI is populated, then drop the Name Otherwise, Map across - Truncation may occur and should be indicated with a + in the last character

Postal Address

Department 70 2 - 7

If the BICFI is populated, then do not populate the Postal Address - drop any Postal Address data. If the unstructured Address Lines are used, they should map across unchanged. If the Structured Address is used, then the structured address must be mapped into the unstructured Address Lines following the CBPR+ translation rules. Truncation should be indicated with a + in the last character of the truncated element

Sub Department 70 2 - 8

Street Name 70 2 - 1

Building Number 16 2 - 2

Building Name 35 2 - 3

Floor 70 2 - 4

Post Box 16 2 - 5

Room 70 2 - 6

Post Code 16 3 - 3

Town Name 35 3 - 2

Town Location Name 35 3 - 4

District Name 35 3 - 6

Country Sub Division 35 3 - 5

Country 2 3 - 1


There is one special case not represented in this table that is probably unlikely to occur. CBPR+ allows the use of just the Clearing System Member Id without BIC, Name & Postal Address. This should only occur if all of the Agent banks are in the UK. If this scenario occurs, then the mapping should be

Direct Participant to enrich the Agent with BIC or Name & Address

Direct Participant to reject the payment back to client.

15

Truncation Symbol Usage and logic to map unsupported information into the L4L Message

Beige rows – truncation possible, data insignificant Pink rows - truncation possible, data potentially significant Red text - CBPRplus fields not present in CHAPS L4L Green text – data could be mapped to Remittance Information using MX/MT mapping rules & code words

Purple text – data could be mapped to Instruction For Next Agent or Instruction For Creditor Agent using MX/MT

mapping rules & codewordsTruncated Data

Significance Information

Remove data with no notification

Map information

to Prefix with Code word

Provide truncation symbol

Truncation symbol to be placed

Payment information

O <PmtId><TxId> Transaction Identification

No Significance No element present in the L4L to carry this information

Yes n/a n/a n/a n/a

O <PmtTpInf><InstrPrty> Instruction Priority


Yes n/a n/a n/a n/a

O <PmtTpInf><SvcLvl> Service Level No Significance Not all CBPR Values can be carried into the L4L message

Yes n/a n/a n/a n/a

O <PmtTpInf><LclInstrm> Local Instrument

Low Significance

Not all CBPR Values can be carried into the L4L message

Yes n/a n/a n/a n/a

O <PmtTpInf><CtgyPurp> Category Purpose

Low Significance

Not all CBPR Values can be carried into the L4L message

Yes n/a n/a n/a n/a

O <SttlmTmReq> Settlement Time Request

No Significance CLSTIME codeword never used in MT103 - Will never be present

n/a n/a n/a n/a n/a

Previous Instructing Agents

O <PrvsInstgAgt1> Previous Instructing Agent 1

Supplementary Data

If BIC present, only map BIC - Otherwise map Name & Address applying the PMPG logic for truncation of structured to unstructured address.

No n/a n/a Yes Whenever data is truncated during this mapping due to space limitation, the indicator "+" must be added at the end of the respective line/data element. Data should be prioritised according to the PMPG guidance.

16



Yes n/a n/a n/a n/a


Supplementary Data





Yes n/a n/a n/a n/a


Supplementary Data





Yes n/a n/a n/a n/a

Intermediary Agents

17

O <IntrmyAgt1> Intermediary Agent 1

No Significance Additional data is only supplementary - Bank Chains will be built by the bank processing the payment and therefore the information derived for the intermediary by the sending bank should be sufficient.

Yes n/a n/a n/a n/a

O <IntrmyAgt1Acct> Intermediary Agent 1 Account

Low Significance

Account Id permitted only in L4L. Any other information provided for the intermediary 1 account will be supplementary data

Yes n/a n/a n/a n/a


Low Significance

It is not expected for there to be a scenario where a Direct participant would need to translate a CBPR+ inbound leg to an outbound CHAPS L4L payment to another CHAPS Direct participant, that would contain 2 intermediaries within. If this scenario occurred, the bank chain would be built along the payment journey and therefore the presence of intermediary 2 information is not significant and can be derived within payment processing anyway.

Yes n/a n/a n/a n/a



Yes n/a n/a n/a n/a


Low Significance

It is not expected for there to be a scenario where a Direct participant would need to translate a CBPR+ inbound leg to an oubound CHAPS L4L payment to another CHAPS Direct participant, that would contain 3 intermediaries within. If this scenario occurred, the bank chain would be built along the payment journey and therefore the presence of intermediary 2 information is not significant and can be derived within payment processing anyway.

Yes n/a n/a n/a n/a

18



Yes n/a n/a n/a n/a

Ultimate Parties

O <UltmtDbtr> Ultimate Debtor

Significant No element present in the L4L to carry this information

No Remittance Information

/ULTD/

For the Ultimate Debtor or Ultimate Creditor

then the mapping will include one of the

following formats...

a) Name + Country + TownName b) Name + Other Id c) Name only d) Other Id only

This results in other data being dropped, for example if Street name & Building Number & Post Code were supplied originally. In CBPR+, the dropping of these structured elements would not be signified using the truncation mark +.UltimateDebtor information prioritized as Name/Country/TownName. TownName is mandatory or (Name/OtherId) or Name alone or OtherId alone

Yes n/a

O <UltmtCdtr> Ultimate Creditor



/ULTC/ For the Ultimate Debtor or Ultimate Creditor

then the mapping will include one of the

following formats...

a) Name + Country + TownName b) Name + Other Id c) Name only d) Other Id only

This results in other data being dropped, for example if Street name & Building Number & Post Code were supplied originally. In CBPR+, the dropping of these structured elements would not be signified using the truncation mark +. UltimateCreditor information prioritized as Name/Country [/TownName]. TownName is optional or

Yes n/a

Initiating Party

O <InitgPty> Initiating Party


Yes n/a n/a n/a n/a

Debtor Party

C <Dbtr/Nm> Debtor Name Significant 140 Characters supported in CBPR+ vs. 66 Characters in CHAPS L4L

No n/a n/a Yes At the end of the Name element

19

C <Dbtr/PstlAdr> Debtor Postal Address

Significant Only Street name, Town name and Country Supported in L4L Structured Address or 3 x 35 of uncstructured address can be mapped. PMPG Guidance should be used to map Structured to Unstructured.


O <Dbtr/Id/OrgId/LEI> Debtor LEI Low Significance

Supplementary data during the transition period

Yes n/a n/a n/a n/a

O <Dbtr/Id/OrgId/Othr> Debtor - Organisation Id - Other

No Significance ID, Scheme name and Issuer sit under this parent element. There are no elements present in the L4L to carry this information.

Yes n/a n/a n/a n/a

O Dbtr/Id/PrvtId/DtAndPlcOfBirth/PrvcOfBirth Debtor - Province of Birth


Yes n/a n/a n/a n/a

O Dbtr/Id/PrvtId/DtAndPlcOfBirth/CityOfBirth

Debtor - City of Birth

No Significance 35 Supported in CBPR+ and 30 supported in CHAPS L4L

No n/a n/a Yes At the end of the element

Creditor Party

C <CdtTrfTxInf/Cdtr/Nm> Creditor Name

Significant 140 Characters supported in CBPR+ vs. 66 Characters in CHAPS L4L


C <CdtTrfTxInf/Cdtr/PstlAdr> Creditor Postal Address

Significant Only Street name, Town name and Country Supported in L4L Structured Address or 3 x 35 of unstructured address can be mapped. PMPG Guidance should be used to map Structured to Unstructured.


20

C <Cdtr/Id/OrgId/LEI> Creditor LEI Low Significance

Supplementary data during the transition period

Yes n/a n/a n/a n/a

C <Cdtr/Id/OrgId/Othr> Creditor - Organisation Id - Other

No Significance ID, Scheme name and Issuer sit under this parent element. There are no elements present in the L4L to carry this information.

Yes n/a n/a n/a n/a

C <Cdtr/Id/PrvtId/DtAndPlcOfBirth> Creditor Date and Place of Birth

Low Significance

Birth Date, Province of Birth, City of Birth, Country of Birth sit under this parent element. There are no elements present in the L4L to carry this information.

Yes n/a n/a n/a n/a

C <Cdtr/Id/PrvtId/Othr> Creditor - Private Id - Other

Low Significance

ID, Scheme name and Issuer sit under this parent element. There are no elements present in the L4L to carry this information.

Yes n/a n/a n/a n/a

Agents - Debtor Agent , Intermediary Agent 1 , Creditor Agent , Charges Information Agent

C <Nm> Name Significant 140 Characters supported in CBPR+ vs. 70 Characters in CHAPS L4L


O <LEI> Legal Entity Identifier

Low Significance

No element present in the L4L to carry this information

Yes n/a n/a n/a n/a

O <PstlAdr> Postal Address

Significant Only Unstructured Address Available 3x35 lines available

No n/a n/a Yes Whenever data is truncated during this mapping due to space limitation, the indicator "+" must be added at the end of the respective line/data element. Data should be prioritised according to the PMPG guidance.`

Accounts (Parties and Agents)

O </Id/Othr> Identification - Other

No Significance Scheme name and Issuer sit under this parent element. There are no elements present in the L4L to carry this information.

Yes n/a n/a n/a n/a

O <Tp> Type No Significance No element present in the L4L to carry this information

Yes n/a n/a n/a n/a

O <Ccy> Currency No Significance No element present in the L4L to carry this information

Yes n/a n/a n/a n/a

21

O <Nm> Name No Significance No element present in the L4L to carry this information

Yes n/a n/a n/a n/a

O <Prxy> Proxy No Significance Type and Id sit under this parent element. No element present in the L4L to carry this information

Yes n/a n/a n/a n/a

Payment information

O <InstrForCdtrAgt> Instruction For Creditor Agent

Significant 140 Characters Supported in CBPR+ and 30 Supported for CHAPS L4L


O <Purp> Purpose Low Significance

CHAPS L4L supports the Proprietary field only

Yes n/a Purpose of Payment should not be provided before 2023 for CHAPS payments.

n/a n/a

O <RgltryRptg> Regulatory Reporting

Significant CBPR permits all elements up to 10 instances, CHAPS L4L supports a single instance of 3x35 chars


O <RltdRmtInf> Related Remittance Information


Yes Remittance Information

/RELID/ - 1 or 2 identifications of the RelatedRemittanceInformation stored outside the message

No Truncation symbol should be at the end of the line prefixed with codeword

O <RmtInf> Remittance Information

Significant Possibility of losing data if other fields are mapped into this element


/URI/ - the MX unstructured remittance information Or (mutually exclusive) /SRI/+ - means that structured remittance information is present in the original message but is not translated.

Yes At the end of the element following the code word

Mapping of Structured Address to Unstructured

For Debtor & Creditor parties (in pacs.008 and in the Underlying Credit Transfer of a pacs.009 COV), CBPR translation of structured address to unstructured has a principle that they

will map the values “2/” and “3/” at the beginning of the address lines that have been translated and place the relevant information within each line (as per the PMPG guidance of

what Postal address is associated to Line 2 vs line 3). It is preferred that Banks follow this principle for these parties including the 2/ or 3/ as it provides better tagging of data for

Sanctions Screening. However, it can be viewed as optional for Banks to use the 2/ & 3/. Therefore it must be possible to receive an unstructured ISO 20022 Address line with this

prefixing logic, however it is not mandatory for all banks to map into the unstructured address in this way. It is acceptable to map the structured address into unstructured by

following the PMPG logic of priority and placing a truncation symbol at the end of each line that has been truncated.

Note that the usage of 2/ & 3/ should not be used when mapping Structured Addresses for Agents.

22

Pacs.004 truncation

Purple text – data could be mapped to Instruction For Next Agent or Instruction For Creditor Agent using MX/MT mapping rules &

codewordsTruncated Data

Significance Information

Remove data with no notification

Map information

to Prefix with Code word

Provide truncation symbol

Truncation symbol to be placed

Payment information

O <OrgnlCreDtTm> Original Creation Date time

Low Significance


Yes n/a n/a n/a n/a

M </Document/PmtRtr/TxInf/OrgnlEndToEndId> Original End to End Id

Significant 35 Characters supported in CBPR and only 16 in CHAPS L4L

No n/a n/a n/a A truncation

symbol should be

present if

truncated

Charges Agent

O </Document/PmtRtr/TxInf/ChrgsInf/Agt Charges Agent

Low Significance

LEI cannot be carried across from CBPR to CHAPS L4L. Name may be truncated and there is no structured postal address supported in the CHAPS L4L

Yes n/a n/a Yes LEI does not need a truncation symbol. Name and Address must have the truncation indicator “+” present where truncation has occurred.

Return Chain

O <PmtRtr/TxInf/RtrChain/UltmtDbtr> Ultimate Debtor

Low Significance

CHAPS L4L holds no ultimate Debtor information

Yes n/a n/a n/a There is no place in the pacs.004 to place the Ultimate Debtor information

M <PmtRtr/TxInf/RtrChain/Dbtr> Debtor – Party information

Significant There is no Party information available in L4L only Agent can be populated. Mapping should be followed as per CHAPS Technical advisory document section 13.3, 13.4 – No truncation symbol required

Yes n/a n/a n/a n/a

O <PmtRtr/TxInf/RtrChain/InitgPty> Initiating Party


Yes n/a n/a n/a n/a

23

O <PmtRtr/TxInf/RtrChain/DbtrAgt> Debtor Agent Significant No element present in the L4L to carry this information

Yes n/a n/a n/a n/a

O <PrvsInstgAgt1> <PrvsInstgAgt2> <PrvsInstgAgt3>

Previous Instructing Agent 1/2/3

Moderate Significance


Yes n/a n/a Yes n/a

O <PrvsInstgAgt1Acct> <PrvsInstgAgt2Acct> <PrvsInstgAgt3Acct>

Previous Instructing Agent 1/2/3 Account


Yes n/a n/a n/a n/a

O <IntrmyAgt1> <IntrmyAgt2> <IntrmyAgt3>

Intermediary Agent 1/2/3

No Significance No element present in the L4L to carry this information - Chains will be built by the bank processing the payment and therefore the information derived for the intermediary by the sending bank should be sufficient.

Yes n/a n/a n/a n/a

O <IntrmyAgt1Acc> <IntrmyAgt2Acc> <IntrmyAgt3Acc>

Intermediary Agent 1/2/3 Account


Yes n/a n/a n/a n/a

<PmtRtr/TxInf/RtrChain/CdtrAgt> Creditor Agent

Significant Mapping should be followed as per CHAPS Technical advisory document section 13.3, 13.4 – No truncation symbol required

Yes n/a n/a n/a n/a

<PmtRtr/TxInf/RtrChain/Cdtr> Creditor Significant There is no Party information available in L4L only Agent can be populated. Mapping should be followed as per CHAPS Technical advisory document section 13.3, 13.4 – No truncation symbol required

Yes n/a n/a n/a n/a

<PmtRtr/TxInf/RtrChain/UltmtCdtr> Ultimate Creditor

Low Significance

CHAPS L4L holds no ultimate Debtor information

Yes n/a n/a n/a n/a

Return reason information

O </PmtRtr/TxInf/RtrRsnlnf/Orgtr> Originator Low Significance

Not present in the CHAPS L4L

Yes n/a n/a n/a n/a

24

Original Transaction Reference

O </PmtRtr/TxInf/OrgnITxRef> Originator Low Significance

Not present in the CHAPS L4L

Yes n/a n/a n/a n/a

CHAPS Enhanced to Like-for-like Additional Technical Guidance

Documents

Transcript of CHAPS Enhanced to Like-for-like Additional Technical Guidance