Directory "Types of Activities" (Catalogs.Types of Activities)

1. Identification

Purpose. The catalog is intended for the classification and accounting of the types of economic activity of the organization in accordance with OKED. It is used by accountants and accounting staff to specify the areas of the company's activities necessary for the correct completion of regulated reporting and tax and contribution analytics. The hierarchical structure (groups and elements) allows for the systematization of types of activity by sections of the classifier. The catalog is rarely changed — usually when registering new business areas or updating the OKED classifier.

Where to find in 1C: section “Enterprise” → “Types of Activity”. Navigation link: e1cib/list/Catalog.TypesOfActivity

2. Attributes and Table Parts

2.1 Header Attributes

Standard attributes of the catalog:

• Code — unique code of the catalog element (type and length are determined by the configuration settings).
• Name — short name of the type of activity for display in selections and lists.
• Parent — reference to the group of the catalog to organize the hierarchy.

2.2 Table Parts

The catalog does not contain table parts. All information is stored in the header attributes.

3. Forms

The catalog contains five forms:

4. Key Module Procedures

In the attached evidence, the program code of the modules (BSL) is not presented, so below are typical handlers characteristic of a hierarchical catalog of this purpose. Their presence/signatures in the specific assembly 3.0.74.2 require verification in the configurator.

Element form module (ElementForm):

• OnCreateOnServer — initialization of the form, setting the availability/visibility of fields (for example, for a group versus an element).
• OKEDCodeOnChange — typical handler for auto-filling/normalizing the OKED code and, if there is a connection, substituting the full name from the built-in classifier.

Object module (ObjectModule):

• CheckFillingProcessing — control of the correctness of filling in the attributes when saving (for this catalog, the attributes are marked as DontCheck, so strict checks are usually absent).
• BeforeSaving — service logic before saving the element.

Manager module (ManagerModule):

• Procedures for programmatically selecting/searching for an element by the OKED code, used by the mechanisms for filling out regulated reporting.

Since the catalog is a regulatory reference information (NRI), its own business logic in the modules is minimal: the main load falls on reading values when forming reports.

5. Posting and Movements

The catalog is not a document and is not posted — it does not generate movements in registers and does not create accounting entries. It is an element of regulatory reference information.

The values of the catalog are used as analytics and filling parameters in other configuration objects. The OKED code and type of activity participate, in particular:

• in the formation of regulated reporting in the RK and when calculating taxes/contributions (for reference on applicable rates in RK for 2026):
  • VAT — 16%; VAT payable account — 3130;
  • Individual Income Tax (IIT) — 10% up to 8,500 MRP annual income and 15% above; basic tax deduction for IIT — 30 MRP/month, but not more than 360 MRP per year;
  • Social Security Contributions (SSC) — 10% (ceiling base 50 MZP), SSC for pension savings — 3.5%, Mandatory Social Health Insurance (MSHI) — 2%, Voluntary Social Health Insurance (VSHI) — 3%, Social Tax — 6%;
  • reference indicators: MRP = 4,325 ₸, MZP = 85,000 ₸, currency — tenge (₸).

An example of typical accounting entries for operations where the type of activity acts as analytics (the catalog itself does not generate entries), according to the typical chart of accounts in RK:

The electronic document management accompanying such operations in RK is electronic invoice (ESF) (ESF IS) and SNF; the OKED code from the catalog is used when forming them.

6. Related Objects and Input Based On

• Organizations / accounting policy — the type of activity is indicated for the purposes of regulated reporting and correct application of tax regimes.
• Regulated Reporting in RK — the OKED code is substituted in the attributes of tax forms and statistical reporting.
• OKED Classifier — the source of codes and full names, with which the catalog is synchronized.

Input based on for this catalog is not provided (it is not a typical scenario for an NRI object). The catalog itself serves as a source of values (reference field) in other objects through SelectionForm/GroupSelectionForm.

7. Extension Points

• Additional attributes and information (properties subsystem) — with the connected mechanism, user-defined characteristics of types of activity can be added without changing the configuration.
• Configuration extensions — adding attributes, forms, and event handlers (OnCreateOnServer, OKEDCodeOnChange) without removing from support.
• Event subscriptions (BeforeSaving, OnSaving) — for custom validation of the OKED code or synchronization with external registers.
• Selection forms — overriding/improving SelectionForm for selection scenarios in industry-specific enhancements.
• Group modification — the “EditSelected” mechanism in ListForm for mass updating when refreshing the OKED classifier.