--- title: "AggregationOfMarkingCodesSUZISMPTK in 1C:Accounting for Kazakhstan 3.0 — complete guide" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-23 canonical: https://buhgpt.kz/suraqtar/agregaciyakodovmarkirovkisuzismptk-v-1s-buhgalteriya-dlya-en source: BuhGPT --- # AggregationOfMarkingCodesSUZISMPTK in 1C:Accounting for Kazakhstan 3.0 — complete guide > **TL;DR:** Verified on release 3.0.74.2 "Accounting for Kazakhstan" (edition 3.0). You packed 12 bottles of marked water into a box and stuck a single aggregate code on it. Now, when shipping, the storekeeper scans not 12 marks one by one, but a single code on the box — and all 12 nested --- Verified on release 3.0.74.2 "Accounting for Kazakhstan" (edition 3.0). You packed 12 bottles of marked water into a box and stuck a single aggregate code on it. Now, when shipping, the storekeeper scans not 12 marks one by one, but a single code on the box — and all 12 nested marking codes should be "pulled up" into the SNT. But for this to work, the box must first be "assembled" in the accounting records: link the 12 marking codes (KM) to a single aggregate code (KITU). This is exactly why the document "Aggregation of marking codes (SUZ IS MPT)" is opened. If the aggregate code has not been created, the box will not be scanned at shipment, and the marks will remain "hanging" individually and will not be written off from the balance. 1. Purpose The document combines individual goods marking codes (KM) into a single aggregated code of transport or group packaging (box, pallet) and registers this link in the information system for marking and traceability of goods (IS MPT) via the SUZ — the order management station. After aggregation, the box/pallet appears in the accounting records and at shipment as a single code, behind which stands the entire list of nested marks. 2. Where to find it Menu path: Warehouse → section "Marking" (block "Marking codes SUZ IS MPT") → "Aggregation of marking codes" → button "Create". Direct navigation link (menu "Service" → "Go to navigation link", paste the string and click "Go"): e1cib/list/Документ.АгрегацияКодовМаркировкиСУЗИСМПТК If the "Marking" item is not visible, enable the functionality: Main → Functionality → "Inventory" tab → checkbox "Goods marking" (IS MPT). Without this checkbox, the section and the document are hidden. 2a. How to find out your release Help → About the program (or the "i" icon in the top right corner). In the window that opens: - Platform version — for example, 8.3.24.xxxx (the "1C:Enterprise" line); - Configuration version — for example, "Accounting for Kazakhstan, edition 3.0 (3.0.74.2)". The instructions below are verified on 3.0.74.2. On neighboring releases, field names may differ by a word or two, but the logic is the same. 3. How to fill it in The fields are divided into the header and the tabular part. Mandatory ones are marked (req.). Header Field Why it matters and what happens on error Organization (req.) The legal entity on whose behalf the aggregation is performed and the request goes to IS MPT. If the wrong GLN/IIN-BIN is specified, the marking operator will reject the aggregation: the codes will not be found in your "account". Date (req.) The date of the packaging operation. Backdating is possible, but the date must not be earlier than the date the codes were introduced into circulation, otherwise the aggregation will not pass the IS MPT logic. Number Assigned automatically upon saving. Do not touch it manually — the numbering is continuous within the organization. Warehouse The place where the box is physically assembled. Affects the balance of marked goods. An empty warehouse means the balance movements will not be tied to the correct storage location. Responsible person Who assembled the packaging. Needed for resolving disputed aggregations. Comment Free text (packaging job number, shift). Does not affect posting. Tabular part "Aggregates" Here each package you are assembling is described. Field Why it matters and what happens on error Aggregate code (KITU) (req.) The transport packaging code that is printed on the box. It is either scanned from a ready-made label or generated by a button. A duplicate of an already existing code — IS MPT will return the error "aggregation code already in use". Aggregation level / Packaging type Group (internal) or transport (box, pallet). An incorrect level breaks the nesting: a pallet cannot be "nested" inside a box. Item The goods being packed. Needed to link the marks to an accounting position and the balance. Number of contents How many KM/child aggregates are inside. A discrepancy with the actual number of mark rows — the document will not post. Nested marking codes (subordinate table to the aggregate row) Field Why Marking code (KM) (req.) Marks of individual units that are placed into this box. Scanned with a 2D scanner in the selection field. One KM cannot be nested in two aggregates at the same time — an error will appear on repetition. Code status Shows that the mark has been emitted/introduced into circulation and is free. A mark with the status "withdrawn" or "already aggregated" cannot be nested. Practical procedure: scan the box code in the "Aggregate code" field, then scan the unit marks one by one — they are added to the nested rows, and the "Number of contents" counter grows on its own. Once the box is assembled, post the document. 4. Worked example Situation. LLP "Aruna" packs marked drinking water for shipment to a retail chain. 12 bottles, each with its own KM, are placed into a box. An aggregate KITU code is stuck on the box. The cost of one bottle is 250 ₸, accounted on account 1330 "Goods". Filling in: - Organization: LLP "Aruna"; Date: 06.09.2026; Warehouse: "Main". - Aggregate row: KITU code 046700000000000123, type — transport packaging, item "Water 0.5 l", number of contents — 12. - Nested KM: 12 scanned bottle marks. What happens on posting. The key point: aggregation does not change the cost and does not sell the goods, so this document, as a rule, does not generate Dr/Cr accounting entries. The goods sat on 1330 for 3,000 ₸ (12 × 250) and stay there: Indicator Before aggregation After aggregation Dr 1330 "Goods" 12 pcs × 250 = 3,000 ₸ 3,000 ₸ (unchanged) Marking codes, free 12 KM individually 0 — all inside KITU Aggregates (boxes) 0 1 box = 12 KM What changes is the state of the codes: 12 marks move from "free" to "aggregated", and a record appears "box ...0123 contains 12 KM". Later, upon sale of this box by another document (Sale of goods and services), at a sale price of, say, 700 ₸/pcs at a VAT rate of 16%, standard entries will follow — but this is no longer the aggregation document: Dr Cr Amount Operation 1210 6010 8,400 ₸ Revenue from the sale of 12 bottles (12 × 700) 1210 3130 1,344 ₸ VAT 16% (8,400 × 16%) 7010 1330 3,000 ₸ Cost written off (12 × 250) And this is where aggregation pays off: in the SNT and on the receipt, a single box code is enough — all 12 KM are withdrawn automatically, because you linked them in advance. 5. Types of operation The document handles operations of packaging/repackaging marked goods: - Aggregation — collecting individual KM into a new aggregate code (the main scenario). - Multi-level aggregation — nesting ready boxes into a pallet (an aggregate within an aggregate). - Addition (re-aggregation) — adding KM to an existing but not yet "closed" aggregate. - Removal / disaggregation — extracting KM from the composition of the packaging (partial or full), when the box has been opened. The available set depends on whether it is transport or group packaging, and on the current status of the codes. 6. What is generated on posting Accounting entries — usually absent: aggregation does not affect the cost of inventory, taxes, or mutual settlements. Movements in the marking information/accumulation registers: - the composition of the aggregate is registered (which KM are included in the KITU); - the status of the nested KM changes to "aggregated"; - the aggregate code becomes available for selection in shipping documents and the SNT. Electronic exchange: the document generates and sends an aggregation request to IS MPT via the SUZ. After a successful operator response, the "box code — nested marks" link is recorded on the side of the state system. The ESF (IS ESF) and SNT themselves are not issued by this document — they are generated by sale/transfer documents, but they already use the aggregate code created here. 7. Printed forms - Aggregate label (KITU) — with the transport packaging code in DataMatrix/GS1-128 format for sticking on a box or pallet. - Aggregate composition — a list of nested KM with item and quantity (for checking completeness during packaging). - Packaging job / aggregation sheet — a working document for the warehouse. The "Print" button on the document form; the specific set depends on the marking functionality settings. 8. Common errors "Marking code is already part of an aggregate" An attempt is being made to nest a mark in two boxes. Find the first aggregate, remove the KM (disaggregation/removal), then repeat the aggregation. "Aggregation code already in use" The box's KITU code is not unique (an old label was scanned again). Generate a new aggregate code or take a blank label. "Number of contents does not match the number of marking codes" You specified 12 in the field but scanned 11. Scan the missing mark or correct the counter — the document will not post until the numbers match. "Marking code in a status not allowed for aggregation" The mark has been withdrawn from circulation, blocked, or not yet introduced into circulation. Check the KM status in IS MPT, introduce it into circulation, and repeat. "IS MPT / SUZ exchange error: subscription limit exceeded" or timeout Check that the exchange settings and the EDS certificate are valid, and that the operator's tariff limit is not exhausted. After fixing it, resend the aggregation request from the document. "Organization not filled in" An empty header — fill in the organization with a correct BIN/GLN registered in the marking system. 9. FAQ Q: Does the document generate Dr/Cr accounting entries? A: No. Aggregation does not change the cost of goods, VAT, or mutual settlements — it shifts the marking codes into the composition of the packaging. The entries will appear later, in the sale document where the box is sold: Dr 1210 Cr 6010 for revenue, Dr 1210 Cr 3130 for VAT 16%, Dr 7010 Cr 1330 for cost. Q: How does an aggregate code (KITU) differ from a marking code (KM)? A: KM is the mark of an individual unit of goods (one bottle). KITU is the code of the packaging (box, pallet), inside which a list of KM is stored. At shipment, a single KITU is scanned, and all nested KM are withdrawn. Q: Can a box be nested inside a pallet? A: Yes, this is multi-level aggregation: first you assemble boxes (KM → KITU), then you fill a pallet with boxes (KITU → top-level KITU). Specify the correct packaging level/type. Q: How to disaggregate a box if the goods were opened? A: Perform a removal/disaggregation operation — the KM will return to the "free" status and again become available for individual sale or a new aggregation. Q: Where to get the KITU code itself? A: Either you print it on a pre-ordered label and scan it during aggregation, or you generate it by means of the document. The main thing is that the code must be unique. Q: Does the document issue an ESF or SNT? A: No. The ESF (IS ESF) and SNT are generated by sale and transfer documents. Aggregation only prepares the aggregate code, which these documents then use so as not to list marks individually. Q: What to do if the exchange with IS MPT fails? A: Check the valid EDS certificate, the SUZ IS MPT exchange settings, and the limit under the marking operator's tariff. Once the cause is fixed, resend the aggregation request from the document — the data will not be lost. Q: Does aggregation affect the balance of goods in the warehouse? A: The balance on account 1330 does not change in quantity or value — the 12 bottles were worth 3,000 ₸ and remain so. Only the "packaging" state of the codes changes: 12 free marks become the contents of a single box. Q: Is it mandatory to fill in the warehouse? A: Strictly speaking, it is not mandatory for the actual sending to IS MPT, but it is advisable: the warehouse ties the movement of marked goods to a storage location and simplifies the subsequent shipment and inventory of marks. Q: Can marks be added to an already assembled aggregate? A: Yes, as long as the aggregate is not "closed" and shipped — via the re-aggregation (addition) operation. After shipment, the composition is fixed. 10. Related documents On the basis of what it appears: - "Introduction of marking codes into circulation (SUZ IS MPT)" / receipt of marked goods — the KM must first be emitted and introduced into circulation, and only then can they be aggregated. - Packaging orders / warehouse jobs — as the basis for assembling boxes. What uses the result of aggregation: - "Sale of goods and services" — when a box is shipped, all nested KM are withdrawn; on its basis the ESF and SNT are issued. - "Transfer of goods" — the box is moved between warehouses as a single aggregate. - "Write-off of marking codes / withdrawal from circulation" — in case of defects or damage to the packaging. How to find out your release Help → About the program — there the version of the 1C:Enterprise platform and the release of the "Accounting for Kazakhstan, edition 3.0" configuration are indicated. Check the number against the one specified at the beginning of the article: the arrangement of fields and button names may change slightly between releases. The guide was prepared for "Accounting for Kazakhstan", edition 3.0, release 3.0.74.2. Current Kazakhstan rates for 2026: VAT 16%, MCI 4,325 ₸, MMW 85,000 ₸. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_