--- title: "Catalog \"Positions of Organizations\" (Catalogs.PositionsOfOrganizations) — Technical Description" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/spravochnik-dolzhnosti-organizaciy-catalogs-dolzhnostiorg-en source: BuhGPT --- # Catalog "Positions of Organizations" (Catalogs.PositionsOfOrganizations) — Technical Description > **TL;DR:** 1. Identification Parameter Value Object Type Catalog Name PositionsOfOrganizations Full Name Catalog.PositionsOfOrganizations ( Catalogs.PositionsOfOrganizations ) Synonym Positions of organizations Configuration Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) Navig --- 1. Identification Parameter Value Object Type Catalog Name PositionsOfOrganizations Full Name Catalog.PositionsOfOrganizations (Catalogs.PositionsOfOrganizations) Synonym Positions of organizations Configuration Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) Navigation Link e1cib/list/Catalog.PositionsOfOrganizations Purpose. The catalog maintains a classifier of positions used in organizations for processing personnel documents, payroll calculation, and reporting. Positions from the catalog are indicated in personnel documents (employment, personnel transfers, orders, time sheets), as well as in the employee directory and staffing data. Main users are HR specialists, payroll accountants, and managers. The catalog is filled as needed: during the initial setup of accounting, when hiring employees for new positions, and when changing the staffing schedule. The catalog supports versioning (automatic tracking of the history of changes to elements) for auditing personnel changes and declension of position names by cases — for correct output in printed forms of documents and reports. Where to find in 1C: section "Personnel Management" → "Positions of Organizations". 2. Attributes and Table Parts 2.1 Header Attributes The catalog uses only standard attributes; there are no specific additional attributes in the header. Name Type Mandatory Purpose Code String Automatically filled Unique position code for identification and sorting Name String Mandatory Full name of the position (e.g., "Chief Accountant", "Sales Manager") 2.2 Table Parts AdditionalAttributes Purpose: storage of user-defined additional attributes and information about the position, configured individually for the needs of the organization (e.g., position category, pay grade, code according to OKPDTR). Name Type Purpose Property PlanOfCharacteristicTypes.AdditionalAttributesAndInformation Reference to the configured property (determines which additional attribute is stored) Value Composite type Value of the additional attribute (type depends on the property configuration) TextString String Text representation of the value (for string properties and display) 3. Forms The catalog contains three forms. Form Purpose ElementForm Main form for editing the position. Contains fields for code and name, as well as a "Declensions" button for configuring case forms of the name. Key form for the user's daily work. ListForm Form of the list of all positions with the ability to group change selected elements. SelectForm Simplified form for selecting a position when filling out documents and related catalogs. 4. Key Module Procedures The application BSL code in evidence is not attached, so below are the typical handlers characteristic of a catalog of this kind in BSP configurations (to which "Accounting for Kazakhstan" belongs). Specific lines of modules are version-specific and require verification in a specific build. Object Module (ObjectModule) - ProcessingFilling — primary initialization of attributes when creating a new element. - BeforeWriting — service logic before writing (including interaction with the "Properties" and "Object Versioning" subsystems). - WhenCopying — correct preparation of a copy of the element (e.g., clearing declensions/additional values if necessary). Element Form Module (ElementForm) - WhenCreatedOnServer — output of additional attributes through PropertyManagement.UpdateAdditionalAttributeElements. - WhenWrittenOnServer / BeforeWritingOnServer — transferring values of additional attributes to the object (PropertyManagement.BeforeWriting…). - Command "Declensions" — calling the declension mechanism for names (subsystem "Declensions") to form case forms. General Mechanism. Tracking the history of changes is implemented by the "Object Versioning" subsystem (regulatory recording of object versions), and additional attributes — by the plan of characteristic types AdditionalAttributesAndInformation and general modules PropertyManagement / ClientPropertyManagement. 5. Posting and Movements The catalog is not a document and does not perform postings — it does not generate movements in registers and accounting entries. It is a normative reference object (NRI). The influence of the position on accounting is indirect, through documents where it is indicated: - In personnel documents and payroll calculation documents, the position is linked to the employee and participates in the analytics of accruals. - Entries are generated by payroll accrual/payment documents, not the catalog itself. According to the typical chart of accounts of the RK, payroll expenses are reflected in the credit of the account for liabilities to personnel, with expenses allocated to cost accounts; withholdings and contributions are reflected in the corresponding accounts for liabilities to the budget and funds. Current calculation parameters of the RK for 2026 (used in related documents, not in the catalog itself): Indicator Value 2026 MPR 4,325 ₸ MZP 85,000 ₸ Basic tax deduction for PIT 30 MPR/month, not more than 360 MPR/year PIT 10% up to 8,500 MPR annual income, 15% above OPV 10% (base ceiling — 50 MZP) OPVR 3.5% VOSMS 2% OSMS 3% SO (social contributions) 5% Social tax 6% VAT rate 16% These figures are provided as context for calculations in RK-2026 and are applied in calculation documents; they do not affect the catalog of positions itself. 6. Related Objects and Input on Basis Input on Basis. For the catalog "Positions of Organizations," input on basis and creation based on other objects are not provided (typical for NRI of this kind). Related Objects (the catalog acts as a value of the attribute): - Catalog "Employees" / "Individuals" — current position of the employee. - Personnel accounting documents: "Employment", "Personnel Transfer", personnel orders. - Documents for time tracking (time sheets) and payroll calculation documents. - Staffing schedule (if used) — staffing positions refer to the position. Used BSP subsystems: - "Properties" — plan of characteristic types AdditionalAttributesAndInformation (table part AdditionalAttributes). - "Object Versioning" — history of changes. - "Declensions" — case forms of the name. 7. Extension Points - Additional attributes and information — standard way of extension without changing the configuration: position category, pay grade, code according to OKPDTR, etc. are added through the properties mechanism. - Configuration Extensions — adding attributes, forms, commands, and overriding handlers of the object/form module without removing from support. - Event subscriptions (BeforeWriting, WhenWriting) — for external validation of names, duplicate control, or integration with third-party HR systems. - Additional processing and commands (subsystem "Additional Reports and Processing") — user-defined actions assigned to the catalog. - Declension configuration — extension/correction of case forms for printed forms. Version-specific details (exact names/lines of module procedures, composition of overridden methods) should be verified with the specific build 3.0.74.2. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_