1. Identification
| Parameter | Value |
|---|---|
| Object Type | Report (Report) |
| Name | TaxAccountingRegisterByInventoryTurnover |
| Full Name | Report.TaxAccountingRegisterByInventoryTurnover |
| Alias | — (not set) |
| Configuration | Accounting for Kazakhstan, edition 3.0.74.2 |
| Mechanism Basis | Data Composition System (DCS) |
Purpose. The report generates a tax register for the balances and turnover of inventory (raw materials, materials, goods, other stocks) for tax accounting purposes in the Republic of Kazakhstan, primarily for preparing VAT data. It operates in two modes:
- “TaxRegister” — a formalized register with the taxpayer's header filled in (for submission to tax authorities / storage as part of tax registers).
- “CustomReport” — analytical mode for internal analysis of inventory turnover and balances without formalization.
It is usually generated quarterly or at the request of tax authorities.
Where to find in 1C. Section of the accounting subsystem of Accounting for Kazakhstan → “Tax accounting register by inventory turnover”. Navigation link: e1cib/list/Report.TaxAccountingRegisterByInventoryTurnover.
2. Attributes and Table Parts
2.1 Attributes (report parameters)
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| StartPeriod | xs:dateTime | DontCheck | Start date of the reporting period (usually the first day of the month/quarter) |
| EndPeriod | xs:dateTime | DontCheck | End date of the reporting period (last day of the month/quarter) |
| Frequency | xs:decimal | DontCheck | Indicator of the frequency of formation (month / quarter / year) |
| OrganizationListRepresentation | xs:string | DontCheck | Text representation of selected organizations when multiple selections are made |
| DepartmentListRepresentation | xs:string | DontCheck | Text representation of selected departments for analytics |
| AdditionalFieldsPlacement | xs:decimal | DontCheck | Method of placing additional fields (horizontally / vertically) |
| DetailingMode | xs:boolean | DontCheck | Indicator of detailing mode: suppresses header output and uses detailing parameters |
| Taxpayer | CatalogRef.Organizations | ShowError | Mandatory attribute — the organization for which the tax register is generated |
| ReportType | xs:string | DontCheck | Operating mode: “TaxRegister” or “CustomReport” |
The only strictly controlled attribute is Taxpayer (
ShowError): without specifying the organization, the formalized register will not be built. Other parameters haveDontChecksince they are filled automatically from the composition settings or are not required in the custom mode.
2.2 Table Parts
Grouping
Manages the structure of data groupings in the report (detail by nomenclature, warehouses, accounts, etc.).
| Name | Type | Purpose |
|---|---|---|
| Usage | xs:boolean | Flag for including grouping in the report structure |
| Field | xs:string | Internal name of the DCS field (e.g., “Nomenclature”, “Warehouse”) |
| Representation | xs:string | User display of the grouping name in settings |
| GroupingType | EnumRef.StandardReportDetailingTypes | Method of grouping: grouping / detailed records / hierarchy |
AdditionalFields
Adding additional columns to the report (valuation method, subaccount, analytics).
| Name | Type | Purpose |
|---|---|---|
| Usage | xs:boolean | Flag for displaying the field in the final report |
| Field | xs:string | Internal name of the DCS field (e.g., “ValuationMethod”, “Subaccount1”) |
| Representation | xs:string | Displayed name of the column in the report |
3. Forms
The standard report in DCS is characterized by a minimal set of forms:
| Form | Purpose |
|---|---|
Main report form (MainSettingsForm / report form) |
Unified form for inputting parameters and outputting results: selection of period, taxpayer, mode (ReportType), setting up groupings and additional fields, “Generate” button, area of the tabular document with results and detailing mechanism |
Separate settings/forms in the standard delivery are usually not highlighted — management of the structure is done through the table parts “Grouping” and “AdditionalFields” and the standard composition settings constructor. The exact list of forms in a specific assembly requires verification in the configurator (version-dependent).
4. Key Module Procedures
Evidence for BSL modules related to this object is not provided, so below are typical report handlers in DCS for this type of object (Accounting for Kazakhstan).
OnResultComposition(ReportResult, DetailingData, StandardProcessing)(report module) — intercepts output: substitutes the header of the tax register (attributesTaxpayer, period), manages header output inDetailingMode, formats the tax form.OnSettingsComposition(Form)/DefaultSettings— initializes composition settings, fills in the period and groupings by default, pre-sets the modeReportType.- Handler for mode selection (
ReportTypeOnChange) on the form — switches between “TaxRegister” and “CustomReport”: shows/hides the taxpayer block, changes the layout. - Filling composition parameters before generation — transferring attribute values (
StartPeriod,EndPeriod,Frequency, list of organizations/departments) toSettingsComposer.Settings.DataParameters. - Detailing processing (
DetailingProcessing) — transitions to detailed records / documents-registers of inventory turnover.
Specific paths
module:stringshould be clarified in the configurator of the target assembly 3.0.74.2 — evidence not provided.
5. Data Sources, Accounts, and Movements
Important: the object is a report and, unlike a document, does not post and does not generate movements in registers (neither accounting entries nor records in accumulation/summary registers). It only reads already formed data.
The data sources of the report are accounting totals and turnovers for inventory accounts and related sales accounts of the standard chart of accounts of the RK:
| Account | Purpose in the context of inventory turnover |
|---|---|
| 1330 | Goods (main account for balances and turnover of inventory) |
| 1210 | Short-term receivables from customers |
| 1030 | Cash on current bank accounts |
| 3310 | Short-term payables to suppliers |
| 3130 | VAT payable (on sales) |
| 6010 | Revenue from sales of goods (works, services) |
| 7010 | Cost of goods sold |
Typical correspondence that falls into inventory turnover, which the register reflects:
- Receipt of goods: Dr 1330 Cr 3310, VAT on acquisition — separately.
- Sale (recognition of income): Dr 1210 Cr 6010 and Dr 1210 Cr 3130 for the amount of VAT.
- Write-off of cost: Dr 7010 Cr 1330.
- Payment by the customer: Dr 1030 Cr 1210.
The calculation of VAT in the register is conducted at a rate of 16% (the current VAT rate in Kazakhstan for 2026). Amounts are reflected in tenge (₸).
The electronic support for inventory turnover is implemented by related mechanisms of the configuration — ESF (electronic invoice, ESF IS) and SNT (accompanying invoice for goods); this report uses their data as primary but does not issue them itself.
6. Related Objects and Input on Basis
As a report, the object does not participate in the “input on basis” mechanism (it is neither a basis nor a result). Functionally related to the following configuration objects:
- Directory “Organizations” — attribute
Taxpayer(mandatory selection). - Directory “Nomenclature”, “Warehouses (storage locations)”, “Departments” — analytics of groupings.
- Inventory and sales accounting accounts (1330, 1210, 1030, 3310, 3130, 6010, 7010) — sources of accounting totals.
- Documents of inventory movements (receipt/sale of inventory, ESF, SNT) — registrars to which detailing leads.
- Enumeration
StandardReportDetailingTypes— type of elements in the table part “Grouping”.
7. Extension Points
- DCS Settings / report variants — adding user-defined groupings, selections, and fields without changing the configuration; saving user-defined variants.
- Table parts “Grouping” and “AdditionalFields” — standard mechanism for extending the output structure (additional subaccounts, valuation method).
- Configuration extension (Extensions) — overriding/adding handlers
OnResultComposition,OnSettingsComposition, adding form attributes. - Mode
ReportType— switching between formalized register and custom analysis as an embedded point of customization behavior. - Detailing mechanism — redefining transitions to primary documents (ESF/SNT) during customization.
Changes in accounts, rates, and settings are best made through accounting policy parameters and composition settings, rather than hardcoding in the module, to maintain the updatability of the standard configuration.