Resolution of the Board of the National Bank of the Kyrgyz Republic No. 25/6 of May 11, 2007 on Amendments and Additions to the 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

Registered in the Ministry of Justice of the Kyrgyz Republic

June 14, 2007. Registration number 58-07

Bishkek

from May 11, 2007 No. 25/6

RESOLUTION OF THE BOARD OF THE NATIONAL BANK

OF THE KYRGYZ REPUBLIC

On Amendments and Additions to the 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

In connection with the industrial operation of the Batch Clearing System for Small Retail and Regular Payments in the Kyrgyz Republic

(hereinafter referred to as SPC) as part of the implementation of the State Program of measures

for the introduction of a cashless payment system and for creating infrastructure,

capable of effectively conducting payments in the Kyrgyz

Republic for 2003-2008, approved by joint Resolution of the

Government of the Kyrgyz Republic and the NBKR No. 916 dated December 31, 2002, the Board of the National Bank, having considered the [Changes](https://cbd.minjust.gov.kg/300649" \l "1)

[and additions](https://cbd.minjust.gov.kg/300649" \l "1) to the "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", approved by Resolution

of the Board No. 5/10 dated March 2, 2006 and registered in the Ministry

of Justice No. 25-06 dated March 23, 2006, resolves:

Approve "Changes and Additions to the 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" ([app-](https://cbd.minjust.gov.kg/300649" \l "1)

[ended](https://cbd.minjust.gov.kg/300649" \l "1)).

The Department of Banking Settlements jointly with the Legal Department

in the established order to carry out state registration of these

changes and additions in the Ministry of Justice of the Kyrgyz

Republic.

These changes and additions enter into force from the moment of offi-

cial publication, after state registration in the Ministry

of Justice of the Kyrgyz Republic.

After official publication of the registered normative

legal act, the Legal Department is to inform the Ministry of Jus-

tice of the Kyrgyz Republic about the source of publication (name

of the publication, its number and date).

The Department of Banking Settlements is to bring this resolution

to the attention of commercial banks, JSC "Clearing and Savings Com-

pany", regional departments and the branch of the National Bank of Ky-

rgyz Republic in the Batken region.

Control over the implementation of this resolution is assigned to

the Member of the Board of the National Bank of the Kyrgyz Republic Imankulova

Ch.K.

Chairman of the Board of the National

Bank of the Kyrgyz Republic M. Alapaev

Approved

by the resolution of the Board

of the National Bank

of the Kyrgyz Republic

of May 11, 2007 No. 25/6

CHANGES AND ADDITIONS

to the 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

Throughout the text, replace in the appropriate cases:

The word "SPC" with the word "batch". In paragraph 9 of point 1.5, the word "pa-

batch" is to be excluded;

The word "SWIFT-like" with the word "SWIFT-like" (SWIFTopodobny);
The word "BIC" with the word "BIC" (Bik).

Point 2.3 is to be supplemented with a paragraph of the following content:

"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".

In paragraph 6 of point 2.4, the word "(optional)" is to be excluded.
Point 2.5 is to be supplemented after the paragraph "Field :20:" with a paragraph of the following

content:

"Field :21: in responses to requests (reports) contains the reference of the

associated request. If the report is generated by the system without a request, then in the

field 21 contains the keyword NONREF, if it is mandatory in this

report and if not otherwise specified."

Point 2.5 is to be supplemented with a paragraph of the following content:

"When receiving messages from the batch clearing system in SWIFT-like

format, each message after the 4th block is supplemented by a 5th block,

which has the form:

}".

Paragraph 1 of point 2.6 is to be presented in the following edition:

"0 1 2 3 4 5 6 7 8 9 () = ; , N % * . - _ / ? ! " " : + ~ @ # $

^ [] Space (Space)".

Point 2.6 is to be supplemented with subpoint 2.6.1 of the following content:

"2.6.1. Combinations of symbols and sequences not permitted for

use in message texts.

Any field cannot start with CrLf (Carriage Return - Line

Feed), except for specially specified cases (field 77E);

Any line inside a field cannot start with the symbol "-" (hy-

phen). Exception - field 79;

It is not permissible in any field to have a completely empty line or a line

consisting only of spaces;

Any line should not start with the symbol ":" (colon) if

this is not a new field;

Fields containing references of documents or payments (20, 21, tag

108 of the message header) should not start with the symbol "/", should not

end with the symbol "/" and should not have 2 or more symbols "/"

in a row;".

In point 2.11.1, the table is to be presented in the following edition:

| DateTime | Field Format | Date and time of message reception by the system |

| | | BCS/X in YYMMDDHHMM format |

|----------|-------------|--------------------------------------------|

|MIR | |Incoming message reference (28 characters), |

| | |consists of: |

| |6!n |1. Send date YYMMDD (6 characters) |

| |6!n4!n!XX |2. Sender user code (10 |

| | |characters) |

| |4!n |3. Communication session number (4 |

| | |characters) |

| |6!n |4. Message sequence number (6 characters)|

|----------|-------------|--------------------------------------------|

|Signature | |Electronic digital signature |

In point 2.11.2, the table is to be presented in the following edition:

| DateTime | Field Format | Date and time of message reception by the system |

| | | BCS/X in YYMMDDHHMM format |

|-----------|------------|--------------------------------------------|

|MIR | |Incoming message reference (28 characters), |

| | |consists of: |

| |6!n |1. Send date YYMMDD (6 characters) |

| |6!n4!n!XX |2. Sender user code (12 |

| | |characters) |

| |4!n |3. Communication session number (4 |

| | |characters) |

| |6!n |4. Message sequence number (6 characters)|

|-----------|------------|--------------------------------------------|

|Code | |Error code |

|-----------|------------|--------------------------------------------|

|Description| |Error text |

|-----------|------------|--------------------------------------------|

|Info | |Error information |

|-----------|------------|--------------------------------------------|

|Signature | |Electronic digital signature |

In the table of point 3.1.2, the position "SPC TYPE" is to be presented in the following

edition:

|Batch Type |M |12 |3!t |Permissible values: |104 |

| | | | |102 | |

| | | | |104 | |

In the position "OM" "Sender Customer Account" in the columns "Format" and

"Comment" of points 4.1.1., 4.1.2., the word "[/LS/13x]" is to be replaced with the word

"[/LS/20x]". In the position "OM" "SPC Sender Customer Account" in the column

"Format" of point 5.1.1., the word "[/LS/13x]" is to be replaced with the word "[/LS/20x]". In

the position "M" "Recipient Customer Account (Sender of Funds)" in the columns "Format" and "Comment" of point 4.2.2., the word

"[/LS/13x]" is to be replaced with the word "[/LS/20x]".

In the position "M" "Recipient Customer Account" in the column "Format" of point

4.1.2., the word "[/SCHET/16x]" is to be replaced with the word "[/SCHET/16!n]". In the posi-

tion "OM" "SPC Sender Customer Account (Recipient of Funds)" in the

column "Format" of points 4.2.1, 4.2.2, 5.2.1 the word "[/SCHET/16x]" is to be re-

placed with the word "[/SCHET/16!n]".

Point 4.1.2 is to be supplemented with a note of the following content:

"When indicating the reason for refusal in tag 70, the

refusal code must also be indicated:

For MT102 (REJT/RTND):

Code Description

ERRACCOUNT Incorrect recipient customer account

ERRBNF Incorrect recipient customer name

For MT104 (REJT):

Code Description

BNFBANKRUPT Insufficient funds in the payer customer account

(included in the blacklist).

ERRACCOUNT Incorrect payer customer account.

ERRBNF Incorrect payer customer name.

ERRCONTRACT No contract for direct debit.

The dimension of the keyword is 20x.

Example of a message tag:

:70:/DESCR/ERRBNF

Please clarify the customer name.

Refusal codes are reference data and may be supplemented with other

values."

In point 4.1.3, the position "M" "Sender Information for Receiver" is to be presented in the following edition:

|M |72 |Information |6*35x |After the keyword |/PURPOSE/Test |

| | |for |26x] |indicates |/PRT/20 |

Point 4.1.3 is to be supplemented with Note 4, points 5.1.3, 5.2.1 to be

supplemented with Note 3 of the following content:

"Note 4. The minimum priority in [PRT], i.e., zero, is

the highest."

In point 4.2.1, the position "M" "Sender Information for Receiver" is to be presented in the following edition:

|M |72 |Information |6*35x |After the keyword |/NUM/3 |

| | |for |26x] |indicates |/PURPOSE/Test |

Point 4.2.1 is to be supplemented with a note of the following content:

"Note. The minimum priority in /PRT/, i.e., zero, is the

highest."

The name of point 5.1.3 is to be presented in the following edition:

"5.1.3. Mandatory Sequence C."

In point 5.1.3, the position "M" "Sender Information for Receiver" is to be presented in the following edition:

|M |72 |Information |6*35x |See Notes 2 and 3 |

| | |Receiver |[//33x] | |

| | | |6!n | |

| | | |[/33x]] |day in which |

Note 2 of points 5.1.3 and 5.2.1 is to be supplemented with a sentence:

"In outgoing batches, field 72 is added by the system the name

of the operational day period after the keyword /BDP/."

In point 5.2.1, the position "M" "Sender to Receiver Information" is to be presented in the following edition:

|M |72 |Information |6*35x |See Note 2 below |

| | |Receiver (Sender |[//33x] | |

| | | |6!n |Batch reference, date |

| | | |6!n |settlement and BIC |

| | | |[/33x]] |day in which |

In point 6.3, the diagram and its description are to be presented in the following re-

vision:

"The object owner is a participant whose object (position property,

participant, user) is subject to change upon request. For

some requests (LOCKACCOUNT, UNLOCKACCOUNT, SETUSERLOCK, ACTIVATE-

BUSINESSDAYPERIOD, SETACCOUNTDEBITCAP, SETACCOUNTDEBITCAPLIMIT) the mes-

sage number 4 is sent to the owner of the changed object, if the owner is not

the sender of the request."

Figure

In point 6.3.3, the position "M" "Request" is to be presented in the following re-

vision:

|M |79 |Request |/18!c/6!n | 1 |Type |/SETPARTICIPANT-|

| | | |------|-----|------|------|

| | | |/6!c/2!n | 2 |Assigned |/STATUS/00 |

| | | | | |ded | |

| | | |------|-----|------|------|

| | | | | 3 |Keyword | |

| | | | | |use| |

In point 6.3.8, the position "M" "Request" is to be presented in the following re-

vision:

|M |79 |Request |/18!c/30x | 1 |Request Type |/SETACCOUNTDEBIT-|

| | | |------|-----|------|------|

| | | | | |use| |

| | | |------|-----|------|------|

| | | | | |use| |

| | | |------|-----|------|------|

| | | |------|-----|------|------|

| | | |------|-----|------|------|

| | | | | |set | |

In points 6.3.8 and 6.3.9, the paragraph "Field :79:" is to be presented in the following

revision:

"Field :79: contains the type and parameters of the request. The order of

lines is not regulated except for the subfield "Request Type", which

must be in the first line of the field."

Point 6.3.12 is to be considered as point 6.4 and presented in the following re-

vision:

"6.4. MT998: Service Request

This message, as a rule, can only be sent by an external sys-

tem to set the Limit simultaneously for several participants.

Figure

Messages in the diagram:

Number Message Name Sections of this document,

of the message in which these messages

in the diagram are described

1 Request 6.4.1

2 Error Message 19.1

3 Response 6.4.2

4 Response 6.4.3

6.4.1. MT998/SPDC: Setting Limit for a List of Positions

6.4.1.1. Mandatory Sequence A: General Information

|Pres-

|-----|-----|---------------------|----------|------------------------|

|M |20 |Request Identifier |16x |Unique reference |

|-----|-----|---------------------|----------|------------------------|

|M |12 |Type of nested |3!n |999 |

|-----|-----|---------------------|----------|------------------------|

|M |77E |Request Content |73x |"CrLf" in the first line |

6.4.1.2. Mandatory Sequence B: Request Details

|Pres-

|-----|-----|---------------------|------------|----------------------|

|M |75 |Request |4!a |SPDC |

| | | |[/9!c/[1!a]]|/DIRECTION/I |

|---------------------------------------------------------------------|

||---> Repeating Sequence D |

|---------------------------------------------------------------------|

|M |79 |Participant BIC |/BIC/6!n |/BIC/234567 |

|-----|-----|---------------------|------------|----------------------|

|---------------------------------|-----------------------------------|

|----| End of Sequence D |

|---------------------------------------------------------------------|

|M |19 |Total Amount |17d |100,00 |

Example:

}}".

In points 7.2.1 and 7.2.2, the position "O" "Comment (Narrative)" is to be presented in the following edition:

|O |77A|Comment |20*35x |EA49 |

In point 7.2.2, the position "M" "SPC Identifier, Participant BIC, Settlement Date, Currency Code, Amount" is to be presented in the following edition:

| | |Participant BIC |6!n |234567 |

| | |Settlement Date, Code |6!n3!a15d |040929KGS12324, |

| | |[Processing Date] |[6!n] |040929 |

Point 7.2.3. is to be supplemented after the paragraph "Field :21:" with a paragraph of the

following content:

"In field :21: the keyword DUPLICATED is contained in case

of sending a file with a reference that has already been used in the current opera-

tional day."

In point 7.2.3, the paragraph "Field :76:" is to be presented in the following re-

vision:

"Field :76: contains the type of response and the status of the corresponding object

(file, batch, payment). In the case of a "status request response"

(Status Answer message), this field can take the following values:

|STAT|A refusal or return was formed for the payment/batch |

|REJT| |

|----|----------------------------------------------------------------|

|STAT|The batch/payment was cancelled due to regulatory rules |

|CANC|of NBKR and/or BCS/X, or was recalled by the sender |

|----|----------------------------------------------------------------|

|STAT|The batch/payment was accepted by the system for clearing |

|NETC| |

|----|----------------------------------------------------------------|

|STAT|The batch/payment is waiting for the processing date to arrive |

|NETL| |

|----|----------------------------------------------------------------|

|STAT|File accepted |

|ACCP| |

|----|----------------------------------------------------------------|

|STAT|File not accepted |

|NACP| |

|----|----------------------------------------------------------------|

|STAT|The batch/payment has passed the settlement procedure |

|SETL| |

|----|----------------------------------------------------------------|

|STAT|An error was detected during the processing of the file/batch/payment |

|ERRC| |

|----|----------------------------------------------------------------|

|STAT|The batch/payment is suspended |

|SUSP| |

|----|----------------------------------------------------------------|

|STAT|Transaction created |

|PROC| |

|----|----------------------------------------------------------------|

|STAT|The batch is included in the clearing transaction |

|NETR| |

|----|----------------------------------------------------------------|

|STAT|The batch is not included in the settlement due to exceeding the Limit |

|INAC| |

The first line (STAT) may be accompanied by an indication of the date/time of

processing of the request.

The second line may be accompanied by an indication of:

|REJT|Time of cancellation due to refusal or return |

|----|----------------------------------------------------------------|

|CANC|Time of cancellation of the file/batch/payment |

|----|----------------------------------------------------------------|

|SETL|Time when settlement was made for the batch (request or to which |

| |the payment relates) |

|----|----------------------------------------------------------------|

|ACCP|Time when the file was accepted |

|----|----------------------------------------------------------------|

|NACP|Time when the file was rejected |

|----|----------------------------------------------------------------|

|ERRC|Time when processing error was recorded |

|----|----------------------------------------------------------------|

|SUSP|Time when the batch (request or to which the |

| |payment relates) was suspended |

|----|----------------------------------------------------------------|

|NETC|Time of receipt of this status |

|----|----------------------------------------------------------------|

|NETR|Time of receipt of this status |

|----|----------------------------------------------------------------|

|NETL|Time of receipt of this status |

|----|----------------------------------------------------------------|

|INAC|Time of receipt of this status |

In points 7.2.3., 8.2.1.2., 9.2.1.2., 13.2.1., 14.2.1.2. the

position "O" "Comment" is to be presented in the following edition:

|O |77A|Comment |20*35x |EA49 |

In points 7.2.3., 8.2.1.2., 9.2.1.2. the paragraph "Field :77A:" is to be pre-

sented in the following edition:

"Field :77A: may contain an explanation to the response given in field

:76:. This clarification is given for the following types of responses:

|STAT|Reason for Cancellation|

|CANC| |

|----|----------------------------------------------------------------|

|STAT|Reason for Suspension|

|SUSP| |

|----|----------------------------------------------------------------|

|STAT|Error Description|

|ERRC| |

Field :77A: of the MTn96 message must contain the following lines:

|1 line |Error/Warning Code|

|-----------|---------------------------------------------------------|

|2 line |Error/Warning Description|

|-----------|---------------------------------------------------------|

|3-20 lines|Additional information related to|

| |the error/warning|

Lines 3-20 are optional."

In paragraph 7.2.3, position "M" "Payment Identifier Identifier of the Batch BIC of the Participant Settlement Date, Currency Code, Amount" is to be worded as follows:

| | |BIC of the Participant |/6!n |234567 |

| | |Settlement Date, Currency|6!n3!a15d |040929KGS1236, |

| | |[Processing Date] |[6!n] |040929 |

In paragraph 8.2.1.2, the paragraph "Field :76:" is to be worded as follows:

"Field :76: contains the Response Type and status of the corresponding payment.

In the case of a status response message, this field may take the following values:

|STAT|A rejection or return was generated for the payment/batch|

|REJT| |

|----|----------------------------------------------------------------|

|STAT|The Batch/Payment was cancelled due to NBUKR and/or BCS/X regulations, or was recalled by the sender|

|CANC| |

|----|----------------------------------------------------------------|

|STAT|The Batch/Payment was accepted by the system for clearing|

|NETC| |

|----|----------------------------------------------------------------|

|STAT|The Batch/Payment is awaiting the processing date|

|NETL| |

|----|----------------------------------------------------------------|

|STAT|The Batch/Payment has undergone the settlement procedure|

|SETL| |

|----|----------------------------------------------------------------|

|STAT|An error was detected during the processing of the batch/payment|

|ERRC| |

|----|----------------------------------------------------------------|

|STAT|The Batch/Payment is suspended|

|SUSP| |

|----|----------------------------------------------------------------|

|STAT|Transaction created|

|PROC| |

|----|----------------------------------------------------------------|

|STAT|The Batch is included in a clearing transaction|

|NETR| |

|----|----------------------------------------------------------------|

|STAT|The Batch is not included in settlement due to exceeding the Daily Limit|

|INAC| |

The first line (STAT) may be accompanied by the date/time of request processing.

The second line may be accompanied by the indication:

|REJT|Time of cancellation due to rejection or return|

|----|----------------------------------------------------------------|

|CANC|Time of cancellation of the file/batch/payment|

|----|----------------------------------------------------------------|

|SETL|Time when settlement was performed for the batch (the requested one or to which the payment relates)|

|----|----------------------------------------------------------------|

|ERRC|Time when the processing error was recorded|

|----|----------------------------------------------------------------|

|SUSP|Time when the batch (the requested one or to which the payment relates) was suspended|

|----|----------------------------------------------------------------|

|NETC|Time of receipt of this status|

|----|----------------------------------------------------------------|

|NETR|Time of receipt of this status|

|----|----------------------------------------------------------------|

|NETL|Time of receipt of this status|

|----|----------------------------------------------------------------|

|INAC|Time of receipt of this status|

In paragraph 9.1.2, position "O" "/Keyword/ BIC of the Participant Settlement Date of the corresponding Batch" is to be worded as follows:

| | |BIC of the Participant |6!n |234567 |

In paragraph 9.2.1.2, the paragraph "Field :76:" is to be worded as follows:

"Field :76: contains the response type and status of the corresponding payment.

In the case of a status response message, this field may take the following values:

|STAT|A rejection or return was generated for the payment/batch|

|REJT| |

|----|----------------------------------------------------------------|

|STAT|The Batch/Payment was cancelled due to NBUKR and/or BCS/X regulations, or was recalled by the sender|

|CANC| |

|----|----------------------------------------------------------------|

|STAT|The Batch/Payment was accepted by the system for clearing|

|NETC| |

|----|----------------------------------------------------------------|

|STAT|The Batch/Payment is awaiting the processing date|

|NETL| |

|----|----------------------------------------------------------------|

|STAT|The Batch/Payment has undergone the settlement procedure|

|SETL| |

|----|----------------------------------------------------------------|

|STAT|An error was detected during the processing of the batch/payment|

|ERRC| |

|----|----------------------------------------------------------------|

|STAT|The Batch/Payment is suspended|

|SUSP| |

|----|----------------------------------------------------------------|

|STAT|Transaction created|

|PROC| |

|----|----------------------------------------------------------------|

|STAT|The Batch is included in a clearing transaction|

|NETR| |

|----|----------------------------------------------------------------|

|STAT|The Batch is not included in settlement due to exceeding the Daily Limit|

|INAC| |

The first line (STAT) may be accompanied by the date/time of request processing.

The second line may be accompanied by the indication:

|REJT|Time of cancellation due to rejection or return|

|----|----------------------------------------------------------------|

|CANC|Time of cancellation of the file/batch/payment|

|----|----------------------------------------------------------------|

|SETL|Time when settlement was performed for the batch (the requested one or to which the payment relates)|

|----|----------------------------------------------------------------|

|ERRC|Time when the processing error was recorded|

|----|----------------------------------------------------------------|

|SUSP|Time when the batch (the requested one or to which the payment relates) was suspended|

|----|----------------------------------------------------------------|

|NETC|Time of receipt of this status|

|----|----------------------------------------------------------------|

|NETR|Time of receipt of this status|

|----|----------------------------------------------------------------|

|NETL|Time of receipt of this status|

|----|----------------------------------------------------------------|

|INAC|Time of receipt of this status|

In paragraph 10.2.1, in "Format MT196: Response to a request for recall or return of the entire Batch" and in "Format MT196: Response to a request for recall of an individual payment", position "O" "Comment (Narrative)" is to be worded as follows:

|O |77A|Comment |20*35х |ERR166 |

In paragraphs 10.2.1, 11.2.1.2, 13.2.3, 14.2.1.2, the paragraph "Field :77A:" is to be worded as follows:

"Field :77A: may contain a clarification to the response given in field :76:. Such clarification is given for the following types of responses:

|CANC |Error Description|

|ERRC | |

Field :77A: of the MTn96 message must contain the following lines:

|1 line |Error/Warning Code|

|-----------|---------------------------------------------------------|

|2 line |Error/Warning Description|

|-----------|---------------------------------------------------------|

|3-20 lines|Additional information related to|

| |the error/warning|

Lines 3-20 are optional."

In paragraph 11.2.1.2, position "O" "Comment" is to be worded as follows:

|O |77A|Comment |20*35х |Result of Recall|

In paragraphs 13.1.1, 13.1.2, 13.1.3, position "O" "List of requested fields" is to be worded as follows:

|O |77A|List |20*35х |FULL or|

In paragraph 13.1.1, position "O" "/Keyword/ BIC of the Participant Settlement Date of the Batch" is to be worded as follows:

| | |BIC of the Participant |6!n |234567 |

In paragraph 13.1.3, the paragraph "Field :77A:" is to be worded as follows:

"Field :77A: may contain:

the FULL option to request all fields of the original batch and payment.
This option must be contained only in field :77A:;
the SHORT option to request only fields :20:, :23:, :32A, 52A of the original batch and fields :20, 23, 21, 32B, 50K, 52A, 59, 32A of the original payment. This option is the default value if field :77A: is omitted in the corresponding request. This option must be contained only in field :77A:;
a list of field tags separated by commas that must be included in the response. Field tags are defined using S.W.I.F.T. standards (e.g., 52a means 52A or 52D in the case of MT102). Only field tags of the corresponding payment may be requested (in the case of a payment copy request). Only field tags of the corresponding batch and payment may be requested (in the case of a batch or file copy request)."

In paragraph 14.1.1.2, position "O" "List of requested fields" is to be worded as follows:

|O |77A|List of requested|20*35х |FULL or|

| | | | |p.13.1.3)|

In paragraph 14.2.1.2, the paragraph "Field :76:" is to be worded as follows:

"Field :76: contains the response type. In the case of a response message with a copy, this field may take the following values:

|COPY |Response to a payment copy request|

|INSTR| |

|-----|---------------------------------------------------------------|

|COPY |Error Description|

|ERRC | |

In paragraph 16.2.1, position "M" "Comment" is to be worded as follows:

|M |79 |Comment|4!a[/6!n4!n1| 1 |Request Type|STAT/0508181443+0|

| | | |!x4!n] | |/Execution Time|600 |

| | | |------|-----|------|------|

| | | |2!a | 2 |Position Status|AA |

| | | | | | | |

| | | |------|-----|------|------|

| | | |[] | |Daily Limit| |

| | | |------|-----|------|------|

| | | |/OL/15n | 4 |Total|/OL/0, |

| | | |------|-----|------|------|

| | | |/D/ | 5 |Current|/D/3000, |

| | | |------|-----|------|------|

| | | |[6!n[/8x]] | 6 |Operational|040929/MORNING |

In paragraph 16.2.1, the paragraph "Field :79:" is to be worded as follows:

"Field :79: Contains the response to the corresponding request.

The following responses are possible:

|AA|Position is not blocked|

|--|------|

|DA|Position is blocked for debit|

|--|------|

|AC|Position is blocked for credit|

|--|------|

|DC|Position is blocked for debit and credit|

In paragraph 17.2, position "O" "Position Movement Line" is to be worded as follows:

|O |61 |Movement|4!n1!a15d1!a3| |Comment|040929D1700,S104|

| | |Line|!n16x//16x | |see below|12345//123456 |

| | |position|16x] | | |040928 |

The processing date of the batch is added to the second line of field 61.

Position "O" "Position Movement Line" in the "Comment" column is supplemented with the following paragraph:

"040929D1700,S10412345//123456

000251/CREDIT/040928/REF0234

This fragment contains the number of payments included in the sum in that line (6 characters), field :23: of the corresponding batch after the symbol "/" and the batch processing date in DDMMYY format after the symbol "/"."

In paragraph 19.1, position "M" "Comment" is to be worded as follows:

|M |77A|Comment|2!a10!n | 1 |Error Code|EA6 |

| | | |------|-----|------|------|

| | | |19*35х |2... |Error Description|Not Found|

| | | | | |; |Related|

In paragraph 19.1, the paragraph "Field :77A:" is to be worded as follows:

"Field :77A: must contain the description of the error indicated in field :76.

Field :77A: MTn96 must contain the following lines:

|1 line |Error/Warning Code|

|-----------|---------------------------------------------------------|

|2 line |Error/Warning Description|

|-----------|---------------------------------------------------------|

|3-20 lines|Additional information related to|

| |the error/warning|

Lines 3-20 are optional."

In paragraphs 22.1, 22.2, the column "LS" is to be worded as follows:

"LS

50K

20x".

In paragraphs 22.3, 22.4, the column "LS" is to be worded as follows:

"LS

20x".

In paragraphs 22.1, 22.2, the column "SCHET" is to be worded as follows:

"SCHET

16!n".

In paragraphs 22.3, 22.4, the column "SCHET" is to be worded as follows:

"SCHET

50K

16!n".

In paragraph 22.5, position "50K" "LS" is to be worded as follows:

|50K|20x |LS |T50_LS |Character(20)|Account Number -|filled only when|

In paragraph 22.7, position "59" "LS" is to be worded as follows:

|59 |20x |LS |T59_LS |Character(20)|Account Number|

In paragraph 22.5, position "59" "SCHET" is to be worded as follows:

In paragraph 22.7, position "50K" "SCHET" is to be worded as follows:

Paragraphs 6.3.10 and 6.3.11 are to be excluded (since messages MTn99/SETPARTICIPANTDEBITCAPLIMIT and MTn99/SETSYSTEMDEBITCAPLIMIT are not used in this version of the software).
Paragraph 20.3 "Processing of a Payment Document" is to be worded as follows:

"20.3. Processing of a Payment Document

|Processing Steps| Description|

|of the Payment| |

|Document| |

|--------------|------------------------------------------------------|

| F |A payment document is created based on the message|

|--------------|------------------------------------------------------|

| C |Payment confirmation is required|

|--------------|------------------------------------------------------|

| H |Outgoing files and a list of rejected payments are created|

|--------------|------------------------------------------------------|

| P |Validation is completed|

|--------------|------------------------------------------------------|

| I |Positions are recalculated|

|--------------|------------------------------------------------------|

| S |Batches are formed that can potentially be recalled|

|--------------|------------------------------------------------------|

| L |Batches are created|

|--------------|------------------------------------------------------|

| D |Batch notifications are created|

|--------------|------------------------------------------------------|

| 3 |Awaiting processing date|

|--------------|------------------------------------------------------|

| A |Document is ready for archiving|

Figure 3. Processing of a Payment Document".

In paragraph 20.4, the table is to be worded as follows:

|Transaction States in BCS/X | Description|

|-------------------|-------------------------------------------------|

| R |Creation of transaction|

|-------------------|-------------------------------------------------|

| I |Transaction not included in settlement (inactive) due|

| |to exceeding the Daily Limit|

|-------------------|-------------------------------------------------|

| C |Transaction is ready for execution|

|-------------------|-------------------------------------------------|

| S |Transaction is suspended (participant and/or position|

| |are blocked)|

|-------------------|-------------------------------------------------|

| N |Transaction is transmitted for execution|

|-------------------|-------------------------------------------------|

| L |Transaction is suspended due to the operational day schedule|

|-------------------|-------------------------------------------------|

| F |Transaction is being executed|

|-------------------|-------------------------------------------------|

| X |Error|

The 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 are supplemented with paragraph 23 of the following content:

"23. Message Exchange Formats

between the Processing Center and the ACH

23.1. Presentation File - MT250

The format of the presentation file accepted by the Batch Processing Center from the Electronic Payment System fully corresponds to MT150 (Chapter 3 "Presentation File. Message Type MT 150", general information on message formation is described in Chapter 2) with the following changes:

Message type 250;
Batch type within the file 203;
The user reference of the message has the format 12x (tag 108 of the MT250 header);
The number of batches within one file is no more than 999.

23.2. Specifications for Batch MT203 within MT250

Mandatory Sequence A: General Information

| | | | | |

|-----|-----|-----------------|------------|--------------------------|

|M |19 |Amount of Funds|17d |Total amount of funds for|

|-----|-----|-----------------|------------|--------------------------|

|M |30 |Settlement Date|6!n |Current settlement date|

|-----|-----|-----------------|------------|--------------------------|

|M |52A |Debtor |6!n |BIC and name of|

| | | |5*50x |the Participant whose|

|-----|-----|-----------------|------------|--------------------------|

|M |72 |Sender Information|6*35x |After the keyword|

| | | |26x] |payment purpose for|

| | | |[//33x] |the entire batch. Continuation|

Mandatory Sequence B: Payment Detail

In each Sequence B, the credited participant and the amount are indicated.

Existence	Tag	Field Name	Format	Comment
M	20	Payment Reference	16x	Unique payment reference
---	---	---	---	---

M	21	Transaction Reference	16x	Constant NONREF is specified
---	---	---	---	---
M	32B	Payment Amount	3!a15d	Currency code and payment amount
---	---	---	---	---
M	58A	Creditor	6!n	BIC and name of the participant whose position is credited
			5*50x

The following rules apply to the processing of MT203 included in the MT250 file:

All MT203 packages are processed on an "all or nothing" basis.
This means that:
In case of an error in any of the MT203 packages, the MT250 file is rejected; In case of exceeding the liquidity limit, all MT203 packages take the status "Inactive".
The MT203 package contains the total debit obligations for each counterparty on a bilateral basis.
For example, if participants have the following obligations:
Participant A has obligations to:
Participant B 1000 KGS
Participant C 2000 KGS
Participant B has obligations to:
Participant A 1500 KGS
Participant C 2500 KGS
Participant C has obligations to:
Participant A 1300 KGS,
In this case, MT250 will contain 3 MT203 packages:

MT203 for Participant A:
:19:3000,
:30:040506
:52A:101109
Participant A
:72:/NUM/2
/PRT/01
:20:BNKA001
:21:NONREF
:32B:KGS1000,
:58A:201109
Participant B
:20:BNKA002
:21:NONREF
:32B:KGS2000,
:58A:301109
Participant C

MT203 for Participant B:
:19:4000,
:30:040506
:52A:201109
Participant B
:72:/NUM/2
/PRT/01
:20:BNKB001
:21:NONREF
:32B:KGS1500,
:58A:101109
Participant A
:20:BNKB002
:21:NONREF
:32B:KGS2500,
:58A:301109
Participant C

MT203 for Participant C:
:19:1300,
:30:040506
:52A:301109
Participant C
:72:/NUM/1
/PRT/01
:20:BNKC001
:21:NONREF
:32B:KGS1300,
:58A:101109
Participant A

23.3. Procedure for processing MT203 packages

The SPK accepts MT250 files with MT203 packages inside. Each package is automatically assigned a reference in the format:
12x/3n

12x - user message reference;
3n - sequence number of the package in the message.

If an error is detected in any payment when receiving the MT250 file, the entire package is rejected with an MT296 notification. Notifications are sent to the sender of the MT250 (PC).

For each package, liquidity limit check upon receipt is not performed. In case of exceeding the liquidity limit, a notification of the position status (MT986) is sent to the participant.

Upon the onset of the "clearing" period, in case of exceeding the liquidity limit, the package is rejected and corresponding MT296 notifications are sent:
9. To the file sender;
10. To the debited participant.

Upon completion of the "clearing" period, the SPK forms an MT250 for distribution to participants. The files include packages:
11. Copy of the original MT203 to the debited participant;
12. MT203 with a copy of the payment to the credited participant.

The format of MT296 notifications fully corresponds to MT196 (paragraph 7.2). The formats of informational messages (for example, about the change of the clearing session period, etc.) coming from the SPK to the EPC are described in the corresponding chapters of the document.

Lineage: No known changes

Timeline