1. Identification
| Parameter | Value |
|---|---|
| Object Type | Document (Documents) |
| Name | NotificationOfIntroductionIntoCirculationISMPK |
| Full Name | Document.NotificationOfIntroductionIntoCirculationISMPK |
| Synonym | — (not specified in metadata; in the interface, it is referred to as “Notification of Introduction into Circulation (IS MPK)”) |
| Configuration | Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 |
| Country/Specificity | Republic of Kazakhstan, labeling and traceability of goods (IS MPK) |
| Where to find | Section “Nomenclature and Warehouse” → “Notification of Introduction into Circulation (IS MPK)”. Journal: “Notifications of Introduction into Circulation (IS MPK)” (command OutgoingNotificationsOfIntroduction) |
| Navigation Link | e1cib/list/Document.NotificationOfIntroductionIntoCirculationISMPK |
Purpose. The document is intended to notify the Information System for Labeling and Traceability of Goods of Kazakhstan (IS MPK) about the introduction into circulation of labeled products. It is used by participants in circulation during the initial or repeated introduction of labeled goods into legal circulation on the territory of the RK (import, production, other activities requiring registration of labeling codes).
The document operates in two-way electronic exchange: it is created in 1C, sent to IS MPK, where it receives an identifier and processing status, after which the status is returned and stored in the document. This is an informational (regulatory-exchange) document — it does not reflect the facts of economic activity in accounting but registers the introduction of labeling codes into the state system. Actual accounting movements are formed by foundational documents (goods receipt, production).
2. Attributes of Header and Table Parts
2.1 Header Attributes
Mandatory for processing (if not filled, 1C does not process the document and issues “Field … is not filled”):
| Attribute | Type (typical) | Purpose |
|---|---|---|
ReasonForIntroductionIntoCirculation |
Enumeration/String | Basis for introduction into circulation (import, production, introduction during inventory, etc.) — determines the type of notification sent to IS MPK |
Supplier |
ReferenceLink.Counterparties | Counterparty — supplier/producer of the batch of labeled goods |
SupplierName |
String | Name of the supplier in a formalized form for transmission to IS MPK |
SupplierIdentificationNumber |
String | BIN/IIN of the supplier for identifying the participant in circulation in the state system |
Other header attributes (typical for IS MPK exchange documents):
| Attribute | Purpose |
|---|---|
Organization |
Organization-participant in circulation, on behalf of which the notification is sent |
Date, Number |
Standard document attributes |
DocumentBasis |
Reference to the goods invoice/receipt on the basis of which the notification is created |
Status / ProcessingStatus |
Current status of the notification in IS MPK (draft, sent, accepted, error) |
IdentifierInISMPK |
Identifier of the document assigned by the state system after sending |
Comment |
User's arbitrary comment |
2.2 Table Parts
Goods / Labeling Codes — list of registered labeling codes (KIZ/DataMatrix) linked to nomenclature and GTIN:
| Field (typical) | Purpose |
|---|---|
Nomenclature |
Accounting position to which the labeling codes relate |
LabelingCode |
The actual labeling code (SGTIN/DataMatrix) |
GTIN |
Global Trade Item Number embedded in the labeling code |
Quantity |
Number of units (for aggregated/group codes) |
Typical Errors — technical table part for storing validation errors returned from IS MPK:
| Name | Type | Purpose |
|---|---|---|
Text |
String | Text of the error message |
Field |
String | Name of the field where the error was found |
3. Forms
| Form | Purpose |
|---|---|
Document Form (DocumentForm) |
Main input form: filling in the header, selecting/loading labeling codes, initiating sending to IS MPK and updating status |
List Form (ListForm) |
Journal “Notifications of Introduction into Circulation (IS MPK)” with filtering by processing status, organization, supplier |
| Selection Form | Document selection when entering based on / from related objects |
| Auxiliary Exchange Forms | Forms for loading labeling codes from a file (Excel/TXT), selecting/registering GTIN, displaying the result of checking the status of codes on the IS MPK server |
4. Key Module Procedures
Evidence with paths
path:stringfor BSL to this object is not attached — below are typical document handlers for IS MPK exchange of this configuration. Specific names of procedures/modules require verification in version 3.0.74.2.
Object Module:
CheckFillingProcessing— control of mandatory attributes (ReasonForIntroductionIntoCirculation,Supplier,SupplierName,SupplierIdentificationNumber) and non-empty composition of labeling codes.Processing— not available: the document does not generate movements (see section 5).BeforeRecording/WhenSettingNewNumber— service initialization of status and exchange attributes.
Form Module:
- Filling based on the foundational document (transferring supplier, identification number, nomenclature, and labeling codes).
- Exchange commands: sending notification to IS MPK, updating status, checking the status of labeling codes on the server.
- Handlers for loading labeling codes from a file and selecting/registering GTIN.
Common Modules (IS MPK Exchange): forming a data package, calling the IS MPK service, parsing the response, and filling the table part “Typical Errors”.
5. Processing and Movements
The document does not generate accounting entries and does not have the procedure Processing — it is an informational document for interaction with the state system IS MPK. It does not perform any movements in accounting registers, accumulation, or information within accounting; the result of “processing”/sending is the registration of labeling codes in IS MPK and obtaining status.
Actual accounting movements for labeled goods are formed by foundational documents (goods receipt, production). For reference — typical entries according to the RK chart of accounts, which are made by these foundational documents (not this notification):
| Operation (foundational document) | Debit | Credit |
|---|---|---|
| Receipt of goods from the supplier | 1330 “Goods” | 3310 “Accounts Payable to Suppliers” |
| Incoming VAT at 16% | 1420 “VAT to be Reimbursed” | 3310 “Accounts Payable to Suppliers” |
| Payment to the supplier | 3310 “Accounts Payable to Suppliers” | 1030 “Cash in Current Accounts” |
| Subsequent sale | 1210 “Short-term Accounts Receivable from Customers” | 6010 “Revenue from Sales” |
| VAT on sale (16%) | 1210 | 3130 “VAT Payable” |
| Cost of goods sold | 7010 “Cost of Goods Sold” | 1330 “Goods” |
VAT rate — 16% (Kazakhstan, 2026). Electronic documents accompanying the turnover of goods — ESF (IS ESF) and SNT. Currency of accounting — tenge (₸).
6. Related Objects and Input Based On
Usage Scenarios (evidence):
- Creating a notification based on a goods invoice — during the initial receipt of a batch of labeled goods (import, purchase from the manufacturer).
- Sending a notification to IS MPK — after fully filling out the document, for registering the introduction of goods in the state system.
- Updating the document status from IS MPK — obtaining the current status of a previously sent notification (checking registration, receiving processing errors).
- Selecting and registering GTIN for nomenclature — when labeling codes contain GTIN that is not yet linked to a nomenclature position.
- Loading labeling codes from a file (Excel/TXT) — bulk input of codes received from the supplier.
- Checking the status of labeling codes on the IS MPK server — verification that the codes are not registered by other participants, are not in the status “Withdrawn from Circulation,” and are ready for registration.
Input Based On / Links:
- Basis for input — goods receipt document / goods invoice / production document (fills in supplier, identification number, nomenclature, labeling codes).
- Logically linked with IS MPK and IS ESF services (ESF, SNT) in the context of supporting the turnover of labeled goods.
- Reference books: Counterparties (supplier), Nomenclature, registers/reference books of GTIN and labeling codes.
7. Extension Points
- Filling based on. Extension of the filling procedure from the foundational document to add custom sources of labeling codes/GTIN.
- Filling validation. Supplementing
CheckFillingProcessingwith custom validation rules before sending (for example, control of BIN/IIN format, mandatory comment for certain reasons for input). - Exchange with IS MPK. Intercepting the formation of the package and parsing the response (subscriptions/redefinable common modules) for logging, resending, additional routing of errors to the “Typical Errors” table.
- Forms. Extensions of the document form and list form: custom commands for bulk loading of codes, additional filtering of the journal by processing status.
- Loading from a file. Extension of the labeling code file parser for non-standard supplier formats.
Since the document is not processed, adding
Processingin the extension for generating entries should not be done — accounting movements should remain on foundational documents.
