Addendum on the XML message for SEPA Direct ... - Deutsche Bank

Deutsche Deutsche Bank Bank<strong>Addendum</strong> on theXML message for SEPADirect Debit Initiation(PAIN)Version 1.0 – April 2013<strong>Addendum</strong> on the XML message for SEPA Direct Debit Initiation (PAIN) 01

Deutsche BankContentsIntroduction 031.1 Change History 041.2 Character Set 041.3 Deutsche Bank Specifics 041.4 XML File Size requirements 042 Message item description 051.1 Message Identification 051.2 Creation Date Time 051.6 Number Of Transactions 051.7 Control Sum 052.1 Payment Information Identification 052.3 Batch Booking 052.4 Number Of Transactions 052.6 Payment Type Information 052.7 Instruction Priority 052.9 Code 052.12 Code 052.13 Proprietary 052.14 Sequence Type 062.18 Requested Collection Date 062.20 Creditor Account 062.23 Ultimate Creditor 062.24 Charge Bearer 062.27 Creditor Scheme Identification 062.30 Instruction Identification 062.31 End To End Identification 062.32 Payment Type Information 062.33 Instruction Priority 072.34 Service Level 072.37 Local Instrument 072.40 Sequence Type 072.44 Instructed Amount 072.45 Charge Bearer 072.48 Mandate Identification 072.51 Amendment Information Details 072.52 Original Mandate Identification 072.58 Original Debtor Agent 072.66 Creditor Scheme Identification 072.70 Debtor Agent 072.77 Code 082.89 Unstructured 082.90 Structured 08Version 1.0 – April 2013<strong>Addendum</strong> on the XML message for SEPA Direct Debit Initiation (PAIN) 02

Deutsche BankIntroductionThis addendum describes the Deutsche Bank additions on the Implementation Guidelines for the XMLCustomer Direct Debit Initiation message UNIFI (ISO20022) “pain.008.001.02” in the Netherlands.This addendum provides guidance on the use of the Deutsche Bank specific extra functionality for sendinga 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 SEPABusiness-to-Business Direct Debit Scheme Customer-to-Bank Implementation Guidelines of the EuropeanCouncil of Payments (EPC).The addendum is based on the Implementation Guidelines that has been developed by the NetherlandsBankers’ 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 anyincorrect or incomplete information as described in this publication.Please contact your contact person at Deutsche Bank for any further information.Version 1.0 – April 2013<strong>Addendum</strong> on the XML message for SEPA Direct Debit Initiation (PAIN) 03

Deutsche Bank1.1 Change HistoryVersion number Dated Reason for revision1.0 April 2013 New version based on version6.0 of the NVB Implementationguideline1.2 Character SetThe 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 zA B C D E F G H I J K L M N O P Q R S T U V W X Y Z0 1 2 3 4 5 6 7 8 9! # $ % * ~ / -? : ; = @ [ \ ] ^ _ { | } ( ) . , ‘ +SpaceNote: the above is about characters that can be used within the tags. Characters other than listed above arereplaced with a dot (.). Within the tags, please note that the XML syntax does not allow the followingspecial characters, which must be exchanged, using the value under “XML Equivalent”:Invalid Special CharacterXML Equivalent< &lt;> &gt;‘ &apos;“ &quot;&&amp;1.3 Deutsche Bank SpecificsThe Pain008 XML ISO 20022 specification is in line with ISO standard, and outlines Deutsche Bank’s requirementsand additional optional services.Definition of AmountExpression of Amounts (14,3) = max 14 char. currency and max. 3 character fractional units.1.4 XML File Size requirementsThe maximum file size supported for the standard XML workflow in Deutsche Bank Internet Bankieren holdsa maximum of 50 MB files (equal to 50,000 – 100,000 transactions). Please be aware that larger files mayhave 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 conversionservice) up to abt. 60,000 transactions per file, and for “mega” XML SEPA files (routing service) up to abt. 2million transactions per file.Version 1.0 – April 2013<strong>Addendum</strong> on the XML message for SEPA Direct Debit Initiation (PAIN) 04

Deutsche Bank2 Message item description1.1 Message IdentificationThis 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 TimeThis date will not be validated, and can be a date in the past.1.6 Number Of TransactionsThe content of this tag will be validated. If there is a mismatch to the no. of transactions on payment informationlevel (if provided), and the no. of occurrences of DirectDebitTransactionInformation, the file will be rejected.1.7 Control SumIf provided, it will be validated (in case of mismatch, the file will be rejected).2.1 Payment Information IdentificationIf the payment is posted as a batch booking, the Payment Information Identification will be included inMT940 and CAMT.053. Default processing setting is that the payment is posted as batch on MT940 anddetailed on CAMT053.If detailed reporting of the transactions is required on MT940 or you wish to receive CAMT053 reports, pleasecontact your contact person of Deutsche Bank.2.3 Batch BookingThe code “false” indicator will overrule the standard default processing setting, whereby default is “true”.2.4 Number Of TransactionsThe technical maximum of a batch is approximately 50,000 -100,000 transactions.2.6 Payment Type InformationPayment Type Information details can be provided either in the PaymentInformation level (B-Level) or in theDirectDebitTransactionInformation level (C-level).If both are provided PaymentInformation level has priority over DirectDebitTransactionInformation level.2.7 Instruction PriorityNot supported for SEPA Direct Debit. If provided, data will be ignored.2.9 CodeCode “SEPA” should be provided. If another code will be provided Deutsche Bank will default code to “SEPA”.2.12 CodeCOR1, 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 tocheck if the debtor bank is a COR1 participant:https://www.ebaclearing.eu/SDD-Services-Participants-N=SDD_Core_SDD_B2B-L=EN.aspx2.13 ProprietaryFrom a syntax perspective the tag LocalInstrument.Proprietary is not allowed to be provided.Version 1.0 – April 2013<strong>Addendum</strong> on the XML message for SEPA Direct Debit Initiation (PAIN) 05

Deutsche Bank2.14 Sequence TypeThe Sequence Type can only be provided on this PaymentInformation level (provision underDirectDebitTransactionInformation level is not allowed).2.18 Requested Collection DateIf the requested maturity date is a non-TARGET day the maturity date will be shifted to the next possible TARGETdate (see http://www.bank-holidays.com for the TARGET calendar). The date can be set max. 30 workingdays in advance.If the batch requires extra authorization due to the fact that the SEPA Direct Debit obligo limit is insufficientthe requested maturity date can also shift to the next possible TARGET date.2.20 Creditor AccountThe account must be registered both in the SDD creditor contract and setup for SDD within Deutsche BankInternet Bankieren or db direct internet.2.23 Ultimate DebtorFor SEPA “Name” is limited to 70 characters in length2.24 Charge BearerThis element will be defaulted by Deutsche Bank to “SLEV”.2.27 Creditor Scheme IdentificationThis data element must be present either here or on Direct Debit Transaction Information level. It is recommendedthat all transactions within the same ‘PaymentInformation’ block have the same ‘CreditorScheme-Identification’.2.30 Instruction IdentificationThis ID will be reported in the account statement (MT940) in case of individual booking / reporting of thepayment.If 16 characters or less are provided, this will be mapped into field 61, subfield 7. If more than 16 charactersare 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 bereported instead.2.31 End To End IdentificationOnly the SEPA clearing supports the E2E ID with a dedicated field. Supported with max. 35 characters, andforwarded into the orderer and debtor account statement (e.g. in MT940 preceded by “EREF+”). Either anID value or e.g. “NOTPROVIDED” can be provided. The respective value will be mapped in the accountstatement.Batch booking: details of individual transactions within a batch can only be reported on the MT940 whenindicator provided in 2.3 Batch booking is “false” or CAMT053 report download is setup. Please contact yourcontact person of Deutsche Bank if you wish to receive CAMT053 reporting.R-transactions are reported individually on MT940 and CAMT053.2.32 Payment Type InformationIf PaymentTypeInformation is provided on PaymentInformation and CreditTransferTransactionInformationlevel, PaymentInformation level has priority.Version 1.0 – April 2013<strong>Addendum</strong> on the XML message for SEPA Direct Debit Initiation (PAIN) 06

Deutsche Bank2.33 Instruction PriorityNot supported, will be ignored.2.34 Service LevelCode “SEPA” should be provided. If another code will be provided, Deutsche Bank will default code to“SEPA”.2.37 Local InstrumentProvision under this level is not allowed.2.40 Sequence TypeProvision under this level is not allowed.2.44 Instructed AmountOnly EUR is allowed. Amount must be between 0,01 and 999 999 999,99 EUR (9,2 according to EPC)Sample: 11.992.45 Charge BearerThis element will be defaulted to “SLEV” by Deutsche Bank.2.48 Mandate IdentificationThis field must be unique in relation to field 2.66 Creditor Scheme Identification excluding the CreditorBusiness Code.Following characters are supported: [A-Za-z0-9]|[+?/-:().,’]Example:For Creditor Scheme Identification NL01ZZZ123456780000, NL01ABC123456780000,NL01XYZ123456780000. It is not possible to use the same Mandate Identification.2.51 Amendment Information DetailsIn relation to field 2.19, in case the name details as administrated at Deutsche Bank have been changed, thefield “Name” under “OriginalCreditorSchemeIdentification” must be filled with the name previously administratedat Deutsche Bank.2.52 Original Mandate IdentificationFollowing characters are supported: [A-Za-z0-9]|[+?/-:().,’]2.58 Original Debtor AgentAccording to the EPC Implementation Guidelines, use “Identification” under “Other” under “Financial InstitutionIdentification” with code “SMNDA” to indicate the same mandate with new Debtor Agent. In this case, theOriginal Debtor Account must not be provided.2.66 Creditor Scheme IdentificationThis 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 PaymentInformation level. It is recommended that all transactions within the same ‘PaymentInformation’ block havethe same ‘CreditorSchemeIdentification’.2.70 Debtor AgentOnly BIC is supported. Sub elements Name and PostalAddress are not recommended, as not supported forSEPA transactions.Version 1.0 – April 2013<strong>Addendum</strong> on the XML message for SEPA Direct Debit Initiation (PAIN) 07