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

Transcription

1 Deutsche Deutsche Bank Bank Addendum on the XML message for SEPA Direct Debit Initiation (PAIN) Addendum on the XML message for SEPA Direct Debit Initiation (PAIN) 01

2 Contents Introduction Change History Character Set Deutsche Bank Specifics XML File Size requirements 04 2 Message item description Message Identification Creation Date Time Number Of Transactions Control Sum Payment Information Identification Batch Booking Number Of Transactions Payment Type Information Instruction Priority Code Code Proprietary Sequence Type Requested Collection Date Creditor Account Ultimate Creditor Charge Bearer Creditor Scheme Identification Instruction Identification End To End Identification Payment Type Information Instruction Priority Service Level Local Instrument Sequence Type Instructed Amount Charge Bearer Mandate Identification Amendment Information Details Original Mandate Identification Original Debtor Agent Creditor Scheme Identification Debtor Agent Code Unstructured Structured 08 Addendum on the XML message for SEPA Direct Debit Initiation (PAIN) 02

3 Introduction This addendum describes the Deutsche Bank additions on the Implementation Guidelines for the XML Customer Direct Debit Initiation message UNIFI (ISO20022) pain in the Netherlands. This addendum provides guidance on the use of the Deutsche Bank specific extra functionality for sending a Direct Debit Initiation Message, and complies with the Customer Direct Debit Initiation message UNIFI (ISO20022), SEPA Core Direct Debit Scheme Customer-to-Bank Implementation Guidelines and the SEPA Business-to-Business Direct Debit Scheme Customer-to-Bank Implementation Guidelines of the European Council of Payments (EPC). 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, Deutsche Bank 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 contact person at Deutsche Bank for any further information. Addendum on the XML message for SEPA Direct Debit Initiation (PAIN) 03

4 1.1 Change History Version number Dated Reason for revision 1.0 April 2013 New version based on version 6.0 of the NVB Implementation guideline 1.2 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 op 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. Characters other than listed above are replaced with a dot (.). Within the tags, please note that the XML syntax does not allow the following special characters, which must be exchanged, using the value under XML Equivalent : Invalid Special Character XML Equivalent < < > > &apos; " & & 1.3 Deutsche Bank Specifics The Pain008 XML ISO specification is in line with ISO standard, and outlines Deutsche Bank s requirements and additional optional services. Definition of Amount Expression of Amounts (14,3) = max 14 char. currency and max. 3 character fractional units. 1.4 XML File Size requirements The maximum file size supported for the standard XML workflow in Deutsche Bank Internet Bankieren holds a maximum of 50 MB files (equal to 50, ,000 transactions). Please be aware that larger files may have impact on the performance during upload of the file. If you require to upload XML files larger than 50 MB, please contact your contact person of the Deutsche Bank. We offer alternative XML workflow solutions for large XML files (with immediate validation and conversion service) up to abt. 60,000 transactions per file, and for mega XML SEPA files (routing service) up to abt. 2 million transactions per file. Addendum on the XML message for SEPA Direct Debit Initiation (PAIN) 04

5 2 Message item description 1.1 Message Identification This MessageIdentification will be replaced with Deutsche Bank s File Reference Code for further processing. However, the Message ID provided in the file is passed back in the MT940 or CAMT report. 1.2 Creation Date Time This date will not be validated, and can be a date in the past. 1.6 Number Of Transactions The content of this tag will be validated. If there is a mismatch to the no. of transactions on payment information level (if provided), and the no. of occurrences of DirectDebitTransactionInformation, the file will be rejected. 1.7 Control Sum If provided, it will be validated (in case of mismatch, the file will be rejected). 2.1 Payment Information Identification If the payment is posted as a batch booking, the Payment Information Identification will be included in MT940 and CAMT.053. Default processing setting is that the payment is posted as batch on MT940 and detailed on CAMT053. If detailed reporting of the transactions is required on MT940 or you wish to receive CAMT053 reports, please contact your contact person of Deutsche Bank. 2.3 Batch Booking The code false indicator will overrule the standard default processing setting, whereby default is true. 2.4 Number Of Transactions The technical maximum of a batch is approximately 50, ,000 transactions. 2.6 Payment Type Information Payment Type Information details can be provided either in the PaymentInformation level (B-Level) or in the DirectDebitTransactionInformation level (C-level). If both are provided PaymentInformation level has priority over DirectDebitTransactionInformation level. 2.7 Instruction Priority Not supported for SEPA Direct Debit. If provided, data will be ignored. 2.9 Code Code SEPA should be provided. If another code will be provided Deutsche Bank will default code to SEPA Code COR1, CORE and B2B are allowed. COR1, CORE and B2B need to be submitted in separate files. Please be aware that not all banks are reachable for COR1 SDD. Before submitting a COR1 file, we advise to check if the debtor bank is a COR1 participant: Proprietary From a syntax perspective the tag LocalInstrument.Proprietary is not allowed to be provided. Addendum on the XML message for SEPA Direct Debit Initiation (PAIN) 05

6 2.14 Sequence Type The Sequence Type can only be provided on this PaymentInformation level (provision under DirectDebitTransactionInformation level is not allowed) Requested Collection Date If the requested maturity date is a non-target day the maturity date will be shifted to the next possible TARGET date (see for the TARGET calendar). The date can be set max. 30 working days in advance. If the batch requires extra authorization due to the fact that the SEPA Direct Debit obligo limit is insufficient the requested maturity date can also shift to the next possible TARGET date Creditor Account The account must be registered both in the SDD creditor contract and setup for SDD within Deutsche Bank Internet Bankieren or db direct internet Ultimate Debtor For SEPA Name is limited to 70 characters in length 2.24 Charge Bearer This element will be defaulted by Deutsche Bank to SLEV Creditor Scheme Identification This data element must be present either here or on Direct Debit Transaction Information level. It is recommended that all transactions within the same PaymentInformation block have the same CreditorScheme- Identification Instruction Identification This ID will be reported in the account statement (MT940) in case of individual booking / reporting of the payment. If 16 characters or less are provided, this will be mapped into field 61, subfield 7. If more than 16 characters are provided this will be mapped into field 86, subfields 20-29, preceded by KREF+ (in this case code KREF+ is quoted in field 61 subfield 7). If no InstructionIdentification is provided, the PaymentInformationIdentification (PmtInfId) of the batch will be reported instead End To End Identification Only the SEPA clearing supports the E2E ID with a dedicated field. Supported with max. 35 characters, and forwarded into the orderer and debtor account statement (e.g. in MT940 preceded by EREF+ ). Either an ID value or e.g. NOTPROVIDED can be provided. The respective value will be mapped in the account statement. Batch booking: details of individual transactions within a batch can only be reported on the MT940 when indicator provided in 2.3 Batch booking is false or CAMT053 report download is setup. Please contact your contact person of Deutsche Bank if you wish to receive CAMT053 reporting. R-transactions are reported individually on MT940 and CAMT Payment Type Information If PaymentTypeInformation is provided on PaymentInformation and CreditTransferTransactionInformation level, PaymentInformation level has priority. Addendum on the XML message for SEPA Direct Debit Initiation (PAIN) 06

7 2.33 Instruction Priority Not supported, will be ignored Service Level Code SEPA should be provided. If another code will be provided, Deutsche Bank will default code to SEPA Local Instrument Provision under this level is not allowed Sequence Type Provision under this level is not allowed Instructed Amount Only EUR is allowed. Amount must be between 0,01 and ,99 EUR (9,2 according to EPC) Sample: <InstdAmt Ccy= EUR >11.99</InstdAmt> 2.45 Charge Bearer This element will be defaulted to SLEV by Deutsche Bank Mandate Identification This field must be unique in relation to field 2.66 Creditor Scheme Identification excluding the Creditor Business Code. Following characters are supported: [A-Za-z0-9] [+?/-:()., ] Example: For Creditor Scheme Identification NL01ZZZ , NL01ABC , NL01XYZ It is not possible to use the same Mandate Identification Amendment Information Details In relation to field 2.19, in case the name details as administrated at Deutsche Bank have been changed, the field Name under OriginalCreditorSchemeIdentification must be filled with the name previously administrated at Deutsche Bank Original Mandate Identification Following characters are supported: [A-Za-z0-9] [+?/-:()., ] 2.58 Original Debtor Agent According to the EPC Implementation Guidelines, use Identification under Other under Financial Institution Identification with code SMNDA to indicate the same mandate with new Debtor Agent. In this case, the Original Debtor Account must not be provided Creditor Scheme Identification This data element is mandatory for SEPA transactions, so the Identification with sub-elements Identification and SchemeName.Proprietary must be provided. This data element can be present here or on Payment Information level. It is recommended that all transactions within the same PaymentInformation block have the same CreditorSchemeIdentification Debtor Agent Only BIC is supported. Sub elements Name and PostalAddress are not recommended, as not supported for SEPA transactions. Addendum on the XML message for SEPA Direct Debit Initiation (PAIN) 07

8 2.77 Code ISO purpose code, please refer to the ISO External Purpose Code list for valid codes. The list can be found on Unstructured Advice is to populate the unstructured remittance information field as follows: <Ustrd> < Kenmerk: Omschrijving: xxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> </Ustrd> In this way Omschrijving can be used to give the debtor a meaningful description of the collection and can be used for reconsiliation. The unstructured information is displayed on the statement of the debtor as initiated Structured Either Structured or Unstructured could be used. If both are used Unstructured has priority. Addendum on the XML message for SEPA Direct Debit Initiation (PAIN) 08