AI Drafter 
TaxTMI 
TaxTMI 
Adoption of ISO 20022 messaging standard in Next Generation RTGS (NG-RTGS) system
X X X X Extracts X X X X
X X X X Extracts X X X X
....doption of ISO 20022 messaging standard in Next Generation RTGS (NG-RTGS) system <br>FEMA & RBI<br>Dated:- 31-12-2012<br><BR>RBI/2012 -13/355 DPSS (CO) RTGS No. 1052/04.04.017/2012-13 December 31, 2012 The Chairman and Managing Director/Chief Executive Officer of all RTGS participants Dear Sir/Madam, In the Second Quarter Review of Monetary Policy 2011-12 it was announced that the NG-RTGS system would be developed using extensible markup language (XML) messages conforming to ISO 20022 standards. 2. Accordingly, a Working Group with members from select banks, IDRBT, NPCI and CCIL and RBI was constituted in May 2012 to identify the business requirements, examine the technical feasibility of adopting the ISO 20022 compliant message formats. The message formats suggested by the Working Group were validated by ISO Standards Certification Authority as being compliant with ISO 20022 standards. The Working Group also examined the timeframe that would be required by the various stakeholders for adopting of the ISO 20022 message formats and suggested a time frame of three months for implementation. 3. In view of the above, it has since been decided to adopt these message formats for t....
X X X X Extracts X X X X
X X X X Extracts X X X X
....he proposed NG-RTGS system which would replace the existing RTGS system. The ISO 20022 compliant message formats for the NG-RTGS system. You are advised to download the same and ensure that the infrastructure at your end enables handling of the ISO message formats by March 31, 2013. This URL 4. The Reserve Bank would be conducting awareness and training workshops for RTGS members for the NG RTGS system. A separate communication in this regard will be sent by our Department of Information Technology. 5. As stated in Para 3, all RTGS members will have to be ready by March 31, 2013 with the technical capabilities to handle ISO 20022 message format to participate in NG-RTGS system. Please acknowledge receipt and confirm initiating necessary action within 7 days of receipt of this letter. Yours faithfully, (Vijay Chugh) Chief General Manager ============= Document 1à¤à¤¾à¤°à¤¤à¥€à¤¯ RESERVE रिज़रà¥à¤µ BANK OF ISO20022 standard Message Implementation ISO20022 Business Application Header ISO Message: "head.001.001.01 BusinessApplicationHeaderV01" ISO20022 Message - head.001.001.01 BusinessApplication He XML tag Description aderV01 Mess....
X X X X Extracts X X X X
X X X X Extracts X X X X
....age Item Index ISO RTGS Rules Multi /NEFT Multi From Root tag The sending MessagingEndpoin It that has created this Business Message for the receiving MessagingEndpoin t that will process [1..1] [1..1] 2.0 [1..1] [1..1] Example Data Type this Business Message. FinancialInstitutionlde Identification of 2.34 [0..1] [1..1] ntification a financial institution ClearingSystemMemb ClearingSystemM 2.37 emberIdentificati [0..1] [1..1] on Member Identification IFSC of the 2.41 [1..1] [1..1] Sending participant CANB0239777 Max35Te Το The 3.0 [1..1] [1..1] MessagingEndpoin t designated by the sending MessagingEndpoin t to be the recipient who will ultimately process Reserve Bank of India ISO Message, "head.001.001.01 BusinessApplication HeaderV01" 1 • à¤à¤¾à¤°à¤¤à¥€à¤¯ RESERVE रिज़रà¥à¤µ BANK OF ISO20022 Message - head.001.001.01 BusinessApplication He aderV01 Message Item ISO20022 standard Message Implementation XML tag Description Index ISO RTGS Rules Multi /NEFT Multi this Business Message FinancialInstitutionlde Identification of 3.34 [0..1] [1..1] ntification a financial institution ClearingSystemMemb ClearingSystemM 3.37 [....
X X X X Extracts X X X X
X X X X Extracts X X X X
....0..1] [1..1] emberIdentificati on Member Identification IFSC of the 3.41 [1..1] [1..1] Sending participant Example Data Type Mmbld> HDFC0239777FinInstnld> Validation are: Character position First four Information Bank code characters Fifth character Zero Branch code BusinessMessagelden Uniquely 4.0 [1..1] [1..1] tifier identifies the business Same as Messageldentification in the associated business message Last six characters HDFC201210180000000 218 message MessageDefinitionIde ntifier Message Identifier 5.0 [1..1] [1..1] BusinessService Business service 6.0 [0..1] [1..1] Contains the Messageldentifier that defines the Business Message as published on the ISO 20022 website. E.g. pacs.008.001.03 Comprises a fixed value of "RTGS", and in the case of BAH for pacs.008 and pacs.009 the fixed value of "RTGS" must be followed by the pacs.008.001.03 RTGS Reserve Bank of India ISO Message, "head.001.001.01 BusinessApplicationHeaderV01†Max35Te xt Max35Te xt Max35Te xt Max35Te xt • à¤à¤¾à¤°à¤¤à¥€à¤¯ RESERVE रिज़रà¥à¤µ BANK OF ISO20022 Message - head.001.001.01 BusinessApplication He aderV01 Message Item ISO20022 standard Messag....
X X X X Extracts X X X X
X X X X Extracts X X X X
....e Implementation XML tag Description Index ISO RTGS Rules Multi /NEFT Multi Reserve Bank of India ISO Message, "head.001.001.01 BusinessApplicationHeaderV01" Example Data Type local instrument name, i.e. for RTGS, BAH for pacs.008: 'RTGSFITOFICustomerCredit'. For RTGS, BAH for pacs.009: -'RTGSFITOFICredit' or -'RTGSOwnAccTtransfer' or -'RTGSNetSettlementXXzNN' Where 'XX' is the clearing type which may take values 'GC', 'IB', 'FX', MC, SE, OT & so on. 'z' is the indicator which may take values C-Original, R-Return, L-Last Return. "NN" is the return serial. "GC" stands for guaranteed settlement of Securities and CBLO segment. "IB" stands for guaranteed settlement of FOREX segment. "FX" stands for non guaranteed settlement. "MC" Stands for MICR Clearing "SE" stands for non-guaranteed MNSB "OT" stands for Other MNSB 3 • à¤à¤¾à¤°à¤¤à¥€à¤¯ RESERVE रिज़रà¥à¤µ BANK OF ISO20022 Message - head.001.001.01 BusinessApplication He aderV01 Message Item CreationDate ISO20022 standard Message Implementation XML tag Description Index ISO RTGS Rules Multi /NEFT Multi Date and time 7.0 [1..1] [1..1] Time up to seconds only when this Business Messag....
X X X X Extracts X X X X
X X X X Extracts X X X X
....e (header) Example Data Type 2012-09-30T09:50Z ISONorm alisedDat eTime was created. CopyDuplicate Indicates 8.0 [0..1] [0..1] DUPL Duplicate(Message is for DUPL Code whether the information/confirmation message is a purposes. It is a duplicate of a Copy, a Duplicate or a copy of a duplicate of a previously sent ISO message previously sent). Valid Values are: CODU COPY DUPL Signature 20022 Message. Contains the digital signature of the Business 11.0 [0..1] [0..1] Entity authorised to sign this Business Message. Related Specifies the 12.0 [0..1] [0..1] Business Application Header of the Business Message to which this Business Reserve Bank of India ISO Message, "head.001.001.01 BusinessApplication HeaderV01" 4 Optional (possibly future use) XML digital signature http://www.w3.org/2000/09/xml dsig# The Sgntr block contains the following elements. Message XML Tag item XMLSigna tures • à¤à¤¾à¤°à¤¤à¥€à¤¯ RESERVE रिज़रà¥à¤µ BANK OF ISO20022 Message - head.001.001.01 BusinessApplication He aderV01 Message Item ISO20022 standard Message Implementation XML tag Description Message relates. Can be used when replying to a query; can also I....
X X X X Extracts X X X X
X X X X Extracts X X X X
....ndex ISO RTGS Rules Multi /NEFT Multi be used when canceling or amending. From Element 12.2 [1..1] [1..1] Content is identical to description is same as that provided for the corresponding element content found in BAH of the message to which this BAH (and the business message) is in response to. Example Data Type same element above. This message item is the part of the Rltd block. To -As Above- 12.53 [1..1] [1..1] -As Above- BusinessMessagelden -As Above- 12.104 [1..1] [1..1] -As Above- Max35Te tifier xt MessageDefinitionlde -As Above- 12.105 [1..1] [1..1] -As Above- Max35Te ntifier xt Business Service -As Above- 12.106 [0..1] [0..1] -As Above- Max35Te xt Creation Date -As Above- 12.107 [1..1] [1..1] -As Above- ISONorm CopyDuplicate -As Above- 12.108 [0..1] [0..1] -As Above- Reserve Bank of India ISO Message, "head.001.001.01 BusinessApplication HeaderV01" 5 alisedDat eTime Code â—â—. à¤à¤¾à¤°à¤¤à¥€à¤¯ रिज़रà¥à¤µ RESERVE BANK OF ISO20022 standard Message Implementation Customer Credit Transfer ISO Message: "pacs.008.001.03 FITOFICustomerCreditTransferV03" * Applicable Areas: RTGS and NEFT i) For defining Customer Trans....
X X X X Extracts X X X X
X X X X Extracts X X X X
....action Messages in RTGS (ii) For defining Outward Debit Message in NEFT (iii) For Defining Credit List message in NEFT originating from RBI This message formats would replace the current R41 used in current RTGS. *Corresponds to R41 in current RTGS, N06 and NO2 in NEFT. ISO 20022 The ISO 20022 Business Message consists of two parts: (1) ISO 20022 Business Appl. Header (2) ISO 20022 Messages Business Appl. Header ISO 20022 Message Business Message Business Application Header is a business header and should not be confused with a file or transport header. It is created before the transport routing header is applied to the business message and is retained after the transport header is removed. So any parties between the two business applications that don't perform a business function are not mentioned in the BAH. Such 'technical' middle men don't open or change the Business Message; they only forward it to the correct business application. Although the BAH is not the transport header, data in the BAH can be used by transport applications to determine the routing header since it does contain the business sender, receiver and document details. It can also be used by the business appl....
X X X X Extracts X X X X
X X X X Extracts X X X X
....ications to determine the appropriate process to perform on the business message. Message fields description ISO Business Application Header Business Application Header (Refer related documentation “RBI_NG_RTGS_ISO20022_BusinessApplication Header") Reserve Bank of India ISO 20022 Message, "pacs.008.001.03 FITOFICustomerCreditTransferV03" 1| Page â— à¤à¤¾à¤°à¤¤à¥€à¤¯ रज़रà¥à¤µ बैंक. RESERVE BANK OF ISO 20022 Message Map ping ISO20022 Message - XML tag FITOFICustomerCre ditTransferV03 Message Item FITOFICustomerCred itTransfer ISO20022 standard Message Implementation Description Index ISO RTGS/ Rules Multi NEFT Multi Message Root tag for Creation Date & Time GROUP HEADER - GROUP HEADER Message Identification FITOFICustomer CreditTransfer Example Data Type GroupHeader Fields common 1.0 [1..1] [1..1] to all the transaction in the message Messageldentificati on Point to point 1.1 [1..1] [1..1] Uniquely identifies message Max35Text reference, as HDFC201210181000000218 account servicing Messageldentification be structured as: institution, and sent to the account owner or the party authorised to receive the mess....
X X X X Extracts X X X X
X X X X Extracts X X X X
....age, to unambiguously identify the message. XXXX-Sender IFSC [4] YYYYMMDD - Creation Date Reverse [8] X-Channel [1] nnnnnnnnn- Sequence Number [9] The values of Channel Identification (X) is the same as defined for TransactionIdentification Creation DateTime Payment origination date time 1.2 [1..1] [1..1] Time up to seconds only 2011-04- 24T09:30:32 ISODateTime Date and time at which the Reserve Bank of India ISO 20022 Message, “pacs.008.001.03 FITOFICustomerCreditTransferV03" 2|Page 4. à¤à¤¾à¤°à¤¤à¥€à¤¯ रिज़रà¥à¤µ जरà¥à¤µ बैंक - 1 BANK RESERVE B No. of Txs. Settlement Settlement Information OF ISO20022 standard Message Implementation NumberOfTransacti ons message was created. TotallnterbankSettl ementAmount Number of transaction 1.4 [1..1] [1..1] Always 1 for customer payment in RTGS system and 10 or more for NEFT 1 Max15Numer icText 1.6 [0..1] | [1..1] Total amount transferred between debtor and creditor Amount Total Settlement Amount + Currency 3400.00 Currency as per the ISO 4217 list 2011-04- 24 InterbankSettlemen SettlementInformat ion Details on how 1.8 settlement of transaction....
X X X X Extracts X X X X
X X X X Extracts X X X X
.... [1..1] [1..1] happens Settlement Method Method used to settle payments [1..1] [1..1] Must be CLRG (i.e., Settlement done through a payment CLRG Code clearing system) Other Codes are: CLRG, COVE, INDA, INGA InstructingAgent Agent that instructs the next party in 1.21 [0..1] [1..1] Mandatory in RTGS implementation the chain to carry out the (set of) instruction(s). FinancialInstitutionl dentification ClearingSystemMe Reserve Bank of India ISO 20022 Message, "pacs.008.001.03 FITOFICustomerCreditTransferV03" [1..1] [1..1] [0..1] [1..1] 3| Page INFOR CREDIT TRANSFER MATION Payment Identification RESERVE रिज़रà¥à¤µ BANK OF ISO20022 standard Message Implementation Member Identification IFSC of the Sending [1..1] | [1..1] Sender IFSC HDFC02397 77 Instructed Agent Agent that is instructed by the previous party in the chain to 1.22 [0..1] [1..1] Mandatory in RTGS implementation FinancialInstitutionl carry out the (set of) instruction(s). [1..1] │[1..1] dentification ClearingSystemMe Member Identification IFSC of the Receiving participant [1..1] │[1..1] Receiver IFSC CreditTransferTrans actionInformation information on [1..n ] [1..1] indivi....
X X X X Extracts X X X X
X X X X Extracts X X X X
....dual transactions PaymentIdentificati on Contains references to a payment 2.1 [1..1] | [1..1] Reserve Bank of India ISO 20022 Message, “pacs.008.001.03 FIToFICustomerCreditTransferV03" Only one occurrence allowed for Customer Payment in RTGS system and 10 or more for NEFT. HDFC02397 77 4| Page â—â— à¤à¤¾à¤°à¤¤à¥€à¤¯ RESERVE रिज़रà¥à¤µ BANK OF EndToEndIdentificat ion ISO20022 standard Message Implementation Identification (Related Reference) 2.3 [1..1] [1..1] TransactionIdentific ation Transaction Identification 2.4 [1..1] | [1..1] Unique identification, as assigned by the bank's customer, to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain to the beneficiary. For MT101, this field corresponds to field 21( Related Reference) For MT103 this field corresponds to field 70 (Remittance Information) with codeword ROC (Ordering customer's reference). If field 70 does not carry this optional reference, then field 20 (Sender's Reference) should be used. For MT202 COV, this field corresponds to field 21(Related Reference). If not known a fixed value of....
X X X X Extracts X X X X
X X X X Extracts X X X X
.... 'NOTPROVIDED' must be used. As per the description, it should be unique transaction reference to identify the transaction. Use UTR (Unique Transaction Reference) format (22 characters) XXXX-Sender IFSC TREF23121354 Max35Text 65781 HDFCR12012042400000023 [4] Max35Text Reserve Bank of India ISO 20022 Message, “pacs.008.001.03 FITOFICustomerCreditTransferV03" 5| Page Payment Information 4. à¤à¤¾à¤°à¤¤à¥€à¤¯ रिज़रà¥à¤µ RESERVE BA BANK OF mation InstructionPriority ISO20022 standard Message Implementation PaymentTypeInfor Payment 2.6 [0..1] [1..1] Information Instruction Priority 2.7 [0..1] [1..1] Reserve Bank of India ISO 20022 Message, “pacs.008.001.03 FIToFICustomerCreditTransferV03" X-Payment System X-Channel YYYYMMDD-Date [8] [1] [1] [8] nnnnnnnn-Sequence Number Unique identification, as assigned by the first instructing agent, to unambiguously identify the transaction that is passed on, unchanged, throughout the entire interbank chain. Usage: The transaction identification can be used for reconciliation, tracking or to link tasks relating to the transaction on the interbank level. Usage: The instructing agent has to m....
X X X X Extracts X X X X
X X X X Extracts X X X X
....ake sure that the transaction identification is unique for a pre-agreed period. Priority is mandatory in RTGS implementation HIGH / NORM Indicator of the urgency or order of importance that the instructing party would like the instructed party to apply to the processing of the instruction at application level. Priority "NORM" will result in liquidity Savings. In FAQ Channels are mentioned as ATM, Internet banking etc., Codes for Payment System (X) are: R->RTGS N->NEFT A-> ACH For Further Information on Channel, pl refer to FAQ on Channel. HIGH Code 6 | Page रिज़रà¥à¤µ बैंक. 4. à¤à¤¾à¤°à¤¤à¥€à¤¯ V RESERVE OF BANK ISO20022 standard Message Implementation ServiceLevel Service level 2.9 [0..1] [0..1] HIGH: Priority Level is high. NORM: Priority Level is normal Default is HIGH. Agreement under which or rules under which the transaction should be processed. Proprietary Proprietary Service Level Code 2.11 [0..1] [1..1] For RTGS processing priority is 80 in range 00-99. LocalInstrument Local instrument type (User 2.12 [0..1] [1..1] To be used for managing queues by sending bank before settlement. community specific in....
X X X X Extracts X X X X
X X X X Extracts X X X X
....strument.) Proprietary Proprietary 2.13 [0..1] [1..1] instrument type code Type of local instrument. For RTGS pacs.008 use: 'FITOFICustomerCredit' CategoryPurpose Purpose of the 2.15 [0..1] | [1..1] Instrument. Payment purpose must be a value listed Reserve Bank of India ISO 20022 Message, “pacs.008.001.03 FITOFICustomerCreditTransferV03" Max35Text (For RTGS lower the number highest will be the priority. For Banks priority range is from 11 to 99. Priority from 00 to 10 is reserved for RBI. FITOFICustomerCredit Max35Text 7| Page 4. à¤à¤¾à¤°à¤¤à¥€à¤¯ रिज़रà¥à¤µ BANK RESERVE BA OF ISO20022 standard Message Implementation in ISO category purpose code Code ISO External category purpose code 2.16 [1..1] [1..1] FROM ISO 20022External Code OTHR list Code (Max4Text) list. Codes are "SALA - SalaryPayment, Loan-Loan, PENS- Pension Paymen t, etc. Details in 3.55 of UNIFI (ISO20022) Msg Definition Rpt. The following codes are available. CASH: CashManagementTransfer CORT: TradeSettlementPayment DIVI: Dividend GOVT: GovernmentPayment HEDG: Hedging INTC: IntraCompanyPayment INTE: Interest LOAN: Loan PENS: PensionPayment SALA: SalaryPayment....
X X X X Extracts X X X X
X X X X Extracts X X X X
.... SECU: Securities SSBE: SocialSecurityBenefit SUPP: SupplierPayment TAXS: TaxPayment TRAD: Trade TREA: TreasuryPayment VATX: ValueAddedTaxPayment WHLD: WithHolding OTHR: Other The generic code for the normal funds transfer may be 'OTHR'. This code will be the default purpose code which stands for "Other Payment Purpose". Example: OTHR Reserve Bank of India ISO 20022 Message, “pacs.008.001.03 FIToFICustomerCreditTransferV03" 8| Page 4. à¤à¤¾à¤°à¤¤à¥€à¤¯ रिज़रà¥à¤µ बैंक। RESERVE Charge Bearer Interbank Settlement Amt Charges Information BANK OF InterbankSettlemen tAmount Amt> ChargeBearer ISO20022 standard Message Implementation For additional codes, please refer to document ExternalcodeLists_3Q2012_22 Oct2012_v4.xls available at www.iso20222.org Banks to suggest additional India Specific codes . 3400.00 Amount Code 2.33 [1..1] │[1..1] =CRED/DEBT/SH AR/SLEV Codes & meanings are: DEBT -> BorneByDebtor CRED-> BorneByCreditor SHAR-> Shared DEBT Code ChargesInformation | Amount 2.34 [0..*] | [0..1] Transaction charges to be paid by the charge bearer. 2.35 [1..1] [1..1] Reserve Bank of India ISO 200....
X X X X Extracts X X X X
X X X X Extracts X X X X
....22 Message, “pacs.008.001.03 FITOFICustomerCreditTransferV03" SLEV-> FollowingServiceLevel If ChargeBearer contains DEBT, then ChargesInformation may be present If ChargeBearer contains CRED, then at least one occurrence of ChargesInformation must be present If ChargeBearer contains SHAR or SLEV, then ChargesInformation is optional. 5000.00 9| Page Amount 4. à¤à¤¾à¤°à¤¤à¥€à¤¯ RESERVE (ORD ERIN Debtor's A/c (Ordering Customer's A/C) Debtor (Ordering Customer) रिज़रà¥à¤µ BANK OF Agent ISO20022 standard Message Implementation 2.36 [1..1] [1..1] Agent that takes the transaction charges or to which the transaction charges are due. FinancialInstitution Identification ClearingSystemMe [1..1] | [1..1] [0..1] |│[1..1] Member [1..1] | [1..1] Max35Text Identification Debtor Name ORDERING CUSTOMER Ordering Customer's Name 2.49 [1..1] | [1..1] [0..1] [1..1] Name is mandatory Umesh Kapoor Max140Text PostalAddress Ordering Customer's [0..1] | [0..1] Postal Address AddressLine Adress in free [0..7] [0..4] form text Number of occurrences is restricted to 4 in RTGS implementation. Boulevard Road Max70Text DebtorAccount Identificati....
X X X X Extracts X X X X
X X X X Extracts X X X X
....on of 2.50 [0..1] [1..1] the account of the debtor to which a debit entry will be made as a result of the transaction. Identification Other Identification [1..1] [1..1] Debtor's [1..1] [1..1] [1..1] [1..1] Account number DebtorAgent ORDERING INSTITUTION 2.51 [1..1] |│[1..1] Pl see FAQ for more details on DebtorAgent Reserve Bank of India ISO 20022 Message, “pacs.008.001.03 FITOFICustomerCreditTransferV03" 265385644663 Max35Text 10 Page रज़रà¥à¤µ बैंक 4. à¤à¤¾à¤°à¤¤à¥€à¤¯ OF BANK RESERVE BA Creditor's Agent (BENEFICIARY INSTITUTION) ISO20022 standard Message Implementation (Financial institution servicing an (i.e Sub-Member) For Participant, IFSC account for the debtor.) FinancialInstitutionl [1..1] │[1..1] dentification ClearingSystemIden dentification Member Indian FinancialS 2.1.6 [1..1] [1..1] Identification ystemCodelden For Participant, IFSC code to be HDFC02397 tifier for participants / Name and Identification for non IFSC, or Name and Other Identification with optional Address. 77> Name Participants is mandatory Ordering [0..1] [0..1] Institution Name Ordering Institution Optional. To ....
X X X X Extracts X X X X
X X X X Extracts X X X X
....be filled if Ordering Customer is other than the Sender of the msg. Bank A Max140Text [0..1] [0..1] PostalAddress Postal Address AddressLine Address in free format text [0..7] [0..4] CreditorAgent Beneficiary Institution identification 2.53 [1..1] | [1..1] FinancialInstitutionl dentification ClearingSystemMe Corn Exchange 5th Floor Mark Lane 55 GB Max70Text 11 | Page 4. à¤à¤¾à¤°à¤¤à¥€à¤¯ RESERVE Creditor's A/c (BENEFICIARY CUSTOMER'S A/C) Creditor (BENEFICIARY CUSTOMER) रिज़रà¥à¤µ BANK OF mberIdentification Member Identification ISO20022 standard Message Implementation dentification d> Indian FinancialS ystemCodelden tifier [1..1] [1..1] For Participant, IFSC code to be HDFC02397 77 Name Beneficiary have IFSC code), Name and Other Identification to be keyed in.. [0..1] [0..1] Bank B Max140Text Institution Name Creditor Beneficiary Customer Information 2.55 [1..1] |│[1..1] Name Beneficiary Customer PostalAddress Name Beneficiary Customer's Postal Address AddressLine Adress in free form text CreditorAccount Beneficiary Institution identification [0..1] [1..1] Mandatory in view of Indian Beneficiary Max70Text Context (....
X X X X Extracts X X X X
X X X X Extracts X X X X
....Ref. Circular issued by RBI) [0..1] [0..1] Optional Field. Enter Beneficiary customer Address if reqd. [0..7] [0..4] Number of occurrence is restricted to 4. Boulevard Road Max70Text 2.56 [0..1] |│[1..1] Mandatory in RTGS implementation Identification Other [1..1] [1..1] ClearingSysteml [1..1] [1..1] Identification dentification Indian FinancialS ystemCodelden [1..1] [1..1] Existing account number 2147743292 Max35Text tifier Currency Identification of [0..1] [0..1] the currency in which account is held For NG-RTGS, "INR" is the only currency that can be specified. INR Code Reserve Bank of India ISO 20022 Message, "pacs.008.001.03 FITOFI CustomerCreditTransferV03" 12 Page RESERVE Beneficiary Information Instruction For Creditor Agent रिज़रà¥à¤µ BANK OF Customer Information InstructionForCredit orAgent ISO20022 standard Message Implementation Beneficiary 2.58 [0..n] |│[0..2] Code Coded information related to the 2.59 [0..1] [0..1] PHOB = Phone Beneficiary Pl see FAQ for other Codes PHOB Max4Text processing of the payment instrument, provided by the initiating party. RemittanceInforma tion Beneficiary 2.69 [0..1] [0..1] Customer's Unstruc....
X X X X Extracts X X X X
X X X X Extracts X X X X
....tured Postal Address Remittance Information 140 2.69 [0..n] [0..4] Size restricted to a maximum of Max140Text 4 repeats of 140 characters. characters up to 4 can be used Sender to Receiver Information Note:- [1..1] -> Mandatory; [0..1] -> Optional; [1..n] -> Mandatory and n times repeated; [0..n] -> Optional and n times repeated; Reserve Bank of India ISO 20022 Message, “pacs.008.001.03 FIToFICustomerCreditTransferV03" 13 | Page ४. à¤à¤¾à¤°à¤¤à¥€à¤¯ रिज़रà¥à¤µ बैंक RESERVE BANK OF IN ISO20022 standard Message Implementation Customer Debit Credit Notification ISO Message "camt.054.001.003 BankToCustomerDebit CreditNotificationV03" Applicable Areas: RTGS & NEFT 1. For defining Debit Notification in MNSB (RTGS) 2. For defining Credit Notification in MNSB (RTGS) The ISO 20022 Business Message consists of two parts: (1) ISO 20022 Business Appl. Header (2) ISO 20022 Messages ISO 20022 Business Appl. Header ISO 20022 Business Message Message Business Application Header is a business header and should not be confused with a file or transport header. It is created before the transport routing header is applie....
X X X X Extracts X X X X
X X X X Extracts X X X X
....d to the business message and is retained after the transport header is removed. So any parties between the two business applications that don't perform a business function are not mentioned in the BAH. Such 'technical' middle men don't open or change the Business Message; they only forward it to the correct business application. Although the BAH is not the transport header, data in the BAH can be used by transport applications to determine the routing header since it does contain the business sender, receiver and document details. It can also be used by the business applications to determine the appropriate process to perform on the business message. Message fields description ISO Business Application Header Business Application Header (Refer related documentation “RBI_NG_RTGS_ISO20022_BusinessApplicationHeader") ISO 20022 Message Reserve Bank of India ISO Messages, "camt.054.001.03 BanktoCustomerDebit Credit NotificationV03" 1| Page à¤à¤¾à¤°à¤¤à¥€ रिज़रà¥à¤µ बैंक BANK RESERVE B OF IND ISO20022 Message - camt.054.001.03 BankToCustomerDebitCredit NotificationV03 Message Item ISO20022 standard Message Implementa....
X X X X Extracts X X X X
X X X X Extracts X X X X
....tion XML tag Description Index ISO RTGS Rules Multi /NEFT Multi GroupHeader Fields common to all the transaction in the message 1.0 [1..1] [1..1] Messageldentification Uniquely identifies the message Example Data Type 1.1 [1..1] [1..1] Uniquely identifies message Max35Text HDFC201210181000000218 Recommend Messageldentification be structured as: XXXX-Sender IFSC Creation DateTime Payment origination 1.2 [1..1] [1..1] date time Notification Notifies debit and 2.0 [1..n] credit entries for [1..1] or [1..10] the account. This msg element is the part of the Ntfctn block. Identification Unique 2.1 [1..1] [1..1] identification, as assigned by the account servicer, to unambiguously identify the account notification. Creation DateTime Date and time at which the message was created. 2.5 [1..1] [1..1] This msg element is the part of the Reserve Bank of India ISO Messages, "camt.054.001.03 BanktoCustomer Debit Credit NotificationV03" YYYYMMDD - Creation Date Reverse [8] X-Channel [4] [1] nnnnnnnnn-Sequence Number [9] The values of Channel Identification (X) is the same as defined for TransactionIdentification Time upto seconds only Occurs once in RTGS, but [1..10] in NEFT 2011-04-24T0....
X X X X Extracts X X X X
X X X X Extracts X X X X
....9:30:32 ISODateTim e EODZERO 2011-04-24T07:30:32 2 | Page Max35Text ISODateTim e à¤à¤¾à¤°à¤¤à¥€ रिज़रà¥à¤µ बैंक BANK RESERVE B OF IND ISO20022 standard Message Implementation ISO20022 Message - XML tag Description camt.054.001.03 BankToCustomer DebitCredit NotificationV03 Message Item Index ISO RTGS Rules Multi /NEFT Multi Ntfctn block. Account Unambiguous identification of the 2.11 [1..1] [1..1] account to which credit and debit entries are made. This msg element is the part of the Ntfctn block. Identification [1..1] [1..1] Other [1..1] [1..1] Identification Settlement account [1..1] [1..1] number Entry Set of elements 2.45 [O..n] [1..1] used to specify an entry in the debit credit notification. This msg element is the part of the Ntfctn block. Amount Amount and currency [1..1] [1..1] This msg element is the part of the Ntry block. Credit DebitIndicator Indicates whether [1..1] [1..1] Codes to be used are: the total net entry amount is a credit CRDT: Credit -> Operation is an increase DBIT: Debit -> Operation is an decrease Status or a debit amount. Usage: A zero balance is Data Type Example 353565651234 1000....
X X X X Extracts X X X X
X X X X Extracts X X X X
....0.00 Amount DBIT considered to be a credit balance. This msg element is the part of the Ntry block. Status of an entry [1..1] [1..1] on the books of the Always BOOK meaning booked amount. Status Booked is the only status that BOOK Reserve Bank of India ISO Messages, "camt.054.001.03 BanktoCustomerDebit Credit NotificationV03" Code Code 3| Page à¤à¤¾à¤°à¤¤à¥€ रिज़रà¥à¤µ बैंक BANK RESERVE B OF IND ISO20022 standard Message Implementation ISO20022 Message - XML tag Description camt.054.001.03 BankToCustomerDebitCredit NotificationV03 Message Item Index ISO RTGS Rules Multi /NEFT Multi Example Data Type 2010-10- 18T13:15:00 DateTime account service.r Code for status BOOK/INFO/PDNG/F UTR This msg element is the part of the Ntry can be reversed. Others Code for status are: BOOK/INFO/PDNG/FUTR For more details pl refer para 2.81 of ISO documentation "Payment Maintenance 2009.pdf". block. ValueDate This msg element [0..1] [1..1] is the part of the Ntry block. DateTime Value date time [0..1] [1..1] Settlement time Set of elements used to fully identify the type of underlying transaction resulting in an entry. This msg elem....
X X X X Extracts X X X X
X X X X Extracts X X X X
....ent is the part of the Ntry BankTransactionCode block. [1..1] [1..1] Bank transaction code in a proprietary form, as defined by Proprietary Code the issuer. [1..1] [1..1] Proprietary bank [1..1] [1..1] transaction code to TxCd> identify the underlying transaction. EntryDetails Provides details on [0..n] [1..1] the entry This msg element is the part of the Ntry block. TransactionDetails References [O..n] [1..1] [0..1] [1..1] EndToEndIdentification Transaction reference 2.128 [0..1] [1..1] Unique identification, as assigned number. by the bank's customer, to This msg element is Reserve Bank of India ISO Messages, "camt.054.001.03 BanktoCustomer Debit Credit NotificationV03" 0001TREF765628561242 4| Page Max35Text à¤à¤¾à¤°à¤¤à¥€ रिज़रà¥à¤µ बैंक BANK RESERVE B OF IND ISO20022 standard Message Implementation ISO20022 Message - XML tag Description camt.054.001.03 BankToCustomerDebitCredit NotificationV03 Message Item the part of the Refs block. Index ISO Multi RTGS /NEFT Multi Rules unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain to the benef....
X X X X Extracts X X X X
X X X X Extracts X X X X
....iciary. For MT101, this field corresponds to field 21( Related Reference) For MT103 this field corresponds to field 70 (Remittance Information) with codeword ROC (Ordering customer's reference). If field 70 does not carry this optional reference, then field 20 (Sender's Reference) should be used. Example Data Type HDFCR12012042400000023 For MT202 COV, this field corresponds to field 21(Related Reference). TransactionIdentification Related reference 2.129 [0..1] [1..1] Use UTR (Unique Transaction number. Reference) format (22 characters) This msg element is the part of the Refs XXXX-Sender IFSC [4] block. X-Payment System [1] X-Channel [1] YYYYMMDD-Date [8] Reserve Bank of India ISO Messages, "camt.054.001.03 BanktoCustomerDebit Credit NotificationV03" nnnnnnnn- Sequence Number [8] Unique identification, as assigned by the first instructing agent, to unambiguously identify the transaction that is passed on, unchanged, For Further Information, pl refer to FAQ on Channel. 5| Page Max35Text à¤à¤¾à¤°à¤¤à¥€ रिज़रà¥à¤µ बैंक BANK RESERVE B OF IND ISO20022 Message - camt.054.001.03 BankToCustomerDebitCredit NotificationV03 ....
X X X X Extracts X X X X
X X X X Extracts X X X X
....Message Item ISO20022 standard Message Implementation XML tag Description Index ISO RTGS Rules Multi /NEFT Multi Amount Transaction amount [1..1] [1..1] This msg element is the part of the TxDtls block. Credit DebitIndicator Indicates whether the transaction is a credit or a debit transaction. throughout the entire interbank chain. Usage: The transaction identification can be used for reconciliation, tracking or to link tasks relating to the transaction on the interbank level. Usage: The instructing agent has to make sure that the transaction identification is unique for a pre- agreed 2.59 [1..1] [1..1] Codes are DBIT & CRDT. Codes DBIT Meanings Debit CRDT Credit This msg element is the part of the TxDtls block. RelatedParties Set of elements used 2.179 [0..1] [1..1] to identify the parties related to the Debtor Identification underlying transaction. This msg element is the part of the TxDtls block. IFSC of the participant 2.184 [0..1] [1..1] which caused the Must reflect the pacs.008 and pacs.009 structure for BOTH Debtor and Creditor credit Identification [0..1] [1..1] Reserve Bank of India ISO Messages, "camt.054.001.03 BanktoCustomerDebit Credit NotificationV03" Example Da....
X X X X Extracts X X X X
X X X X Extracts X X X X
....ta Type 10000.00 Amount DBIT Credit Debit Code 6 | Page à¤à¤¾à¤°à¤¤à¥€ RESERVE BA रिज़रà¥à¤µ बैंक OF IND ISO20022 Message - camt.054.001.03 BankToCustomerDebitCredit NotificationV03 Message Item OrganisationIdentification Other Identification ISO20022 standard Message Implementation XML tag Description organization identifier ifsc Index ISO RTGS Rules Multi /NEFT Multi [1..1] [1..1] [O..n] [1..1] [1..1] [1..1] Example Data Type Purpose Underlying reason for [0..1] [0..1] the payment transaction. This msg element is the part of the TxDtls Usage: Purpose is used by the end- customers, that is initiating party, (ultimate) debtor, (ultimate) creditor to provide information concerning the nature of the payment. CAN Max35Text B0239777 block. Proprietary Purpose, in a [1..1] [1..1] Code values are: REPO or REVREPO Max35Text proprietary form. RemittanceInformation Remittance 2.214 [0..1] [0..1] Information. This msg element is the part of the TxDtls block. Unstructured Remittance Information 140 2.215 [0..n] [1..4] Size restricted to a maximum of 4 repeats of 140 characters. Max140Text characters up to 4 can be used S....
X X X X Extracts X X X X
X X X X Extracts X X X X
....ender to Receiver Information Note:- [1..1] -> Mandatory; [1..0] -> Optional; [1..n] -> Mandatory and n times repeated; [0..n] -> Optional and n times repeated Reserve Bank of India ISO Messages, "camt.054.001.03 BanktoCustomerDebit Credit NotificationV03" 7| Page 8. à¤à¤¾à¤°à¤¤à¥€à¤¯ RESERVE रिज़रà¥à¤µ बैंक BANK OF IN ISO20022 standard Message Implementation Interbank Transfer ISO Message: "pacs.009.001.03 - FinancialInstitutionCreditTransferV03" * Applicable Areas: RTGS 1) For defining Interbank message in RTGS. The same is not applicable to NEFT as there is no concept of Interbank in NEFT. This message formats would replace the current R42 used in current RTGS. *Corresponds to R42 in current RTGS. The ISO 20022 Business Message consists of two parts: (1) ISO 20022 Business Appl. Header (2) ISO 20022 Messages ISO 20022 Business Appl. Header ISO 20022 Message Business Message Business Application Header is a business header and should not be confused with a file or transport header. It is created before the transport routing header is applied to the business message and is retained after the transport header is....
X X X X Extracts X X X X
X X X X Extracts X X X X
.... removed. So any parties between the two business applications that don't perform a business function are not mentioned in the BAH. Such 'technical' middle men don't open or change the Business Message; they only forward it to the correct business application. Although the BAH is not the transport header, data in the BAH can be used by transport applications to determine the routing header since it does contain the business sender, receiver and document details. It can also be used by the business applications to determine the appropriate process to perform on the business message. Message fields description ISO Business Application Header Business Application Header (Refer related documentation “RBI_NG_RTGS_ISO20022_BusinessApplication Header") Reserve Bank of India ISO Messages, "pacs.009.001.03 - FinancialInstitution CreditTransferV03" 1| Page RESERVE रिज़रà¥à¤µ बैंक BANK OF IN ISO 20022 Message Мар ping - ISO20022 Message - pacs.009.001.03- FinancialInstitution CreditTransferV03 Message Item FinancialInstitution CreditTransfer GroupHeader Creation Date & Time GROUP HEADER - GROUP HEADER Message Identification ISO2....
X X X X Extracts X X X X
X X X X Extracts X X X X
....0022 standard Message Implementation XML tag Description Index ISO RTGS Rules Multi Multi Example Data Type Root tag Fields common to all the transaction 1.0 [1..1] [1..1] in the message Messageldentificati on Uniquely identifies the message 1.1 [1..1] [1..1] Uniquely identifies message Max35T HDFC201210181000000218 be structured as: XXXX-Sender IFSC [4] YYYYMMDD - Creation Date Reverse [8] X-Channel [1] nnnnnnnnnn- Sequence Number [9] The values of Channel Identification (X) is the same as defined for TransactionIdentification 2011-04- 24T09:30:32 Creation DateTime Payment origination date time 1.2 [1..1] [1..1] Time up to seconds only Reserve Bank of India ISO Messages, "pacs.009.001.03 - FinancialInstitution CreditTransferV03" 2 Page ISODateT ime Settlement Information रिज़रà¥à¤µ बैंक BANK SERVE BA AH RESER No. of Txs. OF IN NumberOfTransacti ISO20022 standard Message Implementation Number of transactions 1.4 [1..1] |1..1] Always 1 for Interbank payment in RTGS 1 Max15N umericTe xt TotallnterbankSettl Total Settlement Amount + 1.6 [0..1] [1..1] Total amount transferred between debtor and creditor. 3400 InterbankSettleme nt....
X X X X Extracts X X X X
X X X X Extracts X X X X
....Date 1.7 [0..1] [1..1] 2011-04- 24 ISO date SettlementInformat settlement of transaction happens Settlement Method Method used to 1.9 [1..1] [1..1] settle payments Must be CLRG (i.e., Settlement done through a payment clearing system) CLRG Code InstructingAgent instructs the next party in the chain to carry out the (set of) instruction(s). Other Codes are: CLRG, COVE, INDA, INGA FinancialInstitutionl ClearingSystemMe Member IFSC of the Sending participant [1..1] [1..1] Sender IFSC Reserve Bank of India ISO Messages, "pacs.009.001.03 - FinancialInstitution CreditTransferV03" Max35Te HDFC0239777 3 | Page RESERVE जरà¥à¤µ बैंक BANK OF INDIA ISO20022 standard Message Implementation the chain to carry out the (set of) instruction(s). FinancialInstitutionl ClearingSystemMe Member IFSC of the [1..1] [1..1] Receiver IFSC Identification Receiving participant Max35Te HDFC0239777 CreditTransferTran information on Only one occurrence allowed for Interbank Payment individual transactions PaymentIdentificat Contains 2.1 [1..1] [1..1] CREDIT TRANSFER INFORMATION Payment Identification ion references to a payment EndToEndIdentifica Identificatio....
X X X X Extracts X X X X
X X X X Extracts X X X X
....n (Related For FI Credit Transfer (pacs.009), this must be the same value as TransactionIdentification. TREF2312135465781 Max35Te xt Reference) TransactionIdentific Transaction 2.4 [1..1] [1..1] ation Identification Use UTR (Unique Transaction Reference) format (22 characters) XXXX-Sender IFSC HDFCR12012042400000023 Max35Te xt [4] Reserve Bank of India ISO Messages, "pacs.009.001.03 - FinancialInstitution CreditTransferV03" nnnnnnnn-Sequence Number [8] Unique identification, as assigned by the first instructing agent, to For Further Information, pl refer to FAQ on Channel. 4 | Page X-Payment System [1] X-Channel [1] YYYYMMDD-Date [8] RESERVE SERVE BA Payment Information Payment Information Information Payment जरà¥à¤µ बैंक OF INDIA 130 ISO20022 standard Message Implementation unambiguously identify the transaction that is passed on, unchanged, throughout the entire interbank chain. Usage: The transaction identification can be used for reconciliation, tracking or to link tasks relating to the transaction on the interbank level. Usage: The instructing agent has to make sure that the transaction identification is unique for a pre- agreed period....
X X X X Extracts X X X X
X X X X Extracts X X X X
..... PaymentTypeInfor ServiceLevel Service level 2.9 [0..1] [0..1] Reserve Bank of India ISO Messages, "pacs.009.001.03 - FinancialInstitution CreditTransferV03" Indicator of the urgency or order of importance that the instructing party would like the instructed party to apply to the processing of the instruction at application level. Priority "NORM" will result in liquidity Savings. HIGH: Priority Level is high. NORM: Priority Level is normal. Agreement under which or rules under which the transaction should be processed. NORM Code 5 | Page RESERVE BANK बैंक OF IND ISO20022 standard Message Implementation Proprietary Proprietary Service Level Code 2.11 [0..1] [1..1] For RTGS used to indicate RTGS processing priority in range 00-99. 80 Max35Te xt To be used for managing queues by sending bank before settlement. LocalInstrument Local instrument 2.12 type [0..1] [1..1] (User community specific instrument.) Proprietary Proprietary 2.13 instrument type code - [0..1] [1..1] Type of local instrument. For RTGS, pacs.009 use: 'FITOFICredit' FITOFICredit Max35Te xt CategoryPurpose Purpose of the 2.15 [0..1] [1..1] Instrument. Payment purpose must be a value lis....
X X X X Extracts X X X X
X X X X Extracts X X X X
....ted in ISO category purpose code Code ISO External 2.16 [1..1] |│[1..1] FROM ISO 20022External Code list SALA Code category purpose code list. Codes (Max4Te xt) Reserve Bank of India are "SALA - SalaryPayment, Loan-Loan, PENS- Pension Payment, etc. Details in 3.55 of UNIFI (ISO20022) Msg Definition Rpt. ISO Messages, "pacs.009.001.03 - FinancialInstitution CreditTransferV03" The following codes are available. CASH: CashManagementTransfer CORT: TradeSettlementPayment DIVI: Dividend GOVT: GovernmentPayment HEDG: Hedging INTC: IntraCompanyPayment INTE: Interest LOAN: Loan PENS: PensionPayment SALA: SalaryPayment SECU: Securities SSBE: SocialSecurityBenefit 6 Page Debtor (ORDERING Interbank Amt Settlement INSTITUTION). SERVE BA RESERVE रिज़रà¥à¤µ बैंक OF IND ISO20022 standard Message Implementation SUPP: SupplierPayment TAXS: TaxPayment TRAD: Trade TREA: TreasuryPayment VATX: ValueAddedTaxPayment WHLD: WithHolding OTHR: Other The generic code for the normal funds transfer may be 'OTHR'. This code will be the default purpose code which stands for "Other Payment Purpose". Example: OTHR For additional codes, please refer to document....
X X X X Extracts X X X X
X X X X Extracts X X X X
.... ExternalcodeLists_3Q2012_22Oct 2012_v4.xls available at www.iso20222.org Banks to suggest additional India Specific codes. 3400 InterbankSettleme Debtor Amount + Currency ORDERING INSTITUTION Amount transferred between participants 2.40 [1..1] [1..1] FinancialInstitutionl dentification [1..1] [1..1] ClearingSystemMe mberldentification [0..1] [1..1] Reserve Bank of India ISO Messages, "pacs.009.001.03 - FinancialInstitution CreditTransferV03" 7| Page Amount Creditor (BENEFICIARY INSTITUTION) रिज़रà¥à¤µ बैंक RESERVE SERVE BA BANK OF IND Member Ordering [0..1] [0..1] Institution Name Creditor Beneficiary 2.46 [1..1] | [1..1] Institution identification Max35Te HDFC0239777 Bank A Max140T ext FinancialInstitutionl dentification ClearingSystemMe Member kMmbld> Indian FinancialSys [1..1] [1..1] Identification temCodeldentifier for participants / HDFC0239777 Max35Te Name and Identification for non Participants is mandatory Name kNm> Beneficiary [0..1] [0..1] Institution Name Bank b Max70Te xt PostalAddress KPstlAdr> Beneficiary [0..1] [0..1] Institution Postal Address AddressLine Adress in free [0..7] [0..4] form text Number of occ....
X X X X Extracts X X X X
X X X X Extracts X X X X
....urrence is restricted to 4 Boulevard Road Max70Te xt Reserve Bank of India ISO Messages, "pacs.009.001.03 - FinancialInstitutionCreditTransferV03" 8| Page Remittance Information नरà¥à¤µ बैंक. OF INDIA SERVE BA BANK ISO20022 standard Message Implementation Other used when [0..1] [0..1] correspondants are involved Identification Identification [1..1] [1..1] assigned by an institution Max35Te xt CreditorAccount Customer account identification Identification Account number [1..1] [1..1] of Beneficiary It must be used for recording account number for the beneficiary bank for STP process. 0510085 Max35Te xt RemittanceInforma Remittance 2.55 [0..1] [0..1] tion Information Unstructured kUstrd> Remittance 2.56 [0..n] [0..4] Information 140 Size restricted to a maximum of 4 repeats of 140 characters. Max140T ext characters up to 4 can be used Sender to Receiver Information Note:- [1..1] -> Mandatory; [0..1] -> Optional; [1..n] -> Mandatory and n times repeated; [0..n] -> Optional and n times repeated; Reserve Bank of India ISO Messages, "pacs.009.001.03 - FinancialInstitution CreditTransferV03" 9| Page • à¤à¤¾à¤°à¤¤à¥€à¤¯ ....
X X X X Extracts X X X X
X X X X Extracts X X X X
....रिज़रà¥à¤µ बैंक RESERVE BANK OF IND ISO20022 standard Message Implementation Multilateral Net Settlement Batch (MNSB) Request * ISO message pacs.009.001.03 FinancialInstitutionCreditTransferV03 is used for defining the MNSB request. If clearing member in debit, the credit leg will have the clearing house identifier and vice versa. This message formats would replace the current R12 used in current RTGS. *Corresponds to R12 in current RTGS. The ISO 20022 Business Message consists of two parts: (1) ISO 20022 Business Appl. Header (2) ISO 20022 Messages ISO 20022 Business Appl. Header ISO 20022 Business Message Message Business Application Header is a business header and should not be confused with a file or transport header. It is created before the transport routing header is applied to the business message and is retained after the transport header is removed. So any parties between the two business applications that don't perform a business function are not mentioned in the BAH. Such 'technical' middle men don't open or change the Business Message; they only forward it to the correct business application. Although the BAH is n....
X X X X Extracts X X X X
X X X X Extracts X X X X
....ot the transport header, data in the BAH can be used by transport applications to determine the routing header since it does contain the business sender, receiver and document details. It can also be used by the business applications to determine the appropriate process to perform on the business message. Message fields description ISO Business Application Header Business Application Header (Refer related documentation “RBI_NG_RTGS_ISO20022_BusinessApplicationHeaderâ€) ISO 2002 Message Reserve Bank of India ISO Messages, "pacs.009.001.03 FinancialInstitutionCreditTransferV03" 1| Page • à¤à¤¾à¤°à¤¤à¥€à¤¯ रिज़रà¥à¤µ बैंक RESERVE OF INDIA BANK ISO20022 Message pacs.009.001.03 FITOFICustomerCreditT ransferV03 Message Item ISO20022 standard Message Implementation XML tag Description Index ISO RTGS Rules Multi Multi Example Data Type Root tag [1..1] [1..1] GroupHeader Fields common to all the transaction in the message 1.0 [1..1] [1..1] Messageldentification Uniquely identifies the message 1.1 [1..1] [1..1] Uniquely identifies message Max35Text CCIL201210181000000218 Recommend Messageldentifica....
X X X X Extracts X X X X
X X X X Extracts X X X X
....tion be structured as: XXXX-Sender IFSC [4] YYYYMMDD - Creation Date Reverse [8] X-Channel [1] nnnnnnnnn-Sequence Number [9] The values of Channel Identification (X) is the same as defined for TransactionIdentification Time upto seconds only CreationDateTime Payment origination 1.2 [1..1] [1..1] date time NumberOfTransaction Number of 1.4 [1..1] [1..1] S transactions Equal to number of participants in the batch 2011-04-24T09:30:32 3 TotallnterbankSettlem Amount + Currency InterbankSettlementD ate Settlement Date - 1.7 [0..1] [1..1] will settle only current day Total amount of money moved between the instructing agent and the instructed agent. Value date of payment must be same as RTGS date. Mandatory in RTGS implementation 3400.00 2011-04-24 Reserve Bank of India ISO Messages, "pacs.009.001.03 FinancialInstitutionCreditTransferV03" 2| Page ISODateTime Max15Numeri cText Amount ISODate • à¤à¤¾à¤°à¤¤à¥€à¤¯ रिज़रà¥à¤µ बैंक RESERVE OF INDIA BANK ISO20022 Message pacs.009.001.03 FITOFICustomerCreditT ransferV03 Message Item ISO20022 standard Message Implementation XML tag Description Index ISO RTGS Rules....
X X X X Extracts X X X X
X X X X Extracts X X X X
.... Multi Multi Data Type Example SettlementInformation Settlement Method Details on how settlement of transaction happens Method used to settle payments 1.8 [1..1] [1..1] 1.9 [1..1] [1..1] Must be CLRG (i.e., Settlement done through a payment clearing system) CLRG Code Other Codes are: CLRG, COVE, INDA, INGA InstructingAgent Agent that 1.21 [0..1] | [1..1] instructs the next party in the chain to carry out the (set of) instruction(s). entification FinancialInstitutionld ClearingSystemMem berldentification Member [0..1] [1..1] Identification IFSC of the Sending participant [1..1] [1..1] Sender IFSC InstructedAgent Agent that is 1.22 [0..1] [1..1] instructed by the previous party in the chain to carry out the (set of) instruction(s). FinancialInstitutionld ClearingSystemMem berldentification [0..1] [1..1] Reserve Bank of India ISO Messages, "pacs.009.001.03 FinancialInstitutionCreditTransferV03" CCILOPI0001 3| Page • à¤à¤¾à¤°à¤¤à¥€à¤¯ रिज़रà¥à¤µ बैंक RESERVE OF INDIA BANK ISO20022 Message pacs.009.001.03 FITOFICustomerCreditT ransferV03 Message Item ISO20022 standard Message Implementation XML tag D....
X X X X Extracts X X X X
X X X X Extracts X X X X
....escription Index ISO RTGS Rules Multi Multi Example Data Type Member Identification IFSC of the [1..1] [1..1] Receiver IFSC Receiving participant RBISORTGS00 CreditTransferTransact on individual Multiple occurrence based on number of participants transactions PaymentIdentification Contains references 2.1 [1..1] [1..1] to a payment EndToEndIdentification Identification (Related Reference) For FI Credit Transfer (pacs.009), this must be the same value as TransactionIdentification. TREF2312135465781 Transactionldentificati Transaction 2.4 [1..1] [1..1] on Identification Use UTR (Unique Transaction Reference) format (22 characters) XXXX-Sender IFSC CCILR12012042400000023 Max35Text [4] Main clearing Reference Number for return clearing X-Payment System [1] For Further Information, pl refer to FAQ on Channel. X-Channel [1] YYYYMMDD-Date [8] Reserve Bank of India ISO Messages, "pacs.009.001.03 FinancialInstitutionCreditTransferV03" nnnnnnnn-Sequence Number [8] Unique identification, as assigned by the first instructing agent, to unambiguously identify the transaction that is passed on, unchanged, throughout the entire interbank chain. Usage: The transaction identification can be use....
X X X X Extracts X X X X
X X X X Extracts X X X X
....d for reconciliation, tracking or to link tasks relating to the transaction on the interbank level. Usage: The instructing agent has to make sure that the transaction 4| Page • à¤à¤¾à¤°à¤¤à¥€à¤¯ रिज़रà¥à¤µ बैंक RESERVE OF INDIA BANK ISO20022 Message pacs.009.001.03 FITOFICustomerCreditT ransferV03 Message Item ISO20022 standard Message Implementation XML tag Description Index ISO RTGS Rules Multi Multi identification is unique for a pre- agreed period. PaymentTypelnformat Payment 2.6 [0..1] [1..1] ion Instruction Priority Information Priority 2.7 [0..1] [1..1] HIGH / NORM Indicator of the urgency or order of importance that the instructing party would like the instructed party to apply to the processing of the instruction at application level. Priority "NORM" will result in liquidity Savings. HIGH: Priority Level is high. NORM: Priority Level is normal. ServiceLevel Service level 2.9 [0..1] [0..1] Proprietary Proprietary Service Level code 2.11 [0..1] [1..1] LocalInstrument Local instrument type 2.12 [0..1] [1..1] (User community Reserve Bank of India ISO Messages, "pacs.009.001.03 FinancialInstit....
X X X X Extracts X X X X
X X X X Extracts X X X X
....utionCreditTransferV03" Agreement under which or rules under which the transaction should be processed. For RTGS used to indicate RTGS processing priority in range 0 0- 99. To be used for managing queues0 by sending bank before settlement. Example Data Type NORM Code 80 Max35Text 5| Page • à¤à¤¾à¤°à¤¤à¥€à¤¯ रिज़रà¥à¤µ बैंक RESERVE OF INDIA BANK ISO20022 Message pacs.009.001.03 FITOFICustomerCreditT ransferV03 Message Item ISO20022 standard Message Implementation XML tag Description Index ISO RTGS Rules Multi Multi Example Data Type specific instrument.) Proprietary Proprietary 2.13 instrument type code [0..1] [1..1] Type of local instrument. For RTGS, pacs.009 use: -'RTGSNetSettlementXXzNN' NetSettlement Max35Text InterbankSettlementA Where 'XX' is the clearing type which may take values 'GC', 'IB', 'FX', MC, SE, OT & so on. 'z' is the indicator which may take values C-Original, R-Return, L-Last Return. "NN" is the Return serial. "GC" stands for guaranteed settlement of Securities and CBLO segment. "IB" stands for guaranteed settlement of FOREX segment. "FX" stands for non guaranteed settlement. "M....
X X X X Extracts X X X X
X X X X Extracts X X X X
....C" Stands for MICR Clearing. "SE" stands for non-guaranteed MNSB Debtor 2.40 [1..1] [1..1] If net credit then RBI-RTGS IFSC. If net debit the Member IFSC If net debit of RBI current account then RBI-CBS IFSC. If net credit of RBI current account then RBI-RTGS IFSC. FinancialInstitutionlden tification ClearingSystemMembe rldentification [1..1] [1..1] Member Identification Indian FinancialSyste [1..1] [1..1] mCodeldentifier for participants / Name and Identification for non Participants is mandatory Creditor creditor 2.46 [1..1] [1..1] If net credit then Member IFSC. If net debit then RBI-RTGS IFSC. If net debit of RBI current account then RBI-RTGS IFSC. If net credit of RBI current account then RBI-CBS IFSC. FinancialInstitutionlden tification ClearingSystemMembe rldentification Member Identification [1..1] [1..1] Indian FinancialSyste [1..1] [1..1] mCodeldentifier for RemittanceInformatio n participants / Name and Identification for non Participants is mandatory Remittance Information 2.75 [0..1] [0..1] Reserve Bank of India ISO Messages, "pacs.009.001.03 FinancialInstitutionCreditTransferV03" Example Ccy='INR'>3400.00 Data Type H DFC0239777 HD Max35Text FC0239777 7 | Page ....
X X X X Extracts X X X X
X X X X Extracts X X X X
....• à¤à¤¾à¤°à¤¤à¥€à¤¯ रिज़रà¥à¤µ बैंक RESERVE OF INDIA BANK ISO20022 Message pacs.009.001.03 FITOFICustomerCreditT ransferV03 Message Item Unstructured ISO20022 standard Message Implementation XML tag Description Index ISO Multi RTGS Multi Rules Remittance Information 140 characters up to 4 can be used 2.76 [0..n] [0..4] Size restricted to a maximum of 4 repeats of 140 characters. Example Data Type Sender to Receiver Information Note:- [1..1] -> Mandatory; [0..1] -> Optional; [1..n] -> Mandatory and n times repeated; [0..n] -> Optional and n times repeated; Reserve Bank of India 8| Page ISO Messages, "pacs.009.001.03 FinancialInstitutionCreditTransferV03" Max140Text Own Account Transfer (OAT)* ISO message "pacs.009.001.03 FinancialInstitutionCreditTransferV03" is used for defining the Own account transfer in RTGS. This message formats would replace the current R10 used in current RTGS. *Corresponds to R10 in current RTGS. The ISO 20022 Business Message consists of two parts: (1) ISO 20022 Business Appl. Header (2) ISO 20022 Messages ISO 20022 Business Appl. Header ISO 20022 Business Message Message Bus....
X X X X Extracts X X X X
X X X X Extracts X X X X
....iness Application Header is a business header and should not be confused with a file or transport header. It is created before the transport routing header is applied to the business message and is retained after the transport header is removed. So any parties between the two business applications that don't perform a business function are not mentioned in the BAH. Such 'technical' middle men don't open or change the Business Message; they only forward it to the correct business application. Although the BAH is not the transport header, data in the BAH can be used by transport applications to determine the routing header since it does contain the business sender, receiver and document details. It can also be used by the business applications to determine the appropriate process to perform on the business message. Message fields description ISO Business Application Header Business Application Header (Refer related documentation “RBI_NG_RTGS_ISO20022_BusinessApplicationHeader") ISO 20022 Message ISO20022 Message - XML tag Description Index pacs.009.001.03 ISO Multi RTGS Rules Multi FITOFICustomerCreditTr ansferV03 Message Item GroupHeader Root tag Fields common to all 1.0 [1.....
X X X X Extracts X X X X
X X X X Extracts X X X X
.....1] [1..1] Reserve Bank of India ISO Messages, "pacs.009.001.03 FinancialInstitution CreditTransferV03" Example Data Type 1| Page ISO20022 Message pacs.009.001.03 FITOFICustomerCreditTr ansferV03 Message Item XML tag Description Index ISO RTGS Rules Example Data Type Multi Multi the transaction in the message Messageldentification Uniquely 1.1 [1..1] [1..1] Uniquely identifies message identifies the HDFC201210181000000218 Max35T ext message Recommend Messageldentification be structured as: XXXX- Sender IFSC [4] YYYYMMDD - Creation Date Reverse [8] X-Channel [1] nnnnnnnnn-Sequence Number [9] The values of Channel Identification (X) is the same as defined for TransactionIdentification Time upto seconds only CreationDateTime Payment origination date time 1.2 [1..1] [1..1] 2011-04-24T09:30:32 ISODateTi me NumberOfTransactions Number of 1.4 [1..1] [1..1] Always 1 for own account transfer 1 transactions TotallnterbankSettleme ntAmount Total 1.6 [0..1] [1..1] Max15Nu mericText Amount Settlement Amount + Currency InterbankSettlementDa te Settlement Date - will settle only current day 1.7 [0..1] [1..1] ISODate SettlementInformation Details on how 1.8 settlement of [1..1] [1..1] Rese....
X X X X Extracts X X X X
X X X X Extracts X X X X
....rve Bank of India ISO Messages, "pacs.009.001.03 FinancialInstitution CreditTransferV03" 2 | Page ISO20022 Message- pacs.009.001.03 FITOFICustomerCreditTr ansferV03 Message Item XML tag Description Index ISO Multi RTGS Multi Rules Example Data Type transaction happens SettlementMethod Method used to settle 1.9 [1..1] |│[1..1] payments Must be CLRG (i.e., Settlement done through a payment clearing system) CLRG Code Other Codes are: InstructingAgent instructs the next party in the chain to CLRG, COVE, INDA, INGA Mandatory in RTGS implementation IFSC of the bank initiating OAT. carry out the (set of) instruction(s). FinancialInstitutionlde ClearingSystemMemb Member Identification IFSC of the [1..1] [1..1] Sending InstructedAgent participant Agent that is instructed by the previous 1.22 [0..1] | [1..1] Mandatory in RTGS Implementation party in the chain to carry out the (set of) instruction(s). IFSC of RBI FinancialInstitutionlde ClearingSystemMemb [0..1] [1..1] erldentification Reserve Bank of India ISO Messages, "pacs.009.001.03 FinancialInstitution CreditTransferV03" HDFC0239777 3| Page ISO20022 Message - pacs.009.001.03 ansferV03 FITOFICustomerCreditTr Message Item ....
X X X X Extracts X X X X
X X X X Extracts X X X X
....Member Identification XML tag Description Index ISO RTGS Rules Example Multi Multi Data Type IFSC of the Receiving [1..1] |│[1..1] participant RBIS0000001 Max35Te CreditTransferTransacti information Only one occurrence allowed for own account transfer containing credit and debit information PaymentIdentification Payment 2.1 [1..1] [1..1] Identification EndToEndIdentification Identification Related reference. In case of returned transaction. Else same as TREF2312135465781 xt (Related TransactionIdentification Reference) TransactionIdentificatio Transaction 2.4 [1..1] [1..1] n Identification Use UTR (Unique Transaction Reference) format (22 characters) XXXX-Sender IFSC HDFCR12012042400000023 Max35Te xt [4] X-Payment System [1] For Further Information, pl refer to FAQ on Channel. X-Channel [1] YYYYMMDD-Date [8] Reserve Bank of India ISO Messages, "pacs.009.001.03 FinancialInstitution CreditTransferV03" nnnnnnnn-Sequence Number [8] Unique identification, as assigned by the first instructing agent, to unambiguously identify the transaction that is passed on, unchanged, throughout the entire interbank chain. Usage: The transaction identification can be used for reconciliatio....
X X X X Extracts X X X X
X X X X Extracts X X X X
....n, tracking or to link tasks relating to the 4| Page ISO20022 Message - pacs.009.001.03 FITOFICustomerCreditTr ansferV03 Message Item XML tag Description Index ISO RTGS Rules Multi Multi transaction on the interbank level. Usage: The instructing agent has to make sure that the transaction identification is unique for a pre- agreed period. PaymentTypeInformati on Payment Information 2.6 [0..1] [1..1] Priority is mandatory in RTGS implementation. InstructionPriority Priority must 2.7 [0..1] [1..1] HIGH / NORM be valid ISO priority code value ServiceLevel Service level 2.9 Indicator of the urgency or order of importance that the instructing party would like the instructed party to apply to the processing of the instruction at application level. Priority "NORM" will result in liquidity Savings. HIGH: Priority Level is high. NORM: Priority Level is normal. [0..1] [0..1] Agreement under which or rules under which the transaction should be processed. For RTGS used to indicate RTGS processing priority in range 00- Proprietary Proprietary Service Level Code 2.11 [0..1] [1..1] 99. LocalInstrument NORM 80 Max35Te xt 5 | Page ISO20022 Message pacs.009.001.03 FITOFICustomerCreditTr ansfer....
X X X X Extracts X X X X
X X X X Extracts X X X X
....V03 Message Item XML tag Description Index ISO RTGS Rules Example Data Type Multi Multi instrument type (User community Proprietary specific instrument.) Proprietary instrument type code 2.13 [0..1] [1..1] Type of local instrument. OwnAccTransfer Max35Te InterbankSettlementA Settlement Amount 2.18 [1..1] [1..1] For RTGS, pacs.009 use: -'OwnAccTransfer' Amount transferred between accounts xt 3400.00 Amount ORDERING INSTITUTION 2.40 [1..1] [1..1] FinancialInstitutionldent ClearingSystemMemberl dentification Member Identification [0..1] [1..1] Mandatory in RTGS implementation IndianFinanci alSystemCodel dentifier for participants / Name and Identification for non Participants is [1..1] [1..1] IFSC of participant sending the payment request HDFC 0239777 mandatory DebtorAccount Identification Other Identification Account Number 2.41 [0..1] [1..1] Mandatory in RTGS implementation [1..1] [1..1] [1..1] [1..1] [1..1] [1..1] From account of participant 34545353 Reserve Bank of India ISO Messages, "pacs.009.001.03 FinancialInstitution CreditTransferV03" Max35Tex t 6 Page ISO20022 Message - pacs.009.001.03 FITOFICustomerCreditTr ansferV03 Message Item Currency Creditor XML tag Descr....
X X X X Extracts X X X X
X X X X Extracts X X X X
....iption Index ISO RTGS Rules Example Multi Multi Account [0..1] [0..1] currency Beneficiary Institution identification 2.46 [1..1] [1..1] INR Data Type Max35Tex FinancialInstitutionldent ClearingSystemMemberl IFSC [1..1] [1..1] [0..1] [1..1] Mandatory in RTGS implementation [1..1] [1..1] IFSC of participant receiving the payment request. RBISO 000001 CreditorAccount 2.47 Identification [1..1] [0..1] [1..1] [1..1] Mandatory in RTGS implementation Other [1..1] [1..1] Identification [1..1] [1..1] To account of participant 546545353 Account [0..1] [0..1] > INR t currency RemittanceInformation Remittance 2.55 [0..1] [0..1] Information Unstructured Remittance 2.56 [0..n] [0..4] Information 140 Size restricted to a maximum of 4 repeats of 140 characters. characters up to 4 can be used. Reserve Bank of India ISO Messages, "pacs.009.001.03 FinancialInstitution CreditTransferV03" Max35Tex Max140T ext 7 | Page 8. à¤à¤¾à¤°à¤¤à¥€à¤¯ रिज़रà¥à¤µ बैंक RESERVE BANK B OF IN ISO20022 standard Message Implementation Payment Return ISO message "pacs.004.001.03 PaymentReturnV03" Bank-to-Bank message, settlement already complet....
X X X X Extracts X X X X
X X X X Extracts X X X X
....ed in NG-RTGS. Function of the pacs.004 message is “sent by an agent to the previous agent in the payment chain to undo a payment previously settled." This message formats would replace the current R42 for return & N07 in NEFT messages. *Corresponds to R42 in current RTGS & N07 in NEFT messages The ISO 20022 Business Message consists of two parts: (1) ISO 20022 Business Appl. Header (2) ISO 20022 Messages ISO 20022 Business Appl. Header ISO 20022 Message Business Message Business Application Header is a business header and should not be confused with a file or transport header. It is created before the transport routing header is applied to the business message and is retained after the transport header is removed. So any parties between the two business applications that don't perform a business function are not mentioned in the BAH. Such 'technical' middle men don't open or change the Business Message; they only forward it to the correct business application. Although the BAH is not the transport header, data in the BAH can be used by transport applications to determine the routing header since it does contain the business sender, receiver and document details. It can als....
X X X X Extracts X X X X
X X X X Extracts X X X X
....o be used by the business applications to determine the appropriate process to perform on the business message. Message fields description ISO Business Application Header Business Application Header (Refer related documentation “RBI_NG_RTGS_ISO20022_BusinessApplicationHeader") ISO 20022 Message Reserve Bank of India ISO message "pacs.004.001.03 PaymentReturnV03" 1| Page à¤à¤¾à¤°à¤¤à¥€ RESERVE रिज़रà¥à¤µ बैंक BANK OF IND ISO20022 standard Message Implementation Message Item ISO20022 Messages - pacs.004.001.03 XML tag Description Index ISO NEFT/ Rules Example Data Multi RTGS Туре multip Payment ReturnV03 licity Message root Root tag for PaymentReturn Message [1..1] GroupHeader Fields common to all the 1.0 [1..1] transaction in the message Messageldentification Uniquely identifies the message 1.1 [1..1] [1..1] Uniquely identifies message HDFC201210181000 Recommend 000218 Messageldentification be structured as: XXXX-Sender IFSC [4] YYYYMMDD - Creation Date Reverse [8] X-Channel [1] nnnnnnnnn-Sequence Number [9] The values of Channel Identification (X) is the same as defined for TransactionIdentific....
X X X X Extracts X X X X
X X X X Extracts X X X X
....ation CreationDateTime Payment origination date time 1.2 [1..1] [1..1] NumberOfTransactions Number of transactions 1.7 [1..1] [1..1] Total ReturnedInterban Total amount of money moved between the instructing agent and the instructed agent in the return message 1.10 [0..1] [1..1] Reserve Bank of India ISO message "pacs.004.001.03 PaymentReturnV03" ISODateT ime Max15N umericTe xt Amount 2 | Page à¤à¤¾à¤°à¤¤à¥€ RESERVE रिज़रà¥à¤µ बैंक BANK OF IND ISO20022 standard Message Implementation Message Item XML tag Description ISO20022 Messages - pacs.004.001.03 PaymentReturnV03 Interbank SettlementDat e Index ISO NEFT/ Rules Example Data Multi RTGS Туре multip licity 1.11 [0..1] [0..1] ISO Date SettlementInformation Settlement Method Specifies the details on how the settlement of the transactions between the instructing agent and the instructed agent is completed. Method used to settle payments 1.12 [1..1] [1..1] [1..1] [1..1] Default value 'CLRG' Code Other Codes are: CLRG, COVE, INDA, INGA OriginalGroupInformati | on OriginalMessageIdentif ication OriginalMessageNameI 2.3 [0..1] [0..1] me TransactionIn....
X X X X Extracts X X X X
X X X X Extracts X X X X
....formatio n Contains information on individual transactions 3.0 [0..n] [1..10] NEFT Reserve Bank of India ISO message "pacs.004.001.03 PaymentReturnV03" [1..1] RTGS Max35T ext Max35T ext ISODate 3| Page à¤à¤¾à¤°à¤¤à¥€ RESERVE रिज़रà¥à¤µ बैंक BANK OF IND ISO20022 standard Message Implementation Message Item XML tag Description ISO20022 Messages - pacs.004.001.03 PaymentReturnV03 Index ISO NEFT/ Rules Multi RTGS multip licity ReturnIdentification Transaction Identification, as assigned by an returning party for an sending party, to unambiguously Identify the returned transaction. 3.1 [0..1] [1..1] Transaction Reference Number of 22 Chars of Instucting Party Use UTR (Unique Transaction Reference) format (22 characters) XXXX-Sender IFSC [4] X-Payment System [1] X-Channel [1] YYYYMMDD-Date [8] nnnnnnnn-Sequence Number [8] Original TransactionIde ntification Unique Transaction reference, as 3.8 [0..1] [1..1] Original assigned by the original first Transaction Reference instructing agent(sender), to unambiguously identify the Number Instructing party. ReturnedInterbankSettl Reserve Bank of India ISO message "pacs.004.001....
X X X X Extracts X X X X
X X X X Extracts X X X X
.....03 PaymentReturnV03" Transaction. This must contain Transaction Reference Number of the received inward credit message at bank branch that is returned. Amount being returned between instructing and instructed parties on account of returned transaction. This amount should be same as the amount requested by the originator as NEFT doesn't have concept of settling a part amount and returning the rest. 3.11 [1..1] [1..1] Amount Example Data Туре Max35T ext Max35Te xt Amount 4 | Page à¤à¤¾à¤°à¤¤à¥€ RESERVE रिज़रà¥à¤µ बैंक BANK OF IND ISO20022 standard Message Implementation Message Item XML tag Description Index ISO NEFT/ Rules Example Data ISO20022 Messages - Multi RTGS Туре pacs.004.001.03 multip PaymentReturn V03 licity InterbankSettlementD ate Settlement Date. Date on which reversal of the settlement takes place. It can be only the current date. It will have the Date of the return transaction and not the original instruction 3.12 [0..1] [1..1] ISODate InstructingAgent Sender IFSC .This should be the IFSC that is sending the return request and not the branch that has sent the original instru....
X X X X Extracts X X X X
X X X X Extracts X X X X
....ction 3.20 [0..1] [1..1] FinancialInstitutionlden tification ClearingSystemMembe rldentification This should contain the Sender IFSC of the transaction i.e branch IFSC code.This is the Code allocated to a financial institution by the ISO 9362 Registration Authority as described in ISO 9362 MemberIdentification Instructed Agent FinancialInstitutionlden tification Reserve Bank of India ISO message "pacs.004.001.03 PaymentReturnV03" [1..1] [1..1] [0..1] [1..1] Sending Branch's IFSC [1..1] [1..1] Sending Branch's IFSC Max35Te xt Receiver IFSC .This should be the IFSC to which the return transaction is being sent i.e. the IFSC which is receiving the return message 3.21 [0..1] [1..1] [1..1] [1..1] 5 Page à¤à¤¾à¤°à¤¤à¥€ RESERVE रिज़रà¥à¤µ बैंक BANK OF IND ISO20022 standard Message Implementation Message Item XML tag Description ISO20022 Messages - pacs.004.001.03 Payment ReturnV03 ClearingSystemIdentific Index ISO NEFT/ Rules Example Multi RTGS Data Туре multip licity [0..1] [1..1] ation MemberIdentification This should contain the Receiver IFSC of the transaction i.e. beneficiary branch where the [1..1]....
X X X X Extracts X X X X
X X X X Extracts X X X X
.... [1..1] Beneficiary branch's IFSC account needs to be credited back because of return request. This is the Code allocated to a financial institution by the ISO 9362 Registration Authority as described in ISO 9362 Return ReasonInformati Provides detailed information on the 3.22 [O..n] [1..1] return reason. on Originator Originator of remittance 3.23 [0..1] [0..1] Originator of Remittance information (Party that issues the return) [This message item is composed of the following Party Identification43 element(s). i.e., Name, Postal Address, Contact Details, etc.] Name PostalAddress AddressLine [0..1] [0..1] [0..1] [0..1] [0..7] [0..4] Reserve Bank of India ISO message "pacs.004.001.03 PaymentReturnV03" Max140Te xt Max70Tex t 6 | Page à¤à¤¾à¤°à¤¤à¥€ RESERVE रिज़रà¥à¤µ बैंक BANK OF IND ISO20022 standard Message Implementation Message Item ISO20022 Messages - pacs.004.001.03 XML tag Description Index ISO Multi NEFT/ Rules RTGS Example Data Type multip PaymentReturnV03 licity ContactDetails [0..1] [0..1] MobileNumber [0..1] [0..1] EmailAddress Address for electronic mail (e-mail). [0..1] [0..1] PhoneNu mber Max204....
X X X X Extracts X X X X
X X X X Extracts X X X X
....8 Text Reason Code Specifies the reason for the return. 3.24 [0..1] [1..1] This must contain the reason codes for rejection [1..1] [1..1] NARR External ReturnRe For Other Reason Codes are: ason Co de AdditionalInformation Further details on the return reason 3.27 [0..n] [1..1] Reserve Bank of India ISO message "pacs.004.001.03 PaymentReturnV03" NARR, BE01, BE06, CUST, .... For detail pl refer to External CodeLists_3Q2012_220ct201 2_v4 RETURN DUE TO WRONG ACCOUNT CREDIT Max105T ext 7 | Page â— à¤à¤¾à¤°à¤¤à¥€ RESERVE रिज़रà¥à¤µ बैंक BANK OF INDIA ISO20022 standard Message Implementation Payment Status Report * ISO message "pacs.002.001.04, FITOFIPaymentStatus ReportV04" Applicable Areas: RTGS 1) For defining "MNSB Response" in RTGS. 2) For defining "Own Account Transfer Response" in RTGS This message formats would replace the current R13 used in current RTGS for MNSB response & R40 used in Current RTGS for Own A/c Transfer (OAT) response. *Corresponds to R13 & R 40 in current RTGS. The ISO 20022 Business Message consists of two parts: (1) ISO 20022 Business Appl. Header (2) ISO 20022 Messages ISO 20022 Busine....
X X X X Extracts X X X X
X X X X Extracts X X X X
....ss Appl. Header ISO 20022 Message Business Message Business Application Header is a business header and should not be confused with a file or transport header. It is created before the transport routing header is applied to the business message and is retained after the transport header is removed. So any parties between the two business applications that don't perform a business function are not mentioned in the BAH. Such 'technical' middle men don't open or change the Business Message; they only forward it to the correct business application. Although the BAH is not the transport header, data in the BAH can be used by transport applications to determine the routing header since it does contain the business sender, receiver and document details. It can also be used by the business applications to determine the appropriate process to perform on the business message. Message fields description ISO Business Application Header Business Application Header (Refer related documentation “RBI_NG_RTGS_ISO20022_BusinessApplicationHeader") Reserve Bank of India ISO message "pacs.002.001.04, FITOFIPaymentStatus ReportV04" 1| Page • à¤à¤¾à¤°à¤¤à¥€à¤¯ RESERVE à....
X X X X Extracts X X X X
X X X X Extracts X X X X
....°à¤¿à¥›à¤°à¥à¤µ बैंक BANK OF IN ISO 20022 Message ISO20022 Message pacs.002.001.04 FITOFIPaymentStatusRep ortV04 Message Item ISO20022 standard Message Implementation XML tag Description Index ISO RTGS Rules Multi Fields common to 1.0 [1..1] [1..1] all the transaction in the message Messageldentification Uniquely identifies 1.1 [1..1] [1..1] Uniquely identifies message the message Point to point Recommend Messageldentification be structured as: reference, as assigned by the account servicing institution, and sent to the account owner or the party authorised to receive the message, to XXXX-Sender IFSC [4] YYYYMMDD - Creation Date Reverse [8] ✗- Channel [1] nnnnnnnnn- Sequence Number [9] The values of Channel Identification (X) is the same as defined for TransactionIdentification unambiguously identify the message. CreationDateTime Message date time 1.2 [1..1] [1..1] Time upto seconds only OriginalGroupInformatio information concerning the group of transactions, to Reserve Bank of India which the status report message ISO message "pacs.002.001.04, FITOFI PaymentStatus ReportV04" Example Data Type Max35Te HDFC201210181000000218 xt 2....
X X X X Extracts X X X X
X X X X Extracts X X X X
....011-04- 24T09:30:32 2 Page ISODateT ime à¤à¤¾à¤°à¤¤à¥€ RESERVE रिज़रà¥à¤µ बैंक BANK OF IND ISO20022 standard Message Implementation ISO20022 Message pacs.002.001.04 FITOFIPaymentStatusRep ortV04 Message Item XML tag Description Original Messageldentific refers to. Transaction ation reference. This msg element is part of OrgnlGrplnfAndSts block. Original MessageNameld entification original message name identifier to which the message refers. Index ISO RTGS Rules Multi 2.1 [1..1] [1..1] 2.2 [1..1] [1..1] Example Data Туре TREF097865123125 xt pacs.009.001.03 xt This msg element is part of OrgnlGrplnfAndSts block. Original Creation DateAnd Time 2011-04- 24T09:30:32 This msg element is part of OrgnlGrplnfAndSts block. GroupStatus Specifies the status 2.6 [0..1] [1..1] of a group of transactions. Status code- ACSC/ACSP/ACTC/ Mandatory in RTGS implementation For details on status code, pl refer to para 2.6 of documentation "Payment Clearing & Settlement - Maintenance 2012 by ISO". ACSC StatusReasonInformation PDNG/RCVD/RJCT. This msg element is part of OrgnlGrplnfAndSts block. Reason for success 2.7 [O..n] ....
X X X X Extracts X X X X
X X X X Extracts X X X X
....[0..1] Repeats only once / failure. This msg element is Reserve Bank of India ISO message "pacs.002.001.04, FITOFI PaymentStatus ReportV04" 3| Page ISODateT ime Code à¤à¤¾à¤°à¤¤à¥€ RESERVE रिज़रà¥à¤µ बैंक BANK OF IND ISO20022 Message pacs.002.001.04 FITOFIPaymentStatusRep ortV04 Message Item ISO20022 standard Message Implementation XML tag Description Index ISO RTGS Rules Multi Example Data Туре part of OrgnlGrplnfAndSts block. Reason Reason code 2.9 [0..1] [1..1] Proprietary Actual reason code 2.11 [1..1] [1..1] /!3x Reason desc and reason /012 No Liquidity Max35Te xt description Original Transaction Key elements 3.20 [0..1] [1..1] Reference used to identify Mandatory in RTGS implementation for Net Clearing response the original .transaction that is being referred to. InterbankSettlementAmo This msg element is the part of OrgnITxRef block 3.21 [0..1] [1..1] Mandatory in RTGS implementation 10000.00 t PaymentTypeInformatio Set of elements [0..1] [1..1] n used to provide further details of the type of payment. This msg element is the part of OrgnITxRef block. Locallnstrument User community [0..1] [1....
X X X X Extracts X X X X
X X X X Extracts X X X X
......1] specific instrument. This element is used to specify a local instrument, local clearing option and/or further qualify the service or service level Reserve Bank of India ISO message "pacs.002.001.04, FITOFI PaymentStatus ReportV04" 4| Page à¤à¤¾à¤°à¤¤à¥€ RESERVE रिज़रà¥à¤µ बैंक BANK OF IND ISO20022 Message pacs.002.001.04 FITOFIPaymentStatusRep ortV04 Message Item Proprietary ISO20022 standard Message Implementation XML tag Description Index ISO RTGS Rules Multi Proprietary [0..1] [1..1] instrument type code Type of Local Instrument. RTGSFITOFICredit' or Clearing party/ Debtor sponsoring 3.1.63 4 [0..1] [0..1] institution. This msg element is the part of OrgnITxRef block. ClearingSystemMemberl FinancialInstitutionIdenti fication dentification [1..1] [1..1] Member Identification [1..1] [1..1] DebtorAccount Unambiguous -'RTGSOwnAccTtransfer' or -'RTGSNetSettlementXXzNN' Where 'XX' is the clearing type which may take values 'GC', 'IB', 'FX', MC, SE, OT & so on. 'z' is the indicator which may take values C-Original, R-Return, L-Last Return. "NN" is the return serial. "GC" stands for guaranteed settlement of Se....
X X X X Extracts X X X X
X X X X Extracts X X X X
....curities and CBLO segment. "IB" stands for guaranteed settlement of FOREX segment. "FX" stands for non guaranteed settlement. "MC" Stands for MICR Clearing "SE" stands for non-guaranteed MNSB "OT" stands for Other MNSB. Mandatory in RTGS implementation for Own Account Transfer and Net Clearing response 3.1.677 [0..1] [0..1] Mandatory in RTGS implementation for Reserve Bank of India ISO message "pacs.002.001.04, FITOFIPaymentStatus ReportV04" Example Data Туре Max35T ext Max35Te HDFC0239777 xt 5 | Page à¤à¤¾à¤°à¤¤à¥€ RESERVE रिज़रà¥à¤µ बैंक BANK OF IND ISO20022 Message pacs.002.001.04 FITOFIPaymentStatusRep ortV04 Message Item ISO20022 standard Message Implementation XML tag Description identification of the account of the debtor to which a debit entry will be made as a result of the transaction. This msg element Index ISO RTGS Rules Multi Own Account Example Data Туре is the part of OrgnITxRef block. Identification [1..1] [1..1] Other [1..1] [1..1] Identification Account Number [1..1] [1..1] From account of participant Currency Account currency [0..1] [1..1] For NG-RTGS, "INR" is the onl....
X X X X Extracts X X X X
X X X X Extracts X X X X
....y currency that can be specified. Clearing party / 3.1.79. [0..1] [0..1] Creditor sponsoring 9 institution. Mandatory in RTGS implementation for Own Account Transfer and Net Clearing response 34545353 INR This msg element is the part of OrgnITxRef block. FinancialInstitutionIdenti fication ClearingSystemMemberl dentification [1..1] [1..1] Member Identification [1..1] [1..1] HDFC0239777 Max35Te xt CreditorAccount Unambiguous identification of 3.1.842 [0..1] [0..1] Mandatory in RTGS implementation for Own Account the account of the creditor to which a Reserve Bank of India ISO message "pacs.002.001.04, FITOFIPaymentStatus ReportV04" 6 Page à¤à¤¾à¤°à¤¤à¥€ RESERVE रिज़रà¥à¤µ बैंक BANK OF IND ISO20022 Message pacs.002.001.04 FITOFIPaymentStatusRep ortV04 Message Item ISO20022 standard Message Implementation XML tag Description credit entry will be made as a result of the transaction. This msg element Index ISO RTGS Rules Multi Example Data Туре is the part of OrgnITxRef block. Identification [1..1] [1..1] Other [1..1] [1..1] Identification Account Number [1..1] [1..1] From account of participant 34545....
X X X X Extracts X X X X
X X X X Extracts X X X X
....353 Currency Account currency [0..1] [1..1] For NG-RTGS, "INR" is the only currency that can be specified. INR xt Code Note:- [1..1] -> Mandatory; [0..1] -> Optional; [1..n] -> Mandatory and n times repeated; [0..n] -> Optional and n times repeated; Reserve Bank of India 7| Page ISO message "pacs.002.001.04, FITOFI PaymentStatus ReportV04"<BR> News - Press release - PIB....