TIPS Message Specifications Gap Analysis

Size: px

Start display at page:

Download "TIPS Message Specifications Gap Analysis"

Roland Hicks
5 years ago
Views:

3 . Document scope This document aim at describing the differences between TIPS messages implementation EPC guidelines. Reference documents are : - EPC-6 SCT Inst Interbank IG 07 V. related XSD files - TIPS UDFS.0 Where applicable, every difference is assigned a category to describe our understing suggest possible follow up methods for aligning the design of the Xml definitions. The list of identified categories is as follows: - Category : Gap on SCT Inst - Category : Gap on TIPS - Category 3 : EPC clarification needed For items which do not fall on any of these categories, thus not requiring any action, n/a is put in the Category column.. Charset EPC recommendations on charset (chapter.4), mate banks to support Latin charset leaving the choice to adopt different charsets upon agreement within users community. Following the TIPS Contact group written procedure decision, TIPS supports the UTF-8 charset as far as messages described in the EPC Interbank document are concerned. On top of this, EPC requires specific rules on field containing references, identifications identifiers. Actual text in chapter.4 says: References, identifications identifiers must respect the following: o Content is restricted to the Latin character set as defined above o Content must not start or end with a / o Content must not contain // s Following these requirements, for such fields TIPS implementation has been performed by applying a specific regular expression pattern in the appropriate Xml Schema Definition data types. All rights reserved. Page 3

4 The pattern is: <xs:pattern value="[0-9a-za-z\-\?:\(\)\.,'\+](/?([0-9a-za-z\-\?:\(\)\.,'\+ ]/?)*[0-9a-zA-Z\-\?:\(\)\.,'\+]+)?"/> Errors due to not compliance to the pattern are returned to the sender with an admi.007 message out of ESMIG technical validation. 3. Message content 3.. pacs.008 Field name Xpath TIPS EPC Comment Category InstructingAgent/BIC FIToFICstmrCdtTrf/GrpHdr /InstgAgt/FinInstnId/BIC InstructedAgent/BIC FIToFICstmrCdtTrf/GrpHdr /InstdAgt/FinInstnId/BIC DebtorAgent/BIC FIToFICstmrCdtTrf/CdtTrf TxInf/DbtrAgt/FinInstnId/ BIC CreditorAgent/BIC FIToFICstmrCdtTrf/CdtTrf TxInf/CdtrAgt/FinInstnId/B IC Purpose/Proprietary FIToFICstmrCdtTrf/CdtTrf Field must be dropped from TIPS TxInf/Purp/Prtry All rights reserved. Page 4

5 3.. pacs.00 Field name Xpath TIPS EPC Comment Category InstructingAgent/BIC FIToFIPmtStsRpt/GrpHdr/I nstgagt/fininstnid/bic InstructedAgent/BIC FIToFIPmtStsRpt/GrpHdr/I nstdagt/fininstnid/bic DebtorAgent/BIC FIToFIPmtStsRpt/TxInfAnd Sts/OrgnlTxRef/DbtrAgt/Fi ninstnid/bic Additional Information FIToFIPmtStsRpt/TxInfAnd Element should be dropped from TIPS Sts/StsRsnInf/AddtlInf as not foreseen in the Implementation Guideline. Interbank Settlement FIToFIPmtStsRpt/TxInfAnd Element should be dropped from TIPS Amount Sts/OrgnlTxRef/IntrBkSttl as not foreseen in the mamt Implementation Guideline. CreditorAgent FIToFIPmtStsRpt/TxInfAnd Element should be dropped from TIPS Sts/OrgnlTxRef/CdtrAgt as not foreseen in the Implementation Guideline. 3.. pacs.08 Field name Xpath TIPS EPC Comment Category InstructingAgent/BICFI FIToFIPmtStsReq/GrpHdr/ InstgAgt/FinInstnId/BICFI All rights reserved. Page 5

6 InstructedAgent/BICFI FIToFIPmtStsReq/GrpHdr/ InstdAgt/FinInstnId/BICFI TransactionInformation/ FIToFIPmtStsReq/TxInf/Or This block contained elements are OriginalGroupInformatio gnlgrpinf marked in white in the n Implementation Guideline. This means that must not be used (unless agreed) then need to be dropped from EPC Xml Schema Definition. PaymentTypeINformatio FIToFIPmtStsReq/TxInf/Or The EPC definition for the containing n/instructionpriority gnltxref/pmttpinf/instrpr block PaymentTypeInformation, ty includes attributes AT-40 AT-45. This means that only ServiceLevel, LocalInstrumentType CategoryPurpose shall be included. This field has been erroneously included in the EPC must be dropped. PaymentTypeINformatio FIToFIPmtStsReq/TxInf/Or The EPC definition for the containing n/clearingchannel gnltxref/pmttpinf/clrcha block PaymentTypeInformation, nl includes attributes AT-40 AT-45. This means that only ServiceLevel, LocalInstrumentType CategoryPurpose shall be included. This field has been erroneously included in the EPC must be dropped. PaymentTypeINformatio FIToFIPmtStsReq/TxInf/Or The EPC definition for the containing n/sequencetype gnltxref/pmttpinf/seqtp block PaymentTypeInformation, includes attributes AT-40 AT-45. This means that only ServiceLevel, LocalInstrumentType CategoryPurpose shall be included. This field has been erroneously included in the EPC must All rights reserved. Page 6

7 be dropped. DebtorAgent FIToFIPmtStsReq/TxInf/Or only both EPC describes this field with AT-06 gnltxref/dbtragt FinancialInstitution FinancialInstitutionIDe The BIC code of the Originator Bank. Identification ntification BranchIdentification In the pacs.008 distributed by EPC, the field has been designed as it is in TIPS, therefore allowing only FinancialInstitutionIDentification. The BranchIdentification must be dropped from this message to align. 3.. camt.056 Field name Xpath TIPS EPC Comment Category Assigner FIToFIPmtCxlReq/Assgnmt Limited to several TIPS is compliant to specs as only n/a /Assgnr Agent/BIC options deals with Banks EPC specifies that the field must be Limited to BIC to identify a bank or CSM. Since messages are used in bank-tobank mode also, no change is required in TIPS EPC implementations. Assignee FIToFIPmtCxlReq/Assgnmt Limited to several TIPS is compliant to specs as only n/a /Assgne Agent/BIC options deals with Banks EPC specifies that the field must be Limited to BIC to identify a bank or CSM. Since messages are used in bank-tobank mode also, no change is required in TIPS EPC implementations. Underlying FIToFIPmtCxlReq/Undrlyg Cardinality.. Cardinality..n TIPS allows only one transaction to be n/a cancelled for message. No change is required. TransactionInformation Cardinality.. Cardinality..n TIPS allows only one transaction to be n/a TxInf cancelled for message. No change is required. Originator/PrivateIdentif According to EPC Interbank guideline, TxInf/CxlRsnInf/Orgtr/Id/P the Originator can be identified with All rights reserved. Page 7

8 ication rvtid the PrivateIdentification when it is a non financial institution. EPC should update the SettlementInformation Does not include EPC Interbank document does not 3 TxInf/OrgnlTxRef/SttlmInf Reimbursement Reimbusement specify that Reimbursement information. information. information must be dropped, namely: - InstgRmbrsmntAgt - InstgRmbrsmntAgtAcct - InstdRmbrsmntAgt - InstdRmbrsmntAgtAcct - ThrdRmbrsmntAgt - ThrdRmbrsmntAgtAcct This shall be checked by EPC to clarify. PaymentTypeINformatio All the elemens are Only ServiceLevel, The EPC definition for the containing n TxInf/OrgnlTxRef/PmtTpIn included in the LocalInstrument block PaymentTypeInformation, f CategoryPupose includes attributes AT-40 AT-45. This means that only ServiceLevel, LocalInstrumentType CategoryPurpose shall be included. This field has been erroneously included in the TIPS must be dropped. RemittanceInformation Different Different There is no indication on how the 3 TxInf/OrgnlTxRef/RmtInf elements nested in this component must be considered. Reference to AT- 05 only says that either Structured or Unstructured can be used. To be on the safe side, TIPS does not apply any restriction. UltimateDebtor/PostalA Element should be dropped from TIPS ddress TxInf/OrgnlTxRef/UltmtDb tr/pstladr DebtorAgent/BIC TxInf/OrgnlTxRef/DbtrAgt/ FinInstnId/BIC All rights reserved. Page 8

9 CreditorAgent/BIC TxInf/OrgnlTxRef/CdtrAgt/ FinInstnId/BIC 3.. camt.09 Field name Xpath TIPS EPC Comment Category Assigner RsltnOfInvstgtn/Assgnmt/ Limited to several TIPS is compliant to specs as only n/a Assgnr Agent/BIC options deals with Banks EPC specifies that the field must be Limited to BIC to identify a bank or CSM. Since messages are used in bank-tobank mode also, no change is required in TIPS EPC implementations. Assignee RsltnOfInvstgtn/Assgnmt/ Limited to several TIPS is compliant to specs as only n/a Assgne Agent/BIC options deals with Banks EPC specifies that the field must be Limited to BIC to identify a bank or CSM. Since messages are used in bank-tobank mode also, no change is required in TIPS EPC implementations. SettlementInformation RsltnOfInvstgtn/CxlDtls/Tx Does not include EPC Interbank document does not 3 InfAndSts/OrgnlTxRef/Sttl Reimbursement Reimbusement specify that Reimbursement minf information. information. information must be dropped, namely: - InstgRmbrsmntAgt - InstgRmbrsmntAgtAcct - InstdRmbrsmntAgt - InstdRmbrsmntAgtAcct All rights reserved. Page 9

10 - ThrdRmbrsmntAgt - ThrdRmbrsmntAgtAcct This shall be checked by EPC to clarify. PaymentTypeINformatio RsltnOfInvstgtn/CxlDtls/Tx All the elemens are Only ServiceLevel, The EPC definition for the containing n InfAndSts/OrgnlTxRef/Pmt included in the LocalInstrument block PaymentTypeInformation, TpInf CategoryPupose includes attributes AT-40 AT-45. This means that only ServiceLevel, LocalInstrumentType CategoryPurpose shall be included. This field has been erroneously included in the TIPS must be dropped. RemittanceInformation RsltnOfInvstgtn/CxlDtls/Tx Different Different There is no indication on how the 3 InfAndSts/OrgnlTxRef/Rmt elements nested in this component Inf must be considered. Reference to AT- 05 only says that either Structured or Unstructured can be used. To be on the safe side, TIPS does not apply any restriction. UltimateDebtor/PostalA RsltnOfInvstgtn/CxlDtls/Tx Element should be dropped from TIPS ddress InfAndSts/OrgnlTxRef/Ult mtdbtr/pstladr DebtorAgent/BIC RsltnOfInvstgtn/CxlDtls/Tx InfAndSts/OrgnlTxRef/Dbt ragt/fininstnid/bic CreditorAgent/BIC RsltnOfInvstgtn/CxlDtls/Tx InfAndSts/OrgnlTxRef/Cdtr Agt/FinInstnId/BIC 3.. pacs.004 Field name Xpath TIPS EPC Comment Category All rights reserved. Page 0

11 InstructingAgent/BIC PmtRtr/GrpHdr/InstgAgt/FinIn stnid/bic InstructedAgent/BIC PmtRtr/GrpHdr/InstdAgt/FinIn stnid/bic Originator/PostalAdd PmtRtr/TxInf/RtrRsnInf/Orgtr/ Element should not be part of the erss PstlAdr dropped from TIPS PaymentTypeINform PmtRtr/TxInf/OrgnlTxRef/Pmt All the elemens are Only ServiceLevel, The EPC definition for the containing ation TpInf included in the LocalInstrument block PaymentTypeInformation, CategoryPupose includes attributes AT-40 AT-45. This means that only ServiceLevel, LocalInstrumentType CategoryPurpose shall be included. This field has been erroneously included in the TIPS must be dropped. RemittanceInformati PmtRtr/TxInf/OrgnlTxRef/Rmt Different Different There is no indication on how the 3 on Inf elements nested in this component must be considered. Reference to AT- 05 only says that either Structured or Unstructured can be used. To be on the safe side, TIPS does not apply any restriction. 4. Categories way forward For every identified category assigned to each deviation, the following way forward could be put in place. - Category : Gap on SCT Inst Remarks should be sent to EPC/SWIFT for analysis. EPC/SWIFT are in charge to provide with corrected XSD. All rights reserved. Page

12 Corrections may not be deemed necessary as XSD are provided with a disclaimer stating that they are published for information purpose only shall not be used in production environments. - Category : Gap on TIPS If deemed necessary by the TIPS Contact Group, a Change Request should be raised to close all the gaps. Impact in TIPS seems low because affected fields are not part of the core information needed for settlement. - Category 3 : EPC clarification needed Remarks should be sent in terms of question for EPC/SWIFT to clarify. After the clarification is provided, those items will fall either in category A or B follow that specific way forwards. All rights reserved. Page

Rubric ECB-UNRESTRICTED. Q&A of the month ECB DG-MIP/MID. TIPS Contact Group. 8th Meeting on 4 July

Rubric ECB-UNRESTRICTED. Q&A of the month ECB DG-MIP/MID. TIPS Contact Group. 8th Meeting on 4 July Rubric ECB DG-MIP/MID Q&A of the month TIPS Contact Group 8th Meeting on 4 July 2018 We were wondering whether UDFS or XSD is leading specification in case these would contradict: for example, UDFS says