SEPA Credit Transfer PAIN.002.001.03 Unpaid ... - Business Banking

SEPA CreditTransferUnpaid ReportFile FormatPAIN.002.001.03XML File StructureThis document is published by Bank of Ireland, and both it, and its’ contents, are the property of Bank of Ireland.This document may not be reproduced or further distributed, in whole or in part, without the express written permission of Bank of Ireland.Page 1 of 19Code

SEPA Credit Transfer Unpaid Report File Format PAIN.002.001.03 XML File Structure – Contents1. Document Overview 31.1 Background 31.2 Document Purpose 32. Fields Types 33. Tag Depth Structure 44. Characteristics of the PAIN.002.001.03 45. Reason Codes 56. File Specification 6Page 2 of 19Code

SEPA Credit Transfer Unpaid Report File Format PAIN.002.001.03 XML File Structure1. Document OverviewThis document details the PAIN.002.001.03 file format that will be accepted by Bankof Ireland for SEPA Credit Transfers and is based on the European Payments Council(EPC) Implementation guidelines.1.1 BackgroundSEPA aims to create a single, integrated and standardised payments market acrossthe current 32 SEPA countries in Europe.Credit Transfer originators must be SEPA compliant by 1st February 2014 in order tocontinue making electronic non-urgent euro payments (SEPA payments) in Ireland. Furtherbackground information is available on our website: http://bankofireland.com/SEPABank of Ireland has also published a Credit Transfer Readiness Checklist on theBank of Ireland website. To ensure you are aware of the changes required within yourbusiness please visit: http://bankofireland.com/SEPA2. Field TypesThe following section details the type of fields that are contained in the specificationdocument.Always Present – Fields that will always be present on the PAIN.002.001.03Optional Fields – This field will be populated if the corresponding optional fieldon the PAIN.001.001.03 was populatedConditional Fields – This field will be populated based on the criteria set out inthe usage rules 51.2 Document PurposeThe purpose of this document is to outline the PAIN.002.001.03 XML file format.Knowledge of XML is recommended to interpret this document.Page 3 of 19Code

SEPA Credit Transfer Unpaid Report File Format PAIN.002.001.03 XML File Structure3. 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 document.For example:‘+’ would represent a Parent Element‘++’ would represent the Child Element of the previous Parent ElementTAG DEPTH+ ++ TAG STRUCTURE+++ 4. Characteristics of the PAIN.002.001.031. The PAIN.002.001.03 report will be available in XML and reader friendly HTMLformat.2. The report will be available on Bank of Ireland’s dedicated SEPA online channel,Business On Line Payments Plus. Bank of Ireland will communicate details of thischannel and log on details to you.3. The PAIN.002.001.03 file is generated per PAIN.001.001.03 file, per day. It detailsany r-messages that have been created against the PAIN.001.001.03 file and willcontain the reason code for the rejection.4. A PAIN.002.001.03 file will only be available if an r-message has been created forthe associated PAIN.001.001.03 on a given day.5. The r-messages contained in a PAIN.002.001.03 can be matched to the originaltransactions using the end to end ID.6. PAIN.002.001.03 generated by Bank of Ireland will detail r-messages attransaction level. Bank of Ireland will not generate PAIN.002.001.03 messages forfailures at file (Group Header) or batch (Payment Information) level. File failures willbe reported as a specific message on the online channel.Page 4 of 19Code

SEPA Credit Transfer Unpaid Report File Format PAIN.002.001.03 XML File Structure5. Reason CodesOriginators may receive the following reasons codes as part of the PAIN.002.001.03message to detail the reason for the rejection. This code will be populated in the codetag, field index 3.23, as outlined in the Transaction Information block in the file formatsection of this document.Return codesThe following table lists the reason codes that could occur for a return message from adebtor bank:ISO CodeAC01AC04AC06AG01AG02AM05BE04FCORFF01MD07MS02MS03RC01RR01RR02RR03RR04TM01SEPA Reason as specified in the RulebookAccount identifier incorrect (i.e. invalid IBAN)Account ClosedAccount BlockedCredit transfer forbidden on this type of account (e.g. savings account)Invalid Bank Operation CodeDuplicate collectionAccount address invalidPositive Response to RecallInvalid File FormatBeneficiary DeceasedBy order of the beneficiaryReason not specifiedBank identifier incorrect (i.e. invalid BIC)Missing Debtor Account Or IdentificationMissing Debtors Name Or AddressMissing Creditors Name Or AddressRegulatory ReasonFile received after cut-off timePage 5 of 19Code

SEPA Credit Transfer Unpaid Report File Format PAIN.002.001.03 XML File Structure6. File SpecificationField Name – Tag(No. references EPC Implementation Guide)Tag Level Content Mandatory/Optional/ConditionalPopulatedBy/FromDescription/ValueDataAlwaysPresentMandatory for all PAIN.002 XML filesAlwaysPresentMandatory for all PAIN.002 XML filesGroup HeaderField Name – Tag(No. references EPC Implementation Guide)Tag Level Content Mandatory/Optional/ConditionalPopulatedBy/FromDescription/Value1.0 Group Header + Empty Tag Always Present1.1 MessageIdentification ++ Yes Always Present BOI Unique message identification of thepain.002 that is supplied1.2 CreationDateTime ++ Yes Always Present BOI Date and time at which the messagewas created1.5 DebtorAgent ++ Empty Tag Always Present1.6 FinancialInstitutionIdentification +++ Empty Tag Always Present1.6 BIC ++++ Yes Always Present Field 2.21 onPAIN.001BIC code of the Creditor BankField 2.21 on PAIN.001DataData Type: TextFormat: Max length: 35Min length: 1Data Type: ISODateTimeFormat: YYYY-MM-DDTHH:MM:SSe.g. 2012-02-06T08:35:30Data Type: BICIdentifierFormat: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}Always PresentOptional FieldsConditional FieldsPage 6 of 19Code

Original Group Information and StatusField Name – Tag(No. references EPC Implementation Guide)Tag Level Content Mandatory/Optional/ConditionalPopulatedBy/FromDescription/ValueOriginal Group Information and Status will always be present and details original file level details from the submitted PAIN.001 as well as the r-message reason codes2.0 Original Group Information And Status + Empty Tag Always Present2.1 Original Message Identification ++ Yes Always Present Field 1.1 onPAIN.0012.2 Original Message Name Identification ++ Yes Always Present Taken fromfile type thatr-message isassociatedwithPoint to point reference, as assignedby the original instructing partySpecifies the original message nameidentifier to which the message refers.e.g. PAIN.001.001.03DataData Type: TextFormat: Max length: 35Min length: 1Data Type: TextFormat: Max length: 35Min length: 1Always PresentOptional FieldsConditional FieldsPage 7 of 19Code

Original Payment Information and StatusField Name – Tag(No. references EPC Implementation Guide)Tag Level Content Mandatory/Optional/ConditionalPopulatedBy/From3.0 Original Payment Information And Status + Empty Tag Always Present3.1 Original Payment Information Identification ++ Yes Always Present Field 2.1 onPAIN.001Description/ValueUnique identification, as assignedby the original sending party, tounambiguously identify the originalpayment information groupDataData Type: TextFormat: Max length: 35Min length: 1Original Payment Information and Status will be present where a batch has failed and details original batch level details from the submitted PAIN.001 as well as the r-message reason codesNote: Where ‘Payment Information Status’ is present Transaction Information and Status will be omitted3.4 Payment Information Status ++ Yes See PaymentStatus UsageRuleCreditor Bank/CSM3.5 Status Reason Information ++ Yes See PaymentStatus UsageRuleOriginator Usage Rule: Limited to BIC to identify the bank or CSM originating the status or ‘Name’ to indicate a CSM when it has no BIC3.21 Originator +++ Empty Tag See OriginatorUsage Rule3.21 Name ++++ Yes See OriginatorUsage Rule3.21 Identification ++++ Empty Tag See OriginatorUsage Rule3.21 Organisation Identification +++++ Empty Tag See OriginatorUsage Rule3.21 BICOrBEI ++++++ Yes See OriginatorUsage Rule3.22 Reason +++ Empty Tag See OriginatorUsage Rule3.23 Code +++ Yes See OriginatorUsage RuleCSMCreditor Bank/CSM/BOICreditor Bank/CSM/BOIUsage Rule: Either ‘Group Status’,‘Payment Information Status’ or‘Transaction Status’ must be presentwith the code ‘RJCT’.‘Name’ to indicate a CSMwhen it has no BIC.BIC to identify the bank or CSMoriginating the statusSee reason codesRJCTData Type: TextFormat: Max length: 70Min length: 1Data Type: AnyBICIdentifierFormat: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}See section 9.0 for reason codesAlways PresentOptional FieldsConditional FieldsPage 8 of 19Code

Transaction InformationField Name – Tag(No. references EPC Implementation Guide)Tag Level Content Mandatory/Optional/ConditionalPopulatedBy/FromDescription/ValueTransaction Information will be present where a transaction has failed and details original transaction level details from the submitted PAIN.001 as well as the r-message reason codesNote: Transaction Information and Status will not be present when Payment Information Status is present and populated3.15 Transaction Information And Status ++ Empty Tag AlwaysPresent3.16 Status Identification +++ Yes AlwaysPresent3.17 Original Instruction Identification +++ Yes Present ifpopulated onPAIN.001Creditor BankField 2.30from thePAIN.0013.18 Original End To End Identification +++ Yes Always Present Field 2.31from thePAIN.001Transaction Status Usage Rule: Either ‘Payment Information Status’ or ‘Transaction Status’ must be present with the code ‘RJCT’3.19 Transaction Status +++ Yes SeeTransactionStatus UsageRule3.20 Status Reason Information +++ Empty Tag SeeTransactionStatus UsageRuleCreditor Bank/CSMSpecific reference of the bank thatinitiated the rejectUnique identification, as assigned bythe original instructing party for theoriginal instructed party, toOriginators reference of the CreditTransfer TransactionUsage Rule: Either ‘Group Status’,‘Payment Information Status’ or‘Transaction Status’ must be presentwith the code ‘RJCT’.Originator Usage Rule: Limited to BIC to identify the bank or CSM originating the status or ‘Name’ to indicate a CSM when it has no BIC3.21 Originator ++++ Empty Tag See OriginatorUsage Rule3.21 Name +++++ Yes See OriginatorUsage RuleCSM ‘Name’ to indicate a CSM when ithas no BIC.3.21 Identification +++++ Empty Tag See OriginatorUsage RuleDataData Type: TextFormat: Max length: 35Min length: 1Data Type: TextFormat: Max length: 35Min length: 1Data Type: TextFormat: Max length: 35Min length: 1RJCTData Type: TextFormat: Max length: 70Min length: 1Always PresentOptional FieldsConditional FieldsPage 9 of 19Code

Transaction InformationField Name – Tag(No. references EPC Implementation Guide)Tag Level Content Mandatory/Optional/Conditional3.21 Organisation Identification ++++++ Empty Tag See OriginatorUsage Rule3.21 BIC Or BEI +++++++ Yes See OriginatorUsage RulePopulatedBy/FromCreditor Bank/CSM/BOIDescription/ValueBIC to identify the bank or CSMoriginating the statusDataData Type: AnyBICIdentifierFormat: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}3.22 Reason ++++ Empty Tag See OriginatorUsage Rule3.23 Code ++++ Yes See OriginatorUsage RuleOriginal Transaction Reference Usage Rule: Usage Rule: The message elements under ‘Original Transaction Reference’ must be populated with the same value as the message elements of the originalinstruction, as defined within the following elements.3.32 Original Transaction Reference +++ Empty Tag Always Present3.34 Amount ++++ Empty Tag Always Present3.35 Instructed Amount +++++ Yes Always Present Field 2.43 onPAIN.0013.41 Requested Execution Date ++++ Yes Always Present Field 2.17 onPAIN.0013.55 Payment Type Information ++++ Empty Tag Always Present3.57 Instruction Priority ++++ Yes Present if onPAIN.0013.58 Service Level +++++ Empty Tag Always PresentAmount of the Credit Transfer in EuroThe date the Originator requests theCredit Transfer to take place.AT-06 Amount of the Collection inEuro)Usage Rule: Only ‘EUR’ is allowed.Usage Rule: Amount must be 0.01or more and 999999999.99 or less.Format Rule: The fractional parthas a maximum of two digits e.g.109400AT-07 Requested execution date ofthe instructionData Type: ISODateFormat: YYYY-MM-DDAlways PresentOptional FieldsConditional FieldsPage 10 of 19Code

Transaction InformationField Name – Tag(No. references EPC Implementation Guide)Tag Level Content Mandatory/Optional/ConditionalPopulatedBy/From3.59 Code ++++++ Yes Always Present Field 2.9 onPAIN.0013.61 Local Instrument +++++ Empty Tag Always Present3.62 Code ++++++ Yes Present if onPAIN.0013.63 Proprietary ++++++ Yes Present if onPAIN.0013.65 Category Purpose +++++ Empty Tag Present if onPAIN.0013.66 Code ++++++ Yes Present if onPAIN.0013.67 Proprietary ++++++ Yes Present if onPAIN.0013.68 Payment Method ++++ Empty Tag Optional3.88 Remittance Information ++++ Empty Tag Mandatory ifon PAIN.0013.89 Unstructured +++++ Yes Mandatory ifon PAIN.0013.120 Ultimate Debtor ++++ Empty Tag Present if onPAIN.0013.120 Name +++++ Yes Present if onPAIN.001Field 2.12 onPAIN.001Field 2.13 onPAIN.001Field 2.15 onPAIN.001Field 2.16 onPAIN.001Field 2.98 onPAIN.001Field 2.23 onPAIN.001Description/ValueDataMust contain ‘SEPA’??? Data Type: TextFormat: Max length: 35Min Length: 1Data Type: TextFormat: Max length: 35Min Length: 1Category purpose in code form Format: Max length: 4Min length: 1see code list on page11Category purpose, in a proprietaryform.Free text provided for matchingreconciliationUltimate debtor nameData Type: TextFormat: Max length: 35Min Length: 1Data Type: TextFormat: Max length: 140Min Length: 1Data Type: TextFormat: Max length: 70Min Length: 1Always PresentOptional FieldsConditional FieldsPage 11 of 19Code

Transaction InformationField Name – Tag(No. references EPC Implementation Guide)Tag Level Content Mandatory/Optional/Conditional3.120 Identification +++++ Empty Tag Present if onPAIN.0013.120Organisation Identification ++++++ Empty Tag Present if onPAIN.0013.120BICOrBEI +++++++ Yes Present if onPAIN.0013.120 Other +++++++ Empty Tag Present if onPAIN.0013.120 Identification ++++++++3.120Scheme Name ++++++++3.120 Code +++++++++3.120Proprietary +++++++++3.120 Issuer ++++++++YesNoYesYesYesPresent if onPAIN.001Present if onPAIN.001Present if onPAIN.001Present if onPAIN.001Present if onPAIN.0013.120 Private Identification ++++++ Empty Tag Present if onPAIN.0013.120 Date And Place Of Birth +++++++ Empty Tag Present if onPAIN.001PopulatedBy/FromField 2.23 onPAIN.001Field 2.23 onPAIN.001Field 2.23 onPAIN.001Field 2.23 onPAIN.001Field 2.23 onPAIN.001Description/ValueBIC IdentifierIdentification assigned by aninstitutionName of the identification scheme,in a coded form as published in anexternal listName of the identification scheme, ina free text formEntity that assigns the identificationDataData Type: AnyBICIdentifierFormat: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}Data Type: TextFormat: Max length: 35Min Length: 1Data Type: ExternalOrganisationIdentification1CodeFormat: Max Length: 4Min length: 1Data Type: TextFormat: Max length: 35Min Length: 1Data Type: TextFormat: Max length: 35Min Length: 1Always PresentOptional FieldsConditional FieldsPage 12 of 19Code

Transaction InformationField Name – Tag(No. references EPC Implementation Guide)3.120 Birth Date ++++++++3.120 Province Of Birth ++++++++3.120 City Of Birth ++++++++3.120 Country Of Birth ++++++++Tag Level Content Mandatory/Optional/ConditionalYesYesYesYesPresent if onPAIN.001Present if onPAIN.001Present if onPAIN.001Present if onPAIN.0013.120 Other +++++++ Empty Tag Present if onPAIN.0013.120 Identification ++++++++3.120 Scheme Name ++++++++3.120 Code +++++++++3.120 Proprietary +++++++++3.120 Issuer ++++++++YesEmpty TagYesYesYesPresent if onPAIN.001Present if onPAIN.001Present if onPAIN.001Present if onPAIN.001Present if onPAIN.001PopulatedBy/FromField 2.23 onPAIN.001Field 2.23 onPAIN.001Field 2.23 onPAIN.001Field 2.23 onPAIN.001Field 2.23 onPAIN.001Field 2.23 onPAIN.001Field 2.23 onPAIN.001Field 2.23 onPAIN.001Description/ValueDate on which a person is bornProvince where a person was bornCity where a person was bornCountry where a person was bornIdentification assigned by aninstitutionName of the identification scheme,in a coded form as published in anexternal listName of the identification scheme, ina free text formEntity that assigns the identificationDataData Type: ISODateFormat: YYYY-MM-DDe.g. 1998-03-30Data Type: TextFormat: Max length: 35Min Length: 1Data Type: TextFormat: Max length: 35Min Length: 1Data Type: CountryCodeFormat: [A-Z]{2,2}Data Type: TextFormat: Max length: 35Min Length: 1Data Type: ExternalOrganisationIdentification1CodeFormat: Max length: 4Min length: 1Data Type: TextFormat: Max length: 35Min Length: 1Data Type: TextFormat: Max length: 35Min Length: 1Always PresentOptional FieldsConditional FieldsPage 13 of 19Code

Transaction InformationField Name – Tag(No. references EPC Implementation Guide)Tag Level Content Mandatory/Optional/Conditional3.121 Debtor ++++ Empty Tag AlwaysPresent3.121 Name +++++ Yes AlwaysPresent3.121 Postal Address +++++ Empty Tag Present if onPAIN.0013.121 Country ++++++ Yes Present if onPAIN.0013.121 Address Line (2) ++++++ Yes Present if onPAIN.0013.121 Identification +++++ Empty Tag Present if onPAIN.0013.121 Organisation Identification ++++++ Empty Tag Present if onPAIN.0013.121 BICOrBEI +++++++ Yes Present if onPAIN.0013.121 Other +++++++ Empty Tag Present if onPAIN.0013.121 Identification ++++++++3.121 Scheme Name ++++++++YesNoPresent if onPAIN.001Present if onPAIN.001PopulatedBy/FromField 2.19 onPAIN.001Field 2.19 onPAIN.001Field 2.19 onPAIN.001Field 2.19 onPAIN.001Field 2.19 onPAIN.001Description/ValueDebtor nameCountry codeDebtor address in freeformat text.Note: Two occurrences of this tagare allowedBIC IdentifierIdentification assigned by aninstitutionDataData Type: TextFormat: Max length: 70Min Length: 1Data Type: CountryCodeFormat: [A-Z]{2,2}SO 3166, Alpha-2codeData Type: TextFormat: Max length: 70Min Length: 1Data Type: AnyBICIdentifierFormat: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}Data Type: TextFormat: Max length: 35Min Length: 1Always PresentOptional FieldsConditional FieldsPage 14 of 19Code

Transaction InformationField Name – Tag(No. references EPC Implementation Guide)3.121 Code +++++++++3.121 Proprietary +++++++++3.121 Issuer ++++++++Tag Level Content Mandatory/Optional/ConditionalYesYesYesPresent if onPAIN.001Present if onPAIN.001Present if onPAIN.0013.121 Private Identification ++++++ Empty Tag Present if onPAIN.0013.121 Date And Place Of Birth +++++++ Empty Tag Present if onPAIN.0013.121 Birth Date ++++++++3.121 Province Of Birth ++++++++3.121 City Of Birth ++++++++3.121 Country Of Birth ++++++++YesYesYesYesPresent if onPAIN.001Present if onPAIN.001Present if onPAIN.001Present if onPAIN.0013.121 Other +++++++ Empty Tag Present if onPAIN.0013.121 Identification ++++++++YesPresent if onPAIN.001PopulatedBy/FromField 2.19 onPAIN.001Field 2.19 onPAIN.001Field 2.19 onPAIN.001Field 2.19 onPAIN.001Field 2.19 onPAIN.001Field 2.19 onPAIN.001Field 2.19 onPAIN.001Field 2.19 onPAIN.001Description/ValueName of the identification scheme,in a coded form as published in anexternal listName of the identification scheme, ina free text formEntity that assigns the identificationDate on which a person is bornProvince where a person was bornCity where a person was bornCountry where a person was bornIdentification assigned by aninstitutionDataData Type: ExternalOrganisationIdentification1CodeFormat: Max Length: 4Min length: 1Data Type: TextFormat: Max length: 35Min Length: 1Data Type: TextFormat: Max length: 35Min Length: 1Data Type: ISODateFormat: YYYY-MM-DDe.g. 1998-03-30Data Type: TextFormat: Max length: 35Min Length: 1Data Type: TextFormat: Max length: 35Min Length: 1Data Type: CountryCodeFormat: [A-Z]{2,2}Data Type: TextFormat: Max length: 35Min Length: 1Always PresentOptional FieldsConditional FieldsPage 15 of 19Code

Transaction InformationField Name – Tag(No. references EPC Implementation Guide)3.121 Scheme Name ++++++++3.121 Code +++++++++3.121 Proprietary +++++++++3.121 Issuer ++++++++Tag Level Content Mandatory/Optional/ConditionalEmpty TagYesYesYesPresent if onPAIN.001Present if onPAIN.001Present if onPAIN.001Present if onPAIN.0013.122 Debtor Account ++++ Empty Tag AlwaysPresent3.122 Identification +++++ Empty Tag AlwaysPresent3.122 IBAN ++++++ Yes AlwaysPresent3.123 Debtor Agent ++++ Empty Tag AlwaysPresent3.123 Financial Institution Identification +++++ Empty Tag AlwaysPresent3.123 BIC ++++++ Yes AlwaysPresent3.125 Creditor Agent ++++ Empty Tag AlwaysPresent3.125 Financial Institution Identification +++++ Empty Tag AlwaysPresentPopulatedBy/FromField 2.19 onPAIN.001Field 2.19 onPAIN.001Field 2.19 onPAIN.001Field 2.20 onPAIN.001Field 2.21 onPAIN.001Description/ValueName of the identification scheme,in a coded form as published in anexternal listName of the identification scheme, ina free text formEntity that assigns the identificationInternational Bank Account Number(IBAN)Bank Identifier Code.DataData Type: ExternalOrganisationIdentification1CodeFormat: Max length: 4Min length: 1Data Type: TextFormat: Max length: 35Min Length: 1Data Type: TextFormat: Max length: 35Min Length: 1Data Type: IBAN2007IdentifierFormat: [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}Data Type: BICIdentifierFormat: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}Always PresentOptional FieldsConditional FieldsPage 16 of 19Code

Transaction InformationField Name – Tag(No. references EPC Implementation Guide)Tag Level Content Mandatory/Optional/Conditional3.125 BIC ++++++ Yes AlwaysPresent3.127 Creditor ++++ Empty Tag AlwaysPresent3.127 Name +++++ Yes AlwaysPresent3.127 Postal Address +++++ Empty Tag Present if onPAIN.0013.127 Country ++++++ Yes Present if onPAIN.0013.127 Address Line (2) ++++++ Yes Present if onPAIN.0013.128 Creditor Account ++++ Empty Tag AlwaysPresent3.128 Identification +++++ Empty Tag AlwaysPresent3.128 IBAN ++++++ Yes AlwaysPresent3.128 Currency ++++ Yes If populated onPAIN.0013.129 Ultimate Creditor ++++ Empty Tag Present if onPAIN.001PopulatedBy/FromField 2.77 onPAIN.001Field 2.79 onPAIN.001Field 2.79 onPAIN.001Field 2.79 onPAIN.001Field 2.80 onPAIN.001Field 2.80 onPAIN.001Description/ValueBank Identifier CodeName by which a party is known andwhich is usually used to identify thatparty.Country CodePostal address in freeformat text.Note: Two occurrences of this tagare allowedInternational Bank Account Number(IBAN)Identification of the currency in whichthe account is held.Note: No processing or validationis completed on this field – forinformation purpose onlyDataData Type: BICIdentifierFormat: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}Data Type: TextFormat: Max length: 70Min Length: 1Format: [A-Z]{2,2}ISO 3166, Alpha-2codeData Type: TextFormat: Max length: 70Min Length: 1Data Type: IBAN2007IdentifierFormat: [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}Currency CodeFormat: [A-Z]{3,3}Valid active or historic currencycodes are registered with the ISO4217Always PresentOptional FieldsConditional FieldsPage 17 of 19Code

Transaction InformationField Name – Tag(No. references EPC Implementation Guide)Tag Level Content Mandatory/Optional/Conditional3.129 Name +++++ Yes Present if onPAIN.0013.129 Identification +++++ Empty Tag Present if onPAIN.0013.129 Organisation Identification ++++++ Empty Tag Present if onPAIN.0013.129 BICOrBEI +++++++ Yes Present if onPAIN.0013.129 Other +++++++ Empty Tag Present if onPAIN.0013.129 Identification ++++++++3.129 Scheme Name ++++++++3.129 Code +++++++++3.129 Proprietary +++++++++3.129 Issuer ++++++++YesEmpty TagYesYesYesPresent if onPAIN.001Present if onPAIN.001Present if onPAIN.001Present if onPAIN.001Present if onPAIN.0013.129 Private Identification ++++++ Empty Tag Present if onPAIN.0013.129 Date And Place Of Birth +++++++ Empty Tag Present if onPAIN.001PopulatedBy/FromField 2.81 onPAIN.001Field 2.81 onPAIN.001Field 2.81 onPAIN.001Field 2.81 onPAIN.001Field 2.81 onPAIN.001Field 2.81 onPAIN.001Description/ValueUltimate party to which an amount ofmoney is dueBIC IdentifierName of the identification scheme,in a coded form as published in anexternal listName of the identification scheme, ina free text formEntity that assigns the identificationDataData Type: TextFormat: Max length: 70Min Length: 1Data Type: AnyBICIdentifierFormat: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}Data Type: ExternalOrganisationIdentification1CodeFormat: Max Length: 4Min length: 1Data Type: TextFormat: Max length: 35Min Length: 1Data Type: TextFormat: Max length: 35Min Length: 1Always PresentOptional FieldsConditional FieldsPage 18 of 19Code

Transaction InformationField Name – Tag(No. references EPC Implementation Guide)3.129 Birth Date ++++++++3.129 Province Of Birth ++++++++3.129 City Of Birth ++++++++3.129 Country Of Birth ++++++++Tag Level Content Mandatory/Optional/ConditionalYesYesYesYesPresent if onPAIN.001Present if onPAIN.001Present if onPAIN.001Present if onPAIN.0013.129 Other +++++++ Empty Tag Present if onPAIN.0013.129 Identification ++++++++3.129 Scheme Name ++++++++3.129 Code +++++++++3.129 Proprietary +++++++++3.129 Issuer ++++++++YesEmpty TagYesYesYesPresent if onPAIN.001Present if onPAIN.001Present if onPAIN.001Present if onPAIN.001Present if onPAIN.001PopulatedBy/FromField 2.81 onPAIN.001Field 2.81 onPAIN.001Field 2.81 onPAIN.001Field 2.81 onPAIN.001Field 2.81 onPAIN.001Field 2.81 onPAIN.001Field 2.81 onPAIN.001Field 2.81 onPAIN.001Description/ValueDate on which a person is bornProvince where a person was bornCity where a person was bornCountry where a person was bornIdentification assigned by aninstitutionName of the identification scheme,in a coded form as published in anexternal listName of the identification scheme, ina free text formEntity that assigns the identificationDataData Type: ISODateFormat: YYYY-MM-DDe.g. 1998-03-30Data Type: TextFormat: Max length: 35Min Length: 1Data Type: TextFormat: Max length: 35Min Length: 1Data Type: CountryCodeFormat: [A-Z]{2,2}Data Type: TextFormat: Max length: 35Min Length: 1Data Type: ExternalOrganisationIdentification1CodeFormat: Max Length: 4Min length: 1Data Type: TextFormat: Max length: 35Min Length: 1Data Type: TextFormat: Max length: 35Min Length: 1Always PresentOptional FieldsConditional FieldsDisclaimer: This document is for information purposes only and no guarantee or warranty is given in respect of the accuracy or completeness of this document,or its’ content, which are subject to change. Bank of Ireland accepts no liability for any losses howsoever arising in reliance on this document or its content.Page 19 of 19Code