Report "Analysis of Inventory Balances in the Virtual Warehouse Considering Reserves" (Accounting for Kazakhstan 3.0.74.2)

1. Identification of the Object

Purpose. The report analyzes the current balances of goods in the virtual (managerial) warehouse, taking into account reserved quantities. It shows the actual free balance of goods — what is available for shipment after deducting reserves for customer orders. It is used by warehouse staff, sales managers, and executives for daily monitoring of inventory availability, planning shipments, and making decisions about the feasibility of fulfilling new orders.

Where to find in 1C. Section "Sales" → "Analysis of goods balances in the virtual warehouse with reserve accounting". Direct access — via the navigation link above.

Important: this is a report, not a document. It is not processed, does not generate postings or movements in registers. Below, in section 5, the registers that the report reads as data sources are described.

2. Attributes, Table Parts, and Forms

2.1 Header Attributes

The object does not have its own header attributes. The report is built on DCS, so all selection parameters and output settings are specified through the settings compiler, not through fixed attributes of the object.

The actual control parameters of the report are set as DCS parameters and selections (standard set for the report on balances):

2.2 Table Parts

The object has no table parts. The result is dynamically generated by the data composition processor and displayed in a tabular document. The logical composition of output fields is standard for the report on balances with reserves:

• Product (and characteristic/series, if accounting is maintained);
• Warehouse;
• Balance (quantity in stock);
• In reserve (reserved quantity);
• Free balance = Balance − In reserve;
• if necessary — unit of measurement, total valuation of the balance.

2.3 Forms

The metadata list of forms is empty. The report uses the automatically generated main report form based on DCS: settings panel (quick selections, period), table document field for the result, and standard commands "Generate", "Settings", "Select variant". No separate custom forms have been added by the developer.

3. Forms — List and Purpose

The platform automatically creates additional forms (settings forms, variant forms) from the composition scheme as needed; there are no custom forms in the object.

4. Key Procedures of Modules

The provided evidence does not include the original BSL code and paths to module lines. There are no custom attributes, table parts, and forms — all logic is encapsulated in the data composition scheme. Therefore, below are standard handlers typical for reports on DCS of this type; there are no specific user procedures in the object, judging by the structure.

Requires verification in the specific build 3.0.74.2: the presence of the overridden OnResultComposition in the object module — in the basic delivery of reports of this type it is usually not overridden, and composition goes through the standard DCS mechanism.

5. Data Sources (Registers) — Instead of Postings and Movements

The report is not processed and does not create movements. It reads data from the accumulation registers of the configuration. For analyzing balances with reserves, the warehouse contour registers are used (standard logic of "Accounting for Kazakhstan" 3.0):

The free balance is calculated in the DCS data set as the difference between the actual balance and the sum of reserves on the report date. The virtual warehouse means that accounting is maintained in quantitative (managerial) terms, without mandatory binding to accounting postings of a specific warehouse.

Connection with Accounting (for reference, for data reconciliation). The movement of the goods themselves, which forms the balances, is reflected in the configuration documents according to the standard chart of accounts of the RK:

• 1330 "Goods" — cost of inventory;
• 6010 "Revenue from Sales" and 7010 "Cost of Sales" — upon shipment;
• 3130 "VAT Payable" — outgoing VAT at the rate of 16% (current rate of the RK for 2026);
• 1210 "Short-term Receivables from Customers", 3310 "Payables to Suppliers", 1030 "Cash in Current Accounts" — settlements.

The report itself does not make these postings — it only shows quantitative balances and reserves.

6. Related Objects and Input on Basis

The report (unlike a document) does not have input commands on the basis and is not a basis for other objects. It is logically related to:

• source registers — goods balances in warehouses and reserves for customer orders;
• documents that generate these movements: receipt of goods and services, sale of goods and services, customer order (creates a reserve), transfer and adjustment of reserves;
• reference books: "Products", "Product Characteristics"/"Series" (if accounting is maintained), "Warehouses", "Organizations" — used as dimensions for selection and grouping;
• electronic documents of the RK (indirectly, through shipment): ESF (IS ESF) and SCT are formed by sales documents that affect balances, but not by the report itself.

7. Extension Points

Since the object is entirely built on DCS and does not contain its own code/forms, it is most convenient to extend it using the composition tools and the configuration extension mechanism:

1. User DCS Settings — adding selections (by product group, manager), groupings, conditional formatting (highlighting negative free balance), saving report variants.
2. Configuration Extension — adding a new data set or calculated field to the composition scheme (for example, "Expected Receipt", "Days to Shortage"), without changing the main delivery.
3. Handler OnResultComposition in the object module (via extension) — post-processing/formulation of the tabular document before output.
4. Additional Report Variants — storing alternative composition settings (for example, "by warehouses" and "by managers") without modifying the code.
5. Roles and Rights — managing access to the report through the rights subsystem; the report participates in the team interface of the "Sales" section.

Requires verification in the specific build 3.0.74.2: exact names of source registers and the internal name of the main data set of DCS — they are version-dependent and clarified through the configurator/composition scheme of this report.