RUKKENZH
Задать вопрос AI
SectionsОбъекты конфигурации 1С
Documents. Inventory Turnover - Technical Description (Accounting for Kazakhstan 3.0.74.2)
Язык статьи:🇷🇺 RU🇰🇿 KK🇬🇧 EN🇨🇳 ZH

Documents. Inventory Turnover - Technical Description (Accounting for Kazakhstan 3.0.74.2)

Applies to: 1С:Бухгалтерия для Казахстана, release 3.0.74.2 · by 1C-Sapa Group, 1C partner
СТ
Сапа Т.И. — Эксперт по 1С и бухгалтерскому учёту, преподаватель-практик

1. Identification

Parameter Value
Full Name Document.TurnoverOfGoods (navigation: e1cib/list/Document.TurnoverOfGoods)
Metadata Type (by META) Document
Actual Nature of the Object Analytical tool — calculation of turnover indicators of inventory
Synonym not specified (—)
Configuration Accounting for Kazakhstan, edition 3.0, version 3.0.74.2
Currency of Indicators tenge (₸)

Purpose. The object is intended for analyzing the speed of turnover and the efficiency of using inventory. It calculates key indicators: turnover ratio, turnover period (in days), average balance, and actual consumption (outflow) for the selected period. It is used by accountants, economists, and management for controlling the movement of goods, assessing the liquidity of stocks, and identifying non-liquid assets. It is generated regularly (weekly, monthly, quarterly) to meet the needs of management accounting.

Where to find in 1C: section “For the Manager” → “Turnover of Goods”.

Important (metadata discrepancy). By the META field, the object is registered as Document, however, its attribute composition (analysis period, indicator flags, table part “Grouping”, calculation base, placement of fields) is the composition of settings for an analytical report, not a primary document. Accordingly, the object is not a posted document: it does not have the attributes “Number”/“Posting Date” in the usual sense and does not generate accounting entries and movements in registers (see section 5). Below, the description is based on the actual attribute structure from evidence. It requires verification in a specific build: the type of the root object (Document vs Report) is a version-specific detail of the platform.


2. Attributes and Table Parts

2.1 Header Attributes

Name Type Mandatory Purpose
StartPeriod xs:dateTime DontCheck Start date of the analyzed period; base for calculating balances and turnover
EndPeriod xs:dateTime DontCheck End date of the analyzed period; together with the start defines the range of all calculations
Organization CatalogRef.Organizations DontCheck Organization for which the report is generated; when multiple selections are made — through list representation
ListRepresentationOfOrganizations xs:string DontCheck Text representation of selected organizations for the header
ListRepresentationOfDepartments xs:string DontCheck Text representation of selected departments for filter and header
DetailingMode xs:boolean DontCheck Detailing flag: True — reveals analytics by clicking on the row
IndicatorSum xs:boolean DontCheck Include sum indicators (turnovers and balances in tenge ₸)
IndicatorQuantity xs:boolean DontCheck Include quantitative indicators (pieces, liters, etc.)
TurnoverPeriod xs:boolean DontCheck Display turnover period in days (average time from receipt to outflow)
TurnoverRatio xs:boolean DontCheck Display turnover ratio (number of turnovers for the period)
ChangeOfLastPeriod xs:boolean DontCheck Compare with the corresponding period of the previous year and display deviation
CalculationBase xs:string DontCheck Method for calculating average balance (arithmetic mean / weighted average)
PlacementOfAdditionalFields xs:decimal DontCheck Method of placement of additional fields (in rows / in columns)

2.2 Table Parts

Grouping — defines the hierarchy and detail of data (for example: Organization → Warehouse → Nomenclature).

Name Type Purpose
Usage xs:boolean Activity flag of grouping: True — the field participates in the report structure
Field xs:string Technical name of the field (“Organization”, “Warehouse”, “Nomenclature”)
Representation xs:string User-friendly name of the field for headers

In addition to “Grouping”, typical table parts for objects of this class are Selection (filtering conditions by nomenclature/warehouse/characteristic) and AdditionalFields (output of additional attributes of nomenclature). In the attached evidence, they are not detailed — please clarify the composition in a specific build.


3. Forms

The list of forms is not attached in evidence. For objects of this class, the typical set of forms is:

Form Purpose
SettingsForm / DocumentForm Main form: selection of period (StartPeriod/EndPeriod), organization and departments, setting indicator flags (IndicatorSum, IndicatorQuantity, TurnoverPeriod, TurnoverRatio, ChangeOfLastPeriod), selection of calculation base and grouping structure
ListForm List of saved settings/instances (opens at e1cib/list/Document.TurnoverOfGoods)
ResultForm (tabular document) Area for outputting the generated report with detailing (DetailingMode)

4. Key Procedures of Modules

BSL-evidence is not attached. For objects of this class, typical handlers are:

  • OnCreateOnServer — initialization of default settings: period (current month), organization from constants/session parameters, indicator flags, filling the “Grouping” structure with the standard hierarchy (Organization → Warehouse → Nomenclature).
  • Generate (command) → GenerateOnServer — building a query to inventory registers, calculating average balance, turnover, ratio, and turnover period, outputting to a tabular document; if ChangeOfLastPeriod = True — a second pass through the last year's range and calculation of deviations.
  • Flag Handlers (IndicatorSumOnChange, IndicatorQuantityOnChange, etc.) — managing visibility/composition of output columns.
  • GroupingUsageOnChange — restructuring the report structure when levels are turned on/off.
  • DetailProcessing — detailing the row when DetailingMode = True.

Specific paths path:string cannot be provided — modular evidence is absent.


5. Posting and Movements

The object does not generate accounting entries and movements in accumulation/information registers. It works “in read mode”: aggregates already posted inventory data and calculates analytical indicators. Accordingly, the section on postings is not applicable to it in the classical sense.

Data Sources (reading):

  • accumulation register of inventory accounting in warehouses (balances and turnovers in quantity);
  • accounting register “Cost Accounting” for inventory and cost accounts.

Typical chart of accounts of the RK involved as a source for calculations:

Account Role in Calculation
1330 “Goods” Balances for average balance; turnovers on debit — receipt
7010 “Cost of Sales” Outflow turnover (expense) in monetary terms
6010 “Revenue from Sales” Reference — for comparison with turnover (when additional fields are used)

Logic of Indicator Calculation:

Average balance            = f(balances on 1330 for the period, CalculationBase)
Turnover (expense)         = credit turnover 1330 / turnover 7010 for the period
Turnover ratio             = Turnover (expense) / Average balance
Turnover period, days      = Number of days in the period / Turnover ratio

Example (tenge, ₸). For a month (30 days): average balance of goods = 1,200,000 ₸, cost of outflow (turnover on 7010) = 3,600,000 ₸.

  • Turnover ratio = 3,600,000 / 1,200,000 = 3 turnovers.
  • Turnover period = 30 / 3 = 10 days.

Sum indicators are output in accounting valuation (cost), excluding VAT; the VAT rate of the RK (16% in 2026) does not affect the turnover calculation.


  • Directory “Organizations” — attribute Organization (CatalogRef.Organizations).
  • Directory “Departments / Warehouses” — source of values for grouping and filtering.
  • Directory “Nomenclature” — basic measurement of analysis (lowest level of grouping).
  • Primary documents of inventory movement (Receipt of Inventory and Services, Sale of Inventory and Services, Transfer) — data providers to registers from which the object reads turnovers and balances.

Input based on for this object is not provided: as an analytical tool, it is a data receiver, not a source for creating other documents. Reverse input based on (from invoices → to this object) is also not applied.


7. Extension Points

  • Configuration Extension: adding new levels/fields of grouping, additional indicators (for example, turnover in days by weighted average), alternative methodology CalculationBase.
  • Selection and Query Parameters: implementation through the form/module manager — expanding conditions by characteristics, series, managers.
  • External processing / additional reports: connecting an analogue through the mechanism of additional reports and processing without changing the typical configuration.
  • Formatting the result: refining the layout of the tabular document (conditional formatting of non-liquid assets — rows with a ratio below the threshold).

Electronic documents of the RK (ESF in IS ESF, SNT) are not directly related to this object — it does not participate in electronic document flow, but only analyzes the results of already posted operations.

Частые вопросы

Is this a document or a report?
According to the META field, the object is registered as a "Document," but its requisites (analysis period, indicator flags, "Grouping" table part, calculation base) are settings of an analytical report. In fact, the object functions as a report: it does not conduct or generate entries but reads inventory accounting data and calculates turnover indicators. Please clarify the type of the root object in the specific assembly.
What entries does "GoodsTurnover" generate?
None. The object does not create movements in registers or entries. It reads balances and turnovers for account 1330 "Goods" and cost of goods sold for 7010 "Cost of Sales," after which it calculates the average balance, coefficient, and turnover period.
How is the coefficient and turnover period calculated?
Coefficient = Turnover (expense) / Average balance. Period (in days) = Number of days in the period / Coefficient. Example: average balance 1,200,000 ₸, cost of goods sold over 30 days 3,600,000 ₸ → coefficient 3, period 10 days. Amounts are taken at accounting value excluding VAT.
Does the VAT rate of 16% affect the indicators?
No. Turnover is calculated based on accounting cost and balances of inventory items, so the VAT rate of the RK (16% from 2026) does not affect the calculation and is not included in the indicators.
Can other documents be entered based on this object?
No. This is an analytical data receiver, not a primary document, so entry based on it (in both directions) is not provided.

Read also

Источники

Была ли статья полезна?
💼 Нужна помощь с 1С или учётом? Слава КВЦ — многолетняя практика в 1С в Казахстане. Изучите разложенный НК РК 2026 или спросите в чате BuhGPT — ответит за секунды.