---
title: "Guide \"Task Queue Templates\" in 1C:Accounting for Kazakhstan 3.0 — what it is and how to work with it"
country: KZ
lang: en
author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti)
date: 2026-09-07
canonical: https://buhgpt.kz/suraqtar/spravochnik-shablonyzadaniyocheredi-v-1s-buhgalteriya-dly-en
source: BuhGPT
---

# Guide "Task Queue Templates" in 1C:Accounting for Kazakhstan 3.0 — what it is and how to work with it

> **TL;DR:** Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0). You have a background process stuck in your database. For example, the exchange with the ESF information system does not send documents on schedule, or totals are not recalculated, or the partner's technica

---

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

You have a background process stuck in your database. For example, the exchange with the ESF information system does not send documents on schedule, or totals are not recalculated, or the partner's technical support asks: "please send the list of queue tasks and their templates." You go looking for where this is located and stumble upon the directory "TaskQueueTemplates." You open it — and there are incomprehensible lines with method names, without amounts and counterparties. The question arises: is this even about accounting or can it be left alone?

First of all, so you don't search for what doesn't exist. This is a service (technical) directory of the background task mechanism. It is not an accounting document. It has no postings, no ESF and SNT, no printed forms, and no "types of operations" in the accounting sense. VAT rates, MRP, PIT, and the chart of accounts have no relation to it — it is about how and when the program launches its internal procedures, not about what it calculates. Below is what it is, where to find it, and what to do with it.

1. Purpose

The directory stores task queue templates — templates for background (regulatory) operations that are performed in order. Each element describes which procedure is launched and with what parameters. From the templates, specific queue tasks are formed, which are executed on schedule: data exchange, sending electronic documents, recalculating totals, servicing the database. The directory is filled automatically by the program during configuration updates and the setup of regulatory tasks; it is almost never edited manually.

2. Where to find

This directory is not present in the usual sections of the interface ("Sales," "Purchases," "Bank and Cash") — it is a service directory and is not displayed in the command interface. You can open it in two ways:

- Main menu → "All functions" → "Directories" → "TaskQueueTemplates." (The "All functions" item is enabled in "Service → Settings → Display the "All functions" command.")

- By navigation link. Main menu → "Service" → "Go to navigation link" (or Ctrl+click on the line below) and paste:

e1cib/list/Directory.TaskQueueTemplates

Nearby live related service objects: the directory "QueueTasks" (the tasks themselves created from templates) and the standard form "Regulatory and Background Tasks" (Administration → Maintenance → Regulatory Operations).

Tip: to see what is actually being executed and with what errors, you almost always need not this directory, but specifically "Regulatory and Background Tasks." Templates are "recipes," not a "cooking journal."

2a. How to know your release

Main menu → "Help" → "About the program". In the opened window, you will see the version of the platform (for example, 8.3.xx) and the configuration release — a line like "Accounting for Kazakhstan, version 3.0 (3.0.74.2)." It is the configuration release that you should compare with the header of this manual: the set and behavior of service directories change from release to release.

3. How to fill

In normal operation, you do not fill this directory. It is filled by the platform/configuration. But it is worth understanding the fields — at least to read the line and explain it to support.

Field
Purpose
What will happen if filled incorrectly

Name (mandatory)
A human-readable name for the template. Usually matches the name of the regulatory task it launches. You find the needed template in the list by it.
By itself, it does not affect the launch, but if duplicated/renamed manually, you will lose sight of the task and not understand what process is being executed.

Code
Internal identifier of the element. Assigned automatically.
Manual editing of the code may violate the referential integrity with queue tasks. Do not touch.

Method name / predefined task
Link to a specific configuration procedure that the template calls. This is the "engine" of the template.
If a non-existent or foreign method is specified — the task will either not start or fail with an error during execution.

Parameters / schedule (service attributes)
Determine with what arguments and how frequently tasks are created from the template.
Incorrect schedule = the process will not execute on time (for example, ESF will not be sent at night) or, conversely, will overload the database.

The practical conclusion: the only thing that is safe and meaningful to do manually here is to read the elements and, if instructed by support, selectively change the usage flag of a specific template. Leave mass editing, deletion, and creation of elements to the update mechanism and the specialist.

4. Analyzed example

There are no postings and amounts here — therefore, we will show the example based on what the directory exists for: the connection "template → task → result." Let's take the sending of electronic invoices.

Situation. ESF for September 3, 2026, are "stuck" as not sent. You check the mechanism.

- You open "TaskQueueTemplates" via the link e1cib/list/Directory.TaskQueueTemplates.

- You find an element with a name like "Sending electronic documents" (exchange with the ESF/SNT information system). This is a template — a "recipe."

- From this template, a task has been created in the "QueueTasks" directory, which should be launched, for example, every 15 minutes.

- You go to Administration → Maintenance → Regulatory and Background Tasks and see: the corresponding regulatory task is disabled or the last execution finished with a connection error.

- You enable the schedule/repeat the execution — ESF are sent to the ESF information system.

What you saw here specifically: the template specifies what to launch, the queue task — the specific instance of the launch, and the form of regulatory tasks — the fact and result of execution. No debit/credit: movements on accounts (for example, recognition of income Debit 1210 Credit 6010 and VAT 16% to account 3130) are created by the sales document itself, not the service template. The template only ensured that the already posted document was sent to the external system on time.

5. Types of operations

The directory does not have types of operations in the accounting sense (it is not a document). The division here is by the purpose of the template — that is, by what background procedure it serves. Typical groups:

- exchange of electronic documents (ESF, SNT, exchange with state systems);

- data exchanges between databases (RIB, synchronization);

- service maintenance of the information base (recalculation of totals, updating aggregates);

- deferred data update after a release change;

- other internal regulatory operations of the configuration.

The specific list of lines in your database depends on the release and included functional options.

6. What is formed "when posted"

There is nothing to post — this is a directory, not a document. Therefore:

- There are no accounting postings. This object does not create any movements on accounts 1210/1030/1330/3310/3130/6010/7010.

- It does not issue ESF and SNT. It only serves the sending mechanism of already existing electronic documents. The ESF themselves form sales/purchase documents and the integration module with the ESF information system.

- Movements are only service ones. The directory element is used as a source for creating records in "QueueTasks" and related service registers of the background task mechanism. This is the internal "kitchen" of the platform, not accounting registers.

7. Printed forms

There are no printed forms for the directory. This is a service object without forms and reports. If you need to "print" the status of background processes, use the form "Regulatory and Background Tasks" — from there you can output the list of tasks and their execution history.

8. Common errors

"Insufficient rights to perform an operation on the directory 'TaskQueueTemplates'."
The directory is service, access to it is available to users with administrative rights. Log in as an administrator or ask them to open the object.

A task from the template "does not work," although the template exists.
Messages like "Regulatory task disabled" or "Task execution error." The reason is almost always not in the template: check Administration → Maintenance → Regulatory and Background Tasks — whether the schedule is enabled, whether the session/agent is running, and whether there is an error in the text of the last execution.

Someone deleted or renamed the element manually.
"Broken links" appear in the queue tasks, and some background operations stop launching. Do not restore manually — perform update/reconfiguration of the configuration (or testing and correction of the information base) so that the mechanism recreates the standard templates.

Duplicates of templates after a non-standard update.
The same operation is launched twice, the database "lags." Keep the current element, mark the extra for deletion, and delete it through "Delete marked objects" — but only after consulting with the support specialist.

9. FAQ

Is this an accounting document? Does it affect reporting and taxes?
No. This is a service directory of the background task mechanism. It does not directly affect postings, trial balances, VAT (16% in 2026), PIT, and any tax calculations — it only ensures the timely launch of processes.

Can it be cleaned, deleting elements "for order"?
No need. Manual deletion breaks the related queue tasks. The order in it is maintained by the configuration update mechanism.

Why does it not have postings and printed forms?
Because it is not a document, but a directory-"recipe" for background operations. Postings and printed forms are present in accounting documents (sales, purchases, payment documents), not in service objects.

My ESF are not being sent — is this directory to blame?
Usually not. First, check "Regulatory and Background Tasks" (whether the sending schedule is enabled) and the settings for exchanging with the ESF information system. The template is just a launch template.

How to open the directory if it is not in the menu?
Through "All functions" → "Directories" or by the navigation link e1cib/list/Directory.TaskQueueTemplates.

How do "TaskQueueTemplates" differ from "QueueTasks"?
A template is a preparation (what and how to launch). A queue task is a specific instance of a launch created from a template. The result of execution is seen in regulatory tasks.

Can I disable an unnecessary background process through this directory?
It is more correct to manage this through the schedule of regulatory tasks (Administration → Maintenance). Edit the templates themselves only at the direction of support.

After updating the configuration, new lines appeared in the directory — is this normal?
Yes. When updating the release, the set of templates is brought into line with the new version: some elements are added, and some cease to be used. This is normal behavior.

Is it necessary to configure it when starting a new RK database?
No. With a correct installation and first launch, the configuration fills the directory itself. It does not require special manual configuration for Kazakhstan.

10. Related objects

- QueueTasks — created based on templates; these are executable instances.

- Regulatory and Background Tasks (Administration → Maintenance → Regulatory Operations) — where the actual launch, schedule, and errors are visible.

- Settings for exchanging with the ESF / SNT information system and the documents that send these exchanges (sales, purchases) — they generate ESF and create accounting postings (for example, Debit 1210 Credit 6010 and VAT at a rate of 16% to account 3130).

- Updating/testing the information base — a mechanism that recreates and organizes standard templates.

How to know your release

Main menu → "Help" → "About the program". There you will find the version of the 1C:Enterprise platform and the configuration release. Compare the configuration release with the line at the beginning of this manual.

This manual is prepared for release 3.0.74.2 of the "Accounting for Kazakhstan" configuration (version 3.0). When transitioning to another release, the list and behavior of service task templates may differ — check "Help" → "About the program."

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