Report "Results of Accounting Audit" (Reports.Results of Accounting Audit)

1. Identification

Purpose. A specialized report for controlling the quality of accounting. Used by accountants, chief accountants, and controllers to analyze the results of automatic data checks for compliance with built-in accounting rules. The report is generated based on the results of the accounting control subsystem and shows identified issues, their criticality, and possible solutions (correction options).

Called from the context of the reference book AccountingCheckRules — this is not a standalone report in the report panel, but a tool for detailing the results of a specific verification rule. The frequency of use is determined by the organization's inspection regulations: usually weekly or before closing the reporting period (for example, before issuing electronic invoices (ESF) in the ESF information system, generating VAT returns, or calculating VAT liabilities at a rate of 16%).

Where to find in 1C: section “Standard subsystems” → “Results of accounting check”; or directly from the form of the reference book “Accounting check rules”.

2. Header attributes and table parts

2.1 Header attributes

The object does not contain user-defined attributes in the metadata. All report settings are managed through data composition parameters and user settings of the DCS.

The actual parameterization is performed through DCS parameters (for example, selection by a specific verification rule, organization, and period). These parameters are not attributes of the metadata object and are stored in the composition settings.

2.2 Table parts

Table parts are absent. The report belongs to objects of the type “Report”; data is generated dynamically through the DCS mechanism at the composition stage, rather than being stored in attributes or table parts.

3. Forms

• AutoCorrectionIssues — a form for automatically resolving identified accounting issues (31 control elements, 3 pages). Contains buttons “FixIssue”, “Close”, and “HelpForm”. This is a key form for interactive error correction: the user selects a correction option, and the system makes adjustments to related documents/accounting data.
• Main report form (form of the results list) is not explicitly described in the metadata — an automatically generated form with extensions through the report object module is used.

4. Key module procedures

The attached evidence lacks BSL code with exact paths and lines, so below is a typical composition of handlers for this type of object — confidently based on platform and configuration practice.

Report object module (DCS):

• OnResultComposition(DocumentResult, DataDecoding, StandardProcessing) — interception of composition: substitution of data from accounting check results, formatting cells by problem criticality (error/warning/information), generating hyperlinks for decoding to problematic objects.
• SettingsForAutomatedTestingTechnology() / service export procedures for DCS settings — if present in the object.

Form module “AutoCorrectionIssues”:

• OnCreateOnServer(Error, StandardProcessing) — form initialization: reading the problem description, filling pages (steps) with correction options, setting visibility of elements.
• FixIssue(Command) → server procedure (FixIssueOnServer()) — execution of the selected correction scenario: adjustment of the problematic object's data, rewriting/reprocessing affected documents, updating the problem status.
• HelpForm(Command) — calling help for the type of identified problem.
• Close(Command) — closing the form without changes.

Requires verification (version-specific): the exact list of module procedures and the presence of a user-defined main form are clarified through the configurator version 3.0.74.2 — the composition may differ between releases of the accounting control subsystem.

5. Posting and movements

The report is not a document and does not generate movements in registers and does not create postings — an object of the type “Report” has no posting mechanism.

The practical role of the report is to identify violations of correspondence and balances in the accounts of the standard chart of accounts of the RK and suggest corrections. Changes in accounting are made by the form “AutoCorrectionIssues” indirectly — through reprocessing/correction of related documents that already generate movements in the accounting register.

Typical issues diagnosed by the report and affected accounts of the chart of accounts of the RK:

When correcting tax issues, the system relies on RK norms of 2026: VAT 16%; when controlling payroll and individual income tax (IIT) — basic deduction 30 MRP per month (not more than 360 MRP per year) at MRP = 4,325 ₸ and MZP = 85,000 ₸, IIT 10% up to 8,500 MRP of annual income and 15% above; contributions and deductions — OPE 10% (base cap 50 MZP), OPEA 3.5%, VOSMS 2%, OSMS 3%, SO 5%, social tax 6%. All amounts are in tenge (₸).

6. Related objects and input on the basis

• Reference book AccountingCheckRules — main “parent”: the report is called from its form and details the results of a specific rule.
• Accounting control subsystem (register(s) of check results) — data source for DCS.
• Problematic accounting objects — sales/purchase documents, payment documents, payroll and tax documents, which are referenced by decodings and corrected by the auto-correction form.
• Electronic documents of the RK — ESF (ESF information system) and VAT returns: checks of VAT data reconciliation and goods movement form part of the identified issues.

Input on the basis for the report is not provided (uncharacteristic for objects of the type “Report”). Interaction goes in the opposite direction: from the result of the check — transition (decoding) to the problematic document and its correction.

7. Extension points

• DCS settings / report options — user settings, selections, conditional formatting by criticality; saving options through the standard mechanism.
• Configuration extension (Extension) — adding handlers OnResultComposition, overriding the form “AutoCorrectionIssues”, adding custom correction scenarios.
• Custom check rules — extending the reference book AccountingCheckRules with new rules, the results of which will be detailed by this same report.
• Event subscriptions / common modules of the accounting control subsystem — embedding in the regulation of automatic checks before closing the period.
• BSL mechanisms — integration with the “Standard subsystems” subsystem (help, settings, access rights to check results).