Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).
The real situation that brought you here
You sent a batch of electronic invoices (ESF) to the ESF information system, and the status still says "Ready to send." Or the 1C support service asks over the phone: "Open the TaskQueue directory and see if there are any stuck entries." Or you accidentally found this directory through the "All functions" menu and do not understand what it is and whether you can delete anything there. This is a typical situation: you opened not an accounting document, but the internal "kitchen" of the program — the queue of background tasks that 1C performs on its own, without your involvement.
Calm down. You do not need to fill anything in manually during regular work. Let's figure out what this is and when it is actually worth looking here.
1) Purpose
The "TaskQueue" is a service directory. It stores records of background (deferred) tasks that the program queues and executes asynchronously: exchange of electronic documents (ESF, SNT) with government systems, data exchange between databases, deferred processing, long operations. Each element of the directory is a single queued task with its status. The accountant needs it only for diagnostics when a background operation "is not going through".
2) Where to find
This object is intentionally hidden — it is not present in the regular interface sections ("Sales", "Purchases", "Bank and Cash") because you do not need to work with it manually.
You can open it in two ways:
- Through "All functions": "Main Menu" (☰ icon in the upper left corner) → All functions → Directories → TaskQueue. If the "All functions" item is not present, enable it: "Main Menu" → Service → Parameters → check "Show the 'All functions' command".
- Through the navigation link (the fastest way): "Main Menu" → Service → Show navigation link / or paste and go in the address bar of 1C:
e1cib/list/Directory.TaskQueue
Copy this line, in 1C press "Go to navigation link" (Ctrl+F11 or through the menu) and paste it — the directory list will open directly.
2a) How to find out your release
"Main Menu" (☰) → Help → About the program. In the opened window, you will see two lines that support always asks for:
- Platform — version of "1C:Enterprise" (for example, 8.3.24.xxxx);
- Configuration — "Accounting for Kazakhstan, version 3.0" and release number (in this manual — 3.0.74.2).
If your release differs, the composition of the service fields of this directory may change slightly — this is the only place in the instructions that requires verification on your version.
3) How to fill
The key point: in regular work, you do not fill this directory. The records are created by the program itself when it queues a task in the background. Manual creation/editing of elements is allowed only at the direct instruction of a support specialist. Nevertheless, knowing the fields is useful — you read what is happening by them.
The typical composition of an element (task card):
| Field | Purpose and what will happen with an incorrect value |
|---|---|
| Name | A human-readable name of the task (what it does). If empty — you simply won't understand what the entry is; it does not affect work. |
| Status / Condition | The main field. Shows the stage: "In queue", "In progress", "Completed", "Error". This is where you look during diagnostics. It cannot be changed manually — you will distort the picture and not understand the real cause of the failure. |
| Date of queuing | When the task entered the queue. It shows "stuck" old entries. |
| Priority | Order of execution. Manual changes may disrupt the exchange queue. |
| Task / Procedure | What exactly is being launched (method, handler). Service, do not touch. |
| Parameters | Data with which the task is launched (links to documents, identifiers). Changing it is a direct path to an exchange failure. |
| Result / Error description | Text of the response or error. You copy the message for support from here. |
| User / Responsible | Who initiated it. Useful when the database is multi-user. |
There are no mandatory fields for manual input for the accountant here — because you do not create records manually.
4) An analyzed example
Since there are no entries in the directory, I will show a real diagnostic scenario — this is exactly why people come here.
Situation. On September 6, 2026, you conducted a sale of goods for 1,160,000 ₸: income 1,000,000 ₸ and VAT 16% = 160,000 ₸ (the VAT rate in the RK since 2026 is 16%). An automatic task was created to issue and send the ESF to the ESF information system. An hour later, the accountant sees that the ESF has not been sent.
What you do:
- Open
e1cib/list/Directory.TaskQueue. - Find the entry with Date of queuing = 06.09.2026 and a name like "Sending ESF for sale No...".
- Check the Status field — it says "Error".
- Open the card, read the Result: for example, "The certificate of the digital signature has expired" or "No connection to the ESF information system".
- Eliminate the cause (update the certificate / check the internet) and restart the exchange using the standard command from the ESF workplace, not from this directory.
Important about accounting: the actual entry for the sale is formed by the sale document, not the queue. For reference — here is how the entries of this sale look (they are made by the document "Sale of goods and services", not the directory):
| Dr | Cr | Amount, ₸ | Description |
|---|---|---|---|
| 1210 | 6010 | 1,000,000 | Revenue from sale to the customer |
| 1210 | 3130 | 160,000 | VAT 16% payable |
| 7010 | 1330 | (cost) | Cost of goods written off |
These entries provide context so you can see the connection: the queue only delivers the ESF for this sale, but does not move money or taxes.
5) Types of operations
The directory does not have "types of operations" in the accounting sense (like documents). But tasks in the queue can be of different types — by purpose:
- sending/receiving ESF (ESF information system);
- preparing and sending SNT (accompanying invoices for goods);
- data exchange between databases (synchronization, RIB);
- deferred processing of documents;
- background updating / recalculation of data during release updates;
- scheduled background operations.
6) What is formed during processing
Nothing — and this is correct. This is a directory, not a document, it does not have the operation "Process". Accordingly:
- there are no Dr/Cr entries;
- the directory does not create movements in accounting/accumulation registers;
- it does not form ESF and SNT — it only stores a record of the task for their sending; the electronic documents themselves are created by specialized objects (ESF, SNT documents) and exchange workplaces.
The practical conclusion: if something "has not been formed", the reason is looked at here (the "Result" field), and corrections are made in the relevant document or exchange workplace.
7) Print forms
This directory has no print forms. It does not output acts, invoices, ESF, orders, etc. Everything that can be done is to output a list on the screen/to a file using the standard command "More → Output list" for transmission to support.
8) Common errors
"The task completed with an error" (text in the "Result" field). The reason is usually external: no connection to the ESF information system, the digital signature certificate has expired, incorrect account details. Correction: eliminate the cause and restart the exchange from the ESF/SNT workplace, not by recreating the directory element.
"Insufficient rights to perform operations on the data" when trying to open/change. The directory is service, access is limited by roles. Do not grant yourself rights "just in case" — contact the administrator; manual editing here is riskier than beneficial.
"Directory element not found" / broken links after update. Occurs if the task referred to a deleted object. Do not manually delete stuck entries — cleaning is performed by standard database maintenance regulations ("Administration → Maintenance").
Many records have accumulated in the queue and the database is "slowing down". This is not a reason to clean the directory manually. Set up the schedule for background exchange (less/more frequently) and enable scheduled cleaning of completed tasks through administration.
9) FAQ
Can I manually delete entries from the "TaskQueue"? Not recommended. Deleting a task in the status "In queue" or "In progress" will interrupt the exchange (for example, the ESF will not be sent, and you will think it has been sent). Cleaning should only be done using standard maintenance tools and only for completed tasks.
Why does this directory have no entries and print forms? Because it is a technical object, not an accounting document. It organizes the background work of the program. Entries are made by sale, receipt, payment documents; ESF/SNT are formed by specialized documents.
How to understand that the ESF is stuck due to the queue? Find the entry by date and content, check the "Status". "Error" — read the "Result". "In queue" for a long time — likely, the background exchange is not running or there is no schedule.
Does this queue affect VAT and taxes? Indirectly. It does not calculate taxes itself. But if the ESF did not go due to a failure, you will have a problem with VAT confirmation (the rate in the RK is 16%) and offsetting for the buyer. Therefore, errors in the queue regarding ESF should be closed immediately.
Do I need to open this directory in everyday work? No. Normally — never. It is opened only for diagnostics or at the request of support.
Where to configure so that tasks are executed automatically? In the "Administration" section — synchronization/exchange settings and schedule for scheduled tasks. This is where it is set how often the queue is processed.
What to do if support asks to "export the list of tasks"? Open the directory, "More → Output list", save to a file (for example, to a table) and send it. Do not change anything.
Is this directory different in the cloud version (fresh) and in the local version? The logic is the same, but in the cloud, user access to it is usually even more restricted, and the provider handles the queue maintenance. Diagnostics in the cloud are more often conducted through contacting service support.
Can I speed up a "stuck" task by increasing its priority? Technically, the field exists, but it is not advisable to change it manually — you will disrupt the order of exchange. It is better to eliminate the cause and restart the exchange using the standard command.
10) Related documents
The "TaskQueue" directory is not generated based on accounting documents and does not serve as a basis for them — it works "on the side". But it is related to them by data:
- Sale of goods and services, Invoice (ESF), SNT — tasks for sending to the ESF information system/electronic exchange are set for them; their status is what you diagnose here.
- Data synchronization/exchange settings — manage what goes into the queue and how often it is executed.
- Scheduled and background tasks ("Administration → Maintenance") — the mechanism that actually processes this queue.
For real entries and printing, go to the relevant documents (sale, receipt, payment), and here — only to understand "why the background operation did not complete".
How to find out your release
"Main Menu" (☰) → Help → About the program: it indicates the version of the "1C:Enterprise" platform and the release of the configuration "Accounting for Kazakhstan, version 3.0".
This manual is relevant for release 3.0.74.2 of the "Accounting for Kazakhstan" configuration (version 3.0). If you have a different release, verify the composition of the service fields through "Help → About the program".