If an ESF freezes and is neither accepted nor sent, the cause is most often in the digital signature (EDS) key or in the program's accumulated cache. This is resolved by changing the EDS key and clearing the cache. Below we will look at the procedure in more detail, as well as what to do if the basic steps did not help.
Quick solution: changing the EDS key and clearing the cache
In most cases the problem is resolved by two actions. Perform them one after another and after each one recheck the sending or receipt of the document.
- Change the EDS key — update or reload the current electronic signature certificate used to sign the ESF. Make sure you select exactly the key that is registered to the organization and intended for signing documents (and not the authentication key).
- Clear the cache — this will remove outdated data that could interfere with the correct processing of the invoice. The cache accumulates during repeated sending attempts and often "hangs" an already generated document.
After these two actions, try to receive or send the ESF again — in most cases the problem goes away at this point.
Why the ESF "freezes"
Understanding the cause helps to avoid repeating the mistake. The most common sources of failure when working with the ESF IS are:
- Problem with the EDS key — the wrong certificate is selected, the key is damaged, or an outdated signature file has been loaded.
- Accumulated cache — outdated program data interferes with correctly generating or sending the document.
- The certificate has expired — the signature is no longer accepted, the document does not go through.
- The wrong type of key — different keys are used for signing and for authentication; they are easy to confuse.
- ESF IS connection settings — a communication failure with the information system, incorrect connection parameters.
Step-by-step procedure in case of failure
If the ESF is not accepted and not sent, proceed sequentially, from simple to complex:
- Change (reload) the EDS key used to sign the invoice.
- Clear the program cache to remove outdated data.
- Retry the receipt or sending of the ESF.
- If it did not help — check the certificate's validity period and its type (for signing, not for authentication).
- Check the ESF IS connection settings.
- If the problem persists, contact the ESF system technical support or the specialist servicing your account.
If the basic steps did not help
If after changing the key and clearing the cache the situation has not changed, you need to look deeper. Possible directions of diagnostics:
- The certificate itself. It has expired — then you need to obtain a new EDS key. Or the wrong type of key is being used — an appropriate certificate must be applied for signing documents.
- ESF IS connection settings. Check the connection parameters with the information system: the correctness of the address, the availability of the service, the absence of blocking by the network or antivirus.
- The state of the information system itself. Sometimes the failure is not on the user's side but on the ESF IS side — in this case it helps to retry later or clarify the system's status.
Working with ESF in 1C:Accounting for Kazakhstan
If you generate and send invoices from an accounting program, pay attention to the link between 1C and the ESF IS:
- Check that the program specifies the current EDS certificate used to sign the document.
- Make sure that the document data is uploaded without errors — an incorrectly filled out document may not be accepted by the system.
- After reloading the key and clearing the cache, repeat the upload and sending.
Typical mistakes
- Selecting the authentication key instead of the signing key and not understanding why the document does not go through.
- Repeatedly clicking "Send", which causes the cache to accumulate even more, and the document "hangs" completely.
- Working with an expired certificate without checking its validity period.
- Looking for the cause in the document, when the problem is in the connection to the ESF IS.
- Not retrying after each step and not understanding which action exactly helped.
What to check
- The relevance and correctness of the selected EDS key (whether the right certificate is loaded).
- The type of key — for signing, not for authentication.
- The certificate's validity period.
- Whether the program cache has been cleared.
- The settings and availability of the connection to the ESF IS.
- The correctness of filling out the document itself before sending.