1. Identification
| Parameter | Value |
|---|---|
| Object Type | Document (Documents) |
| Name | NotificationOfAcceptanceEAESESMPTK |
| Full Name | Document.NotificationOfAcceptanceEAESESMPTK |
| Synonym | Notification of acceptance of goods (EAEU) (IS MPT) |
| Configuration | Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) |
| Class of Objects | Electronic marking documents (IS MPT) |
Purpose. The document is intended to notify the information system for monitoring the movement of goods (IS MPT) of the Republic of Kazakhstan about the fact of acceptance of marked goods received from the countries of the Eurasian Economic Union (EAEU). It is used by participants in the turnover of marked products (recipients of goods) to confirm receipt of goods with marking codes. The document is created based on the shipping document from IS MPT and sent to the system after the actual acceptance of goods. It is used in companies participating in cross-border trade of marked products within the EAEU; the frequency of use depends on the volume of import operations.
Where to find in 1C. Section “1C Service: Marking (IS MPT)” → “Notification of acceptance of goods (EAEU) (IS MPT)”.
Navigation link: e1cib/list/Document.NotificationOfAcceptanceEAESESMPTK.
2. Attributes of Header and Table Parts
2.1 Header Attributes (Purpose of Fields)
| Attribute | Type | Purpose |
|---|---|---|
Number |
String | Internal document number in the accounting system |
Date |
Date | Date of registration of the notification in 1C |
Organization |
ReferenceLink.Organizations | Participant in turnover — recipient of goods (owner of IS MPT cabinet) |
Counterparty |
ReferenceLink.Counterparties | Supplier from the EAEU country that shipped the marked goods |
DocumentBasis |
Link | Shipping document from IS MPT on the basis of which the notification is formed; key point of connection with accounting documents |
IdentifierISMPPT |
String | Unique identifier of the document on the side of IS MPT |
Status / StatusISMPPT |
Enumeration / String | Current status of processing the notification in IS MPT (draft, sent, accepted, rejected, error) |
SubmissionDate |
Date | Date/time of submission of the notification to IS MPT |
OperationType |
Enumeration | Nature of the acceptance operation: full acceptance, partial acceptance, rejection of the batch |
Comment |
String | User's arbitrary comment |
The exact composition of header attributes is version-specific — clarified according to the configurator of version 3.0.74.2 (requires verification only regarding the names of service attributes of exchange).
2.2 Table Part “Goods” (Marking Codes)
The main table part stores the list of accepted goods and their associated marking codes. The typical composition of columns:
| Column | Type | Purpose |
|---|---|---|
Product |
ReferenceLink.Products | Accepted marked goods |
MarkingCode / GTIN |
String | Marking code (KIZ/CM) or product identifier |
Quantity |
Number | Accepted quantity |
AcceptanceResult |
Enumeration | Indicator: accepted / rejected / not found (for partial acceptance scenarios) |
RejectionReason |
String | Reason for rejection of the marking (defect, shortage, mis-sorting) |
2.3 Table Part “Typical Errors”
Service table part for storing validation errors and results of exchange with IS MPT.
| Name | Type | Purpose |
|---|---|---|
Text |
String | Error message text |
Field |
String | Name of the field to which the error relates |
3. Forms
| Form | Purpose |
|---|---|
| List Form | View and selection of notifications, control of exchange statuses with IS MPT, group operations (send, update status) |
| Document (Object) Form | Input/editing of header and table part of goods, scanning of marking codes, sending notification and receiving response from IS MPT |
| Selection Form | Selection of notification in other documents/processings when linking data |
Typically, a separate form is used to display the table part “Typical Errors” (error panel in the document form) after unsuccessful validation or exchange.
4. Key Module Procedures
The attached evidence does not provide the source code (BSL) of the procedures. Below are typical handlers of this type of object (electronic document IS MPT). Exact names and contents of procedures require verification according to the object module of version 3.0.74.2.
Object Module:
ProcessingConducting(Refusal, ConductingMode)— for this document, conducting does not generate accounting movements (see section 5); if a procedure exists, it usually only records the status/service data.ProcessingFilling(FillingData, ...)— filling in attributes when entering based on the shipping document from IS MPT and transferring marking codes.ProcessingCheckingFilling(Refusal, CheckedAttributes)— control of mandatory fields and correctness of the composition of marking codes before submission.
Form Module:
- Handlers of commands for sending to IS MPT (
SendToISMPPT), updating status/response, scanning marking codes. - Handler for filling the table part of goods from the basis document.
- Filling and displaying the table part “Typical Errors” based on validation/exchange results.
5. Conducting and Movements
The document does not generate entries in accounting or warehouse registers directly. Registration of movements of marking codes occurs on the side of IS MPT; in the accounting system 1C, changes are reflected indirectly — through related accounting documents (Receipt of goods, Report to the consignor, etc.), linked to the attribute DocumentBasis.
The financial and warehouse consequences of accepting imported marked goods are reflected by not this notification, but the document of the accounting contour (for example, “Receipt of goods”). For Kazakhstan (2026), the typical set of entries for such a related receipt document is:
| Operation | Debit | Credit | Comment |
|---|---|---|---|
| Receipt of goods | 1330 “Goods” | 3310 “Short-term payables to suppliers” | For the cost of received goods |
| Input VAT | 1420 “VAT to be refunded” | 3310 | VAT rate 16% (Kazakhstan 2026) |
| Payment to supplier | 3310 | 1030 “Cash in current accounts” | When paying from the settlement account |
Upon subsequent sale of marked goods, accounting documents generate:
| Operation | Debit | Credit |
|---|---|---|
| Recognition of income | 1210 “Short-term receivables from buyers” | 6010 “Revenue from sales” |
| VAT payable (16%) | 1210 | 3130 “VAT payable” |
| Cost of goods sold | 7010 “Cost of sales” | 1330 “Goods” |
All amounts are in tenge (₸). The notification itself does not participate in these entries: it only confirms the fact of acceptance of markings in the state system. Accompanying electronic documents (ESF through IS ESF, CNT) are issued as separate configuration objects.
6. Related Objects and Input Based On
Input Based On (incoming link):
- The document is created based on the shipping document from IS MPT — the source for filling in goods, marking codes, and the EAEU sender counterparty.
Related Objects:
DocumentBasis— accounting documents of receipt (Receipt of goods, Report to the consignor, etc.), through which the operation is reflected in accounting and warehouse accounting.- Electronic documents: ESF (IS ESF) and CNT — accompanying documents for the import supply.
- Reference directories “Products”, “Counterparties”, “Organizations”.
Typical Usage Scenarios:
| No. | Scenario | When Applied |
|---|---|---|
| 3.1 | Creation of a notification of acceptance based on the shipping document from IS MPT | After receiving goods from the EAEU country, when the supplier has already registered the shipping document in IS MPT |
| 3.2 | Updating notification data from IS MPT | Synchronization of status and receiving response from IS MPT after submission |
| 3.3 | Partial acceptance of goods with rejection of some markings | When defects, shortages, or discrepancies in some goods are found |
| 3.4 | Complete rejection of a batch of goods | When refusing the entire batch (critical defect, delivery not according to order) |
| 3.5 | Acceptance of goods with unaccounted markings | If codes found during scanning are missing in the shipping document (mis-sorting, supplier error) |
| 3.6 | Export of marking codes for verification or archiving | Data transfer to other systems, reporting, archival storage |
7. Extension Points
- Event Handlers of the Object Module (
BeforeRecording,ProcessingFilling,ProcessingCheckingFilling) — for additional validation of marking codes and auto-filling from the basis document. - Form Extensions — adding attributes/commands to the document form (additional marking checks, integration with scanner, custom statuses).
- Event Subscriptions — reaction to recording/conducting the notification to trigger related operations of the accounting contour.
- Exchange Rules with IS MPT — configuration of export/import formats, processing of response packages, and filling the table part “Typical Errors”.
- Integration with ESF/CNT — linking the notification with accompanying electronic documents of the import supply.