Document "Notification of Withdrawal from Circulation of Electronic Invoices" - Technical Description (Accounting for Kazakhstan 3.0.74.2)

1. Identification of the Object

Purpose. The document is intended for registering and transmitting notifications of the withdrawal of labeled goods from circulation in the territory of the Republic of Kazakhstan to the state information system ESDM (Centralized Electronic Document Management for Labeling). It is used by participants in the circulation of labeled products (retail chains, pharmacies, distributors) to record the fact of destruction, damage, sale to the end consumer, or other disposal of goods with applied labeling codes.

The document is part of the integration subsystem with the ESDM Information System and provides bidirectional exchange: creating notifications in 1C with subsequent sending to ESDM and receiving processing statuses. By its nature, this is an informational (integrational) document — it does not reflect economic transactions in accounting but only registers and synchronizes the statuses of labeling codes. The actual disposal of goods, income, and cost are reflected in primary documents (supporting documents).

Where to find in 1C: section "Nomenclature and Warehouse" → "Notification of Withdrawal from Circulation (ESDM)".

2. Attributes of the Header and Table Parts

2.1 Attributes of the Header

Mandatory attributes for processing (if not filled, 1C does not process the document and gives an error "Field ... is not filled"):

Other header attributes characteristic of this type of document:

2.2 Table Parts

Products / Labeling Codes — the main table part with a list of codes withdrawn from circulation (GTIN, labeling code, packaging/aggregate indicator). Supports a hierarchical structure of the "product tree" for aggregates (group and transport packages).

Typical Errors — a service table part for storing validation messages and responses from ESDM:

3. Forms

4. Key Module Procedures

Evidence with exact paths path:string by modules is not attached. Below are typical handlers for the integration document of this type; actual procedure names should be clarified in the specific assembly.

Object Module:

• ProcessingFilling(BasisFilling, …) — filling in supplier attributes and labeling code tree when entering based on the sale/write-off document.
• ProcessingCheckFilling(Refusal, CheckedAttributes) — control of mandatory attributes (Supplier, SupplierName, SupplierIdentificationNumber) and non-empty list of codes.
• ProcessingConducting(Refusal, ConductingMode) — in the standard delivery, the document does not contain the formation of movements in accounting/accumulation registers (see section 5). Registration of code statuses is performed upon receipt of a response from ESDM.

Document Form Module:

• Commands SendToESDM / UpdateStatus — serialization of the package, calling the ESDM Information System web service, parsing the response, filling in the status and the "Typical Errors" table part.
• LoadCodesFromTSD / LoadFromFile — importing labeling codes from a scanner/data collection terminal or from a file.
• ExportToExcel — exporting codes for reconciliation with regulatory authorities.
• WhenChangingProductTree — supporting the hierarchy of aggregates.

The key application logic (exchange with ESDM, parsing statuses) is concentrated in the common modules of the ESDM integration subsystem, not in the document module itself.

5. Conducting and Movements

The document does not contain ProcessingConducting in terms of accounting movements and does not generate entries in the accounting register, nor movements in accumulation registers. This is an informational document intended solely for data exchange with an external system (ESDM). The actual write-off of goods and reflection of sales are performed by primary documents (supporting documents).

Upon successful sending and receiving the status "Accepted" from ESDM, the document registers movements in the information register "LabelingCodeStatusesInESDM":

This is necessary for controlling the reuse of labeling codes and building reports on the movement of labeled products.

How Withdrawal is Reflected in Accounting (Reference, Supporting Documents)

The accounting result is not created by this notification, but by the primary document. For Kazakhstan 2026 (VAT rate 16%, typical chart of accounts of the RK) typical entries of the primary document:

• Sale to the end consumer:
  • Debit 1210 "Short-term Receivables from Buyers" — Credit 6010 "Revenue from Sales" (for the amount of income);
  • Debit 1210 — Credit 3130 "VAT Payable" (VAT 16% of taxable turnover);
  • Debit 7010 "Cost of Sales" — Credit 1330 "Goods" (write-off of cost);
  • upon payment: Debit 1030 "Cash in Current Accounts" — Credit 1210.
• Destruction/Damage (withdrawal without sale):
  • Debit of other expenses account — Credit 1330 "Goods" (write-off of the cost of the disposed goods).

Electronic documents for the operation (ESF in the ESDM Information System and if necessary SNT) are generated separately from the ESDM notification.

Example of VAT calculation: with a taxable turnover of 1,000,000 ₸ the VAT amount = 160,000 ₸ (16%), to be reflected in Credit 3130.

6. Related Objects and Input Based on

Input Based On (Scenario 3.1). The notification is created based on primary documents for the withdrawal of labeled products:

• sale documents (retail/wholesale sale, pharmacy sale);
• write-off documents / acts of damage and destruction;
• return and inventory documents (when using TSD, scenario 3.6).

Related Objects:

• Information register "LabelingCodeStatusesInESDM" — receiver of movements and source for controlling the reuse of codes.
• Subsystem ESDM Information System (exchange web services, service common modules for sending/receiving statuses).
• Directories Counterparties/Organizations (supplier), Nomenclature (GTIN, labeling codes).
• Adjacent subsystems of electronic document management — ESF (ESF Information System) and SNT — for processing accompanying tax and supporting documents.

Typical Operation Scenarios: creation based on sales (3.1), sending to ESDM (3.2), updating status (3.3), manual input of codes through the product tree (3.4), correcting a rejected document (3.5), loading codes from TSD (3.6), exporting to Excel for reconciliation (3.7).

7. Extension Points

• Configuration Extension (form/module adapters): adding custom attributes to the product tree, additional validation of codes before sending, batch processing buttons — through extending the document form module without removing from support.
• Handler ProcessingCheckFilling: implementation of additional checks (GTIN compliance, control of duplicate codes by the register "LabelingCodeStatusesInESDM").
• Event Subscriptions (EventSubscription) on document record/conducting events — for automating sending to ESDM or logging exchanges.
• Common modules of the ESDM subsystem: overridable methods for forming exchange packages and parsing responses (if *Overridable modules are present in the delivery).
• Additional reports/processings: external reports on the register "LabelingCodeStatusesInESDM", processing of bulk loading of codes from TSD/Excel.

Version-specific (requires verification in the specific assembly 3.0.74.2): exact composition of measurements/resources of the register "LabelingCodeStatusesInESDM", presence of overridable common modules of the ESDM subsystem and exact names of sending/updating status commands.