XML SEPA client format (PDF file) - Komerční banka

XML SEPA client format (PDF file) - Komerční banka XML SEPA client format (PDF file) - Komerční banka

09.02.2015 Views

XML SEPA client format in KB otherwise it will be rejected). 2.23 CreditTransferTransactionInfo [1..n] compulsory rmation 2.24 PaymentIdentification [1..1] compulsory 2.25 InstructionIdentification [0..1] Text Unique identification for KB (duplicate detection); if not specified, information of the EndToEnd field will be used. 2.26 EndToEndIdentification [1..1] Text compulsory Handed over to the partner; if InstrId is not specified, this value is used for KB purpose: InstrId = EndToEndId. 2.27 PaymentTypeInformation [0..1] 2.28 InstructionPriority [0..1] Code If it is stated "HIGH" = urgent payment. If it is stated "NORM" or is blank = express payment. 2.29 ServiceLevel [0..1] 2.30 Code [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. 2.37 Amount [1..1] compulsory 2.38 InstructedAmount [1..1] Amount Amount in EUR (required) Currencies other than EUR will be rejected in KB; required. 2.46 ChargeBearer [0..1] Code Only “SLEV” can be used for SEPA payments. Not compulsory; KB uses it by default. 2.55 CreditorAgent [0..1] + BIC - the bank must be SEPA-compliant; required. 2.57 Creditor [0..1] + Name, address - required; identification (optional) 2.58 CreditorAccount [0..1] + IBAN - required 2.59 UltimateCreditor [0..1] + Will be transferred by KB when Rulebook 3.2. is officially approved; clients will be informed on KB website. 2.84 RemittanceInformation [0..1] 2.85 Unstructured [0..n] Text Details of payment (optional) 4. Rules according to ISO 20022 for selected tags used in KB FOR Header: 1.1 MessageIdentification Presence: [1..1] Definition: Point to point reference assigned by the instructing party and sent to the next party in the chain to unambiguously identify the message. s Komerční banka, a. s., registered office: Praha 1, Na Příkopě 33, 969, Postcode 114 07, IČ (Company ID): 45317054 REGISTERED IN THE COMPANIES REGISTER KEPT BY PRAGUE MUNICIPAL COURT, B SECTION, RECORD 1360 6/21

XML SEPA client format in KB Usage: The instructing party has to make sure that 'MessageIdentification' is unique per instructed party for a pre-agreed period. Data Type: Max35Text Format: maxLength: 35 minLength: 1 1.2 CreationDateTime Presence: [1..1] Definition: Date and time at which a (group of) payment instruction(s) was created by the instructing party. Data Type: ISODateTime 1.5 NumberOfTransactions Presence: [1..1] Definition: Number of individual transactions contained in the message. Data Type: Max15NumericText Format: [0-9]{1,15} 1.6 ControlSum Presence: [0..1] Definition: Total of all individual amounts included in the message, irrespective of currencies. Data Type: DecimalNumber Format: fractionDigits: 17 totalDigits: 18 1.7 Grouping Presence: [1..1] 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 InitiatingParty Presence: [1..1] 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 PartyIdentification8 element(s): FOR Payments Or Message Item Mult. Represent./Type Name [0..1] Text PostalAddress [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 5 - Address in KB. 2.0 PaymentInformation 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 PaymentInformation block is composed of the following PaymentInstructionInformation1 element(s): Index OR Message item Mult. Presentation Used in KB 2.1 PaymentInformationIdentification [0..1] Text 2.2 PaymentMethod [1..1] Code TRF 2.3 PaymentTypeInformation [0..1] 2.13 RequestedExecutionDate [1..1] DateTime DATE 2.15 Debtor [1..1] + Address and name is not taken over, only identification is, if specified. 2.16 DebtorAccount [1..1] + IBAN currency need s Komerční banka, a. s., registered office: Praha 1, Na Příkopě 33, 969, Postcode 114 07, IČ (Company ID): 45317054 REGISTERED IN THE COMPANIES REGISTER KEPT BY PRAGUE MUNICIPAL COURT, B SECTION, RECORD 1360 7/21

<strong>XML</strong> <strong>SEPA</strong> <strong>client</strong> <strong>format</strong> in KB<br />

Usage: The instructing party has to make sure that 'MessageIdentification' is unique per instructed party for<br />

a pre-agreed period.<br />

Data Type: Max35Text<br />

Format: maxLength: 35<br />

minLength: 1<br />

1.2 CreationDateTime <br />

Presence: [1..1]<br />

Definition: Date and time at which a (group of) payment instruction(s) was created by the instructing party.<br />

Data Type: ISODateTime<br />

1.5 NumberOfTransactions <br />

Presence: [1..1]<br />

Definition: Number of individual transactions contained in the message.<br />

Data Type: Max15NumericText<br />

Format: [0-9]{1,15}<br />

1.6 ControlSum <br />

Presence: [0..1]<br />

Definition: Total of all individual amounts included in the message, irrespective of currencies.<br />

Data Type: DecimalNumber<br />

Format: fractionDigits: 17<br />

totalDigits: 18<br />

1.7 Grouping <br />

Presence: [1..1]<br />

Definition: Indicates whether common accounting in<strong>format</strong>ion in the transaction is included once for all transactions or<br />

repeated for each single transaction.<br />

In KB only one possibility: single – „SNGL“<br />

1.8 InitiatingParty <br />

Presence: [1..1]<br />

Definition: Party initiating the payment. In the payment context, this can either be the debtor (in a credit transfer), the<br />

creditor (in a direct debit), or the party that initiates the payment on behalf of the debtor or creditor.<br />

Type: This message item is composed of the following PartyIdentification8 element(s):<br />

FOR Payments<br />

Or Message Item Mult. Represent./Type<br />

Name [0..1] Text<br />

PostalAddress [0..1] Not taken over or<br />

validated in KB. The<br />

address administered in<br />

DB DCS is used. If to be<br />

sent, see the structure<br />

description in chapter 5<br />

- Address in KB.<br />

2.0 PaymentIn<strong>format</strong>ion <br />

Presence: [1..n]<br />

Definition: Set of characteristics that applies to the debit side of the payment transactions included in the credit transfer<br />

initiation.<br />

Type: The PaymentIn<strong>format</strong>ion block is composed of the following PaymentInstructionIn<strong>format</strong>ion1 element(s):<br />

Index OR Message item Mult. Presentation Used in KB<br />

2.1 PaymentIn<strong>format</strong>ionIdentification [0..1] Text<br />

2.2 PaymentMethod [1..1] Code TRF<br />

2.3 PaymentTypeIn<strong>format</strong>ion [0..1]<br />

2.13 RequestedExecutionDate [1..1] DateTime DATE<br />

2.15 Debtor [1..1] + Address and name<br />

is not taken over,<br />

only identification is,<br />

if specified.<br />

2.16 DebtorAccount [1..1] + IBAN currency need<br />

s<br />

<strong>Komerční</strong> <strong>banka</strong>, a. s., registered office:<br />

Praha 1, Na Příkopě 33, 969, Postcode 114 07, IČ (Company ID): 45317054<br />

REGISTERED IN THE COMPANIES REGISTER KEPT BY PRAGUE MUNICIPAL COURT, B SECTION, RECORD 1360<br />

7/21

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!