RUKKENZH
Ask AI
Sections1C configuration objects
Reference "Mailing Groups and Notifications" (Trade Management for Kazakhstan 3.4.5.21)
Article language:🇷🇺 RU🇰🇿 KK🇬🇧 EN🇨🇳 ZH
Article version:📘 For accountants⚙️ For technical specialists

Reference "Mailing Groups and Notifications" (Trade Management for Kazakhstan 3.4.5.21)

Applies to: 1С:Управление торговлей для Казахстана, release 3.4.5.21 (9 July 2026) · by 1C-Sapa Group, 1C partner
СТ
Сапа Т.И. — 1C and accounting expert, practising trainer
Prepared by the BuhGPT editorial team

1. Identification

Parameter Value
Object type Catalog (Reference)
Name ГруппыРассылокИОповещений
Full name Справочник.ГруппыРассылокИОповещений
Synonym "Mailing and Notification Groups"
Configuration Trade Management for Kazakhstan, ed. 3.4.5.21
Hierarchy Typically linear (no group hierarchy) — a service classifier
Owner None (independent catalog)
Purpose A classifier for combining recipients (users, contact persons, counterparties) into named groups used by the report mailing mechanism and the notification/alert system. Allows scheduled mailings and notifications to be addressed to a pre-configured group rather than individual recipients.

Where to find it: navigation link e1cib/list/Справочник.ГруппыРассылокИОповещений. In the interface, items are usually accessible from the report mailing settings and the notification subsystem (administration/service section), not from "sales" sections, since the object is service-related in nature.


2. Header attributes and tabular sections

The catalog is a service address classifier, so the set of fields is minimal and focused on identifying the group and storing the list of recipients.

Header attributes

Attribute Type Purpose
Код (Code) String/Number Standard item code, auto-numbering
Наименование (Description) String Name of the mailing/notification group (e.g., "Managers", "Accounting", "Sales Department Managers")
ПометкаУдаления (DeletionMark) Boolean Standard deletion mark attribute
Описание/Комментарий (Description/Comment) String (multiline) Free-form text description of the group's purpose

Tabular section "Composition" (group recipients)

Column Type Purpose
Получатель (Recipient) CatalogRef (composite: Users / Individuals / ContactPersons / Partners) Addressee included in the group
АдресЭлектроннойПочты (EmailAddress) String Explicit e-mail address of the recipient (if not taken from the recipient's contact information)
СпособОповещения (NotificationMethod) Enumeration Delivery channel (e-mail, pop-up notification, SMS — depending on the subsystem composition)
Использовать/Активность (Use/Active) Boolean Row activity flag — allows temporarily excluding a recipient without deleting them

The exact set of attributes and the presence of the "Composition" tabular section are version-specific: in some 3.4 releases the recipient list is stored directly in the catalog, while in others only the group name is stored, and recipient binding is performed in the mailing/notification settings. Requires verification against the specific 3.4.5.21 build.


3. Forms

Form Purpose
ФормаСписка (List form) (default list form) Viewing and filtering groups, creating/marking for deletion, navigating to an item
ФормаЭлемента (Item form) (default item form) Editing the group name and its composition (recipient table)
ФормаВыбора (Selection form) Selecting a group from other objects (in report mailing and notification settings)

As is typical for a service catalog, specialized forms (wizards, assistants) are usually absent; auto-generated or standard managed forms are used instead.


4. Key module procedures

The attached evidence contains only the purpose facet; the source code of the modules (BSL) is not attached. Below is a typical set of handlers for a catalog of this kind; specific lines/names require verification against the object module in build 3.4.5.21.

Object module:

  • ОбработкаПроверкиЗаполнения (FillCheckProcessing) — checks that the name is filled in and that the list of active recipients is not empty; validates e-mail correctness in the composition rows.
  • ПередЗаписью (BeforeWrite) — address normalization, deduplication of rows in the "Composition" tabular section.
  • ПриКопировании (OnCopy) — resets service flags when copying a group.

Item form module:

  • ПриСозданииНаСервере (OnCreateAtServer) — configures visibility of composition columns and availability of notification channels.
  • СоставПолучательПриИзменении (Composition Recipient OnChange) — substitutes e-mail from the contact information of the selected recipient.
  • ОбработкаПроверкиЗаполненияНаСервере (FillCheckProcessingAtServer) — additional validation before writing from the form.

Manager module:

  • Procedures for building the list of group recipients for the report mailing and notification mechanisms (returns an array/table of addresses by group reference).

5. Posting and register movements

The catalog is not a document and is not posted — it does not generate registers or accounting entries. It is a classifier and therefore does not participate directly in operational or regulated accounting.

Indirectly, a catalog item is used as a dimension/filter in service mechanisms:

  • in report mailing settings (scheduled jobs) — as an address group;
  • in the notification/alert subsystem — as a list of event subscribers.

For reference, the financial operations of the Trade Management for Kazakhstan 3.4 configuration itself (to which this catalog is unrelated) are reflected using the standard Kazakhstan chart of accounts: sales — Dt 1210 Kt 6010 and Dt 3130 Kt … for VAT; cash receipt — Dt 1030 Kt 1210; cost write-off — Dt 7010 Kt 1330; settlements with suppliers — Kt 3310. The VAT rate in Kazakhstan for 2026 is 16%. These entries are provided as configuration context and are not related to movements of this catalog.


6. Related objects and "input based on"

  • Recipients (addressees): "Users", "Individuals", "Contact Persons", "Partners/Counterparties" catalogs — sources of the group composition rows.
  • Report mailings: scheduled mailings reference the group as a set of recipients.
  • Notification/alert subsystem: uses the group as a list of subscribers.
  • Contact information: recipient e-mail addresses are taken from the "Contact Information" information register.

"Input based on" is generally not provided for a service catalog (neither as a basis nor as a result).


7. Extension points

  • Configuration extension: adding attributes (e.g., group priority, default e-mail template, trigger event type) via an extension without removing the configuration from support.
  • Event subscriptions: ПередЗаписью/ПриЗаписи (BeforeWrite/OnWrite) of the catalog — for auditing changes to group composition.
  • Overridable modules: integration into the recipient list generation procedures (object manager) for connecting external delivery channels (messengers, SMS gateways).
  • Additional attributes/details: via the "Properties" mechanism for arbitrary group classification without changing the metadata.
  • Scheduled jobs: linking a group to custom automatic mailing scenarios.

Frequently asked questions

Is the "MailingAndNotificationGroups" catalog posted, and does it generate journal entries?
No. This is a service classifier catalog, not a document. It is not posted and does not generate register movements or accounting entries. It is used only as an address group in report distribution and notification mechanisms.
What is this catalog used for?
To combine recipients (users, contact persons, counterparties) into named groups, in order to address scheduled report distributions and notifications to a group of recipients at once, rather than to each individually.
How do I open the list of groups?
Via the navigation link e1cib/list/Справочник.ГруппыРассылокИОповещений, or from the report distribution settings and the notification subsystem in the administration/service section.
Why doesn't the description include the exact composition of attributes from the code?
The attached evidence contains only the purpose facet; the source code of the modules is not attached. The set of attributes (in particular, the presence of the "Composition" tabular section) is version-specific and requires verification against the object module in build 3.4.5.21.

Read also

Latest answers

Sources

Was this article helpful?
💼 Need help with 1C or accounting? Слава КВЦ — many years of 1C practice in Kazakhstan. Explore the annotated Tax Code of RK 2026 or ask in the BuhGPT chat — answers in seconds.