Rules for Filling Out Formats of Electronic Payment Documents and Messages of the Batch Clearing System for Small Retail and Regular Payments in the Kyrgyz Republic

Back

Print Version

Date of creation: 2017-06-30

Registered with the Ministry of Justice of the Kyrgyz Republic March 23, 2006. Registration No. 25-06

Approved by Resolution of the Board of the National Bank of the Kyrgyz Republic dated March 2, 2006 No. 5/10

RULES for filling out formats of electronic payment documents and messages of the Batch Clearing System for Small Retail and Regular Payments in the Kyrgyz Republic

(As amended by Resolutions of the Board of the National Bank dated May 11, 2007 No. 25/6, June 8, 2017 No. 2017-P-14\23-11-(PS)

1. Introduction

2. General Information

3. Presentation File. Message Type MT150

4. Individual Batches within the Incoming File

5. Individual Batches within the Outgoing File

6. Free-format Messages, Text and Service Messages

7. Status of File, Batch or Individual Payment

8. Status of Multiple Payments within a Batch

9. Request for Status of Individual Payments within a File or Batch

10. Recall of a Batch or Individual Payment

11. Recall of Individual Payments within a Batch

12. Cancellation of Payment in a File without Request

13. Copy of File, Batch or Individual Payment

14. Copy of Multiple Payments within a Batch

15. Statistical Information

16. Positions and Fund Movements

17. Net Positions

18. Fund Movement Requests

19. Message with Error Code Response

20. Message Processing

21. Rules for Conversion of Net Position File and Debit Limit Net Position File

22. Electronic Table Formats for Sub-participants

23. Message Exchange Formats of the Processing Center and BCS

24. Introduction

1.1. (Ceased to be in force in accordance with the Resolution of the Board of the National Bank dated June 8, 2017 No. 2017-P-14\23-11-(PS).

1.2. This document establishes the formats of electronic payment documents, electronic tables, and messages (based on SWIFT standards) sent/received by participants in the Batch Clearing System for Small Retail and Regular Payments in the Kyrgyz Republic (hereinafter - BCS) and rules for their completion.

1.3. Electronic tables include information on payments (salary disbursements, pensions, utility bill payments, etc.) transmitted to agent banks and received from them by system sub-participants (Regional branches of the Central Treasury and Social Fund, large utility companies providing bill payments using direct debit, etc.).

1.4. Electronic messages include various requests by participants regarding payment, batch, and file statuses, net position information, etc., and system responses to such requests.

1.5. Terms and definitions used in these Rules are understood as defined by the Law of the Kyrgyz Republic "On the Payment System of the Kyrgyz Republic" and the Regulation "On the Batch Clearing System for Small Retail and Regular Payments in the Kyrgyz Republic", approved by Resolution of the Board of the National Bank of the Kyrgyz Republic dated December 15, 2005 No. 37/8. Additionally, the following terms and abbreviations are used in this document: BCS - Batch Clearing System for Small Retail and Regular Payments in the Kyrgyz Republic; BCS/X - standard system for processing mass payments; "KO" - unsuccessful message processing result (error); "OK" - successful message processing result; RTGS (Real-Time Gross Settlement system) - Real-time Gross Settlement System (RTGS); Batch - consolidated payment order - a collection of electronic payments directed to one receiving bank, grouped by identical type and settlement date; EDS - electronic digital signature; Net Position File (NPF) - net position file (information exchange file); Debit Limit Net Position File (DLNPF) - debit limit net position file (information exchange file).

2. General Information

2.1. Document Diagrams Diagramms in this document, illustrating fund movements, consist of the following objects:

• Rectangles denote BCS/X, participants (PA, PB, ...) and clients (CA, CB, ...).
• Participants and clients have numbers corresponding to field numbers in the message.
• Solid lines indicate data transmission (e.g., batch, message), and dashed lines indicate individual payments. Each batch may contain one or multiple payments. Figure.

2.2. System Message List The system supports the following message types:

N	Message Type	Description	Can be sent to/from whom	Section in document
MT150	Presentation file: batch set sent as a whole	Participant <-> BCS; Sub-participant <-> BCS	3
MT102	Batch: Consolidated credit payment order (Copy) within presentation file; Sub-participant <-> BCS (Copy) within presentation file	Participant <-> BCS; Sub-participant <-> BCS	4.1, 5.1
MT104	Batch: Consolidated debit payment order (payment claim) within presentation file; Sub-participant <-> BCS within presentation file	Participant <-> BCS; Sub-participant <-> BCS	4.2, 5.2
MTn98	Special message type. Used as an envelope for transmitting special message types	Participant <-> BCS; Participant <-> Sub-participant; Sub-participant <-> BCS	6.1
MT199/TEXTMESSAGE	Represents a message transmitted via email from one participant to another. The Central Bank may also issue or receive such messages	Participant <-> BCS; Participant <-> Sub-participant; Sub-participant <-> BCS	6
System request set MT199 or MT999	Request to change a corresponding system parameter. Does not include field :21:	Participant <-> BCS (limited set); Sub-participant <-> BCS (full set)	6.3
System response set MT199 or MT999	Response to the corresponding request. Response includes field :21:	BCS <-> Participant (limited set); BCS <-> Sub-participant (full set)	6.3.10
MT195/STAT	Status request for payment document (file, batch or payment)	Participant <-> BCS; Sub-participant <-> BCS	7.1
MT196/STAT	Response to status request for payment document (file, batch or payment)	BCS <-> Participant; BCS <-> Sub-participant	7.2
MT198/SPDC	Setting DLNPF on position list	Participant <-> BCS	6.3.12
MT198 (Request)	Status request for individual payments in batch	Participant <-> BCS; Sub-participant <-> BCS	8.1.1
MT198 (Response)	Response to status request for individual payments in batch	BCS <-> Participant; BCS <-> Sub-participant	8.2.1
MT195/LIST	Status request for specified payments in file or batch	Participant <-> BCS; Sub-participant <-> BCS	9.1.1
MT198/STAT (Response)	Response on status of specified payments in batch	BCS <-> Participant; BCS <-> Sub-participant	9.2.1
MT158 (Response)	Response on status of specified payments in file	BCS <-> Participant; BCS <-> Sub-participant	9.2.2
MT192	Request to recall a batch or payment previously sent to the system	Participant <-> BCS; Sub-participant <-> BCS	10.1
MT196/CANC	Response to recall of batch or payment	BCS <-> Participant; BCS <-> Sub-participant	10.2
MT198 (Request)	Request to recall individual payments in batch	Participant <-> BCS; Sub-participant <-> BCS	11.1
MT198 (Response)	Response on recall of individual payments in batch	BCS <-> Participant; BCS <-> Sub-participant	11.2
MT158 (Cancellation)	Cancellation of individual payments in file without request	BCS <-> Participant; BCS <-> Sub-participant	12.1
MT195/COPY	Request for copy of file, batch or payments previously sent to the system	Participant <-> BCS; Sub-participant <-> BCS	13.1
MT156 (Copy)	Copy of file previously sent to the system	BCS <-> Participant; BCS <-> Sub-participant	13.2.1
MT196/COPY (Copy)	Copy of batch previously sent to the system	BCS <-> Participant; BCS <-> Sub-participant	13.2.2
MT196/COPY (Payment)	Copy of payment previously sent to the system	BCS <-> Participant; BCS <-> Sub-participant	13.2.3
MT198 (Request)	Request for copies of specified payments in batch	Participant <-> BCS; Sub-participant <-> BCS	14.1
MT198 (Response)	Copies of specified payments in batch	BCS <-> Participant; BCS <-> Sub-participant	14.12
MT985/TTLS	Request to obtain participant statistics for this clearing session	Participant <-> BCS; Sub-participant <-> BCS	15.1.1
MT985/TTLD	Request to obtain participant statistics for the current operational day	Participant <-> BCS; Sub-participant <-> BCS	15.1.2
MT985/TTLF	Request to obtain participant statistics on payments in file	Participant <-> BCS; Sub-participant <-> BCS	15.1.3
MT985/TTLV	Request to obtain participant statistics for the specified settlement day	Participant <-> BCS; Sub-participant <-> BCS	15.1.4
MT986/TTLS	Statistical information on participant activity for this clearing session	BCS <-> Participant; BCS <-> Sub-participant	15.2.1
MT986/TTLD	Statistical information on participant activity for the current operational day	BCS <-> Participant; BCS <-> Sub-participant	15.2.2
MT986/TTLF	Statistical information on participant activity on payments in file	BCS <-> Participant; BCS <-> Sub-participant	15.2.3
MT986/TTLV	Statistical information on participant activity for the settlement day	BCS <-> Participant; BCS <-> Sub-participant	15.2.4
MT985/STAT	Position request	Participant <-> BCS; Sub-participant <-> BCS	16.1.1
MT985/TRNR	Fund movement request	Participant <-> BCS; Sub-participant <-> BCS	16.1.3
MT985/SSCH	Payment schedule request	Participant <-> BCS; Sub-participant <-> BCS	16.1.3
MT986/STAT	Response to position request	BCS <-> Participant; BCS <-> Sub-participant	16.2.1
MT986/TRNR	Response on fund movement	BCS <-> Participant; BCS <-> CB	16.2.2
MT986/SSCH	Response to payment schedule request	BCS <-> Participant; BCS <-> CB	16.2.3
MT973	Request for interim statement on clearing documents	Participant <-> BCS; Sub-participant <-> BCS	17.1
MT970	Statement on clearing documents	BCS <-> Participant; BCS <-> Sub-participant	17.1
MT972	Interim statement on clearing documents	BCS <-> Participant; BCS <-> Sub-participant	17.2
MT971	Aggregated positions	BCS <-> Participant; BCS <-> Sub-participant	17.3
MTn90	Notification on settlements for expenses, interest and other adjustments	BCS <-> Sub-participant	18.1
MTn91	Request for payment of expenses, interest and other adjustments	BCS <-> Participant	18.2
MTn96/ERRC	This message is generated in case of an error during receipt or processing of the corresponding message	BCS <-> Participant; BCS <-> Sub-participant	19.1

2.3. Message Field Requirements Conventions used when describing message fields: n - only digits; a - only uppercase letters; c - only uppercase letters and/or digits; x - any character from the permitted set; ! - fixed field format only; d - amount, up to 15 digits without space with a possible separator (comma) separating the integer part from the fractional part (if no fractional part follows the amount, a comma is placed after it; before the fractional separator there must be at least one digit (e.g., 0,); where amount is specified with currency, the number of fractional digits must not exceed the maximum allowed for that currency code (for KGS - 2, i.e., 100, 120 is invalid, 10, 12 is correct); nm - defines field/subfield dimension: number of rows (n) multiplied by number of characters per row (m) (e.g., 435x). [ ] - information in brackets is optional. │ --> - start of repeating field sequence. --- │ - end of repeating field sequence. M - mandatory tag status. O - optional tag status. OM - mandatory to fill in one of the sequences. If field value is filled in sequence A, it is not filled in sequence B and vice versa. In fields consisting of a set of lines with keywords, the order of lines is not regulated unless otherwise specified. For example, according to formats, the following is permissible: :79:/SETACCOUNTDEBITCAP/CLEARING /ACCOUNT/35215601 /AMOUNT/200, /DIRECTION/I Also permissible: :79:/SETACCOUNTDEBITCAP/CLEARING /AMOUNT/200, /ACCOUNT/35215601 /DIRECTION/I. (As amended by Resolution of the Board of the National Bank dated May 11, 2007 No. 25/6)

2.4. Message Format All payment and message formats are based on SWIFT standards, however, due to the need for additional information about payments for complete accounting by senders and receivers, the formats developed in this document are SWIFT-like, i.e., individual field formats differ from identical SWIFT fields. Each message prepared for sending to/from BCS must contain:

• User Code (sender);
• BIC of BCS as recipient/sender;
• Message Type;
• Message Reference;
• Message Text. The listed information, except for message text, constitutes the message header. (As amended by Resolution of the Board of the National Bank of KR dated May 11, 2007 No. 25/6)

2.4.1. Message Header Sent to BCS When using a SWIFT-like format, header information is specified in blocks 1, 2 and 3. Each block starts with a string sequence "{n:" (n-block number) and ends with the symbol "}". Block 1:

Tag	Field Name	Field Format	Note	Example
1	Block Opening	1!x	{ - must not change (constant)	{
2	Block Number	1!n1!x	Block number identifier and separator (symbol ":")	1:
3	System Constant	1!a2!n	F01 - must not change	F01
4	Sender	6!n4!nXX	User Code - sender (when sending to BCS). Consists of Bank BIC, user number (automatically adjusted by software at send time; no manual adjustment required) and suffix XX	1011090001XX
5	Communication Session Number	4!n6!n	Automatically adjusted by software at send time; no manual adjustment required	0001000001
6	Block Closing	1!x	} - must not change (constant)	}
All fields are mandatory.
Example Block 1: {1:F011011090001XX0001000001}

Block 2:

Tag	Field Name	Field Format	Note	Example
	Block Opening	1!x	{ - must not change (constant)	{
1	Block Number	1!n1!x	Block number identifier and separator (symbol ":")	2:
3:	Message Type	3!n	Message type specified	195
4	Recipient	6!nXXXXXX	BIC of BCS specified	999999XXXXXX
5	Constant	1!a	Always specified as N	N
6	Block Closing	1!x	} - must not change (constant)	}
All fields are mandatory.
Example Block 2: {2:I195999999XXXXXXN}

Block 3:

Tag	Field Name	Field Format	Note	Example
1	Block Opening	1!x	{ - must not change (constant)	{
2	Block Number	1!n1!x	Block number identifier and separator (symbol ":")	3:
3	Internal Priority	{:113:0100}	Constant	{:113:0100}
4	Reference	{:108:16x}	Unique file reference assigned by sender	{108:11568}
5	Block Closing	1!x	} - must not change (constant)	}
All fields are mandatory.
Example Block 3: {3:{113:0100}{108:11568}}

Example of message header in SWIFT-like format prepared for sending to BCS: {1:F011011090001XX0001000001}{2:I195999999XXXXXXN}{3:{113:0100} {108:11568}}

2.4.2. Message Header Sent from BCS The message header received from BCS also consists of blocks 1, 2 and 3. Block 1:

Tag	Field Name	Field Format	Note	Example