Report “Statement of Transferred Returnable Packaging” (Trade Management for Kazakhstan 3.4.5.21)

1. Identification

Purpose. The report generates a statement of settlements for returnable (deposit) packaging transferred to customers and not returned by them. It shows the opening packaging balances held by counterparties, transfer and return turnover for the period, and closing balances, broken down by counterparties, contracts, packaging items and, where necessary, recorder documents. The report is a tool for monitoring packaging held by customers and serves as a basis for collecting the deposit or demanding the return of the packaging.

In Trade Management, returnable packaging is accounted for separately from goods: its transfer is not a sale and does not generate income; instead, it is recorded in the transferred packaging accounting register. The report reads this particular accounting ledger rather than sales turnover.

Where to find it

• Navigation panel: Warehouse and Delivery section (or Sales → packaging reports group).
• Direct access: e1cib/list/Отчет.ВедомостьПоПереданнойВозвратнойТаре.
• Via All Reports → search for “packaging”.

2. Attributes and data structure

The report has no attributes or tabular sections in the sense applicable to a document. Its “structure” is defined by the main data composition schema (ОсновнаяСхемаКомпоновкиДанных) and report variants (settings). The standard composition is provided below.

2.1. Report parameters (settings form header)

2.2. Fields (available for output)

Packaging is valued at its deposit (carrying) value; as a rule, VAT is not charged on returnable packaging transactions until the packaging is recognized as unreturned and reclassified as a sale. If such reclassification occurs, the effective VAT rate of 16 % applies (Republic of Kazakhstan, 2026).

3. Forms

Custom forms are generally not created for DCS reports; the platform’s automatically generated report form is used. The standard composition is as follows:

As a rule, the standard distribution contains no custom managed forms for the object; all logic is encapsulated in the DCS and the object module.

4. Key module procedures

Evidence from the BSL code for this object is not attached (only the naznachenie facet is available). The following are standard DCS report handlers for Trade Management 3.4 / Standard Subsystems Library configurations. The specific procedure names may differ in version 3.4.5.21, and this must be verified in Designer.

Report object module:

• ПриКомпоновкеРезультата(ДокументРезультат, ДанныеРасшифровки, СтандартнаяОбработка) — output interception: programmatic fine-tuning of the layout, substitution of calculated fields and formatting.
• НастройкаПараметровВыполнения(...) / ПриОпределенииНастроек(Настройки) (Standard Subsystems Library) — registration of variants, setting functional options and restricting available fields.
• ПередВыполнениемКомпоновкиДанных(...) — presetting period/organization parameter values before execution.

Report form module:

• ПриСозданииНаСервере(Отказ, СтандартнаяОбработка) — initialization of default parameters (current organization, period—the current month).
• ПриОткрытии(Отказ) — restoration of user settings.
• <Параметр>ПриИзменении(...) — interdependent filters (for example, selecting a counterparty clears/resets the contract).

DCS data source — a query to the accumulation register used to account for transferred returnable packaging (the ОстаткиИОбороты virtual tables), joined to the item, counterparty and contract catalogs.

5. Data generation, registers and accounts

The report is not posted and does not generate movements—it is a read-only facility. It aggregates data from the accumulation register to which packaging dispatch/return documents write movements.

Source register (standard):

• “Transferred Returnable Packaging” accumulation register (balances)—receipt when packaging is transferred to a customer and expense when it is returned. The report uses its ОстаткиИОбороты virtual table.

Documents generating movements (recorders):

• Sale of Goods and Services / Goods Issue Note—for the packaging transfer portion.
• Return of Goods from Customer / packaging return documents—for the packaging receipt portion.

Correspondence with the chart of accounts of the Republic of Kazakhstan (2026), if packaging transactions are recorded in statutory accounting:

Accounts are not used in the report itself; amounts are displayed based on the packaging register valuation (deposit value, ₸). The entries above relate to recorder documents and are provided to explain the accounting ledger.

6. Related objects and create based on

As a report, the object does not participate in the “create based on” mechanism (either as a source or a destination). Related objects:

• Accumulation register for transferred returnable packaging accounting—the main data source.
• Recorder documents: Sale of Goods and Services, Goods Issue/Goods Receipt Note, Return of Goods from Customer (details down to the recorder and drill-down).
• Catalogs: Organizations, Counterparties, Partners, CounterpartyContracts, Items, Warehouses, Currencies.
• Electronic documents: when unreturned packaging is reclassified as a sale, an Electronic Invoice (EI) is generated in the Electronic Invoice Information System and, where necessary, a Goods Accompanying Note (GAN); the report itself does not generate them but helps identify the volume of such packaging.

Drill-down is available from report cells (double-click) to the recorder document and to item/counterparty cards.

7. Extension points

• Report variants—creating user-defined variants (by counterparty, by item, only with a non-zero closing balance) without modifying the configuration.
• Configuration extension—adding a custom DCS schema or variants through a report extension object; overriding ПриОпределенииНастроек / ПриКомпоновкеРезультата.
• External report—connecting an equivalent as an additional report through the “Additional Reports and Data Processors” subsystem (Standard Subsystems Library), assigned to the “Warehouse and Delivery” / “Sales” sections.
• Functional options—report visibility is controlled by the option for using returnable packaging; when the option is disabled, the report is hidden from the interface.
• DCS conditional appearance and user-defined fields—highlighting overdue unreturned packaging and calculated fields (for example, the deposit amount to be collected).

Version-specific (verification required in 3.4.5.21): the exact name of the source register, the composition of predefined variants and the signatures of object module handlers. All of these must be confirmed in Designer for the specific distribution.