2008-01-09

Guidelines for Preparation and Electronic Submission of Overnight Interbank Money Market Loan Data

The National Bank of Serbia mandates that commercial banks electronically submit daily XML-formatted data on overnight interbank money market loans to calculate the BEONIA reference rate. The guidelines specify strict technical requirements, including standardized file naming conventions, mandatory XML tags for transaction type, counterparty identification, loan value, and interest rate, alongside precise validation rules and error codes. Banks must transmit these files via a dedicated FTP server, ensuring daily reporting on business days or submitting a header-only file when no qualifying transactions occur, with technical support provided by the NBS Central Reception Office.

National Bank of Serbia logo

Serbia

National Bank of Serbia

Click to view thumbnail

NATIONAL BANK OF SERBIA GUIDELINES for preparation and electronic submission of data on overnight interbank money market loans to the National Bank of Serbia VERSION 1.0 December 2007

1 BO – BEONIA – Report on overnight interbank loans in the domestic interbank market…………………………………………………………………………………… 3 2 GENERAL NOTES AND CONTROLS ……………………………………… 6 2.1 Error messages ……………………………………………………………….. 7 2.2 Data transmission protocol …………………………………………………… 8 2.3 Technical support …………………………………………………………….. 9

1 BO – BEONIA – Data on overnight interbank loans in the domestic interbank market Submitted pursuant to: Decision on Submitting Data on Overnight Interbank Money Market Loans to the National Bank of Serbia

  1. 1 Report heading TAG NAME CONTENT TYPE NOTE/information required (R) <Document>

<ValueDate> Date of validity of data Date DD.MM.YYYY Value date is the date on which data are valid and corresponds to the date specified in the file name (R)

<Form> Data code Text CC BO, the same as specified in the file name, length – 2 characters (R) <IdentificationNumber> Identification number of the bank transmitting data Integer 8N Numeric value, length – 8 characters (R) <OrdinalNumber> Ordinal number of data transmission for the set transmission date Integer NN Ordinal number must be the same as in the file name, length – 2 characters (R) <DataProcessedBy> Name and surname of the responsible person Text 240C Textual data, length – 240 characters (R) <Contact> Telephone, fax or e-mail address of the responsible person Text 240C Textual data, length – 240 characters (R)

1.2 Description of the BO message TAG NAME CONTENT TYPE NOTE/information required (R) Transaction code BO <TransactionType> 1=Loans granted 2=Loans taken Integer N Integer numeric value, length – 1 character (R) <Bank> Identification number of the borrowing/lending bank – the borrowing/lending bank may not be the data transmitting bank or the NBS Integer 8N Numeric value, length – 8 characters (R) <Value1> Transaction value Decimal 15N.NN Numeric value with at most 15 integers and 2 decimals, may not equal zero (R) <Value2> Interest rate Decimal 2N.NN Numeric value with at most 2 integers and 2 decimals, may not equal zero (R) Data shall be submitted for each business day. For the purposes of the Decision, a business day shall not include Saturdays, Sundays or state holidays that are non￾business days. Frequency of data submission: pursuant to the decision on the interest rate on overnight loans – BEONIA. If a bank has neither granted nor taken any overnight loans, or all individual loans granted or taken by such bank were below the minimum amount prescribed in the Decision, such bank shall submit only the heading of the document.

Example of data in XML format BO010307_01_99999999.xml

<?xml version="1.0" encoding="WINDOWS-1250" ?>
  • <ForTransmission>
  • <Document>

<ValueDate>01.03.2007</ValueDate>

<Form>BO</Form> <IdentificationNumber>99999999</IdentificationNumber> <OrdinalNumber>1</OrdinalNumber> <DataProcessedBy>Petar Petrovic</DataProcessedBy> <Contact>011 198345, e-mail: petar.petrovic@nbs.yu</Contact> - <BOTransactionCode> <TransactionType>1</TransactionType> <Bank>99999999</Bank> <Value1>1000000.00</Value1> <Value2>8.75</Value2> </BOTransactionCode> </Document> </ForTransmission> Example of data in XML format if the bank has no data BO010307_02_99999999.xml <?xml version="1.0" encoding="WINDOWS-1250" ?> - <ForTransmission> - <Document> <ValueDate>01.03.2007</ValueDate> <Form>BO</Form> <IdentificationNumber>99999999</IdentificationNumber> <OrdinalNumber>2</OrdinalNumber> <DataProcessedBy>Petar Petrovic</DataProcessedBy> <Contact>011 198345, e-mail: petar.petrovic@nbs.yu</Contact> - <BOTransactionCode></BOTransactionCode > </Document> </ForTransmission>
  1. GENERAL NOTES AND CONTROLS The project envisages the exchange of data in XML format. The name of data submitted by banks to the NBS is formally defined, as are all data that are already included in the system of electronic exchange. Example and structure of the name of the file which is submitted BO311207_02_07023664.xml BO Form reference code 31122007 Date to which data refer, in the following form: ddmmyy (daymonthyear) _ Required_ 02 Ordinal number of data transmission _ Required_ 07023664 Bank identification number The content of data is formally defined and divided into three parts: required tags (definitions), document and general data on the document, and document reference codes. Required tags. The first tag of all messages defined herein shall be: <?xml version= “1.0” encoding= “WINDOWS-1250”?>
  2. Document and general data on the document. The following tags must be filled out: a. Date of data validity, in a defined form, represents the date on which data are valid, depending on the type of data; allowed value is between 31 December 2002 and the current date; the date is the same as in the file name. b. Form – data code is the same as in the file name c. Identification number is the same as in the file name d. Ordinal number is the same as in the file name
  3. Document reference codes. Data on reference codes are explained in the second section hereof.
  4. Dates are in a defined form: DD.MM.YYYY, except in file name: DDMMYY.
  5. Decimals are separated by a point.
  6. After logical controls of data validity are performed, data shall be entered in a database if correct. If data are incorrect, a list of errors shall be compiled and NBS response on the result of processing shall be sent to the bank’s folder on FTP server, in the following form: NBBO31122007_02_07023664.txt, where BO31122007_02_07023664.txt is the name of the data for which the response is transmitted.

2.1 Error messages 1 Data processed and accepted 10 Incorrect data type 11 Error in the name of the xml document 12 Required information missing 14 Ordinal number of the transmission must be higher than that of the latest transmission 15 Invalid data value 21 Data from xml document do not equal data from xml document name 31 Date cannot be later than today’s date 34 Date must be in a format defined by the Guidelines for Exchange of Data 36 Data exceed maximum allowed length 43 Not all amounts may equal zero 46 Data for Sundays and holidays are not sent 47 Value may not be zero or less 800 Parsing error – contact your programmer

2.2 Data transmission protocol Data can be transmitted by using standard Windows programmes. After the connection is set up, connect to the FTP server of the NBS in Belgrade via: “COMMAND PROMPT, C:>”, command: “FTP 10.16.10.72”, by entering USER and PASSWORD. An even simpler procedure is to use one of the FTP programmes if available. Effect data transfer by FTP commands. All types of reference codes are sent together as one or more file types. Please note that you should not occupy the connection longer than necessary. Please ensure that the data you transmit are checked and free from viruses.

2.3 Technical support Information Technology – Central Reception Office Darinka Jankovic 011 333-7605, darinka.jankovic@nbs.yu Zorka Vukobrat 011 333-7607, zorka.vukobrat@nbs.yu Dragan Petkovic 011 333-7610, dragan.petkovic@nbs.yu