SEPA payment transactions. Formats

Transcription

1 SEPA payment transactions Formats Updated Version Status: November 2014 with amendments from 17 November 2014

2 2 Table of Contents 1. Data formats and SEPA processes current status in Germany 4 2. Relation between customer and bank formats (ISO 20022) 5 3. SEPA customer formats 6 4. Changes from November Identification of message types 9 6. Customer file structure: Extensible Mark-up Language XML SEPA Credit Transfer (SCT) Example of a customer file Reporting overview Reporting (bank-customer) Posting of SEPA bulks International SEPA formats The country-specific formats The European SEPA basic format EPC CGI Common Global Implementation (Format) Initiative Same-day urgent credit transfers in euro via pain SEPA Direct Debit (SDD) SEPA usual payment information in the format Remittance information Purpose code Category purpose The five parties to a SEPA message Name, address IBAN, IBAN-Only Creditor Identifier (CI) Identification numbers (OrgId/PrvtId) Ultimate/reference party/on behalf Mandate amendment Direct debit sequence Characters and mutated vowels (umlauts) Competing fields XOR SEPA reference numbers and how to use them 40 Identifiers are placed in the margin to quickly show you where the amendments have occurred.

3 3 For the SEPA migration, data fields in your systems will have to be updated accordingly. The following brochure contains important details about the technical specifications and the different SEPA formats. Please consider the information provided in this brochure as recommendations. It is based on the DFÜ Agreement (Remote-Data-Transfer Agreement in the German Bank Association DK). On the following pages, you will find a summary of the most important functional fields required for the migration of SEPA. For further details or information about the technical fields, please follow this link: Annex 3 of the Interface Specification for Remote Data Transmissions between Customers and Banks Pursuant to the DFÜ Agreement Version 2.8 of 30 April 2014, effective as of 17 November For more information on the final description of the formats, please consult the following: Die Deutsche Kreditwirtschaft (DK) German banking sector Annexes to Chapter 2, SEPA Payment Transactions, Version 2.8 of Annex 3 XML schemes for SEPA:

4 4 1. Data formats and SEPA processes current status in Germany Data formats SEPA data formats are based on ISO Standard 20022/UNIFI (Universal Financial Industry Message Scheme: for XML. XML is an open standard Arbitrary field content Larger than the well-known DTA formats (e. g. DTAUS and DTAZV) Character set is UTF-8, specified in XML header <?xml version= 1.0 encoding= UTF-8?> The implementation guidelines (Inter-banking-Transactions) were released by the European Payments Council (EPC) in September 2006 and are further developed on an annual basis As an XML-based format, ISO provides the foundation for modern global payment transactions and offers a vast spectrum of choices; hence, appropriate flexibility SEPA is the first application of consistent ISO processing in the payment transactions process as far as all SEPA products are concerned. The entire process chain, including account statements, is already XML- ISO based in the SEPA environment <CdtTrfTxInf> <PmtId> <EndToEndId>OriginatorID1234</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="EUR"> </InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <BIC>SPUEDE2UXXX</BIC> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>Creditor Name</Nm> </Cdtr> <CdtrAcct> <Id> <IBAN>DE </IBAN> </Id> </CdtrAcct> <RmtInf> <Ustrd>Unstructured Remittance Information</Ustrd> </RmtInf> </CdtTrfTxInf> The pain-format (payment initiation) has been defined for the customer-bank space.

5 5 2. Relation between customer and bank formats (ISO 20022) Customers submit the pain format for payment transaction files to banks. In inter-bank relationships, the payments are subsequently exchanged between the banks using the pacs format. As an option, the customer is provided with the camt format to document account postings. As an option, errors/rejects may also be provided to the customer by the bank as a file in the pain format. Payment order Error information Customer pain pain = payment initiation Payment initiation for Credit Transfers (pain.001) Direct Debits (pain.008) pain pain = payment initiation error messages** Error message/status message (pain.002) Bank Customer pacs camt pacs = payment clearing & settlement Clearing for Credit Transfers (pacs.008) Direct Debits (pacs.003) camt = cash management* Account information Notification (camt.052) Statement of account (camt.053) DTI (camt.054) pacs pacs = payment clearing & settlement error messages Error message/status (pacs.002) Customer information * Optional also as MT940 or DTI ** Optional also as DTI

6 6 3. SEPA customer formats Format evolution What will change as far as the SEPA Credit Transfer data is concerned? (DFÜ: Remote-Data Transfer Agreement in the German Bank association DK) January 2008 (DFÜ Agreement Annex 3 Version 2.2) Start SEPA Credit Transfer Format versions: pain , ct November 2008 (DFÜ Agreement Annex 3 Version 2.3) No changes to the format. No content-related format changes, although grouping and containers have been taken into account: pain , pain grp, pain con, pain ct, pain ct.con November 2009 (DFÜ Agreement Annex 3 Version 2.4) Start SEPA Direct Debit CORE & SEPA Direct Debit Business-to-Business (B2B) Format versions: pain , pain , pain Grouping standard homogenised MIXED only in compliance with European Payments Council (EPC) requirements Optional: PurposeCodes standardised (more than 100 purpose codes) e. g. salary, employee/employer sponsored deferred savings plans, public contribution accounts Optional: additional fields for the entry of third party names: ultimate creditor/debtor Optional: definition of formats for XML statement reporting (camt.052, camt.053, camt.054) November 2010 (DFÜ Agreement Annex 3 Version 2.5) Format versions: pain , pain , pain Totals fields (amount, item & reference) on the bulk level (PaymentInformation) Restructuring of the reject pain.002-message to accommodate customer requirements Structured feedback on returns fees in MT940/MT942/DTI Return code FOCR due to SCT-recall after settlement (recall) Optional: purpose of payment donation (purpose code = CHAR) Optional: verification numbers adequate CreditorReference on transfer receipts November 2011 No new formats November 2012 (DFÜ Agreement Annex 3 Version 2.6) No format changes Return code AC13 if the debtor is a consumer and FF05 if a direct debit with shorter presentation period COR1 (D -1) is not possible

7 7 November 2013 (DFÜ Agreement Annex 3 Version 2.7) Format versions: pain , pain , pain Shorter presentation period COR1 IBAN-Only Urgent credit transfer as pain.001 with URGP service level November 2014 (DFÜ Agreement Annex 3 Version 2.8) No format changes Amendments of account statements, see chapter 4 for more details Integration of SCC (SEPA Cards Clearing) Optional extension in file names of XML files in ZIP files Outlook Every year in November, a new SEPA Rulebook comes into force that provides the basis for the continuous updates to the latest requirements. The German Banking Industry Committee transfers the necessary updates into Annex 3 to the DFÜ Agreement, which means that you may possibly also have to make updates to the formats and processes. The German Banking Industry Committee has made an agreement that customarily both the current and the previous format versions are to be accepted. In addition, UniCredit accepts even older versions. However, the respective formats do have to be used to be able to utilise the new functions. The currently discussed updates can be followed on the Internet: Changes in Annex 3 to the DFÜ Agreement planned by the German Banking Industry Committee: ( top right ) Updates to be discussed by the European Payments Council (EPC) that issues the SEPA Rulebook: The consultation documents published by the EPC list various interesting fields of action, three of which deserve special mention since their implementation by November 2016 seems possible: Europe-wide support of Direct Debit Core with shorter presentation period (COR1), so that direct debit presenters can use the COR1 direct debit product throughout Europe Simplifications regarding the sequence type, so that the RCUR (recurrent) sequence type can be used generally for recurrent direct debits Relaxation regarding electronic direct debit mandates to the effect that in addition to a qualified electronic signature other legally binding methods of signature are now permitted as well.

8 8 4. Changes from November 2014 With 17 November 2014 a new DFÜ Agreement Annex 3, Version 2.8, will be implemented, which contains the following changes (published at Submission of SEPA credit transfers and SEPA direct debits only clarifications for character set schemes pain and pain remain valid Amendments of reporting of electronic XML statements (camt formats)* camt.052/054, optional usage of AdditionalInformation in GroupHeader for different use cases, e. g. if a certain filter was set camt.05x, standardized format rules for AdditionalEntry/TransactionInformation camt.05x, element group ReturnInformation, optional field AdditionalInformation now with format rule for RETURN, REJECT or REFUND in case of r-transaction for direct debits Amendments of reporting in general* new BTC for ELV card direct debits with purpose code CGDD (BTC 107 SEPA direct debit, single booking debit, via card generated direct debit at point of sale) SEPA cards clearing for start in April 2015* new schemes for submission of guaranteed card payments (e. g. POS-net operators) in format pain with LocalInstrument code CARD and reversal pain new BTC for SEPA cards clearing 106 SCC card debit; 110 SCC debit return; 182 SCC refund; 190 SCC debit collection; 198 SCC credit collection; 199 SCC reversal new return codes for SEPA cards clearing SVNR service not rendered; EMVL EMV liability shift; PINL PIN liability shift) return code BE06 is mapped to text key extension 929 and AM09 to 935 new purpose codes for guaranteed card payments IDCP/CDDP card payment; CDCB/CDCD/CDCS cash disbursement; MTUP mobile top up; ETUP/CBLK/FCOL e-purse * Please find further information in our brochures SEPA reporting and Business transaction and return codes, which you can obtain from your Cash Management & ebanking Specialist upon request.

9 9 5. Identification of message types How can you identify the type of message and the version? Structure of an XML message designation: pain Version V3 ISO Status 2009 Variant Die Deutsche Kreditwirtschaft (German Banking Sector) Message Definition CustomerCreditTransferInitiation Business Area PaymentInitiation pain Business Area pain PAymentINnitiation Message Definition 001 CustomerCreditTransferInitiation 008 CustomerDirectDebitInitiation 002 CustomerPaymentStatusReport (Reject) 007 CustomerPaymentReversal (cancellation of a direct debit) 009 through 012 Initiation, Amendment, Cancellation and Acceptance of a Mandate Variant 003 DK Version DK Version ISO 20022/EPC Version 05 ISO Version 05/ ISO Version 04/ ISO Version 03/ ISO Version 09/ ISO Version 09/2005 camt CAshManagemenT 052 BankToCustomerAccountReport Successor of payment transaction notification MT BankToCustomerStatement Successor of account statement MT BankToCustomerDebitCreditNotification Successor of bulked DTI 055 CustomerPaymentCancellationRequest Recall by customer 086 BankServicesBillingStatement (previously TWIST-BSB) Planned Planned Planned

10 10 Initiation of a SEPA Credit Transfer customer-to-bank space The following types of orders are available through the transfer channels (EBICS/HBCI or FinTS): SEPA Credit Transfer Order Types DK format Name space/scheme SCT 2.7/2.8 (2013/2014) EBICS mixed urn:iso:std:iso:20022:tech:xsd:pain CCT pain EBICS mixed special process without VEU details urn:iso:std:iso:20022:tech:xsd:pain XCT pain EBICS XML container urn:conxml:xsd:container.nnn (+urn:iso:std:iso:20022:tech:xsd:pain ) CCC pain EBICS reject urn:iso:std:iso:20022:tech:xsd:pain CRZ (zip file) or CRC (XML container) pain HBCI bulk HKCCM, HKCME HBCI single HKCCS, HKCSE UniCredit still accepts and delivers older versions of the DFÜ Agreement: DFÜ Agreement Annex 3 Version 2.5/2.6 (2010/2012): pain or pain DFÜ Agreement Annex 3 Version 2.4 (2009): pain or pain or DFÜ Agreement Annex 3 Version 2.3 (2008): pain grp, pain con, pain or pain Initiation of a SEPA Direct Debit customer format The following types of orders are available through the transfer channels (EBICS/HBCI or FinTS): SEPA Direct Debit Order Types Name space/scheme SDD CORE/COR1 2.7/2.8 (2013/2014) SDD B2B 2.7/2.8 (2013/2014) EBICS mixed urn:iso:std:iso:20022:tech:xsd:pain CDD/CD1 pain EBICS XML container urn:conxml:xsd:container.nnn (+urn:iso:std:iso:20022:tech:xsd:pain ) CDC/D1C pain EBICS reject urn:iso:std:iso:20022:tech:xsd:pain CDZ (zip file) or CBC (XML container) pain HBCI bulk HKDME HKBME CDB pain C2C pain CDZ (zip file) or CBC (XML container) pain UniCredit still accepts and delivers older versions of the DFÜ Agreement: DFÜ Agreement Annex 3 Version 2.5/2.6 (2010/2012): pain or pain DFÜ Agreement Annex 3 Version 2.4 (2009): pain or pain Reject messages (pain.002) are used if the return occurs prior to settlement, i.e. prior to booking, e.g. due to formatting errors. Further information on pain.002 and the return reasons is provided in the documents Customer information on reporting within the SEPA and Business transaction and return codes for camt.05x, pain.002 and MT94x, which you can obtain from your Cash Management & ebanking Specialist upon request. From April 2015, transactions for the SEPA Cards Clearing (SCC) can be transmitted using the ISO message types pain (submission) and pain (correction) as well as the pertinent order types. Again, your Cash Management & ebanking Specialist will be happy to provide you upon request with the document SEPA data exchange by remote data transfer with data processing service centres (SRZ) and net operators via EBICS containing further information on SCC. Further information on pain.002 and the return reasons is provided in our brochures SEPA reporting and Business transaction and return codes, which you can obtain from your Cash Management & ebanking Specialist upon request.

11 11 6. Customer file structure: Extensible Mark-up Language XML XML Container Only for German DK formats Optional GroupHeader This block must be included and exists once It contains elements, such as the message ID, creation date and time PaymentInformation (bulk level) This block must appear at least once and is repeatable It contains elements that pertain to the transaction s origins, e. g. the presenter or payment type information or several transaction information blocks Logical bulk level for the posting of the presenter (consolidated) TransactionInformation This block must appear at least once per payment information and is repeatable Among other things, it contains elements that refer to the payment beneficiary for credit transfers the debtor in conjunction with direct debits Contains the amount and remittance information Order Type Containers and File Structure with GroupHeader, PaymentInformation and TransactionInformation DK XML container EBICS order type CCC pain.001 GroupHeader InitiatingParty Company name-1 PaymentInformation Debtor: Account-1 TransactionInfo Creditor/EUR PaymentInformation Debtor: Account-2 TransactionInfo Creditor/EUR EBICS order type CCT (mixed) pain.001 GroupHeader InitiatingParty Company name-1 PaymentInformation Debtor: Account-1 TransactionInfo Creditor/EUR PaymentInformation Debtor: Account-2 TransactionInfo Creditor/EUR pain.001 GroupHeader InitiatingParty Company name-1 PaymentInformation Debtor: Account-3 TransactionInfo Creditor/EUR EBICS order type CCT (mixed) pain.001 GroupHeader InitiatingParty Company name-1 PaymentInformation Debtor: Account-3 TransactionInfo Creditor/EUR

12 12 Grouping of files and which ones can be delivered in mixed transactions? SEPA files are submitted as bulks, so that files have to be created For each physical file (delivery (e. g. XML container/groupheader) divided by Product (SCT, SDD CORE, SDD COR1, SDD B2B, CT-Urgent) XML-Scheme, <PmtInfId>, <SvcLvl> and <LclInstrm>), given that a separate transmission order type has to be used for each delivery For each logical bulk (PaymentInformation), in particular also divided by IBAN of ordering party Due date <ReqdColltnDt> or execution date <ReqdExctnDt> Direct debit sequence (First, Recurrent, Final, OneOff) <SeqTp> Differentiation between SCT and SCT-Preferred (same day clearing) <InstrPrty> Bulk/single posting of the submission <BtchBookg> Number of transactions or file size limits, see below* The following can e. g. be placed into one logical bulk together: Direct debits: various recipients or debtors Different amounts <Amt> RemittanceInformation <RmtInf>, PurposeCodes <Purp>, End-to-End references <EndToEndId> Differing mandate information for direct debits * DTAUS, the current payment format, uses much smaller file sizes than the XML file format. Without a header, a DTAUS transaction may have up to 622 bytes, while a SEPA transaction may contain up to 2,100 bytes, plus header information. In order to receive files that can still be processed (file transfer, mapping, validation, error research, etc.) it is recommended not to use bulks of excessive size. A maximum of 100,000 transactions per file is recommended (up to 210 MB) Checks for duplicate file processing To prevent the duplicate processing of files, UniCredit checks the logical bulkes (PaymentInformation) based on the following principles: IBAN for presenter Time frame: 15 target days Total amount in EUR Determined number of items Product (SEPA Credit Transfer, SEPA Direct Debit CORE/COR1, SEPA Direct Debit B2B) Total check digits (digits 3 4) for all beneficaries and debtors IBAN

13 13 7. SEPA Credit Transfer (SCT) Basic characteristics Presenter and beneficiary accounts are both being maintained in the SEPA zone (the account holder may also be domiciled outside of this zone) The transaction currency is always EUR What distinguishes the above from domestic transfers (replaced since 1 August 2014) Use of IBAN/BIC Remittance information is limited to 140 characters (DTA: 378 characters) Additional purpose codes are possible as an option Use of on-behalf/ultimate optionally possible Additional reference options available For border crossing transactions in the SEPA zone What distinguishes the above from standard EU transfers (replaced since 1 April 2012) Explicitly also for domestic use No balance of payments reporting included in the data Also for payments to Switzerland and Monaco

14 14 Important functional XML fields for SEPA Credit Transfer Field names Description pain Entry DFÜ Agreement Annex 3 Versions 2.8 For more details see Page GrpHdr GroupHeader Sender data 1 per logical file 11 f. MsgId Submitter reference number for Mandatory (unique) Max. 35 characters 37 f., 40 ff. (Message-Id) each file CreDtTm Date/time file was created Mandatory ISO date (CreationDateTime) NbOfTxs (NumberOfTransactions) Number of all single transactions Mandatory Unlimited CtrlSum (ControlSum) InitgPty-Nm (InitiatingPartyName) InitgPty-Nm-Id-OrgId/PrvtId (InitiatingPartyOrganisation-Id/ Private-ID) Amount submitted in EUR for cross-checking Recommended Unlimited Name of the initiating party (may Mandatory Max. 70 characters 24 f. be different from name of ordering party) Identification DK not recommended Various 30 PmtInf PaymentInformation Debtor data Any frequency possible, 11 f. max. recommended 100 PmtInfId Bulk reference Mandatory Max. 35 characters 37 f., 40 ff. (PaymentInformation-ID) PmtMtd (PaymentMethod) Payment method: credit transfer Mandatory TRF BtchBookg (BatchBooking) NbOfTxs (NumberOfTransactions) CtrlSum (ControlSum) InstrPrty (InstructedPriority) SvcLvl-Cd (ServiceLevelCode) CtgyPurp (CategoryPurpose) ReqdExctnDt (RequestedExecutionDate) Dbtr-Nm (DebtorName) Dbtr-PstlAdr-Ctry (DebtorCountry) Dbtr-PstlAdr-AdrLine (DebtorAddress) Dbtr-Id-OrgId/PrvtId (DebtorOrganisation-Id/Private-ID) DbtrAcct-IBAN (DebtorIBAN) DbtrAcct-Ccy (DebtorAccountCurrency) DbtrAgt-BIC (DebtorAgentBIC) DbtrAgt-Othr-Id (DebtorAgentId) UltmtDbtr (UltimateDebtorName) UltmtDbtr-Id-OrgId-Othr (UltimateDebtor-IBAN) Presenter booking bulk/sinlge Total number of all single transactions Cross-checking logical file amount in EUR Priority of execution high or norm Service scheme File payment type/category Purpose Optional, administrated in the master data system Recommended Recommended Optional, administrated in the master data system Mandatory field if the higher-level Payment Type Information field is used, otherwise only recommended Optional, administrated in the master data system false single transaction true bulk transaction Unlimited Unlimited Requested execution date Mandatory ISO date 44 f. HIGH SCT Preferred 39 NORM SCT Normal SEPA, URGP 39, 51 For salary payment on the same day SALA 24, 39 Name debtor, may have been replaced with account holder name by the bank Mandatory Max. 70 characters 24 f. Country of debtor s address Optional Country code ISO 3166, 25 DE for Germany Address of the debtor, may have Optional Max. 140 characters 25 been replaced with account holder name by the bank Identification DK not recommended Miscellaneous 30, 40 ff. IBAN of the debtor Mandatory Max. 34 characters 26 ff., 37 f. Debtor account currency Optional Currency code BIC/SWIFT code of the debtor Mandatory 8 or 11 digits 28, 37 f. IBAN-Only ID Optional in the case of German banks (IBAN-Only), otherwise mandatory NOTPROVIDED 28 Debtor that is not identical with Optional Max. 70 characters 24 f., 31, 39 the account holder. Sole purpose is to provide information. Ultimate submitter debit IBAN Optional, only for product Ultimate ordering party Max. 34 characters 26 ff., 31, 37 f. ChrgBr (ChargeBearer) Charging always shared Recommended SLEV 39

15 15 Continuation Field names CdtTrf- TxInf CreditTransfer- TransactionInformation InstrId (Instruction-ID) EndToEndId (End2End-ID) InstrAmt (InstructedAmount) UltmtDbtr (UltimateDebtor) UltmtDbtr-Id-OrgId/PrvtId (UltimateDebtorOrganisation-Id/ Private-ID) CdtrAgt-BIC (CreditorAgentBIC) Cdtr-Nm (CreditorName) Cdtr-PstlAdr-Ctry (CreditorCountry) Cdtr-PstlAdr-AdrLine (CreditorAddress) Cdtr-Id-OrgId/PrvtId (CreditorOrganisation-Id/Private-ID) CdtrAcct-IBAN (CreditorIBAN) UltmtCdtr (UltimateCreditorName) UltmtCdtr-Id-OrgId/PrvtId (UltimateCreditorOrganisationId/ Private-ID) Purp (Purpose) Ustrd-RmtInf (UnstructuredRemittanceInfo) Strd-CdtrRefInf- CdtrRefTp-Cd (StructuredCreditor Reference-Code) Strd-CdtrRefInf-CdtrRef (StructuredCreditor Reference) Description pain Transaction information Technical reference between submitter and bank Reference to be passed on to the beneficiary Entry DFÜ Agreement Annex 3 Versions 2.8 For more details see Page Any frequency possible, 11 f. max. recommended 100,000 Optional, if completed: unique Max. 35 characters 37 f., 40 ff. Mandatory (has to be definitive, if not: NOTPROVIDED ) Max. 35 characters Amount and currency code Mandatory EUR permitted only 37 f., 40 ff. Different debtor Optional. Not to be entered if information has already been entered on the PmtInf level Max. 70 characters 24 f., 31, 39 Identification DK not recommended Miscellaneous 30, 39, 40 ff. BIC/SWIFT code of beneficiary s bank Optional in the case of German banks (IBAN-Only), otherwise mandatory 8 or 11 digits Additionally at UniCredit NOTPROVIDED, NOTAVAIL Name of the beneficiary Mandatory Max. 70 characters 24 f. Country of beneficiary s address Optional Country code ISO 3166, 25 DE for Germany Address of the beneficiary Optional Max characters 25 Identification DK not recommended Miscellaneous 30 28, 37 f. IBAN of the beneficiary Mandatory Max. 34 characters 26 ff., 37 f. Different final beneficiary. Provided for information only. Optional Max. 70 characters 24 f., 31, 39 Identification DK not recommended Miscellaneous 30, 39, 40 ff. Type of payment (text code), e. g. SALA (Salary) in the case of salary payment* Unstructured remittance information Structured remittance information for creditor reference Structured remittance information Part 2 CreditorReference: Check digits adequate creditor reference Optional ISO ExternalPurposeCode- List 23 Recommended Max. 140 characters 21, 39 To be used only if the remittance information is not unstructured To be used only if the remittance information is not unstructured RF + check digits + reference (ISO 11649) SCOR 22, 39 Max. 35 characters 22, 39 Strictly technical fields or fields that are possible in Germany but not recommended by the banks have not been listed (e. g. OrgId, other structured remittance information). Details and the specifics on all fields can be found in the DFÜ Agreement Annex 3 in Specification of the Data Formats. * Please find further information in our brochures SEPA reporting and Business transaction and return codes, which you can obtain from your Cash Management & ebanking Specialist upon request.

16 16 8. Example of a customer file GroupHeader Description DTAUS-Feld <?xml version="1.0" encoding="utf-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain " xmlns:xsi=" xsi:schemalocation="urn:iso:std:iso:20022:tech:xsd:pain pain xsd"> <CstmrCdtTrfInitn> <GrpHdr> <MsgId> </MsgId> <CreDtTm> T10:55:06</CreDtTm> <NbOfTxs>1</NbOfTxs> <InitgPty> <Nm>MEIER PAYMENT MUENCHEN</Nm> </InitgPty> </GrpHdr> PaymentInformation logical file <PmtInf> <PmtInfId>PAYMENT </PmtInfId> <PmtMtd>TRF</PmtMtd> <BtchBookg>true</BtchBookg> <NbOfTxs>1</NbOfTxs> <CtrlSum> </CtrlSum> <PmtTpInf> <InstrPrty>NORM</InstrPrty> <SvcLvl> <Cd>SEPA</Cd> </SvcLvl> </PmtTpInf> <ReqdExctnDt> </ReqdExctnDt> <Dbtr> <Nm>MEIER CORNELIA MUENCHEN</Nm> </Dbtr> <DbtrAcct> <Id> <IBAN>DE </IBAN> </Id> </DbtrAcct> <DbtrAgt> <FinInstnId> <BIC>HYVEDEMMXXX</BIC> </FinInstnId> </DbtrAgt> <UltmtDbtr> <Nm>MEIER GEHALTSABTEILUNG</Nm> </UltmtDbtr> <ChrgBr>SLEV</ChrgBr> CreditTransferTransactionInformation individual transaction <CdtTrfTxInf> <PmtId> <EndToEndId>OriginatorID1234</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="EUR"> </InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <BIC>SPUEDE2UXXX</BIC> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>Creditor Name</Nm> </Cdtr> <CdtrAcct> <Id> <IBAN>DE </IBAN> </Id> </CdtrAcct> <Purp> <Cd>PENS</Cd> </Purp> <RmtInf> <Ustrd>Unstructured Remittance Information</Ustrd> </RmtInf> </CdtTrfTxInf> </PmtInf> </CstmrCdtTrfInitn> </Document> XML scheme and XSD location GroupHeader MessageID unique reference of the file Creation Date/Time Number of transactions Optional grand total EUR across all logical files Name initating party (e. g. DATEV) (~DTA-A7) (DTA-A6) PaymentInfID definitive reference of the logical bulk (~DTA-A10) Payment method:transfer Batch booking true/false bulk/single transaction Number of items (DTA-E4) Total amount in EUR (DTA-E8) Priority NORM/HIGH (SCT-Preferred) ServiceLevel SEPA Execution date Debtor name (if applicable, with address) Debtor IBAN BIC of the originator bank Ultimate debtor name SLEV = Share End2End-Id Payment reference from ordering debtor s perspective Amount in EUR Creditor BIC of beneficiary bank Creditor name Creditor IBAN Purpose text code for payment see ISO external code list Remittance Information 140 characteres (DTA-A11b) (DTA-C15) (~DTA-C11) (~DTA-C10) (DTA-C12) (~DTA-C4) (DTA-C14a + Erw) (~DTA-C5) (~DTA-C7a) (~DTA-C16 + Erw)

17 17 9. SEPA Direct Debit (SDD) Basic characteristics SEPA Direct Debit CORE (SDD CORE) Similar to Collection Authorisation Procedure (Einzugsermächtigung) SEPA Direct Debit Business-to-Business (SDD B2B) Similar to Debit Order Procedure (Abbuchungsauftrag) For the purpose of validation, the mandate must also on hand at the debtor s bank What distinguishes the above from domestic direct debits: Collection Authorisation Procedure ( Einzugsermächtigung ) was superseded as of 1 August 2014 and Debit Order Procedure ( Abbuchungsauftrag ) as of 1 February 2014 Provision of the Creditor Identifier (assigned by the German Federal Bank) Provision of mandate information (mandate-id and mandate signature date) Provision of process relevant information (submission sequence, due date with respective presentation periods) Use of IBAN/BIC Remittance information limited to 140 characters (DTA: 378 characters) Additional payment purposes (PurposeCodes) are possible as an option Use of on-behalf/ultimate possible Additional referencing options Cross-border use in the SEPA zone Important functional XML fields for SEPA Direct Debit Field names Description pain Entries DFÜ Agreement Annex 3 Version 2.8 Content of the paperbased mandate GrpHdr GroupHeader Sender data 1 per logical file 11 f. MsgId (Message-Id) CreDtTm (CreationDateTime) NbOfTxs (NumberOfTransactions) CtrlSum (ControlSum) InitgPty-Nm (InitiatingPartyName) InitgPty-Nm-Id-OrgId/PrvtId (InitiatingPartyOrganisation-Id/ Private-ID) Submitter reference number for each file More details on Page Mandatory (unique) Max. 35 characters 37 f., 40 ff. Date/time file was created Mandatory ISO date Total number of individual transactions Mandatory Unlimited Amount submitted in EUR for Recommended Unlimited cross-checking Name of the initiater/submitter Mandatory Max. 70 characters 24 f. (may be different from the creditor) Identification DK not recommended Miscellaneous 30 PmtInf PaymentInformation Payment recipient data Any frequency possible, max. recommended 100 PmtInfId (PaymentInformation-ID) PmtMtd (PaymentMethod) BtchBookg (BatchBooking) NbOfTxs (NumberOfTransactions) Bulk reference Mandatory Max. 35 characters 37 f., 40 ff. Payment method: direct debit Mandatory DD Presenter/creditor booking bulk/ single transaction Total number of single transactions Optional, administrated in the master data system Recommended true bulk trans action false single transaction Unlimited 11 f. 44 f.

18 18 Continuation Field names CtrlSum (ControlSum) SvcLvl-Cd (ServiceLevelCode) LclInstrm-Cd (LocalInstrumentCode) SeqTp (SequenceType) CtgyPurp (CategoryPurpose) ReqdColltnDt (RequestedCollectionDate) Cdtr-Nm (CreditorName) Cdtr-PstlAdr-Ctry (CreditorCountry) Cdtr-PstlAdr-AdrLine (CreditorAddress) CdtrAcct-IBAN (CreditorIBAN) CdtrAcct-Ccy (CreditorAccountCurrency) CdtrAgt-BIC (CreditorBIC) CtrAgt-Othr-Id (CreditorAgentId) UltmtCdtr (UltimateCreditor) UltmtCdtr-Id-OrgId-Othr (UltimateCreditorIBAN) UltmtCdtr-Id-OrgId/PrvtId (UltimateCreditorOrganisation-Id/ Private-ID) ChrgBr (ChargeBearer) CdtrSchmeId-Id-PrvtId-OthrId-Id (CreditorIdentification) Description pain Entries DFÜ Agreement Annex 3 Version 2.8 Content of the paperbased mandate Cross-checking logical file amount in EUR Recommended Unlimited Service scheme Mandatory SEPA 39 Direct Debit CORE or Direct Debit B2B Sequence: first, recurrent, OneOff or final direct debit Mandatory (cannot be mixed within GrpHdr) Mandatory More details on Page CORE, COR1 or B2B 35, 39 FRST, RCUR, OOFF or FNAL Mandatory (recurring or one-time) File category purpose Optional Not to be forwarded to the end customer 24, 39 Direct debit due date (date to be Mandatory ISO date 35 posted to the debtor s account) Name of the creditor, may have Mandatory Max. 70 characters Mandatory 24 f. been replaced with account holder name by the bank Country of creditor s address Optional Country code ISO 3166, Mandatory 25 DE für Deutschland Address of the creditor, may Optional Max. 140 characters Mandatory 25 have been replaced with account holder name by the bank IBAN of the creditor Mandatory Max. 34 characters 26 ff., 37 f. Account currency: has to be EUR Optional EUR BIC/SWIFT code of the creditor IBAN-Only ID Creditor that is not identical with the account holder. For information only. Ultimate creditor IBAN Optional in the case of German banks (IBAN-Only), otherwise mandatory Optional when using IBAN-Only for Germany 32 ff. 8 or 11 digits 28, 37 f. NOTPROVIDED 28 Optional Max. 70 characters Optional 24 f., 31, 39 Optional, only if the product is Ultimate ordering party Max. 34 characters 26 ff., 31, 37 f. Identification DK not recommended Miscellaneous 30, 39, 40 ff. Charging always shared Mandatory. As of DFÜ SLEV 39 Agreement Annex 3 Version 2.6 changed to Recommended Creditor identification. Clear identification characteristic of the creditor (per legal entity) Mandatory, either on the PmtInf level or on the transaction level always the same Max. 35 characters Mandatory 29, 32 ff., 39

19 19 Continuation Field names DbtTrf- TxInf DirectDebit- TransactionInformation InstrId (Instruction-ID) EndToEndId (End2End-ID) InstrAmt (InstructedAmount) MndtId (MandateID) DtOfSgntr (DateOfSignature) AmdmntInd (AmendmentIndicator) OrgnlMndtId (OriginalMandateID) OrgnlCdtrSchmeId-Nm (OriginalCreditorName) OrgnlCdtrSchmeId-Id-PrvtId- OthrId-Id (OriginalCreditorIdentification) OrgnlDbtrAcct-IBAN (OriginalDebtorIBAN) OrgnlDbtrAgt-Id (OrignalDebtorAgentID) ElctrncSgntr (ElectronicSignature) CdtrSchmeId-Id-PrvtId-OthrId-Id (CreditorIdentification) UltmtCdtr (UltimateCreditorName) UltmtCdtr-Id-OrgId/PrvtId (UltimateCreditorOrganisation-Id/ Private-ID) DbtrAgt-BIC (DebtorAgentBIC) DbtrAgt-Othr-Id (DebtorAgentId) Description pain Transactions information Technical reference between submitter and bank Reference, to be passed on to the debtor Entries DFÜ Agreement Annex 3 Version 2.8 Any frequency possible, max. recommended Optional, if completed: unique Mandatory (if used, otherwise: NOTPROVIDED ) Max. 35 characters Max. 35 characters Amount and currency code Mandatory EUR permitted only Content of the paperbased mandate Unique mandate reference Mandatory Max. 35 characters Can be supplied later Date, on which the mandate was signed Indicates whether the mandate was amended Reference of the original mandate if the mandate reference (MndtId) has changed Original creditor name if the creditor of the payment has changed Original creditor identification if the creditor identification has changed (CdtrSchmeId) Original IBAN of the debtor if the IBAN has changed The original debtor bank has changed. Resubmission with sequence FRST required Electronic mandate emandate electronic signature Creditor identification. Unique identification property of the creditor of the payment (per legal entity) Name of a different creditor Mandatory ISO date Mandate, in papermandates also location where it was signed and signature Mandatory Amendment = true Standard = false Only if the mandate has Max. 35 characters changed (AmdmntInd = true ) Only in the event of a Max. 70 characters mandate change (AmdmntInd = true ) Only in the event of a mandate change (AmdmntInd = true ) Only in the event of a mandate change (AmdmntInd = true ) Only in the event of a mandate change (AmdmntInd = true ) Optional. Not for paperbased mandates Mandatory, either on the PmtInf level or on the transaction level, always the same. Optional. Nor if already entered in the PmtInf level More details on Page 11 f. 37 f., 40 ff. 37 f., 40 ff. 37 f., 40 ff. 32 ff. 32 ff., 37 f., 40 ff. 32 ff. Max. 35 characters 29, 32 ff., 40 ff. Max. 34 characters 26 ff., 32 ff., 37 ff. Identifier SMNDA (Same Mandate New Debtor Agent) Max characters; relevant with emandate at future date 32 ff., 36 Max. 35 characters 29, 32 ff., 39 Max. 70 characters 24 f., 31, 39 Identification DK not recommended Miscellaneous 30, 39, 40 ff. BIC/SWIFT code of the debtor bank IBAN-Only ID Optional in the case of German banks (IBAN-Only), otherwise mandatory Optional when using IBAN-Only for Germany 8 or 11 digits Additionally at UniCredit: NOTPROVIDED, NOTAVAIL Optional in the case of German banks (IBAN-Only), otherwise mandatory 28, 37 f. NOTPROVIDED 28

20 20 Continuation Field names Dbtr-Nm (DebtorName) Dbtr-PstlAdr-Ctry (DebtorCountry) Dbtr-PstlAdr-AdrLine (DebtorAddress) Dbtr-Id-OrgId/PrvtId (DebtorOrganisation-Id/Private-ID) DbtrAcct-IBAN (DebtorIBAN) UltmtDbtr (UltimateDebtor) UltmtDbtr-Id-OrgId/PrvtId (UltimateDebtorOrganisation-Id/ Private-ID) Purp (Purpose) Ustrd-RmtInf (Unstructured RemittanceInfo) Strd-CdtrRefInf-CdtrRefTp-Cd (StructuredCreditor Reference-Code) Strd-CdtrRefInf-Cdtr Ref(StructuredCreditorReference) Description pain Entries DFÜ Agreement Annex 3 Version 2.8 Content of the paperbased mandate Name of the debtor Mandatory* Max. 70 characters 24 f. Country of debtor s address Optional Country code ISO 3166, Optional 25 DE for Germany Address of the debtor Optional Max. 140 characters Optional 25 More details on Page Identification DK not recommended Miscellaneous 30, 40 ff. IBAN of the debtor Mandatory Max. 34 characters Mandatory 26 ff., 37 f. Name of the different debtor. For information only. Optional Max. 70 characters Optional 24 f., 31, 39 Identification DK not recommended Miscellaneous 30, 39, 40 ff. Type of payment (text code). Not all codes are provided in account statement MT940/942.** Unstructured remittance information Structured remittance information Structured remittance information Part 2 Optional ISO ExternalPurposeCode- List 23 Recommended Max. 140 characters Optional 21, 39 (contract number and description) DK not recommended SCOR 22, 39 DK not recommended Max. 35 characters 22, 39 * If a direct debit mandate for a SEPA direct debit is generated at the POS/card terminal from card data, and the debtor s name is not available, the card data with the constant/cdgm (Card Data Generated Mandate) followed by /Card number/serial number/expiry date (YYMM) can be entered. The card number must be rounded up to 19 digits with zeros to the left. If the card number is unavailable, the PAN should be used. ** Please find further information in our brochures SEPA reporting and Business transaction and return codes, which you can obtain from your Cash Management & ebanking Specialist upon request.

21 SEPA usual payment information in the format Remittance information Unstructured remittance information <RmtInf><Ustrd> Only 140 characters are provided for the remittance information in SEPA. The still valid domestic payment transaction, on the other hand, permits in DTAUS German payment transfers up to characters (= 378 digits). In addition to the unstructured remittance information, however, a structured purpose <Purp> and specifics about the parties involved (address and identification numbers) as well as the End-to-End refence with 35 characters can be added in SEPA <RmtInf> <Ustrd> </Ustrd> </RmtInf> Structuring through code words defined by EACT in unstructured remittance information The ordering party may include references, e.g. invoice number of the transaction, in the remittance information, so that the beneficiary can easily allocate the incoming payment and clear open items. In order for this to take place automatically in the ideal case, the European Association of Corporate Treasurers (EACT, has defined code words and format rules. The complete list of code words and format rules can be seen on the EACT website at through the Working Group 8 (SEPA Documents). Examples of use in accordance with the EACT Standard: <RmtInf> <Ustrd>/RFB/ </Ustrd> </RmtInf> (RFB = Reference for Beneficiary) The payment transaction is related to the business transaction with the reference <RmtInf> <Ustrd>/RFS/RF </Ustrd> </RmtInf> (RFS = Reference secured with check digits) The payment transaction also refers to the business transaction with the reference , with the reference being indicated this time as a reference secured with check digits in accordance with ISO 11649, see also the sections on structured remittance information on the next page.

22 22 <RmtInf> <Ustrd> /CNR/876543/DOC/ /DOC/ / 54.67/ </Ustrd> </RmtInf> (CNR = Customer Number, DOC = Document reference) /CNR/876543/ indicates the customer number /DOC/ refers to the invoice number /DOC/ / 54.67/ is a so-called compound element containing additional data, separated by slash and space, in this case the invoice number dated 28/11/2014, with only the amount of being contained. Employee savings plans (VL benefits) In the case of employee savings plans (VL benefits), the XXJ/contract number is presented here, whereby XX is replaced either by 00 or by the percentage rate of the savings bonus, and the letter J represents the last figure of the benefit year. The name of the VL benefit recipient can be saved in the Ultimate Creditor data element, if required. CBFF can also be set as the Purpose Code. <Purp> <Cd>CBFF</Cd> </Purp> <RmtInf> <Ustrd>003/ABC123456</Ustrd> </RmtInf> Structured RemittanceInformation <RmtInf> <Strd> Structured creditor reference <CdtrRefInf> Forms with check digits adequate remittance information are also available for SEPA, just like they are in the form of BZÜ-receipts for domestic payments. In SEPA they are called creditor references in compliance with ISO 11649, starting with identifiers RF followed by 21 alpha-numerical digits. Modulus 97 is used to compute the creditor reference. In SEPA, structured remittance information are permitted only with code word SCOR If the check digit is not correct, the reference is transferred to an unstructured remittance information The structure is principally not provided in the paper-based and electronic account statement MT940; all it reflects is the content without tags, e. g. SCOR RF In the new camt.05x, the structure will be forwarded. <RmtInf> <Strd> <CdtrRefInf> <Tp> <CdOrPrtry> <Cd>SCOR</Cd> </CdOrPrtry> </Tp> <Ref>RF </Ref> </CdtrRefInf> </Strd> </RmtInf>

23 Purpose code <CdtTrfTxInf> The structured payment purpose information for each payment, <Purp> e. g. donation or salary, is reflected by the purpose code in SEPA. <Cd>PENS</Cd> </Purp> The purpose code is principally sent to the recipient bank and its end recipient </CdtTrfTxInf> It may result in different business transaction codes (BTC) in the electronic account statement* The payment purposes are listed in under tab 11-Purpose Purpose code statement Definition Special BTC at the electronic statement of accounts* ADVA Advance payment AGRT Agriculture AIRB Air transportation ALMY Alimony and support BECH Benefits for children BENE Unemployment benefits BTC Credit 156 BLDM Building maintenance BONU Bonus payment BTC Credit 153 BUSB Bus transportation CASH Cash management CBFF Savings benefits BTC Credit 154 CBTV Cable television CDBL Credit card billing statement CDCB Card payment POS cashback BTC Credit 198, Debit 106 CDCD ATM cash withdrawal BTC Debit 106 CDCS ATM cash withdrawal with surcharging BTC Debit 106 CDDP Card payment POS maximum BTC Credit 198, Debit 106 authorisation CFEE Cancellation CGDD Card-generated direct debit BTC Debit 107 CHAR Charity donation BTC Debit 119, Credit 169 CLPR Car loan COMM Commission payment COST General costs CSLP Contributions to social security DCRD Debit card payment DNTS Dental services ELEC Electric bill ENRG Energy ESTX Estate tax ETUP E-purse top up BTC Debit 106 FOCL Fee collection e-purse BTC Debit 106 GASB Gas bill GDDS Goods purchases/sale GOVI Government insurance GOVT Payment to/from the government BTC Credit 156 GWLT Injured war veterans benefits HLTC Healthcare services HLTI Health insurance HSPC Hospitalization Purpose code statement Definition Special BTC at the electronic statement of accounts* IDCP Card payment POS BTC Credit 198, Debit 106 INPC Automotive insurance INSM Instalment payment plan INSU Insurance INTC Intra-company transfer INTE Interest INTX Income tax LBRI Professional liability insurance LICF Licensing fees LIFI Life insurance LOAN Loan payment MDCS Medical services MTUP Mobile top up BTC Debit 106 NWCM Network communications PAYR Payroll disbursement BTC Credit 153 PENS Pension and retirement benefits BTC Credit 153 disbursement PHON Telephone PPTI Property/home owner s insurance RINP Recurring transfer order / Standing BTC Credit 152 order RLWY Railway transportation SALA Salary disbursement BTC Credit 153 SAVG Savings payment SCVE General services SSBE Social security benefits BTC Credit 156 STDY Studies and education SUPP Supplier payment TAXS Tax payment TELI According to telephone order TRAD Trade transaction VATX Value added tax WEBI According to online order placed WTER Water * Please find further information in our brochures SEPA reporting and Business transaction and return codes, which you can obtain from your Cash Management & ebanking Specialist upon request.

24 Category purpose The category purpose is an instruction the submitter gives to the paying bank The orders/files are subject to special processing, e. g. subject to prioritization or special terms The above applies to a file or each payment The information is not transferred to the receiving bank A bilateral usage agreement with the bank is required Currently, UniCredit only uses SALA (same day salary payments) on the file level. Additional product information can also be found in our special flyer Credit Transfer Preferred. Card payments in SEPA Cards Clearing are identified by the category purpose IDCP (guaranteed card payment) or CBLK (card bulk clearing) or FCOL (fee collection). <PmtInfId> <PmtTpInf> <CtgyPurp> <Cd>SALA</Cd> </CtgyPurp> </PmtTpInf> </PmtInfId> The five parties to a SEPA message The presenter and the recipient appear on different levels of a SEPA order or file submission. Fields Ultimate can be used to enter an additional different presenter and payment recipient. Example of a SEPA Credit Transfer GroupHeader InitiatingParty (submitter) PaymentInformation bulk level Debtor IBAN/BIC (debtor) UltimateDebtor Name (70 digits) Address (country code plus 2 70 digits)* Organisation identification Person identification Transaction Creditor IBAN/BIC (beneficiary/recipient) Required information Optional UltimateCreditor *The provision of an address for the initiating party and for the Ultimates is not possible

25 25 Example of a SEPA Direct Debit GroupHeader Initiating Party (submitter) PaymentInformation bulk level Creditor Creditor identifer (creditor) IBAN/BIC (creditor) Name (70 digits) Address (country code plus 2 70 digits)* Organisation number** Person identification number** UltimateCreditor Transaction Debtor Required information Optional IBAN/BIC (debtor) UltimateDebtor * Address for the initiating party and for the Ultimates not possible ** OrgId & PrvtId not possible for the creditor Name, address Five possible parties are involved in a SEPA message (debtor, creditor, initiating party, ultimate creditor and ultimate debtor) The respective party name <Nm> is always provided using up to 70 characters As an option, it is also possible to provide addresses <PstlAdr>. The country code <Ctry> plus two times 70 characters from the unstructured address <AdrLine> must be used. The name of the presenter and the address (for border-crossing payments) must be provided correctly pursuant to the Regulation EC 1781/2006. UniCredit completes same automatically, using the master account data <Nm>ABC Handels GmbH</Nm> <PstlAdr> <Ctry>DE</Ctry> <AdrLine>Dorfstrasse 14</AdrLine> <AdrLine>Muenchen</AdrLine> </PstlAdr>

26 IBAN, IBAN-Only The International Bank Account Number IBAN is the definitive identification criteria for beneficiaries and debtors of payments. In the SEPA payment zone, the IBAN will completely supersede the domestic account number for SEPA orders. <Id> <IBAN>DE </IBAN> </Id> Its structure is defined by ISO :2007. The IBAN begins with two letters, which identify the country. Two check digits follow. These two check digits are calculated pursuant to ISO 7064 in modulus across the entire IBAN. The next numbers identify a bank/account. Depending on the country, this bank/account identification has a different structure and a distinct number of digits. Consequently, the IBAN may span 15 to 31 digits and may not only contain the numeric values, but also alphanumerical values besides the country code. In Germany, the first 8 digits after the two check digits reflect the bank code (German Bankleitzahl), while the following 10 digits identify the numeric account number, so that the total length of the German IBAN is 22 digits. Many banks have the capability to verify the correctness of the account number based on the last digit of the account number. Many banks use this final digit as a check digit. The required calculation modulus each individual bank requires can be determined from the Routing Code Directory of the German Federal Bank based on the bank code. Bank routing code: 8 digits DE: Germany DE Check digits: 2 digits Account number: 10 digits A simple determination of the check digits based on the bank code and account number does frequently result in the misrouting of payments in Germany, since the following special circumstances have to be taken into account: Some banking institutions fail to complete the IBAN account number field with zeros from left to right if the account number has less than 10 digits, but insert the zeros after the account number In particular after consolidations and mergers of bank branches, numerous customers continue to use their old bank codes, although they have already been provided with a new bank code along with their IBAN For this reason, an IBAN calculation should always be conducted by the bank that manages the account, or in Germany by the German company Bank-Verlag, or by processes that take specific institutional particularities into account as published by the Bundesbank. Examples of specific institutional particularities when calculating the IBAN The IBAN calculation converts charity and pseudo accounts into genuine account numbers, e. g.: Bank code and account is converted in IBAN into account , in other words DE Accounts are filled up with zeros to 10 digits at the rear instead of at the front, e. g.: Bank code and account becomes IBAN DE The bank code is exchanged, e. g.: Bank code and account is converted in IBAN into account DE