Documents.OrganizationSubdivisions — technical description (Accounting for Kazakhstan 3.0.74.2)

Important note on the object type. In the metadata provided, the object is declared as Документ.ПодразделенияОрганизаций (object_type_ru: "Документ", navigation e1cib/list/Документ.ПодразделенияОрганизаций). However, the attached evidence (purpose and composition of attributes: BIN/IIN, RNN, OKPO, main cash desk, main bank account, "Is a structural subdivision" flag) unambiguously describes a catalog of separate subdivisions/branches, not a posted document. In the standard "Accounting for Kazakhstan" it is a catalog object. The description below is based on the actual purpose from the evidence; the "Document vs Catalog" discrepancy requires verification in the specific build 3.0.74.2 (configurator metadata). The practical conclusion is the same: the object does not perform its own posting and does not generate movements — it is analytics (an accounting dimension) for operational documents.

1. Identification

Purpose. Stores information about separate structural subdivisions and branches of organizations in Kazakhstan. Used for maintaining accounting across several legal addresses of a single organization, when each subdivision has its own BIN/IIN, RNN, bank accounts and cash desks. The object is used in all documents where a specific subdivision needs to be indicated for correct generation of tax reporting and printed forms. Access to subdivisions in the interface depends on the user's rights to the parent organizations.

Where to find it in 1C:

• Navigation link: e1cib/list/Документ.ПодразделенияОрганизаций
• Interface: "Personnel Management" section → "Organization Subdivisions".

2. Attributes and tabular sections

2.1 Header attributes

The widespread "Not checked" is the standard state of this object's attributes: their completion is controlled not by the "Fill check" property but by the business logic of the reports and printed forms that consume these fields.

2.2 Tabular sections

ДополнительныеРеквизиты

Storage of custom additional attributes configured by the administrator via the property management subsystem (SSL, the "Additional attributes and information" mechanism).

(The column composition of the ДополнительныеРеквизиты tabular section is given partially in the evidence; the specific list is standard for the SSL additional attributes mechanism.)

3. Forms

The BSL description of the forms is not attached in the evidence, so the list is typical for an object of this kind:

4. Key module procedures

The BSL code of the modules is not attached in the evidence. Below are the typical handlers for an object of this kind (catalog/accounting-dimension object):

Object module:

• ОбработкаЗаполнения(ДанныеЗаполнения, ...) — filling in default attributes upon creation (including from the parent organization).
• ПередЗаписью(Отказ) — checking the correctness of RNN/BIN-IIN, consistency of the ЯвляетсяСтруктурнымПодразделением / УказыватьРеквизитыГоловнойОрганизации flags.
• ПриУстановкеНовогоКода(СтандартнаяОбработка, Префикс) — setting the prefix/code.
• Working with the "Additional attributes and information" mechanism (writing the ДополнительныеРеквизиты tabular section).

Element form module:

• ПриСозданииНаСервере(Отказ, СтандартнаяОбработка) — initializing field visibility (for example, hiding the "Local budget" block when УчетПоМестнымБюджетам is cleared).
• УказыватьРеквизитыГоловнойОрганизацииПриИзменении / УчетПоМестнымБюджетамПриИзменении — managing the availability of dependent fields.

The exact names and contents of the handlers require verification against the modules of build 3.0.74.2.

5. Posting and movements

The object is not posted and does not generate its own register movements — it is an accounting dimension (analytics), not a business transaction. Entries are generated by operational documents in which the subdivision is specified as an attribute. Below is how RK values for 2026 make it into the entries of the corresponding documents (accounts — standard RK chart of accounts):

Sale of goods (example for the amount of 1,160,000 ₸ including 16% VAT; goods 1,000,000 ₸ + VAT 160,000 ₸):

Broken down by VAT: Dr 1210 Cr 6010 — 1,000,000; Dr 1210 Cr 3130 — 160,000 (VAT 16%).

Receipt of goods (example 1,160,000 ₸ including 16% VAT):

Payment from customer / to supplier via the subdivision's ОсновнойБанковскийСчет or ОсновнаяКасса: Dr 1030 Cr 1210 (receipt to the current account), Dr 3310 Cr 1030 (payment to the supplier).

The subdivision as an attribute determines:

• through which cash desk/bank account (1030) the money passes;
• in which tax authority (НалоговыйКомитет) and budget (МестныйБюджет, when УчетПоМестнымБюджетам is set) taxes are reflected;
• the details of the ESF/SNT (BIN/IIN, RNN, OKPO) — when generating electronic invoices in the ESF IS and accompanying waybills for goods.

Payroll taxes/contributions of the RK for 2026, where the subdivision is a dimension of accruals (for reference, current rates/bases): IIT 10% up to 8,500 MCI of annual income and 15% above that; the basic IIT deduction — 30 MCI/month, but no more than 360 MCI per year; OPC 10% (base cap 50 MMW), OPCE 3.5%, CHIC 2%, CHIP 3%, SC 5%, social tax 6%. Constants: MCI = 4,325 ₸, MMW = 85,000 ₸.

6. Related objects and entry on the basis

References:

• Справочник.Контрагенты — НалоговыйКомитет, МестныйБюджет;
• Справочник.Кассы — ОсновнаяКасса;
• Справочник.БанковскиеСчета — ОсновнойБанковскийСчет;
• Справочник.ВидыДеятельности — ОсновнойВидДеятельности;
• ПланВидовХарактеристик.ДополнительныеРеквизитыИСведения — additional attributes.

Used in (as an attribute-dimension): sales documents, receipt documents, cash and bank documents, payroll documents, tax returns and regulated/statistical reporting, printed forms (selection of subdivision or parent organization details based on the УказыватьРеквизитыГоловнойОрганизации flag), generation of ESF and SNT.

Entry on the basis: for an accounting-dimension object, standard entry on the basis is generally not provided; creation and filling are performed manually or via the fill handler from the parent organization.

7. Extension points

• Additional attributes and information (SSL) — extending the set of subdivision attributes without changing the configuration.
• Configuration extensions — adding attributes, forms, overriding handlers (ПередЗаписью, ПриСозданииНаСервере) without taking it off support.
• Event subscriptions — reacting to the writing of a subdivision (for example, catalog synchronization, integrations).
• Overridable SSL modules — default fill rules, attribute checks.
• Printed forms — adding/replacing templates taking into account the УказыватьРеквизитыГоловнойОрганизации flag.
• Data exchange / integrations — exporting details (BIN/IIN, RNN, OKPO) to the ESF IS and SNT modules.