Report "Universal Tax Accounting Register" - Technical Description (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. A flexible analytical report for viewing data from tax accounting registers for any period. Designed for accountants and tax specialists to analyze the state of tax registers, verify the accuracy of tax calculations, audit, and prepare tax reporting for the RK with the ability to detail (break down) down to primary documents.

The key feature is universality: the report is not tied to a specific register. Through the parameters RegisterName / TableName, it is dynamically configured for any of the tax accounting registers in the configuration, which is why it is most often called not from the general list of reports, but from the context menu of the register itself.

Where to find in 1C: section “Reports” → “Tax Accounting” → “Universal tax accounting register”, or by using the opening command from the form of the corresponding tax accounting register.

2. Attributes and Table Parts

2.1 Attributes (DCS settings parameters)

Since the object is a report, the “header attributes” are implemented as data composition parameters available in the form and in the DCS settings.

2.2 Table Parts

No table parts. The result is displayed using DCS as a tabular document. Rows, groupings, resources, and totals are dynamically formed by the composition scheme based on the structure of the selected register (RegisterName).

3. Forms

There are no separate settings/report variant forms in the object — the standard DCS settings panel is used within ReportForm.

4. Key Module Procedures

Evidence for BSL modules (specific path:string) is not attached. Below is a typical set of handlers for the report in DCS in BK 3.0; verify actual names and availability in the configurator.

Object module of the report (ObjectModule):

• OnResultComposition(DocResult, DataDetailing, StandardProcessing) — intercepting composition: substituting RegisterName/TableName in the scheme, programmatically generating the data source for the selected register, adjusting the composition layout before output.
• OnSettingsSelectionComposition / SetDefaultParameters — initializing period, organization, detailing mode.

Form module (ReportForm):

• OnCreateOnServer(Failure, StandardProcessing) — filling in default parameters (Taxpayer = main organization, period = current), setting field visibility.
• OnOpen — adjusting the command interface, restoring saved settings.
• Result field handlers (Result…Processing, …DetailingClick) — navigation through detailing to primary documents when DetailingMode = True.
• <Attribute>OnChange for period/taxpayer — reformation of the report or cache reset.

General logic: the report reads data from the tax accounting register table, limiting the selection by organization (Taxpayer), period, and, if available, subdivisions; output and totals are handled by DCS.

5. Posting and Movements

The report is not a document — it is not posted and does not generate movements in registers, nor does it create accounting entries. This is a “read-only” object.

Data source — records from the tax accounting registers of the BK 3.0 configuration (accumulation/summary tax accounting registers), selected through the RegisterName parameter. The report merely visualizes data already formed by other documents.

For context, below are typical accounts of the RK (Chart of accounts of RK), the data of which are matched with tax registers during analysis:

Numerical norms of RK 2026, involved in tax registers analyzed by the report:

• VAT — 16 %.
• MPR — 4,325 ₸; MSP — 85,000 ₸.
• Individual income tax: basic tax deduction — 30 MPR/month (no more than 360 MPR per year); rate 10 % up to 8,500 MPR annual income and 15 % above.
• OPV — 10 % (base ceiling 50 MSP), OPVR — 3.5 %, VOSMS — 2 %, OSMS — 3 %, CO — 5 %, social tax — 6 %.
• Accounting currency — tenge (₸).

Example: when selling for 1,160,000 ₸ with VAT, the income register lines will show income of 1,000,000 ₸ (account 6010) and VAT of 160,000 ₸ (account 3130), which the report will display in the context of the selected tax register.

6. Related Objects and Input Based On

• Input based on is not supported (the object is a report).
• Tax accounting registers — the main related objects (sources); the report is opened via a command from the form of the specific register.
• Reference “Organizations” — mandatory parameter Taxpayer.
• Reference of subdivisions (structural units) — selection through ListOfStructuralUnitsRepresentation.
• Primary documents — available through the DCS detailing mechanism (DetailingMode).
• Electronic documents of the RK (ESF through IS ESF, SNT) are indirectly related: the data of sales/receipts reflected in them enter the tax registers that the report visualizes.

7. Extension Points

• Configuration extensions: adding your own report variants, additional selections, and parameters through intercepting OnResultComposition; adding form attributes and handlers in ReportForm.
• User DCS settings: saving variants (selections, groupings, conditional formatting) without changing the configuration.
• Additional reports (external): connecting through the BSP subsystem “Additional reports and processing” as an alternative to modifying the standard.
• New registers: since the report is universal, an added tax accounting register in the extension can be output by passing its RegisterName/TableName.
• Roles and rights (RLS): restricting access to data by organization at the role level.

Requires verification (version-specific): exact names of module procedures and the complete list of supported registers in build 3.0.74.2 — check in the configurator, as the composition of tax registers changes between releases.