--- title: "Document \"Notification of Shipment EAEU ISMPTK\" - Technical Description" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/dokument-uvedomlenieobotgruzkeeaesismptk-tehnicheskoe-opi-en source: BuhGPT --- # Document "Notification of Shipment EAEU ISMPTK" - Technical Description > **TL;DR:** 1. Identification Parameter Value Object Type Document (Documents) Name NotificationOfShipmentEAESESMPTK Full Name Document.NotificationOfShipmentEAESESMPTK Synonym Notification of goods shipment (EAEU) (IS MPT) Configuration Accounting for Kazakhstan, edition 3.0 (3.0.74.2) O --- 1. Identification Parameter Value Object Type Document (Documents) Name NotificationOfShipmentEAESESMPTK Full Name Document.NotificationOfShipmentEAESESMPTK Synonym Notification of goods shipment (EAEU) (IS MPT) Configuration Accounting for Kazakhstan, edition 3.0 (3.0.74.2) Object Class Integration document (exchange with IS MPT), without movements in registers Purpose. The document is intended for accounting notifications of the shipment of marked goods within the Eurasian Economic Union (EAEU) through the information system for monitoring the movement of goods in Kazakhstan (IS MPT). It is used by participants in the turnover of marked products for cross-border supplies within the EAEU to register the fact of shipment of goods with marking codes. The document is created upon receiving data from IS MPT through the synchronization mechanism or when preparing to send a notification to the system. This is an integration document: it does not generate movements in accounting registers. Work with the document is carried out by employees responsible for marking. Where to find in 1C: - Interface: section “1C Service: Marking (IS MPT)” → “Notification of goods shipment (EAEU) (IS MPT)”. - Navigation link: e1cib/list/Document.NotificationOfShipmentEAESESMPTK. 2. Header Attributes and Table Parts 2.1 Header Attributes (field purpose) Attribute Type (typical) Purpose Number, Date String / Date Standard attributes of the document. The date records the moment of registration of the notification in the accounting system. Organization ReferenceLink.Organizations Participant in the turnover — sender/recipient of the shipment in IS MPT. Counterparty ReferenceLink.Counterparties The second party of the cross-border supply (EAEU buyer for outgoing, supplier for incoming). Contract ReferenceLink.CounterpartyContracts The contract under which the shipment is carried out. OperationType / Direction Enumeration Defines the type of notification: incoming (receipt from IS MPT) or outgoing (sending to IS MPT). CountryOfDeparture / CountryOfDestination ReferenceLink.CountriesOfTheWorld Countries of the EAEU of departure and destination of the goods. Status Enumeration / String The state of the document in the lifecycle of exchange (Draft / Sent / Accepted / Error, etc.). Changing the status to “Accepted” is blocked in the presence of validation errors. DocumentIdentifierISMP (GUID/UUID) String Unique identifier of the notification on the side of IS MPT; used for matching when updating the status and linking documents. SenderDocumentNumber String External document number of the shipment (SNT/ESF), assigned by the sender. BasisDocument DocumentReference Reference to the accounting document (Sale/Receipt of goods) on the basis of which the notification is formed. Responsible ReferenceLink.Users Employee responsible for marking. Comment String Arbitrary text explanation. 2.2 Table Part “Goods” (marking codes) Column Type Purpose Nomenclature ReferenceLink.Nomenclature Marked item being shipped. MarkingCode / KIZ String Product identification code (Data Matrix, GTIN+serial). The main item of exchange with IS MPT. GTIN String Global Trade Item Number. Quantity Number Number of units/codes per line. UnitOfMeasurement ReferenceLink Unit of measurement of the nomenclature. Status (by code) String Status of a specific marking code in IS MPT. 2.3 Table Part “Errors” Column Type Mandatory Purpose ErrorCode String Automatically filled Code from the error reference of IS MPT. Example: ERR_001. ErrorDescription String Automatically filled Text description for the user. Example: “Invalid GTIN format”. Impact: if there are entries in “Errors,” the document cannot be successfully sent and blocks the setting of Status = “Accepted”. 3. Forms The standard composition of forms for documents of this type: Form Purpose DocumentForm Main form: input/view of header attributes, tables “Goods” and “Errors,” commands for exchange with IS MPT (send, update status, import codes). ListForm List of notifications filtered by organization, status, direction; opened by navigation link. SelectForm Select notification when linking with other objects (for example, with the receipt notification). 4. Key Procedures of Modules In the attached evidence, the original BSL code (paths: lines) is not provided. Below are typical handlers for the integration document of this type. The presence/signatures of specific procedures in 3.0.74.2 requires verification by the object module. - FillingHandler (object module) — filling in attributes when entering based on the accounting document (Sale/Receipt of goods): transferring organization, counterparty, contract, and marking codes to the “Goods” table. - BeforeSaving / OnSaving (object module) — control of correctness before saving, checking non-empty marking codes, prohibiting setting the status to “Accepted” in the presence of lines in “Errors.” - OnCreatingOnServer / OnOpening (form module) — managing the availability of exchange commands depending on Status. - Exchange commands (client/server or common module of the marking subsystem): - sending notification to IS MPT; - receiving/updating status from IS MPT; - importing marking codes from a file; - linking with the receipt notification by DocumentIdentifierISMP. ProcessingConduct is absent — the document does not generate movements (see section 5). 5. Conduct and Movements The document does not generate entries and does not have a handler ProcessingConduct. This is an integration document intended solely for data exchange with IS MPT and monitoring the movement of marked goods. The “Conduct” option is either disabled or has a status character without accounting movements. Accounting (financial) movements are formed in related documents, on the basis of which the notification is created. For reference — the typical logic of these documents according to the chart of accounts of the RK (Kazakhstan, 2026): Sale of goods (outgoing shipment), VAT rate 16 %: Debit Credit Content 1210 6010 Revenue reflected (Accounts Receivable ← income from sales) 1210 3130 VAT payable (16%) included in the cost 7010 1330 Cost of goods sold written off Receipt of goods (incoming supply from EAEU): Debit Credit Content 1330 3310 Goods received (KZ to suppliers) 1030 — Settlements through current accounts upon payment Electronic support for supplies — ESF (IS ESF) and SNT; marking codes are monitored through IS MPT. All monetary calculations are in tenge (₸). 6. Related Objects and Input Based On Work scenarios (from evidence): - Receiving incoming notification from IS MPT — upon receiving the shipment of goods from a supplier from another EAEU country registered in IS MPT. - Creating outgoing shipment notification — upon shipping marked goods to a buyer in another EAEU country. - Updating document status — after sending the notification to IS MPT to obtain the current processing status. - Importing marking codes from a file — when there is a large number of shipped marks instead of manual entry. - Linking shipment notification with receipt notification — after the recipient has accepted the goods and registered the receipt notification in IS MPT. Input based on: the document is usually created based on “Sale of goods” (outgoing) or “Receipt of goods” (incoming) — transferring the parties to the transaction and marking codes. Related objects: - documents of the subsystem “1C: Marking (IS MPT)” (including receipt notification from EAEU); - electronic documents ESF and SNT; - reference books: Organizations, Counterparties, Nomenclature, CountriesOfTheWorld. 7. Extension Points - Configuration extensions: adding attributes/commands to the document form without removing from support; overriding form handlers (OnCreatingOnServer, OnOpening). - Event subscriptions: BeforeSaving/OnSaving of the document for custom validation of marking codes or integration with external systems. - Common modules for exchange with IS MPT: overriding/extending procedures for sending and parsing responses from IS MPT (handling ErrorCode/ErrorDescription). - Additional processing (BSP): external processing for bulk importing marking codes from a file. - Exchange rules/HTTP services: points for configuring the correspondence of DocumentIdentifierISMP for linking with the receipt notification. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_