Credit Transfer PAIN.001.001 - Bank of Ireland

1 Page 1 of xml file Structure Version Usage Rules Mandatory Fields Optional Fields Payment Information (Batch) /Transaction LevelCredit Transfer xml file Structure V document is published by Bank of Ireland , and both it, and its contents, are the property of Bank of document may not be reproduced or further distributed, in whole or in part, without the express written permission of Bank of 2 of xml file Structure Version Transfer xml file Structure Document Overview 3 Background 3 Document Purpose 32.

2 The Character Set 43. field Types 54. Usage Rules 55. Unused Optional Tags 56. Tag Depth Structure 67. File Name 68. File Format Table 79. Section 9: Sample File 2710. Appendix 3111. Change Control 32 Page 3 of xml file Structure Version Transfer xml file Document OverviewThis document details the ISO 20022 xml file format that will be accepted by Bank of Ireland for SEPA Credit Transfers. This document was compiled with information from: ISPO Customer File Formats V10 Failure to provide files that meet this specification may results in files and/or transactions being rejected, either by Bank of Ireland or by the beneficiary BackgroundSEPA aims to create a single, integrated and standardised payments market across the current SEPA countries in of Ireland has also published a Credit Transfer Readiness Checklist on the Bank of Ireland website.

3 To ensure you are aware of the changes required within your business please visit: Document PurposeThe purpose of this document is to outline the xml file format that will be accepted by Bank of of XML is recommended to interpret this The Character SetThe 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 zA 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 0 1 2 3 4 5 6 7 8 9/ ? : ( ) . , +SpaceIf required, the following characters can also be used in text or information fields only, but must be provided using the XML representation XML CharacterXML Representation& (ampersand)& ~~Z< (left brace)<> (right brace)> (double quotation)" AB & C Transport would populate their name in a , appearing as:<Cdtr> <Nm>AB & C TRANSPORT </Nm> </Cdtr> Note: Senders must ensure that the content of Identifiers/reference data elements is restricted to the restricted basic Latin character set (across).

4 If non supported characters are used in these fields they may lead to rejection of files or transactions in the payment , 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:Mandatory Fields End-to-End Identification Message Identification Payment Information IdentificationOptional Fields Instruction Identification Creditor and Debtor Identification Ultimate Debtor/Creditor Identification Remittance Information Proprietary CodesAdditionally, the content of Message Identification - Must not contain an 4 of xml file Structure Version Transfer xml file StructurePage 5 of xml file Structure Version Transfer xml file Structure3.

5 field TypesThe following section details the type of fields that are contained in the specification document. Mandatory Fields Fields must be populated or the file/batch will be rejected Optional Fields Originator to decide if this field needs to be populated Payment Information (Batch)/Transaction Level There are a numberof optional fields that may be populated at payment information level or attransaction level, however it is recommended They are populated at payment information level if being following fields are optional to populate and may be populated at payment information or transaction level Payment Type Information Charge Bearer4.

6 Usage RulesFor 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/ Rules can be found in the Grey Unused Optional TagsWhere optional tags have not been populated, the tag should be omitted from the file along with its parent 6 of xml file Structure Version Transfer xml file Structure6. Tag Depth StructureIn the TAG DEPTH column within the file format table below, each of the field name tags are represented by a + .These + icons represent the depth of the field name tag within the example: + would represent a Parent Element ++ would represent the Child Element of the previous Parent ElementTag DepthTag Structure+<>++<> <>+++<> <> <>7.

7 File NameThe 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 The file extension must be .xml 3. Filename must not exceed 50 Only alphanumeric characters and the underscore _ character can be used in the filename (preceding the file extension .xml ).5. Must not contain spaces Example: 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 7 of xml file Structure Version Usage Rules Mandatory Fields Optional Fields Payment Information (Batch) /Transaction LevelCredit Transfer xml file Structure8.

8 File Format TableField Name Tag(No. references EPC Implementation Guide)Tag LevelContentMandatory / OptionalDescription/ValueData<?xml version= encoding= UTF-8 ?> <Document xmlns= urn:iso:std:iso:20022:tech: xmlns:xsi= >MandatoryThis tag must always be placed before the group header tag<?xml version= encoding= UTF-8 ?> <Document xmlns= urn:iso:std:iso: 20022:tech: xmlns:xsi= 2001/XMLS chema-instance > <CstmrCdtTrfInitn>MandatoryThis tag must always be placed before the group header tag<CstmrCdtTrfInitn> - XML tag for messageGroup Header BlockField Name Tag(No. references EPC Implementation Guide)Tag LevelContentMandatory / Group Header <GrpHdr>+Empty MessageIdentification <MsgId>++Ye sMandatoryOriginator s unique identifier of the submitted : This ID cannot be reused on future filesData Type: TextFormat: Max length: 35 Min length: CreationDateTime <CreDtTm>++Ye sMandatoryDate and time at which the message was createdData Type: ISODateTimeFormat: YYYY-MM-DDTHH: 2012-02-06T08:35 Number Of Transactions <NbOfTxs>++Ye sMandatoryNumber of individual transactions contained in the fileData Type: Max15 NumericTextFormat.

9 [0-9] {1,15} Control Sum <CtrlSum>++Ye sMandatoryTotal of all individual amounts included in the fileData Type: Decimal NumberFormat: Fraction Digits: 2 Total Digits: 18 Page 8 of xml file Structure Version Usage Rules Mandatory Fields Optional Fields Payment Information (Batch) /Transaction LevelCredit Transfer xml file StructureGroup Header Block this can only occur once per fileField Name Tag(No. references EPC Implementation Guide)Tag LevelContentMandatory / OptionalDescriptionDataInitiating Party Usage Rule: For Group Header BOI originators must populate either Private ID or Organisation Initiating Party <InitgPty>++Empty Identification <Id>+++Empty Organisation Identification <OrgId>++++Empty TagOptionalsee usage rule Other <Othr>+++++Empty Identification <Id>++++++Ye sMandatoryPopulate with OIN NumberData Type: TextFormat: Max length: 35 Min length: 1 Scheme Name Usage Rule.

10 Scheme Name is optional, if used either Code or Proprietary must be Scheme Name <SchmeNm>++++++Empty Code <Cd>+++++++Ye sOptionalsee usage rule aboveData Type: TextFormat: Max length: Proprietary <Prtry>+++++++Ye sOptionalsee usage rule aboveData Type: TextFormat: Max length: Issuer <Issr>++++++Yes OptionalData Type: TextFormat: Max length: 35 Min length: Private Identification <PrvtId>++++Empty TagOptionalsee usage rule Other <Othr>+++++Empty Identification <Id>++++++MandatoryMandatoryPopulate with OIN NumberData Type: TextFormat: Max length: 35 Min length: 1 Page 9 of xml file Structure Version Usage Rules Mandatory Fields Optional Fields Payment Information (Batch) /Transaction LevelCredit Transfer xml file StructureScheme Name Usage Rule: Scheme Name is optional, if used either Code or Proprietary must be Scheme Name <SchmeNm>++++++ Code <Cd>+++++++Optionalsee usage rule aboveData Type: TextFormat: Max length: Proprietary <Prtry>+++++++Optionalsee usage rule aboveData Type: TextFormat: Max length: Issuer <Issr>++++++OptionalFormat: Max length: 35 Min length.