09.02.2015 Views

EDI BEST client format supported by KB valid from ... - Komerční banka

EDI BEST client format supported by KB valid from ... - Komerční banka

EDI BEST client format supported by KB valid from ... - Komerční banka

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

k<br />

3. line: Issuer with “IS=” prefix (such as<br />

“IS=Licensing authority in Prague”<br />

11. Filler 513 397 X(513) reserve<br />

12. File sentinel 2 910 X(2) CRLF record end character<br />

<strong>EDI</strong> <strong>BEST</strong> <strong>client</strong> <strong>format</strong><br />

2.2.3 Difference between standard Foreign payment and SEPA payment<br />

In both cases they represent foreign payment system and arrangement of transferal of the<br />

payment generated <strong>by</strong> the <strong>client</strong> to the partner, and receipt of the foreign partner plus transferal<br />

to his <strong>client</strong>.<br />

If the <strong>client</strong>’s partner is located in the EU zone and the <strong>client</strong> is paying in EUR, he can use a<br />

favourable type of SEPA (Single European Payment Area) payment and inter-banking<br />

agreements between banks adopting this type of payment.<br />

For both payment types, only SWIFT characters are permitted (if another character is<br />

transferred, it will be converted).<br />

• Standard foreign payment<br />

o<br />

Record 02 with standard payment data - no changes. (The<br />

“Y” character is not located in the offset. Of course, this form<br />

can still be used for payments even if the partner is based in<br />

the EU zone.<br />

• SEPA payment<br />

o Record 02 with standard payment data of FPO and marked<br />

with the SEPA sign. If the record is marked, it is a SEPA<br />

payment that must conform to the following requirements:<br />

Field of offset Required <strong>valid</strong>ation (if not conforming, the payment is<br />

SEPA<br />

rejected)<br />

payment<br />

Payment 59 Only EUR<br />

currency code<br />

Payer of 77 Only SLV<br />

charges<br />

ISO currency 96 With no <strong>valid</strong>ation, the currency downloaded in the DB is taken<br />

code of<br />

account for<br />

charges<br />

Express<br />

payment<br />

99 The payment cannot be entered as Urgent. Everything else is<br />

projected as normal, i.e. Express.<br />

Payer’s 170 With no <strong>valid</strong>ation, the currency downloaded in the DB is taken<br />

currency<br />

SWIFT code 278 If 8 characters are transferred, “XXX” is added <strong>from</strong> the right and<br />

of<br />

then <strong>valid</strong>ation for the BIC library is carried out.<br />

beneficiary’s<br />

bank<br />

Ben. account 594 IBAN form<br />

no.<br />

Payment <strong>by</strong> 908 Must not be “Y”<br />

cheque sign<br />

SEPA sign 909 Must be “Y”<br />

2.2.4 Sorting of SEPA optional data<br />

• Transferred SEPA payment 1.<br />

o<br />

Record 02 with standard payment data of FPO and marked<br />

with SEPA sign<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<br />

ID): 45317054<br />

19/46<br />

<strong>valid</strong> <strong>from</strong> 12th June 2010

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

Saved successfully!

Ooh no, something went wrong!