---
title: "Reference \"Task Queue Handlers\" in 1C:Accounting for Kazakhstan 3.0 — service reference for task queue management"
country: KZ
lang: en
author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti)
date: 2026-09-07
canonical: https://buhgpt.kz/suraqtar/spravochnik-obrabotchikiocheredizadaniy-v-1s-buhgalteriya-en
source: BuhGPT
---

# Reference "Task Queue Handlers" in 1C:Accounting for Kazakhstan 3.0 — service reference for task queue management

> **TL;DR:** Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0). You have stopped receiving updates for some background operation. For example, newsletters are not coming to your email, currency rates are not loading, or the exchange task is "hanging." You write to the s

---

Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).

You have stopped receiving updates for some background operation. For example, newsletters are not coming to your email, currency rates are not loading, or the exchange task is "hanging." You write to the service support, and they respond: "Check if the handler is registered in the task queue." You open the list and see an unclear directory with methods like CommonPurpose.ExecuteTask. Nothing resembling familiar documents. Below is what this object is, why it exists, and what can (and cannot) be done with it.

First and foremost: this is a technical directory, not an accounting document. It is not about VAT, not about accounts, and not about entries. It is about which configuration procedures are allowed to be run in the background task queue when the database operates in service model (SaaS, "1C:Fresh" / rental). If you are keeping records in a regular local database, you will most likely not encounter this object at all.

1. Purpose

The directory stores a list of registered task queue handlers — configuration methods (usually procedures of common modules) that the "Task Queue" mechanism of the BSP is allowed to call on a schedule or once in a specific data area. Essentially, this is a "whitelist" of entry points: the queue does not run arbitrary code — only what is described by the element of this directory.

2. Where to find

This is a service object, so it is not present in the standard sections of the interface ("Sales," "Purchases," "Bank and Cash"). It can be opened in two ways.

- Through "All Functions": "Main Menu" (≡ icon in the upper left corner) → All Functions → Directories → TaskQueueHandlers. If the "All Functions" item is not visible — "Main Menu" → Service → Settings → check the box Show "All Functions" command.

- Through the navigation link (the fastest way): "Main Menu" → Service → Show Navigation Link / Go to Navigation Link and paste:

e1cib/list/Directory.TaskQueueHandlers

You will only be able to open the item form if you have administrator rights. Usually, this list is not accessible to a regular accountant — and that is normal.

2a. How to know your release

"Main Menu" (≡) → Help → About the Program. In the opened window, you will see:

- platform version (for example, 8.3.24.xxxx);

- configuration release — "Accounting for Kazakhstan, version 3.0 (3.0.74.2)".

It is the configuration release that determines which handlers are registered and what their set looks like. Always compare the instructions with your release.

3. How to fill

The key point: you do not fill this directory manually. The list of handlers is formed automatically during the configuration update and during the initial setup of operation in the service model. The developer describes the set of handlers in the code, and the BSP mechanism creates/updates the directory elements. Manually adding an element without the corresponding method in the configuration will lead to nothing — the task will not start anyway.

Therefore, the section below is not "how to create," but what the fields mean, so you understand what you are looking at during diagnostics.

Field
What it means and what will happen with an incorrect value

Code (mandatory, filled automatically)
Internal identifier of the element. Do not touch; it serves for referential integrity.

Name (mandatory)
Human-readable name of the handler. You find the necessary line by it when troubleshooting.

Identifier / method name
Full name of the called configuration procedure (for example, CommonModule.ProcedureName). This is the entry point. If the name does not match an actually existing method — the task will end with an error "method not found".

Usage / relevance flag
Indicates whether the handler is active. If the flag is off = the queue does not start it, even if there is a schedule.

The exact composition of the form attributes depends on the version of the BSP within a specific release and may differ in the set of service fields — this is the only place in the instructions that should be checked specifically on your release through "All Functions".

The practical conclusion: if something is not working, your task is not to "fill in the field," but to check that the required handler is present and active, and then pass this information to the service administrator or support.

4. Analyzed example

A typical accounting example with amounts and entries is impossible here — the object does not participate in money and taxes. Therefore, let’s analyze a real diagnostic scenario, for which the accountant ends up here.

Situation. The service is set up for automatic loading of currency rates from the National Bank of the RK. In the morning you notice: the exchange rate of the tenge to the dollar for yesterday did not load, documents in foreign currency were recalculated at the old rate.

Steps for analysis:

- Open e1cib/list/Directory.TaskQueueHandlers.

- Find the line responsible for loading rates (by name/method name related to updating currency rates).

- Check: the element exists, the usage flag is on.

- Look at the task queue log (regulatory and background tasks / queue tool in service model): whether the task was started, with what error it finished.

What you will see instead of entries: not Dr/Cr, but a log line with the task status — "Completed," "Error," "Pending." It is this status, not the accounting amount, that is the "result" of the object's work.

Conclusion of the example. If the handler is in place and active, but the task fails with an error — the problem is not in the directory, but in the procedure itself or in the external service (the resource of the National Bank of the RK is unavailable). If the handler is missing or turned off — the queue physically cannot start the loading, and this is fixed by updating the configuration to the current release or actions of the service administrator. No amounts in tenge, VAT 16%, or accounts (1210, 3310, etc.) are involved in this process.

5. Types of operations

The directory does not have "types of operations" in the accounting sense — it is not a document. Functionally, its elements are divided by the role of the handler:

- system handlers of the BSP — serve data exchange, deferred tasks, background updates of the IB;

- application handlers of the configuration — regulatory operations of "Accounting for Kazakhstan" itself (mailings, loading directories/rates, service recalculations), performed in the service model.

There is no need to select a type of operation when creating, and there is nowhere to do it.

6. What is formed when using

The honest answer for each item of the standard checklist:

What is usually checked
For this directory

Accounting entries (Dr/Cr)
Are not formed. The directory does not create movements in accounting registers.

Movements in registers
The directory element itself does not make movements. The work is reflected by the task queue mechanism (task log), not by entries.

ESF (ESF IS)
Are not formed. Electronic invoices are issued from sales/purchase documents, not from here.

SN
Are not formed. Accompanying invoices for goods are not related to this object.

Tax registers (VAT, PIT, WHT, etc.)
Are not affected. The object is outside tax accounting.

The only observable "result" is the fact and status of the launch of the corresponding background task.

7. Printed forms

There are no printed forms. This is a service directory; there is nothing to print from it — neither an act, nor an invoice, nor a certificate. For reporting on background operations, use the log of regulatory and background tasks, not this object.

8. Frequent errors

"Task queue handler not found" / "Handler with identifier ... not found."
Reason: the task specifies a method for which there is no element in the directory (a common case — the database is not updated to the release where the handler appeared). How to fix: update the configuration to the current release (in service model — wait for the scheduled service update or contact the administrator), after which the directory will be updated automatically.

"Task completed with error" with an active handler.
Reason: a failure within the procedure itself or unavailability of an external resource (the website of the National Bank of the RK, mail server, exchange server). How to fix: check the error text in the task log; the directory is not to blame — fix the source.

"Insufficient rights" when trying to open the list.
Reason: the user does not have administrative rights. How to fix: this is protection, not a malfunction. Diagnostics of the task queue is conducted by the service administrator.

"Task duplication" / task is not launched in the correct data area.
Reason: a feature of the queue's operation by data areas in the service model. How to fix: resolved on the service administrator's side; manually editing the directory does not fix it.

9. FAQ

What does the "TaskQueueHandlers" directory do?
It stores a "whitelist" of configuration methods that the "Task Queue" mechanism is allowed to run in the background in the service model. This is a technical registry, not an accounting document.

Does it have entries and how does it affect the balance?
It does not affect at all. There are no entries, no movements in accounting registers, it does not impact the balance, VAT, or taxes.

Why are there no VAT rates of 16%, MRP, or accounts in the instructions?
Because the object is outside accounting and tax records. VAT rate of 16%, MRP 4,325 ₸, accounts 1210/3310 and similar figures relate to accounting documents, and it is incorrect to apply them here.

Can an element be added or deleted manually?
Technically, the administrator can open the form, but there is no practical sense: without the corresponding method in the configuration, the added element will not work, and deleting the necessary handler will break the background operation. The list is maintained by the platform/BSP automatically during updates.

I am a regular accountant and do not see this directory — is this an error?
No. Access to it is only available to the administrator. You do not need it in everyday accounting.

Is an ESF or SN issued from this directory?
No. ESF is issued through the ESF IS from sales/purchase documents, SN is a separate mechanism. They are not related to the task queue.

My automatic loading of currency rates is not working — is this directory to blame?
Not necessarily. First, check that the required handler is present and active, and then check the task status in the queue log. More often, the reason is the unavailability of an external resource or an outdated release, not the directory itself.

How to properly diagnose a problem with a background task?

- Ensure that the handler is present in the directory and is enabled; 2) check the log of regulatory/background tasks and the error text; 3) if the handler is missing — update the configuration to the current release; 4) if there is an error within the task — fix the source or contact service support.

Do I need to clean or archive it to "lighten" the database?
No. It is small and service-related. Cleaning will not speed anything up and may break background operations.

10. Related objects

- The "Task Queue" mechanism (BSP) — uses elements of this directory as allowed entry points; it maintains a task log by data areas.

- Task queue templates — specify which handler and according to which schedule to run; they refer to elements of this directory.

- Regulatory and background tasks — a platform mechanism, with which the queue operates in the service model.

- Data exchange subsystems and service mechanisms (loading rates, mailings, background updates) — application consumers of the task queue.

None of these objects is created "based on" the handler directory and does not generate it manually — the connection is made through configuration and service settings.

How to know your release

"Main Menu" (≡) → Help → About the Program: there you will find the version of the platform "1C:Enterprise 8.3" and the configuration release "Accounting for Kazakhstan, version 3.0". Always compare the instructions with your release — the set of service handlers depends on the version.

The material was prepared for "Accounting for Kazakhstan," version 3.0, release 3.0.74.2. Since the object is service-related...

---
_BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_