Document Overview. Credit Transfer PAIN XML File Structure. 1.1 Background. 1.2 Document Purpose. The Character Set.

Transcription

1 ASOCIAȚIA ROMÂNĂ A BĂNCILOR Credit Transfer PAIN XML File Structure Document Overview 1.1 Background 1.2 Document Purpose The Character Set Fields Types Usage Rules Unused s Depth Structure File Name File Format Table Appendix

2 Credit Transfer PAIN XML File Structure 1. Document Overview This document details the PAIN ISO XML file format that will be accepted by members of Romanian Banking Association for SEPA Credit Transfers in EUR. This document was compiled with information from: RBA_Customers_File_Format_mandatory_minimum_accepted_fields. Failure to provide files that meet this specification may results in files and/or transactions being rejected, either by Romanian Banks or by the beneficiary bank. 1.1 Background SEPA aims to create a single, integrated and standardised payments market across 33 countries in Europe. Credit Transfer Originators must be SEPA compliant by 31 Octomber 2016 in order to continue making electronic non-urgent euro payments (SEPA payments) in Romania. Further background information is available on our website: www://arb.ro RBA (Romanian Banks Asociation) has also published a Credit Transfer Readiness Checklist on the RBA website. To ensure you are aware of the changes required within your business please visit: www://arb.ro 1.2 Document Purpose The purpose of this document is to outline the PAIN XML file format that will be accepted by all Romanian Banks. Knowledge of XML is recommended to interpret this document. 2. The Character Set The PAIN message format can support a range of characters; the following are the supported characters which are the basic Latin character set: a b c d e f g h i j k l m n o p q r s t u v w x y z A B C D E F G H I J K L M N O P Q R S T U V W X Y Z /-? : ( )., ' + Space If required, the following characters can also be used in text or information fields only, but must be provided using the XML representation shown. Special XML Character XML Representation & (ampersand) & < (left brace) < > (right brace) > (double quotation) " (single quotation) &apos; e.g. Apa & Canal would populate their name in a PAIN.001, appearing as: <Cdtr> <Nm>Apa & Canal </Nm> </Cdtr> 3. Field Types The following section details the type of fields that are contained in the specification document. Fields Fields must be populated or the file/batch will be rejected Fields Originator to decide if this field needs to be populated Payment Information (Batch)/Transaction Level There are a number of optional fields that may be populated at payment information level or at transaction level, however it is recommended They are populated at payment information level if being used The following fields are optional to populate and may be populated at payment information level :

3 Note: Senders must ensure that the content of Identifiers/reference data elements is restricted to the restricted basic Latin character set (across). If non supported characters are used in these fields they may lead to rejection of files or transactions in the payment chain. Exceptionally, the content of Identifiers/reference data elements Must not start or end with a / Must not contain two consecutive / s anywhere in the data element These identifier fields include the following: Fields Creditor Account Fields Initiating Party Ignore Option Private Identification Proprietary Other Equivalent Amount 4. Usage Rules For a number of fields usage rules must be followed. These are outlined throughout the specification and failure to adhere to these usage rules will result in failed payments/ batches/files. 5. Unused s Where optional tags have not been populated, the tag should be omitted from the file along with its parent tag. 6. Depth Sructure For example: + would represent a Parent Element ++ would represent the Child Element of the previous Parent Element TAG DEPTH TAG STRUCTURE + <> <> ++ <> <> +++ <> <> 7. File Name The following rules apply to the file name: 1. The file name must contain the following reference PAIN001. This may appear at the beginning or within the filename. 2. The file extension must be.xml 3. Filename must not exceed 50 characters. 4. Only alphanumeric characters must be used in the filename (preceding the file extension.xml ). 5. Must not contain spaces Example: PAIN001.xml It is recommended that a unique file name is used for each file. For example, this can be achieved by incorporating a date or sequence number of your own choosing. Fields -Fields must be populated or the file/batch will be rejected Fields

4 8. File Format Table Credit Transfer PAIN XML File Structure Or Field Name- <?xml version= 1.0 encoding= UTF-8?> <Document xmlns= urn:iso:std:iso:20022:tech:xsd:pain xmlns:xsi= > Level Content / / This tag must always be placed before the group header tag <?xml version= 1.0 encoding= UTF-8?> <Document xmlns= urn:iso:std:iso: 20022:tech:xsd:PAIN xmlns:xsi= /XMLSchema-instance > characters XML tags and data included <CstmrDrctDbtInitn> This tag must always be placed before the group header tag <CstmrCdtTrfInitn> - XML tag for message Group Header Block Or Field Name- Level Content / / 1.0 Group Header <GrpHdr> Message Identification <MsgId> ++ Yes Originator s unique identifier of the submitted file. Note: This ID cannot be reused on future files 1.2 Creation Date Time <CreDtTm> ++ Yes Date and time that the file was created Group Header Block - this can only occur once per file Or Field Name- Level Content / / 1.6 Number Of Transactions <NbOfTxs> ++ Yes Number of individual transactions Data Type: ISODateTime Format: YYYY-MM-DDTHH:MM:SS e.g T08:35:30 Data Type: Max15NumericText Format: [0-9] {1,15} 1.7 Control Sum <CtrlSum> ++ Yes Total of all individual amounts included Data Type: Decimal Number Format: Fraction Digits: 2 Total Digits: Initiating Party <InitgPty> ++ Party that initiates the payment for customer Not use in processing Not sent in clearing file Identification <Id> {Or Organisation Identification <OrgId> Or} Private Identification <OrgId> ++++ If it's used will be ignored

5 Payments Information Block- this can occur multiple time Or Field Name- 2.0 Payment Information <PmtInf> 2.1 Payment Information dentification <PmtInfId> Level Content / / + ++ Yes Originator s unique identifier of the batch of transactions Format: Min length: Payment Method <PmtMtd> ++ Yes Only TRF is allowed ++ Yes Identifies whether a single entry Data Type: Indicator per individual transaction or a Format: True, false 2.3 Batch Booking <BtchBookg> batch entry for the sum of the amounts of all transactions within the group of a message is requested Specific use by each Romanian bank 2.4 Number Of Transactions <NbOfTxs> 2.5 Control Sum <CtrlSum> 2.6 Payment Type Information <PmtTpInf> Yes Data Type: Numeric Text Format: [0-9] {1,15} ++ Yes Total of all individual amounts Data Type: Decimal Number included in the batch Format: Fraction Digits: 2 Total Digits: 18 Set of elements used to further specify the type of transaction 2.7 Instruction Priority <InstrPrty> +++ Yes Agreement under which or rules under which the transaction should be processed Payment Type Information usage rule:this is optional If used, it is recommended to be filled in at "Payment information" level and not at "Credit Transfer Transaction information". If filled at both levels then it will be ignored at "Credit Transfer Transaction information" level Specific use by each Romanian bank 2.8 Service Level <SvcLvl> {Or Code <Cd> ++++ Yes Only SEPA is allowed 2.10 Or} Proprietary <Prtry> ++++ Yes If it's used will be ignored 2.11 Local Instrument <LclInstrm> {Or Code <Cd> ++++ Yes Mandatoy Specifies the local instrument, as published in an external local instrument code list. Min length: Or} Proprietary <Prtry> ++++ Yes Mandatoy Specifies the local instrument, as a proprietary code. Min length: 1 Local instrument Usage Rule This is an optional field, if being used either Code or Proprietary is to be populated

6 Payments Information Block- this can occur multiple time Or Field Name- Level Content / / 2.14 Category Purpose <CtgyPurp> {Or Code <Cd> ++++ Yes Category purpose, as published in an external category purpose code list Or} Proprietary <Prtry> ++++ Yes 2.17 Requested Execution Date <ReqdExctnDt> ++ Yes Date the peyee/beneficiary ist o receive the payment Debtor <Cdtr> Format: Max length: 4 Min length: 1 see code list in appendix Data type: ISO Date Format:YYYY-MM-DD Name <Nm> +++ Yes Name of the payer/originator Data Type:Text Format:Max length: Identification <Id> +++ Originator ID Code {Or Organisation Identification <OrgId> ++++ Unique way to identify an organisation BICOrBEI <BICOrBEI> Yes Code allocated to a financial institution or non financial institution by the ISO 9362 Registration Authority as described in ISO 9362 Banking Banking telecomunicatin messages-business identifier code (BIC) Data Type:Any BIC identifier Payments Information Block- this can occur multiple time Or Field Name- Level Content / / Other <Othr> Unique identification of an organisation, as assigned by an insitution,using an identification scheme Identification <Id> Yes Identification assigned by an institution Or} PrivateIdentification <PrvtId> Debtor Account <DbtrAcct> ++ Account of the Payer/Originator that will be debited Min length: 1 One occurrence of Other is allowed If it's used will be ignored Identification <Id> [Or IBAN <IBAN> ++++ Yes Only International Bank Account Number (IBAN) is allowed Only IBAN allowed Only IBAN allowed

7 Payments Information Block- this can occur multiple time Or Field Name- Level Content / / Or} Other<Othr> ++++ Yes If you used will be ignored 2.21 Debtor Agent <DbtrAgt> Financial Institution Identification <FinInstnId> BIC <BIC> ++++ Yes Bank Identifier Code Data Type:BIC Identifier 2.23 Ultimate Debtor <UltmtDbtr> ++ Ultimate Debtor Usage Rule Ultimate Debtor is an optional field, if used can be populated at either payment information (batch) or transaction level Name <Nm> +++ Yes Name of the Originator Reference Party Identification <Id> +++ Format: Max length: 70 Min length: {Or Organisation Identification <OrgId> BICOrBEI <BICOrBEI> Yes Code allocated to a financial institution or non financial institution by the ISO 9362 Registration Authority as described in ISO 9362 Banking Banking telecomunicatin messages-business identifier code (BIC) Data Type:Any BIC identifier Identification Usage Rule Either Organisation Identification or Private Identification to be populated Organisation Identification Usage Rule: Either BIC or BEI or one occurrence of Other is allowed Other <Othr> Identification <Id> Yes Unique identification of a party Scheme Name <SchmeNm> No {{Or Code <Cd> Yes Name of the identification scheme, in a coded form as published in an external list Or}} Proprietary <Prtry> Yes Name of the identification scheme, in free text form Issuer <Issr> Yes Entity that assigns the identification Or} Private Identification <PrvtId> Date And Place Of Birth <DtAndPlcOfBirth> Data Type: External Organisation Identification1Code Format: Max Length: 4 Min length: 1 Scheme Name Usage Rule Either Code or Proprietary to be populated Private Identification Usage Rule: Either Date and Place of Birth or one occurrence of Other is allowed

8 Payments Information Block- this can occur multiple time Or Field Name- Level Content / / Birth Date <BirthDt> Yes Date on which a person is born Data type: ISO Date Format:YYYY-MM-DD Province Of Birth <PrvcOfBirth> Yes Province where a person was born City Of Birth <CityOfBirth> Yes City where a person was born Country Of Birth <CtryOfBirth> Yes Country where a person was born Data Type: Country Code Format: [A- Z]{2,2} Other <Othr> One occurrence of Other is allowed Identification <Id> Yes Unique identification of a person Scheme Name <SchmeNm> No Scheme Name Usage Rule Either Code or Proprietary to be populated {Or Code <Cd> Yes Name of the identification scheme, in a coded form as published in an external list Data Type: External Organisation Identification1Code Format: Max Length: 4 Min length: Or} Proprietary <Prtry> Yes Name of the identification scheme, in free text form Issuer <Issr> Yes Entity that assigns the identification 2.24 Charge Bearer <ChrgBr> ++ Yes Specifies which party/parties will bear the charges associated with the processing of the payment transaction Only SLEV is allowed Credit Transfer Transaction Information Definition: Set of elements used to provide information on the individual transaction(s) included in the message Or Field Name- Level Content / / 2.27 Credit Transfer Transaction Information <CdtTrfTxInf> Payment Identification <PmtId> Instruction Identification <InstrId> ++++ Yes 2.30 End to End Identification <EndToEndId> ++++ Yes

9 Credit Transfer Transaction Information Definition: Set of elements used to provide information on the individual transaction(s) included in the message Or Field Name- Level Content / / 2.32 InstructionPriority <InstrPrty> +++ Yes 2.33 Service Level <SvcLvl> +++ Service level usage Rule:Either Code or Proprietary to be populated Specifies a pre-agreed service or level or Only SEPA is allowed 2.34 Code <Cd> ++++ Yes service between the parties as published in an external service level code list {Or 2.35 Or} Proprietary<Prty> ++++ Yes 2.36 Local Instrument <LclInstrm> +++ Yes Local Instrument usage Rule:Either Local Instrument or Code to be populated 2.37 {Or Code <Cd> ++++ Yes Specifies the local instrument 2.38 Or} Proprietary <Prtry> ++++ Yes Specifies the local instrument as a proprietary code 2.39 Category Purpose <CtgyPurp> +++ Category Purpose Usage Rule: Depending on the agreement between the Originator and the Originator Bank, Category Purpose may be forwarded to the Beneficiary Bank 2.40 {Or Code <Cd> ++++ Yes This is used by initating party to provide information concerning the processing of the paymentcode form Format: Max length: 4 See code list in appendix 2.41 Or} Proprietary <Prtry> ++++ Yes This is used by initating party to provide information concerning the processing of the paymentproprietary form 2.42 Amount <Amt> +++ The amount to be paid in full to the payee/beneficiary Amount usage Rule:Either Instructed Amount or Equivalent Amount to be populated 2.43 {Or Instructed Amount <InstdAmt> ++++ Yes Amount must be 0.01 or more and or less. Usage Rule: Only EUR is allowed The fractional part has a max of 2 digits

10 Credit Transfer Transaction Information Definition: Set of elements used to provide information on the individual transaction(s) included in the message Or Field Name- Level Content / / 2.44 Or} Equivalent Amount <EqvtAmt> ++++ Yes If it's used will be ignored 2.51 Charge Bearer <ChrgBr> +++ Yes Specifies which party/parties will bear the charges associated with the processing of the payment transaction Only SLEV is allowed Ultimate Debtor <UltmtDbtr> Name <Nm> ++++ Yes Name of the Originator Reference Party Format: Max length: Identification <Id> {Or Organisation Identification <OrgId> ++++ Yes BICOrBEI <BICOrBEI> Yes Code allocated to a financial institution or non financial institution by the ISO 9362 Registration Authority as described in ISO 9362 Banking Banking telecomunicatin messages-business identifier Data Type:Any BIC identifier code ( BIC) Other <Othr> Other <Othr> Identification <Id> Yes Identificationassigned by an institution Scheme Name <SchmeNm> No {{Or Code <Cd> Yes Name of the identification Data Type: External Organisation scheme, in a coded form as Identification1Code published in an external list Format: Max Length: 4 Identification Usage Rule Either Organisation Identification or Private Identification to be populated One occurrence of Other is allowed. Scheme Name Usage Rule Either Code or Proprietary to be populated Min length: 1

11 Credit Transfer Transaction Information Definition: Set of elements used to provide information on the individual transaction(s) included in the message Or Field Name- Level Content / / Or}} Proprietary <Prtry> Yes Name of the identification scheme, in free text form Issuer <Issr> Yes Entity that assigns the identification Or} Private Identification <PrvtId> ++++ Date And Place Of Birth <DtAndPlcOfBirth> Birth Date <BirthDt> Yes Date on which a person is born Province Of Birth <PrvcOfBirth> Yes Province where a person was born City Of Birth <CityOfBirth> Yes City where a person was born Country where a person was Data Type: Country Code Format: [A- Country Of Birth <CtryOfBirth> Yes born Z]{2,2} Other <Othr> Identification <Id> Yes Identification assign by an institution Scheme Name <SchmeNm> No Name of the identification Code <Cd> Yes scheme, in a coded form as {Or published in an external list Name of the identification Proprietary <Prtry> Yes Or} scheme, in free text form Entity that assigns the Issuer <Issr> Yes identification Creditor Agent <CdtrAgt> Financial Institution Identification <FinInstnId> BIC <BIC> Yes Bank Identifier Code Creditor <Cdtr> One occurrence of Other is allowed One occurrence of Other is allowed Scheme Name Usage Rule Either Code or Proprietary to be populated Name <Nm> ++++ Yes Name of the payee/beneficiary This field it is mandatory for customer

12 Credit Transfer Transaction Information Definition: Set of elements used to provide information on the individual transaction(s) included in the message Or Field Name- Level Content / / Postal Address <PstlAdr> Country <Ctry> Yes Country Address Line (2) <Adrline> Postal address in free format Yes text Credit Transfer Transaction Information Definition: Set of elements used to provide information on the individual transaction(s) included in the message Or Field Name- Level Content / / It is recommended to be max 2 iteration Identification <Id> {Or Organisation Identification <OrgId> ++++ Yes BICOrBEI <BICOrBEI> Yes Code allocated to a financial institution or non financial institution by the ISO 9362 Registration Authority as described in ISO 9362 Banking Banking telecomunicatin messages-business identifier Data Type:Any BIC identifier code (BIC) Other <Othr> Identification <Id> Yes Identification assigned by an institution Scheme Name <SchmeNm> No {{Or Code <Cd> Yes Name of the identification Data Type: ExternalOrganisation scheme, in a coded form as Identification1Code published in an external list Format: Max length: Or}} Proprietary <Prtry> Yes Name of the identification scheme, in free text form Issuer <Issr> Yes Entity that assigns the identification Identification Usage Rule This is an optional field group, if being used either Organisation Identification or Private Identification is to be populated One occurrence of Other is allowed. Scheme Name Usage Rule Either Code or Proprietary to be populated

13 Credit Transfer Transaction Information Definition: Set of elements used to provide information on the individual transaction(s) included in the message Or Field Name- Level Content / / Or} Private Identification <PrvtId> ++++ Date And Place Of Birth <DtAndPlcOfBirth> Birth Date <BirthDt> Yes Date on which a person is born Province Of Birth <PrvcOfBirth> Yes Province where a person was born City Of Birth <CityOfBirth> Yes City where a person was born Country Of Birth <CtryOfBirth> Yes Other <Othr> Country where a person was born Data Type: Country Code Format: [A- Z]{2,2} One occurrence of Other is allowed Identification <Id> yes Scheme Name <SchmeNm> No {Or Code <Cd> Yes Name of the identification Data Type: ExternalOrganisation scheme, in a coded form as Identification1Code published in an external list Format: Max length: Or} Proprietary <Prtry> Yes Name of the identification scheme, in free text form Issuer <Issr> Yes Entity that assigns the identification Creditor Account <CdtrAcct> Identification <Id> {Or IBAN <IBAN> ++++ Yes Or} Other<Othr> ++++ Yes Account of the payee/beneficiary Scheme Name Usage Rule Either Code or Proprietary to be populated for customer Identification Usage Rule Either IBAN or Other to be populated Identification <Id> Yes

14 Credit Transfer Transaction Information Definition: Set of elements used to provide information on the individual transaction(s) included in the message Or Field Name- Level Content / / Ultimate Creditor <UltmtCdtr> Name <Nm> ++++ Yes Ultimate party to which an amount of the money is due Format: Max length:70 Identification <Id> {Or Organisation Identification <OrgId> Yes Identification Usage Rule Either Organisation Identification or Private Identification to be populated Or} BICOrBEI <BICOrBEI> Yes Other <Othr> Identification <Id> Yes Private Identification <PrvtId> Date And Place Of Birth <DtAndPlcOfBirth> Code allocated to a financial institution or non financial institution by the ISO 9362 Registration Authority as described in ISO 9362 Banking Banking telecomunicatin messages-business identifier code (BIC) Identification assigned by an institution Data Type:Any BIC identifier Birth Date <BirthDt> Yes Date on which a person is born Province Of Birth <PrvcOfBirth> Yes Province where a person was born City Of Birth <CityOfBirth> Yes City where a person was born Country where a person was Data Type: Country Code Format: [A- Country Of Birth <CtryOfBirth> Yes born Z]{2,2} Other <Othr> Identification <Id> Yes 2.86 Purpose <Purp +++ Yes 2.87 {Or Code <Cd> ++++ Yes One occurrence of Other is allowed. One occurrence of Other is allowed Purpose Usage Rule Either Code or Proprietary to be populated Proprietary ++++ Yes 2.88 Or}

15 Credit Transfer Transaction Information Definition: Set of elements used to provide information on the individual transaction(s) included in the message Or Field Name- Level Content / / 2.89 RegulatoryReporting<RgltryRptg> +++ It s recomanded to be max 3 occurence DebitCreditReportingIndicator<DbtCdtRptgInd> ++++ Yes Only DEBT is allowed Authority <Authrty> Name<Nm> Yes Only BNR is allowed Country <Ctry> Yes Only RO is allowed Details<Dtls> Code<Cd> Yes Used for statistical code {Or Amount<Amt Ccy="AAA"> Yes Used for amount of each statistical code Information<Inf> Yes Remittance Information <RmtInf> +++ Unstructured <Ustrd> ++++ Yes Or} Structured <Strd> ++++ Yes ReferenceDocumentInformation<RfrdDocInf> Type<Tp> Yes Code or Proprietary <CdOrPrtry> Yes {Or Free text provided for information purposes Only one occurrence of Unstructured is allowed Provides the type details of the referred document Code<Cd> Yes Document type in a coded form Format: Max length:140 Used for additional details of the reporting/code Remittance Information Usage Rule: field, either 1 instance of Structured or 1 instance of Unstructured, may be used Recomanded to use CINV (CommercialInvoice) from MDR 2009 List. See code list in appendix Proprietary<Prtry> Yes If it's used will be ignored Or} Number<Nb> Yes Unique identification of the referred document (e.g no of Recomanded to use max lenght 31 invoice) Format: Max length:35

16 Credit Transfer Transaction Information Definition: Set of elements used to provide information on the individual transaction(s) included in the message Or Field Name- Level Content / / RelatedDate <RltdDt> Yes Date associated with the referred document Data type: ISO Date e.g invoice date; document date CreditorReferenceInformation <CdtrRefInf> Yes Reference information provided by the creditor to allow the identification of the underlying documents Format:YYYY-MM-DD Reference<Ref> Yes Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction Unique reference, as assigned by the creditor Format: Max length:35 9 Appendix 1. ISO Country Codes 2. Category Purpose Code List ISO publish lists of codes allowed within ISO XML message schemes. Please see the Inventory of External Code Lists on the ISO website 3. MDR CODES - DocumentType5Code used for structured information in code field

17 One of the following DocumentType5Code values must be used: Code Name AccountReceivableOpenIte AROI m Definition Document is a payment that applies to a specific source document. BOLD CINV CMCN CNFA CREN DEBN DISP DNFA HIRI MSIN SBIN SOAC TSUT VCHR BillOfLading CommercialInvoice CommercialContract CreditNoteRelatedToFinanc ialadjustment CreditNote DebitNote DispatchAdvice DebitNoteRelatedToFinanci aladjustment HireInvoice MeteredServiceInvoice SelfBilledInvoice StatementOfAccount TradeServicesUtilityTransac tion Voucher Document is a shipping notice. Document is an invoice. Document is an agreement between the parties, stipulating the terms and conditions of the delivery of goods or services. Document is a credit note for the final amount settled for a commercial transaction. Document is a credit note. Document is a debit note. Document is a dispatch advice. Document is a debit note for the final amount settled for a commercial transaction. Document is an invoice for the hiring of human resources or renting goods or equipment. Document is an invoice claiming payment for the supply of metered services, eg, gas or electricity, supplied to a fixed Document is an invoice issued by the debtor. Document is a statement of the transactions posted to the debtor's account at the supplier. Document is a transaction identifier as assigned by the Trade Services Utility. Document is an electronic payment document