RUKKENZH
Задать вопрос AI
SectionsОбъекты конфигурации 1С
Directory "Nomenclature Groups" - Technical Description (Accounting for Kazakhstan 3.0.74.2)
Язык статьи:🇷🇺 RU🇰🇿 KK🇬🇧 EN🇨🇳 ZH
Версия статьи:📘 Для бухгалтера⚙️ Для тех-специалиста

Directory "Nomenclature Groups" - Technical Description (Accounting for Kazakhstan 3.0.74.2)

Applies to: 1С:Бухгалтерия для Казахстана, release 3.0.74.2 · by 1C-Sapa Group, 1C partner
СТ
Сапа Т.И. — Эксперт по 1С и бухгалтерскому учёту, преподаватель-практик

1. Identification

Parameter Value
Object Type Catalog
Name ProductGroups
Full Name Catalog.ProductGroups
Alias — (not set)
Configuration Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2)
Type of Catalog Hierarchical (hierarchy of groups and items)
Main Representation Name

Purpose. The catalog is intended for group classification of products, independent of its own hierarchy in the Products catalog. The product group combines goods, works, and services based on arbitrary analytical criteria and is used as a dimension of analytical accounting (subaccount) when reflecting revenues from sales and cost of goods sold. Practically, this is the dimension used in the RK for accounting revenue on account 6010 "Revenue from Sales of Goods and Services" and cost of goods sold on account 7010 "Cost of Goods Sold", as well as for reporting by groups of goods/services.

The configuration supports two modes:

  • Single Base Group — simplified accounting without actual separation by groups;
  • Multiple Groups — extended classification.

During the initial setup, the configuration automatically creates a base product group and manages the functional option of multiple grouping depending on the number of actually created groups.

Where to find in 1C: section "Enterprise" → "Product Groups". Navigation link: e1cib/list/Catalog.ProductGroups


2. Header Attributes and Table Parts

2.1 Header Attributes

The catalog uses only standard attributes of the hierarchical catalog; there are no custom user attributes in the metadata.

Name Type Mandatory Purpose
Code String/Number Yes (auto-numbering) Unique identifier of the item/group
Name String Yes Name of the product group, main representation
Parent CatalogReference.ProductGroups No Reference to the higher-level node for the hierarchical structure

Additional characteristics are not placed in the header attributes but in the table part of additional attributes (see below) through the "Properties" mechanism.

2.2 Table Parts

AdditionalAttributes

Stores arbitrary additional characteristics of the product group, defined by the user through the property management subsystem.

Name Type Purpose
Property PlanTypesOfCharacteristics.AdditionalAttributesAndInformation Reference to the definition of the additional property
Value Composite type Actual value of the property; specific type is determined by the setting in the "Property" field
TextString String Text representation of the value for long text fields

3. Forms

Form Purpose
ElementForm Main form for editing the product group. Contains all functions for managing the composition of the group (composition table, composition update field) and additional attributes. ~51 control elements. Key form for the user.
GroupForm Simplified form for editing nodes of the hierarchy (folders). ~13 elements.
ListForm List of all product groups; includes group change command. ~56 elements.
SelectForm Form for selecting a group from the list when filling in attributes in other objects. ~50 elements.
SelectGroupForm Specialized form for selecting a group node (e.g., for specifying the parent). ~23 elements.

4. Key Module Procedures

In the attached evidence, the specific BSL code of the catalog module is not provided, so below is a typical set of handlers for a catalog of this type in BK 3.0. Specific names and the presence of handlers require verification in the object/form module of the target release.

Object Module (typical handlers):

  • BeforeWriting — control of data correctness before writing; if necessary — setting the base group flags.
  • OnWriting — recalculation of the number of created groups and management of the functional option of multiple grouping: when more than one significant group appears, the option is enabled; when returning to a single base group — it is disabled.
  • BeforeDeleting — prohibition of deleting the base group and control of referential integrity (use of the group in transactions/documents).
  • FillingHandler — filling in attributes when creating a new item (including substituting the parent, default values).

Forms (typical handlers):

  • ElementForm.OnCreatingOnServer — initialization of the group composition table, setting visibility of fields depending on the accounting mode.
  • Composition form commands — adding/removing products to the group and updating the composition (recalculation of the belonging of product items to the group).
  • Handlers of the "Properties" subsystem (ClientCommands/ManageProperties) — rendering and recording the table part AdditionalAttributes.

5. Posting and Movements

The catalog is not a document and does not independently generate movements and postings — records in accounting registers and accumulations are created by documents that refer to the product group.

The product group acts as analytics (subaccount) and participates in postings generated by sales, receipts, and month-end closing documents. In the typical chart of accounts of the RK, this is reflected as follows:

Sale of goods/services (document "Sale of Goods and Services", generation of ESF/SNT in the ESF IS):

Dr Cr Content Analytics
1210 6010 Revenue reflected (short-term receivables from customers ↔ income) 6010 — by product group
6010 3130 VAT accrued payable at the rate of 16%
7010 1330 Cost of goods sold written off 7010 — by product group

Payment from customer / to supplier:

Dr Cr Content
1030 1210 Receipt of money into the current account in settlement of receivables
3310 1030 Payment to supplier from the current account

Example for VAT rate (Kazakhstan, 2026 — rate 16%). Sale of goods for a total of 1,160,000 ₸ including VAT:

  • amount excluding VAT: 1,160,000 ÷ 1.16 = 1,000,000 ₸ → Dr 1210 Cr 6010 for 1,000,000 ₸ (by product group);
  • VAT: 160,000 ₸ → Dr 6010 Cr 3130;
  • cost (conditionally 700,000 ₸): Dr 7010 Cr 1330 (by product group).

Thus, the product group ensures the receipt of revenue and cost turnovers by groups for reports on financial results and profitability analysis.

Numerical norms are provided for the RK for 2026: VAT 16%, MRP 4,325 ₸, MSP 85,000 ₸. These parameters relate to the accounting of documents using the group, not to the catalog itself.


The catalog is a classifier object, so input based on it is generally not provided; on the contrary, it is used as a value of an attribute in other objects:

  • Catalog Products — the attribute "Product Group" links the product position with the group; this forms the composition of the group.
  • Sales and receipt documents (e.g., "Sale of Goods and Services", "Provision of Services") — use the group as analytics for income/cost.
  • Accounting Register (Cost Accounting) — accounts 6010 and 7010 are maintained with subaccount "Product Groups".
  • Accumulation Registers for Inventory and Sales Accounting — measurement/attribute "Product Group".
  • Electronic documents ESF and SNT (ESF IS) — generated by sales documents; the group itself is not directly exported in ESF/SNT but determines the analytics of postings for these documents.
  • Properties Subsystem (PlanTypesOfCharacteristics.AdditionalAttributesAndInformation) — source of values for the table part AdditionalAttributes.
  • Functional option of multiple grouping — managed by the record of catalog elements.

7. Extension Points

  • Additional attributes and information — standard extension without changing the configuration through the "Properties" mechanism (table part AdditionalAttributes).
  • Configuration Extensions — adding attributes, commands, and form handlers (OnCreatingOnServer, BeforeWriting) without removing from support.
  • Group change of attributes — processing from the list form for mass changes of group properties.
  • Event subscriptions (BeforeWriting/OnWriting/BeforeDeleting of the catalog) — for embedding custom logic for controlling multiple grouping and integrity of composition.
  • Reports by groups — building analytics of revenue (6010) and cost (7010) by product groups in the data composition system.

Version-specific (requires verification in release 3.0.74.2): the exact composition of control elements of forms, presence and names of handlers of the object module, as well as the logic of auto-creation of the base group and switching the functional option of multiple grouping.

Частые вопросы

Does the directory "NomenclatureGroups" generate entries?
No. This is a reference-classifier; it is not a document and does not create movements on its own. Entries are generated by documents (sales, receipts, month-end closing), and the nomenclature group serves as analytics (subaccount) primarily for accounts 6010 "Revenue from Sales" and 7010 "Cost of Goods Sold".
What is the purpose of nomenclature groups if the nomenclature already has its own hierarchy?
The own hierarchy of the "Nomenclature" directory is the structure for storing items. Nomenclature groups provide a separate, independent analytical perspective for accounting revenue and cost, and for generating reports by groups of goods, works, and services, which does not coincide with the folders of the "Nomenclature" directory.
What is the mode of a single basic group and multi-grouping?
The configuration supports simplified accounting with a single basic group (automatically created during setup) and an extended mode with multiple groups. When more than one significant group appears, the functional option for multi-grouping is activated; when returning to a single basic group, it is deactivated.
How to set additional characteristics for the group?
Through the tabular part "AdditionalAttributes" and the subsystem "Properties": the field "Property" refers to the definition from the classification of characteristic types "AdditionalAttributesAndInformation", "Value" stores the actual value of a composite type, "TextString" is the textual representation for long texts. This is a standard extension point without changing the configuration.

Read also

Источники

Была ли статья полезна?
💼 Нужна помощь с 1С или учётом? Слава КВЦ — многолетняя практика в 1С в Казахстане. Изучите разложенный НК РК 2026 или спросите в чате BuhGPT — ответит за секунды.