XML SEPA CT IN KB (valid from 28th November 2015)

Size: px
Start display at page:

Download "XML SEPA CT IN KB (valid from 28th November 2015)"

Transcription

1 XML SEPA CT IN KB (valid from 28th November 2015) 1/20

2 Content: 1. Scope Application Message structure (items used by KB) Group leader N Payment information Rules according to ISO for selected tags used in KB Details for address structure in KB Details of structure of organization or private person identification in KB Examples of identification definition for Payer and Beneficiary in XML and on DCS Mojebanka channel screens Example of XML with two payments Example of SEPA urgent payment version /20

3 1. Scope Electronic transfer of KB client requests for sending cross-border payments in EUR within the SEPA. KB arranges debiting of the required account according to SEPA terms (scheme Rulebooks), and sending the payment to the defined bank and account including non-accounting data handed over to the partner. The XML format can be used for executing/initiating a SEPA payment to a SEPA Reachable Bank as well as to a SEPA Non-Reachable Bank (including EUR payments to KBSK). A note concerning the handing over to the counterpart of non-accounting information: If a EUR payment is used within the SEPA Area but the relevant bank is not a SEPA Reachable Bank, the only non-accounting information the beneficiary receives will be additional information (remittance information). 2. Application Standard pain (version 02) defines 3 types of modes (i.e. three options of constructing XML): Single (single orders - each payment has its own Payment Information Block) Group (multiple orders - a common Payment Information Block and several occurrences of payment blocks) Mixed (both types within a single message) Standard pain (version 03) and standard pain (version 04) do not specify any mode any more and are implicitly considered as the Mixed mode. KB converts MIXED and GROUP modes to single payments. A character set of all SEPA payments text fields is limited to valid characters of the SWIFT character set; the SWIFT character set currently valid characters must always be adhered to see Table of allowed characters available at 3/20

4 3. Message structure (items used by KB) Note: KB accepts SEPA payments according to ISO standard namespace urn:iso:std:iso:20022:tech:xsd:pain , tag <Grpg> or a preceding code GRPD or MIXD, converted to SNGL SINGLE by KB. standard namespace urn:iso:std:iso:20022:tech:xsd:pain , expected preceding code MIXD, converted to SNGL SINGLE by KB. standard namespace urn:iso:std:iso:20022:tech:xsd:pain , expected preceding code MIXD, converted to SNGL SINGLE by KB. 4/20

5 This document contains tags, from which values are accepted for further processing in KB and are only valid for standard pain There are minor differences in the element structure and names under the versions pain and pain It is therefore desirable to follow the following descriptions: for pain , for pain XML without namespace or with different namespace will be considered as an invalid format. Tags of required (mandatory) fields are put in grey background in the tables below 3.1 Group leader 1.0 Group Header <GrpHdr> [1..1] 1.1 Message Identification <MsgId> [1..1] Text 1.2 Creation Date Time <CreDtTm> [1..1] DateTime Used for duplication detection. 1.5 Number Of Transactions <NbOfTxs> [1..1] Text Validations only with notification 1.6 Control Sum <CtrlSum> [0..1] Quantity Validations only with notification 1.7 Grouping <Grpg> [1..1] Code SNGL, GRPD or MIXD required for pain v02, this tag is not applicable for any other pain standards 1.8 Initiating Party <InitgPty> [1..1] +- Not taken over in KB 3.2 N Payment information 2.0 Payment Information <PmtInf> [1..n] 2.2 Payment Method <PmtMtd> [1..1] Code TRF 2.13 Requested Execution Date <ReqdExctnDt> [1..1] Date Debit due date 2.15 Debtor <Dbtr> [1..1] + Name, address, identification. KB takes over only identification; it does not take over the name and address, but uses it according to its own administration Debtor Account <DbtrAcct> [1..1] + IBAN (currency need not be specified; if it is specified, it must correspond to administration, otherwise it will be rejected) Debtor Agent <DbtrAgt> [1..1] + Not taken over and validated by KB; KB checks the bank using IBAN Ultimate Debtor <UltmtDbtr> [0..1] + Will be transferred by KB when Rulebook 3.2. is officially approved; clients will be informed on KB website Charge Bearer <ChrgBr> [0..1] Code If not specified, KB will use SLEV; if to be specified, only SLEV can be used Charges Account <ChrgsAcct> [0..1] + To be specified only if you require different KB account to be charge (currency need not be specified; if to be specified, it must correspond to administration, otherwise it will be rejected) Credit Transfer <CdtTrfTxInf> [1..n] Transaction Information 2.24 Payment Identification <PmtId> [1..1] 2.25 Instruction Identification <InstrId> [0..1] Text Unique identification for KB (duplicate detection); if not specified, information of the 5/20

6 EndToEnd field will be used End To End Identification <EndToEndId> [1..1] Text Handed over to the partner; if InstrId is not specified, this value is used for KB purpose: InstrId = End To End Id Payment Type Information <PmtTpInf> [0..1] 2.28 Instruction Priority <InstrPrty> [0..1] Code If it is stated "HIGH" = urgent payment. If it is stated "NORM" or is blank = express payment Service Level <SvcLvl> [0..1] 2.30 Code <Cd> [1..1] Code All transferred via XML will be SEPA only in KB. Specification is not necessary; if different value is used, it will be rejected Category Purpose [0..1] Code For the version pain (only in this level and only as Code) 2.37 Amount <Amt> [1..1] 2.38 Instructed Amount <InstdAmt> [1..1] Amount Amount in EUR Currencies other than EUR will be rejected in KB Charge Bearer <ChrgBr> [0..1] Code Only SLEV can be used for SEPA payments. Not compulsory; KB uses it by default Creditor Agent <CdtrAgt> [0..1] + BIC - the bank must be SEPA-compliant Creditor <Cdtr> [0..1] + Name, address - required; identification (optional) 2.58 Creditor Account <CdtrAcct> [1..1] + IBAN 2.59 Ultimate Creditor <UltmtCdtr> [0..1] + Will be transferred by KB when Rulebook 3.2. is officially approved; clients will be informed on KB website Purpose <Purp> [0..1] See the Chapter 2.64 Purpose <Purp> 2.84 Remittance Information <RmtInf> [0..1] 2.85 Unstructured <Ustrd> [0..n] Text Details of payment 4. Rules according to ISO for selected tags used in KB FOR Header: 1.1 Message Identification <MsgId> Definition: Point to point reference assigned by the instructing party and sent to the next party in the chain to unambiguously identify the message. Usage: The instructing party has to make sure that 'MessageIdentification' is unique per instructed party for a pre-agreed period. Data Type: Max 35 Text Format: max Length: 35 minlength: Creation Date Time <CreDtTm> Definition: Date and time at which a (group of) payment instruction(s) was created by the instructing party. Data Type: ISO Date Time 1.5 Number Of Transactions <NbOfTxs> Definition: Number of individual transactions contained in the message. Data Type: Max 15 Numeric Text Format: [0-9]{1,15} 6/20

7 1.6 ControlSum <CtrlSum> Definition: Total of all individual amounts included in the message, irrespective of currencies. Data Type: Decimal Number Format: fraction Digits: 17 totaldigits: Grouping <Grpg> Definition: Indicates whether common accounting information in the transaction is included once for all transactions or repeated for each single transaction. In KB only one possibility: single SNGL 1.8 Initiating Party <InitgPty> Definition: Party initiating the payment. In the payment context, this can either be the debtor (in a credit transfer), the creditor (in a direct debit), or the party that initiates the payment on behalf of the debtor or creditor. Type: This message item is composed of the following Party Identification 8 element(s): Or Message Item <XML Tag> Mult. Represent./Type Name <Nm> [0..1] Text Postal Address <PstlAdr> [0..1] Not taken over or validated in KB. The address administered in DB DCS is used. If to be sent, see the structure description in chapter 4 - Address in KB. FOR Payments 2.0 Payment Information <PmtInf> Presence: [1..n] Definition: Set of characteristics that applies to the debit side of the payment transactions included in the credit transfer initiation. Type: The Payment Information block is composed of the following Payment Instruction Information 1 element(s): 2.1 Payment Information Identification <PmtInfId> [0..1] Text 2.2 Payment Method <PmtMtd> [1..1] Code TRF 2.3 Payment Type Information <PmtTpInf> [0..1] 2.13 Requested Execution Date <ReqdExctnDt> [1..1] DateTime DATE 2.15 Debtor <Dbtr> [1..1] + Address and name is not taken over, only identification is, if specified Debtor Account <DbtrAcct> [1..1] + IBAN currency need not be specified. If specified, it will be validated against the status in DB Debtor Agent <DbtrAgt> [1..1] + Not taken over and validated. The bank will be validated via IBAN Ultimate Debtor <UltmtDbtr> [0..1] + Currently not transferred by KB Charge Bearer <ChrgBr> [0..1] Code KB will use SLEV; however, if you specify a value, which is different from SLEV, it will be rejected Charges Account <ChrgsAcct> [0..1] + The account number is to be specified only if it is different from the account number for the actual payment (always only in KB) Credit Transfer Transaction Information <CdtTrfTxInf> [1..n] Creditor description block 7/20

8 2.2 Payment Method <PmtMtd> Definition: Specifies the means of payment that will be used to move the amount of money. Data Type: Code TRF 2.13 Requested Execution Date <ReqdExctnDt> Definition: Date at which the initiating party requests the clearing agent to process the payment. If payment by cheque, the date when the cheque must be generated by the bank. Usage: This is the date on which the debtor's account(s) is (are) to be debited. Data Type: ISO Date 2.15 Debtor <Dbtr> Definition: Party that owes an amount of money to the (ultimate) creditor. Type: This message item is composed of the following Party Identification 8 element(s): Or Message Item <XML Tag> Mult. Represent./Type Name <Nm> [0..1] Text Postal Address <PstlAdr> [0..1] Chapter 5 Identification [0..1] Chapter 6 Country Of Residence <CtryOfRes> [0..1] Code 2.16 Debtor Account <DbtrAcct> Definition: Unambiguous identification of the account of the debtor to which a debit entry will be made as a result of the transaction. Type: This message item is composed of the following Cash Account 7 element(s): Or Message Item <XML Tag> Mult. Represent./Type Identification [1..1] <IBAN> Currency <Ccy> [0..1] Code 2.17 Debtor Agent <DbtrAgt> Definition: Financial institution servicing an account for the debtor. Type: This message item is composed of the following Branch And Financial Institution Identification3 element(s): Or Message Item <XML Tag> Mult. Represent./Type Financial Institution Identification <FinInstnId> [1..1] <BIC> not validated by KB 2.19 Ultimate Debtor <UltmtDbtr> Definition: Ultimate party that owes an amount of money to the (ultimate) creditor. Type: This message item is composed of the following Party Identification 8 element(s): Or Message Item <XML Tag> Mult. Represent./Type Name <Nm> [0..1] Text Postal Address <PstlAdr> [0..1] Chapter 5 Identification [0..1] Chapter 6 Country Of Residence <CtryOfRes> [0..1] Code 2.20 Charge Bearer <ChrgBr> Definition: Specifies which party/parties will bear the charges associated with the processing of the payment transaction. Data Type: Code When this message item is present, one of the following Charge Bearer Type 1 Code values must be used: Code Name Definition (for KB SEPA is acceptable only SLEV) CRED Borne By Creditor All transaction charges are to be borne by the creditor. DEBT Borne By Debtor All transaction charges are to be borne by the debtor. 8/20

9 SHAR Shared In a credit transfer context, means that transaction charges on the sender side are to be borne by the debtor, transaction charges on the receiver side are to be borne by the creditor. In a direct debit context, means that transaction charges on the sender side are to be borne by the creditor, transaction charges on the receiver side are to be borne by the debtor. SLEV Following Service Level Charges are to be applied following the rules agreed in the service level and/or scheme Charges Account <ChrgsAcct> Definition: Account used to process charges associated with a transaction. Usage: charges account should be used when charges have to be booked to an account different from the account identified in debtor's account. Type: This message item is composed of the following Cash Account 7 element(s): Or Message Item <XML Tag> Mult. Represent./Type Identification [1..1] <IBAN> Currency <Ccy> [0..1] Code 2.23 CreditTransferTransactionInformation <CdtTrfTxInf> Presence: [1..n] Definition: Set of elements providing information specific to the individual transaction(s) included in the message. Type: This message item is composed of the following Credit Transfer Transaction Information 1 element(s): 2.24 Payment Identification <PmtId> [1..1] 2.27 Payment Type Information <PmtTpInf> [0..1] 2.37 Amount <Amt> [1..1] 2.55 Creditor Agent <CdtrAgt> [0..1] Creditor <Cdtr> [0..1] Creditor Account <CdtrAcct> [0..1] Ultimate Creditor <UltmtCdtr> [0..1] Remittance Information <RmtInf> [0..1] 2.36 Category Purpose <CtgyPurp> Presence: [1..n] Definition: Category Purpose standardised code optional field. Type: More information about the ISO codes can be found at Purpose <Purp> [0..1] {Or Code <Cd> [1..1] Code by ISO ISO Code for pain and pain Or} Proprietary <Prtry> [1..1] Text Purpose for pain and pain Amount <Amt> Definition: Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. Type: This message item is composed of one of the following Amount Type 2 Choice element(s): 2.38 Instructed Amount <InstdAmt> [1..1] Amount Only EUR permitted in KB 2.38 Instructed Amount <InstdAmt> This message item is part of choice 2.37 Amount. Definition: Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in The currency as ordered by the initiating party. Data Type: CurrencyAndAmount This data type must be used with the following XML Attribute: Currency (Ccy) which is typed by Currency Code. Format: Currency And Amount Fraction Digits: 5 Min Inclusive: 0 Total Digits: 18 Currency Code 9/20

10 [A-Z]{3,3} Rule(s): Currency Code Validation By Table 2.55 Creditor Agent <CdtrAgt> Definition: Financial institution servicing an account for the creditor. Type: This message item is composed of the following Branch And Financial Institution Identification 3 element(s): Or Message Item <XML Tag> Mult. Represent./Type Financial Institution Identification <FinInstnId> [1..1] <BIC> - the bank can be, but does not have to be SEPA-complying. A format can be either 8 or 11 character. If the BIC consists of 8 valid characters, 3 blank spaces should be added to the right Creditor <Cdtr> Definition: Party to which an amount of money is due. Type: This message item is composed of the following Party Identification 8 element(s): Or Message Item <XML Tag> Mult. Represent./Type Name <Nm> [0..1] Text Postal Address <PstlAdr> [0..1] Chapter 5 Identification [0..1] Chapter 6 Country Of Residence <CtryOfRes> [0..1] Code 2.58 Creditor Account <CdtrAcct> Definition: Unambiguous identification of the account of the creditor to which a credit entry will be posted as a result of the payment transaction. Type: This message item is composed of the following Cash Account 7 element(s): Or Message Item <XML Tag> Mult. Represent./Type Identification [1..1] 2.59 Ultimate Creditor <UltmtCdtr> Definition: Ultimate party to which an amount of money is due. Type: This message item is composed of the following Party Identification 8 element(s): Or Message Item <XML Tag> Mult. Represent./Type Name <Nm> [0..1] Text Postal Address <PstlAdr> [0..1] Chapter 5 Identification [0..1] Chapter 6 Country Of Residence <CtryOfRes> [0..1] Code 2.64 Purpose <Purp> Definition: Purpose of Payment standardised code optional field. Type: More information about the ISO codes can be found at Purpose <Purp> [0..1] 2.65 {Or Code <Cd> [1..1] Code by ISO ISO Code 2.66 Or} Proprietary <Prtry> [1..1] Text Purpose of Payment In case of the Purpose <Purp> tag, both embedded tags can be used, i.e. Proprietary <Prtry> and Code <Cd>. However, only one of them can be filled in an instruction, NOT both at the same time. When submitting an instruction, the client can choose whether the purpose of the payment, as specified by the client, will be inserted into the <Prtry> tag or <Cd> tag. Proprietary is an arbitrary text consisting of 35 characters of a standard character set (SWIFT) at a maximum. Purpose Code: The code should be in line with the ISO external code list (e.g. COLL or AREN ). The field is validated against the code list in case of pain , as the ISO code list is part of the XSD definition. The validation against the ISO code list is not 10/20

11 performed under the most recent versions. The client will be liable for possible faults (e.g. if an instruction is rejected by the debtor s bank because the Code is inconsistent with a ISO code list) Remittance Information <RmtInf> Definition: Information that enables the matching, ie, reconciliation, of a payment with the items that the payment is intended to settle, eg, commercial invoices in an account receivable system. Type: This message item is composed of the following Remittance Information 1 element(s): 2.85 Unstructured <Ustrd> [0..n] Text Only non-structured information used Unstructured <Ustrd> Presence: [0..n] Definition: Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, eg, commercial invoices in an accounts' receivable system in an unstructured form. Data Type: Max140Text Format: max Length: 140 minlength: 5. Details for address structure in KB In KB, the structured approach will be required for the structure of the address, as well as using of appropriate tags for name, town, street, number, postcode and country. Address validation will be applied according to effective rules for foreign payments transferred via DCS (same as for BEST and EDI_BEST formats) Postal Address <PstlAdr> Definition: Information that locates and identifies a specific address, as defined by postal services. Type: This message item is composed of the following PostalAddress1 element(s): Street Name <StrtNm> [0..1] Text Building Number <BldgNb> [0..1] Text Post Code <PstCd> [0..1] Text Town Name <TwnNm> [0..1] Text Country <Ctry> [1..1] Code Street Name <StrtNm> UNIFI (ISO 20022) - Payments Standards - Initiation October 2006 Message Item Types Page 343 Definition: Name of a street or thoroughfare. Data Type: Max 70 Text Format: max Length: 70 Min Length: Building Number <BldgNb> Definition: Number that identifies the position of a building on a street. Data Type: Max 16 Text Format: max Length: 16 Min Length: Post Code <PstCd> Definition: Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail. 11/20

12 Data Type: Max16Text Format: max Length: 16 Min Length: Town Name <TwnNm> Definition: Name of a built-up area, with defined boundaries, and a local government. Data Type: Max35Text Format: max Length: 35 Min Length: Country <Ctry> Definition: Nation with its own government. Data Type: Country Code Format: [A-Z]{2,2} Rule(s): Country The code is checked against the list of country names obtained from the United Nations (ISO 3166, Alpha-2 code). 6. Details of structure of organization or private person identification in KB The client can transfer identification of payer, beneficiary, original payer and final beneficiary according to whether the identification refers to an organization or a private person. This chapter specifies tags defined in XML, which are taken over in KB. The following is standard usage: Selecting the identification type - whether it is an organization of a private person Using for Organization (<OrgId>) - the <PrtryID> tag with nested tags for identification data and the <Issr> tag for document issuer. Using for Private (<PrvtId>) - the <OthrID> tag with nested tags for identification data, <IdTp> for Document type and the <Issr> tag for document issuer Identification Definition: Unique and unambiguous way of identifying an organisation or an individual person. Type: This message item is composed of one of the following Party 2 Choice element(s): {Or Organisation Identification <OrgId> [1..1] Or} Private Identification <PrvtId> [1..4] Organisation Identification <OrgId> This message item is part of choice Identification. Definition: Unique and unambiguous way of identifying an organisation. Type: This message item is composed of the following Organisation Identification 2 element(s): ProprietaryIdentification <PrtryId> [0..1] KB allows only this tag ProprietaryIdentification <PrtryId> Definition: Unique and unambiguous identifier for an organisation that is allocated by an institution. Type: This message item is composed of the following Generic Identification 3 element(s): Identification [1..1] Text Identification data Issuer <Issr> [0..1] Text Issuer of document Identification 12/20

13 Definition: Name or number assigned by an entity to enable recognition of that entity, eg, account identifier. Data Type: Max 35 Text Format: max Length: 35 Min Length: Issuer <Issr> Definition: Entity that assigns the identification. Data Type: Max 35 Text Format: max Length: 35 Min Length: Private Identification <PrvtId> Presence: [1..4] This message item is part of choice Identification. Definition: Unique and unambiguous identification of a person, eg, passport. Type: This message item is composed of the following Person Identification 3 element(s): OtherIdentification <OthrId> [1..1] KB allows only this tag Issuer <Issr> [0..1] Text Issuer of document OtherIdentification <OthrId> This message item is part of choice Private Identification. Definition: Identifier issued to a person for which no specific identifier has been defined. Type: This message item is composed of the following Generic Identification 4 element(s): Identification [1..1] Text Identification data IdentificationType <IdTp> [1..1] Text Document type Identification Definition: Identifier issued to a person for which no specific identifier has been defined. Data Type: Max 35 Text Format: max Length: 35 Min Length: IdentificationType <IdTp> Definition: Specifies the nature of the identifier. Usage: IdentificationType is used to specify what kind of identifier is used. It should be used in case the identifier is different from the identifiers listed in the pre-defined identifier list. Data Type: Max 35 Text Format: max Length: 35 Min Length: Issuer <Issr> Definition: Entity that assigns the identifier. Data Type: Max 35 Text Format: maxlength: 35 minlength: 1 13/20

14 7. Examples of identification definition for Payer and Beneficiary in XML and on DCS Mojebanka channel screens <!-- Identification of payer --> <Dbtr> <OrgId> <PrtryId> Identification data <Issr>Issuer of document</issr> </PrtryId> </OrgId> </Dbtr> <!-- Identification of beneficiary --> <Cdtr> <PrvtId> <OthrId> Identification data <IdTp>Document type</idtp> </OthrId> <Issr>Issuer of document</issr> </PrvtId> </Cdtr> <!-- Identification of original payer --> <UltmtDbtr> <Nm>Original payer s name</nm> </UltmtDbtr> <!-- Identification of final payer --> <UltmtCdtr> <PrvtId> <OthrId> Identification data <IdTp>Document type</idtp> </OthrId> <Issr>Issuer of document</issr> </PrvtId> </UltmtCdtr> 14/20

15 8. Example of XML with two payments Example of two payments sent in a single file: The first payment is sent for organization, the other for a private person. Optional identification of partner is transferred in both payments. Optional debit account currency is specified in the first payment. In both payments, the optional payment identification item is specified; this item is necessary for processing in KB to keep uniqueness within the framework of the client (if not specified, the EndToEnd item, which would have to proof satisfactory in validation against uniqueness, would be taken over for this purpose). In both payments, SEPA service level is specified; this field is optional and KB is not performing any other service level for an XML of transferred payments. Charges are not specified; the bank will use SLEV by default for SEPA. Number of account for charges is identical as the account number for the actual payment in one of the payments; for the other payment, different account number is required. <?xml version="1.0" encoding=" UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain "> <!--CustomerCreditTransferInitiationV02 pain > <pain > <GrpHdr> <!-- Not taken over --> <MsgId> PAY1234</MsgId> <!-- Creation date --> <CreDtTm> T16:36:00</CreDtTm> <!-- Number of orders --> <NbOfTxs>2</NbOfTxs> <!-- Checksum of amounts--> <CtrlSum>300.88</CtrlSum> <!-- Only version02 --> <Grpg>SNGL</Grpg> <!-- Not taken over (identification of the party that created the file) --> <InitgPty> <Nm>ABC Consulting s.r.o.</nm> <PstlAdr> <StrtNm>U žluťoučkého koně</strtnm> <BldgNb>1622/12</BldgNb> <PstCd>158 00</PstCd> <TwnNm>Praha 13</TwnNm> <Ctry>CZ</Ctry> </PstlAdr> </InitgPty> </GrpHdr> <!-- PAYMENT 1 [BEGIN] {Organisation}--> <PmtInf> <!-- Not taken over --> <PmtMtd>TRF</PmtMtd> <!-- Required due date --> <ReqdExctnDt> </ReqdExctnDt> <!-- Identification of order party --> <Dbtr> <Nm>TKT_NTI a.s.</nm> <PstlAdr> <StrtNm>Na Příkopě</StrtNm> <BldgNb>22</BldgNb> <PstCd>114 07</PstCd> <TwnNm>Praha 1, Staré Město</TwnNm> <Ctry>CZ</Ctry> </PstlAdr> <OrgId> 15/20

16 </Dbtr> <PrtryId> DIC <Issr>Issuer of document - payment 1</Issr> </PrtryId> </OrgId> <!-- Order party s account number --> <DbtrAcct> <IBAN>CZ </IBAN> <Ccy>USD</Ccy> </DbtrAcct> <!-- Not taken over --> <DbtrAgt> <FinInstnId> <BIC>KOBACZPX</BIC> </FinInstnId> </DbtrAgt> <CdtTrfTxInf> <PmtId> <!-- Client ID (Duplicate payment validation in KB) --> <InstrId>KB00001 client ID</InstrId> <!-- Payer's reference --> <EndToEndId>00001 ID agreed with partner</endtoendid> </PmtId> <!-- Not taken over --> <PmtTpInf> <SvcLvl> <Cd>SEPA</Cd> </SvcLvl> </PmtTpInf> <!-- Amount and currency of payment (only EUR in KB!!!) --> <Amt> <InstdAmt Ccy="EUR">100.67</InstdAmt> </Amt> <!-- Charge type --> <ChrgBr>SLEV</ChrgBr> <!-- Identification of beneficiary s bank --> <CdtrAgt> <FinInstnId> <BIC>SOGEFRPP</BIC> </FinInstnId> </CdtrAgt> <!-- Beneficiary s data --> <Cdtr> <Nm>COMM France Ltd.</Nm> <PstlAdr> <StrtNm>Veine Jugulaire</StrtNm> <BldgNb>58/125B</BldgNb> <PstCd>3PA00</PstCd> <TwnNm>Paris</TwnNm> <Ctry>FR</Ctry> </PstlAdr> <OrgId> <PrtryId> PCA B <Issr>Paris Central Authority</Issr> </PrtryId> 16/20

17 </Cdtr> </OrgId> <!-- Beneficiary s account number --> <CdtrAcct> <IBAN>FR M02606</IBAN> </CdtrAcct> <!-- Details of payment --> <RmtInf> <Ustrd>Goods-and-Services-Tax Pay-Off (max length 140 characters)</ustrd> </RmtInf> </CdtTrfTxInf> </PmtInf> <!-- PAYMENT 1 [END] --> <!-- PAYMENT 2 [BEGIN] {Private}--> <PmtInf> <!-- Not taken over --> <PmtMtd>TRF</PmtMtd> <!-- Required due date --> <ReqdExctnDt> </ReqdExctnDt> <!-- Identification of order party --> <Dbtr> <Nm>TKT_NTI a.s.</nm> <PstlAdr> <StrtNm>Na Příkopě</StrtNm> <BldgNb>22</BldgNb> <PstCd>114 07</PstCd> <TwnNm>Praha 1, Staré Město</TwnNm> <Ctry>CZ</Ctry> </PstlAdr> <OrgId> <PrtryId> DIC <Issr>Issuer of document - payment 2</Issr> </PrtryId> </OrgId> </Dbtr> <!-- Order party s account number --> <DbtrAcct> <IBAN>CZ </IBAN> <Ccy>USD</Ccy> </DbtrAcct> <!-- Not taken over --> <DbtrAgt> <FinInstnId> <BIC>KOBACZPX</BIC> </FinInstnId> </DbtrAgt> <!-- Account for charges (+currency, as the case may be)--> <ChrgsAcct> <IBAN>CZ </IBAN> <Ccy>CZK</Ccy> </ChrgsAcct> 17/20

18 <CdtTrfTxInf> <PmtId> <!-- Client ID (Duplicate payment validation in KB) --> <InstrId>KB00002 client ID</InstrId> <!-- Payer's reference --> <EndToEndId>00002 ID agreed with partner</endtoendid> </PmtId> <!-- Not taken over --> <PmtTpInf> <SvcLvl> <Cd>SEPA</Cd> </SvcLvl> </PmtTpInf> <!-- Amount and currency of payment (only EUR in KB!!!) --> <Amt> <InstdAmt Ccy="EUR">200.21</InstdAmt> </Amt> <!-- Charge type --> <ChrgBr>SLEV</ChrgBr> <!-- Identification of original payer (SEPA 2)--> <UltmtDbtr> <Nm>NTI a.s.</nm> </UltmtDbtr> <!-- Identification of beneficiary s bank --> <CdtrAgt> <FinInstnId> <BIC>DEUTDEDB101</BIC> </FinInstnId> </CdtrAgt> <!-- Beneficiary s data --> <Cdtr> <Nm>Hans Friedrich</Nm> <PstlAdr> <StrtNm>Halsschlagader Strasse</StrtNm> <BldgNb>1</BldgNb> <PstCd>14165</PstCd> <TwnNm>Berlin - Zehlendorf</TwnNm> <Ctry>DE</Ctry> </PstlAdr> <PrvtId> <OthrId> FS <IdTp>Fuhrerschein</IdTp> </OthrId> <Issr>Berliner Landesamt</Issr> </PrvtId> </Cdtr> <!-- Beneficiary s account number --> <CdtrAcct> <IBAN>DE </IBAN> </CdtrAcct> <!-- Identificatin of final beneficiary (SEPA 2 - taken over, however, currently not used in KB)--> <UltmtCdtr> <PrvtId> <OthrId> DE /20

19 </UltmtCdtr> <IdTp>Passport No.</IdTp> </OthrId> <Issr>Münchener Landesamt</Issr> </PrvtId> <!-- Details of payment --> <RmtInf> <Ustrd>service-supply payment /VS/ /KS/10 (max length 140 characters)</ustrd> </RmtInf> </CdtTrfTxInf> </PmtInf> <!-- PAYMENT 2 [END] --> </pain > 9. Example of SEPA urgent payment version 03 <?xml version="1.0" encoding=" UTF-8"?> - <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain "> - <CstmrCdtTrfInitn> - <GrpHdr> <MsgId>KB</MsgId> <CreDtTm> T14:34:37</CreDtTm> <NbOfTxs>1</NbOfTxs> <CtrlSum>1.15</CtrlSum> - <InitgPty> - <PstlAdr> <StrtNm>NA STROUZE 1</StrtNm> <PstCd>110 00</PstCd> <TwnNm>PRAHA</TwnNm> <Ctry>CZ</Ctry> </PstlAdr> </InitgPty> </GrpHdr> - <!-- PAYMENT 1 [BEGIN] --> - <PmtInf> <PmtInfId>NOVE</PmtInfId> <PmtMtd>TRF</PmtMtd> - <PmtTpInf> <InstrPrty>HIGH</InstrPrty> </PmtTpInf> <ReqdExctnDt> </ReqdExctnDt> - <Dbtr> <Nm>KLIENT ABC</Nm> - <PstlAdr> <StrtNm>NA STROUZE 1</StrtNm> <PstCd>110 00</PstCd> <TwnNm>PRAHA</TwnNm> <Ctry>CZ</Ctry> </PstlAdr> </Dbtr> - <!-- Neprebirano --> - <DbtrAcct> - <IBAN>CZ </IBAN> <Ccy>CZK</Ccy> </DbtrAcct> - <DbtrAgt> - <FinInstnId> 19/20

20 <BIC>KOMBCZPPXXX</BIC> </FinInstnId> </DbtrAgt> - <ChrgsAcct> - <IBAN>CZ </IBAN> <Ccy>CZK</Ccy> </ChrgsAcct> - <CdtTrfTxInf> - <PmtId> <InstrId>1</InstrId> <EndToEndId>1 ID dohodnuté s partnerem</endtoendid> </PmtId> - <!-- Neprebirano --> - <PmtTpInf> - <SvcLvl> <Cd>SEPA</Cd> </SvcLvl> </PmtTpInf> - <Amt> <InstdAmt Ccy="EUR">1.15</InstdAmt> </Amt> <ChrgBr>SLEV</ChrgBr> - <CdtrAgt> - <FinInstnId> <BIC>SOGEFRPPXXX</BIC> </FinInstnId> </CdtrAgt> - <Cdtr> <Nm>Jean Luc Creperu</Nm> - <PstlAdr> <StrtNm>Le Pufova 1</StrtNm> <PstCd>PARIS</PstCd> <Ctry>FR</Ctry> </PstlAdr> </Cdtr> - <CdtrAcct> - <IBAN>FR M02606</IBAN> </CdtrAcct> - <RgltryRptg> <Dtls /> </RgltryRptg> - <RmtInf> <Ustrd>AV1 DO EHP EUR IBAN AV2 DO EHP EUR IBAN AV3 DO EHP EUR IBAN AV4 DO EHP EUR IBAN</Ustrd> </RmtInf> </CdtTrfTxInf> </PmtInf> - <!-- PAYMENT 1 [END] --> </CstmrCdtTrfInitn> </Document> 20/20

XML message for SEPA Credit Transfer Initiation Implementation Guidelines for the Netherlands

XML message for SEPA Credit Transfer Initiation Implementation Guidelines for the Netherlands XML message for SEPA Credit Transfer Initiation Implementation Guidelines for the Netherlands Disclaimer These guidelines may be subject to changes. Utmost care has been taken to ensure the information

More information

SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES

SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Doc: EPC115-06 25 November 2014 (Version 8.0 Approved) EPC SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for implementing

More information

SEPA Direct Debit Unpaid Report File Format

SEPA Direct Debit Unpaid Report File Format SEPA Direct Debit Unpaid Report File Format PAIN.002.001.03 XML File Structure This document is published by Bank of Ireland, and both it, and its contents, are the property of Bank of Ireland. This document

More information

DESCRIPTION OF SEPA XML FORMAT FOR ING BUSINESSONLINE IMPORT AND EXPORT TEMPLATES

DESCRIPTION OF SEPA XML FORMAT FOR ING BUSINESSONLINE IMPORT AND EXPORT TEMPLATES DESCRIPTIN F SEPA XML FRMAT FR ING BUSINESSNLINE IMPRT AND EXPRT TEMPLATES TABLE F CNTENTS Import of orders 3 1. Introduction 3 1.1 Notation 3 1.2 File structure 4 1.3 Batching rules 4 1.4 Differentiation

More information

XML message for SEPA Direct Debit Initiation Implementation Guidelines for the Netherlands

XML message for SEPA Direct Debit Initiation Implementation Guidelines for the Netherlands XML message for SEPA Direct Debit Initiation Implementation Guidelines for the Netherlands Core and Business-to-Business Implementation Guidelines Disclaimer These guidelines may be subject to changes.

More information

XML message for SEPA Direct Debit Initiation Implementation Guidelines for the Netherlands

XML message for SEPA Direct Debit Initiation Implementation Guidelines for the Netherlands XML message for SEPA Direct Debit Initiation Implementation Guidelines for the Netherlands Core and Business-to-Business Implementation Guidelines Disclaimer These guidelines may be subject to changes.

More information

How To Create A Credit Card From A Creditcard In A Microsoft Web Server On A Microsql Web Server

How To Create A Credit Card From A Creditcard In A Microsoft Web Server On A Microsql Web Server Appendix to Danish Message Implementation Guideline for Common Global Implementation (CGI) Customer Credit Transfer Initiation and Danish Implementation Guideline for CGI Customer Payment Status Report

More information

Payments Market Practice Document. ISITC Settlements Working Group

Payments Market Practice Document. ISITC Settlements Working Group Payments Market Practice Document ISITC Settlements Working Group Publication Date: October, 2012 Author(s): ISITC Settlements Working Group DISCLAIMER This market practice document has been developed

More information

SEPA CORE DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES

SEPA CORE DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Doc: EPC114-06 25 November 2014 (Version 8.0 Approved) EPC SEPA CORE DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for implementing

More information

Record description XML File Transfer ISO 20022 XML pain.001.001.02

Record description XML File Transfer ISO 20022 XML pain.001.001.02 Record description XML File Transfer 20022 XML pain.001.001.02 15.11.2012 2 Change date Version Changed 2.6.2010 1.0 2.15 Payer s business id. Length can be 8, 9, 13 or 14 marks (so called long business

More information

XML ACCOUNT STATEMENT. Service Description

XML ACCOUNT STATEMENT. Service Description XML ACCOUNT STATEMENT Service Description October 2011 OY SAMLINK AB SERVICE DESCRIPTION 2 (18) Table of contents Table of contents Error! No table of contents entries found. OY SAMLINK AB SERVICE DESCRIPTION

More information

Format description XML SEPA Credit Transfer. Format Description

Format description XML SEPA Credit Transfer. Format Description Format description XML SEPA Credit Transfer Format Description CONTENTS 1 SEPA CT Import format 3 1.1 SEPA CT import format description 3 1.1.1 Description 3 1.1.2 General characteristics 3 1.1.3 Difference

More information

XML message for Payment Initiation Implementation Guideline. Version 1.02

XML message for Payment Initiation Implementation Guideline. Version 1.02 XML message for Payment Initiation Implementation Guideline Version 1.02 Version 1.02 Changes Updated 20131211 1) SEB specific rule added under tag 2.44 Equivalent Amount 2) To the tag 2.89 Regulatory

More information

ISO 20022 PAYMENT GUIDE. Messages: Pain.001.001.03 Pain.002.001.03

ISO 20022 PAYMENT GUIDE. Messages: Pain.001.001.03 Pain.002.001.03 ISO 20022 PAYMENT GUIDE Messages: Pain.001.001.03 Pain.002.001.03 20.11.2012 1 ISO 20022 Payment Guide Table of Contents 1 Background... 3 1.1 SEPA and ISO 20022... 3 1.2 Usage of ISO 20022 in Finland...

More information

OP's C2B SERVICES Pain 03. Payment Transfer Products

OP's C2B SERVICES Pain 03. Payment Transfer Products OP's C2B SERVICES Pain 03 Payment Transfer Products Customer Guidelines March 2015 2/104 Version Key Changes Changed section November 2012 added money orders 13 C2B money orders July 2013 updated payment

More information

Record description XML File Transfer Balance and Transaction list camt.052.001.02

Record description XML File Transfer Balance and Transaction list camt.052.001.02 Record description XML File Transfer Balance and Transaction list camt.052.001.02 15.11.2012 Page 2 of 14 Change date Version Changed 10.10.2011 1.0 07.02.2012 1.1 2.1 Identification kentän pituus muuttunut,

More information

OUTGOING PAYMENTS ISO 20022 APPLICATION GUIDELINE

OUTGOING PAYMENTS ISO 20022 APPLICATION GUIDELINE Version 2.5 13.4.2016 OUTGOING PAYMENTS ISO 20022 APPLICATION GUIDELINE 2 (54) CONTENTS VERSION INFORMATION... 4 1 OUTGOING PAYMENTS, ISO 20022 APPLICATION GUIDELINE... 5 1.1 ISO 20022 MESSAGE DESCRIPTION

More information

SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES

SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Doc: EPC301-07 25 November 2014 (Version 6.0 Approved) EPC SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the

More information

Payments Standards - Clearing and Settlement

Payments Standards - Clearing and Settlement UNIFI (ISO 20022) Message Definition Report Payments Standards - Clearing and Settlement Approved by UNIFI Payments SEG on 06 June 2006 Edition July 2006 Table Of Contents Overview... 1 What does this

More information

Payment Status Report

Payment Status Report Payment Status Report Implementation Guidelines Version 1.0 Beligian Finance Sector Federation rue d Arlon, 82 B-1040 Brussels http://www.febelfin.be T +32 2 507 68 11 F +32 2 888 68 11 2 Table of Contents

More information

OP's C2B SERVICES Pain 02. Payment transfer products

OP's C2B SERVICES Pain 02. Payment transfer products OP's C2B SERVICES Pain 02 Payment transfer products Customer Guidelines March 2015 2/105 Version Key Changes Changed section November 2012 added money orders 1.3 C2B money orders July 2013 updated payment

More information

SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES

SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Doc: EPC130-08 30 November 2012 (Version 7.0 Approved) EPC SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for

More information

Format Description. SWIFT MT103 Single Customer Credit Transfer

Format Description. SWIFT MT103 Single Customer Credit Transfer De Format Description SWIFT MT103 Single Customer Credit Transfer COLOPHON Title Format Description SWIFT MT103 Version, date 1.3, June 2015 On behalf of Contact address Corporate Client Channels Rabobank

More information

Danish Implementation Guideline for Common Global Implementation (CGI) Customer Payment Status Report

Danish Implementation Guideline for Common Global Implementation (CGI) Customer Payment Status Report Danish Implementation Guideline for Common Global Implementation (CGI) Customer Payment Status Report based on documentation from ISO 20022 Message Definition Report December 15th 2012 FINAL VERSION Page

More information

SEPA Credit Transfer Customer-to-Bank Implementation Guidelines for the Netherlands

SEPA Credit Transfer Customer-to-Bank Implementation Guidelines for the Netherlands SEPA Credit Transfer Customer-to-Bank Implementation Guidelines for the Netherlands Disclaimer These guidelines may be subject to changes. Utmost care has been taken to ensure the information in this publication

More information

SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES

SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Doc: EPC115-06 30 November 2012 (Version 7.0 Approved) EPC SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for implementing

More information

ISO 20022 ACCOUNT STATEMENT GUIDE. v 1.3

ISO 20022 ACCOUNT STATEMENT GUIDE. v 1.3 ISO 20022 ACCOUNT STATEMENT GUIDE v 1.3 4.10.2012 1 ISO 20022 Account Statement Guide Table of contents 1 Introduction... 3 2 General... 3 2.1 Effects on customer routines... 4 2.2 Activities... 4 3 Electronic

More information

OUTGOING PAYMENTS ISO 20022 APPLICATION GUIDELINE

OUTGOING PAYMENTS ISO 20022 APPLICATION GUIDELINE Version 1.94 13.4.2016 OUTGOING PAYMENTS ISO 20022 APPLICATION GUIDELINE Pain.001.001.02 Pain.002.001.02 2 (51) Sisällysluettelo MANUAL VERSION INFORMATION... 4 1 SEPA CREDIT TRANSFER, ISO 20022 APPLICATION

More information

Format description XML SEPA Credit Transfer

Format description XML SEPA Credit Transfer Format description XML SEPA Credit Transfer Rabo Cash Management Colophon Title Format description XML SEPA CT Version, date 1.7, April 30, 2014 Our reference Format description XML SEPA Credit Transfer

More information

SEPA Direct Debit Initiation Customer-to-Bank Implementation Guidelines for the Netherlands

SEPA Direct Debit Initiation Customer-to-Bank Implementation Guidelines for the Netherlands SEPA Direct Debit Initiation Customer-to-Bank Implementation Guidelines for the Netherlands CORE and Business-to-Business Implementation Guidelines Disclaimer These guidelines may be subject to changes.

More information

SEPA DATA MODEL. Reason for Issue Approved by the EPC Plenary on 13 December 2006

SEPA DATA MODEL. Reason for Issue Approved by the EPC Plenary on 13 December 2006 Doc: EPC029-06 (Version 2.2) 13 December2006 OITS SG SEPA DATA MODEL Abstract Document Reference Issue This document sets out the SEPA Data Model which is referred to in the SEPA Credit Transfer and Direct

More information

BEST client format supported by KB (valid from 28th November 2015)

BEST client format supported by KB (valid from 28th November 2015) supported by KB (valid from 28th November 2015) 1/19 List of contents: 1 Introduction... 4 1.1 Purpose of this document... 4 1.2 Characteristics of BEST format... 4 2 Formal check of BEST format... 4 2.1

More information

SEPA DIRECT DEBIT SCHEME IMPLEMENTATION GUIDELINES

SEPA DIRECT DEBIT SCHEME IMPLEMENTATION GUIDELINES Doc: EPC114-06 19 June 2007 (Version 2.3 ) OITS SG SEPA DIRECT DEBIT SCHEME IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the SEPA rules for implementing the direct

More information

SEPA formats - an introduction to XML. version September 2013. www.ing.be/sepa

SEPA formats - an introduction to XML. version September 2013. www.ing.be/sepa Financial Supply Chain SEPA SEPA formats - an introduction to XML version September 2013 www.ing.be/sepa INTRODUCTION 1 INTRODUCTION TO XML 2 What is XML? 2 What is a root element? 2 What are the specifications

More information

ISO 20022 Message Implementation Guide for Payment Initiation

ISO 20022 Message Implementation Guide for Payment Initiation ISO 20022 Message Implementation Guide for Payment Initiation Pain001 Pain002 Version: 1.5 Issue date: 16 November 2015 Author: Swedbank Table of Contents 1. Introduction 2. Customer Credit Transfer Initiation

More information

HSBC Your Guide to SEPA. Capitalising on the opportunities

HSBC Your Guide to SEPA. Capitalising on the opportunities HSBC Your Guide to SEPA Capitalising on the opportunities Executive Summary Developed by the European Payments Council, the Single Euro Payments Area or SEPA expands on the vision behind the Euro to establish

More information

Online Banking Record Descriptions

Online Banking Record Descriptions Record s hotline@sydbank.dk Page 1 of 65 Contents Introduction... 3 Sydbank format... 3 Format descriptions... 5 of fixed-length records... 5 of variable-length records... 6 Payment start... 7 IB000000000000...

More information

Customer Statement - MT940 with Structured Information To Account Owner

Customer Statement - MT940 with Structured Information To Account Owner General Information The MT940 customer statement message is an electronic message containing financial statement information for customers concerning their accounts. Danske Bank can send a MT940 either

More information

Format Description SWIFT MT940 Structured

Format Description SWIFT MT940 Structured Format Description SWIFT MT940 Structured Rabo Cash Management Colophon Title Format Description SWIFT MT940 Structured Version, date 3.331, November 2014 On behalf of Zakelijke Klantkanalen Contact address

More information

Deutsche Bank Global Transaction Banking. Internet Bankieren. Entering Payments and Collections. www.deutschebank.nl

Deutsche Bank Global Transaction Banking. Internet Bankieren. Entering Payments and Collections. www.deutschebank.nl Deutsche Bank Global Transaction Banking Internet Bankieren Entering Payments and Collections www.deutschebank.nl Internet Bankieren Entering Payments and Collections 2 Entering payments and collections

More information

User's manual for OTPdirekt Internet Banking. v.1.0

User's manual for OTPdirekt Internet Banking. v.1.0 User's manual for OTPdirekt Internet Banking v.1.0 1 Contents General... 4 Log in... 4 Logging out... 4 Home page... 5 Accounts... 5 Accounts - Overview of movements... 6 Accounts - OTPdirekt transactions...

More information

Implementation of ISO 20022: starter kit for software partners

Implementation of ISO 20022: starter kit for software partners Insert images: Swiss Post menu > image > insert image. For more images go to www.brandingnet.ch Technical details Full screen image size W 25.4 cm x H 19.05 cm equals W 1500 pixels x H 1125 pixels Resolution

More information

SEPA - Frequently Asked Questions

SEPA - Frequently Asked Questions SEPA - Frequently Asked Questions Contents SEPA Overview Questions... 2 What is SEPA?... 2 What is the aim of SEPA?... 3 Where did SEPA come from?... 3 What countries are included in SEPA?... 3 What currencies

More information

Format Description XML SEPA CT

Format Description XML SEPA CT Format Description XML SEPA CT SWIFT FileAct Rabobank Format Description XML SEPA CT - SWIFT FileAct November 2015 Version 2.2 1 Contents SEPA CT Import Format 3 SEPA CT Structure 4 Segment description

More information

pg. 2 pg. 6 pg.8 pg. 20

pg. 2 pg. 6 pg.8 pg. 20 SEPA Extra Payment news pg. 2 pg. 6 pg.8 pg. 20 SEPA harmonises payments The account number format when SEPA is valid SEPA will cause changes to material transfer services Is your company ready for SEPA?

More information

TERMS AND CONDITIONS APPLICABLE TO CREDIT INSTITUTIONS

TERMS AND CONDITIONS APPLICABLE TO CREDIT INSTITUTIONS ERSTE BANK HUNGARY ZRT TERMS AND CONDITIONS APPLICABLE TO CREDIT INSTITUTIONS Effective from: 01 September 2014 1. General Provisions 1.1. These Terms and Conditions (hereinafter TC ) apply to all correspondent

More information

SEPA. Frequently Asked Questions

SEPA. Frequently Asked Questions SEPA Frequently Asked Questions Page 1 of 13 Contents General SEPA Questions... 4 What is SEPA?... 4 What is the aim of SEPA?... 4 What are the benefits of SEPA?... 4 What countries are included in SEPA?...

More information

Foreign payment orders

Foreign payment orders p. 1 Foreign payment orders The Foreign payment orders bank standard deals with the electronic exchange of payment orders in euro or in foreign currencies transmitted by the customer to his bank. For payments

More information

LECTURE No.9 INSTRUMENTS OF PAYMENT

LECTURE No.9 INSTRUMENTS OF PAYMENT LECTURE No.9 INSTRUMENTS OF PAYMENT Cash and cash instruments The cashier s work consists in receiving cash and cash instruments such as cheques and other instruments ( documents of title to cash ) in

More information

SEPA Credit Transfer. Readiness Checklist

SEPA Credit Transfer. Readiness Checklist SEPA Credit Transfer Readiness Checklist This document is published by Bank of Ireland, and both it, and its contents, are the property of Bank of Ireland. This document may not be reproduced or further

More information

Format Description MT940. Rabo Cash Management

Format Description MT940. Rabo Cash Management Format Description MT940 Rabo Cash Management COLOFON Title Format Description MT940 Version, date 2.4, January 2013 On behalf of Contact address FL-Services Rabobank Nederland, Croeselaan 18, Postbus

More information

TERMS AND CONDITIONS OF PAYMENT ORDER IN FOREIGN EXCHANGE TRANSACTIONS AT PKO BP SA BANK

TERMS AND CONDITIONS OF PAYMENT ORDER IN FOREIGN EXCHANGE TRANSACTIONS AT PKO BP SA BANK TERMS AND CONDITIONS OF PAYMENT ORDER IN FOREIGN EXCHANGE TRANSACTIONS AT PKO BP SA BANK TABLE OF CONTENTS SECTION 1 General provisions... 1 I. General rules for payment execution in foreign exchange transactions...

More information

User Manual Internet Banking Enter and Send Orders

User Manual Internet Banking Enter and Send Orders This manual of ABN AMRO Internet Banking describes how to enter payment orders, stock orders, investment orders and how to send your orders to the bank. You can enter a maximum of 45 orders for dispatch.

More information

499.35 en (pf.ch/dok.pf) 11.2015 PF. EPO manual Electronic payment order via file transfer

499.35 en (pf.ch/dok.pf) 11.2015 PF. EPO manual Electronic payment order via file transfer 499.35 en (pf.ch/dok.pf) 11.2015 PF EPO manual Electronic payment order via file transfer Customer support Customer support for EPO Consulting & Sales Phone +41 848 888 900 (CHF 0.08/min. from a landline)

More information

Swedish Common Interpretation of ISO 20022 Payment Messages. Appendix 1: Common Payment Types in Sweden

Swedish Common Interpretation of ISO 20022 Payment Messages. Appendix 1: Common Payment Types in Sweden Swedish Common Interpretation of ISO 20022 Payment Messages Appendix 1: 2 (27) Version Date Changes 0.1 2013-12-11 Initial version 1.0 2014-02-10 Updates after external review Page 5: Added that BG/PG

More information

SEPA Direct Debit Implementation Guide. Version 1.7

SEPA Direct Debit Implementation Guide. Version 1.7 SEPA Direct Debit Implementation Guide Version 1.7 DANSKE BANK Table of contents 1 Change log... 3 2 Purpose of this document... 4 2.1 Target groups... 4 2.2 Help... 4 3 Introduction to SEPA Direct Debit...

More information

White Paper on Extended Remittance Information (ERI) and Payment Notification

White Paper on Extended Remittance Information (ERI) and Payment Notification White Paper on Extended Remittance Information (ERI) and Payment Notification (Version 1.0, February 2015) Note: Relevant regulations and any applicable legislation take precedence over the guidance notes

More information

Intra-day payment Frequently asked questions

Intra-day payment Frequently asked questions Intra-day payment Frequently asked questions Contents 1. THE MEANING, advantages and scope of intra-day payment... 3 1.1. What does the launch of intra-day payment mean?... 3 1.2. What advantages does

More information

Make payments. Bankline support guides: In this guide. How to make a standard domestic payment. Did you know? Page 1

Make payments. Bankline support guides: In this guide. How to make a standard domestic payment. Did you know? Page 1 Bankline support guides: Make payments In this guide Learn how to make standard domestic payments and CHAPS payments. Learn how to transfer money between your accounts. Learn how to make international

More information

Spanish legacy branch code 4 numbers. Spanish legacy bank code 4 numbers

Spanish legacy branch code 4 numbers. Spanish legacy bank code 4 numbers SEPA in Spain Useful links Spanish official SEPA website (in Spanish language) http://www.sepaesp.es/ National Central Bank of Spain www.bde.es/bde/en Official Migration Guide for the Spanish market Download

More information

Creating international money transfers

Creating international money transfers Creating international money transfers About this guide This guide takes you through the process of creating international money transfers (IMT) through CommBiz. Important information If you are making

More information

SEPA Direct Debit PAIN.008.001.02 XML File Structure

SEPA Direct Debit PAIN.008.001.02 XML File Structure SEPA Direct Debit PAIN.008.001.02 XML File Structure This document is published by Bank of Ireland, and both it, and its contents, are the property of Bank of Ireland. This document may not be reproduced

More information

KM client format supported by KB valid from 26 March 2007

KM client format supported by KB valid from 26 March 2007 supported by KB valid from 26 March 2007 1/15 VRSION 1.2. UPDATD: 13.12.2005. 1 Introduction...2 1.1 Purpose of this document...2 1.2 Characteristics of the KM format...2 2 Formal check of KM format...3

More information

Bankline internet banking import file layout user guide

Bankline internet banking import file layout user guide Bankline internet banking import file layout user guide Bankline internet banking import file layout user guide 2 Contents 1. Introduction to Bankline import...3 1.1 What is Bankline import?...3 1.2 How

More information

Internet Banking for Business

Internet Banking for Business INTERNET BANKING FOR BUSINESS Information you need to know about importing transaction files into Internet Banking for Business For more info bnz.co.nz Internet Banking for Business. This guide provides

More information

RF Creditor Reference

RF Creditor Reference RF Creditor Reference Facilitating full end-to-end straight-through payment processing version 1.0, May 2010 RF Expert Group 2 (36) Page RF Creditor Reference... 1 Facilitating full end-to-end straight-through

More information

Hal E-Bank Foreign payments (Format of export/import files)

Hal E-Bank Foreign payments (Format of export/import files) Hal E-Bank Foreign payments (Format of export/import files) Hal E-Bank Foreign payments: format of export/import files Version: 17.x.x.20 Author: HALCOM d.d., Ljubljana Editor: HALCOM a.d., Beograd, July

More information

Standards MX Message Implementation Guide and Rule Book

Standards MX Message Implementation Guide and Rule Book Solutions SWIFT for Corporates Standards MX Message Implementation Guide and Rule Book Payment Initiation and Account Reporting This document describes and references a set of rules and guidelines you

More information

SEPA CREDIT TRANSFER SCHEME RULEBOOK

SEPA CREDIT TRANSFER SCHEME RULEBOOK EPC125-05 Version 7.2 Approved Date issued: 4 March 2015 Date effective: 3 April 2015 SEPA CREDIT TRANSFER SCHEME RULEBOOK Conseil Européen des Paiements AISBL Cours Saint-Michel 30 B 1040 Brussels Tel:

More information

SEPA CREDIT TRANSFER SCHEME RULEBOOK

SEPA CREDIT TRANSFER SCHEME RULEBOOK EPC125-05 Version 4.1 approved Date issued: 1 November 2010 Date effective: 1 November 2010 SEPA CREDIT TRANSFER SCHEME RULEBOOK Conseil Européen des Paiements AISBL Av. de Tervueren 12 B 1040 Brussels

More information

SEPA Customer File Formats-Definition Proposals

SEPA Customer File Formats-Definition Proposals SEPA Customer File Formats-Definition Proposals Purpose: The purpose of this document is to agree customer file formats for both direct debits (DDs) and credit transfers (CTs). The aim is to ensure all

More information

Guide. 1 Dec 2010. Introduction of the global Structured Creditor Reference in Finnish companies. 1 December 2010

Guide. 1 Dec 2010. Introduction of the global Structured Creditor Reference in Finnish companies. 1 December 2010 1 Dec 2010 Guide Introduction of the global Structured Creditor Reference in Finnish companies 1 December 2010 Federation of Finnish Financial Services Contents Guide Introduction of the global Structured

More information

Payment Instructions Frequently Asked Questions. global

Payment Instructions Frequently Asked Questions. global global Payment Instructions Frequently Asked Questions The following are some frequently asked questions about payment instructions. If you have additional queries or would like more information about

More information

Single Euro Payments Area (SEPA) with Oracle E-Business Suite for German Banks

Single Euro Payments Area (SEPA) with Oracle E-Business Suite for German Banks Single Euro Payments Area (SEPA) with Oracle E-Business Suite for German Banks DOAG SIG-Meeting E-Business Suite Vienna, 27-SEP-2010 Daphne Schmitz Copyright 2010, Toshiba Corporation. Information Systems

More information

SEPA Reason Codes. Direct Debit Customer to Bank Implementation Guidelines

SEPA Reason Codes. Direct Debit Customer to Bank Implementation Guidelines SEPA Reason s The SEPA reason codes in this document are sourced from the following European Payments Council Implementation Guideline documentation which detail the customer-to-bank and inter-bank formats

More information

Implementing SEPA in Belgiu m

Implementing SEPA in Belgiu m SEPA Country Guide Belgium Implementing SEPA in Belgiu m All you need to know for a successful SEPA migration Introduction This document provides an overview of all the country specific information you

More information

AX 2012 R3 SEPA (ISO 20022 XML) Credit transfer and direct debit payments Date: March 3 rd, 2015

AX 2012 R3 SEPA (ISO 20022 XML) Credit transfer and direct debit payments Date: March 3 rd, 2015 Contents Introduction... 2 Setup Credit Transfer... 3 Export the xml stylesheet for the payment format from AOT... 3 Setup a batch job to generate SEPA files... 4 Setup Outbound ports for electronic payments...

More information

480.84 en (pf.ch/dok.pf) 10.2015 PF. Manual PostFinance ISO messages for banks [pacs messages]

480.84 en (pf.ch/dok.pf) 10.2015 PF. Manual PostFinance ISO messages for banks [pacs messages] 480.84 en (pf.ch/dok.pf) 10.2015 PF Manual PostFinance ISO messages for banks [pacs messages] Customer service Enquiries concerning service ISO 20022 for banks PostFinance Ltd Customer Service Banks Mingerstrasse

More information

ERP SEPA readiness checklist

ERP SEPA readiness checklist ERP SEPA readiness checklist version July 2013 www.ingsepa.com Financial Supply Chain SEPA This list contains 11 questions to determine the level of SEPA-readiness of an ERP 1. The first 3 questions deal

More information

for CONSUMERS Information on the SINGLE EURO PAYMENTS AREA

for CONSUMERS Information on the SINGLE EURO PAYMENTS AREA Version 5.0 - February 2014 for CONSUMERS Information on the SINGLE EURO PAYMENTS AREA All you need to know about SEPA EPC Shortcut Series* Shortcut to SEPA Shortcut to the SEPA Direct Debit Schemes Shortcut

More information

ELECTRONIC BANKING. RFT MT101 File Format Description Ver. 2009-09-28

ELECTRONIC BANKING. RFT MT101 File Format Description Ver. 2009-09-28 ELECTRONIC BANKING RFT MT101 File Format Description Ver. 2009-09-28 CONTENTS: 1. RFT MT101 File Format Description 3 2. Detailed MT101 File Format Description 3 2.1 Key to description of the records 3

More information

EBS204 Version 1 Published November 1996. EBS204 Version 2 Published July 2000. EBS204 Version 3 Published February 2001

EBS204 Version 1 Published November 1996. EBS204 Version 2 Published July 2000. EBS204 Version 3 Published February 2001 EUROPEAN COMMITTEE FOR BANKING STANDARDS IBAN: INTERNATIONAL BANK ACCOUNT NUMBER EBS204 V3 FEBRUARY 2001 Document history EBS204 Version 1 Published November 1996 EBS204 Version 2 Published July 2000 EBS204

More information

Schedule of fees and charges for business customers

Schedule of fees and charges for business customers Schedule of fees and charges for business customers Effective 23 February 2015 Bank of Ireland is regulated by the Central Bank of Ireland. 37-560RU.35(02/15) Schedule of fees and charges Contents Introduction

More information

Electronic foreign currency payments, LUM2

Electronic foreign currency payments, LUM2 Electronic foreign currency payments, LUM2 Contents 1 Electronic foreign currency payment service... 3 2 Service agreement and testing... 3 2.1 Agreement... 3 2.2 Testing... 4 2.2.1 File transfer and processing...

More information

Format description of MT103 (Multicash PLA) foreign payment file.

Format description of MT103 (Multicash PLA) foreign payment file. Format description of MT103 (Multicash PLA) foreign payment file. 1 General information about MT103 file This document explains formats of MT103 file - used to import International / Foreign Currency Order

More information

SEPA CREDIT TRANSFER SCHEME RULEBOOK

SEPA CREDIT TRANSFER SCHEME RULEBOOK EPC125-05 Version 8.2 Date issued: 03 March 2016 Date effective: 01 April 2016 SEPA CREDIT TRANSFER SCHEME RULEBOOK Conseil Européen des Paiements AISBL Cours Saint-Michel 30 B 1040 Brussels Tel: +32 2

More information

Single Euro Payments Area

Single Euro Payments Area Single Euro Payments Area Overview SEPA (Single Euro Payments Area) is a European payments initiative which aims to create one single, integrated, standardised payments market in Europe. It is an area

More information

TERMS AND CONDITIONS OF CASH TRANSACTIONS IN DOMESTIC TRANSACTIONS AT PKO BP SA BANK

TERMS AND CONDITIONS OF CASH TRANSACTIONS IN DOMESTIC TRANSACTIONS AT PKO BP SA BANK TERMS AND CONDITIONS OF CASH TRANSACTIONS IN DOMESTIC TRANSACTIONS AT PKO BP SA BANK TABLE OF CONTENTS Section 1... 1 GENERAL PROVISIONS... 1 I. Acceptance and execution of the payment order by the Bank...

More information

1.1. Overview... 5 1.2. Direct credits... 6 1.3. Direct debits... 9 1.4. Nab direct credits... 12

1.1. Overview... 5 1.2. Direct credits... 6 1.3. Direct debits... 9 1.4. Nab direct credits... 12 1.1. Overview... 5 1.2. Direct credits... 6 1.3. Direct debits... 9 1.4. Nab direct credits... 12 2.1. Overview... 16 2.2. Credit card transaction... 17 2.3. Credit card response... 20 3.1. Overview...

More information

Format description XML SEPA Credit Transfer

Format description XML SEPA Credit Transfer Format description XML SEPA Credit Transfer Version, date Project 1.4, 24 April 2013 Rabo Cash Management 1 Colophon Title Format description XML SEPA CT Version, date 1.4, 24 April 2013 Our reference

More information

in Fr a nce Introduction

in Fr a nce Introduction in Fr a nce Introduction This document provides an overview of all the country specific information you need to successfully implement your migration to SEPA in France. Intending to provide a global picture

More information

Information Concerning the Use of the SEPA Payment Schemes

Information Concerning the Use of the SEPA Payment Schemes DEUTSCHES PATENT- UND MARKENAMT 80297 München Telephone: +49 89 2195-0 Telephone enquiries: +49 89 2195-3402 Internet: http://www.dpma.de Beneficiary: Bundeskasse Halle/DPMA IBAN: DE84 7000 0000 0070 0010

More information

SEPA. Changes in the Payment System Implementation of the European SEPA Regulations for Kuna and Euro Payments

SEPA. Changes in the Payment System Implementation of the European SEPA Regulations for Kuna and Euro Payments SEPA Changes in the Payment System Implementation of the European SEPA Regulations for Kuna and Euro Payments SEPA The Single Euro Payments Area (SEPA) stands for a European Union (EU) payments integration

More information

Deutsche Bank www.deutschebank.nl. Deutsche Bank MT940/942 format specifications

Deutsche Bank www.deutschebank.nl. Deutsche Bank MT940/942 format specifications Deutsche Bank www.deutschebank.nl Deutsche Bank MT940/942 format specifications Content 1. Introduction 3 2. SWIFT MT940 Customer Statement Message 4 2.1 MT940 Format 4 2.2 MT940 Tag & (sub)field Specifications

More information

HANDBOOK FOR THE STANDARDISATION AND APPLICATION OF

HANDBOOK FOR THE STANDARDISATION AND APPLICATION OF BANKING COMMITTEE FOR THE STANDARDISATION AND APPLICATION OF IBAN HANDBOOK FOR THE STANDARDISATION AND APPLICATION OF Basic Bank Account Number (BBAN) And International Bank Account Number (IBAN) IN CYPRUS

More information

This translation has been prepared with the greatest possible care; however, in case of doubt, the German text is the authoritative version.

This translation has been prepared with the greatest possible care; however, in case of doubt, the German text is the authoritative version. The Deutsche Bundesbank s technical specifications for the clearing and settlement of interbank SEPA credit transfers via the RPS ( SCT/BCT/SCL technical specifications ) Version 2.4 valid from 30 September

More information

Functional specification for Payments Corporate egateway

Functional specification for Payments Corporate egateway Functional specification for Payments Corporate egateway 2(53) Page Table of contents 1 Introduction... 5 1.1 Explanation of definitions for EDIFACT & XML ISO20022 6 1.2 Level descriptions for EDIFACT

More information

NATIONAL BANK OF ROMANIA

NATIONAL BANK OF ROMANIA NATIONAL BANK OF ROMANIA Unofficial translation Regulation regarding the usage of the IBAN codes in Romania Having regard to the provisions of Article 2, paragraph (2) and Article 23 of the Law no. 101/1998

More information

Impact of SEPA on CODA2.3 for SEPA credit transfer (SCT) version April 2013. ing.be/sepa

Impact of SEPA on CODA2.3 for SEPA credit transfer (SCT) version April 2013. ing.be/sepa Financial Supply Chain SEPA Impact of SEPA on CODA2.3 for SEPA credit transfer (SCT) version April 2013 ing.be/sepa Introduction 1 How does migration to SEPA credit transfer affect CODA2.3? 2 Global debit

More information

SEPA Creditors Guide. SEPA Direct Debit Core Scheme. Version 1.3 Final Page 1 of 38

SEPA Creditors Guide. SEPA Direct Debit Core Scheme. Version 1.3 Final Page 1 of 38 SEPA Creditors Guide SEPA Direct Debit Core Scheme Version 1.3 Final Page 1 of 38 Log of Revisions to the SDD Creditors Guide Version number Version1.1 Brief description of revision Comprehensive guide

More information