Document “КонтрольДублированияТоваровНаВиртуальныхСкладах” — Technical Description (Accounting for Kazakhstan 3.0.74.2)

Important Note on the Object Type

The task and navigation link classify the object as a Document (Документ.КонтрольДублированияТоваровНаВиртуальныхСкладах). However, the attached metadata dump (evidence) describes an object with the characteristics of a DCS-based report: empty collections of custom attributes, tabular sections, and forms, and the presence of the system attributes СхемаКомпоновкиДанных and КомпоновщикНастроек.

This discrepancy is typical of service objects used for data control: the analysis mechanism itself is implemented through the DCS/query rather than through register movements. The description below is based on the evidence where available and on the standard logic of objects of this type where evidence is absent. The actual object type in the specific build must be verified in Designer (metadata tree → “Documents” or “Reports” branch).

1. Identification

Purpose. A service object for identifying and monitoring duplicate product records (inventory items) in virtual warehouses. In the Republic of Kazakhstan, the concept of a “virtual warehouse” is associated with the “Virtual Warehouse” module of the Electronic Invoice Information System (EIIS) and the issuance of ACNs (accompanying consignment notes for goods): balances of traceable goods are maintained by EAEU CN/GTIN codes and must match government system data. Duplicate items lead to discrepancies in virtual warehouse balances, errors when issuing EIs/ACNs, and incorrect inventory accounting in account 1330 “Goods”.

The object is used by warehouse personnel, accountants, and auditors during periodic reconciliations and when balance discrepancies are detected.

Where to find it in 1C: navigation link e1cib/list/Документ.КонтрольДублированияТоваровНаВиртуальныхСкладах. By purpose, it belongs to the “Inventory Items and Warehouse” section.

2. Header Attributes and Tabular Sections

According to the evidence, custom attributes and tabular sections are not defined—the result structure is generated dynamically by the Data Composition System.

2.1 System attributes (provided by the platform)

If the object in the specific build is nevertheless a document, the expected minimum set of header attributes consists of the standard Номер, Дата, Организация, Ответственный, and Комментарий attributes (must be verified against the build metadata).

2.2 Tabular sections

Not defined (tabular_sections is empty). The tabular selection of duplicates is generated dynamically by the DCS.

3. Forms

Custom forms are not listed in the metadata (forms is empty). A universal form generated automatically by the platform is used (a DCS-based report form or a list/document form), providing:

• a settings panel (filters, groupings);

• a result area containing the list of duplicate items;

• a command bar (generate/refresh, settings, print).

Separate list, selection, and object forms are not specified in the evidence.

4. Key Module Procedures

The BSL code is not attached to the evidence, so standard handlers for objects of this type are listed below.

If the object is a DCS-based report (according to the evidence):

• ПриКомпоновкеРезультата(ДокументРезультат, ДанныеРасшифровки, СтандартнаяОбработка) — report object module: intercepting output, post-processing the result, and highlighting duplicates.

• ПриСозданииНаСервере / ПриОткрытии — form module: initializing settings and setting the period and organization filter.

• The duplicate-search logic is contained in the DCS data-set queries (grouping inventory items by code/variant/warehouse with the condition КОЛИЧЕСТВО(...) > 1).

If the object is a document:

• ОбработкаПроведения(Отказ, РежимПроведения) — object module: for a control document, it is generally empty or does not generate register movements.

• ОбработкаЗаполнения(ДанныеЗаполнения, ТекстЗаполнения, СтандартнаяОбработка) — filling when created on the basis of another document.

• ОбработкаПроверкиЗаполнения(Отказ, ПроверяемыеРеквизиты) — validating attributes before recording.

• ПередЗаписью(Отказ, РежимЗаписи, РежимПроведения) — service validations.

The specific procedure names and contents must be verified against the object module in build 3.0.74.2.

5. Posting and Register Movements

By purpose, this is a control and analytical object: it identifies duplicates but does not generate accounting entries or accumulation-register movements. This is consistent with the evidence (a DCS structure without tabular sections or recorder mechanisms).

Therefore:

• Dr/Cr entries are not generated;

• balance/turnover register movements are not generated.

The object only reads inventory accounting data and virtual warehouse data. The goods it monitors are recorded in the principal accounts under account 1330 “Goods” of the standard chart of accounts of the Republic of Kazakhstan; related business transactions involving goods use the following accounts:

If the object in the build turns out to be a document with register movements, the set of registers must be verified; however, movements are not typical of “duplicate control.”

6. Related Objects and Creation on the Basis of Another Document

Conceptually, the object relies on the goods traceability subsystem of the Republic of Kazakhstan:

• EIIS virtual warehouse registers/data — the source of balances by EAEU CN/GTIN codes.

• ACN (accompanying consignment note for goods) — a document recording movements of goods in the virtual warehouse; duplicate inventory items distort ACN issuance.

• EI (electronic invoice, EIIS) — uses virtual warehouse balances; the VAT rate in its attributes is 16%.

• “Inventory Items” catalog — the control object (matching by name, EAEU CN code, and variant).

• Inventory receipt/sales documents — generate balances in account 1330.

Creation on the basis of another document is generally not provided for the control object (must be verified against the composition of the “Create on the Basis” criteria). The result is used as the basis for manually correcting/merging duplicate inventory item records.

7. Extension Points

• Configuration extensions (Extensions): adding custom data sets/fields to the DCS, refining the duplicate-search query (accounting for GTINs, serial numbers, and variants), and borrowing the form for additional filters.

• Form event handlers (ПриСозданииНаСервере, ПриКомпоновкеРезультата) — custom highlighting/grouping of duplicates and export.

• Additional reports and data processors (Standard Subsystems Library) — if necessary, connect an external control option without modifying the standard configuration.

• Comparison criteria — move the rules for identifying a “duplicate” into a setting (information register/constant) for flexible adjustment to the accounting policy.

• Integration with the EIIS — reconcile identified duplicates with virtual warehouse balances before issuing EIs/ACNs.

All extension points are implemented through the configuration extension mechanism without removing the standard configuration from support.

Frequently Asked Questions (FAQ)

Why is the object called a document even though it has no tabular sections or forms?

In this case, the duplicate control mechanism is implemented using the Data Composition System (DCS). The object uses dynamic queries to identify discrepancies and output the result rather than storing static data. Therefore, the tabular-section structure is empty, while forms are generated automatically by the 1C platform based on the DCS settings.

Does this object generate accounting entries or register movements?

No. It is solely a service control and analytical tool. It does not generate accumulation-register movements or accounting entries (for example, in account 1330 “Goods”); it only reads and compares existing data.

What are the consequences of duplicate inventory items in the Virtual Warehouse?

Duplicate items distort balances by EAEU CN/GTIN codes between the 1C accounting system and the government EIIS. This blocks or causes errors when issuing Accompanying Consignment Notes for Goods (ACNs) and Electronic Invoices (EIs).

How can the duplicate-search logic be adapted to the company’s specific requirements?

The enhancement is implemented through the configuration extension mechanism (Extensions) without removing the standard database from support. A developer can intercept the data composition schema and add new search criteria to the query (for example, strict matching by GTIN, serial numbers, or additional attributes)

Author’s Conclusion

The КонтрольДублированияТоваровНаВиртуальныхСкладах object is an architectural hybrid: although formally listed as a document (or service data processor) in navigation, it technically functions as a DCS-based report. This tool is critically important for accounting in Kazakhstan because desynchronization of the Inventory Items catalog with the government “Virtual Warehouse” module brings goods shipments and the issuance of ACNs/EIs to a halt. Regular use of this object allows accountants and auditors to keep account 1330 clean and tax accounting accurate (including VAT calculations at the rate of 16% from 2026), while the absence of hard-coded forms and tabular sections makes it easy to scale through standard 1C extensions.

Sources

• Metadata dump (evidence) for the КонтрольДублированияТоваровНаВиртуальныхСкладах object.

• Standard “1C:Accounting for Kazakhstan” configuration, edition 3.0 (version 3.0.74.2).

• Rules for maintaining accounting records and issuing source documents in the Republic of Kazakhstan (regarding the use of account 1330 and inventory control).

• Operating procedures for the “Virtual Warehouse” module of the EIIS and rules for issuing accompanying consignment notes for goods (ACNs).