--- title: "Document \"Notification of Import from Third Countries and Electronic Document Management\" - Technical Description" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/dokument-uvedomlenieovvozeiztretihstraniscedm-tehnichesko-en source: BuhGPT --- # Document "Notification of Import from Third Countries and Electronic Document Management" - Technical Description > **TL;DR:** 1. Identification Parameter Value Object Type Document ( Documents ) Name NotificationOfImportFromThirdCountriesInISCEDM Full Name Document.NotificationOfImportFromThirdCountriesInISCEDM Synonym “Notification of the import of marked products (import) (IS CEDM)” Configuration A --- 1. Identification Parameter Value Object Type Document (Documents) Name NotificationOfImportFromThirdCountriesInISCEDM Full Name Document.NotificationOfImportFromThirdCountriesInISCEDM Synonym “Notification of the import of marked products (import) (IS CEDM)” Configuration Accounting for Kazakhstan, ed. 3.0 (version 3.0.74.2) Task Class Electronic document management with IS CEDM (marking) Purpose. The document registers and transmits to the Integrated System for Control of Export-Import Marking Documents (IS CEDM) information about the import of marked goods from third countries into the territory of the Republic of Kazakhstan. It is used by importers and customs declarants when processing the import of products subject to mandatory marking. The document is created based on customs declarations or other primary import documents, filled with marking codes (GTIN, KIZ, transport/group packaging codes), and sent to IS CEDM for legal import registration. After successful submission and receipt of confirmation, the document receives a status and registration number in IS CEDM, which legalizes the marked products at the recipient's warehouse. Where to find in 1C. Section “1C Service: Marking (IS CEDM)” → “Notification of the import of marked products (import) (IS CEDM)”. Navigation link: e1cib/list/Document.NotificationOfImportFromThirdCountriesInISCEDM This is an information exchange document. It does not directly affect accounting and inventory management — monetary and inventory operations for imports are processed by separate documents (customs declaration for import, receipt of goods). 2. Header Attributes and Table Parts 2.1 Header Attributes Mandatory attributes for processing (if not filled, 1C does not process the document and gives an error “Field … is not filled”): Attribute Purpose DeleteSupplier Reference to the supplier counterparty (third country). Marked as deprecated (prefix Delete) — kept for compatibility. DeleteSupplierName Text name of the supplier for transmission to IS CEDM. DeleteSupplierIdentificationNumber Identification number of the supplier (foreign equivalent of BIN/IIN). Recipient Organization/counterparty-receiver of the imported products. RecipientName Name of the recipient for export. RecipientIdentificationNumber BIN/IIN of the recipient. Attributes with the prefix Delete — are legacy service attributes of the exchange scheme. In new releases, supplier data is filled through current fields, but old ones are retained in the object structure. Requires verification of the compliance of the set of received fields with the specific version of the XSD schema of IS CEDM. Additionally, the header typically contains service attributes of the exchange: document status in IS CEDM, registration number, date/time of sending and receiving a response, reference to the underlying document (customs declaration/receipt). 2.2 Table Parts Table Part Purpose Goods / Totals Rows of marked products: GTIN, nomenclature, quantity, price/amount, VAT rate. The VAT rate for imports in 2026 is 16% (account for VAT on import — 1420 “VAT to be refunded”, to be paid — 3130). Marking Codes (KIZ) Individual identification codes, codes for group and transport packaging. Tree of Marked Products Hierarchy of packaging: transport → group → consumer; used for visual control of nesting and quantity. Typical Errors (service table part) Storage of validation errors and responses from IS CEDM. Fields: Text (xs:string — text of the error message), Field (xs:string — name of the field to which the error relates). 3. Forms Form Purpose Main Document Form Specialized form with the tree of marked products and table parts for goods and marking codes. Buttons for submission to IS CEDM, status update, loading codes from a file, filling prices based on the underlying document. List Form Journal of notifications with columns for IS CEDM status, registration number, recipient, date. Selection Form Document selection when entering based on / in related exchange processes. 4. Key Module Procedures In the attached evidence, the original BSL code (path:string) is not provided, therefore below are typical handlers for the exchange document of IS CEDM for this configuration. Specific procedure names require verification against the object module version 3.0.74.2. Object Module: - ProcessingFilling(FillingData, …) — filling the header and goods when entering based on the customs declaration/receipt (scenario 3.1). - ProcessingCheckFilling(Refusal, CheckedAttributes) — control of mandatory fields (Recipient, identification numbers) and correctness of marking codes before recording. - ProcessingConducting — missing. The document does not generate movements (see section 5). Form Module / Manager Module: - SendToISCEDM() — serialization to XML according to the XSD schema and calling the web service of IS CEDM (scenario 3.2). Results/errors are written to the service table part “Typical Errors”. - UpdateStatusFromISCEDM() — request for the current status of the notification processing by the system (scenario 3.3). - LoadMarkingCodesFromFile() — import KIZ from Excel/text files from the scanner (scenario 3.4). - FillPricesBasedOnDocument() — setting prices in the totals table based on the primary receipt document (scenario 3.5). - GenerateProductTree() / tree handlers — building and controlling the hierarchy of packaging (scenario 3.6). 5. Conducting and Movements The document does not have a handler ProcessingConducting and does not generate movements in the registers (neither accounting nor accumulation). This is an information exchange document with the external system IS CEDM; it does not directly affect accounting and inventory management. Accordingly, this document does not create any entries in the typical chart of accounts of the RK. The actual accounting of imports is reflected by accompanying documents of the configuration, for reference — typical import scheme from third countries (VAT rate 16%, currency — tenge ₸): Operation Debit Credit Receipt of imported goods 1330 “Goods” 3310 “Payables to suppliers” VAT on import to be paid 1420 “VAT to be refunded” 3130 “VAT to be paid” Payment to supplier 3310 1030 “Cash in current accounts” Further sale 1210 / 7010 6010 / 1330 These entries generate other documents (customs declaration for import, receipt of goods, sale). The notification to IS CEDM only legalizes the marking codes for these goods. 6. Related Objects and Entry Based On Entry based on (the document is created based on): - Customs declaration for goods / customs declaration for import — main scenario (3.1); - Receipt document (Receipt of goods and services) — for filling goods and prices (3.5). Related Objects: - Other electronic marking documents of IS CEDM (SNT, notifications on turnover/removal); - Nomenclature directory with GTIN/marking code attributes; - Registers of information storage of marking codes and their statuses; - Electronic invoice (ESF) (IS ESF) and SNT — accompany legalized products in further circulation. 7. Extension Points - Event subscriptions BeforeRecording / OnRecording of the document — for additional validation of marking codes or logging of exchanges. - Configuration extension: adding header/table part attributes, overriding sending procedures (SendToISCEDM) through &Instead/&After. - XSD serialization handlers — adaptation to the updated IS CEDM schema (relevance of the field structure requires verification when changing the schema version). - Loading codes — external processing/rules for parsing scanner files for the procedure LoadMarkingCodesFromFile. - Service table part “Typical Errors” — integration point with monitoring/notification mechanisms for exchange failures. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_