Changes in the format of the electronic signature of messages sent to the GIS GMP.

Since July 1, 2015, new formats have been used for the interaction of the State Information System on State and Municipal Payments (GIS GMP) and information systems of participants - 1.16 (current version 1.16.1). In accordance with the formats of version 1.16, a new GIS GMP service was put into operation. Test service and industrial service are registered in the interdepartmental electronic interaction system with the assignment of SID0003663 and SID0003998, respectively.

The change in formats is associated with a change in the order of interaction with the GMF GIS. In the standard configurations of the program "1C: Accounting of a state institution 8" edition 1 (from version 1.0.34), then - BGU1, and edition 2 (from version 2.0.34), then - BGU2, the change in the order of interaction with the GIS GMP was taken into account and implemented data exchange with GIS GMP in version 1.16.1 format. Interaction with GIS GMP in version 1.15 formats is also possible. *

Changes in the format of the electronic signature of messages sent to the GIS GMP

According to the formats of version 1.16, an electronic signature (ES) must be used in the XadES-T format, which assumes the installation of a time stamp. To do this, when generating the signature, a call is made to the trusted time server (TimeStamp Authority), hereinafter referred to as the TSA server.

According to information from the technical support of the GIS GMP “The participant can access any TSA server. At the moment, the Federal Treasury does not provide a TSA server for time stamping. "

TSA server is a rather expensive software product. It is marketed as a turnkey solution by various companies. It is probably assumed that the participant himself must attend to the availability of this service.

The program "1C: Accounting of a State Institution 8" implements interaction with the TSA server, specified in the participant's settings, using the TSP protocol. The TSA server is addressed via the http protocol.

The address of the TSA server is set in (in BSU1: menu "Calculations - Interaction with GIS GMP / IS RNIP / UNP", in BSU2: command Tinctures of organizations for exchange with GIS GMP, UNP v Navigation bars organization cards). In a typical configuration, by default, the Crypto-Pro test service is used, located at http://www.cryptopro.ru/tsp/tsp.srf which is listed in Settings of the exchange participant with GIS GMP as the address of the TSA server.

According to information from the Crypto-Pro website: “This TSP server should be used for testing purposes only. Do not trust the timestamps issued by this server. "

Restriction on the use of electronic signature when transferring by GAN of charges of subordinate institutions

According to formats 1.16, it is unacceptable to sign with the signature of GAN (a participant in direct interaction) accruals formed by its subordinate institutions - AN (participants in indirect interaction). Each participant must sign their charges with their electronic signature.

According to clause 2.26 of the Procedure for information interaction of the Participants with the operator of the GIS GMP (Order of the Treasury of Russia dated November 30, 2012 No. 19n), the interaction of charge administrators (AS) with the GIS GMP is possible both through the main administrator of charges (GAN) - when registering in the GIS GMP of the chief administrator of charges with a list of charge administrators who will interact with the GIS GMP through GAN, and independent - when registering the Academy of Sciences in the GIS GMP as an administrator of charges.

In the program "1C: Accounting of a state institution 8" implemented interaction of administrators of charges with the GIS GMP both independently and through the main administrator of charges.

In the program "1C: Accounting of a state institution 8", two methods of generating electronic signatures are implemented:

1. When performing an exchange with the service (performed in the base of the sending member)- in this case, according to the documents sent to the GIS GMP - accruals, files are formed, and each charge in the file is signed by the signature of the participant who generated this charge.

This method is suitable for participants in direct interaction, as well as for participants in indirect interaction (if there is a technical possibility in the GAN database to form ES for charges subordinate).

2. A separate process (performed in the base of the participant who generated the accrual)- in this case, in the participant's documents " Receipt for payment " the button “ Sign the electronic signature " when you click on which, an xml file is generated and the digital signature of the certificate specified in the settings of this participant is signed. The generated and signed file is saved in the information register " Signed charges ", and the signed document itself becomes unavailable for editing (until the signature is removed). When a participant's accruals are sent with this setting, a previously saved and signed xml file is sent. Unsigned charges cannot be sent.

Changes in the order of interaction with GIS GMP

The procedure for transferring charges has changed significantly:

When transferring charges to the GIS GMP in 1.16 formats, several charges may be in one file.
The transfer of charges itself has become asynchronous:
a file containing several charges (package of charges) is transferred to the GIS GMP. If the packet format does not contain errors, then it enters the service queue for processing, and in response the service sends the packet registration number.
later, the participant forms a request for processing this packet and sends it to the service. If by this time the package has been processed, then the download result is returned for each of the charges in the package. If the charge has been loaded successfully, then the code "0" is returned to it. If not successful, then the code and error message are indicated.

The list of error codes and their meaning are listed in the formats of exchange with GIS GMP 1.16 in section “6. List of controls ".

Transfer of charges to the GIS GMP in the program "1C: Accounting of a state institution 8"

When exchanging in 1.16 formats, non-documents are transferred to the GIS GMP " Receipt for payments y ", and documents" Packages of charges ".

In the tabular section of the document “ Accrual package " contains a list of documents " Receipt for payment " and / or " Accrual from the subordinate "(when transferring charges of subordinate AH from remotely located bases). One document each " Package of charges " one file is formed containing the charges listed in the tabular section of the document. Each charge in the file is signed by the participant's electronic signature specified in the settings.

When sending a document " Accrual package " into the service, if it does not contain errors, it is assigned a registration number. Documents " Receipt for payment " the status is assigned " Submitted for processing ".

Later, the participant forms a request for the result of processing the package, and if by this time the package has been processed, then the result of processing the award is loaded into the document for each charge. If the accrual is a document " Receipt for payment " loaded successfully, it is assigned the status " On performance and". If errors were found during the download, the status changes back to " Prepared ".

In the program "1C: Accounting of a State Institution 8" for the exchange with the GIS GMP, processing is applied, which allows you to send charges to participants, request the result of processing charge packages, payments, and verify charges both for payments and without payment.

Treatment " Formation of receipts and data exchange with GIS GMP / IS RNIP / UNP " provides for exchange with GIS GMP both in formats 1.15 and in formats 1.16. Exchange parameters are set on the corresponding processing tabs.

For formats 1.16, the necessary charges are marked in processing. Further, documents are automatically generated “ Packages of charges ", for them xml-files are generated and signed with electronic signature. The signed files are transferred to the GIS GMP.

On a separate processing tab, it is possible to send independently generated documents to the GMP GIS " Packages of charges " or, according to the documents sent for processing, request the processing result.

Standard configurations of BGU1 and BGU 2 include Instructions for setting up the configuration "Accounting of a state institution" for interaction with GIS GMP in formats 1.16

In the Instructions for setting up the configuration "Accounting of a state institution" for interacting with the GIS GMP in formats 1.16 (section "Procedure for exchanging data with the GIS GMP - Export receipts"), examples of transferring charges to the GIS GMP both with the use of this processing and without use are considered.

Changing the format for generating a unique accrual identifier

When switching to 1.16 formats, follow in the reference “ Templates of identifiers of documents "Receipt for payment" " re-fill the setting for each institution.

Changing the algorithm for generating payer identifiers

According to formats 1.16, a single payer identifier is possible only for individuals who are individual entrepreneurs (IE). For individuals who are not individual entrepreneurs, only alternative payer identifier - according to TIN, SNILS, passport and other documents and a specific list.

Therefore, when switching to 1.16 formats, you should check for the elements of the directory " Nomenclature" with type " State service " settings used for generating payer identifiers and, if necessary, add new ones.

Transition from 1.15 to 1.16 formats

To switch to exchange with the SID0003998 service in 1.16 format, you must do the following.

1. Load the GIS GMP 1.16 formats from the configuration delivery file (GIS GMP 1.16.xml).

The GIS GMP 1.16.xml file is located in the configuration template directory \ v82 \ 1c \ StateAccounting \ 1_0_2X_X \ ECExchangeFormats.

See point 4. Loading the exchange formats with the GIS GMP of the section Configuring the BGU for interaction with the GIS GMP Instructions for setting up the "Accounting of a state institution" configuration for interacting with the GIS GMP by formats 1.16.

2. Set the settings of the exchange participants for all participants - direct and indirect.

For more details see clause 7. Setting up participants for exchange with GIS GMP section Configuring BGU to interact with GIS GMP Instructions for setting up the "Accounting of a state institution" configuration for interacting with GIS GMP by formats 1.16.

3. Edit Template for generating a unique identifier of accruals in the document "Receipt for payment".

For more details see clause 8. Template for forming a unique identifier of accrual of the section Configuring BGU for interaction with GIS GMP Instructions for configuring the "Accounting of a state institution" configuration for interaction with GIS GMP in formats 1.16.

4. Check the used types of payer identifiers in the item setup and, if necessary, add new ones (SNILS or others).

5. If possible, fill in the requisite " Compiler status (101) " since this is a required field in the document " Receipt for payment ".

For more details on interaction with GIS GMP - in the Instructions for setting up the configuration "Accounting of a state institution" for interaction with GIS GMP in formats 1.16:

BGU1 - menu Calculations - Interaction with GIS GMP / IS RNIP / UNP - Help on interaction with GIS GMP ".
BGU2 - section "Normative reference information", navigation panel "See also - Help on interaction with GIS GMP".

Ministry of Finance of the Russian Federation

FEDERAL TREASURY

On the formats of interaction of the GIS GMP with the information systems of the participants of versions 1.16.5 and 2.0

We hereby inform you about the development by the Federal Treasury of Interaction Formats of the State Information System on State and Municipal Payments with the Participants' Information Systems version 2.0 (hereinafter referred to as the 2.0 formats), providing for the use of a single electronic service of the interdepartmental electronic interaction system, functioning in accordance with the Methodological Recommendations for working with the interdepartmental system. electronic interaction version 3.XX.

At the same time, in order to ensure interaction of participants with the State Information System on State and Municipal Payments (hereinafter referred to as the GIS GMP) during the transition to the above formats, we inform you about the changes corresponding to these formats, reflected by the Federal Treasury in the Forms of Interaction of the State Information System on State and Municipal Payments. payments with information systems of participants of version 1.16.5 (hereinafter - formats 1.16.5) of the electronic service GIS GMP of the unified system of interdepartmental electronic interaction, functioning in accordance with the Methodological Recommendations for working with the system of interdepartmental electronic interaction of version 2.XX.

Formats 2.0 and formats 1.16.5 are posted on the official website of the Federal Treasury on the Internet in the "GIS GMP" section (roskazna.ru/gis) and come into force on March 15, 2018.

Participants of the GIS GMP can start testing the types of GIS GMP information developed in accordance with Formats 2.0 using the emulator of the interdepartmental electronic interaction system in December 2017. At the same time, the opportunity to test with GIS GMP will be provided to participants from January 15, 2018.

At the same time, we would like to inform you that the GIS GMP electronic service, functioning in a unified system of interdepartmental electronic interaction, in accordance with the Interaction Forms of the State Information System on State and Municipal Payments with the information systems of participants, version 1.16.4, will be updated to 1.16.5 formats. on the test loop (SID0003663) on February 1, 2018, on the industrial loop (SID0003998) on March 15, 2018. At the same time, in accordance with the Plan for the transition of federal executive bodies and state extra-budgetary funds to provide information using a single electronic service of the interdepartmental electronic interaction system in accordance with the methodological recommendations for working with the system of interdepartmental electronic interaction version 3.XX, approved at a meeting of the subcommittee on the use of information technology in the provision of state and municipal services to the Government Commission on the use of information technology to improve the quality of life and business conditions, this electronic service GIS GMP (SID0003998) will be decommissioned in December 2018.

I ask you to bring the above information to the participants of the GIS GMP, informing about the need to ensure the configuration of the information systems they use in accordance with the 1.16.5 formats by March 15, 2018, as well as to ensure the transition to interaction with the GIS GMP in accordance with the 2.0 formats within 1 December 2018.

And about. the head

Federal Treasury

S.E. Prokofiev

Electronic text of the document

prepared by JSC "Kodeks" and verified by.

As part of supporting the album of GIS GMP 1.16.2 formats and legislation (subparagraph "b" of clause 1 of Order No. 148 of the Ministry of Finance of the Russian Federation of 09/23/2015, effective date from 03/28/16) the following checks have been implemented:

Introduce the previously implemented checks on the 1.16.2 album into the 1.6.0 release:

1. For the field SupplierBillID:

1.1. If field value = "0".

If the field value = "0", then check that the "PayerIdentifier" field has a non-zero value. If both fields are equal to "0", then return the error "UIN and payer's identifier cannot be equal to zero at the same time!"

1.2. If the field is 20 characters long .

1.2.1. 16 digits specified in digits from 4 to 19 cannot all be = 0 at the same time. With zero values, return the error "Possible UIN values:" 0 "or a string with a dimension of 20 non-blank characters or 25 digits in accordance with the format album 1.16.2! "

1.2.2 The value of the UIN field should not coincide with the value of the KBK field. If there is a match, return the error "KBK cannot match UIN"

1.2.3 If the value in the 20th bit of the UIN does not correspond to the calculated value, then the error “Check bit of the UIN has an incorrect value” is returned.

The control category of the UIN is formed according to the following rules :

the value of the UIN variable consists of numbers;
each UIN category, starting from the most significant category, is assigned a set of weights corresponding to a natural series of numbers from 1 to 10, then the set of weights is repeated;
each digit of the UIN is multiplied by the assigned category weight and the sum of the products obtained is calculated;
the check bit for UIN is the remainder of dividing the received sum by the module "11". The check bit must have a value between 0 and 9;
if a remainder equal to 10 is obtained, then to ensure a one-bit check bit, it is necessary to re-calculate using the second sequence of weights, which is the result of a cyclic shift of the original sequence by two digits to the left (3, 4, 5, 6, 7, 8, 9, 10, 12...). If, in the case of repeated calculation, the remainder of the division is again kept equal to 10, then the value of the check digit is set equal to "0".

Example:

UIN (without check discharge) is equal to 1881035013021000001

Calculation of the value of the control bit UIN:

Calculation of the value of the check digit with the first weighting factors:

1 * 1 + 8 * 2 + 8 * 3 + 1 * 4 + 0 * 5 + 3 * 6 + 5 * 7 + 0 * 8 + 1 * 9 + 3 * 10 + 0 * 1 + 2 * 2 + 1 * 3 + 0 * 4 + 0 * 5 + 0 * 6 + 0 * 7 + 0 * 8 + 1 * 9 = 1 + 16 + 24 + 4 + 0 + 18 + 35 + 0 + 9 + 30 + 0 + 4 + 3 + 0 + 0 + 0 + 0 + 0 + 9 = 153

153 \ 11 = 10 (remainder of division)

Since the remainder of the division is 10, the calculation is performed with the second weight coefficients:

1 * 3 + 8 * 4 + 8 * 5 + 1 * 6 + 0 * 7 + 3 * 8 + 5 * 9 + 0 * 10 + 1 * 1 + 3 * 2 + 0 * 3 + 2 * 4 + 1 * 5 + 0 * 6 + 0 * 7 + 0 * 8 + 0 * 9 + 0 * 10 + 1 * 1 = 3 + 32 + 40 + 6 + 0 + 24 + 45 + 0 + 1 + 6 + 0 + 8 + 5 + 0 + 0 + 0 + 0 + 0 + 1 = 171

171 \ 11 = 6 (remainder of division)

Full UIN: 18810350130210000016

1.3. If the field is 25 characters long.

1.3.1. 16 digits specified in digits from 9 to 24 cannot all be = 0 at the same time. With zero values, return the error "Possible UIN values:" 0 "or a string with a dimension of 20 non-blank characters or 25 digits in accordance with the 1.16.2 album! "

If the value in the 25th bit of the UIN does not correspond to the calculated value (according to the algorithm from clause 1.2.3), then the error "Control bit of the UIN has an incorrect value" is returned

1.4. Add a check to the validation of the UIN value: the last digit (20 or 25 characters) must be a digit.

2. If the field value " PayerIdentifier"=" 0 ", then check that the SupplierBillID field has a nonzero value. If both fields are equal to" 0 ", then return the error" UIN and payer ID cannot be equal to zero at the same time! "

3. Change the format of the field " Narrative"- input from 1 to 210 characters is allowed.

4. In the " Purpose"add possible values of VU, DK, PK, KK, TK.

5. Change the format of the field " TaxDocNumber": Valid values are from 1 to 15 characters.

6. Change the regular expression for the field " PaymentType", the value" 0 "or the input of 2 uppercase letters of the Cyrillic alphabet is allowed.

Input mask:

or the value "0".

7. Change the format of the field " PayeeName": Valid values are from 1 to 500 characters.

8. For the field KBK:

8.1. The field can take the value "0"

8.2 If the value is nonzero, the BCF field should not coincide with the value of the UIN field. If there is a match, return the error "KBK cannot match UIN"

8.3 In the event that funds are credited to the "40101%" account, then the BCF value should be non-zero. Otherwise, issue the error "The value of the KBK for the recipient's account 40101% should not be equal to zero!"

9. For the field OKTMO:

9.1. The presence of three zeros in the most significant digits in the field value is not allowed (left)

Input masks:

([^ 0 ^ \ D] \ d (2) | \ d (2) [^ 0 ^ \ D] | \ d [^ 0 ^ \ D] \ d) \ d (8)

value "0"

9.2 If funds are credited to the "40101%" account, then the OKTMO value must be non-zero. Otherwise, issue the error "The value of OKTMO with the recipient's account 40101% should not be equal to zero!"

10. For the details of the KBK (CBC, value "0" or 20 characters), OKATO (value "0", 8 or 11 characters), KIO (5 characters) and UIN (PaymentID, 20 or 25 characters) can take the value zero ("0");

11. For TIN details (INN, 10 or 12 characters) and checkpoint (KPP, 9 characters) are the first two characters cannot simultaneously take on the value zero ("0"). The check for invalidation is currently implemented three leading characters zero ("0").

In addition, for checkpoint 5 and 6, the symbol can be capital Latin letters or numbers, and symbols 1-4 and 7-9 - only numbers.

PayeeINN input mask ("PayeeINN"):

([^ 0 ^ \ D] \ d | \ d [^ 0 ^ \ D]) \ d (8)

PayeeKPP input mask ("PayeeKPP"):

([^ 0 ^ \ D] \ d | \ d [^ 0 ^ \ D]) \ d (2) (2) \ d (3)

12. Implement a check that PaymentDate no more than the current system date. If the date is exceeded, issue the error "Payment date must not exceed the current date and time!"

13.In system setting with code 102012 ("Unique identifier assigned by the Federal Treasury") add validation of the entered value. A valid value of 6 characters (letters and numbers). Otherwise, display the error text "Allowed values are 4 digits or 6 letters and numbers!"

Input mask:

^ (\ d (4) | (6)) $

14. Filling INN individual payer (INN, 12 characters) becomes mandatory under the following conditions:

a) Status = "03", "16", "19", "20", "24", TaxDocNumber = "0", SupplierBillID = "0".

b) Status = "09" - "14", SupplierBillID = "0".

If, under these conditions, the TIN is not filled in, then issue the error "Under the conditions of UIN = 0, document number = 0, payer's status code = 03,16,19,20 or 24, as well as for UIN = 0 and payer's status code = 09, 10, 11, 12, 13 or 14 the payer must be an individual or individual entrepreneur with identification by TIN! ".