Transcription
Module 6:ISO pacs.004.001.09& pacs.002.001.10Jill RestifoIsabelle BouilleProduct ManagementBNY Mellon Treasury ServicesProduct ManagementBNY Mellon Treasury ServicesMarch, 2021Information Classification: Public
1.1Module 6 - Agenda1. Introduction2. pacs.004 vs pacs.0023. pacs.004.001.084. pacs.002.001.102Information Classification: Public1.1Welcome and Agenda for the Session1.2Recap of previous training sessions2.1Shall I use a Return of Funds or a Rejection Message ?3.1Scope – pacs.004.001.083.2Return of Funds Message Flows3.3Message Structure and Elements review4.1Scope – pacs.002.001.104.2Rejection Message Flows: Slides 4 & 5 (covered in section 2: pacs.004 vspacs.002)4.2Message Structure and Elements review
1.2Past ModulesDemystifyingISO 20022SWIFT TransactionManagement Platform(September 2020)(November 2020)RTGS Migration PlansCBPR Message Flows(October 2020)Deep Dive pacs.008(December 2020)Deep Dive pacs.009(February 2020)Available for each Module: Learning Guide Links to Webcast Recording Training Deck Enriched Q&A Document3Information Classification: Public
2.1 Difference between a Return and a Reject:pacspainCorp. YAgent A1. pain.001 or elseAgent BcamtAgent CCorp. Z2. pacs.008Settlement: INDA3. pacs.002 (RJCT/AM02)Whenever the payment transaction can not be processed (eg Invalid Currency) and Settlement is not done yet, the pacs.002should be used to reject the payment transaction.4Information Classification: Public
Difference between a Return and a Reject (cont’d):pacspainCorp. YAgent A1. pain.001 or elseAgent BcamtAgent CCorp. Z2. pacs.0083. pacs.008Settlement: INDA4. pacs.002 (RJCT/RR03)5. pacs.004 (RR03)6. camt.0547. camt.053Whenever the payment transaction can not be processed (Missing Creditor Name & Address):Step 4: Settlement was not done by Agent C pacs.002 RJCT must be sentStep 5: Settlement has been done by Agent B pacs.004 must be sent to return the funds5Information Classification: Public
3.1pacs.004.001.09 – Payment Return(FIN MT Equivalent: MT 103/MT 202 Field 72 - /RETN/)Scope:The PaymentReturn message is sent by an agent to the previous agent in the payment chain toundo a payment previously settled.6Information Classification: Public
3.2pacs.004.001.09 – Return of a pacs.008.001.08pacspainAgent ACorp. Y1. pain.001 or elsecamtAgent CAgent BCorp. Z2. pacs.0083. pacs.0084. pacs.004 (eg AC04)5. pacs.004 (eg AC04)6. camt.0547. camt.0537Information Classification: PublicAC04: ClosedAcount Number
3.2pacs.004.001.09 – Return of a pacs.009.001.08pacsAgent AAgent BAgent C1. pacs.0092. pacs.0093. pacs.004 (eg AC04)6. pacs.004 (eg AC04)AC04: ClosedAcount Number8Information Classification: Public
3.2pacs.004.001.09 – Return of a pacs.009.001.08 COVpacspain1. pain.001 or elseCorp. Ycamt2a. pacs.008pacs.002 (Negative)Agent AAgent B3 pacs.009 COV6. Pacs.004Agent C9Information Classification: PublicAgent DCorp. Z
3.3Identification of Agents (Refresher Modules 4 & 5)Financial Institution IdentificationBICFI(0.1)Name(0.1)Structured Address10Information Classification: PublicUnstructured Address
3.3 Identification of Parties (Modules 4 & 5 Refresher)Parties IdentificationName(0.1)Structured Address11Information Classification: PublicUnstructured AddressIdentification(0.1)
3.3 Account Structure (Refresher Modules 4 & 5)IBAN (1.1) or Other (1.1)(New)(New)(New)(New)The Account component is not available for Ultimate Debtor, Ultimate Creditor and Initiating Party12Information Classification: Public
3.3 Settlement Information/Settlement Method (Refresher Modules 4 & 5)Settlement Information(1.1)(New)CLRG (HVPS flow only)COVE (CBPR ) – Not Used in Pacs.004INDA (CBPR )Instructing Agent (0.1)INGA (CBPR )INDA: Settlement Account is maintained by theINSTRUCTED AGENTINGA: Settlement Account is maintained by theINSTRUCTING AGENT13Information Classification: Public
3.3 Identifications: p Header/Message Identification (1.1)Identifies the MX ISO 20022 message – Max 35 charactersPoint to PointTransaction Information/Return Identification (0.1)Identification of the Returned transactionMax 35 charactersEnd to EndOriginal Instruction Identification (0.1)FIN Equivalent: (Field 20) of underlying transaction, i.e. pacs.008/pacs.009Limited to 16 characters to allow smooth translationPoint to PointOriginal End to End Identification (1.1)FIN Equivalent: (Field 21 of MT 202 COV) of underlying transaction, i.e.pacs.008/pacs.009Max 35 charactersEnd to EndOriginal Transaction Identification (0.1)Conditional - Max 35 characters of underlying transaction, i.e. pacs.008/pacs.009End to EndOriginal UETR (1.1)FIN Equivalent: (Field 121, Block 3) of underlying transaction, i.e. pacs.008/pacs.009 –Mandatory – exact 36 characters (validated)End to EndOriginal Clearing System Reference (0.1)(New) – of underlying transaction, i.e. pacs.008/pacs.009Reference allocated by RTGS System – Max 35 charactersFrom RTGS to Direct Member only14Information Classification: Public
3.3 Original Group Information: ormation/OriginalGroupInformationOriginal Message Identification (1.1)Message Identification of underlying transactionOriginal Message Name Identification(1.1)Format of the underlying transaction (eg pacs.008.001.08)Original Creation Date Time (0.1)Creation Date Time of the underlying transaction15Information Classification: Public
3.3 AmountsAmount ElementsSpecificitiesTransaction Information/Original Interbank Settlement AmountInterbank Settlement Amount from Underlying TransactionTransaction Information/Returned Interbank Settlement AmountInterbank Settlement Amount of the Returned TransactionTransaction Information/Returned Instructed AmountInstructed Amount of the Returned TransactionTransaction Information/Charges Information/AmountReturn Transaction ChargesOriginal Transaction Reference/Interbank Settlement AmountInterbank Settlement Amount from Underlying TransactionOriginal Transaction Reference/Amount/Instructed AmountInstructed Amount of the Underlying TransactionOriginal Transaction Reference/Amount/Equivalent AmountAmount expressed in the Debtor’s Account Currency of tje UnderlyingTransactionTotal Returned Interbank Settlement AmountNot Used – Single transactions only are allowed for CBPR and HVPS Compensation AmountNot Used – Used in Direct Debit Transactions16Information Classification: Public
3.3 Return Reason InformationReturn Reason Information/Originator (0.1)Party that issues the Return transactionReturn Reason Information/Reason/Code (1.1)Reason for the Return in coded form (Proprietary/Free text not allowed inCBPR ) – Codes must be contained in ISO Code List published underwww.iso.orgReturn Reason Information/Additional Information (0.2)Additional details about the return in free text (Max 105 Text)17Information Classification: Public
3.3 Return ChainUltimate DebtorDebtorParties involved in the Return TransactionInitiating PartyDebtor AgentPrevious Instructing Agent 1Note: Ultimate Debtor, Debtor, Debtor Agent,Previous Instructing Agent 2Ultimate Creditor, Creditor, Creditor AgentPrevious Instructing Agent 3from the original transaction (pacs.008 orIntermediary Agent 1pacs.009) can be found under OriginalIntermediary Agent 2Intermediary Agent 3Creditor AgentCreditorUltimate Creditor18Information Classification: PublicTransaction Reference block.
3.3 pacs.004.001.09 Message StructureGroup HeaderSet of characteristics shared by all individual transactionsincluded in the message.TransactionInformationInformation concerning the original transactions, to whichthe return message refers.Note: Limited to 1 for CBPR and HVPS mation Classification: PublicKey elements used to identify the original transactionthat is being referred to.
Available under CreditTransfer TransactionInformationElement removedin pacs.004 CBPR 20Information Classification: PublicMessage Identification1.1Creation Date Time1.1Autorisation0.2Batch Booking0.1Number of Transactions1.1Control Sum0.1Group Return0.1Total Returned Settlement Amount0.1Interbank Settlement Date0.1Settlement Information 1.1Settlement Information1.1Settlement Method (Slide 13)1.1Instructing Agent0.1Settlement Account (Slide 12)0.1Instructed Agent0.1Clearing System0.1Instructing Reimbursement Agent0.1Instructing Reimbursement Agent Account0.1Instructed Reimbursement Agent0.1Instructed Reimbursement Agent Account0.1Third Reimbursement Agent0.1Third Rimbursement Agent Account0.1
21Returned Instructed Amount (Slide 16)0.1Exchange Rate0.1Charge Bearer0.1Charges Information0.*Instructing Agent1.1Instructed Agent1.1Return Chain (Slide 18)1.1Return Reason Information (Slide 17)1.1Information Classification: PublicReturn Identification (Slide 14)0.1Original Group Information (Slide 15)0.1Original Instruction Identification (Slide 14)0.1Original End to End Identification (Slide 14)1.1Original Transaction Identification (Slide 14)0.1Original UETR (Slide 14)1.1Original Clearing System Reference (Slide 14)0.1Original Interbank Settlement Amount (Slide 16)0.1Original Interbank Settlement Date0.1Returned Interbank Settlement Amount (Slide 16)1.1
Copy of elements from the underlying payment transaction, i.e.:Please refer to Module 4:pacs.008 Deep DivePlease refer to Module 5:pacs.009 Deep Dive22Information Classification: Public
4.1pacs.002.001.10 – FI to FI Payment Status ReportScope:The FIToFIPaymentStatusReport message is sent by an instructed agent to the previous party in thepayment chain. It is used to inform this party about the positive or negative status of an instruction(either single or file). It is also used to report on a pending instruction.23Information Classification: Public
4.3 pacs.002.001.10 Message StructureGroup HeaderSet of characteristics shared by all individual transactionsincluded in the status report message.TransactionInformation &StatusInformation concerning the original transactions, to which thestatus report message refers.Note: Limited to 1 for CBPR and HVPS mation Classification: PublicKey elements used to identify the original transactionthat is being referred to (copy of the pacs.008/pacs.009elements)Note: Not used for CBPR and HVPS transactions
4.3 Original Group Information: ormation/OriginalGroupInformationOriginal Message Identification (1.1)Message Identification of underlying transactionOriginal Message Name Identification(1.1)Format of the underlying transaction (eg pacs.008.001.08)Original Creation Date Time (0.1)Creation Date Time of the underlying transaction25Information Classification: Public
4.3 Identifications: p Header/Message Identification (1.1)Identifies the MX ISO 20022 message – Max 35 charactersPoint to PointTransaction Information/Status Identification (0.1) – Not used in CBPR Identification of the Reported StatusMax 35 charactersEnd to EndOriginal Instruction Identification (1.1)FIN Equivalent: (Field 20) of underlying transaction, i.e. pacs.008/pacs.009Limited to 16 characters to allow smooth translationPoint to PointOriginal End to End Identification (1.1)FIN Equivalent: (Field 21 of MT 202 COV) of underlying transaction, i.e.pacs.008/pacs.009Max 35 charactersEnd to EndOriginal Transaction Identification (0.1)(New) – Conditional - Max 35 characters of underlying transaction, i.e.pacs.008/pacs.009End to EndOriginal UETR (1.1)FIN Equivalent: (Field 121, Block 3) of underlying transaction, i.e. pacs.008/pacs.009 –Mandatory – exact 36 characters (validated)End to EndClearing System Reference (0.1)(New) – of underlying transaction, i.e. pacs.008/pacs.009Reference allocated by RTGS System – Max 35 charactersFrom RTGS to Direct Member only26Information Classification: Public
3.3 Transaction Status: « Specifies the status of a transaction, in a coded form”PositiveLogicalOrder1. RCVD2. ACTC3. ACCP4. ACWC5. ACSP6. ACSC7. ACCCNotes: If TransactionStatus/Code equals RJCT, then “Status Reason Information/Reason” is mandatory.27Information Classification: Public
3.3 Status Reason InformationStatus Reason Information/Originator (0.1)Party that issues the StatusStatus Reason Information/Reason/Code (1.1)Reason for the status report – If codes are used, these must be containedin the ISO Code List published under www.iso.orgStatus Reason Information/Additional Information (0.2)Additional details about the status reason28Information Classification: Public
Element removedin pacs.002 CBPR 29Information Classification: PublicMessage Identification1.1Creation Date Time1.1Instructing Agent0.1Instructed Agent0.1
Not used in CBPR Element removedin pacs.002 CBPR 30Information Classification: PublicStatus Identification0.1Original Group Information (Slide 26)0.1Original Instruction Identification (Slide 27)0.1Original End to End Identification (Slide 27)1.1Original Transaction Identification (Slide 27)0.1Original UETR (Slide 27)1.1Transaction Status (Slide 28)1.1Status Reason Information (Slide 29)0.1Charge Information0.*Acceptance Date Time0.1Effective Interbank Settlement Date0.1Account Service Reference0.1Clearing System Reference (Slide 27)0.1Instructing Agent1.1Instructed Agent1.1
Next Module: Reporting messagesNext training module will be available from Monday, April 26, 2021Module 7:Deep Dive: camt.054 (equivalent to MT 900/MT 910) and camt.053 (equivalent to MT940/MT 950) Scope & Message Flows Message Structure & ContentPLEASE SEND YOUR QUESTIONS ON TODAY’S OR PREVIOUS MODULES TOiso20022migration@bnymellon.com31Information Classification: Public
Disclosures & DisclaimersBNY Mellon is the corporate brand of The Bank of New York Mellon Corporation and may also be used as a generic term to reference theCorporation as a whole or its various subsidiaries generally and may include The Bank of New York Mellon 240 Greenwich Street, NewYork, New York 10286, a banking corporation organized and existing pursuant to the laws of the State of New York and operating in Englandthrough its branch at One Canada Square, London E14 5AL, England. BNY Mellon has various subsidiaries, affiliates, branches andrepresentative offices in the Asia Pacific Region which are subject to regulation by the relevant local regulator in that jurisdiction. Theinformation contained in this presentation is for use by wholesale clients only and is not to be relied upon by retail clients. Not all productsand services are offered at all locations.This presentation, which may be considered advertising, is for general information and reference purposes only and is not intended toprovide legal, tax, accounting, investment, financial or other professional advice on any matter, and is not to be used as such. BNY Mellondoes not warrant or guarantee the accuracy or completeness of, nor undertake to update or amend the information or data containedherein. We expressly disclaim any liability whatsoever for any loss howsoever arising from or in reliance upon any of this information ordata.Trademarks and logos belong to their respective owners. This material may not be reproduced or disseminated in any form without the priorwritten permission of BNY Mellon. 2020 The Bank of New York Mellon Corporation. All rights reserved.32Information Classification: PublicDecember 2020
33Information Classification: Public
5 Information Classification: Public pain pacs camt Corp. Y Agent A Agent C Corp. Z Whenever the payment transaction can not be processed (Missing Creditor Name & Address): Step 4: Settlement was not done by Agent C pacs.002 RJCT must be sent Step 5: Settlement has been done by Agent B pacs.004 must be sent to return the funds 2. pacs.008
