Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).
You have ordered labeling codes, the SUZ issued them, the codes are "hanging" in the status "Issued. Received". You printed the Data Matrix, stuck it on cigarette packs (or on shoes, tires, medicines — depending on what you are trading) — but the labeling system does not know about it yet. Until you report the application, the codes cannot be put into circulation, and their validity period is ticking. This is where the document "Application of labeling codes SUZ IS MPT" comes into play. It records the fact: the codes are physically printed and applied to the goods, and transmits this to the national system.
1. Purpose
The document reports to the IS MPT (Information System for Labeling and Traceability of Goods of the RK) that the labeling codes received from SUZ have been applied to specific units of goods. It changes the codes to the status "Applied" and opens the way for putting them into circulation. This is an operational labeling document — it does not create accounting entries.
2. Where to find
Section "Sales" (or "Purchases" — depending on whether you are a manufacturer or an importer) → group "Labeling" → journal "Orders, Application and Introduction into Circulation (SUZ IS MPT)". In the journal, click "Create" → "Application of labeling codes". Most often, the document is entered not from scratch, but based on the order of codes (see section 10).
Open the list directly in 1C: "Service" → "Go to navigation link" and paste:
e1cib/list/Document.ApplicationOfLabelingCodesSUZISMPTK
If the "Labeling" section is not visible, enable the functionality: "Administration" → "Labeling Settings" (or "Functionality") → check the box "Labeling of goods" and the necessary product groups.
2a. How to know your release
"Help" → "About the program" (or the "i" icon in the upper right corner). In the opened window: at the top — the version of the platform (for example, 8.3.24.xxxx), below — release of the configuration "Accounting for Kazakhstan", version 3.0. If your release differs from 3.0.74.2 — the composition of fields and buttons may shift slightly, but the logic remains the same.
3. How to fill
| Field | Why and what will happen in case of error |
|---|---|
| Organization (mandatory) | On whose behalf the report is sent to IS MPT. It must match the organization from the order of codes and have a configured exchange with IS MPT. If it's the wrong organization — the message will not be sent or will be sent under someone else's GLN/IIN-BIN. |
| Date (mandatory) | Date of the application operation. Do not set a future date — the operator will not accept it. The expiration period of the codes is calculated from this date. |
| Date of application | The actual date when the codes were applied to the goods. Usually coincides with the date of the document. This is what the system sees when checking the expiration dates. |
| Order (basis) | Reference to the document "Order of labeling codes SUZ IS MPT", based on which you received these codes. Fill it in — then the table part of the codes will be pulled in automatically, and you won't have to enter the GTIN manually. |
| Method of application / Method of release | Indicate who is putting the goods into circulation: "Production in RK", "Imported from EAEU", "Import from third countries". This affects what further documents (SNT, ESF, declaration) the system will require. An incorrect method — the codes cannot be put into circulation by the chosen way. |
| Operator / emission registrar | Account for exchange with IS MPT (SUZ). If not filled in — the document will not be sent. It is configured once in the exchange parameters. |
| Goods / Labeling Codes (table part, mandatory) | Here is the nomenclature, its GTIN, and the codes (KM/KIZ) that you are applying. Filled in by the button "Fill by order" or by uploading from a file/scanner. An empty table part = nothing to report, the document will not be processed. |
| Quantity | The number of applied codes for each GTIN. Must match the number of actually printed labels. Discrepancy — part of the codes will "hang" in the status "Received". |
| Comment | A free field for yourself. Does not affect the exchange. |
The workflow is simple: select the organization → insert the order → click "Fill by order" → check that the codes and quantities match what you printed → "Process and close" → send to IS MPT and wait for the status receipt.
4. Detailed example
Condition. LLP "Tabak-Opt" — importer of cigarettes from the EAEU. Based on the order of labeling codes dated 02.09.2026, received from SUZ 500 labeling codes for cigarettes GTIN 04870123456789. The codes are printed and applied to the packs. Date of application — 05.09.2026.
Filling out the document "Application of labeling codes SUZ IS MPT":
- Organization: LLP "Tabak-Opt"
- Date: 05.09.2026, date of application: 05.09.2026
- Order: "Order of labeling codes SUZ IS MPT No. 3 dated 02.09.2026"
- Method of release: "Imported from EAEU"
- Table part (by the button "Fill by order"): cigarettes, GTIN 04870123456789 — 500 pcs., 500 labeling codes.
What happens upon processing.
The document does not create accounting entries Dr/Cr — this is fundamental. The cost of the codes themselves and the operator's services are accounted for by separate documents (see below). Here, another movement occurs — the statuses of the codes and the labeling registers:
| Register (movement) | Before | After |
|---|---|---|
| Statuses of labeling codes | Issued. Received (500 pcs.) | Applied (500 pcs.) |
| Labeling codes (accounting KM by organization) | listed under the order | linked to GTIN and ready for circulation |
| Exchange with IS MPT | — | report on application sent, receipt received |
After a successful receipt, 500 codes transitioned to the status "Applied". Now you can issue the document "Introduction into circulation SUZ IS MPT" for them.
And where is the money? The cost of the codes (in the RK, the emission of the code is charged separately) and the operator's services are accounted for by the document of service receipt: for example, Dr 7210 (or expense account) Cr 3310 for the amount of services + Dr 1420 Cr 3310 for the amount of VAT 16 % (rate of RK since 2026). The application itself does not move money.
5. Types of operations
Depending on the role and product group, the document supports:
- Application on own production goods (RK) — you are the manufacturer, labeling what you produced yourself.
- Application on imported goods (third countries) — labeling before or after import, before declaration.
- Application on goods from EAEU — cross-border trade within the union.
- Application during relabeling — if the old code is damaged/lost and a new one is applied instead.
The specific set depends on the product group (tobacco, shoes, medicines, tires, etc.) and exchange settings.
6. What is formed upon processing
- Accounting entries — are not formed. This is an operational labeling document.
- Movements in the registers of information/accumulation of labeling — change of the status of codes to "Applied", linking KM to nomenclature/GTIN and organization.
- Electronic document in IS MPT (via SUZ) — report on the application of codes. In response, a receipt comes: codes accepted or rejected with a reason. The sending status is visible in the document itself and in the exchange journal.
- SNT and ESF are not created by this document — they are issued later, at the stages of introduction into circulation and sale.
7. Printed forms
There are no specific "accounting" printed forms for the document — it is a service document. Available:
- List of labeling codes — a list of applied KM (for reconciliation with those actually printed).
- Print labels / Data Matrix — output of the codes for printing (usually through the related labeling workplace or label printing service).
- Standard output of the table part of the document for printing/in Excel via "More" → "Output list".
8. Common errors
"Exchange account with IS MPT (SUZ) not filled in" — exchange is not configured. Go to "Administration" → "Exchange with IS MPT / Labeling Settings", specify the operator, GLN, and the organization's digital signature certificate.
"Labeling code already applied" / "Code status does not allow operation" — you are reporting again on the same codes or the codes are already in another status. Check the status in the register of codes; remove already applied KM from the table part.
"Number of codes in the document does not match the order" — not all codes were printed or extra ones were added. Adjust the quantity in the table part to the actually applied ones; leave the rest in the status "Received" until the next application.
"Expiration date of labeling codes has expired" — too much time has passed since receiving from SUZ. Such codes cannot be applied — you will have to order new ones.
"Digital signature error / certificate not found" — the signature certificate is expired or not installed. Update the certificate in the cryptography settings and in the exchange account.
"GTIN not registered in the national catalog" — the product is not entered in the labeling catalog. First, register the product card (GTIN) in the system, then repeat the application.
9. FAQ
Does the document create accounting entries? No. This is an operational labeling document. It changes the statuses of codes and sends a report to IS MPT. Costs for codes and operator services are reflected in separate receipt documents.
What is the difference between "Application of codes" and "Introduction into circulation"? Application records that the codes are physically printed and stuck on the goods. Introduction into circulation makes the goods legal for sale. The order is strict: first order → receipt → application → introduction into circulation.
Can codes be applied in parts? Yes. From one order, several application documents can be issued — for those codes that have already been printed. The rest will remain in the status "Received".
What to do if the code is damaged during printing? Issue a relabeling: write off the damaged code and apply a new one instead. The corresponding type of operation is available in the document or in a separate KM write-off document.
Is a digital signature required for sending? Yes. The report on the application is signed with the organization's electronic signature. Without a valid certificate, the document will not be sent to IS MPT.
What VAT rate applies to labeling operator services? Operator services are subject to VAT at the general rate of 16 % (RK norm since 2026). The application document itself does not calculate VAT — this is done by the service receipt document.
Codes are "hanging" in the status "Received" — why are they not applied? Either they are not in the table part of the document, or the expiration date has passed, or the receipt from the operator has not arrived. Check the exchange status and the expiration dates of the codes.
Is it mandatory to enter the document based on the order? Not mandatory, but convenient. By order, the codes and GTIN are pulled in automatically by the button "Fill by order", and you won't make mistakes in the numbers.
How to understand that the report is accepted by the system? The document shows the status of a successful receipt from IS MPT, and the codes transition to the status "Applied". If a rejection comes — read the reason in the receipt text and correct it.
Can the processing be canceled after sending to IS MPT? Processing can be canceled in 1C, but the status of the codes in the national system will not roll back. To withdraw data from IS MPT, use the standard operation of cancellation/relabeling, not just simple unprocessing.
10. Related documents
- Input based on: "Order of labeling codes SUZ IS MPT" — codes and GTIN are pulled from it.
- Input based on application: "Introduction into circulation SUZ IS MPT" — the next mandatory step before sale.
- Nearby in the chain: SNT documents (accompanying invoices for goods), ESF (electronic invoices in IS ESF) — issued at the stages of introduction into circulation and sale; receipt of operator services — to reflect costs in accounting.
How to know your release. "Help" → "About the program": it indicates the version of the 1C:Enterprise platform and the release of the configuration. This instruction is compiled for "Accounting for Kazakhstan", version 3.0, release 3.0.74.2. In neighboring releases, the names of buttons and the composition of fields may differ slightly, but the overall logic of working with the document remains.