Document "Report on Transfer of Property from Non-Resident to RK ISCEDM" (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. The document is intended for the formation and transmission of reports on the movement of marked goods (identification codes, IC) from non-residents of the Republic of Kazakhstan to the Information System of Digital Electronic Documents and Marking (IS CEDM). It is used by participants in the turnover of marked products when importing goods to record the fact of transferring IC from the non-resident supplier to the resident importer of the RK.

The document supports two directions of exchange:

• incoming reports — receiving information about the transfer of IC from a non-resident (including synchronization from CEDM when the report is created by the non-resident directly);
• outgoing reports — transferring marked goods to the importer (another resident of the RK).

The document is an informational (registration) element of the integration subsystem with the IS MPT (marking of goods) and does not generate movements in accounting/tax records (see section 5). It is used daily in import operations with marked products.

Where to find in 1C:

• Section "Sales" → "Report on Transfer of IC to Importer (IS CEDM)";
• integration subsystem commands with IS MPT "Reports on Transfer of IC to Importer (incoming/outgoing) (IS CEDM)";
• navigation link: e1cib/list/Document.ReportOnTransferOfIdentificationCodesFromNonResidentRKISCEDM.

2. Header Attributes and Table Parts

2.1 Mandatory Header Attributes (by evidence)

If any of the listed fields are not filled, 1C will not allow the document to be processed and will display an error message such as "Field ... is not filled".

In addition to the listed ones, the document typically contains standard attributes: Number, Date, Organization, as well as service attributes of the exchange state (document identifier in CEDM, status of sending/receiving, direction "incoming/outgoing").

2.2 Table Part "Identification Codes" (Goods Part)

The main table part contains a list of transmitted IC and the product nomenclature. Typical composition: nomenclature, marking code (GTIN/full code), unit of measurement, quantity. Filling is possible manually, from CEDM, and through a mobile application/TSD (see scenario 3.4).

2.3 Table Part "Typical Errors" (Technical)

Serves to store error messages during exchange with CEDM.

3. Forms

4. Key Procedures of Modules

No separate BSL-evidence for this object is attached, so below are typical handlers for documents integrating with IS MPT/CEDM of this configuration.

Object Module:

• ProcessHandling(Refusal, ProcessingMode) — does not perform actual movements (the document is informational); if necessary, registers a record in service registers of integration with IS MPT through overridable modules.
• CheckFilling(Refusal, CheckedAttributes) — control of filling mandatory header fields (Supplier, SupplierName, SupplierIdentificationNumber, Recipient, RecipientName, RecipientIdentificationNumber).
• FillErrors(...) / methods for filling the table part "Typical Errors" — receiving validation results from CEDM and recording messages in the table part.

Form Module:

• Commands "Send to CEDM", "Receive/synchronize from CEDM" — calling exchange services with IS CEDM.
• Handlers for loading codes from a mobile application/TSD.
• Rendering the exchange status and formatting rows of the table part of errors.

Overridable modules of IS MPT integration — all accounting of marking codes and updating specialized registers of IS MPT are performed here (see section 7).

5. Processing and Movements

The document does not generate accounting entries and does not create movements in accounting registers. This is an informational registration document for integration with IS CEDM. Accounting for marking codes is maintained in specialized registers of IS MPT, the update of which occurs through overridable integration modules, not through the typical ProcessHandling.

Accordingly, for this document the accounts of the typical RK plan are not involved — sale of goods and its cost (6010 "Revenue from Sales", 7010 "Cost of Sales"), settlements (1210 Accounts Receivable, 3310 Accounts Payable), VAT at the rate of 16% (3130 "VAT Payable"), cash (1030) and goods (1330) are reflected by other documents of goods movement and cash settlements.

Financial/tax consequences of the import operation (including VAT at the rate of 16%, accounting for goods on account 1330, settlements with the supplier on 3310) are documented by related documents of receipt/sale and electronic invoices (ESF), while this document only records the movement of identification codes in CEDM.

6. Related Objects and Input on Basis

• Electronic documents of the RK: ESF (IS ESF), SNT — accompany the import/turnover of marked goods and are related to it by product part and counterparties.
• Documents of goods movement: receipt of goods (import), sale of goods/services — sources of nomenclature and IC.
• Counterparties/Organizations — sources of attributes of the non-resident supplier and resident recipient.
• Registers and exchange IS MPT/CEDM — service objects of the integration subsystem with which the document exchanges data.
• Mobile application/TSD — source of marking codes during collection in the warehouse (scenario 3.4).

Input on basis is implemented within the integration subsystem: the document can be created from documents of the turnover of marked products and synchronized directly from CEDM.

Typical application scenarios:

1. Creating an incoming report on the transfer of IC from a non-resident (receiving marked goods from a foreign supplier registered in CEDM).
2. Synchronizing the incoming report from CEDM (the non-resident created the report directly, without initiation from 1C).
3. Creating an outgoing report on the transfer of IC to the importer (transferring marked goods to another resident of the RK).
4. Editing marking codes through a mobile application/TSD (collecting codes in the warehouse).
5. Handling errors when sending to CEDM (validation and recording in the table part "Typical Errors").

7. Extension Points

• Overridable modules of IS MPT integration — the main mechanism for customization: the logic of updating marking code registers and rules for exchange with CEDM are moved to overridable procedures.
• Configuration extensions — adding handlers Before…/After… on document and list forms, supplementing filling checks.
• Event subscriptions — if necessary, respond to the recording/processing of the document for integration tasks.
• Table part "Typical Errors" — a point of extension for diagnostics: the logic of parsing the response from CEDM can be supplemented for more detailed routing of errors by fields.

Version-specific (requires verification for 3.0.74.2): the exact composition of service registers of IS MPT and signatures of specific overridable integration procedures may change between releases — verify with the composition of configuration objects.