1. Identification
| Parameter | Value |
|---|---|
| Object Type | Catalog |
| Name | TaskQueueTemplates |
| Full Name | Catalogs.TaskQueueTemplates |
| Alias | — (no separate alias specified; used in the interface as “Task Queue Templates”) |
| Configuration | Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) |
| Object Class | Service (technological) catalog |
| Navigation Link | e1cib/list/Catalog.TaskQueueTemplates |
Purpose. The catalog stores settings for scheduled (background) tasks performed through the task queue mechanism — a subsystem for automating periodic operations in the service model. Each element is a “template” for a single task: which method to call, on what schedule, how many times to repeat in case of failure, and with what interval between attempts.
The object is service and intended for administrators and developers. It has no direct relation to accounting/taxation: the catalog itself does not generate accounting entries and does not participate in tax calculations. It merely manages the launch of background processes, which in turn may initiate accounting operations (exchange of electronic invoices (ESF)/tax invoices (SNT) with the ESF information system, loading exchange rates, scheduled closures, etc.).
It is rarely used — during the initial setup of the system or when adding new automated processes.
Where to find in 1C: section “Service Technology” → “Task Queue Templates” (or via the navigation link above).
2. Attributes and Table Parts
2.1 Header Attributes
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| Usage | Boolean (xs:boolean) |
Not checked | Indicator of the template's activity. Allows temporarily disabling the task without deleting its settings. When the flag is off, the task is not queued |
| Name | String (xs:string) |
Not checked | Human-readable name of the template for display in the list and identification by the administrator |
| Key | String (xs:string) |
Not checked | Unique string identifier of the template for programmatic search and addressing the task in code |
| MethodName | String (xs:string) |
Not checked | Full programmatic name of the procedure/function (usually CommonModule.Method) called when executing the task |
| Schedule | Value Storage (v8:ValueStorage) |
Not checked | Serialized object ScheduledRegulatoryTask — when and how often to perform the task |
| NumberOfRetriesOnFailure | Number (xs:decimal) |
Not checked | How many times to repeat the task in case of failure/error |
| RetryIntervalOnFailure | Number (xs:decimal) |
Not checked | Interval between retry attempts, in seconds |
The attribute Name (standard for the catalog) is filled in manually/programmatically; the semantic identifier for launching is Key, not the code.
2.2 Table Parts
Table parts are absent. The catalog contains only header attributes — one “template” per element.
3. Forms
No specialized (custom) forms for this object are defined in the delivery — automatically generated forms by the platform are used:
| Form | Purpose |
|---|---|
| List Form (auto-generated) | View the list of task templates, enable/disable via the Usage attribute |
| Element Form (auto-generated) | Edit parameters of a specific template: method name, key, schedule, retry parameters |
| Selection Form (auto-generated) | Select a template from other objects/settings processes |
Since the object is service, elements are most often created and filled programmatically (during deployment/update of the configuration), rather than through the interface.
4. Key Procedures of Modules
Evidence with module texts (BSL) for this object is not attached. Below are typical handlers for a catalog of this kind. Specific lines/paths should be checked in the object module and manager in the configurator (Catalog.TaskQueueTemplates).
- Object Module —
BeforeWriting: control of the correctness of filling (presence of non-emptyKeyandMethodName), checking the uniqueness of the key. - Object Module —
FillingHandler: filling default values (for example,NumberOfRetriesOnFailure,RetryIntervalOnFailure) when creating a new element. - Manager Module — methods for obtaining/initializing templates: functions like “get template by key”, “create/update predefined set of templates”. These are usually called by the task queue subsystem when queuing a task for execution.
- Service common module of the task queue subsystem (not the module of the catalog itself): reads active templates (
Usage = True), determines the moment of launch bySchedule, callsMethodName, and in case of error initiates a retry according toNumberOfRetriesOnFailureandRetryIntervalOnFailure.
Exact method names and line numbers are version-specific; requires verification in the specific build 3.0.74.2.
5. Posting and Movements
The catalog is not posted and does not independently generate movements in registers and does not create accounting entries — it is a service object for storing settings, not a document.
Accounting consequences arise not from the catalog itself, but from the methods it launches. For example, a background task for exchanging electronic documents (ESF information system: ESF, SNT) processes documents of sales/purchases, which already in their logic generate entries according to the standard chart of accounts of the RK. For reference — typical correspondence of such documents (numbers/rates of Kazakhstan, 2026):
| Operation | Debit | Credit |
|---|---|---|
| Sale of goods to the customer (income) | 1210 “Short-term receivables from customers” | 6010 “Income from sales” |
| VAT accrued on sales (rate 16 %) | 1210 | 3130 “VAT payable” |
| Cost of goods sold written off | 7010 “Cost of goods sold” | 1330 “Goods” |
| Receipt of goods from the supplier | 1330 | 3310 “Payables to suppliers” |
| Payment to the supplier from the current account | 3310 | 1030 “Cash in current accounts” |
These movements are the responsibility of the corresponding documents, while TaskQueueTemplates merely initiate their background processing according to the schedule.
Reference values of the RK for 2026 (used by methods, but not by the catalog itself): MRP = 4,325 ₸, MZP = 85,000 ₸; basic deduction for individual income tax = 30 MRP/month (not more than 360 MRP/year); individual income tax 10 % up to 8,500 MRP annual income and 15 % above; OPE 10 % (base ceiling 50 MZP), OPEA 3.5 %, VOSMS 2 %, OSMS 3 %, SO 5 %, social tax 6 %; VAT rate 16 %.
6. Related Objects and Input on the Basis
- Input on the basis for the service catalog is not provided (it is not a basis document).
- Task queue subsystem — the main consumer: reads elements and queues tasks for execution according to
Schedule. - Type
ScheduledRegulatoryTask— stored in the attribute Schedule viaValueStorage. - Common modules of launched methods — addressed through the attribute MethodName (exchange with ESF/SNT information system, loading exchange rates, scheduled period closing operations, etc.).
- Scheduled and background tasks of the platform — the mechanism through which the queue is actually executed on the server.
7. Extension Points
- Adding a new automated process: create a catalog element with a unique
Key, setMethodNameto your exported method of the common module, and configureSchedule. - Managing activity: mass enable/disable tasks via the Usage attribute without deleting settings.
- Fault tolerance policy: configuring
NumberOfRetriesOnFailureandRetryIntervalOnFailurefor a specific method (for example, increase the interval for exchanging with the external ESF service when unavailable). - Configuration extension (without removing from support): adding parameter attributes, subscriptions to events
BeforeWriting/OnWritingfor auditing changes to queue settings, custom forms for element/list. - Programmatic support: initialization/updating of a predefined set of templates during updates via methods of the manager module.