--- title: "ESF stuck in the sending queue — how to fix" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-23 canonical: https://buhgpt.kz/suraqtar/esf-zavisli-v-ocheredi-na-otpravku-kak-reshit-en source: BuhGPT --- # ESF stuck in the sending queue — how to fix > **TL;DR:** If electronic invoices are not sent to the server and remain "in the queue," the problem is resolved through the list of documents awaiting sending — it needs to be cleared and the ESF resent. In most cases this eliminates the "freeze" without reinstalling the program and with --- If electronic invoices are not sent to the server and remain "in the queue," the problem is resolved through the list of documents awaiting sending — it needs to be cleared and the ESF resent. In most cases this eliminates the "freeze" without reinstalling the program and without reissuing the documents. Why ESF get stuck in the queue Sending ESF from 1C:Accounting for Kazakhstan to the electronic invoices information system (IS ESF) is performed in the background through the outgoing documents queue. If the exchange is interrupted for some reason, documents remain in this queue with a pending status and new ESF are "attached" to them, but in fact they do not go to the server. The most common causes are: - a brief connection interruption or unavailability of the IS ESF server at the moment of sending; - an expired or unselected electronic digital signature (EDS) certificate; - a failure of the background exchange task in 1C; - one "problematic" document in the queue that blocks the sending of the rest. What to do At the top of the program window there is a hyperlink that opens the entire list of documents queued for sending. The procedure is as follows: - Follow this hyperlink — a list of ESF stuck in the queue will open. - Delete all documents from this list. - Resend the ESF. After this the documents should go to the server without delays. Please note: deleting documents from the sending queue does not delete the invoices themselves from the database — you only clear the list of exchange tasks, while the ESF themselves remain in the journal and are placed in the queue again at the next sending. Step-by-step procedure for resending - Make sure there is a stable internet connection and the IS ESF server is available. - Check that a valid EDS certificate whose validity period has not expired is selected in the exchange settings. - Open the hyperlink with the sending queue at the top of the program window. - Clear the list of stuck documents. - Open the ESF journal and resend the required invoices. - Wait for the documents' status to change to successful sending (delivered/processed on the IS ESF side). If the problem recurs after clearing the queue When the ESF get "stuck" again after resending, proceed step by step to localize the cause: - Check a single document. Try sending one ESF separately. If it goes through but the bulk sending does not, then the queue is being blocked by a specific problematic document. - Check the EDS certificate. Make sure the signature is valid, is linked to the correct person, and is properly installed in the system. An expired or incorrectly selected EDS is one of the most common causes of failure. - Restart the background exchange task. Sometimes it is enough to restart 1C for the background sending process to start working again. - Check the status on the IS ESF side. If the document actually went through but the status in 1C did not update, you can verify it in the IS ESF cabinet itself so as not to issue a duplicate. - Check the document details. Errors in the counterparty, IIN/BIN, HS codes, or other mandatory fields can lead to rejection and "freezing" of the sending. How to avoid repeated freezes - Send ESF regularly, without accumulating large batches — this makes it easier to track a failure by a specific document. - Monitor the validity period of the EDS certificate and renew it in advance. - Control the statuses of sent ESF in the journal: a successfully accepted document should have the corresponding processing status. - Remember the established deadlines for issuing ESF under the Tax Code of the RK — a "stuck" queue does not exempt you from the obligation to issue the invoice on time, so it is better to fix the failure immediately. Typical mistakes - They reissue the ESF instead of clearing the queue and sending the existing document — as a result, duplicates appear. - They delete invoices from the journal, confusing this with clearing the sending queue. - They do not check the EDS certificate and repeatedly try to send documents with an expired signature. - They ignore the document status in IS ESF and consider the ESF sent, although it has been rejected. - They postpone solving the problem, violating the deadlines for issuing ESF. What to check - Whether there is access to the IS ESF server and a stable internet connection. - Whether the selected EDS certificate is valid and whether its validity period has expired. - Whether the sending queue has been cleared via the hyperlink at the top of the program window. - Whether the queue is being blocked by one specific document with an error in its details. - Whether the ESF statuses have updated after resending and whether they match the data in the IS ESF cabinet. - Whether the deadlines for issuing ESF established by the Tax Code of the RK have been observed. If the situation recurs after resending, it is worth contacting BuhGPT support — at buhgpt.kz you can quickly get an answer to any question related to 1C, accounting, and taxes. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_