Medical institutions use not only paper sick leave, but also electronic certificates of incapacity for work (ELN). This simplifies the interaction between hospitals, Social Insurance Fund and employers.
Exchange with the FSS is implemented in 1C. If the 1C-Reporting service is connected, the settings are performed automatically. If the service is not used, the process will take a little longer.
In the instructions, we will look at how to independently download and install FSS certificates for 1C, as well as setting up exchange with the FSS using the example of the 1C 8.3 ZUP program.
Connection
To activate the service, fill out an application for its connection.
You can find detailed information on how to do this in the “Subscriber Service” and “Tax Representative Service” sections.
Within three business days you will receive confirmation that your application has been accepted. If the information in the application is incorrect or your tariff plan does not provide for connection of the service, a notification will be sent to the system mailbox indicating the reason for its rejection.
After processing the application, a connection notification will be sent to your mailbox.
You can view all notifications:
- in “Referent” - on the “News” tab in the “Distribution” section;
- in “Online Sprinter” - on the “Letters from Tax” tab;
- In Taxi-Docliner - on the "Mail" tab in the "Mailout" section.
You can monitor the status of your application in your “Personal Account” on the “Management” tab.
The first stage is registration on the Portal of the FSS of the Russian Federation.
In case you are already registered on the Portal of the FSS of the Russian Federation https://fz122.fss.ru or to receive a payslip file in accordance with Form 4 of the FSS of the Russian Federation . xml
established
by the Technology
, use third-party software (for example, accounting systems, Parus, etc., or provided by your special operator), proceed to the second stage.
Download the Portal of the FSS of the Russian Federation https://fz122.fss.ru in your Internet browser, click Registration
,
a card opens to fill out the data of the user authorized by the head of the organization to fill out the pay slip according to Form 4 of the Federal Tax Service of the Russian Federation, you need to come up with a unique user name
and a complex
password
, which you will use in the future to work on the Portal of the FSS of the Russian Federation.
You can use Russian and Latin letters, both lowercase and uppercase, as well as numbers. After that, click the button Go to step 2
.
After this, within 24 hours, a letter will be sent to the mailbox you specified during registration about the need to activate your account on the Portal of the FSS of the Russian Federation. Click on the link in the middle of the letter to activate your account.
You will automatically be taken to the FSS RF Portal, enter your username
and
password
in the top left corner and click
Login
After that, through the menu Profile - Organizations
and click the
Add button.
In the card that opens, fill in the required fields, in the Type of organization field – Third party organization
, in
the Name
- Full name of your organization, fill in the fields
TIN, KPP, OGRN, Registration number of the policyholder
,
Address
, in the
Regional office/branch of the Fund
select
your
branch and click the
Save button.
Policyholder Application button in the horizontal menu
, check that all fields are filled in correctly, and click the
Print button.
Print out the specified application on paper, sign it with the head of the organization, affix the seal of the organization or individual entrepreneur (if any), send it by mail to the address of the Fund branch:
Within a few working days after your application is received at the Fund’s office, you, as a policyholder, will be given expanded rights on the RF FSS Portal, about which you will receive a letter to the email address specified when registering on the RF FSS Portal.
Similarly, you can fill in information about your other organizations (no more than 100).
When, after receiving a new certificate, can you send reports to the FSS?
It is recommended to send a report to the FSS within 2-3 hours from the moment the certificate is received. This time is necessary to synchronize software settings.
To successfully send a report after registering a certificate:
In "Referent":
Update the Referent settings and make sure that the new certificate is specified in the exchange direction settings.
If the old certificate is specified in the settings:
- Open the menu item “Options” - “Box settings” - “FSS” tab;
- Select the line with the data in the “Exchange Directions” section;
- Click the "Edit" button;
- In the “Personal Certificate” item, click the “…” button and select a new certificate;
- Click “Select” - “Ok”.
In Taxi-Docliner:
Update the Taxcom-Docliner program settings and make sure that the new certificate is specified in the exchange direction settings.
In Online Sprinter:
Settings are updated automatically. To submit a report, log into Online Sprinter using a new certificate, which will be displayed on the main page of the service.
In the 1C-Sprinter program:
Update the settings of the 1C-Sprinter program.
Code table
The code, name and description of errors can be viewed on the official website of the FSS of the Russian Federation.(https://portal.fss.ru/fss/analytics/gate/error-description)
Below is a table that describes in detail what an error code is when sending a sick leave certificate to the Social Insurance Fund, for example, code 508 is a logical control error, and code 503 means that the calculation file did not pass format control. The reasons for these errors and ways to solve them are also given.
Error code | Name | Reason for appearance | Solution |
10 | The file cannot be decrypted. | The file is damaged, expired, or invalid. | It is necessary to check the status of the file (expiration, legal accuracy). |
11 | Failed to verify digital signature. | The encryption sequence is broken; The digital signature was entered incorrectly. | Check the encoding algorithm; contact the certification authority (hereinafter CA) and re-sign the certificate. |
12 | The digital signature is not correct. | The digital signature is incorrect or missing. | If there is no signature, contact the CA to affix it; If the digital signature is incorrect, the certificate must be reissued. |
13 | The certificate does not contain the registration number of the policyholder. | When preparing the document, the registration number of the policyholder was not indicated. | The certificate must be reissued. |
14 | The certificate does not contain a subdivision code of the FSS of the Russian Federation. | The certificate does not include the department code of the FSS of the Russian Federation. | You should contact the CA and reissue the certificate. |
15 | Encryption error. | Violation of the encoding algorithm in the file transfer system. | Restore the file encryption sequence and resend it to the FSS. |
16 | Invalid policyholder registration number format. | The number of digits of the registration number is less than or greater than 10. | The certificate must be reissued. |
17 | Incorrect code format for the Federal Tax Service of the Russian Federation. | The number of department code characters is less than or greater than 4. | Re-issue the document with the appropriate FSS unit code. |
18 | The calculation is encrypted using a key that does not match the public key of the Federal Tax Service of the Russian Federation. | The FSS authorized person certificate has been selected incorrectly; The validity period of this document has expired. | Use a new certificate (to do this, you need to go to the official website of the FSS of the Russian Federation (https://www.fss.ru/uc), download the new certificate and install it in the repository). |
19 | The payment is not encrypted or signed. | The file does not have an encryption code or does not have an electronic digital signature. | Check the calculation encoding sequence and re-encrypt. Enter your digital signature. |
20 | Unknown file format. | The system supports XML format and XD schema. | Bring the document into the format required by the rules. |
41 | No trust. | The digital signature does not meet the requirements of the Federal Law “On Electronic Signatures” dated April 6, 2011; the validity period has ended. | Issue a certificate in full compliance with existing digital signature requirements. |
42 | Error validating the certificate. | Possible violation of the encoding algorithm | Check the coding sequence and resubmit for verification. |
43 | The certificate has been revoked. | The document has no legal validity. | Contact the CA to obtain a new certificate. |
44 | The certificate revocation list (CRL) was not found or has expired. | Outdated SOS database at the CA. | You should contact the CA to resolve the problem. |
45 | The certificate is damaged | The file encryption technology has been broken. | Check the coding sequence. |
46 | The certificate has expired. | The validity period has come to an end. | Receive the document. |
50 | The certificate does not contain the policyholder's TIN. | TIN is not specified. | The certificate needs to be reissued. |
51 | The TIN indicated in the calculation is not in the Unified State Register of Legal Entities database. | Outdated Unified State Register of Legal Entities database. | It is necessary to go to the Federal Tax Service at the place of registration to correct the deficiency. |
503 | The calculation XML file did not pass format control. | The calculation format is incorrectly specified. | Create a new calculation file in accordance with the required format. |
504 | The certificate indicates a non-existent division of the FSS of the Russian Federation. | There was a typo when entering data. | The certificate needs to be reissued. |
505 | Incorrect file names. | The document name is incorrectly formulated. | Correct the name in accordance with the Technology for accepting payments, which is contained on the official website of the FSS. |
506 | The second sections of the calculation have the same taxation figures. | There was a typo when filling out the calculation form. | The shortcomings in the calculation sections should be corrected. |
507 | There is no *.XML file. | The file was not loaded or not found. | Re-upload the file to the system. |
508 | Logic control errors. | There are errors in the calculation parameters. | All errors must be eliminated. |
509 | The reporting period in the XML file did not match the reporting period in the file name. | Data entry error. | Bring the contents of the document in accordance with the name (or vice versa); reissue the certificate. |
511 | Error reading XML calculation file. | The XML format is not followed or the document is empty. | Re-create the file (making sure that it is in XML format) and send it to the FSS. |
512 | The calculation year in the XML file did not match the calculation year in the name of the calculation file. | Data entry error. | Bring the contents of the document in accordance with the name (or vice versa); reissue the certificate. |
513 | The policyholder's registration number on the certificate does not match the registration number indicated in the file name. | Incorrectly filled in policyholder number. | Bring the contents of the document in accordance with the name (or vice versa); reissue the certificate. |
514 | The policyholder's registration number in the XML file does not match the registration number in the digital signature certificate. | There was a typo when entering data. | Contact the CA and reissue the certificate. |
515 | The policyholder registration number in the XML file does not match the policyholder registration number specified in the file name. | Data entry error. | Bring the contents of the document in accordance with the name (or vice versa); reissue the certificate. |
516 | The additional separate division code in the XML file does not match the policyholder number specified in the file name. | Data entry error. | Bring the contents of the document in accordance with the name (or vice versa); reissue the certificate. |
517 | The file is too large. | The size exceeds 665 kilobytes. | Create a new file no larger than 665 kilobytes. |
518 | Zero file size. | File size 0 kilobytes. | Create a new file whose size exceeds 0 kilobytes. |
519 | The policyholder's TIN in the XML file does not match the policyholder's TIN in the certificate. | Data entry error. | Contact the CA and get a new certificate. |
520 | The policyholder's OGRN in the XML file does not match the policyholder's OGRN in the certificate. | Data entry error. | Contact the CA and reissue the document. |
550 | The certificate is not a qualified certificate. | The document is not qualified. | Reissue the certificate in an officially accredited CA. |
552 | The QUART_NUM attribute of the TITLE element can only have a value from the following series: “3”, “6”, “9”, “0”, “03”, “06”, “09”, “12”. | The TITLE element's QUART_NUM Attribute value does not match the specified number series. | Bring the value of the element in accordance with the specified number series. |
598 | The policyholder's TIN in the XML file differs from the TIN corresponding to the registration number. | There was a typo when filling out the form; The specified TIN is outdated. | Check that the TIN provided is up-to-date; reissue the certificate. |
599 | Internal error in the received data control module. | Technical failure of the site. | Contact technical service to troubleshoot problems. |
When sending reports to the FSS, the message “The validity period of the certificate for the FSS has expired” appears.
To correct this situation:
- Go to the Subscriber Support Forum in the section “Certificates for EDF with FSS have been updated”;
- Download the archive with FSS certificates;
- Install the F4_FSS_RF_2016_qualified certificate in the “Other users” store:
- open the downloaded certificate;
- click the “Install certificate” button;
- click "Next";
- in the “Place all certificates in the following store” window, select “Other users”;
- Click "Ok" and "Done".
- Install the GUC_FSS_RF_2016 certificate in a similar way in the “Trusted Root Certification Authorities” store;
- Set up 1C-Sprinter for reporting to the Social Insurance Fund.
How to install a certificate of the insured organization
Contact an accredited certification center to obtain an organization certificate. If you plan, in addition to downloading the electronic tax record and sending the electronic tax registration registers , to also send 4-FSS and the Register of information necessary for the assignment and payment of benefits , then the certification center must be in the list of trusted centers of the 1C company.
Then install the cryptoprovider CryptoPro CSP or VipNet CSP. Let's look at installing an electronic signature using CryptoPro as an example.
Run the program and on the Tools click View certificates in container :
Select the container using the Browse or By certificate , set the Entered name specifies the key container radio button to User and click Next :
Click Install :
The certificate will be installed in the Personal :
An error occurred while trying to load data from the database.
An error occurred while trying to load data from the database.
Report the following information: org.hibernate.exception.SQLGrammarException: could not extract ResultSet.
Cause:
The automated workplace health care facility application cannot obtain data from the PostgreSQL database. This error occurs most often after installing an update, when the application is updated, but the PostgreSQL database is not updated for some reason.
What to do:
- If the application is installed on the user's computer and the PostgreSQL database is installed on the server. It is necessary to run the update application not only on the client, but also on the server machine;
- If both the application and the PostgreSQL database are installed on the same machine. Check the application installation directory. By default, the automated workplace medical facility application is placed in the C:FssTools directory, and the PostgreSQL database in the C:postgresql directory. If during the initial installation you selected a different directory to install the application, then when updating you must specify this exact directory.
Error calling data transfer/reception service.
Error encrypting message for recipient. Client received SOAP Fault from server: Fault occurred while processing. Please see the log to find more detail regarding the exact cause of the failure.NULL
Cause:
You specified an incorrect certificate for message encryption in the MO Certificate Name field: the specified certificate can only be used for signing, not encryption.
What to do:
Order and install a certificate that supports not only the signing operation, but also the encryption operation.
Registration of electronic sick leave
To issue an electronic sick leave certificate, the doctor will ask the employee to give written consent. The form for such consent was prepared by the Russian Ministry of Labor. The draft resolution is available on the website regulation.gov.ru .
After the end of treatment, the doctor will mark the closing of the sick leave in the program and inform the employee of his number. The employee will give this number to the HR specialist. After this, the payroll specialist or accountant will calculate the benefits and fill out his part of the sick leave.