1. Identification of the Object
| Parameter | Value |
|---|---|
| Object Type | Document (Documents) |
| Name | NotificationOfImportFromEAEUISMP |
| Full Name | Document.NotificationOfImportFromEAEUISMP |
| Synonym | “Notification of Import of Marked Products (EAEU) (IS MP)” |
| Configuration | Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) |
| Country/Specificity | Republic of Kazakhstan, 2026 |
| Object Class | Electronic document of the traceability system (non-accounting) |
Purpose. The document is intended for registering and transmitting information about the import of marked products from EAEU countries (tobacco, footwear, etc.) to the Kazakhstan information system for monitoring the movement of goods (IS MP). It is used by importing organizations for declaring goods subject to mandatory marking when crossing the customs border. It is created upon the arrival of each batch of marked products from the EAEU — usually based on customs declarations or import statements. After completion, the document is sent to IS MP for obtaining permission to introduce goods into circulation and registering marking codes in the national register. It is part of the traceability system and is mandatory for participants in foreign economic activity working with marked products.
Important (boundary of responsibility). This is an informational document of the monitoring system. It does not reflect either the movement of goods in the warehouse, nor settlements with the supplier, nor VAT in accounting. Financial and warehouse accounting of the batch is performed by foundational documents (“Receipt of Goods and Services”, ESF/SNT, etc.). The notification only records the fact of import and the marking codes for the state IS MP.
Where to find in 1C: section “1C Service: Marking (IS MP)” → “Notification of Import of Marked Products (EAEU) (IS MP)”.
Navigation link: e1cib/list/Document.NotificationOfImportFromEAEUISMP
2. Header Attributes and Table Parts
2.1. Header Attributes
| Attribute | Purpose | Mandatory |
|---|---|---|
Number, Date |
Standard document attributes | Automatically filled |
Organization |
Importing organization (recipient of goods) | Generally mandatory |
SupplierName |
Name of the supplier from the EAEU country | Mandatory |
SupplierIdentificationNumber |
Identification/tax number of the supplier (analogous to IIN/BIN in the country of dispatch) | Mandatory |
RecipientIdentificationNumber |
BIN/IIN of the recipient organization (importer) in the RK | Mandatory |
| IS MP Status Attributes | Registration number, processing status, date of submission/registration | Filled based on the exchange fact |
| Attributes of the Foundational Document | Reference to customs declaration / import statement / receipt | Filled manually or when entering based on |
If one of the mandatory attributes (
SupplierName,SupplierIdentificationNumber,RecipientIdentificationNumber) is not filled — the platform will not allow the document to be processed and will display the error “Field … is not filled”.
2.2. Table Part “Products / Marking Codes”
Rows with descriptions of imported products and their related marking codes (Data Matrix / GTIN, identification codes, quantity). Filled manually, by scanning codes, or by uploading from a file (see scenario 3.6).
2.3. Table Part “Typical Errors”
List of validation errors received from IS MP when attempting to send or process the document.
| Field | Type | Purpose |
|---|---|---|
Text |
xs:string |
Description of the error returned by the IS MP system |
Field |
xs:string |
Name of the attribute or field in the table part where the error was detected |
3. Forms
For this type of object, the standard forms are provided in the typical configuration (exact composition is specified by the configurator of the specific version):
| Form | Purpose |
|---|---|
Document Form (DocumentForm) |
Main form for entering/editing the notification: header, products, marking codes, exchange panel with IS MP (sending, updating status, revocation), error table. |
List Form (ListForm) |
List of notifications filtered by processing status, organization, period; opens via link e1cib/list/Document.NotificationOfImportFromEAEUISMP. |
Selection Form (SelectionForm) |
Selecting a notification from other objects (for example, when entering related documents). |
| Service Exchange Forms | Dialogs for uploading codes from a file, viewing the result of sending, displaying validation errors from IS MP. |
4. Key Procedures of Modules
The original text of the modules (BSL with paths
path:string) is not provided in the attached evidence. Below are typical handlers for the electronic document of IS MP of this type. Specific procedure names should be verified according to the object/form module in the configurator version 3.0.74.2.
Object Module:
FillingProcessing— filling in attributes when entering based on (supplier, recipient, products from the foundational document).FillingCheckProcessing— control of mandatory attributes (SupplierName,SupplierIdentificationNumber,RecipientIdentificationNumber) and correctness of marking codes.ConductingProcessing— absent. The document does not generate accounting entries (see section 5).
Form Module / Server Exchange Handlers:
- Formation of XML message for IS MP and sending via the transport module of the service “1C: Marking (IS MP)” (scenario 3.2).
- Updating the status of the notification and loading the registration number from the response of IS MP (scenario 3.3).
- Formation of a correction and revocation of a previously sent notification (scenarios 3.4, 3.5).
- Loading marking codes from a file and parsing Data Matrix (scenario 3.6).
- Filling the table part “Typical Errors” based on the validation result of the IS MP response.
Usage Scenarios
| # | Scenario | When Applied |
|---|---|---|
| 3.1 | Creating the primary notification of goods import | Receiving marked products from the EAEU with a customs declaration/import statement; it is necessary to register marking codes in IS MP. |
| 3.2 | Sending notification to IS MP and receiving registration number | All mandatory attributes and codes are filled, the document is ready for registration in the state system. |
| 3.3 | Updating the status of the notification from IS MP | The document has been sent, but the processing status is unknown or requires updating. |
| 3.4 | Creating a correction for a previously submitted notification | Errors found in the registered notification (quantity, codes, supplier attributes). |
| 3.5 | Revoking the sent notification | The notification was sent by mistake, it is necessary to cancel the registration before acceptance by the customs authority. |
| 3.6 | Loading marking codes from a file | Manual scanning of a large number of Data Matrix or receiving a file with codes from the supplier. |
| 3.7 | Confirming receipt of goods (for incoming notifications) | The notification was created not by your organization (incoming); it is necessary to confirm the actual receipt of the products. |
5. Conducting and Movements
The document does not generate entries in accounting registers — the procedure ConductingProcessing is absent. This is an informational document of the goods monitoring system, which does not directly affect accounting registers. The movement of goods and settlements are reflected in foundational documents.
The corresponding accounting operations for the batch of imported goods are generated by “Receipt of Goods and Services” (and related ESF/SNT). For reference — typical entries for receipt according to the chart of accounts of the RK:
| Operation | Debit | Credit |
|---|---|---|
| Receipt of goods | 1330 “Goods” | 3310 “Short-term Payables to Suppliers” |
| VAT on import / for offset (rate 16 %) | 1420 “VAT to be Reimbursed” (or corresponding) | 3130 “VAT Payable” / 3310 |
| Payment to the supplier | 3310 | 1030 “Cash in Current Bank Accounts” |
The VAT rate in the RK for 2026 is 16 % (not 12 %). Upon subsequent sale of the goods, income is reflected in account 6010 “Income from Sales”, cost of goods sold — in 7010 “Cost of Sales”, settlements with the buyer — in 1210 “Short-term Receivables from Buyers”.
The notification itself in IS MP, when sent, only changes its own status attributes (registration number, processing state) and may write records in the service registers of the marking subsystem (exchange log, code statuses) — but not in the accounting and tax registers.
6. Related Objects and Input Based On
- Foundational Documents: “Receipt of Goods and Services”, customs declaration / import statement from EAEU — source of data about the batch, supplier, and goods.
- Electronic Documents: ESF (IS ESF) and SNT (accompanying invoice for goods) — accompany the same batch in terms of fiscal and commodity accounting.
- Service “1C: Marking (IS MP)”: transport and message exchange with the state system; stores connection settings, signature certificates, exchange log.
- Marking Codes: directories/registers of identification codes of marked products, filled from this notification.
- Incoming Notifications: notifications created by the counterparty, for which the organization performs receipt confirmation (scenario 3.7).
Input based on: as a rule, the notification is created based on the receipt/declaration document with auto-filling of the supplier, recipient, and product lines through FillingProcessing.
7. Extension Points
- Configuration Extension: adding header/table part attributes and subscribing to
FillingCheckProcessingfor additional control of codes and BIN/IIN without removing from support. - Form Handlers: overriding handlers for sending/updating status/revocation commands for integration with external marking accounting systems.
- Event Subscriptions:
BeforeWriting/OnWritingof the object — logging of exchanges, auto-filling of recipient attributes from organization settings. - Exchange Rules: refinement of XML formation for IS MP (field mapping, format versions) when changing operator requirements.
- Service Registers of the Marking Subsystem: extension of service registers of code statuses for internal analytics.
“Requires verification” (actually version-specific): the exact composition of forms, names of module procedures, and format of XML messages for IS MP should be verified according to the configurator version 3.0.74.2, as they change with updates of the marking operator formats.