20.5.2014 SEPA SK Country Guide en New 16012014-New

1

SEPA COUNTRY SPECIFIC INFORMATION SLOVAKIA Cash Management & eBanking

The aim of the Single Euro Payments Area (SEPA) project is to unify the rules and standards of Euro payments (credit transfers and direct debits). The principal objective of SEPA is practically to abolish the borders for Euro payments. Within SEPA the consumers, corporates and other economic entities will be able to send and receive Euro payments within one country, or among the respective countries under the same conditions, rights and duties without regard to the country, in which they have their accounts opened.

This document provides an overview of all country specific information you need in order to successfully overcome the challenges of SEPA and achieve a seamless migration. Being fully informed and properly equipped with the necessary tools, you will be able to fully realize the potential all new SEPA instruments will bring. Basic information about SEPA in Slovakia you can find on the website of the National Bank of Slovakia http://www.nbs.sk/sk/platobne-systemy/sepa

END-DATE INFORMATION SEPA has become a regulatory project, the mandatory end-date was agreed for 1st of February 2014. The main technical and business requests for SEPA credit transfers and SEPA Direct Debit according to the Regulation (EU) no. 260/2012:

Communication between banks and SIPS (Slovak Interbank Payment System) in local formats via SEPA convertor: Till: 31st of January 2014

Communication between banks and SIPS only in ISO 20022 XML formats Since: 1st of February 2014

Communication between customers and banks in ISO 20022 XML format with exceptions* Since: 1st of February 2014 - till 31st of January 2016

Communication between customers and banks in ISO 20022 XML format without exceptions* Since: 1st of February 2016

BIC as an optional data for customers Since: 1st of February 2014 - for domestic transactions Since: 1st of February 2016 - for cross-border transactions

Niche products: there are no niche products in Slovakia

Conversion services for consumers (customers can send orders to the bank in currently used formats and bank will convert them to the xml format): Till: 31st of January 2016

*Exceptions:

a) for using the IBAN. The customer will keep using the account number in the form of the BBAN (Basic Bank Account Number) and the bank will convert it to the IBAN (International Bank Account Number).

b) for using XML messaging formats . The corporates will be allowed to use the existing formats. During the transition period the bank will support the existing formats extended by the mandatory fields of SEPA standard.

IBAN CONVERSION SERVICE

conversion tools offered by UniCredit Bank Slovakia a.s. UniCredit Bank Slovakia a.s. has developed a proprietary conversion service - an IBAN to-and-from method - able to determine and update IBAN and BIC for the accounts held with us.

2

IBAN structure In Slovakia, the IBAN is composed of 24 characters, structured as follows:

o Positions 1 to 2: ISO country code (SK for Slovakia) o Positions 3 to 4: check digits o Positions 5 to 8: bank identifier (bank code e.g. 1111 in case of UniCredit Bank Slovakia a.s.) o Characters 9 to 24: account number*

maximum 6 digits for a prefix maximum 10 digits for a main account number

* please note that some Slovak account numbers can have less digits than maximum; in this case '0' should be added on the left side in order to

reach the 16 characters (e.g. the account number with the prefix 0000190000123123; the account number without prefix 0000001234567890)

SEPA PRODUCTS

Domestic products domestic EUR credit transfers will have to be migrated to SEPA Credit Transfers (SCT) domestic direct debits will have to be migrated to SEPA Direct Debits - SDD Core or SDD B2B

COMPARISON - Credit Transfer in local format vs. SEPA Credit Transfer

Credit Transfer in local format

SEPA Credit Transfer

Coverage area only for domestic payments For domestic payments and cross-border payments within SEPA countries

IBAN / BIC BBAN and National Bank Code of beneficiary required IBAN / BIC* of beneficiary required

Transactions Interbank transactions in EUR currency only; creditor account in SK bank only

SHA fees only, EUR currency only, creditor account in SEPA banks;

Execution date

Debit: at execution date, Credit: intra-bank: D+0** standard payments to other banks: D+1** urgent payments to other bank D+0**

u

Debit: at execution date, Credit: intra-bank: D+0** EEA standard paymentsD+1** urgent payments D+0** Outside of EEA, paper based payments Standard value date D+2** urgent D+1**

Payment identification

Variable symbol, specific symbol, constant symbol End To End Reference

* BIC mandatory for domestic payments till 1st of February 2014 and for cross-border payments till 1st of February 2016; **working days

COMPARISON - Direct Debits in local format vs. SEPA Direct Debits

SDD is a new standard for receivables collection, for EUR payments only, characterized by two different schemes : CORE and B2B, from the 1st of February 2014 which the bank will accept also for local payments. The process is based on a mandate signed by the debtor/payer and presented to the creditor/payee. The mandate content is standardized and must be issued in the local language of the debtor. SDD service will be specially contracted, i.e. only the payee with whom the bank will make an agreement, will be able to use it.

3

While designing your migration approach, make sure you understand the related impact, as also summarized below:

Criteria Direct Debit in local format SDD Core SDD B2B

Allowance of SDD collection

local format does not contain all necessary data to allow SDD

yes

Region only domestic (SK) domestic and cross border domestic and cross border

Format Local KV format ISO 20022 XML ISO 20022 XML

Sequence Type N/A first / recurrent / one-off first / recurrent / one-off

Eligible debtor consumer and non-consumer consumer and non-consumer non-consumer only

Submission** and due date paid after acceptance

of collection request

by the debtor bank

D-5 (first / one-off)

D-2 (recurrent)

D-1 (all)

Mandate management

Debit mandate flow

mandate kept by the debtor bank

mandate kept by the creditor

mandate kept by the creditor and by the debtor bank

Refunds

no refund is possible for an authorized DD - it is irrevocable 13 months for an unauthorized

transaction

unconditional refund right within 8 weeks, following the date of

debit; 13 months for an unauthorized transaction

no refund possible

Mandate checking

Mandate checking is mandatory for the debtor bank;

Mandate contains a maximum collection limit also

Mandate will be stored and has to be checked by debtor's bank in

case of conditionally protected client account

mandate must be stored at debtor's bank before the first collection and checked by debtor

bank with every debit entry

Pre-notification N/A 14 days before due date 14 days before due date

SEPA CREDITOR IDENTIFIER (CID)

CID for Slovakia is structured as follows: o Positions 1 to 2: ISO country code (SK for Slovakia) o Positions 3 to 4: check digits o Positions 5 to 7: Creditor Business Code (to be assigned by creditor, by default 'ZZZ') o Characters 8 to 18: Creditor National Identifier for the creditor, numbered in consecutive ascending order; beginning

with digit 7 from the left side (e.g. 70000000025)

How to get a Creditor Identifier?

The creditors are registered with a standardized, unique and harmonizes identification number CID (Creditor Identifier). CID is a prerequisite of SEPA Direct Debit.

The payee shall ask his bank for the CID, any of the several, and he can use for the direct debit only one CID regardless of the bank and the account, from which the direct debit is effected. The list of the CID is managed by the National Bank of Slovakia.

4

MANDATE INFORMATION

Mandate Migration

Based on the Regulation (EU) no. 260/2012 a continuity clause for existing mandates has been enabled:

the existent mandates, given by debtors to their banks until the 1st of February 14 remain valid for SDD Core for SDD B2B will always be required the signature of a new mandate

Migration rules:

Since the 1st of February 2014 the banks will implement the protection of the payer accounts in accordance with SEPA standards as follows: Accounts fully open to any direct debit or Conditionally protected accounts, i.e. the accounts open to the direct debit, which the payer agreed with in advance or the accounts closed to any direct debits. In Slovakia the banks will migrate all payer accounts as conditionally protected accounts on the 1st of February 2014.

COUNTRY SPECIFIC FORMATS are based on local KV format which is used by all domestic banks.

Overview of Products related to Domestic Formats

Direct debits in Slovakia are largely used as payment collection instruments and are generally processed in local KV format. The same file format is used for domestic credit transfers.

Type Description End date Target Product and Specifics /

Formats

HD:32 and HD:12 / local KV format via SIPS

Used for request for collection and direct debit

31st of January 2014 SDD CORE and SDD B2B /XML

HD:11 / local KV format via SIPS used for domestic credit transfers 31st of January 2014 SCT /XML

SWIFT MT103 - to TARGET2 used for urgent payments no end date has been defined

so far MT103 - to TARGET2

XML related Payment Initiation, Booking Information and account statements

XML urgent

pain.001 pain.001 pain.002 pain.008 camt.052 camt.053 camt.054 camt.086

Availability at Unicredit Bank SK yes yes no yes yes yes no no

REMITTANCE INFORMATION

Unstructured remittance information (140 characters) is recommended. E2E reference is conventionally used for reconciliation purposes in SK.

5

CHANNELS FOR SEPA PAYMENT INITIATION

SEPA Credit transfer SEPA Direct Debit CORE /B2B Other transfers in XML format MultiCash Yes Yes No Business Net Professional Yes Yes Yes EuropeanGate Yes No Yes Paper based Yes No Yes

CUT-OFF-TIMES

SEPA Credit Transfer SDD Core SDD B2B

COT * 21:30 CET

08:00 CET 08:00 CET

Presentation day * same day D-6 / D-3 / D-2 first / one-off / recurrent D-2

*under discussion

There is no multilateral interchange fee (MIF) per item in Slovakia.

ADDITIONAL OPTIONAL SERVICES Migration of symbols to the E2E reference

If customers want to use for payment identification the variable, specific and constant symbols also in the new XML formats, they will have to use the following Slovak convention /VS[N10]/SS[N10]/KS[N4] and enter these data into the E2E reference, while

o /VS[N10] is a variable symbol consisting of ten digits o /SS[N10] is a specific symbol consisting of ten digits o /KS[N4] - is a constant symbol consisting of four digits

The observance of this convention will ensure that also the customers, who will not convert to the XML standards since the 1st of February 2014, can keep reconciling the payments according to the currently used symbols.

VALUE ADDED SERVICES

UniCredit Bank Slovakia a.s. is also able to provide you with additional value-added service, such as:

The conversion of the BBAN to the IBAN the bank will convert it on request of customers. The customers shall give to the bank the BBANs in the .xls files and the bank will convert them to the IBANs.

SEPA Messages

UniCredit Bank Slovakia is supporting for customers these types of messages: o Pain.001 Customer Credit Transfer Initiation o Pain.008 - Customer Debit Initiation o Camt.052, Camt.053 - electronic account statements, Slovak national standard

http://www.iso20022.org/payments_messages.page http://www.europeanpaymentscouncil.eu/

6

Paper statement Statements for domestic SEPA transactions will be enhanced to contain maximum 6 lines. For SEPA credit transfers the structure of statement details will remain same as for current credit transfers with following changes:

1st line - symbols (variable, constant, specific) will be displayed on the statements in the same way as now, if they are available.

2nd line - counter party account numbers will be replaced by IBANs, counter party bank codes will be replaced by BIC codes

3rd line - if symbols are not available, E2E reference will appear in the 3rd line, unless it contains default value NOTPROVIDED, E2E reference will be followed by Payment Information ID

4th 6th line will be narrative containing following information Return/rejection reason text reference of original transaction being returned/rejected Remittance information

If the total length of statement information exceeds the space available for statement details, it will be truncated.

7

SEPA a elektronick bankovnctvo Unicredit Bank Czech Republic and Slovakia supports in all electronic banking channels Sepa Credit Transfers (SCT) and Sepa Direct Debits (SDD) payment orders Bank still supports all existing formats of input formats in electronic banking systems toll February 1, 2016. Decision for change of existing electronic banking format to xml format is on the customer. We suggest to our customers always ask bank for testing procedure before such change and after confirmation from bank side that new format is acceptable, to provide such change. Description of xml formats you can find directly in this document for each electronic banking channel. After suggested test process of input xml file customer can start use it after February 1, 2014. It is important to implement the special input format for concrete electronic banking channel, details you can find in the format decryption for concrete electronic banking channel. In case that customer would like to receive from February 1, 2014, account statement camt.053 (xml format), customer has to ask bank for such service via his responsible relationship manager. Bank suggest to have parallel delivery of existing format of account statement and camt.053 and only based on non-problem reconciliation process based on camt.053 ask bank for cancelation of delivery of old account statement format. The decision can be taken individually by each customer, so Bank offer to its customer enough time for testing period and adoption of ERP systems to new xml format.

8

MultiCash In case customer would like to send to the Bank from February 1, 2014 Sepa Credit Transfers and Sepa Direct Debits (SCT and SDD), it is necessary, that customer have to ask the Bank via responsible relationship manager for installation of SEPA module into Multicash customer application. Installation of SEPA module will be charged according valid Tariff if charges for Corporate customers. In case customer has SEPA module from other bank we suggest to contact our bank to clarify, that version of SEPA module installed in his application is compatible and able to communicate without problems with our server MultiCash version. Customer can contact our Bnak either via responsible relationship manager, or send email to email address [email protected] or call +421 905 455 883, +421 905 470 999. Bank supports following version on server MultiCash side and SEPA module on customer side for non-problem communication: Version MultiCash server bank use from 01.02.2014 version 3.23.003 SP7

9

Version of Multicash customer application in case customer would like to send SCT and SDD via Multicash to Bank, latest before February 1, 2014 SEPA Modul 3.20.030 SP2 has to be installed on his Multicash application. Description of input format for MultiCash: SEPA Credit Transfer english language The file is located in the attachment of this PDF document. SEPA Direct Debit english language The file is located in the attachment of this PDF document.

MultiCash - SEPA Credit Transfer import format description_aj.doc

MultiCash - SEPA Credit Direct Debit import format description.doc

10

SEPA Credit Transfer example

The file is located in the attachment of this PDF document. SEPA Direct Debit example

The file is located in the attachment of this PDF document. New information on MT 940 account statement from input xml file, necessary for reconciliation process Bank will delivered following structure of information: MT940 structured local standard For SEPA credit transfers the structure of statement details will remain same as for current credit transfers with following changes:

Remittance information will start in the subfield ?24 and will contain following information (if available) in following order :

E2E reference if E2E reference is NOTRPOVIDED, it will not appear on the statement Delimiter Payment Information ID Delimiter Return/rejection reason text reference of original transaction being returned/rejected Remittance information

If the space of the subfields ?26-?29 is not sufficient, information will continue in the subfields ?60 - ?63 MT940 unstructured For SEPA credit transfers the structure of statement details will remain same as for current credit transfers with following changes:

Counter party account numbers will be replaced by IBANs Counter party bank codes will be replaced by BIC codes Symbols (variable, constant, specific) will be displayed on the statements in the same way as now. If symbols

are not available, E2E reference will appear on the statements instead, unless it contains default value NOTPROVIDED. Pretext for E2E reference will be E2E:

Narrative fields will be replaced by remittance information containing following information (if available) delimited by //:

Payment Information ID Return/rejection reason text reference of original transaction being returned/rejected Remittance information

If the total length of statement information exceeds the space available for IZV statement details, it will be truncated. Account statement camt .053

11

IN case customer would like to receive electronic account statement in xml format-camt.053, he has to ask the Bank for delivery of this service via his responsible relationship manager. In case that customer would like to receive from February 1, 2014, account statement camt.053 (xml format), customer has to ask bank for such service via his responsible relationship manager. Bank suggest to have parallel delivery of existing format of account statement and camt.053 and only based on non-problem reconciliation process based on camt.053 ask bank for cancelation of delivery of old account statement format. The decision can be taken individually by each customer, so Bank offer to its customer enough time for testing period and adoption of ERP systems to new xml format. Bank will not apply special fee for delivery of both types of account statements in parallel. The camt account statements are generating according Slovak norm defined by SBA: Description of norm camt.03 according SBA:

anglXML_struktura_SK.xls

anglXML_standard_SK.doc

anglXML_vypis_transakcne_kody_SK.xls The files are located in the attachments of this PDF document.

12

BusinessNet Professional Bank allow to its customers to import from February 1, 2014, Sepa Credit Transfers (also for Domestic paymets ) and Sepa Direct Debits in xml format. In case of any further questions for these related questions for import payments in xml format and download account statement in xml format please contact your relationship manager. In case you need to delivery camt account statement camt.053 or send to us email to email address [email protected]. Description of input format for BusinessNet Professional : SEPA Credit Transfer english language The file is located in the attachment of this PDF document. SEPA Credit Transfer english language The file is located in the attachment of this PDF document. SEPA Credit Transfer example

The file is located in the attachment of this PDF document. SEPA Direct Debit example

The file is located in the attachment of this PDF document.

New information on MT 940 account statement from input xml file, necessary for reconciliation process Bank will delivered following structure of information: MT940 structured local standard For SEPA credit transfers the structure of statement details will remain same as for current credit transfers with following changes:

Remittance information will start in the subfield ?24 and will contain following information (if available) in following order :

E2E reference if E2E reference is NOTRPOVIDED, it will not appear on the statement

BusinessNet - SEPA Credit Transfer import format description.doc

BusinessNet - SEPA Direct Debit import format description.doc

13

Delimiter Payment Information ID Delimiter Return/rejection reason text reference of original transaction being returned/rejected Remittance information

If the space of the subfields ?26-?29 is not sufficient, information will continue in the subfields ?60 - ?63 MT940 unstructured For SEPA credit transfers the structure of statement details will remain same as for current credit transfers with following changes:

Counter party account numbers will be replaced by IBANs Counter party bank codes will be replaced by BIC codes Symbols (variable, constant, specific) will be displayed on the statements in the same way as now. If symbols

are not available, E2E reference will appear on the statements instead, unless it contains default value NOTPROVIDED. Pretext for E2E reference will be E2E:

Narrative fields will be replaced by remittance information containing following information (if available) delimited by //:

Payment Information ID Return/rejection reason text reference of original transaction being returned/rejected Remittance information

If the total length of statement information exceeds the space available for IZV statement details, it will be truncated. Account statement camt .053 IN case customer would like to receive electronic account statement in xml format-camt.053, he has to ask the Bank for delivery of this service via his responsible relationship manager. In case that customer would like to receive from February 1, 2014, account statement camt.053 (xml format), customer has to ask bank for such service via his responsible relationship manager. Bank suggest to have parallel delivery of existing format of account statement and camt.053 and only based on non-problem reconciliation process based on camt.053 ask bank for cancelation of delivery of old account statement format. The decision can be taken individually by each customer, so Bank offer to its customer enough time for testing period and adoption of ERP systems to new xml format. Bank will not apply special fee for delivery of both types of account statements in parallel. The camt account statements are generating according Slovak norm defined by SBA: Description of norm camt.03 according SBA:

anglXML_struktura_SK.xls anglXML_vypis_transakcne_kody_SK.xls

anglXML_standard_SK.doc The files are located in the attachment of this PDF document.

INTERNET BANKING OF UNICREDIT BANK CZECH REPUBLIC AND SLOVAKIA, A.S. BUSINESSNET BASIC BUSINESSNET PROFESSIONAL SEPA CREDIT TRANSFER IMPORT FORMAT DESCRIPTION December 2013

Contents: SEPA Credit Transfer Import format description

Introduction .................................................................................................................................................................. 3

SEPA Credit Transfer basic description ................................................................................................................. 4

Main features of SEPA Credit Transfer .................................................................................................................... 4

Advantages of SEPA Credit Transfer ........................................................................................................................ 5

How to import SEPA Credit Transfer into BusinessNet .......................................................................................... 5

Allowed character set ................................................................................................................................................... 6

Element occurrence ...................................................................................................................................................... 6

Structure of the ISO 20022 payment .......................................................................................................................... 6

General information ..................................................................................................................................................... 7

Implementation of the pain.001.001.03 for BusinessNet SEPA Credit transfer ................................................. 9

Root: ........................................................................................................................................................................... 9 Group Header ............................................................................................................................................................ 9 Payment Information ................................................................................................................................................ 10 Credit Transfer Transaction Information ................................................................................................................ 11

BusinessNet filling instructions ................................................................................................................................. 13

Organisation Identification elements ....................................................................................................................... 15 Person Identification elements ................................................................................................................................. 16

BusinessNet Import of a SEPA Credit Transfer XML Definition PAIN.001.001.03

Page 3

Introduction Dear Client, We are pleased you have decided to use BusinessNet, a modern electronic banking service designed specifically for corporate clients. Internet banking services will enable you to manage your financial flows simply, comfortably, securely and effectively for 24 hours a day, 7 days a week. This manual will guide you through SEPA Credit Transfer format description. If you have any questions, you can contact us on every business day from 7.00 to 18.00, our technical assistance is available at the telephone number Unitel 0800 14 00 14 , or you can send an e-mail to [email protected].

UniCredit Bank Czech Republic and Slovakia, a.s.


Page 4

SEPA Credit Transfer basic description A SEPA credit transfer is a euro-denominated noncash transfer of funds to a beneficiary (known as the creditor in the EPCs SEPA mandates) initiated by a payer (known as the debtor in EPC mandates) through a payment order submitted to a bank electronically. A SEPA credit transfer has precisely defined requirements and is executed within SEPA countries between banks that have acceded to the SEPA Credit Transfer Scheme. Since its launch on 28 January 2008, more than 4,480 banks from 32 countries have already joined. They represent more than 95% of payment transactions in SEPA countries.

Main features of SEPA Credit Transfer

Payment is in Euro.

The beneficiarys account number must be entered in IBAN format.

The beneficiarys bank is identified by the valid BIC code.

The beneficiarys bank has accepted the conditions for processing SEPA credit transfers.

Transparency of fees The shared-fees system (SHA=SLEV) is applied, meaning the beneficiary and payer pay the fees of their own banks.


Page 5

Advantages of SEPA Credit Transfer

Payment (without conversion) is always delivered to the beneficiary at the latest within 3 banking days. Once the PSD is transposed into national payment system law, payment delivery will be shortened to the following banking day.

The transfer amount is not limited.

The entire transferred amount is credited to the beneficiarys account; fees are paid separately.

Payment processing takes place under uniform, standardised conditions.

The payment format contains an additional field in which the payer may give additional information.

The new XML data format of payments allows more data to be transferred.

How to import SEPA Credit Transfer into BusinessNet

The user can upload the file into the BusinessNet by use of option Payments > Imports & Uploads > Start Import or by use of option Payments > Imports & Uploads > Start Upload. When using these options, the user must first choose the type of order Sepa Payment and then item SEPA Pain001 (XML) in the field File Structure in order to upload the file corresponding to this description. Find detailed user instruction concerning the upload of the transaction file in the application Help which you can open by clicking on a question mark in the right upper corner.

File extension which the file name may include:

The file containing SEPA Credit Transfer payment orders may include only *.xml extension. Max. length of file name (incl. possible file extension) is 64 characters.


Page 6

Allowed character set Please note that within the fields of the XML only the following characters are allowed to use:

Permitted Character Code Character Hex Code numeric characters 0 to 9 X'30' -X'39' capital characters A to Z X'41' -X'5A' small characters a to z X'61' -'X'7A' apostrophe ' X'27' colon ": X'3A' question mark "? X'3F' comma "," X'2C' minus "-" X'2D' blank character X'20' left bracket "(" X'28' plus sign "+" X'2B' period "." X'2E' right bracket ")" X'29' slash "/" X'2F'

Element occurrence Element occurrence is defined by the following parameters:

Min. occurrence : Max. occurrence 0 = optional : 1 = once

1 = mandatory : 2 = twice : n = unbounded

Structure of the ISO 20022 payment

It is important to understand that some of the information within these Pain messages apply to the whole message, to a certain bulk or to a single transaction, depending on the information level.


Page 7

General information Group Header Within the Group Header (Tag ) all information related to the whole file are to be found. The most important ones are:

Message Identification , mandatory (1:1): This Id is used to identify the message and should be unique to the submitter of the message for a predefined period of time. It is a point-to-point reference between the instructing party and the next party in the chain.

Creation Date Time , mandatory (1:1): Date and time at which the message was created.

Number of Transactions , mandatory (1:1): Number of all transactions contained within this message / file.

Control Sum , optional (0:1): Contains the sum of all instructed amounts of all transactions within this message regardless of the currency of the single transaction.

Initiating Party , mandatory (1:1): Party that initiates the payment, e.g. a service bureau or a dedicated payment factory. Does not need to be the account holder and is not forwarded in the payments process.

There are some more fields which may be used by the instructing party. For further details please refer to the ISO 20022 maintenance guide, available at www.iso20022.org. Payment Information Within the Payment Information (Tag ) typically a bulk of payments is stated. One Pain.001.001.03 messages may contain an unbounded number of blocks but does have to have at least one occurrence (1:n). Each PmtInf is dedicated to one account and one requested execution date. The most important tags to be used by the instructing party are:

Payment Information Identification , mandatory (1:1): Used to identify a specific bulk within the file when being processed.

Payment Method , mandatory (1:1): Used to further specify the type of the transaction. BusinessNet only accept Credit Transfers, code TRF.

Payment Type Information , optional (1:1): Is a set of elements that is used to further specify the type of payments in this respective PmtInf block.

o Instruction Priority , optional (0:1): - to be supported at the earliest in 2014

o Service Level , mandatory (1:1): Agreement under which the instructions should be processed, as defined in the "ExternalServiceLevel1Code" (www.iso20022.org). Banking service BusinessNet support only SEPA code.

Requested Execution Date , mandatory (1:1): Specifies the day when the transaction shall be executed by the instructed party (the date when the debtor's account has to be debited). In case this is not a working day the instructed party shall process the instruction on the next possible day.

Debtor , mandatory (1:1): Party that owes an amount of money to the creditor, usually account holder. There are certain elements to further specify the debtor, e.g. Id fields etc.


Page 8

Debtor Account , mandatory (1:1): Element group that provides the account that has to be debited with the instructed amount. Account must be provided as an IBAN.

Debtor Agent , mandatory (1:1): Element group that specifies the account holding institution as a BIC identification.

Charge Bearer , optional (0:1): Used to indicate which party/parties will bear the charges associated with the processing of the transactions. Only SLEV is allowed.

Credit Transfer Transaction Information The Credit Transfer Transaction Information describes the individual transactions within a PmtInf block. Theoretically the number of occurrences is unbounded (1:n), but due to some technical issues the receiving institution may limit the number of occurrences per PmtInf block. It is recommended import max 99.999 occurences.

The important information within the CdtTrfTxInf are:

Payment Identification , mandatory (1:1): Element group that uniquely identifies the individual transaction. May contain a Instruction Identification (0:1) which is a point-to-point reference and must contain a End To End Identification (1:1) which is transported without any amendments throughout the whole processing cycle.

Amount , mandatory (1:1): Element group that specifies the instructed amount. Must be provided as an amount with currency EUR.

Creditor Agent , mandatory (1:1): Used to specify the beneficiary's account holding institution. Must consist of a BIC.

Creditor , mandatory (1:1): Specifies the beneficiary (e.g. Name, address, organisation or private identification etc.).

Creditor Account , mandatory (1:1): Used to specify the creditor's account with the account holding institution. Creditors account must be filled in in IBAN format.

Remittance Information , optional (0:1): Group of elements used to describe the payment for the beneficiary more in detail. Please refer to www.iso20022.org for a detailed description of the various elements within the RmtInf. We recommend to use it with unstructured format.


Page 9

Implementation of the pain.001.001.03 for BusinessNet SEPA Credit transfer

Root:

Group Header The Group Header consists of the following elements:

Element name Occurrence Format Comments MsgId 1:1 Max35Text Unique message

identification CreDtTm 1:1 ISODateTime Timestamp when the message

had been created Authstn 0:2 Complex element

Authorisation1Choice Not supported

NbOfTxs 1:1 Max15NumericText Number of all individual transactions within this message/file

CtrlSum 0:1 DecimalNumber Sum of all instructed amounts in this message, irrespective of the currencies

InitgPty 1:1 Complex element PartyIdentification32

Party that created the message, at least the name has to be provided. In general we recommend not to use other elements than the name except where necessary due to local practices

FwdgAgt 0:1 Complex element BranchAndFinancialInstitution Identification4

Not supported


Page 10

Payment Information

The Payment Information may be repeated unbounded, but has to be present at least once. BusinessNet does support the usage of the following elements:

Element name Occurrence Format Comments PmtInfId 1:1 Max35Text Used to identify a specific bulk within the file

when being processed. PmtMtd 1:1 PaymentMethod3Code Only usage of TRF is allowed. PmtTpInf 1:1 Complex element

PaymentTypeInformation19 Service Level SEPA to be defined in this area.

ReqdExctnDt 1:1 ISODate Booking day when the instructed institution shall debit the customers account.

Dbtr 1:1 Complex element PartyIdentification32

Party that owes an amount of money to the creditor. There are certain elements to further specify the debtor, e.g. ID fields etc.

DbtrAcct 1:1 Complex element CashAccount16

Account that will be debited with the transactions amount. IBAN requested.

DbtrAgt 1:1 Complex element BranchAndFinancialInstitution Identification4

Debtors financial institution. BIC requested.

CdtTrfTxInf 1:n Complex element CreditTransferTransaction Information10

Set of elements used to provide information on the individual transaction(s) included in the message.


Page 11

Credit Transfer Transaction Information

The CreditTransferTransactionInformation block must be present at least once, and can be repeated unlimited. All single transaction information are specified within this block, that is beneficiary's data, instructed amount and currency and so on.

Element name Occurrence Format Comments PmtId 1:1 Complex element

PaymentIdentification1 Used to uniquely identify the single transaction

PmtTpInf 0:1 Complex element PaymentTypeInformation

To be defined in PmtInf level

Amt 1:1 Complex element AmountType3Choice

Instructed amount, only in EUR currency

XchgRateInf 0:1 Complex element ExchangeRateInformation1

Not supported

ChrgBr 0:1 ChargeBearerTypel Code Only SLEV code is allowed ChqInstr 0:1 Complex element

Cheque6 Not supported

UltmtDbtr 0:1 Complex element PartyIdentification32

Not supported

IntrmyAgt1 0:1 Complex element BranchAndFinancial InstitutionIdentification4

Not supported

IntrmyAgt1Acct 0:1 Complex element CashAccount16

Not supported


Page 12

Element name Occurrence Format Comments IntrymAgt2 0:1 Complex element

BranchAndFinancial InstitutionIdentification4

Not supported


Not supported

IntrymAgt3 0:1 Complex element BranchAndFinancial InstitutionIdentification4

Not supported


Not supported

CdtrAgt 1:1 Complex element BranchAndFinancial InstitutionIdentification4

BIC requested for SEPA

CdtrAgtAcct 0:1 Complex element CashAccount16

Not supported

Cdtr 1:1 Complex element Specifies the beneficiary CdtrAcct 1:1 Complex element

CashAccount16 Specifies the beneficiary's account as IBAN identification.

UltmtCdtr 0:1 Complex element PartyIdentification32

Not supported

InstrForCdtrAgt 0:n Complex element InstructionForCreditor Agent1

Not supported

InstrForDbtrAgt 0:1 Max140Text Special instruction for bank It is possible to use this field for entry of code words significant for the processing of a payment order. Their list, meaning and way of their entering is described in the foreign payments manual for electronic banking (topical version of the manual is available for downloading on a product page of the BusinessNet application - www.unicreditbank.cz/businessnet). If this optional element is filled in incorrectly, the payment will be executed as NON-STP.

Purp 0:1 Complex element Purpose2Choice

Not supported

RgltryRptg 0:10 Complex element RegulatoryReporting3

Not supported

Tax 0:1 Complex element TaxInformation3

Not supported

RltRmtInf 0:10 Complex element RemittanceLocation2

Not supported

RmtInf 0:1 Complex element RemittanceInformation5

Used to provide the beneficiary with additional information related to the specific instruction. It is recommend to use it with unstructured format.


Page 13

BusinessNet filling instructions Element name Occurrence Format Comments PmtInf 1:1 Complex element

PaymentInstructionInformation3 Payment information

PmtInfId 1:1 Max35Text Used to identify a specific bulk within the file when being processed.

PmtMtd 1:1 PaymentMethod3Code Only usage of TRF is allowed PmtTpInf 1:1 Complex element

PaymentTypeInformation19 Used to provide further instructions for all payments within this bulk. Service level SEPA to be defined in this area.

InstrPrty 0:1 Priority2Code To be supported at the earliest in 2014 SvcLvl 1:1 Complex Element

ServiceLevel8Choice Mandatory for SEPA

Cd 1:1 ExternalServiceLevel1Code Only SEPA code is allowed ReqdExctnDt 1:1 ISODate Date

Booking day when the instructed institution shall debit the customer's account, up to max. 90 days in the future

Dbtr 1:1 Complex element PartyIdentification32

Account holder details

Nm 1:1 Max140Text Debtor name must be provided, only first 35 characters shall be used

PstlAdr 0:1 Complex element PostalAddress6

Used to provide address details of account holder

Ctry 0:1 Country Code Used to provide country of residence of the account holder

Adrline 0:7 Max70Text Used to provide Street and Town of account holder

Id 0:1 Complex element Party6Choice

Debtor ID Unique and unambiguous way of identifying an organisation or an individual person. If Id element is used, than OrgId or PrvtId must be also used.

OrgId 0:1 or 1:1 Complex element OrganisationIdentification4

Organisation Unique and unambiguous way of identifying an organisation. This message item is composed of the various Organisation Identification elements (for details please see table Organisation identifications details). If OrgId element is used, than also one of complex element from table Organisation identification details must be also used.

PrvtId 0:1 or 1:1 Complex element PersonIdentification5

Private Unique and unambiguous identification of a person, eg, passport. This message item is composed of the various Person Identification elements (for details please see table Private identifications details). If PrvtId element is used, than also one of complex element from table Private identification details must be also used.

DbtrAcct 1:1 Complex element CashAccount16

Payer account

Id 1:1 Complex element AccountIdentification4Choice

Specifies the account details

IBAN 1:1 IBAN2007Identifier Only usage of IBAN is allowed DbtrAgt 1:1 Complex element

BranchAndFinancialInstitution Identification4

Debtor's agent

FinInstnId 1:1 Complex element FinancialInstitutionIdentification7

Specifies the agent's details

BIC 1:1 BICIdentifier Must be provided, only usage of BIC is allowed (BACXCZPP)

CdtTrfTxInf 1:n Complex element CreditTransferTransactionInformation10

Contains the single payment instructions

PmtId 1:1 Complex element PaymentIdentification1

Used to uniquely identify the single payment

InstrId 0:1 Max35Text Instructing party's reference EndToEndId 1:1 Max35Text End-to-End Ref.

Transaction reference


Page 14

Element name Occurrence Format Comments Amt 1:1 Complex element

AmountType3Choice Contains the instructed amount

InstdAmt 1:1 ActiveOrHistoricCurrencyCode Currency and Amount Instructed amount, only currency "EUR" is allowed. This data type must be used with the following XML Attribute: Currency (CCy) which is typed by ActiveOrHistoricCurrency Code.

CdtrAgt 1:1 Complex element BranchAndFinancialInstitution Identification4

Used to specify the creditor's account holding bank


Specifies the creditor bank's details

BIC 1:1 BICIdentifier SWIFT / BIC BIC identifier must be provided

Cdtr 1:1 Complex element PartyIdentification32

Used to provide beneficiary's details

Nm 1:1 Max140Text Payee Creditor name must be provided, only first 70 characters shall be used


Address Used to provide address details of beneficiary

Ctry 0:1 CountryCode Resident of Used to provide country of residence of the account holder

AdrLine 0:7 Max70Text Used to provide Street and Town of account holder. - Max. accepted occurrence is 0:3 more than 3 occurrence will be not transferred into the bank system - Max. count of characters in this three occurrences (together) is 105 characters (3x 35 char.) - rest of characters will be not transferred into the bank system

Id 0:1 Complex element Party6Choice

Creditor ID Unique and unambiguous way of identifying an organisation or an individual person. If Id element is used, than OrgId or PrvtId must be also used.

OrgId 0:1 or 1:1 Complex element OrganisationIdentification4

Organisation Unique and unambiguous way of identifying an organisation. This message item is composed of the various Organisation Identification elements (for details please see table Organisation identifications details). If OrgId element is used, than also one of complex element from table Organisation identification details must be also used.

PrvtId 0:1 or 1:1 Complex element PersonIdentification5

Private Unique and unambiguous identification of a person, eg, passport. This message item is composed of the various PersonIdentification elements (for details please see table Private identifications details). If PrvtId element is used, than also one of complex element from table Private identification details must be also used.

CdtrAcct 1:1 Complex element CashAccount16

Used to specify the creditor's account


Detailed account information, provided as IBAN account identification

IBAN 1:1 IBAN2007Identifier For SEPA Credit Transfer is providing of IBAN mandatory

RmtInf 0:1 Complex element RemmitanceInformation5

Remmitance Information Either Ustrd or Strd may be used, but not both of them. We propose to use Ustrd

Ustrd 0:1 Max140Text Used to provide further information useful for the recipient.

Strd 0:1 Complex element StructuredRemittanceInformation7

Not to be used


Page 15

Organisation Identification elements Element name Occurrence Format Comments BICOrBEI 0:1 Complex element

AnyBICIdentifier (8 or 11 characters) BIC (Bank Identifier Code) Bank Identifier Code. Code allocated to financial institutions by the Registration Authority, under an international identification scheme, as described in the latest version of the standard ISO 9362 Banking (Banking telecommunication messages, Bank Identifier Codes).

Othr 0:1 Complex element GenericOrganisationIdentification1

Unique identification of an organisation, as assigned by an institution, using an identification scheme.

Id 1:1 Max35Text Customer No. Number assigned by an issuer to identify a customer. Number assigned by a party to identify a creditor or debtor relationship.

SchmeNm 1:1 OrganisationIdentificationSchemeName1Choice

Name of identification scheme.

Cd 1:1 ExternalOrganisationIdentification1Code Value CUST must be filled in. Othr 0:1 Complex element

GenericOrganisationIdentification1 Unique identification of an organisation, as assigned by an institution, using an identification scheme.

Id 1:1 Max35Text (GS1GLN Identifier (13 characters))

EANGLN/GS1GLN (Global Location Number) Global Location Number. A non-significant reference number used to identify legal entities, functional entities, or physical entities according to GS1 numbering scheme rules.The number is used to retrieve detailed information that is linked to it.



Cd 1:1 ExternalOrganisationIdentification1Code Value GS1G must be filled in.

Othr 0:1 Complex element GenericOrganisationIdentification1

Unique identification of an organisation, as assigned by an institution, using an identification scheme.

Id 1:1 Max35Text Employer Identification No. Number assigned by a registration authority to an employer.



Cd 1:1 ExternalOrganisationIdentification1Code Value EMPL must be filled in. Othr 0:1 Complex element


Id 1:1 Max35Text (DUNS Identifier (9 characters))

DUNS (Data Universal Numbering System) Data Universal Numbering System. A unique identification number provided by Dun & Bradstreet to identify an organization.



Cd 1:1 ExternalOrganisationIdentification1Code Value DUNS must be filled in. Othr 0:1 Complex element


Id 1:1 Max35Text Bank party identification Unique and unambiguous assignment made by a specific bank to identify a relationship as defined between the bank and its client.



Cd 1:1 ExternalOrganisationIdentification1Code Value BANK must be filled in. Othr 0:1 Complex element


Id 1:1 Max35Text Tax Identification Number assigned by a tax authority to an entity.



Cd 1:1 ExternalOrganisationIdentification1Code Value TXID must be filled in. Othr 0:1 Complex element

GenericOrganisationIdentification1 Proprietary Identification Unique identification of an organisation, as assigned by an institution, using an identification scheme.

Id 1:1 Max35Text Identification Unique and unambiguous identifier for an organisation that is allocated by an institution.

Issr 0:1 Max35Text Issuer - Entity that assigns the identification.


Page 16

Person Identification elements Element name Occurrence Format Comments Othr 0:1 Complex element

GenericPersonIdentification1 Unique identification of a person, as assigned by an institution, using an identification scheme.

Id 1:1 Max35Text Drivers licence No. Number assigned by a license authority to a driver's license.

SchmeNm 1:1 PersonIdentificationSchemeName1Choice Name of the identification scheme. Cd 1:1 ExternalPersonIdentification1Code Value DRLC must be filled in. Othr 0:1 Complex element


Id 1:1 Max35Text Customer No. Number assigned by an agent to identify its customer.

SchmeNm 1:1 PersonIdentificationSchemeName1Choice Name of the identification scheme. Cd 1:1 ExternalPersonIdentification1Code Value CUST must be filled in. Othr 0:1 Complex element


Id 1:1 Max35Text Social Security No. Number assigned by a social security agency.

SchmeNm 1:1 PersonIdentificationSchemeName1Choice Name of the identification scheme. Cd 1:1 ExternalPersonIdentification1Code Value SOSE must be filled in. Othr 0:1 Complex element


Id 1:1 Max35Text Alien Security No. Number assigned by a government agency to identify foreign nationals.

SchmeNm 1:1 PersonIdentificationSchemeName1Choice Name of the identification scheme. Cd 1:1 ExternalPersonIdentification1Code Value ARNU must be filled in. Othr 0:1 Complex element


Id 1:1 Max35Text Passport No. Number assigned by a passport authority to a passport.

SchmeNm 1:1 PersonIdentificationSchemeName1Choice Name of the identification scheme. Cd 1:1 ExternalPersonIdentification1Code Value CCPT must be filled in. Othr 0:1 Complex element


Id 1:1 Max35Text Tax Identification No. Number assigned by a tax authority to an entity.

SchmeNm 1:1 PersonIdentificationSchemeName1Choice Name of the identification scheme. Cd 1:1 ExternalPersonIdentification1Code Value TXID must be filled in. Othr 0:1 Complex element


Id 1:1 Max35Text Identity Card No. Number assigned by a national authority to an identity card.

SchmeNm 1:1 PersonIdentificationSchemeName1Choice Name of the identification scheme. Cd 1:1 ExternalPersonIdentification1Code Value NIDN must be filled in. Othr 0:1 Complex element


Id 1:1 Max35Text Employer Identification No. Number assigned to an employer by a registration authority.

SchmeNm 1:1 PersonIdentificationSchemeName1Choice Name of the identification scheme. Cd 1:1 ExternalPersonIdentification1Code Value EMPL must be filled in. DtAndPlcOfBirth 0:1 Complex element

DateAndPlaceOfBirth Date and Place of Birth Date and place of birth of a person.

BirthDt 1:1 ISO Date (YYYY-MM-DD) Birth Date Date on which a person is born.

PrvcOfBirth 0:1 Max35Text Province of birth Province where a person was born.

CityOfBirth 1:1 Max35Text City of birth City where a person was born.

CtryOfBirth 1:1 Country code (2 characters) Country of birth Country where a person was born.


Page 17

Element name Occurrence Format Comments Othr 0:1 Complex element

GenericPersonIdentification1

Other Identification Identifier issued to a person for which no specific identifier has been defined.

Id 1:1 Max35Text Identification Identifier issued to a person for which no specific identifier has been defined.

Issr 1:1 Max35Text Issuer Entity that assigns the identification.

INTERNET BANKING OF UNICREDIT BANK CZECH REPUBLIC AND SLOVAKIA, A.S. BUSINESSNET BASIC BUSINESSNET PROFESSIONAL SEPA DIRECT DEBIT IMPORT FORMAT DESCRIPTION December 2013

Contents: SEPA Direct Debit Import description

Introduction .................................................................................................................................................................. 3

SEPA Direct Debit basic description ....................................................................................................................... 4

Advantages of SEPA Direct Debit .............................................................................................................................. 5

Supported type of SEPA direct debit in BusinessNet ............................................................................................... 5

How to import SEPA Direct Debit into BusinessNet ................................................................................................ 5

Allowed character set ................................................................................................................................................... 6

Element occurrence ...................................................................................................................................................... 6

Structure of the ISO 20022 payment .......................................................................................................................... 6

General information ..................................................................................................................................................... 7

Implementation of the pain.008.001.02 for BusinessNet SEPA Direct Debit ...................................................... 9 Root ............................................................................................................................................................................ 9 Group Header ............................................................................................................................................................ 9 Payment Information ................................................................................................................................................ 11 Direct Debit Transaction Information ..................................................................................................................... 12 Direct Debit Transaction ......................................................................................................................................... 13

BusinessNet filling instructions ................................................................................................................................. 15 Organisation Identification elements ....................................................................................................................... 19 Person Identification elements ................................................................................................................................. 20

BusinessNet Import of a SEPA Direct Debit XML Definition PAIN.008.001.02

Page 3

Introduction Dear Client, We are pleased you have decided to use BusinessNet Professional, a modern electronic banking service designed specifically for corporate clients. Electronic banking services will enable you to manage your financial flows simply, comfortably, securely and effectively for 24 hours a day, 7 days a week. This manual will guide you through SEPA Direct Debit format description. If you have any questions, you can contact us on every business day from 7.00 to 18.00, our technical assistance is available at the telephone number Unitel 0800 14 00 14 , or you can send an e-mail to [email protected].

UniCredit Bank Czech Republic and Slovakia, a.s.


Page 4

SEPA Direct Debit basic description Since the end of 2008, businesses and consumers have been able, for the first time ever, to use cross-border direct debiting across 32 European countries. This service may be used if the payers bank and the beneficiarys bank have both acceded to the SEPA Direct Debit Scheme. A SEPA direct debit is a euro-denominated noncash payment initiated electronically by the beneficiary through its bank on the basis of a prior agreement with the payer (a so-called mandate). The agreement between the payer and the beneficiary must contain the required particulars, including the type of SEPA direct debit used. Direct debits are most often used for recurrent payments with a fixed or variable amount, but a one-time direct debit can also be made.

Main features of SEPA Direct Debit

Payment currency is EUR. Account of the beneficiary of the SEPA direct debit payments must be in Euro. The beneficiarys and payers account numbers must be entered in IBAN format. The beneficiarys and payers banks must be identified by their valid BIC codes. The beneficiary of a SEPA direct debit must be a business entity. To obtain a beneficiary identification code (PRINK), the beneficiary of a SEPA direct debit must be

registered at the Czech National Bank in the Czech Republic (or at the appropriate authority for the given country).

The payer concludes a written agreement (a so-called mandate) with the beneficiary. The beneficiary is obliged to send information about the amount and payment date of the SEPA Direct

Debit to the payer in advance (for example in invoice form). The beneficiary is obliged to archive the agreement between itself and the payer (the so-called mandate)

and to present it upon request. The validity of the mandate will expire automatically 36 months after the last request sent.


Page 5

Advantages of SEPA Direct Debit

Possibility to carry out SEPA direct debit within 32 European countries. The payer is informed in advance of an incoming SEPA direct debit and the payment date and thus is able

better to manage its cash. The beneficiary is able to send a message for the payer along with the request. Centralisation of accounts as well as liquidity into a single bank. Due to uniform formats, payments can easily be matched up with accounts receivable or payable in

accounting systems. Processing of payments, including rejected and returned payments, is governed by uniform, standardised

conditions, and thus processing can be automated. Legal harmonisation ensures better predictability of transactions.

Supported type of SEPA direct debit in BusinessNet

Business-to-business (B2B) direct debit is intended exclusively for business entities. A SEPA direct debit mandate must be granted in order to execute a payment on the basis of a request for a SEPA B2B direct debit. This type of SEPA direct debit is irrevocable, and thus the payer cannot request reimbursement of an executed SEPA direct debit. A SEPA Direct Debit may be executed if the banks of the sender of the direct debit and of the payer have accepted the conditions for processing SEPA direct debits.

Consumer SEPA Direct Debit (CORE scheme) is fully supported.

How to import SEPA Direct Debit into BusinessNet

The user can upload the file into the BusinessNet by use of option Payments > Imports & Uploads > Start Import or by use of option Payments > Imports & Uploads > Start Upload. When using these options, the user must first choose the type of order Sepa Payment and then item SEPA Direct Debit Request Pain008 (XML) in the field File Structure in order to upload the file corresponding to this description. Find detailed user instruction concerning the upload of the transaction file in the application Help which you can open by clicking on a question mark in the right upper corner.

File extension which the file name may include: The file containing SEPA Credit Transfer payment orders may include only *.xml extension. Max. length of file name (incl. possible file extension) is 64 characters.


Page 6

Allowed character set Please note that within the fields of the XML only the following characters are allowed to use:

Permitted Character Code Character Hex Code numeric characters 0 to 9 X'30' -X'39' capital characters A to Z X'41' -X'5A' small characters a to z X'61' -'X'7A' apostrophe ' X'27' colon ": X'3A' question mark "? X'3F' comma "," X'2C' minus "-" X'2D' blank character X'20' left bracket "(" X'28' plus sign "+" X'2B' period "." X'2E' right bracket ")" X'29' slash "/" X'2F'

Element occurrence Element occurrence is defined by the following parameters:

Min. occurrence : Max. occurrence 0 = optional : 1 = once

1 = mandatory : 2 = twice : n = unbounded Structure of the ISO 20022 payment

It is important to understand that some of the information within these Pain messages apply to the whole message, to a certain bulk or to a single transaction, depending on the information level.


Page 7

General information Group Header Within the Group Header (Tag ) all information related to the whole file are to be found. The most important ones are:

Message Identification , mandatory (1:1): This Id is used to identify the message and should be unique to the submitter of the message for a predefined period of time. It is a point-to-point reference between the instructing party and the next party in the chain.

Creation Date Time , mandatory (1:1): Date and time at which a (group of) payment instruction(s) was created by the instructing party.

Number of Transactions , mandatory (1:1): Number of all individual transactions contained within this message / file.

Control Sum , optional (0:1): Contains the sum of all instructed amounts of all transactions within this message regardless of the currency of the single transaction.

Initiating Party , mandatory (1:1): Party that initiates the payment. This can either be the creditor or a party that initiates the direct debit on behalf of the creditor.

There are some more fields which may be used by the instructing party. For further details please refer to the ISO 20022 maintenance guide, available at www.iso20022.org. Payment Information Within the Payment Information (Tag ) typically a bulk of payments is stated. One Pain.008.001.02 messages may contain an unbounded number of blocks but does have to have at least one occurrence (1:n). Each is dedicated to one account and one requested execution date. The most important tags to be used by the instructing party are:

Payment Information Identification , mandatory (1:1): Used to identify a specific bulk within the file when being processed.

Payment Method , mandatory (1:1): Used to further specify the type of the transaction. BusinessNet accept only Direct Debit, code DD.

Payment Type Information , mandatory (1:1): Is a set of elements that is used to further specify the type of payments in this respective PmtInf block.

o Service Level , mandatory (1:1): Agreement under which or rules under which the transaction should be processed, as defined in the "ServiceLevel8Choice" (www.iso20022.org). BusinessNet application support only SEPA code.

o Local Instrument , mandatory (1:1) This element is used to specify a local instrument, local clearing option and/or furher qualify the service or service level. In BusinessNet application we support both B2B and B2C code.

o Sequence Type , mandatory (1:1) This element identifies the direct debit sequence, such as first (sequence type FRST), recurrent (sequence type RCUR), final (sequence type FNAL) or one-off (sequence type OOFF).

Requested Collection Date , mandatory (1:1): Specifies the day at which the creditor request that the amount of money is to be collected from the debtor. Requested collection date must be set 2 banking day at the earliest from the current (insertion) date.

Creditor , mandatory (1:1): Party to which an amount of money is due. There are certain elements to further specify the creditor, e.g. Name and Postal Address fields etc.

Creditor Account , mandatory (1:1): Element group that provides the account that has to be credited with the instructed amount. Account must be provided as an IBAN.

Creditor Agent , mandatory (1:1): Element group that specifies financial institution servicing an account for the creditor as a BIC identification.


Page 8

Charge Bearer , optional (0:1): Used to indicate which party/parties will bear the charges associated with the processing of the payment transactions. Only SLEV is allowed.

Direct Debit Transaction Information The Direct Debit Transaction Information describes the individual transactions within a PmtInf block. Theoretically the number of occurrences is unbounded (1:n), but due to some technical issues the receiving institution may limit the number of occurrences per PmtInf block. It is recommended import max 99.999 occurences.

The important information within the DrctDbtTxInf are:

Payment Identification , mandatory (1:1): Element group that uniquely identifies the individual transaction. May contain a Instruction Identification (0:1) which is a point-to-point reference and must contain a End To End Identification (1:1) which is transported without any amendments throughout the whole processing cycle.

Instructed Amount , mandatory (1:1): Element group that specifies the instructed amount. Must be provided as an amount with currency EUR.

Direct Debit Transaction , mandatory (1:1): Set of elements providing information specific to the direct debit mandate and creditor identification (PRINK).

Debtor Agent , mandatory (1:1): Used to specify the debtor's account holding institution. Must consist of a BIC.

Debtor , mandatory (1:1): Specifies the debtor (party that owes an amount of money to the creditor) (e.g. Name, address, organisation or private identification etc.).

Debtor Account , mandatory (1:1): Used to specify the debtor's account with the account holding institution. Debtors account must be filled in in IBAN format.

Remittance Information , optional (0:1): Group of elements used to describe the payment for the debtor more in detail. Please refer to www.iso20022.org for a detailed description of the various elements within the RmtInf. We recommend to use it with unstructured format.


Page 9

Implementation of the pain.008.001.02 for BusinessNet SEPA Direct Debit

Root

Group Header The Group Header consists of the following elements:

Element name Occurrence Format Comments MsgId 1:1 Max35Text Unique message

identification. CreDtTm 1:1 ISODateTime Timestamp when the message

had been created. NbOfTxs 1:1 Max15NumericText Number of all individual

transactions within this message/file.

CtrlSum 0:1 DecimalNumber Sum of all instructed amounts in this message, irrespective of the currencies.

InitgPty 1:1 Complex element Party that created the message, at least the name has to be provided. In general we recommend not to use other elements than the name except where necessary due to local practices.


Page 10


Page 11

Payment Information

The Payment Information may be repeated unbounded, but has to be present at least once. BusinessNet does support the usage of the following elements:

Element name Occurrence Format Comments PmtInf Id 1:1 Max35Text Used to identify a specific bulk within the file

when being processed. PmtMtd 1:1 PaymentMethod2Code Only usage of DD is allowed PmtTpInf 1:1 Complex element Service Level SEPA to be defined in this area.

Local instrument must be B2B. Also sequence type must be defined (FRST, RCUR, FNAL or OOFF).

ReqdColltnDt 1:1 ISODate Date at which the creditor requests that the amount of money is to be collected from the debtor.

Cdtr 1:1 PartyIdentification32 Party to which an amount of money is due. There are certain elements to further specify the creditor, e.g. Name and Postal Address fields etc.

CdtrAcct 1:1 Complex element Account that will be credited with the transactions amount. IBAN requested

CdtrAgt 1:1 Complex element Creditors financial institution. BIC requested DrctDbtTxInf 1:n Complex element Set of elements used to provide information on

the individual transaction(s) included in the message.


Page 12

Direct Debit Transaction Information

The DirectDebitTransactionInformation block must be present at least once, and can be repeated unlimited. All single transaction information are specified within this block, that is debtor's data, instructed amount and currency and so on.

Element name Occurrence Format Comments Pmtld 1:1 Complex element Used to uniquely identify the single

transaction PmtTpInf 0:1 Complex element To be defined in PmtInf level InstAmt 1:1 Complex element Instructed amount, only in EUR currency ChrgBr 0:1 ChargeBearerType1 Code SLEV code is requested DrctDbtTx 1:1 Complex element Set of elements providing information

specific to the direct debit mandate and creditor identification (PRINK).

UltmtCdtr 0:1 Complex element Not supported DbtrAgt 1:1 Complex element BIC requested for SEPA Direct Debit DbtrAgtAcct 0:1 Complex element Not supported Dbtr 1:1 Complex element Specifies the debtor DbtrAcct 1:1 Complex element Specifies the debtor's account as IBAN

account identification UltmtDbtr 0:1 Complex element Not supported

InstrForCdtrAgt 0:1 Max140Text Not supported Purp 0:1 Purpose2choice Underlying reason for the payment

transaction. RgltryRptg 0:10 Complex element Not Supported Tax 0:1 Complex element Not supported RltdRmtInf 0:10 Complex element Not supported RmtInf 0:1 Complex element Used to provide the beneficiary (debtor) with

additional information related to the specific instruction. It is recommended to use it with unstructured format.


Page 13

Direct Debit Transaction

The DirectDebitTransaction element provide information specific to the direct debit mandate and creditor information identification.

Element name Occurrence Format Comments MndtRltdInf 1:1 Complex element

Set of elements used to provide further details of the direct debit mandate signed between the creditor and the debtor

MndtId 1:1 Max35Text Mandate Id (assigned by the creditor) DtOfSgntr 1:1 ISODate Date on which the direct debit mandate has

been signed by the debtor AmdmntInd 1:1 TrueFalseIndicator Amendment Indicator notifying whether the

underlying mandate is amended or not. Possible value are true or false

AmdmntInfDtls 0:1 AmendmentInformation Details6

Amendment Information Details If Amendment Indicator is false, then AmdmntInfDtls is not allowed. If Amendment Indicator is true, then AmdmntInfDtls must be present.

OrgnlMndtId 0:1 Max35Text Original Mandate ID Unique identification, as assigned by the creditor, to unambiguously identify the original mandate.


Page 14

OrgnlCdtrSchmeId PartyIdentification32 Original creditor scheme identification that has been modified.

Id 0:1 Party6Choice Identification of a party (PrvtId) PrvtId 0:1 PersonIdentification5 "Othr" element must be chosen Othr 0:1 GenericPerson

Identification1 Identification and Scheme name

Id 0:1 Max35Text Original Creditor ID (Original PRINK) SchmeNm 0:1 PersonIdentification

SchemeName1Choice "Prtry" must be chosen

Prtry 0:1 Max35Text Must contain SEPA CdtrSchmeId 1:1 Complex element Credit party that signs the mandate Id 1:1 Party6Choice Identification of a party (PrvtId) PrvtId 1:1 PersonIdentification5 "Othr" element must be chosen Othr 1:1 GenericPerson


Id 1:1 Max35Text Creditor ID (PRINK) SchmeNm 1:1 PersonIdentification


Prtry 1:1 Max35Text Must contain SEPA


Page 15

BusinessNet filling instructions Element name Occurrence Format Comments PmtInf 1:n Complex element

PaymentInstructionInformation4 Payment information

PmtInfId 1:1 Max35Text Used to identify a specific bulk within the file when being processed.

PmtMtd 1:1 PaymentMethod2 Code Only usage of DD is allowed PmtTpInf 1:1 Complex element

PaymentTypeInformation20 Used to provide further instructions for all payments within this bulk. Service level SEPA, Local Instrument B2B and one of Sequence Type FRST, FNAL, OOFF or RCUR to be defined in this area.

InstrPrty 0:1 Priority2Code Currently not supported SvcLvl 1:1 ServiceLevel8Choice Mandatory for SEPA Direct Debit Cd 1:1 ExternalServiceLevel1Code Only SEPA code is allowed LclInstrm 1:1 LocalInstrument2Choice Only SEPA Business to Business Direct Debit is allowed Cd 1:1 ExternalLocalInstrument1Code Only B2B code is allowed SeqTp 1:1 SequenceType1Code One of the following Sequence Types must be chosen:

Final (FNAL) Final collection of a series of direct debit instruction First (FRST) First collection of a series of direct debit instructions OneOff (OOFF) Direct debit instruction where the debtors authorisation is used to initiate one single direct debit transaction Recurring (RCUR) - Direct debit instruction where the debtors authorisation is used for regular direct debit transaction initiated by the creditor

ReqdColltnDt 1:1 ISODate Specifies the day at which the creditor request that the amount of money is to be collected from the debtor. Requested collection date must be set 2 banking day at the earliest from the current (insertion) date.

Cdtr 1:1 Complex element PartyIdentification32

Party to which an amount of money is due.

Nm 1:1 Max140Text Creditor name must be provided, only first 35 characters shall be used


Used to provide address details of account holder

Ctry 0:1 CountryCode Used to provide country of residence of the account holder

AdrLine 0:7 Max70Text Used to provide Street and Town of account holder.

CdtrAcct 1:1 Complex element CashAccount16

Creditors's account


Specifies the account details

IBAN 1:1 IBAN2007Identifier Only usage of IBAN is allowed CdtrAgt 1:1 Complex element

BranchAndFinancialInstitution Identification4

Financial institution servicing an account for the creditor


Specifies the financial institution servicing an account for the creditor

BIC 1:1 BICIdentifier Must be provided, only usage of BIC is allowed (BACXCZPP)

DrctDbtTxInf 1:n Complex element DirectDebitTransactionInformation9

Contains the single payment instructions

PmtId 1:1 Complex element PaymentIdentification1

Used to uniquely identify the single payment

InstrId 0:1 Max35Text Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the instruction.

EndToEndId 1:1 Max35Text Unique identification assigned by the initiating party to unumbiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain.

InstdAmt 1:1 Complex element ActiveOrHistoricCurrencyAndAmount

Instructed amount, only currency "EUR" is allowed. This data type must be used with the following XML Attribute: Currency (Ccy) which is typed by ActiveOrHistoricCurrencyCode.

ChrgBr 1:1 ChargeBearerType1Code

Specifies which party/parties will bear the charges associated with the processing of the payment transaction. Only SLEV is allowed


Page 16


Page 17

Element name Occurrence Format Comments DrctDbtTx 1:1 Complex element

DirectDebitTransaction6 Set of elements providing information specific to the direct debit mandate and creditor information identification

MndtRltdInf 1:1 Complex element MandateRelatedInformation6

Set of elements used to provide further details of the direct debit mandate signed between the creditor and the debtor

MndtId 1:1 Max35Text Mandate Id (assigned by the creditor) DtOfSgntr 1:1 ISODate Date on which the direct debit mandate has been signed by

the debtor AmdmntInd 1:1 TrueFalseIndicator Amendment Indicator notifying whether the underlying

mandate is amended or not. Possible value are true or false

AmdmntInfDtls 0:1 AmendmentInformation Details6

Amendment Information Details If Amendment Indicator is false, then AmdmntInfDtls is not allowed. If Amendment Indicator is true, then AmdmntInfDtls must be present.

OrgnlMndtId 0:1 Max35Text Original mandate ID Unique identification, as assigned by the creditor, to unambiguously identify the original mandate.

OrgnlCdtrSchmeI d

PartyIdentification32 Original creditor scheme identification that has been modified.

Id 0:1 Party6Choice Identification of a party (PrvtId) PrvtId 0:1 PersonIdentification5 "Othr" element must be chosen Othr 0:1 GenericPerson


Id 0:1 Max35Text Original Creditor ID (Original PRINK)

SchmeN m

0:1 PersonIdentification SchemeName1Choice

"Prtry" element must be chosen

Prtry 0:1 Max35Text Must contain SEPA CdtrSchmeId 1:1 Complex element Credit party that signs the mandate Id 1:1 Party6Choice Identification of a party (PrvtId) PrvtId 1:1 PersonIdentification5 "Othr" element must be chosen Othr 1:1 GenericPerson


Id 1:1 Max35Text Creditor ID (PRINK) SchmeNm 1:1 PersonIdentification


Prtry 1:1 Max35Text Must contain SEPA DbtrAgt 1:1 Complex element

BranchAndFinancialInstitutionIdentification4

Used to specify the debtor's account holding bank


Specifies the debtor bank's details

BIC 1:1 BICIdentifier BIC identifier must be provided Dbtr 1:1 Complex element

PartyIdentification32 Used to provide debtor's details

Nm 1:1 Max140Text Debtor name must be provided, only first 70 characters shall be used

PstlAdr 0:1 Complex element Used to provide address details of beneficiary, same rules as Cre

Documents

20.5.2014 SEPA SK Country Guide en New 16012014-New