If an ESF is "stuck" and does not get sent to the IS ESF website, most often the document is stuck in the sending queue. The basic solution is to clear this queue and send the ESF again. In most cases, the document then goes through without problems, because the old "stuck" task that was interfering with normal sending no longer blocks the process.
Why an ESF is not being sent
The reason for the freeze is not always an error in the invoice itself. Exchange with the IS ESF goes through background jobs of 1C:Accounting for Kazakhstan, and if one of the jobs for some reason did not complete (loss of connection, timeout, disconnection from the portal), it remains in the queue and blocks subsequent submissions. Other typical factors:
- Temporary unavailability or maintenance work on the IS ESF website side.
- Problems with the internet connection at the moment of sending.
- An improperly completed previous exchange operation that left a "hung" job.
- A failure of the digital signature certificate or of the connection to the portal.
As long as the "stuck" task remains in the list, new documents may fail to send or accumulate in the "awaiting sending" state.
Procedure
- Find the stuck ESF document that is not being sent. Note its status in the ESF journal — it remains unsent or "in queue".
- Clear the sending queue — remove the document from the list of "stuck" or unsent exchange jobs. This lifts the block created by the incomplete operation.
- After clearing, repeat sending the ESF to the website again, as a regular operation.
After this, the document usually goes through normally. If there are several invoices and they are all "stuck" behind one job, after clearing the queue it makes sense to send them one by one to make sure each goes through correctly and to immediately notice if the problem concerns a specific document.
If resending did not help
When the situation recurs even after clearing the queue and resending, the problem is most likely deeper than a one-time freeze. Check in order:
- Exchange settings with IS ESF in 1C — the correctness of the specified parameters for connecting to the portal.
- Correctness of the connection — the availability of the IS ESF website and the stability of the internet connection.
- Digital signature certificate — whether its validity period has expired, whether the correct key is selected, whether it is correctly installed in the system.
- Portal availability — sometimes the IS ESF website is unavailable due to maintenance work on the SRC side; in this case sending must be repeated later.
It is also worth making sure that the ESF document itself is filled out without errors: if the portal rejects the invoice by content (counterparty details, product codes, amounts), then this is no longer a queue freeze but a rejection of acceptance — and here you need to look at the error text that the IS ESF returns.
How to distinguish a "freeze" from a document error
It is important to correctly understand the nature of the problem so as not to waste time in vain:
- Freeze in the queue — the document does not go through at all, the status remains "awaiting sending", there is no content error message. Cured by clearing the queue and resending.
- Portal rejection — IS ESF returns a specific message (for example, about incorrect details or data mismatch). Here clearing the queue will not help — you need to correct the document itself and send it again.
- Service unavailability — the exchange does not go through due to problems on the portal or connection side. The solution is to repeat sending later.
Prevention of freezes
To make ESFs get stuck in the queue less often:
- Do not close the program and do not break the connection at the moment of sending the document to the portal.
- Wait for the current exchange operation to complete before starting the next one.
- Keep track of the currency of the 1C:Accounting for Kazakhstan release — exchange with IS ESF is regularly improved.
- Monitor the validity period of the digital signature in advance so that sending does not fail at the most inopportune moment.
- Periodically check the ESF journal for unsent documents so as not to miss "stuck" invoices.
Typical mistakes
- Repeatedly clicking "Send" on a stuck document — this only increases the queue but does not lift the block.
- Ignoring unsent ESFs in the journal until the end of the reporting period, when there is no longer time to correct them.
- Trying to "cure" by clearing the queue a document that is actually rejected by the portal by content.
- Sending when the IS ESF website is unavailable without checking the connection — the document will hang again.
What to check
- The document status in the ESF journal: "in queue"/"not sent" or there is an error text.
- Whether the queue of unsent exchange jobs has been cleared before resending.
- Exchange settings with IS ESF and the correctness of the connection to the portal.
- The validity and correctness of the digital signature certificate selection.
- The availability of the IS ESF website (whether there is maintenance work) and the stability of the internet.
- The correctness of filling out the document itself, if the portal returns a rejection rather than simply "staying silent".