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
k OUR BEN SHA BN1 BN2 STD SLV Other OUR BEN SHA SHA BEN SHA SLV SHA EDI BEST client format Clients not using EDI can use this format in Profibanka and Direct channel services directly from their accounting systems instead of the BEST format (domestic and foreign payments, statements and debit and credit advise). Apart from the actual EDI server, cancellation batches can only be sent via Direct channel. In this case, an identical Creation date is necessary in addition to Identification generated by the client (Item sequential number). 1.3 Char set for UNOA syntax level Texts in EDI subsets are in the UNOA format - capital characters of the English alphabet. UNOA level allows the characters specified in the following table to be used: capital characters A to Z numbers 0 to 9 space dot . comma , minus - left parenthesis ( right parenthesis ) slash / equal sign = exclamation mark ! quotation marks " percent sign % asterisk * semi-colon ; “less than” sign < “greater than” sign > Reserved characters are those used as separators and limiters of message elements and segments. In spite of the fact that these can be changed and the change declared in the UNA segment, KB shall use those defined by the standard. For the future, the * (asterisk) sign is considered to be used as another separator. apostrophe ´ segment end character plus + data element separator dot . decimal separator colon : partial data element separator question mark exemption character • Code page • DC and EDI - requires windows-1250 – Windows Eastern European (Windows CRLF line feed) • PCB - requires windows-1250 – Windows Eastern European (PCB line feed can be managed by both CRLF (#13#10) and Unix LF (#10) or MAC CR (#13) • MC – requires CP852 Komerční banka, a.s., registered office: Praha 1, Na Příkopě 33, 969, Postcode 114 07, IČ (Company ID): 45317054 4/46 valid from 12th June 2010
k EDI BEST client format 1.3.1 Other services • BEST format includes: • Domestic payment orders (Import): accounting and non-accounting data • Foreign payment orders (Import): accounting and non-accounting data derived from the needs of SWIFT messages in foreign payment orders. • Electronic statement (Export): accounting and non-accounting data provided by printout (paper) statements and all identification data and notes related to transactions. • Error report (Export) - EDI clients only • Advice (Export) - accounting and non-accounting data of transactions processed during the business day 1.4 Main characteristics of operation with EDI batches IMPORT • The client transfers a batch of payment orders in the UN/EDIFACT format to the bank. EDI server in the 24x7 mode converts received batches (converts them into the EDI_BEST format) and sends a batch to AS. AS will send the validation result to the specified directory; from here, the file is immediately picked up, converted into the UN/EDIFACT format - BANSTA subset and sent to the client. A report detects the 1st found error for a single payment. This way, the client receives a response for each sent payment and can diagnose, based on OK / NOK status, whether the payment was formally correct and accepted. EXPORT In case of EDI, it is not the client who initializes downloading of the statement; however, the bank guarantees that the data for the client will be distributed as soon as it is available. • KB will place both the statements and reports in the specified directory; from here, the file is immediately picked up, converted into the UN/EDIFACT format - FINSTA and BANSTA or CREMUL and DEBMUL subsets and sent to the client. This means the client will receive the accounting response for every formally accepted payment. The “OK” accounting is included in FINSTA, the “NOK” accounting with rejection reasons specified is included in the morning BANSTA. In addition, ADVICE will be downloaded according to requested timing of individual clients. 1.5 SEPA payments - new non-accounting optional data SEPA - Single European Payment Area SEPA non-accounting optional data • The client will be able to transfer the payment in EUR to EU countries under better conditions. At the same time, he/she can transfer other non-accounting data to their partner. See Foreign payment - new types of records. • The client will be able to use new non-accounting optional data on his/her side for SEPA payments to exchange with their partner. He/she will receive these data in the new types of records in the ADVICE or in the Electronic statement. 2 Formal check of EDI_BEST format Note: Komerční banka, a.s., registered office: Praha 1, Na Příkopě 33, 969, Postcode 114 07, IČ (Company ID): 45317054 5/46 valid from 12th June 2010
- Page 1 and 2: k EDI BEST client format EDI BEST c
- Page 3: k • EDI • MC (MultiCash) EDI BE
- Page 7 and 8: k EDI BEST client format 2.1.2 Desc
- Page 9 and 10: k of (2) NT payment 2. not zero pay
- Page 11 and 12: k The file with payments contains o
- Page 13 and 14: k 6. Payment currency code (require
- Page 15 and 16: k has been transferred to record 03
- Page 17 and 18: k 12. Payer's reference - 35 469 X(
- Page 19 and 20: k 3. line: Issuer with “IS=” pr
- Page 21 and 22: k • Is sorted by the Processing d
- Page 23 and 24: k date 4. File identificatio n 5. C
- Page 25 and 26: k EDI BEST client format to the con
- Page 27 and 28: k If it concerns an Outgoing or Inc
- Page 29 and 30: k EDI BEST client format Type of re
- Page 31 and 32: k 2.4 EDI_BEST format - Error repor
- Page 33 and 34: k 1. OK answer after a formal check
- Page 35 and 36: k 2. Filler 2 2 X(2) reserve EDI BE
- Page 37 and 38: k - for the credit advice of FP, Gr
- Page 39 and 40: k EDI BEST client format Advice - t
- Page 41 and 42: k of charges SHA, SLV for SEPA 30.
- Page 43 and 44: k 19. Original payer’s name - 20.
- Page 45 and 46: k Identification type 1-8 1st line:
k<br />
OUR<br />
BEN<br />
SHA<br />
BN1<br />
BN2<br />
STD<br />
SLV<br />
Other<br />
OUR<br />
BEN<br />
SHA<br />
SHA<br />
BEN<br />
SHA<br />
SLV<br />
SHA<br />
<strong>EDI</strong> <strong>BEST</strong> <strong>client</strong> <strong>format</strong><br />
Clients not using <strong>EDI</strong> can use this <strong>format</strong> in Profi<strong>banka</strong> and Direct channel services directly <strong>from</strong> their<br />
accounting systems instead of the <strong>BEST</strong> <strong>format</strong> (domestic and foreign payments, statements and<br />
debit and credit advise). Apart <strong>from</strong> the actual <strong>EDI</strong> server, cancellation batches can only be sent via<br />
Direct channel. In this case, an identical Creation date is necessary in addition to Identification<br />
generated <strong>by</strong> the <strong>client</strong> (Item sequential number).<br />
1.3 Char set for UNOA syntax level<br />
Texts in <strong>EDI</strong> subsets are in the UNOA <strong>format</strong> - capital characters of the English alphabet.<br />
UNOA level allows the characters specified in the following table to be used:<br />
capital characters<br />
A to Z<br />
numbers 0 to 9<br />
space<br />
dot .<br />
comma ,<br />
minus -<br />
left parenthesis (<br />
right parenthesis )<br />
slash /<br />
equal sign =<br />
exclamation mark !<br />
quotation marks "<br />
percent sign %<br />
asterisk *<br />
semi-colon ;<br />
“less than” sign <<br />
“greater than” sign ><br />
Reserved characters are those used as separators and limiters of message elements and segments.<br />
In spite of the fact that these can be changed and the change declared in the UNA segment, <strong>KB</strong> shall use those<br />
defined <strong>by</strong> the standard. For the future, the * (asterisk) sign is considered to be used as another separator.<br />
apostrophe ´ segment end character<br />
plus + data element separator<br />
dot . decimal separator<br />
colon : partial data element separator<br />
question mark exemption character<br />
• Code page<br />
• DC and <strong>EDI</strong> - requires windows-1250 – Windows Eastern European (Windows<br />
CRLF line feed)<br />
• PCB - requires windows-1250 – Windows Eastern European (PCB line feed can be<br />
managed <strong>by</strong> both CRLF (#13#10) and Unix LF (#10) or MAC CR (#13)<br />
• MC – requires CP852<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 />
4/46<br />
<strong>valid</strong> <strong>from</strong> 12th June 2010
Change language