4 0.3 Purpose of Document The objective of these Guidelines is to define the rules to be applied to the ISO XML message standards for the implementation of the SEPA Credit Transfers in the customer-tobank space. SEPA Credit Transfer C2B Implementation Guidelines Version 6.0 Approved Page 3 November 2011

5 1 INTRODUCTION This document sets out the SEPA rules for implementing the credit transfer ISO XML initiation message standards. The SEPA Credit Transfer Scheme Rulebook defines data sets which are implemented in the relevant ISO XML message standard of which the following are covered: SEPA Credit Transfer Scheme Rulebook DS-01 Customer to Bank Credit Transfer Instruction Information DS-04 Bank to Customer Credit Transfer Information Reject based on DS-03 for the Bank to Customer reject ISO XML Message Standards Customer Credit Transfer Initiation (pain ) Statements/advice ISO XML standards are covered separately. Reject Customer Payment Status Report (pain ) The use of customer-to-bank and bank-to-customer XML message standards is recommended as are these Guidelines. 1.1 Coverage of the SEPA customer-to- bank Implementation Guidelines The purpose of the SEPA customer-to- bank Implementation Guidelines, hereafter referred to as the Guidelines, is to provide guidance on the use of the payment initiation ISO XML standards (the pain messages) in initiating SEPA core payments as defined in the SEPA scheme rulebooks and supplemented by processing requirements. The implementation of the messages and the compliance with these guidelines are strongly recommended. The Guidelines are fully aligned to the SEPA core requirements when defined in the Rulebook and identify message elements needed for initiating SEPA payments while recognising message elements that may be available for use in Additional Optional Services (AOS), as shown below. SEPA Credit Transfer C2B Implementation Guidelines Version 6.0 Approved Page 4 November 2011

6 Global ISO XML Message Standards Message elements from the ISO messages corresponding to Rulebook requirements Message elements that are mandatory in the ISO messages or needed for Processing Message elements from the ISO messages available for use by AOS within an EPC Governance framework Message elements from ISO messages not applicable to SEPA EPC Implementation Guidelines for SEPA Core subset, identifying elements - to be used as defined in ISO - to be used with SEPA usage rules (from or completing the Rulebook) SEPA Payments To be developed and documented by AOS Communities Not available for use in SEPA payments Figure 1 These Guidelines define the SEPA Core Mandatory Subset 2 of the Global ISO XML standard that consists of message elements: required in the Rulebook as business requirements needed for processing by banks, clearing and settlement mechanisms and bank customers Elements needed for specific national regulatory requirements are not considered in these guidelines. They have to be dealt with at national level without being regarded as an AOS. These message elements define the SEPA core service and are denoted by yellow shading in the message structures given in the following chapters. Only these elements are further detailed with relevant SEPA core requirements, such as the use of the message element, its components or the values that must be used. Usage rules, for example, may indicate limits on the number of repetitions, or code value restrictions, while format rules may be used to indicate the allowable combinations of components of a message element. These Guidelines also recognise message elements and the usage rules in the ISO XML standard that may be available for use in an AOS, subject to a governance framework to be defined by the EPC. The definition and documentation of these message elements are a matter for the AOS communities involved. These message elements are denoted by white shading. Where there are message elements that do not apply to SEPA payments, these are denoted with red shading in the right-most column of the message structures. To date, few such message elements have been identified. 2 The SEPA Core Mandatory Subset is hereafter known as the SEPA core service. SEPA Credit Transfer C2B Implementation Guidelines Version 6.0 Approved Page 5 November 2011

7 1.2 Use of these Guidelines by the instructing and instructed parties 3 SEPA core payments are executed using messages only containing message elements defined as part of the SEPA Core Subset (shaded yellow in Figure 2). Payments that include message elements that are defined and documented by AOS communities (shaded white in Figure 2) are considered as SEPA payments, but not as SEPA core payments. It is the responsibility of the instructing customer and instructed bank of the message to ensure that message elements defined for use in an AOS are only included in messages sent to AOS community members. The instructed bank receiving a message containing AOS message elements, but which is not a member of this AOS community, may ignore the information, that is, not use it for processing, nor forward it to the next party in the chain. The instructed bank, however, may reject the message for this reason. 1.3 Notation Conventions The Guidelines are presented in the format of the ISO XML standard. Index Mult Message Element SEPA Core Requirements 1 [1..1] + Transaction Information 2 [1..1] ++ Payment Information Identification. n ++ Message Element that is not part of the Core and Basic Service but is available for use in a SEPA AOS n+1 [0..1] ++ Message Element that is a mandatory part of the SEPA Payment Initiation service Mandatory n+2 [0..1] ++ Message Element that is not to be used in SEPA Payments Where: Figure 2 Column 1 indicates the message element Index number in the relating ISO Message Definition Report, PDF version. Components and sub-components of message elements that are not allowed in SEPA core payments or where no specific SEPA requirements are defined, in which case ISO rules apply, are not represented in full and therefore the Index numbers will have gaps. 3 Instructing and instructed parties include CSMs. SEPA Credit Transfer C2B Implementation Guidelines Version 6.0 Approved Page 6 November 2011

8 Column 2 indicates the mandatory or optional status and the number of repetitions allowed in the ISO XML standard. When the first digit has the value 1, the message element is mandatory; when the value is 0 the message element is optional. The second digit indicates the number of repetitions allowed, where n is used to indicate no specified limit. Column 2 may also indicate conditional relationships between components of a message element, for example, either component 1 or component 2 must be present, but not both (indicated in the column 2 as {Or and Or} ). Column 3 gives the name of the message element as defined in the ISO XML standard. When an element contains sub-elements these are indented to the right and noted with a plus sign (+) per level. Column 4 specifies the requirements for the initiation of SEPA Core Payments as additional rules to those specified in the ISO XML standards, as appropriate. o Where defined in the Rulebook, the attribute is indicated between parentheses by the attribute name and where applicable number, ie, (AT-nn), and such message elements are shaded yellow. o Where the message element relates to processing requirements, it is shaded yellow. o Where the message element specified in the ISO XML standard is used for SEPA payments without change (regarding its mandatory or optional status, number of repetitions, the definition and any usage rules), no specific SEPA Core Requirements are provided and is shaded yellow. o In addition, for message elements with multiple occurrences in the ISO XML standard and shaded yellow in these Guidelines, and where a SEPA usage rule limits the number of occurrences, the remaining occurrences are available for use in an AOS. o Where the message element is specified in the ISO XML standard as optional, but is mandatory in SEPA Core Requirements, this is specified as Mandatory and is shaded yellow. o Where the message element is not available for use in SEPA payments, this is indicated with red shading. Note that these message elements are similarly not available for use in an AOS. 1.4 Character Set The character set issue centres on the use of the full set characters in the message elements. Two considerations are: While banks and their customers must be allowed to use the character set currently in use at national level, banks and their customers throughout SEPA cannot be required to support the full character set used in SEPA countries. Therefore: The ISO XML messages allow for the full range of global language requirements (UTF-8). SEPA Credit Transfer C2B Implementation Guidelines Version 6.0 Approved Page 7 November 2011

9 Banks and their customers must be able to support the Latin character set commonly used in international communication, as follows: 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 However, there may be bilateral or multilateral agreements to support one or more sets of characters beyond the Latin character set referred to above. 1.5 General Message Element Specifications BIC The BIC used to identify financial institutions (Agents in the ISO XML standards) may be either BIC 11 or BIC Implementation of ISO XML rules This document should be read in conjunction with the ISO XML message standards. ISO rules on the usage of the elements have not been repeated in these Implementation Guidelines and should be taken into account where applicable. SEPA Credit Transfer C2B Implementation Guidelines Version 6.0 Approved Page 8 November 2011

10 2 RECOMMENDED CUSTOMER-TO-BANK AND BANK-TO-CUSTOMER MESSAGES The Guidelines prescribe, where relevant and dictated by the Rulebooks, usage rules for the EPC recommended customer-to-bank and bank-to-customer ISO XML messages. The message elements identified with yellow shading must be provided when mandatory. However, message elements known by the Debtor Bank may be filled in by the Debtor Bank in order to populate the subsequent inter-bank message The elements shaded yellow specify the SEPA Core Requirements and are defined in the Rulebook, are required for inter-bank and customer-to-bank processing or are mandatory in the ISO message standards. 2.1 Customer to Bank Credit Transfer Information (DS-01) Use of the Customer Credit Transfer Initiation (pain ) The message is used to transport the Customer to Bank Credit Transfer Information sent by the Originator to the Originator Bank. The message caters for bulk and single payment instructions Message Root Index Mult Message Element SEPA Core Requirements [1..1] + Message root Group Header The group header contains information required for the processing of the entire message. Index Mult Message Element SEPA Core Requirements 1.0 [1..1] + Group Header 1.1 [1..1] ++ Message Identification 1.2 [1..1] ++ Creation Date Time 1.3 [0..2] ++ Authorisation 1.6 [1..1] ++ Number Of Transactions 1.7 [0..1] ++ Control Sum 1.8 [1..1] ++ Initiating Party 1.8 [0..1] +++ Name Usage Rule: Name is limited to 70 characters in length. 1.8 [0..1] +++ Postal Address 1.8 [0..1] +++ Identification SEPA Credit Transfer C2B Implementation Guidelines Version 6.0 Approved Page 9 November 2011

18 Index Mult Message Element SEPA Core Requirements [0..1] Creditor Reference Information Usage Rule: When present, the Debtor Bank is not obliged to validate the reference information [0..1] Type [1..1] Code or Proprietary Usage Rule: When used both Creditor Reference Type and Creditor Reference must be present. 2;123 {Or Code Usage Rule: Only SCOR is allowed Or} Proprietary [0..1] Issuer [0..1] Reference Usage Rule: If a Creditor Reference contains a check digit, the receiving bank is not required to validate this [0..1] Invoicer [0..1] Invoicee [0..3] Additional Remittance Information Usage Rule: If the receiving bank validates the check digit and if this validation fails, the bank may continue its processing and send the transaction to the next party in the chain Usage Rule: RF Creditor Reference may be used (ISO 11649) SEPA Credit Transfer C2B Implementation Guidelines Version 6.0 Approved Page 17 November 2011

19 2.2 Bank to Customer Reject Credit Transfer Dataset (based on DS-03) Caution: These Guidelines provide recommendations on the use of this XML message and are not mandatory. These Guidelines are not sufficient to fully implement this message and require additional information under bilateral agreement between the customer and its bank. The Rulebook in addition does not specify the dataset requirements Use of the Customer Payment Status Report (pain ) The code RJCT must be used in Group Status, or Transaction Status, to transport the Credit Transfer Reject instruction between the banks and their remitting customers. The message caters for bulk and single reject instructions. Note: Attribute AT-R1 in DS-03 is implied by the Message Name, pain , the Original Message Name Identification, pain and Group Status or Transaction Status. Note: Attribute AT-R4 is not applicable to reject instructions. Note: Message elements under Original Transaction Reference sequence are based on DS- 01 or DS-02 attributes. Message Root Index Mult Message Element SEPA Core Requirements [1..1] + Message root Group Header The group header contains information required for the processing of the entire message. Index Mult Message Element SEPA Core Requirements 1.0 [1..1] + Group Header 1.1 [1..1] ++ Message Identification 1.2 [1..1] ++ Creation Date Time 1.3 [0..1] ++ Initiating Party 1.4 [0..1] ++ Forwarding Agent 1.5 [0..1] ++ Debtor Agent (AT-06 BIC code of the Originator Bank) 1.6 [0..1] ++ Creditor Agent SEPA Credit Transfer C2B Implementation Guidelines Version 6.0 Approved Page 18 November 2011

25 List of changes in C2B Credit Transfer Implementation Guidelines Relative to v5.0 (This list is for information the changes included in the body of the document are the changes in effect) SYMBOLS USED 1. Column one contains the identification number of the Change 2. Column two contains the reference(s) to the relevant sections of the these Guidelines 3. Column three contains a description of the change 4. Column four contains a status code: REJ: Rejected by the SPS WG PEN: Issue pending in the SPS WG ACC: Accepted by the SPS WG in Guidelines 5. Column five contains the type of change: TYPO: Typing and layout errors CLAR: Clarification of the text CHAN: Change in or further alignment with the Rulebook content ReferenceChapter / Section / Paragraph / Bullet Description Status Type 11/ Use of these Guidelines by the instructing and instructed parties Paragraph updated as follows: Payments that include message elements that are defined and documented by AOS communities (shaded white in Figure 2) are considered as SEPA payments, but not as SEPA Core payments. Info between brackets was moved (before it was at the end of the sentence). ACC CLAR 11/ , Index , Index 3.6 Add additional Usage Rule: Name is limited to 70 characters in length. ACC CHAN 11/ Notation Conventions Paragraph updated as follows: Column 1 indicates the message element Index number in the relating ISO Message Definition Report. (instead of Column 1 indicates the message element Index number in the ISO XML standard, ISO Core Documentation ) ACC CLAR SEPA Credit Transfer C2B Implementation Guidelines Version 6.0 Approved Page 24 November 2011

SEPA Reason s The SEPA reason codes in this document are sourced from the following European Payments Council Implementation Guideline documentation which detail the customer-to-bank and inter-bank formats

EPC 004-16 Version 0.1 for public consultation 12 April 2016 SEPA INSTANT CREDIT TRANSFER SCHEME RULEBOOK Version 0.1 for public consultation from 12 April to 10 July 2016 Conseil Européen des Paiements

SEPA Direct Debit Unpaid Report File Format PAIN.002.001.03 XML File Structure This document is published by Bank of Ireland, and both it, and its contents, are the property of Bank of Ireland. This document

SEPA Credit Transfer Unpaid Report File Format PAIN.002.001.03 XML File Structure This document is published by Bank of Ireland, and both it, and its contents, are the property of Bank of Ireland. This

SEPA Credit Transfer Customer-to-Bank Implementation Guidelines for the Netherlands Disclaimer These guidelines may be subject to changes. Utmost care has been taken to ensure the information in this publication

SEPA Credit Transfers Originators Guide This 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

Credit Transfer PAIN.001.001.03 XML File Structure This 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

Financial Supply Chain SEPA SEPA formats - an introduction to XML version September 2013 www.ing.be/sepa INTRODUCTION 1 INTRODUCTION TO XML 2 What is XML? 2 What is a root element? 2 What are the specifications

XML message for SEPA Credit Transfer Initiation Implementation Guidelines for the Netherlands Disclaimer These guidelines may be subject to changes. Utmost care has been taken to ensure the information

Doc: EPC209-08 3 October 2008 (Version 2.0) EPC GUIDANCE NOTES: On the implementation of Regulation (EC) No 1781/2006 on information on the payer transposing SR VII of the FATF related to anti money laundering

General Information The MT940 customer statement message is an electronic message containing financial statement information for customers concerning their accounts. Danske Bank can send a MT940 either

Version 5.0 - February 2014 for CONSUMERS Information on the SINGLE EURO PAYMENTS AREA All you need to know about SEPA EPC Shortcut Series* Shortcut to SEPA Shortcut to the SEPA Direct Debit Schemes Shortcut

Introduction This document provides an overview of all the country specific information you need to successfully implement your migration to SEPA in Switzerland. Intending to provide a global picture of

XML message for SEPA Direct Debit Initiation Implementation Guidelines for the Netherlands Core and Business-to-Business Implementation Guidelines Disclaimer These guidelines may be subject to changes.

Since 1 st February 2014, SEPA became a reality and succeeded in harmonising the European payment landscape. However, in order to support strong local market practices, some local flavours remain applicable

SEPA Customer File Formats-Definition Proposals Purpose: The purpose of this document is to agree customer file formats for both direct debits (DDs) and credit transfers (CTs). The aim is to ensure all

SEPA Country Guide Belgium Implementing SEPA in Belgiu m All you need to know for a successful SEPA migration Introduction This document provides an overview of all the country specific information you

HSBC Your Guide to SEPA Capitalising on the opportunities Executive Summary Developed by the European Payments Council, the Single Euro Payments Area or SEPA expands on the vision behind the Euro to establish

SEPA SEPA Direct Debit Creditor Guide Glossary of Terms Version Control Version Date Name Update V1.0 30/10/2013 Bank of Ireland Creditors Guide published on BOI website This document is published by Bank

SEPA Direct Debit Instructions on the initiation format in case of amendments Occasions leading to mandate amendments During the use of the SEPA Direct Debit (SDD) product there are a number of occasions,

Version 2.0 - September 2009 How to get your Company ready for Information for BUSINESS All you need to know about SEPA EPC brochures* Making SEPA a Reality the definitive Guide to the Single Euro Payments

XML message for SEPA Direct Debit Initiation Implementation Guidelines for the Netherlands Core and Business-to-Business Implementation Guidelines Disclaimer These guidelines may be subject to changes.

Implementing SEPA in Au s t r ia All you need to know for a successful SEPA migration Introduction This document gives you an overview of all the country specific information you need to implement successfully