Does the "RegulatedReport" document generate accounting entries?

No. The document itself does not create entries — it stores reporting data. Entries are generated by the related document "ReflectionOfTaxReportingInRegulatedAccounting", a reference to which is stored in the DocumentOfReflectionInAccounting attribute.

What VAT rate and MCI value are used in the examples for the RK 2026?

The VAT rate is 16% (not 12%), MCI = 4,325 ₸, MMW = 85,000 ₸. The basic tax deduction for IIT is 30 MCI per month (no more than 360 MCI per year).

Why do the messages "Insufficient rights!" and "Report not found!" appear?

They are issued in the OpenReportFormOnClient procedure of the list form when the FormOpeningResultOnServer values equal "Insufficient rights" and "Report not found" respectively. Check the user's rights and the availability/correctness of the selected report.

How do I open the list of regulated reports?

Section "Regulated reporting" → "Regulated reporting", or via the navigation link e1cib/list/Document.RegulatedReport.

Document "Regulated Report" — technical description (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Parameter	Value
Object type	Document (Documents)
Name	`РегламентированныйОтчет`
Full path	`Документ.РегламентированныйОтчет`
Synonym	«Regulated reporting»
Configuration	Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2)
Accounting country	Republic of Kazakhstan, currency — tenge (₸)
Purpose	Generation, storage and management of mandatory reporting submitted to government bodies of the RK (tax returns, financial and statistical reporting). Serves as a container of structured report data, supports versioning and electronic signing. Does not generate postings on its own.

Where to find in 1C: section «Regulated reporting» → «Regulated reporting». Navigation link: e1cib/list/Документ.РегламентированныйОтчет

The document is a universal «envelope» for any regulated report: the specific declaration form (FNO 100.00, 200.00, 300.00, etc.) is selected via the report type, and its data is stored in linked structures (templates/value storages). The reflection of declaration indicators in accounting is performed by a separate document — ОтражениеНалоговойОтчетностиВРеглУчете.

2. Header attributes and tabular sections

2.1 Header attributes

Attribute	Type	Purpose
`Номер`	String	Standard document number.
`Дата`	Date	Document date (report compilation date).
`Организация`	СправочникСсылка.Организации	Organization on behalf of which the report is submitted.
`ВидОтчета` / `Форма`	String / СправочникСсылка	Identifier of the specific regulated form (e.g., VAT return — FNO 300.00, for IIT/social tax — FNO 200.00).
`Период` (`НачалоПериода` / `КонецПериода`)	Date	Reporting period for which the report is generated (month, quarter, year).
`Состояние` / `Статус`	Enumeration	Current state of the report: «Prepared», «Signed», «Sent», etc.
`ДокументОтраженияВУчете`	ДокументСсылка.ОтражениеНалоговойОтчетностиВРеглУчете	Link to the associated document that generates postings based on declaration data. Key attribute of the «report → accounting» link.
`ДанныеОтчета` / `ХранилищеЗначения`	ХранилищеЗначения	Serialized data of the completed report form.
`Ответственный`	СправочникСсылка.Пользователи	User responsible for the report.
`Комментарий`	String	Arbitrary comment (explanations, notes to the report).

Note: the set of attributes of a specific build may differ in the composition of service fields for versioning and signing. Requires verification in the configurator only for the exact names of state/period attributes — they are version-specific.

2.2 Tabular sections

The container document, as a rule, does not have «business tabular sections» in the usual sense — detailed declaration indicators are stored in a structured form (templates/value storage) rather than in separate tabular sections. Service tabular sections are possible:

Tabular section	Purpose
`Разделы` / `Приложения`	List of sections and appendices of the selected report form.
`ЭлектронныеПодписи` (or signature storage)	Digital signature (EDS) data with which the report is signed before submission.

3. Forms

Form	Purpose
List form (`ФормаСписка`)	Main entry point. List of all regulated reports with filtering by type and period. The form of a specific report is opened from it (see procedure `ОткрытьФормуОтчетаНаКлиенте`).
Document form / report form	Form for editing data of the selected regulated form: filling in indicators, auto-fill based on accounting data, checking control ratios.
Report type selection / picking form	Selection of a specific FNO form when creating a new report.
Signing form	Applying an electronic signature to the report before sending it to the tax committee.

4. Key module procedures

From evidence (release 3.0.68.1, mechanics retained in 3.0.74.2):

ОткрытьФормуОтчетаНаКлиенте (Form.ФормаСписка) — opens the form of a specific regulated report. On the server, РезультатОткрытияФормыНаСервере is calculated; for values "Недостаточно прав" or "Отчет не найден", the user is shown the messages «Insufficient rights!» and «Report not found!» respectively. When controlling access/availability of the report, check exactly this condition.

Typical handlers of this type of object (general 1C logic), if there is no specific code in evidence:

ПередЗаписью / ПриЗаписи — control of filling in the period, organization and report type; fixing the data version.
ОбработкаЗаполнения — initial filling when creating a new report (scenario 3.1).
ОбработкаПроверкиЗаполнения — checking mandatory attributes and control ratios of the form.
Client commands of the list form — filtering by type and period (scenario 3.3), signing (scenario 3.4), transition to reflection in accounting (scenario 3.5).

Typical errors (verbatim from the code)

1C message	Where it occurs	Condition in the code
Insufficient rights!	Form.ФормаСписка / `ОткрытьФормуОтчетаНаКлиенте`	`РезультатОткрытияФормыНаСервере = "Недостаточно прав"`
Report not found!	Form.ФормаСписка / `ОткрытьФормуОтчетаНаКлиенте`	`РезультатОткрытияФормыНаСервере = "Отчет не найден"`

5. Posting and movements

The РегламентированныйОтчет document does not generate postings. It stores reporting data and does not make movements in accounting registers.

Postings based on declaration indicators are generated by the associated document ОтражениеНалоговойОтчетностиВРеглУчете, a link to which is stored in the ДокументОтраженияВУчете attribute (scenario 3.5).

Typical postings generated by the reflection document (RK chart of accounts, 2026 rates):

Business transaction	Dr	Cr	Comment
Accrual of VAT payable per the return (FNO 300.00)	3130	3130/settlements with budget	VAT at the rate of 16% (not 12%). Example: sale of 1,000,000 ₸ → VAT 160,000 ₸.
Accrual of IIT at the source of payment	settlements with personnel	3120	IIT 10% up to 8,500 MCI of annual income, 15% above. The deduction of 30 MCI/month is taken into account (no more than 360 MCI/year).
Accrual of social tax	7210	3150	Social tax 6%.
Accrual of liabilities for social payments	7210/3350	3210–3240	OPV 10% (base cap — 50 MMW = 4,250,000 ₸), OPVR 3.5%, VOSMS 2%, OSMS 3%, SO 5%.

Reference values of the RK for 2026: MCI = 4,325 ₸, MMW = 85,000 ₸, VAT rate — 16%, basic IIT tax deduction — 30 MCI per month (≤ 360 MCI per year).

Example of IIT deduction per month: 30 × 4,325 = 129,750 ₸.

The specific corresponding settlements-with-budget account (subaccounts to 3110–3190) depends on the type of tax and accounting settings — it is determined by the reflection document, not by the report itself.

6. Related objects and entry on the basis

Object	Relation
`Документ.ОтражениеНалоговойОтчетностиВРеглУчете`	Main related object: generates postings based on declaration data; stored in `ДокументОтраженияВУчете`. Usually entered on the basis of the report (scenario 3.5).
Electronic documents ESF (IS ESF)	Electronic invoices — source of data for the VAT return (FNO 300.00).
Electronic documents SNT	Accompanying waybills for goods — data on goods turnover.
Accounting registers/documents (sales, receipt, payroll)	Source of indicators when auto-filling regulated forms.
Versioning mechanism	Tracking report changes between edits (scenario 3.2).
Electronic signature (EDS) mechanism	Signing the report before sending it to the tax committee (scenario 3.4).

Work scenarios (from evidence):

3.1 Creating a new report — at the beginning of the reporting period/when the submission deadline arrives.
3.2 Opening and editing an existing report — before submission, for corrections and clarifications.
3.3 Filtering reports by type and period — finding the required document.
3.4 Signing the report before submission — after the final check.
3.5 Reflection of tax reporting in regulated accounting — creating postings based on declaration data.

7. Extension points

Extension of the list form/report form — adding your own filters, commands, additional checks without removing the configuration from support.
Event subscriptions (ПриЗаписи, ПередЗаписью) of the document — for integration with external systems (e.g., export to SGDS/taxpayer's cabinet) or additional control.
Additional attributes and information (properties mechanism) — for storing internal document flow attributes.
Interception of ОткрытьФормуОтчетаНаКлиенте — for custom handling of access rights and logging of report openings.
Extension of the reflection logic — refinement of ОтражениеНалоговойОтчетностиВРеглУчете for non-standard tax accounting methodology.

When making refinements, keep in mind that business data is stored in serialized form (ХранилищеЗначения) — direct modification of the report's data structure without the standard configuration mechanisms may disrupt the reading of forms.