ABI Italian. Release 3.0A September 30 th Banking Association. Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 0/41

Transcription

1 Interbank agreement for offering the additional optional service (AOS) of the SEPA Direct Debit Scheme named SEPA compliant Electronic Database Alignment (SEDA) Release 3.0A September 30 th 2014 Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 0/41

2 DOCUMENT UPDATES Date Release Effective Date Reference Documents 07/08/ October 2013 Free network message (A97) of 08 August /12/ December 2013 ABI Communication n 32 of 23 December /03/ March 2014 ABI Communication n 10 of 12 March /04/ A 30 September 2014 ABI Communication n 15 of 29 April 2014 NOTES: Release 1.0 Release 1.0 of this document has been prepared on the basis of the release 1.0 of the document Functional Specifications published on 28 December 2012 on the website and has been updated with integrations related to the standardized framework contract and to the remuneration model. Release 2.0 Release 2.0 has been updated in order to align the document to the contents of the Agreement for adherence to the SEDA service. From an operating point of view, the current release has been also updated with: - the attributes of the messages foreseen in the service remuneration model have been numerated; Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 1/41

3 - Appendices I and II have been updated (the field Reference of the Underlying Contract is no more mandatory in compliance with the SEPA Direct Debit Core and B2B Scheme Rulebook). Release 3.0 Release 3.0 has been updated in order to take in to account the following aspects: - paragraphs 7 (Remuneration model) and 8 (Obligations and responsibilities) have been reviewed to be aligned to the contents of the Implementation Guidelines for the exchange of SEDA Remuneration Messages and to correct some misprints; - changes related to the Tax identification number/vat no. of the Debtor and to the Tax identification number of the subscriber and review of the forms for the subscription of SEPA Direct Debit mandates in the SEDA context; - changes related to the AT-09 The address of the Debtor that is no more mandatory in accordance with the last release of the SEPA Direct Debit Core and B2B Scheme Rulebook. Release 3.0A Release 3.0A includes some clarifications and the following changes: - a prevision was inserted in paragraphs (Request for a new Direct Debit mandate signed by the Debtor and given to the Debtor PSP), (Communication to amend mandate data initiated by the Debtor PSP) and (Communication to cancel the mandate initiated by the Debtor PSP) in order to allow the Alignment PSP to transmit a negative response to the Debtor PSP in case it is not able to send the message received by the Debtor PSP to the Beneficiary due to formal errors; - the equalisation of values First and Recurrent in the attribute AT-21 The Transaction type was provided for in paragraph 6.3 (Management of SEPA debit requests); - Appendices I and II (mandate forms) to clarify that all the elements of the Creditor Address are mandatory. Changes are highlighted in yellow. Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 2/41

4 INDEX 1 Introduction Parties involved Agency relationship among PSPs Operating modules Participation and master data Participation by Payment Service Providers Participation by Creditors Amending and updating the Table of participating PSPs and master data Operating rules Direct debit mandate signed by the Debtor Messaging and functionalities Request for a new Direct Debit mandate signed by the Debtor and given to the Creditor Request to amend mandate data initiated by the Creditor Request to cancel the mandate initiated by the Creditor Request for a new Direct Debit mandate signed by the Debtor and given to the Debtor PSP Communication to amend mandate data initiated by the Debtor PSP Communication to cancel the mandate initiated by the Debtor PSP Management of SEPA debit requests SEDA data set DS-01: The mandate DS-02: The dematerialised mandate DS-SEDA-01: Request for a new Direct Debit mandate signed by the Debtor DS-SEDA-02: Request to amend mandate data initiated by the Creditor DS-SEDA-03: Request to cancel the mandate initiated by the Creditor DS-SEDA-05: Communication to amend mandate data initiated by the Debtor PSP DS-SEDA-06: Communication to cancel the mandate initiated by the Debtor PSP DS-SEDA-04: Responses to messages initiated by the counterparty Remuneration model Determination and publication of the price Count of active mandates and sending the Forecast report Payment of fees Detailed mandate reporting Obligations and responsibilities Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 3/41

5 8.1 Obligations of the Alignment PSP Obligations of the Debtor PSP Appendix I: SEPA DIRECT DEBIT CORE mandate form Appendix II: SEPA DIRECT DEBIT B2B mandate form Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 4/41

6 1 Introduction SEDA is an additional optional service ( AOS ) of the Pan-European direct debit schemes (SEPA Direct Debit Core and SEPA Direct Debit Business to Business 1 ) as defined by the Italian banking community in compliance with the rules set by the European Payment Council (EPC) 2. This service has been developed in response to needs expressed by the representatives of companies participating the National Committee for Migration to SEPA 3 (known by the Italian acronym CNM), wishing to incorporate the functionalities offered today by the RID Electronic Archives Alignment procedure of SITRAD (hereinafter referred to as the AEA procedure ) into SEPA standards, in order to use the Pan-European direct debiting system with the same methods and service levels to those currently guaranteed by the RID domestic debit service. On the basis of CNM s recommendation, the Italian ( ABI ) is the manager of the said AOS, is responsible in this capacity for coordinating activities for the definition and development of the SEDA service, and for participation in the service by Payment Service Providers ( PSPs ). Participating PSPs provide the service to Creditors on the basis of an executed contract, which is written according to a template, made available on the website This service is not offered to Creditors that belong to the category of consumers as defined in Italian Legislative Decree no. 206 of 6 September 2005 (the Consumer Code ) 4. PSPs offer the service in compliance with the terms and conditions laid out in this Interbank Agreement. Terms and conditions of this Interbank Agreement have been defined in line with: the provisions of EU regulation no. 260 of 14 March 2012 (art. 1, paragraph 3), hereinafter referred to as Regulation; the provisions of Bank of Italy Implementing Law of 12 February 2013 (articles 6 and 8), laying out instructions for applying the Regulation, hereinafter referred to as Implementing Law; the content of the Rulebooks of the SEPA Direct Debit Core (SDD Core) and Business to Business (SDD B2B) schemes, hereinafter referred to as Rulebooks. 1 It can be assessed in the future whether the scope of application of the SEDA service may be extended to any additional pan-european debit schemes that may be defined by the EPC. 2 To meet the specific needs of clients, the EPC recognises the possibility for individual Participants or communities of Participants to offer additional optional services (AOS) in addition to and in compliance with the basic Schemes. 3 The National Committee for Migration to SEPA (CNM) is the body - jointly monitored by the Bank of Italy and the ABI - which provides guidelines for and monitors the process of the national migration to SEPA. To ensure respect for multiple interests, representatives of all SEPA stakeholders participate in the CNM (business associations, the Public Administration, consumer associations, the post office). 4 Consumer is defined as a natural person who acts for purposes extraneous to any business, commercial, craft or professional activities carried out. Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 5/41

7 2 Parties involved The following parties are involved in providing and using the SEDA service: Creditor is the party, not belonging to the category of consumers, which uses SEPA direct debit services and the related SEDA service, as identified by one or more identification codes ( Creditor Identifiers 5 ). Alignment PSP - unique for each Creditor Identifier; is the PSP that: transmits/receives SEDA messages to/from Debtor PSPs on behalf of the Creditor; participates in the SDD Core Scheme and possibly in the SDD B2B Scheme as well; coincides with the (or one of the) PSP that also acts in the role of Creditor PSP for the Creditor (PSP that accepts the SEPA direct debit collections). Debtor PSP is the PSP that participates in the SDD Core Scheme and possibly in the SDD B2B Scheme as well, to which the SEPA direct debits sent by Creditors participating in the service are addressed. Debtor is the party that authorises SEPA direct debits on the account held at the Debtor PSP; at the choice of the Creditor, these debits may be managed in accordance with the rules of the SEDA service. The Debtor has no active role within the SEDA service. SEDA messages are exchanged through the parties qualified to operate in the role of Clearing Mechanisms (CMs) in the SEPA Direct Debit schemes. To carry out the functions associated with the transmission/receipt of SEDA messages, the PSPs that rely, under their own responsibility, on another party to offer the service (called Operative Intermediary) must report this circumstance, by qualifying their participation as indirect and specifying the information of the chosen Operative Intermediary. 5 The Creditor Identifier (corresponding to data element 2.7 of ISO standard Creditor Scheme Identification ) consists of a code format with a maximum of 35 alphanumeric characters broken down as follows: from the 1 st to 2 nd position, the ISO code of the country in which the code was issued; from the 3 rd to 4 th position, the check digits calculated using the MOD97-10 algorithm (ISO7064); from the 5 th to 7 th position, the Business Code as indicated by the Creditor for its business needs (if not indicated, the default value ZZZ is used); from the 8 th to 35 th position, the national identification code. Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 6/41

8 3 Agency relationship among PSPs PSPs wishing to offer the SEDA service to Creditors shall execute a contract to them through the Alignment PSPs who has authority to enter into the SEDA service agreement on their behalf by virtue of this provision that sets the agency relationship among the PSPs involved. In particular, the PSPs participating in the SEDA service, already chosen or which will be chosen by the Creditors to carry out the function of Alignment PSP, accept the role of agent and commit to implementing all activities associated with entering into the SEDA service agreement by using the Template available on the website (hereinafter referred to as Agreement for adherence to the SEDA service ), in the name and on behalf of each principal, who are all the PSPs time to time published on the Table of participating PSPs ). The agency relationship is free of charge and granted in the exclusive interest of each principal. The agent is vested with direct and exclusive representation of each principal in relation to the Creditor and third parties for the transactions strictly required to enter into the SEDA service agreement. The agency relationship becomes effective on the date of each principals adherence to the SEDA. Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 7/41

9 4 Operating modules The SEDA service is an additional service of the SEPA Direct Debit service, and it is offered through two different operating modules: the Basic and the Advanced module. The Basic module allows the Creditors of SEPA Direct Debits to: send - through an electronic communication with its own PSP ( Alignment PSP ), which in turn communicates with the PSPs to which the direct debits are destined ( Debtor PSPs ) - the information about the mandates acquired; send and receive information about any amendments or cancellations of mandates to/from Debtor PSPs using the same electronic communication process; obtain a confirmation of the existence and chargeability of the Debtor s account before sending the first direct debit collection and decrease errors in debit management through consistency checks that the Debtor PSPs will conduct between the information present in the debit request and the information recorded in the mandate archive. In particular, Creditors that adhere to the Basic module can receive and transmit the following messages and the associated responses: Request for a new Direct Debit mandate signed by the Debtor and given to the Creditor ; Request to amend mandate data initiated by the Creditor ; Request to cancel the mandate initiated by the Creditor ; Communication to amend mandate data initiated by the Debtor PSP ; Communication to cancel the mandate initiated by the Debtor PSP. The Advanced module supplements the functionalities of the Basic module by giving the possibility to the Creditor to delegate to the Debtor PSPs the activities connected with the acquisition and storage 6 of the mandates signed by the Debtor at its PSP (the so called Debtor Bank Mandate Flow or DMF scheme - not provided in the SDD Schemes). The additional message foreseen within the Advanced SEDA module is: Request for a new Direct Debit mandate signed by the Debtor and given to the Debtor PSP. The SEDA service applies for all mandates (and associated direct debits) relating to a Creditor Identifier of the Creditor participating in the SEDA service, that are registered in the archive of the Debtor PSPs which are also participants. The definition of mandate, and therefore the scope of application of the SEDA service, also includes direct debit authorisations issued in compliance with domestic schemes which, by virtue of what is expressly laid out in art. 7, paragraph 1 of the Regulation, shall remain valid during the transition to Pan-European Direct Debit schemes 7. The service is provided through the Basic module when the Creditor adheres to that module. 6 See art. 5, paragraph 3, letter a), point ii) of the Regulation: the payee s PSP must ensure that the payer gives consent both to the payee and to the payer s PSP (directly or indirectly via the payee), the mandates, together with later modifications or cancellation, are stored by the payee or by a third party on behalf of the payee and the payee is informed of this obligation by the PSP in accordance with Articles 41 and 42 of Directive 2007/64/EC. 7 For debit authorisations issued in Italy (called RID mandates), migration to SEPA Direct Debit schemes takes place based on the rules described in ABI Circular - technical series no. 10 of 23 April Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 8/41

10 The service is provided through the Advanced module when the Debtor PSP and the Creditor adhere to that module Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 9/41

11 5 Participation and master data 5.1 Participation by Payment Service Providers All PSPs participating in the SDD Core Scheme can adhere to the SEDA service. For PSPs, participation in the SEDA service entails offering the service at least in the role of Debtor PSP. Offering the SEDA service in the role of Alignment PSP is possible for all participating PSPs that also act as Creditor PSP for a specific Creditor. All ABI-associated PSPs participating in the SDD Core Scheme 8 must participate in the Basic module of the SEDA service. Participation in the Advanced module is optional for all PSPs. PSPs that offer the service as Alignment PSP provide this service to Creditors based on the Basic or Advanced operating module chosen by the Creditor. Debtor PSPs participating in the SDD B2B Scheme also offer the Basic or Advanced SEDA service for mandates referred to the aforementioned Scheme. The list of PSPs participating in the SEDA service ( Table of participating PSPs ) is available on the website A specific procedural master data of the participating PSPs, named SED000, is used to manage and route messages. In the service s initial phase, this master data is managed by SIA 9 since it also manages the registers currently used for the domestic debit procedure. The SED000 master data comply with the population, access and distribution rules of the master data currently in use for the domestic procedures, as described in detail in the document SIA RI ANA 001 available on the website techinfo.sia.eu. In order to participate in the SEDA service, PSPs must provide the following information in compliance with the methods announced from time to time on the website a) company name, ABI code and BIC code 10 ; b) adherence date 11 ; c) direct or indirect participation mode 12 and, for indirect participation, company name and 8 ABI Executive Committee Resolution of 17 April SIA s management of the SED000 record may be reconsidered (confirmed or changed) by sending a notice 6 months in advance. 10 So it can be registered, the PSP indicates only one BIC 11 characters long (for 8-character BIC codes, the conventional rule of inserting XXX as the last 3 characters must be observed). 11 For all ABI associates that participate in the SEPA Direct Debit Core Scheme, adherence to the Basic SEDA module is required beginning on 14 October The direct participant independently carries out the application activities associated with the transmission/receipt of flows to/from the interbank network in the role of Debtor PSP/Alignment PSP and, possibly, Intermediary PSP on behalf of other indirect participants. The indirect participant delegates the functions associated with the transmission/receipt of flows to/from the interbank network in the role of Debtor PSP/Alignment PSP to a direct participant. Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 10/41

12 BIC code of the Operative Intermediary; d) company name and BIC code of the Clearing Mechanism (CM); e) participation in the SDD Core and/or SDD B2B Scheme; f) adherence to the Basic or Advanced module; g) maximum quarterly price applied for each active mandate acquired and stored at the Creditor; h) maximum quarterly price applied for each active mandate acquired and stored at the Debtor PSP. The Table of participating PSPs provides the information referred to in letters a), b), e), f), g) and h) above. The SED000 master data includes the information referred to in letters a), b), c), d) and f) above, as well as any withdrawal date and the ABI code/company name of the incoming PSP. 5.2 Participation by Creditors Creditors that use SEPA Direct Debit services may optionally participate in the SEDA service. In order to participate, Creditors must enter into the Agreement for adherence to the SEDA service, available on the website with the Alignment PSP (which signs the agreement in the name and on behalf of itself and of the Debtor PSPs participating in the SEDA service) and provide the following information: the Creditor Identifier code(s) that they will use to be uniquely identified within the operations of the SEDA service 13 ; the operating module of participation in the service ( Basic module or Advanced module) for each of the Creditor Identifier codes indicated; IBAN of the account held at the Alignment PSP against which the Debtor PSPs participating in the service are allowed to send SEPA Direct Debit collections relating to fees due by the Creditor for using the SEDA service. Participation by Creditors will be noted within specific procedural master data named CRI000, also initially managed by SIA for the reasons already mentioned with respect to the SED000 master data. Creditors that participate in the SEDA service must be included in the CRI000 master data in order to participate in the service. In fact: SEDA service messages may be exchanged only if those messages come from or are sent to a valid Creditor Identifier code recorded in the CRI000 master data; the controls established by the SEDA service when receiving SEPA Direct Debit collections are carried out by the Debtor PSPs only if the Creditor Identifier code indicated in the direct debit collection is valid and listed in the CRI000 master data. 13 It is clarified that Creditors may participate in the service using a Creditor Identifier code not generated in Italy. Creditor Identifiers not generated in Italy are registered in the CRI000 Record based on the same rules as those used to register Italian Creditor Identifiers. Please also note that SIA has automatically generated a proposed Italian Creditor Identifier code for all companies participating in the domestic AEA-RID procedure, for which information relating to the company s tax identification number is available in the RAC procedure. Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 11/41

13 CRI000 includes the following information for each Creditor Identifier participating in the SEDA service 14 : a) company name of the Creditor; b) address of the Creditor; c) SIA code of the Creditor; d) participation in the Basic or Advanced SEDA module; e) adherence date; f) BIC of the Alignment PSP (unique for each individual Creditor Identifier code); g) date of adherence and possibly of withdrawal by the Alignment PSP (including an incoming BIC in the case of withdrawal); h) IBAN indicated by the Creditor to be used by Debtor PSPs to charge the SEDA service fee 15. Data is populated in the CRI000 master data by the Alignment PSP using the SITRAD RAC procedure ( Companies and Alignment segments) based on the methods and timing defined in the following documentation available on the website techinfo.sia.eu: SIA-RI- RAC-001 AZI, SIA-RI-RAC-003 AZI, SIA-RI-RAC MODCAR AZI, SIA-RI-RAC-001 Align, SIA- RI-RAC- 003 Align, SIA-RI-RAC MODCAR Align. The CRI000 master data is distributed based on the rules set forth in the document SIA-RI- ANA 001, also available on the website techinfo.sia.eu. By participating in the SEDA service, Creditors enter into a contractual relationship with all participating Debtor PSPs by virtue of the agency mandate granted by all participating Debtor PSPs to the Alignment PSPs 16. However, Creditors are entitled not to use the service provided by one or more specific Debtor PSPs and to stop using the SEDA service for certain mandates at any time: the participating Creditor that does not intend to use the service for mandates that will be signed by Debtors after its adherence to the SEDA service must identify such mandates using a Creditor Identifier code not registered in the CRI000 master data; the participating Creditor that does not intend to use the service for mandates issued at Debtor PSPs with a Creditor Identifier registered in the CRI000 master data must send the Debtor PSPs a Request to amend Request to amend mandate data initiated by the Creditor to change the Creditor Identifier code from a code registered in CRI000 to a code not registered in CRI000; the Creditor that decides, after its adherence to the service, to use it for certain mandates that have a Creditor Identifier code not registered in CRI000, must send the Debtor PSPs a Request to amend mandate data initiated by the Creditor to change the Creditor Identifier code from a code not registered in CRI000 to a code registered in CRI000. Creditors are also entitled to withdraw from the SEDA service at any time in relation to a specific Creditor Identifier. Withdrawal is carried out by deleting the Creditor Identifier code from the CRI000 master data, after which the PSPs (Alignment and Debtor) will stop transmitting and 14 The Creditor Identifier codes of non-profit organisations participating in the RID anch io initiative (see ABI circular letter of 4 August 2006 Prot. SP (OC/OF004347)) are also registered in the CRI000 record. Such organisations do not necessarily participate in the SEDA service. 15 The IBAN indicated by the Creditor identifies an account at the Alignment PSP. 16 See par. 3 (Granting the agency mandate between PSPs). Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 12/41

14 sending SEDA messages. By virtue of this withdrawal, the Debtor PSPs also stop carrying out the controls established by the SEDA service on direct debit collections (which will be managed without interruption in compliance with the rules set by the SEPA Direct Debit Core or B2B Scheme Rulebooks). 5.3 Amending and updating the Table of participating PSPs and master data The PSPs are entitled to announce any changes in participation that could occur in relation to: change in the operating module for providing the service ( Basic or Advanced module); change in the participation mode (direct or indirect); amendment of maximum prices applied; choice of a new Clearing Mechanism; choice of a new Operative Intermediary; withdrawal from the SEDA service (e.g., during merger/incorporation procedures). If a PSP withdraws from the SEDA service, an incoming PSP may be indicated. By virtue of this withdrawal, the PSPs do not offer the service in the role of either Debtor PSP or Alignment PSP. The aforementioned changes must be announced by the PSPs in compliance with the methods and deadlines published from time to time on the website Updates to the SED000 procedural master data also follow the rules defined in the document SIA-RI-ANA 001 available on the website techinfo.sia.eu. The Table of participating PSPs and the SED000 procedural master data are updated on a monthly basis. Creditors are entitled to report, through the Alignment PSP, any changes in participation that may involve: change in the operating module for using the service ( Basic or Advanced module); choice of a new Alignment PSP; change in the IBAN of the account to be debited for the SEDA service fee; change in the Creditor Identifier code(s) registered; withdrawal from the service. These changes must be reported by the Alignment PSP using the SITRAD RAC procedure ( Companies and Alignment segments) based on the methods and timing defined in the following documentation available on the website techinfo.sia.eu: SIA-RI-RAC-001 AZI, SIA- RI-RAC-003 AZI, SIA-RI-RAC MODCAR AZI, SIA-RI-RAC-001 Align, SIA-RI-RAC-003 Align, SIA-RI-RAC MODCAR Align. Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 13/41

15 6 Operating rules This paragraph describes the service s operating rules, the types of messages available ( Dataset ) and the information ( Attributes ) required within these messages. SEDA interbank messages: are managed with the same infrastructures used by PSPs for SDD Schemes, under a system of interoperability between Clearing Mechanisms (CMs); comply with the exchange and intermediation rules established for the same Schemes (although the PSPs are entitled to rely on Clearing Mechanisms and operative intermediaries other than those that may have been chosen for adherence to the SEPA Schemes); are exchanged using the File transfer transmission method, based on the ISO standard Payments Mandate (XML language). The interbank messages described in this paragraph are subject to the rules set by the document Implementation Guidelines and Interoperability Agreement between Clearing Mechanisms (CMs), which describes the technical rules of the procedure used by Clearing Mechanisms (CMs) to exchange SEDA messages. 6.1 Direct debit mandate signed by the Debtor The SEPA debit Schemes establish that the mandate filled out on paper and signed by the Debtor or, alternatively, filled out electronically and signed in a secure manner, must be transmitted to the Creditor. The Creditor is responsible for storing the original mandate along with any amendments that may be made to the mandate for its entire period of validity. The mandate is stored after it is cancelled in compliance with what is laid out in domestic regulations and in compliance with the deadlines by which the Rulebooks establish that the Debtor is allowed to request reimbursement of a direct debit associated with an unauthorised mandate. The mandate must comply with the instructions set by the EPC. In particular, for both SDD schemes (Core and B2B), the mandate is required to have a clear heading entitled SEPA Direct Debit Mandate. (with the addition of Business-to-Business for that type of mandate) and must contain the following attributes: Unique Mandate reference Name of the Debtor Debtor s account number IBAN Creditor company name Creditor s identifier Address, city and postal code of the Creditor Country of the Creditor Type of payment ( Recurrent or One-off ) Signature place and time Signature(s). Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 14/41

16 Mandates issued in favour of Creditors participating in the SEDA service must follow the following instructions in addition to the rules set by the SDD Scheme Rulebooks: a) the Debtor s identification code number must be obtained; b) it is also possible to include the personal data (surname, name and identification code) of the party that signed the mandate if different from the Debtor. The identification code of the Debtor and/or of the party that signed the mandate must be acquired so the Debtor PSP can verify that operations may be carried out on the account of the party that issued the mandate. For participation in the Advanced module, the Creditor must provide the Debtor with all information for which it is responsible that is needed to issue the mandate at the Debtor PSP: Unique Mandate reference Creditor company name Creditor s identifier Address, city and postal code of the Creditor Country of the Creditor Type of payment ( Recurrent or One-off ) If such information is not provided, the Debtor PSP cannot acquire the mandate. Appendices I and II include the mandate forms that Creditors participating in the SEDA service (and, for the Advanced module, participating Debtor PSPs) must use to obtain the SEPA Direct Debit Core and SEPA Direct Debit B2B Mandates, respectively. The layout of those forms may be customised, but they must contain the mandatory information. For extensive and more precise information on mandatory elements of the mandate and possible layouts, please refer to the document Guidelines for the Appearance of Mandates published on EPC s website. 6.2 Messaging and functionalities The messages that may be exchanged through the SEDA service are described below, along with the rules and controls to be carried out by the PSPs when receiving/sending such messages. Any reference to business days shall refer to the Target calendar Request for a new Direct Debit mandate signed by the Debtor and given to the Creditor This process is initiated by the Creditor after the Debtor has signed the mandate to request that the Debtor PSP activate the mandate itself. Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 15/41

17 Figure 1 Description of flow for issuing and validating a mandate - Creditor side 1. The Creditor acquires the mandate signed by the Debtor (dataset DS 01). 2. The Creditor dematerialises and files the information on the mandate in its archive (dataset DS 02). 3. After receiving the mandate from the Debtor, the Creditor sends the Alignment PSP a SEDA message containing the information on the mandate (dataset DS-SEDA 01). 4. The Alignment PSP sends the Debtor PSP a SEDA message containing the information of the mandate (dataset DS-SEDA 01). 5. The Debtor PSP performs the following minimum required controls on the information received: that the mandate received is not already present and active 17 in its archive; that the IBAN provided by the Debtor identifies an active account that can be debited 18 through SDD; that the party that signed the mandate is entitled to carry out operations on the debit account; that the mandate scheme code (AT-20 Core, B2B, other Schemes) is compliant with the debit account classification. 6. For B2B mandates, after receiving the alignment flow, the Debtor PSP obtains confirmation of the mandate data pursuant to the provisions of the SEPA B2B Scheme Rulebook and according to methods established with its client (including transmission of a copy of the mandate immediately after it is signed). 7. If the verifications have a positive outcome, the Debtor PSP activates the mandate in its archive by using the following attributes of the SEDA message received as unique key: i. The unique Mandate reference (AT-01); ii. The identifier of the Creditor (AT-02), excluding the business code 19 ; iii. The identification code of the Scheme (AT-20 - Core, B2B, other schemes). 17 If the mandate is present but inactive, the Debtor PSP shall reactivate it upon receipt of this new request message. 18 Chargeability includes the debit limitations that the debtor may choose pursuant to Regulation no. 260/ Please note that although the business code is not used to create the unique mandate key, the Debtor PSP records attribute AT-02 Creditor Identifier in the archive including the business code component. That element is relevant to the management of mandates and SEDA direct debits. Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 16/41

18 8. The Debtor PSP transmits the SEDA message containing the results of the verifications conducted to the Alignment PSP within five business days from the date of receipt of the request message (dataset DS-SEDA 04). 9. The Alignment PSP transmits the SEDA results message received from the Debtor PSP to the Creditor (dataset DS SEDA 04). The mandate is deemed active beginning on the business day subsequent to that on which the positive results message transmitted by the Debtor PSP is sent Request to amend mandate data initiated by the Creditor This process is initiated by the Creditor to communicate the Debtor PSP amendments to the mandate agreed between the Creditor and the Debtor, in relation to changes to the unique mandate key (unique mandate reference and/or Creditor identifier) or to the name of the Creditor. Figure 2 - Definition of mandate amendment flow - Creditor side 1. The Creditor manages the amendment of the mandate with the Debtor. 2. The Creditor dematerialises and files amendments made to the mandate in its archive (dataset DS 02). 3. The Creditor sends the Alignment PSP a SEDA message containing the information on the amendment of the mandate (dataset DS-SEDA 02). 4. The Alignment PSP sends the Debtor PSP a SEDA message containing the information on the amendment of the mandate (dataset DS-SEDA 02). 5. After receiving a Request to amend mandate data initiated by the Creditor, the Debtor PSP checks that: the original unique mandate key is present in its archive; the Creditor Identifier indicated in the request (including the business code) is the same recorded in the archive for that mandate 20 ; 20 The Creditor Identifier AT-02 (including the business code) filled out in this amendment message must coincide with the identifier present in the archived mandate; if there is a specific change in the Creditor identifier, it must be Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 17/41

19 the attribute being changed coincides with the corresponding archived information. 6. For B2B mandates, after receiving the alignment flow, the Debtor PSP obtains confirmation of the mandate data according to the provisions of the SEPA B2B Scheme Rulebook and according to methods established with the client (including transmission of a copy of the amendment) when the changes concern: i) the unique mandate reference, ii) the Creditor Identifier. 7. If the verifications have a positive outcome, the Debtor PSP modifies the data of the mandate in its archive effective starting on the business day subsequent to the clearing day on which the results message pursuant to the point below is sent. 8. The Debtor PSP transmits the SEDA message containing the results of the verifications conducted to the Alignment PSP 21 within five business days from the date of receipt of the mandate data amendment flow (dataset DS-SEDA 04). 9. The Alignment PSP transmits the SEDA results message received from the Debtor PSP to the Creditor (dataset DS SEDA 04). The mandate data amendment is deemed valid beginning on the business day subsequent to that on which the positive results message transmitted by the Debtor PSP is sent Request to cancel the mandate initiated by the Creditor This procedure is initiated by the Creditor to communicate to the Debtor PSP the cancellation of mandates managed through the SEDA service. Figure 3 - Definition of mandate cancellation flow - Creditor side 1. The Creditor manages the cancellation and revocation of the mandate with the Debtor; 2. The Creditor dematerialises and files in its archive the information related to the verified whether the amended Creditor identifier (including the business code) coincides with the identifier present in the archived mandate. 21 If the Creditor Identifier (AT-02) is amended via this amendment message, and the new Creditor identifier is not registered in the table of participants, the Debtor PSP indicates in the response message the amended Creditor identifier and transmits the message to the Alignment PSP associated with it. Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 18/41

20 cancellation of the mandate. 3. The Creditor sends the Alignment PSP a SEDA message for cancellation of the mandate (dataset DS-SEDA 03); 4. The Alignment PSP sends the Debtor PSP the SEDA message for cancellation of the mandate (dataset DS-SEDA 03); 5. The Debtor PSP verifies whether the cancelled mandate, identified by its unique key, is present in its archive; 6. If the verifications have a positive outcome, the Debtor PSP cancels the mandate in its own archive effective starting on the business day subsequent to the date of receipt of the communication sent by the Creditor; 7. The Debtor PSP transmits the SEDA results message to the Alignment PSP within five business days only if, following the verifications performed, it finds that the mandate is not present in its archive (dataset DS-SEDA 04); 8. The Alignment PSP forwards the result to the Creditor in a SEDA message if the Debtor PSP confirms that the mandate does not exist (dataset DS-SEDA 04). The mandate is deemed cancelled and therefore no longer active beginning on the business day subsequent to the date of receipt of the request by the Debtor PSP Request for a new Direct Debit mandate signed by the Debtor and given to the Debtor PSP This process is initiated by the Debtor PSP participating in the Advanced module, to notify the Creditor, through the Alignment PSP, registered in the table of SEDA participants, of the new mandates acquired by the Debtor PSP on behalf of the Creditor that adopts the Advanced module. Figure 4 Definition of the flow for issuing and validating a Mandate - Debtor PSP side 1. The Debtor PSP acquires the mandate signed by its client (dataset - DS-01) after verifying that the mandate includes a Creditor Identifier (AT-02), including the business code, identified in the CRI000 master data as an Advanced SEDA module participant. Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 19/41

21 2. The Debtor PSP carries out the verifications indicated in paragraph (point 5). 3. If the verifications have a positive outcome, the Debtor PSP creates an entry in its archive and registers the mandate information, using the following mandate attributes as a unique key: i. The unique Mandate reference (AT-01); ii. The identifier of the Creditor (AT-02), excluding the business code 22 ; iii. The identification code of the Scheme (AT-20 - Core, B2B, other schemes). 4. The Debtor PSP sends the SEDA new request message to the Alignment PSP of the Creditor registered in the table of SEDA participants (dataset DS-SEDA 01). 5. The Alignment PSP sends the Creditor the SEDA message regarding the new mandate (dataset DS-SEDA 01). If the Alignment PSP is not able to send the SEDA message regarding the new mandate to the Beneficiary due to formal errors, it sends a negative response to the Debtor PSP (dataset DS-SEDA 04). 6. The Creditor files the dematerialised information received. If the request is not successful, it sends the response message to the Alignment PSP within five business days (dataset DS-SEDA 04). 7. The Alignment PSP transmits the response message to the Debtor PSP. If there is no negative response message from the Creditor, the mandate must be deemed active in any event (dataset DS-SEDA 04). The mandate is deemed active beginning on the sixth business day subsequent to the date on which the request is sent by the Debtor PSP Communication to amend mandate data initiated by the Debtor PSP This process is initiated by the Debtor PSP to notify the Creditor, through the Alignment PSP, of changes in the debit account information (IBAN) due to reorganisation processes between PSPs 23 or of changes in the account provided by the Debtor within the same PSP. 22 Please note that the business code is not used to create the unique mandate key, but the Debtor PSP records attribute AT-02 Creditor Identifier in the archive including the Business Code component. 23 For example, due to mergers/acquisitions or following the sale or acquisition of branches by the Debtor PSP. Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 20/41

22 Figure 5 - Definition of mandate amendment flow - Debtor PSP side 1. The Debtor or its PSP determines the change in the debit account information (IBAN). 2. The Debtor PSP updates its archive of mandates (dataset DS-02). 3. The Debtor PSP sends the Alignment PSP the mandate amendment message (dataset DS-SEDA 05). 4. The Alignment PSP sends the Creditor the mandate amendment message (dataset DS- SEDA 05). If the Alignment PSP is not able to send the SEDA message regarding the amendment of the mandate to the Beneficiary due to formal errors, it sends a negative response to the Debtor PSP (dataset DS-SEDA 04). 5. The Creditor files the dematerialised information received. 6. The Creditor sends the Alignment PSP the SEDA results message within five business days only if, following the verifications performed, it is found that the mandate does not exist in its archive (dataset DS-SEDA 04). 7. The Alignment PSP sends the Debtor PSP the SEDA results message received (dataset DS-SEDA 04). The mandate is deemed amended beginning on the sixth business day subsequent to the date on which the request is sent by the PSP Communication to cancel the mandate initiated by the Debtor PSP This process is initiated by the Debtor PSP to notify Creditor, through the Alignment PSP, of cancellations or revocations of mandate originated by the same PSP or by the Debtor, for any reason (e.g., withdrawal of PSP authorisation, closure of the account, death, closure of the account to SDD debit requests, etc.). Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 21/41

23 Figure 6 - Definition of mandate cancellation flow - Debtor PSP side 1. The Debtor or its PSP establishes the cancellation of the mandate. 2. The Debtor PSP updates its archive of mandates effective starting on the business day subsequent to the day on which the SEDA message is sent. 3. The Debtor PSP sends the Alignment PSP the SEDA message for cancellation of the mandate (dataset DS-SEDA 06). 4. The Alignment PSP sends the Creditor the SEDA message for cancellation of the mandate (dataset DS-SEDA 06). If the Alignment PSP is not able to send the SEDA message regarding the cancellation of the mandate to the Beneficiary due to formal errors, it sends a negative response to the Debtor PSP (dataset DS-SEDA 04). 5. The Creditor files the dematerialised information received. 6. The Creditor transmits the SEDA results message to the Alignment PSP within five business days of receipt of the request only if, following the verifications performed, it is found that the mandate does not exist in its archive (dataset DS-SEDA 04). 7. The Alignment PSP sends the Debtor PSP the SEDA results message received (dataset DS-SEDA 04). The mandate is deemed cancelled and therefore no longer active beginning on the business day subsequent to the date on which the notice is sent by the Debtor PSP. 6.3 Management of SEPA debit requests The process of collecting a SEPA Direct Debit is initiated by the Creditor. If the direct debit collections report a Creditor Identifier referring to a Creditor that participates in the SEDA service, the receiving Debtor PSP carries out the specific controls described below. Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 22/41

24 Figure 7 - Definition of controls for SEPA Direct Debit collections 1. The Creditor sends the SEPA Direct Debit collection to the Creditor PSP. 2. The Creditor PSP sends the SEPA Direct Debit collection to the Debtor PSP. 3. At the reception of the SEPA Direct Debit collection, the Debtor PSP checks for the presence of the Creditor Identifier (attribute AT-02), including the Business Code, in the master data of SEDA service participants (CRI000). If the Creditor Identifier (AT-02), including the Business Code, is included in the master data of SEDA service participants (CRI000), the Debtor PSP uses the unique mandate key indicated in the direct debit collection to access the archive and find the corresponding entry. If the Debtor PSP does not find a corresponding active mandate in its archives, it rejects the direct debit collection; if, on the other hand, the PSP finds the corresponding active mandate, it carries out at least the following controls: verification that no notice of amendment (attribute AT-24) of the mandate data is indicated in the direct debit collection. If that indication is present, it does not make any change and rejects the direct debit collection 24 (any mandate amendments must be reported by the Creditors participating in SEDA using the message Request to amend mandate data initiated by the Creditor referred to in the Operating Rules paragraph); verification that the business code indicated in the direct debit collection coincides with the code recorded in the mandate. If the control has a negative result, it rejects the direct debit collection; verification that the scheme code indicated in AT-20 (Core, B2B, other Schemes) is compliant with the debit account classification. If the control has a negative result, it rejects the direct debit collection. In the SEDA context the values First and Recurrent in the attribute AT-21 The 24 As an exception to this general principle, in the first SEPA direct debit collection associated with a RID mandate to be converted to a SEPA mandate, it is possible to assign a value to the attribute AT-24 The reason for amendment of the Mandate to amend only the mandate identification code (AT-01 The unique Mandate reference ). Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 23/41

25 Transaction Type are considered equivalent 25. It follows that in case of errors regarding the usage of the values First and Recurrent, the Debtor PSP must not reject the direct debit collection 26. If all of the above controls have a positive result, the Debtor PSP performs the debit on the IBAN associated with the mandate recorded in the archive. 25 In compliance with the SDD Core and B2B Scheme Rulebooks, the usage rules for the values Last and Oneoff are unchanged. 26 This approach is based on the fact that in SEDA any additional checks carried out by the Debtor PSP when acquiring a First direct debit collection are performed in advance during the alignment phase. Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 24/41

26 6.4 SEDA data set ABI Italian DS-01: The mandate Description: indicates the information present in the mandate signed by the Debtor and sent to the Creditor. The attributes listed correspond to those provided in the SDD Rulebooks; attribute AT-S1 has been introduced in relation to the particular functionalities of SEDA. These attributes are mandatory unless otherwise indicated. Attributes AT-01 The unique Mandate reference AT-14 The name of the Debtor AT-09 The address of the Debtor (Optional) AT-27 Debtor identification code (Optional) AT-15 The name of the Debtor Reference Party (Optional) AT-37 The identification code of the Debtor Reference Party (Optional) AT-07 The account number (IBAN) of the account of the Debtor to be debited AT-08 The identifier of the underlying contract AT-13 The BIC code of the Debtor Bank (Optional) 27 AT-02 The identifier of the Creditor AT-03 The name of the Creditor AT-38 The name of the Creditor Reference Party (Optional) AT-39 The identification code of the Creditor Reference Party (Optional) AT-05 The address of the Creditor AT-25 The date of signing of the mandate AT-21 The Transaction Type 28 AT-S1 The identification code of the subscriber 29. AT-27 corresponds to the Identification code of the Debtor of the hard-copy mandate if the Debtor is not the party that signed the mandate. AT-S1 corresponds to the Identification code of the Debtor of the hard-copy mandate if the Debtor is the party that signed the mandate. AT-S1 corresponds to the Identification code of the subscriber of the hard-copy mandate if the Debtor is not the party that signed the mandate. 27 After 1 February 2014 for domestic payments and after 1 February 2016 for cross-border payments, PSPs do not ask the USPs to indicate the BIC of the debtor PSP or of the creditor PSP (art. 5, paragraph 7 of EU Regulation no. 260/2012). 28 The values Recurrent and One-off are indicated. 29 The situation of accounts requiring joint signatures, for which it may be necessary to ask the EPC and the ISO to supplement the messaging standard, shall be analysed in further detail. Document: SEDA AOS Interbank Agreement Release 3.0A Date 30/04/2014 Page 25/41