---
title: "Guide \"RemoveRegulatedReports\" — Technical Description"
country: KZ
lang: en
author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti)
date: 2026-09-07
canonical: https://buhgpt.kz/suraqtar/spravochnik-udalitreglamentirovannyeotchety-tehnicheskoe--en
source: BuhGPT
---

# Guide "RemoveRegulatedReports" — Technical Description

> **TL;DR:** 1. Identification Parameter Value Object Type Catalog Name DeleteRegulatedReports Full Name Catalog.DeleteRegulatedReports Alias — (displayed in the interface with the note “(Do not use)”) Configuration Accounting for Kazakhstan, ed. 3.0 (version 3.0.74.2) Hierarchy Hierarchic

---

1. Identification

Parameter
Value

Object Type
Catalog

Name
DeleteRegulatedReports

Full Name
Catalog.DeleteRegulatedReports

Alias
— (displayed in the interface with the note “(Do not use)”)

Configuration
Accounting for Kazakhstan, ed. 3.0 (version 3.0.74.2)

Hierarchy
Hierarchical (groups and elements)

Code
Auto-generated, format YYYYNNN (year + serial number)

Purpose
Deprecated catalog of regulated reports

Purpose. The catalog is a deprecated metadata object marked for deletion (the prefix Delete in the name and the note “(Do not use)” in the interface). It is retained in the configuration solely for compatibility during updates and data migration from older versions. Historically, it stored a catalog of available forms of regulated reporting and allowed the administrator to replace built-in reports with external files. In the current versions of “Accounting for Kazakhstan” 3.0, work with regulated reporting is conducted through the built-in mechanism of regulated reports of the platform and the service for submission to government agencies, and this catalog is not populated in new accounting nodes.

Where to find in 1C:
e1cib/list/Catalog.DeleteRegulatedReports
In the interface: section “Regulated Reporting” → “(Do not use) regulated reports”.

Important: the object does not participate in tax accounting and calculations. The rates and indicators of the RK for 2026 (VAT 16%, MRP 4,325 ₸, MSP 85,000 ₸, deduction for individual income tax 30 MRP/month, individual income tax 10%/15%, OPP 10%, OPR 3.5%, VOSMS 2%, OSMS 3%, CO 5%, social tax 6%) are implemented in other objects of the configuration (accrual documents, regulated operations), not in this catalog.

2. Header Attributes and Table Parts

2.1 Header Attributes

Name
Type
Mandatory
Purpose

ReportSource
String
Not checked
Defines the source of the report (built-in / external). Used as an indicator of the method of obtaining the form.

DoNotShowInList
Boolean
Not checked
Flag for hiding the item in the general list of available reports. Allows temporarily disabling the report without deleting it.

Description
String
Not checked
Text description of the report, its purpose, and filling features. Displayed to the user in the selection interface.

UseExternalReport
Boolean
Not checked
Flag for using an external report instead of the built-in one. When True, the system takes the report from the ExternalReportStorage attribute.

ExternalReportStorage
ValueStorage
Not checked
Binary data of the external report file (*.erf, *.rdl, etc.). Used only when UseExternalReport = True.

ReportPrefix
String
Not checked
String prefix for identifying the type of report. Used in programmatic access and generating unique names.

In addition to the listed attributes, the object has standard catalog attributes: Code, Name, Parent, ThisIsGroup, DeletionMark, Predefined.

2.2 Table Parts

Table parts are absent.

3. Forms

The catalog contains 6 forms.

Form
Purpose

ElementForm
Main form for editing an element (≈50 elements). Key for the user. Fields: Parent, Name, ReportPrefix, ReportSource, ReportSourceFile, Description. Commands: SaveFile, FormSaveAndClose, FormSave.

GroupForm
Editing the group of the catalog (≈15 elements): Name, Code, Description.

ListForm
List of elements (≈98 elements). Commands: MoveUp, MoveDown, Hide, Restore, New, Journal, Refresh.

ElementSelectionForm
Universal form for selecting an element (≈45 elements).

GroupSelectionForm
Form for selecting a group of the catalog (≈18 elements).

ElementSelectionFormForRestoringVisibility
Specialized form for restoring the visibility of hidden elements (≈44 elements). Contains a tree of values with selection checkboxes.

Key form for the user: ElementForm.

4. Key Procedures of Modules

Direct BSL-evidence for modules in the source is not attached, so below are typical handlers for a catalog of this type (loading/exporting external files, managing visibility, auto-generating codes). When working with a specific build, rely on the code of the form modules.

Form module ElementForm:

- OnCreateOnServer — form initialization, reading attributes, adjusting the visibility of fields ReportSourceFile/ExternalReportStorage depending on UseExternalReport.

- Handler for the command SaveFile — exporting binary data from ExternalReportStorage to a file on the user's disk (save dialog, PlaceFile/file transfer mechanism).

- File upload handler (by the field ReportSourceFile) — placing the selected file in temporary storage and writing it to the ExternalReportStorage attribute (New ValueStorage(...)).

- FormSave, FormSaveAndClose — saving the element with preliminary filling checks and updating related form data.

Form module ListForm:

- Hide / Restore — setting/removing the flag DoNotShowInList for selected elements.

- MoveUp / MoveDown — managing the order (sorting) of elements in the list.

- New, Journal, Refresh — standard commands for creating, navigating to related data, and refreshing the list.

Form module ElementSelectionFormForRestoringVisibility:

- Filling the tree of values with hidden elements (DoNotShowInList = True), processing checkboxes and group restoring of visibility.

Manager / object module:

- Handler OnSettingNewCode / logic for generating the code in the format YYYYNNN (year + serial number).

- FillingHandler — if necessary, initializing default attributes for a new element.

5. Posting and Movements

The catalog is not posted and does not generate movements in registers — it is a catalog object, not a document. It does not create postings according to the RK chart of accounts.

For context: accounting postings and records in the configuration form accounting documents that use the standard RK chart of accounts, for example:

Account
Name

1010 / 1030
Cash (cash / current bank accounts)

1210
Short-term receivables from customers

1330
Goods

3310
Short-term payables to suppliers

3130
VAT payable (rate 16% in 2026)

6010
Revenue from sales

7010
Cost of sales

This catalog does not participate in such postings and is not a dimension/resource of any accounting registers. It only stores metadata about forms of regulated reporting.

6. Related Objects and Input Based On

- Input based on: not provided (the catalog does not serve as a basis and is not input based on).

- External report files (*.erf, *.rdl) — the only external link: stored in ExternalReportStorage, loaded/exported through ElementForm.

- Regulated reporting / electronic documents: the current submission of reports and work with electronic invoices (ESF) and electronic documents in the configuration is performed through the standard mechanisms of regulated reports and the electronic document subsystem, not through this catalog.

- Migration: the object is only related to historical data — when updating from older versions, previously created elements could be transferred here. In new databases, the catalog is usually empty.

7. Extension Points

Since the object is marked for deletion, it is not recommended to modify it — any extensions will lose meaning when the catalog is decommissioned. If modification is still necessary for migration support:

- Configuration extension — borrowing forms (ElementForm, ListForm) and adding handlers &Before/&After to save and load file commands without changing standard modules.

- Event subscriptions (BeforeSaving, OnSaving) of the catalog — for integrity control during bulk data transfer.

- Migration processing — transferring significant elements to the current receiving object of regulated reporting through processing code, not through direct modification of the catalog.

Requires verification (version-specific): the presence and content of form modules, as well as the exact receiving object to which functionality has been transferred, depend on the specific build 3.0.74.2 and the history of database updates.

---
_BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_