Addendum on the XML message for SEPA Direct Debit Initiation (PAIN)

Transcription

1 Addendum on the XML message for SEPA Direct Debit Initiation (PAIN) Version May 2012

2 Table of content 1 Introduction Character Set Change history 6 2 Message item description Group Header Message Identification Creation Date Time Authorisation Code Proprietary Number Of Transactions Control Sum Initiating Party Forwarding Agent Payment Information Payment Information Identification Payment Method Batch Booking Number Of Transactions Control Sum Payment Type Information Instruction Priority Service Level Code Proprietary Local Instrument Code Proprietary Sequence Type Category of Purpose Code Proprietary RequestedCollectionDate Creditor Creditor Account Creditor Agent Creditor Agent Account Ultimate Creditor Charge Bearer Charges Account 9 2 of 12

3 2.26 Charges Account Agent Creditor Scheme Identification Direct Debit Transaction Information Payment Identification Instruction Identification End To End Identification Payment Type Information Instruction Priority Service Level Code Proprietary Local Instrument Code Proprietary Sequence Type Category Purpose Code Proprietary Instructed Amount Charge Bearer Direct Debit Transaction Mandate Related Information Mandate Identification Date Of Signature Amendment Indicator Amendment Information Details Original Mandate Identification Original Creditor Scheme Identification Original Creditor Agent Original Creditor Agent Account Original Debtor Original Debtor Account Original Debtor Agent Original Debtor Agent Account Original Final Collection Date Original Frequency Electronic Signature First Collection Date Final Collection Date Frequency Creditor Scheme Identification Identification Pre Notification Identification 11 3 of 12

4 2.68 Pre Notification Date Ultimate Creditor Debtor Agent Debtor Agent Account Debtor Debtor Account Ultimate Debtor Instruction For Creditor Agent Purpose Code Proprietary Regulatory Reporting Tax Related Remittance Information Remittance Identification Remittance Location Method Remittance Location Electronic Address Remittance Location Postal Address Name Address Remittance Information Unstructured Structured 12 4 of 12

5 1 Introduction This addendum describes the ABNAMRO additions on the Implementation Guidelines for the XML Customer Direct Debit Initiation message UNIFI (ISO20022). This addendum provides guidance on the use of the ABNAMRO specific extra functionality for sending a Direct Debit Initiation Message, and comply with the SEPA Business-to- Business Direct Debit Scheme Customer-to-Bank Implementation Guidelines and the SEPA Core Direct Debit Scheme Customer-to-Bank Draft Implementation Guidelines of the European Council of Payments (NVB). Note: At the moment ABNAMRO supports only the Core scheme. The Business to Business scheme will be supported in the near future. The addendum is based on the Implementation Guidelines that has been developed by the Netherlands Bankers Association (NVB). The utmost has been done to make sure the information in this publication is correct. However, ABNAMRO can by no means be held responsible for any loss or damage incurred to any incorrect or incomplete information as described in this publication. Please contact your account manager at ABNAMRO for any further information. 5 of 12

6 1.1 Character Set The UTF8 character encoding standard must be used in the UNIFI messages. The Latin character set, commonly used in international communication, must be used. It contains the following characters : 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 Note: the above is about characters that can be used within the tags. For the message itself also other characters (especially < and >) can be used. The following characters will be blanked out in channel Access Online if used: : ' Change history Version number Dated Reason for revision 2.0 November 2010 New version based on version 2.0 of the NVB Implementation guideline. 2.1 April 2011 Added addendum rules for Creditor name amendment. 2.2 May 2011 Added clarification on ABN Amro usage of Category of Purpose and Purpose Code fields March 2012 Updated to version of the NVB Implementation Guidelines. 6.0 May 2012 Updated to version 6.0 of the NVB Implementation Guidelines. Only content change is the exclusion of the COR1 value in of 12

7 2 Message item description 1.0 Group Header 1.1 Message Identification This reference needs to be unique for a period of minimal one year. 1.2 Creation Date Time 1.3 Authorisation 1.4 Code 1.5 Proprietary 1.6 Number Of Transactions 1.7 Control Sum 1.8 Initiating Party 1.9 Forwarding Agent 2.0 Payment Information 2.1 Payment Information Identification Payment Information Identification will be included in account reporting, if in the SDD creditor contract batch booking is true. 2.2 Payment Method 2.3 Batch Booking This indicator is overruled with the agreed value administrated in the SDD creditor contract. Don t use this field. 2.4 Number Of Transactions The maximum number of transactions allowed is administrated in the SDD creditor contract. The technical maximum of a batch is different per channel. Please consult your channel documentation for more information. 7 of 12

8 2.5 Control Sum The maximum allowed total of all individual amounts is administrated in your SDD creditor contract. 2.6 Payment Type Information 2.7 Instruction Priority 2.8 Service Level 2.9 Code 2.10 Proprietary 2.11 Local Instrument 2.12 Code Only CORE is allowed. B2B will be allowed in the near future. COR1 is not allowed Proprietary 2.14 Sequence Type 2.15 Category of Purpose Will not be used/forwarded by ABN AMRO. Don t use this field Code 2.17 Proprietary 2.18 RequestedCollectionDate If the requested collection date is a non-target day the collection date will be shifted to the next possible TARGET date (see for the TARGET calendar) Creditor All fields will be replaced during processing with the values as administrated in the SDD creditor contract Creditor Account The account must be registered both in the SDD creditor contract and setup within the channel. 8 of 12

9 2.21 Creditor Agent The BIC that belongs to creditor account ABNANL2A. Currently mandatory, but will be optional in the near future Creditor Agent Account 2.23 Ultimate Creditor 2.24 Charge Bearer 2.25 Charges Account 2.26 Charges Account Agent 2.27 Creditor Scheme Identification 2.28 Direct Debit Transaction Information 2.29 Payment Identification 2.30 Instruction Identification 2.31 End To End Identification End To End Identification will be included in account reporting, when an R-transaction is reported (individual debit postings) Payment Type Information 2.33 Instruction Priority 2.34 Service Level 2.35 Code 2.36 Proprietary 2.37 Local Instrument 2.38 Code 2.39 Proprietary 9 of 12

10 2.40 Sequence Type 2.41 Category Purpose 2.42 Code 2.43 Proprietary 2.44 Instructed Amount 2.45 Charge Bearer 2.46 Direct Debit Transaction 2.47 Mandate Related Information 2.48 Mandate Identification 2.49 Date Of Signature 2.50 Amendment Indicator In relation to field 2.19, it is not possible to amend the creditor name Amendment Information Details 2.52 Original Mandate Identification 2.53 Original Creditor Scheme Identification 2.54 Original Creditor Agent 2.55 Original Creditor Agent Account 2.56 Original Debtor 2.57 Original Debtor Account 2.58 Original Debtor Agent 2.59 Original Debtor Agent Account 2.60 Original Final Collection Date 10 of 12

11 2.61 Original Frequency 2.62 Electronic Signature 2.63 First Collection Date 2.64 Final Collection Date 2.65 Frequency 2.66 Creditor Scheme Identification This creditor-identification identifies the current contract for SDD. This field must be the same within the batch. Business code: positions 5 to 7 contain the Creditor Business Code. This code is not part of the SDD creditor contract and can be used freely. When the Creditor Business Code is not used, then the value is set to ZZZ 2.66 Identification 2.67 Pre Notification Identification 2.68 Pre Notification Date 2.69 Ultimate Creditor 2.70 Debtor Agent Currently mandatory, but will be optional in the near future Debtor Agent Account 2.72 Debtor 2.73 Debtor Account 2.74 Ultimate Debtor 2.75 Instruction For Creditor Agent 2.76 Purpose 2.77 Code Will not be used by ABN AMRO but will be forwarded unaltered. 11 of 12

12 2.78 Proprietary 2.79 Regulatory Reporting 2.80 Tax 2.81 Related Remittance Information 2.82 Remittance Identification 2.83 Remittance Location Method 2.84 Remittance Location Electronic Address 2.85 Remittance Location Postal Address 2.86 Name 2.87 Address 2.88 Remittance Information 2.89 Unstructured Advice is to populate the unstructured remittance information field as follows: <Ustrd> < Kenmerk: Omschrijving: xxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> </Ustrd> In this way Kenmerk can be used for reconciliation, containing the current Dutch betalingskenmerk or any other reference used by the Creditor. It is recommendable to use the same reference here as in the End to end identification field. Omschrijving can be used to give the debtor a meaningful description of the collection. The unstructured information is displayed on the statement of the debtor as initiated Structured Advice is to not use this field. 12 of 12