Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).
You have shipped marked goods (footwear, tires, medicines, tobacco) to a buyer from the EAEU country. You have already recorded the sale in your accounting, you are waiting for the money — but the marking codes are still "hanging" on your balance in the MPT IS. Formally, the goods are with the buyer, but according to the traceability system, they are still yours. Until you transfer the codes via the shipment notification, the buyer will not be able to account for them, and you will have a discrepancy between the remaining codes and the actual stock. This document comes into play here: it removes the transferred codes from your accounting and generates an electronic notification for the marking system.
1. Purpose
The document "EAEU Shipment Notification MPT IS K" transfers marking codes (DataMatrix / KIZ) to a buyer from the EAEU and writes them off from your balance in the marking and traceability information system (MPT IS of the RK). This is an electronic exchange document with the marking operator, not a sales document: revenue and VAT are recorded by the sale, while the notification is only responsible for the movement of the codes themselves.
2. Where to find
You can open the list in two ways.
Through the menu: section "Sales" → group "MPT IS (Goods Marking)" → "EAEU Shipment Notifications". Create a new document — button "Create".
Through the navigation link: menu "Service" → "Go to navigation link" (or navigation field by address), paste:
e1cib/list/Document.ShipmentNotificationEAEUMPTISK
If the "MPT IS" group is not visible, enable exchange with marking: "Administration" → "Exchange of electronic documents" → "Goods marking MPT IS".
2a. How to find out your release
Menu "Help" → "About the program" (or the "i" icon in the upper right corner). It indicates the version of the "1C:Enterprise" platform (for example, 8.3.24) and the release of the "Accounting for Kazakhstan" configuration. The instruction is written for release 3.0.74.2; in other releases, the names of the fields may differ slightly.
3. How to fill out
It is more convenient to enter the document based on the sale — then the counterparty, contract, and codes will be pulled in automatically. Below is a breakdown by fields.
| Field | Purpose and what happens in case of an error |
|---|---|
| Organization (mandatory) | The name under which the shipment is made and whose registration number goes to the MPT IS. If you make a mistake, the notification will go under someone else's participant in the turnover and will not pass the operator's verification. |
| Date (mandatory) | Date of shipment/transmission of codes. Affects the date of movement in the marking registers. Enter the actual shipment date; otherwise, it will not link with the STN and sale by deadlines. |
| Counterparty (mandatory) | The buyer from the EAEU to whom the codes are transferred. Based on their IIN/BIN and turnover participant data, the codes "move" to their balance. An incorrect counterparty means the codes will go to the wrong place. |
| Contract | Basis for shipment. Determines the currency of settlements and the procedure for mutual settlements. |
| Destination country (mandatory) | The EAEU state to which the goods are going (Russia, Belarus, Kyrgyzstan, Armenia). Determines that this is a cross-border shipment within the Union, not an internal sale. |
| Document basis / Sale | Reference to the sale from which the codes are taken. Without it, the codes will have to be selected manually. |
| Table part "Goods" (mandatory) | Product nomenclature, quantity, marking codes (GTIN/KIZ). These are the codes that are written off from the balance. If the code is not listed under you, the notification will not be processed. |
| Marking codes (mandatory) | Scanned by a scanner or selected from the balance DataMatrix codes. The number of codes must match the quantity of goods in the line. |
| Responsible / Department | For analytics and access delimitation. Does not affect movements. |
| Comment | Arbitrary note for yourself. |
Order of actions:
- Create a document based on the sale of marked goods.
- Check the organization, counterparty, and EAEU destination country.
- In the table part, ensure that all marking codes are selected for each line (number of codes = number of goods).
- Process the document ("Process").
- Send the notification to the operator: "EDO" → "Send" (or "Transfer to MPT IS"). Wait for the status "Accepted".
4. An example with entries
Condition. LLP "Astana-Footwear" ships 10 pairs of marked boots to Russia at 5,000 ₸ per pair. VAT rate — 16 %. Cost price per pair — 3,000 ₸.
Calculation for the sale:
- Cost excluding VAT: 10 × 5,000 = 50,000 ₸
- VAT 16 %: 50,000 × 16 % = 8,000 ₸
- Total to be paid: 58,000 ₸
- Cost price: 10 × 3,000 = 30,000 ₸
The document generates the entries for the sale (not the notification):
| Dr | Cr | Amount, ₸ | Description |
|---|---|---|---|
| 1210 | 6010 | 50,000 | Revenue from the sale of goods |
| 1210 | 3130 | 8,000 | VAT on sale (16 %) |
| 7010 | 1330 | 30,000 | Cost of 10 pairs written off |
Upon receipt of payment to the account: Dr 1030 Cr 1210 — 58,000 ₸.
The EAEU shipment notification does not create accounting entries. Its function is to record movements in the marking registers: 10 DataMatrix codes for these boots are written off from your balance of codes and fixed as transferred to the buyer in Russia. After acceptance by the operator, the codes are assigned to the Russian buyer in the MPT IS.
Result: money and VAT "sit" in the sale, while the notification aligns the balance of marking codes with the fact — you no longer have those 10 codes on your balance.
5. Types of operations
The document serves to transfer codes during cross-border shipment of marked goods within the EAEU:
- Shipment (sale) to an EAEU country — the main scenario, transferring codes to the buyer.
- Movement of own goods in the EAEU — if the goods are going to another of your subdivisions/countries without changing ownership.
- Return to the supplier from the EAEU — reverse transfer of codes upon return.
The specific set of types depends on the exchange settings with the MPT IS and the product group (footwear, tires, light industry, tobacco, medicines).
6. What is generated upon processing
- Entries in accounts — the document does not generate (revenue, VAT, and cost price are recorded by the sale).
- Movements in marking registers — writing off transferred codes from the organization's balance of marking codes and marking the transfer to the EAEU buyer. (Exact names of registers depend on the release and product group — when making changes, refer to the structure of the specific version.)
- Electronic document for MPT IS — the shipment notification itself, which is sent to the marking operator; statuses ("Sent", "Accepted", "Rejected") are reflected in the document card.
- Link with STN and ESF — the notification is linked with the accompanying invoice for goods (STN) and electronic invoice (ESF) for the same shipment, so that data on codes, STN, and the tax side of the transaction do not diverge.
7. Print forms
Available from the document:
- Shipment notification — printed form of the notification itself with a list of marking codes.
- List of marking codes (KIZ/DataMatrix list) — registry of transferred codes for reconciliation with the buyer.
- Print labels / codes — if necessary, print codes from the document.
The "Print" button is in the command panel of the document.
8. Common errors
"Marking code not found in the organization's balance" You are trying to transfer a code that is not listed under you (already shipped, not accounted for upon receipt, or entered incorrectly). Check the balance of codes, account for the missing ones through the receipt/input document, and select the codes again.
"The number of marking codes does not match the quantity of goods in the line" In the line, there are 10 pairs, but 9 codes have been selected. Rescan or select the missing code — each unit of marked goods needs its own code.
"Destination country not filled in" For shipments to the EAEU, the country is mandatory: without it, the operator will not understand the direction of the transfer. Fill in the EAEU member state.
"Notification rejected by the MPT IS operator" The reason comes in the text of the response: most often incorrect buyer details (IIN/BIN, turnover participant) or codes have already been transferred by another document. Correct the details/codes and resend.
"Exchange with MPT IS not configured" The send button is inactive. Enable exchange: "Administration" → "Exchange of electronic documents" → "Goods marking MPT IS", specify the certificate and participant's account details.
9. FAQ
Does this document create accounting entries? No. Revenue (Dr 1210 Cr 6010), VAT 16 % (Dr 1210 Cr 3130), and cost price (Dr 7010 Cr 1330) are recorded by the sale document. The notification only moves the marking code registers.
Why is it needed if the sale has already been processed? The sale reflects money and taxes but does not transfer marking codes to the MPT IS. Until there is a notification, the codes are listed under you, and the buyer does not account for them — a discrepancy in balances arises.
How is it different from the usual transfer of codes during internal sales? Here, the shipment goes to another EAEU country, so the destination country and cross-border format for transferring codes to the operator are mandatory.
What is the VAT rate in the shipment example? In 2026, the basic VAT rate in the RK is 16 %. When exporting/shipping to the EAEU, a zero rate may apply if confirmation conditions are met — this is determined by the sale document, not the notification.
What to do if the code is not found in the balance? This means the code is not accounted for or has already been transferred. Check the receipt of marked goods and the balance of codes; if necessary, enter/account for the codes and repeat the selection.
Do I need to issue STN and ESF separately? Yes. The MPT IS notification does not replace either the STN or the ESF. All three are linked together for the same shipment.
Can I resend the notification after rejection? Yes. Correct the reason from the operator's response (buyer details or composition of codes) and resend the document — the status will update to "Accepted".
How to check if the codes have been removed from my balance? After the status "Accepted", the codes are written off from the balance of marking codes. Reconcile with the report/list of codes or the KIZ list from the printed form.
What to enter if the buyer returns goods from the EAEU? A reverse operation is processed — a return notification/receipt of codes, so that the codes return to your balance. The sale is reversed by the return document.
10. Related documents
Entered based on:
- Sale of goods and services (shipment of marked goods to the EAEU) — the main source of codes, counterparty, and contract.
- Movement of goods — when sending your own goods to another EAEU country.
Related and subsequently entered:
- STN (accompanying invoice for goods) — mandatory for marked/traceable goods when moving within the EAEU.
- ESF (electronic invoice, ESF IS) — tax document for the same shipment.
- Receipt / accounting of marking codes — source of codes on your balance; without it, there is nothing to transfer.
How to find out your release: menu "Help" → "About the program" — it indicates the version of the platform and the release of the configuration.
The material is prepared for the "Accounting for Kazakhstan" configuration, version 3.0, release 3.0.74.2. When updating, check the names of fields and registers with your version.