Report “Statement of Goods in Warehouses at Item Prices” (Trade Management for Kazakhstan 3.4.5.21)

1. Identification

Purpose. The report generates a warehouse statement of goods movements for a period, broken down by warehouse and item: it shows the opening balance, receipts, issues, and closing balance in both quantitative and monetary terms—at item prices (accounting prices from the “Item Prices” information register). Its primary use is to monitor inventory balances and turnover, reconcile warehouse records, and value inventory at accounting prices. The report is analytical (read-only): it does not post documents or generate register movements.

All monetary examples below are stated in tenge (₸) in accordance with Kazakhstan’s 2026 regulations.

2. Parameters and settings (equivalent to “attributes”)

Because this is a DCS-based report, data composition parameters, user settings, and selection fields are used instead of header attributes and tabular sections.

2.1. Report parameters

2.2. Selection fields (resources and dimensions)

2.3. Standard user settings

• Filters by organization, warehouse, item, characteristic, and price type.
• Groupings (for example: Warehouse → Item → Characteristic).
• Conditional formatting (highlighting negative balances).
• Selection of the report variant and appearance.

3. Forms

As a rule, custom forms are not created for a DCS-based report—the main report form generated by the platform is used.

If a custom managed form is included in a particular delivery, its parameters override the automatically generated ones, but the field set corresponds to the table in section 2.

4. Key module procedures

The attached evidence contains only the “purpose” facet; the source BSL code of the report modules is not attached. The following are typical handlers for a DCS-based report in 1C configurations (their actual names and availability depend on the delivery).

Report object module:

• ПриКомпоновкеРезультата(ДокументРезультат, ДанныеРасшифровки, СтандартнаяОбработка) — intercepting output: programmatic generation or post-processing of the composition layout (for example, additional formatting of negative balances or substitution of accounting prices). When СтандартнаяОбработка = Ложь is set, the report is composed entirely by code.
• НастройкиДляТехническогоСпециалиста() / schema override—dynamic modification of the composition schema before output.

Report form module:

• ПриСозданииНаСервере(Отказ, СтандартнаяОбработка) — initializes settings, sets the default period, and restricts available warehouses according to permissions.
• ПриОткрытии — restores the most recently selected parameters.
• ОбработкаПользовательскогоЗапросаНастроек / filter handlers—respond to changes in the period, warehouse, or price type.

Requires verification for the specific version: the availability and exact signatures of the ПриКомпоновкеРезультата procedures, because they are version-specific and the standard report may rely exclusively on a declarative DCS schema without program code.

5. Data sources (registers) instead of movements

The report does not generate movements or accounting entries—it reads them. DCS sources:

Link to the RK chart of accounts. The “Goods in Warehouses” register corresponds to inventory accounting under account 1330 “Goods”. The movement of goods shown in the statement corresponds to the standard entries generated by recorder documents (the report itself does not make entries):

• Receipt of goods: Dr 1330 — Cr 3310 (amount payable to supplier); input VAT Dr 1420 — Cr 3310.
• Sale: cost of sales Dr 7010 “Cost of Sales” — Cr 1330; revenue Dr 1210 “Short-term Trade Receivables” — Cr 6010 “Revenue from Sales”; VAT at the rate of 16%—Cr 3130 “VAT Payable”; payment—Dr 1030 “Cash in Current Bank Accounts” — Cr 1210.

Thus, the monetary closing balance in the statement must reconcile with the balance of account 1330 if the accounting prices match.

6. Related objects and creation based on

The report is a read-only object and therefore does not support “creation based on.” The following are functionally related:

• Recorder documents of the “Goods in Warehouses” register: “Purchase of Goods and Services,” “Sale of Goods and Services,” “Transfer of Goods,” “Receipt/Write-off of Goods,” and “Assembly (Disassembly) of Goods.”
• Catalogs: “Items,” “Item Characteristics,” “Warehouses” (enterprise structure), “Organizations,” and “Price Types.”
• “Item Prices” information register—source of accounting prices.
• Electronic document flow in the RK: the goods movements shown in the statement are accompanied by the issuance of ESFs (ESF IS) and SNTs for sales/receipt documents; the report itself does not create these documents, but the goods movement data serves as the basis for reconciliation with issued ESFs/SNTs.

7. Extension points

• Custom report variants (DCS): adding groupings, filters, fields, and conditional formatting without modifying the configuration; saving them as separate variants.
• Configuration extension: adding a ПриКомпоновкеРезультата handler or overriding the composition schema for non-standard monetary valuation (for example, valuation at a fixed price instead of the item price).
• Additional item attributes/information as filter and grouping fields in the composition schema.
• Integration with the cash flow budget/accounting: using statement data to reconcile the balance of account 1330 and verify the accuracy of cost of sales (7010).
• Access permissions (RLS): restricting the visibility of warehouses/organizations through access group profiles—automatically filters the report selection.

Requires verification for 3.4.5.21: the exact set of predefined report variants and the availability of extensible module procedures depend on the version and enabled functional options (characteristic accounting, lot accounting, multiple organizations).