Reports. Regulated Report 701 Form - Form 701.00 "Vehicle Tax" (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. The report generates a tax declaration on the state form 701.00 of the Republic of Kazakhstan (vehicle tax). It is used by accountants and tax specialists for periodic (usually quarterly) reporting to the tax authorities of the RK. The report allows data to be filled in automatically from accounting records or manually, exported to XML for electronic submission, and printed on paper forms.

Where to find in 1C: section “Reports” → “Regulated Reporting” → group of tax reporting of the RK → “Form 701.00”. Navigation link: e1cib/list/Report.RegulatedReport701Form.

Important: this is an object of type Report, not a document. It is not processed and does not generate movements in registers and postings — see section 5.

2. Attributes and Structure

2.1 Header Attributes

The mandatory DontCheck is typical for regulated reports: control of filling is performed by internal form validation procedures (the “Check” button), not by the platform mechanism.

2.2 Table Parts

In the metadata of the object, table parts are not defined. The rows of the declaration (list of vehicles, tax amounts by objects) are stored in the internal structures of the form and transmitted through printing/export parameters. This is the standard architecture of regulated reports: the layout of the form and its row composition are stored in layouts and form data, not in the object's attributes.

2.3 Amounts Used in Filling (RK, 2026)

Values relevant for calculations when generating reports for RK for the year 2026:

• MPR = 4,325 ₸
• MZP = 85,000 ₸
• Currency of the report — tenge (₸)

Vehicle tax rates are set in MPR depending on engine capacity / carrying capacity / type of vehicle and are taken from built-in tables of the form edition as of the date of relevance. The values of MPR/MZP, as well as the rates of other taxes in the configuration (VAT 16%, PIT 10%/15% with a basic deduction of 30 MPR per month and no more than 360 MPR per year, OPE 10%, OPEI 3.5%, VOSMS 2%, OSMS 3%, CO 5%, social tax 6%) for the year 2026 are stored in general registers/constants of the configuration and used by other subsystems; only MPR directly affects form 701.00. Requires verification: specific vehicle tax rates by vehicle categories in the current edition — they are version-dependent and updated with the form.

3. Forms

The object contains 14 forms — one for each edition of the form (for correct filling of declarations for previous periods) plus service forms:

The form selection mechanism: MainForm determines the active edition for the selected period and opens the corresponding form Form701…. Forms from previous years are preserved to allow for correct generation and printing of declarations for closed periods.

4. Key Module Procedures

Evidence with BSL sources for the object is not attached, so below is the typical composition of handlers for the regulated report of this type in the RK. Verify specific procedure names in the configurator.

Form module (Form701…Qn):

• OnCreateOnServer — initialization: reading attributes of the taxpayer/tax committee, setting the period, configuring field availability and the printed table of the form.
• FillReport / Fill (the “Fill” command) — gathering accounting data on the organization's vehicles for the period and calculating tax amounts by the rows of the form.
• CheckFilling (the “Check” command) — control of mandatory attributes and logical verification of indicators before export/printing.
• Print / PreparePrintForm — generating a tabular document according to the layout of the state form.
• ExportToFile / GenerateXML — serializing indicators into XML of the established tax return form format for loading into SONO/Taxpayer's Cabinet.
• DetailIndicator — opening FormDetailing for a specific cell/row of the report.

Object module / manager module:

• Procedures for determining the current edition by date (GetFormNameByPeriod and analogs).
• Procedures for setting the composition of indicators and rounding parameters (UnitOfMeasurement, PrecisionOfUnitOfMeasurement).

Regulated reports in the typical BK 3.0 largely rely on the general mechanisms of the regulated reporting subsystem (common filling, verification, export modules), so part of the logic is not in the object itself, but in the common modules of the subsystem.

5. Processing and Movements

The object is a report and is not processed. It does not generate movements in accumulation/summary registers and does not create accounting postings. Accordingly, there are no account correspondences for the report itself.

When auto-filling, the report reads data from the organization's accounting:

• information about taxable objects (vehicles) — from directories/registers of fixed assets accounting and tax accounting for vehicle tax;
• attributes of the organization and tax authority — from directories Organizations and Counterparties.

The accrual and payment of the vehicle tax itself are reflected by separate documents of the configuration (regulated operations / manually entered operations) and use the typical chart of accounts of the RK, for example:

• accrual of tax: Debit of expense/tax account — Credit 3130 (tax liabilities, corresponding sub-account for vehicle tax);
• payment from the current account: Debit 3130 — Credit 1030 (“Money in current bank accounts”).

The report 701.00 only aggregates and presents this data in the form of a declaration; it does not affect the balances and turnovers of accounts.

6. Related Objects and Input Based On

• Directory Organizations — source of taxpayer attributes.
• Directory Counterparties — tax authority recipient (TaxCommittee).
• Enumeration RoundingRules — units of measurement/rounding of amounts.
• Accounting of fixed assets and tax accounting for vehicles — source of declaration rows.
• Regulated reporting subsystem of the RK — common mechanisms for filling, verification, and XML export; journal/list of regulated reports, where generated instances are stored.
• Electronic documents of the RK (IS ESF, SNT) — not directly related to form 701.00 (pertaining to the turnover of invoices and accompanying documents), but part of the overall electronic interaction framework of the configuration.

Input based on is not applied for regulated reports — the report instance is created from the list of regulated reporting by selecting the period and taxpayer.

7. Extension Points

• Configuration extension: borrowing forms Form701…Qn and MainForm with overriding handlers FillReport, CheckFilling, Print to add custom checks or additional attributes without removing from support.
• Object manager module: redefinition of procedures for selecting the edition by period and logic of auto-filling.
• Common modules of the regulated reporting subsystem: points for fine-tuning filling rules and XML export (consider during updates — version-dependent).
• Form layouts: adjustment of printed forms for custom requirements (with caution — overridden by form updates).
• Updating rates/MPR: values of MPR (4,325 ₸) and rates by vehicle categories for the new period come with the configuration update; when manually adjusting, use mechanisms of constants/registers, not hard coding in the form.

Requires verification (version-specific): exact names of auto-filling and export procedures in 3.0.74.2, as well as the composition of rows of the current edition Form7012025Q1 — verify in the configurator of the specific delivery.