Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).
The application approval task has "stalled." You assigned it to a specific manager, and they went on vacation — and the application has been sitting for three days because there's no one else to pick it up. Or the opposite: the same task is seen by five people, each thinks a colleague will take it, and in the end no one does. Both problems are solved by the same place in the program — the reference book "Task Executor Groups". Here you describe exactly who tasks fall into "a common pool" for: not to Ivanov personally, but to the "Procurement Approval Group," from which the task will be picked up by any available employee.
1. Purpose
The reference book stores groups of users for task addressing in business processes (approval of applications, invoices, orders, assignments). A task can be sent not to a specific person, but to a group — then it is seen and can be completed by all group members. This relieves addressing: there's no need to remember who's currently available, and no need to manually reassign tasks during vacations and dismissals.
2. Where to find it
The reference book is not obvious — there is usually no direct command on the sections panel for it; it opens from settings.
- Master Data and Administration → User and Rights Settings → Task Executor Groups (in some interfaces — the Administration section).
- The group composition can also be opened from the user's card: Master Data and Administration → Users → select a user → the groups/tasks section.
- The fastest way is a navigation link. Menu Service → Go to navigation link (or the icon in the upper right corner), paste:
e1cib/list/Справочник.ГруппыИсполнителейЗадач
The full list of groups will open regardless of whether the command is shown in the menu or not.
2a. How to find your release
Help (the "?" icon) → About the program. In the window that opens, you will see two lines: the platform version (e.g., 8.3.24.xxxx) and the configuration — "Trade Management for Kazakhstan," edition 3.4, release (e.g., 3.4.5.21). Focus on the configuration release: it is to this that the field composition and behavior described below are tied. On other releases, minor interface details may differ.
3. How to fill it in
The reference book is hierarchical: groups can be nested within groups (folders). The card is simple, with few fields, but each one affects whether the task reaches people or not.
| Field | Required | Why it's needed and what happens on error |
|---|---|---|
| Name | Yes | The group's name, seen when assigning a task and in the list. Name it by the role's meaning: "Expense Application Approval," "Warehouse Keepers," "Accounting — Invoices." If named abstractly ("Group 1"), when selecting an executor a person won't understand who they're addressing the task to, and will send it to the wrong place. |
| Parent (Group) | No | The owner folder in the hierarchy. Needed only for organization when there are many groups. Does not affect addressing: a nested group does not automatically inherit the parent's composition. |
| Composition (members / users) | Effectively yes | The list of users who belong to the group. It is exactly these people the task will become visible to. If the composition is empty — a task addressed to the group will hang: there is physically no one to take it. Add only those who really should perform this type of task. |
| Comment / Description | No | A free-form note: what the group is for, who is the lead, from what date the composition was changed. Helps avoid guessing six months later. |
| Deletion mark | — | Do not delete a group directly if tasks have ever been assigned to it — mark it for deletion instead. Directly deleting an active group will break links in unclosed tasks. |
Procedure
- Click Create (for a folder — Create group).
- Enter the Name by role, not by surname.
- If necessary, specify the Parent (folder).
- Go to Composition and use the Add button to enter users. One person can belong to several groups — this is normal.
- Save and close. Changes to composition take effect immediately: remove a user — they will no longer see new tasks for this group (tasks already assigned to them personally will remain).
Practice: create groups by role, not by person. A "vacationer" is simply removed from the group temporarily — tasks continue going to the rest, no need to redo business processes.
4. Worked example
Given: expense applications at the company are approved by two people — Akhmetova A. and Nurlanov B. Previously, all tasks were assigned personally to Akhmetova. She is on vacation — approval has stalled.
What you do:
- Open
e1cib/list/Справочник.ГруппыИсполнителейЗадач, click Create. - Name:
Expense Application Approval. - In Composition, add two users: Akhmetova A., Nurlanov B. Save.
- In the expense application approval route settings (Treasury/approval business process), specify as the executor not Akhmetova, but the group "Expense Application Approval."
Result. A new application for 250,000 ₸ goes for approval. The task appears in the "My Tasks" list for both Akhmetova and Nurlanov. While Akhmetova is on vacation, Nurlanov opens the task, clicks Accept for Execution (the task is assigned to him, disappearing from Akhmetova's active tasks) and approves it. The process continues without manual reassignment.
Important to understand about this example. The "Task Executor Groups" reference book is an organizational setting, not an accounting document. It does not generate accounting entries (no Dt/Ct), does not create ESF or SNT, and does not move VAT, mutual settlements, or cost registers. It only determines who sees the task. Therefore, there are no and can be no "entries with figures" for this object — the application amount (250,000 ₸) is here only the content of the document being approved, not something generated by the group. Entries and ESF will appear later, when the approved application turns into a payment and sale — but that is the work of other documents, not this reference book.
5. Types of operation
The reference book does not have separate "operation types" like documents do. By purpose, groups are as follows:
- Functional / role-based — "Warehouse Keepers," "Accounting," "Sales Managers." The most common variant.
- Approving — participants in application, invoice, and contract approval routes.
- Territorial / by department — "Almaty Warehouse," "Astana Office."
- Technical (folders) — parent groups that don't themselves contain executors, but only group other groups for list organization.
6. What is generated when saving
- No accounting entries. This is a reference book; it does not create movements on accounting accounts.
- No electronic documents. This object does not issue ESF (ESF IS) or SNT.
- What actually changes: the group composition is updated, which is read by the task addressing mechanism. After saving, new tasks for the group become visible to the current composition; excluded users drop out of active addressing. References to the reference book element are inserted into the "Executor"/"Responsible" attributes of business processes and tasks.
7. Printed forms
The reference book has no printed forms of its own — there is no need or provision for printing an "executor group." You can view who belongs where as follows:
- More → Change form / Print list — export the list of groups to a spreadsheet document or Excel for review and approval.
- Reports on tasks and assignment execution (the tasks section) show which groups and which people tasks are assigned to.
8. Common mistakes
"Task executor not specified" / task was not assigned. The reason — the approval route specifies a group with an empty composition. Open the group, add at least one user, save. Reassign an already failed task manually.
No one sees the task, even though the group is filled. Check that the users in the composition have active accounts (not marked "Invalid," have access to the program). A dismissed/disabled user will not see the task, even while remaining in the composition.
"Item is in use…" when attempting to delete. The group is involved in unclosed tasks or in the route setting. Do not delete — mark for deletion, and replace it with another group in the process settings. Physical deletion is only possible after referential integrity control finds no references.
Duplication of groups with nearly identical names ("Warehouse Keepers" and "Warehouse"). Tasks spread across two lists, some get lost. Keep one group, switch all routes to it, mark the second for deletion.
One person is "overwhelmed" with the group's tasks. This happens if they are the only one in the composition. Add colleagues — tasks will become available to everyone, and anyone will be able to Accept for Execution.
9. FAQ
What is the difference between "Task Executor Groups" and "User Groups"? "User Groups" manage access rights (what a person can see and change in the data). "Task Executor Groups" manage task addressing (who the assignment falls to). These are different reference books with different purposes — don't confuse them.
Can several people see a task at the same time? Yes. That's the point of group addressing: the task is visible to the entire composition until someone clicks Accept for Execution. After that it is assigned to the executor.
How do I temporarily exclude an employee (vacation, sick leave)? Remove them from the group's composition and save. They will not receive new tasks for this group. When they return, add them back. No need to redo routes.
Does this reference book generate accounting entries, ESF, or SNT? No. This is an organizational setting. It does not create accounting entries, ESF (ESF IS), or SNT, and does not affect VAT.
Can one group be nested inside another and get a shared composition? The hierarchy (parent–child) is only for list organization. Composition is not inherited: members must be listed explicitly in the nested group.
Why can't I find the reference book in the menu?
The command is often not displayed on the panel. Open it via user and rights settings or directly via the link e1cib/list/Справочник.ГруппыИсполнителейЗадач.
Can one person be included in several groups? Yes, there are no restrictions. For example, a warehouse keeper can be in both "Warehouse Keepers" and "Goods Receiving" at the same time.
What happens to already assigned tasks if a person is removed from a group? Tasks they have already accepted for execution personally will remain with them. They will drop out of addressing for the group's future tasks.
Who can edit the composition of groups? A user with user and rights administration privileges. An ordinary manager typically cannot modify the composition of executor groups.
Does the group affect month-end closing or reporting? No. It relates to the organization of work with tasks, not to accounting, and does not participate in regulated operations or VAT/individual income tax reports.
10. Related objects
- Users (
Справочник.Пользователи) — the group's composition is drawn from them; from here you can also see which groups a person belongs to. - User Groups — a neighboring mechanism, but about access rights, not tasks.
- Business processes and tasks (expense application approval, invoices, assignments) — these are what actually use the group as an executor; based on their operation, tasks land on the group.
- Cash expenditure applications, Orders, contracts — documents whose approval is routed through executor groups.
How to find your release
Help → About the program. The "Configuration" line will show "Trade Management for Kazakhstan," edition 3.4, and the exact release; the 1C:Enterprise platform version is indicated separately. Check the release before repeating the steps — on other versions the location of fields may differ slightly.
This guide was prepared for release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).