1. Identification
| Parameter | Value |
|---|---|
| Object Type | Document (Documents) |
| Name | NotificationOfExportEAESESMPTK |
| Full Name | Document.NotificationOfExportEAESESMPTK |
| Synonym | Export Notification (EAEU) (IS MPT) |
| Configuration | Accounting for Kazakhstan, version 3.0 (3.0.74.2) |
| Navigation Link | e1cib/list/Document.NotificationOfExportEAESESMPTK |
| Where to Find | Section “1C Service: Marking (IS MPT)” → “Export Notification (EAEU) (IS MPT)” |
Purpose. The document is intended for the formation and sending of notifications about the export of marked goods outside the Republic of Kazakhstan to EAEU countries through the Information System for Monitoring the Movement of Goods (IS MPT). It is used by participants in the turnover of marked products to notify the traceability system about cross-border shipments of goods with marking codes. The document is usually created based on the sales/shipping document and sent to IS MPT for registering the fact of the goods being removed from the national segment of the traceability system.
Important. This is a notification (integration) document, not a document of an economic transaction. It does not reflect the movement of goods, settlements, or VAT in accounting — this is the responsibility of the underlying sales document.
2. Header Attributes and Table Parts
2.1. Mandatory Header Attributes
The attributes listed below are mandatory for completion: without them, 1C will not allow the document to be processed/sent and will issue an error like “Field … is not filled in.”
| Attribute | Purpose |
|---|---|
ProductGroup |
Product group of marking (e.g., footwear, tobacco, tires), determining the rules of IS MPT |
Supplier |
Counterparty-exporter (sender of goods), participant in turnover from the RK |
SupplierName |
Name of the supplier for transmission to IS MPT |
SupplierIdentificationNumber |
Identification number of the supplier (BIN/IIN) |
Recipient |
Counterparty-recipient in the EAEU country |
RecipientName |
Name of the recipient for transmission to IS MPT |
RecipientIdentificationNumber |
Identification number of the recipient (TIN/UNP of the EAEU country) |
CountryRecipient |
Country of destination (EAEU country) to which the goods are exported |
DocumentNumberCrossBorder |
Number of the cross-border (shipping) underlying document |
DocumentDateCrossBorder |
Date of the cross-border underlying document |
ShippingDateTime |
Actual date and time of goods shipment |
In addition to the mandatory attributes, the document usually contains service attributes for integration: Date, Number, Organization, as well as attributes for the status of exchange with IS MPT (document identifier in the system, current processing status).
2.2. Table Part “Marking Codes”
Rows with marking codes (KIs/KIZs, GTIN, serial/aggregated codes) being removed from circulation during export. Filled from the underlying document, from a file, or from a data collection terminal (DCT).
2.3. Table Part “Errors”
List of validation errors received from IS MPT during the document check or submission.
| Field Name | Type | Purpose |
|---|---|---|
Text |
xs:string | Error message text |
Field |
xs:string | Name of the field/attribute to which the error relates |
3. Forms
| Form | Purpose |
|---|---|
Document Form (DocumentForm) |
Main input form: filling in the header, marking codes, initiating checks/sending, viewing status and error list |
List Form (ListForm) |
List of notifications filtered by exchange status, product group, recipient, period |
Selection Form (SelectionForm) |
Selecting a notification when picking from other objects |
The document form usually contains integration commands: “Check”, “Send to IS MPT”, “Update Status”, as well as commands for loading marking codes (from file/DCT).
4. Key Module Procedures
Evidence with BSL paths to procedures is not attached. Below are typical handlers for the integration document with IS MPT in the BK 3.0 configuration. Verify specific names in the configurator for version 3.0.74.2.
Object Module:
CheckFillingProcessing— control of filling in mandatory header attributes (see p. 2.1) and presence of marking code rows; generating a refusal for empty fields.FillingProcessing— filling in attributes when entering based on the sales/shipping document (supplier, recipient, marking codes, shipping date).Processing/DeleteProcessing— minimal logic; movements in registers are not formed (see p. 5).
Form Module:
OnCreateOnServer— form initialization, setting visibility of commands based on exchange status.CheckDocument— calling server-side filling check according to IS MPT rules, filling in the table part “Errors”.SendToISMPT— serializing the document in IS MPT format and sending it through the integration service; saving the identifier and status.UpdateStatus— requesting the current processing status of the notification from IS MPT and displaying it.LoadMarkingCodes— loading codes from a file/DCT into the table part.
5. Processing and Movements
The document does not generate accounting entries and does not make movements in registers (register_records = []). This is a notification document of the traceability system, not an economic transaction. Processing only records the fact of readiness/sending the notification to IS MPT.
The actual economic transaction of export is reflected by the underlying sales document on the basis of which the notification is created. It is the sale that generates movements in the RK accounting (rates and accounts — Kazakhstan, 2026):
| Economic Transaction | Debit | Credit | Comment |
|---|---|---|---|
| Export of goods reflected | 1210 (short-term receivables from buyers) | 6010 (income from sales) | Sales to EAEU countries; confirmed export has VAT at a zero rate |
| Cost of goods sold written off | 7010 (cost of sales) | 1330 (goods) | |
| VAT (for domestic transactions, for reference) | — | 3130 (VAT payable) | Standard VAT rate in RK from 2026 — 16%; for confirmed export to EAEU, a rate of 0% applies |
Electronic support for export supply: ESF (IS ESF) and, if necessary, SNT. The export notification to EAEU (IS MPT) is a separate channel for traceability of marking codes, independent of ESF/SNT.
6. Related Objects and Input Based On
- Input Based On: the document is created based on sales/shipping documents of marked goods to a counterparty in the EAEU country.
- Copying: a new document can be created by copying an existing one (scenario of repeated shipment to the same recipient).
- Related Systems: IS MPT (traceability and marking codes), IS ESF (ESF), SNT.
- Directories: “Counterparties” (supplier/recipient), “Nomenclature” (product groups of marking), country classifier (EAEU recipient country).
Typical Work Scenarios
- Creation Based on Sale — when shipping marked goods to a counterparty in the EAEU.
- Check Before Sending — identifying filling errors before sending to IS MPT.
- Sending to IS MPT — after successful check and filling of mandatory attributes.
- Updating Status — obtaining the current processing status from IS MPT.
- Loading Marking Codes from a file/DCT — during manual formation or additional filling.
- Copying — for repeated shipment to the same recipient.
7. Extension Points
- Configuration Extension: overriding
CheckFillingProcessingfor additional checks of attributes; adding commands/fields on the document form through form extension. - Form Event Handlers (
OnCreateOnServer, handlers for sending/updating commands) — for integration logic. - Subscriptions to Events:
BeforeRecording/OnRecordingof the document for custom validation or logging of exchanges. - Input Based On: adding custom sources/receivers through the manager module (
FillingProcessing). - Additional Attributes and Information — through the BSP mechanism (set of additional document attributes).
Requires Verification (version-wise): exact names of module procedures, composition of form commands, and serialization format in IS MPT should be verified in the configurator of the specific version 3.0.74.2, as integration mechanisms for marking are regularly updated.