--- title: "Directory \"Types of Inspections\" - Technical Description (Accounting for Kazakhstan 3.0.74.2)" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/spravochnik-vidyproverok-tehnicheskoe-opisanie-buhgalteri-en source: BuhGPT --- # Directory "Types of Inspections" - Technical Description (Accounting for Kazakhstan 3.0.74.2) > **TL;DR:** 1. Identification Parameter Value Object Type Catalog Name TypesOfChecks Full Path Catalogs.TypesOfChecks / Catalog.TypesOfChecks Synonym — (no separate synonym assigned; the object's name is used) Configuration Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 Currency --- 1. Identification Parameter Value Object Type Catalog Name TypesOfChecks Full Path Catalogs.TypesOfChecks / Catalog.TypesOfChecks Synonym — (no separate synonym assigned; the object's name is used) Configuration Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 Currency of Transactions Tenge (₸) Purpose. The catalog is intended for the classification and accounting of various types of checks (audits, control activities) in the accounting system of Kazakhstan. The catalog element can refer to specific checked objects (documents, elements of other catalogs) or describe abstract concepts — for example, "Month-End Closing Operation." It is used by accountants and auditors to structure control procedures: when setting up internal control systems, planning audit activities, and recording the results of checks. The frequency of use depends on the scale of control procedures in the organization — from weekly to monthly. Where to find in 1C: section "Standard Subsystems" → "Types of Checks". Navigation link: e1cib/list/Catalog.TypesOfChecks 2. Attributes and Table Parts 2.1 Header Attributes The distinctive feature of the catalog is universal attributes of composite type boolean/string/dateTime. The specific purpose of each field is determined by the context of the type of check for which the element is created. The filling check is disabled (DontCheck), so the obligation is controlled by application logic, not the platform. Name Type Mandatory Purpose Property1 boolean / string / dateTime DontCheck Universal property for storing a boolean value, string, or date/time. The purpose is determined by the context of the type of check Property2 boolean / string / dateTime DontCheck Second universal property with a similar composite type for additional characterization of the check Property3 boolean / string / dateTime DontCheck Third universal property that expands the possibilities for describing the parameters of the type of check Property4 boolean / string / dateTime DontCheck Fourth universal property for accounting specific attributes of control activities Property5 boolean / string / dateTime DontCheck Fifth universal property that completes the basic set of characteristics of the type of check Note. The composite type of all five attributes (boolean/string/dateTime) provides maximum flexibility in adapting the catalog to various types of checks without modifying metadata. 2.2 Table Part "PropertiesOfObject" (Properties of the Object) Stores a dynamic set of additional properties of the checked object in a "key-value" format. Allows unlimited expansion of the attribute composition of the type of check without changing the configuration structure. Name Type Purpose PropertyName string Name of the characteristic of the checked object (for example, "Responsible Person", "Frequency of Check") PropertyValue boolean / string / dateTime Value of the corresponding property; supports boolean flags, textual descriptions, and timestamps 3. Forms Form Purpose ElementForm Main form for editing the catalog element (≈58 controls). Key user form: filling in the name, five universal properties, and the table part "PropertiesOfObject" ListForm (default) Standard form for selecting and viewing the list of types of checks. Opens via the link e1cib/list/Catalog.TypesOfChecks SelectForm (default) Used when selecting the type of check in the attributes of documents and control processes Only ElementForm is explicitly described in the metadata; list and selection forms are generated automatically by the platform if custom ones are not defined. 4. Key Module Procedures No specific BSL code in evidence for this object is attached. For catalogs of this type, standard handlers are used (form module / object module): - OnCreateOnServer (form module) — initial setup of the element form: availability and visibility of universal property fields depending on the context, initialization of service attributes of the form. - FillProcessing (object module) — filling in attributes when creating a new element, including when entering based on or from filling data. - BeforeSaving (object module) — application check of the consistency of values Property1…Property5 and rows of the table part "PropertiesOfObject" before saving (platform check is disabled by the flag DontCheck). - FillCheckProcessing (object module) — control of filling key properties according to the logic of the specific type of check. - OnPropertyChange… (form module) — recalculation of dependent fields and control of visibility when selecting a value for one of the universal properties. Requires verification for version 3.0.74.2: the exact composition of handlers for ElementForm (58 controls implies the presence of procedures for managing the visibility of groups). 5. Posting and Movements The catalog is a non-postable object. It does not itself create records in accounting registers and does not generate postings. The values of the catalog serve as analytics/parameters in documents and processes that already generate movements according to the standard chart of accounts of the RK. Guidelines for the accounts referenced by related accounting operations (standard chart of accounts of Kazakhstan): Account Purpose 1030 Cash on current bank accounts 1210 Short-term accounts receivable from customers 1330 Goods 3130 VAT payable (at the rate of 16 %) 3310 Short-term accounts payable to suppliers 6010 Revenue from sales 7010 Cost of sales Example of impact (sale of goods for 1,000,000 ₸ excluding VAT): - Dr 1210 Cr 6010 — 1,000,000 ₸ (revenue); - Dr 1210 Cr 1330 — 160,000 ₸ (VAT 16 %); - Dr 7010 Cr 1330 — cost of sales. The electronic registration of such operations in the RK is done through ESF (ESF IS) and SNT; the type of check may be used to control the correctness of these documents, but it does not generate movements itself. 6. Related Objects and Entry Based On - Documents and internal control / period closing processes — use elements of the catalog as a sign of the type of control activity (for example, "Month-End Closing Operation"). - Checked Objects — through universal properties of composite type, the element can refer to documents and elements of other catalogs or store a textual/logical description of an abstract check. - Entry Based On — a standard mechanism for entry based on for this catalog is not provided in the delivery; the element is created manually or programmatically when setting up control procedures. 7. Extension Points - Table Part "PropertiesOfObject" — standard mechanism for expanding the attribute composition without changing metadata: any additional characteristics are added as "key-value" rows. - Universal Properties Property1…5 — redefining the meaning of fields for a specific type of check in the form/object extension module. - Configuration Extension — adding custom attributes, commands, and forms; redefining BeforeSaving/FillCheckProcessing to implement business control rules. - Event Subscriptions — processing the recording of elements for integration with external regulations of checks. - Additional Attributes and Information (BSP) — with the properties subsystem enabled, expansion is possible without changing the structure of the object. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_