Verified on release 3.0.74.2 "Accounting for Kazakhstan" (edition 3.0).
A truck with labeled goods has arrived at your warehouse. Each bottle, pack, or vial has its own marking code (KM). The store ordered a box of 200 units. Preparing an SNT and shipment by manually listing 200 separate codes takes an hour of work and guarantees scanning errors. It's easier to pack everything into a box and get one code for the entire package. This is exactly why you open "Aggregation outside production IS CED M": you scan 200 codes, link them to a single transport packaging code (KITU), and then work with the box as a single object.
1. Purpose
The document combines individual marking codes (KM) into one aggregated transport packaging code — KITU — without linking to a production process (you are a distributor or wholesaler, not a manufacturer). Aggregation data goes to the national marking system (IS CED M). After this, during shipment and in the SNT, you can specify one box code instead of dozens of nested ones.
2. Where to find it
The "Marking" section (or "Warehouse" → "Marking of goods IS CED M", depending on the interface setting) → the "Aggregation" group → the "Aggregation outside production" journal → the "Create" button.
To open the journal directly, copy the navigation link and paste it into 1C via "Service" → "Go to navigation link" (or Functions menu → link icon):
e1cib/list/Документ.АгрегацияВнеПроизводстваИСЦЭДМ
If the "Marking" section is not visible, check that in "Administration" → "Functionality" (or "Marking settings") the exchange with IS CED M is enabled and a digital signature profile is connected for sending data.
2a. How to find out your release
"Help" → "About the program" (or the "i" icon in the upper right corner). In the window that opens, you will see the platform version (for example, 8.3.24.xxxx) and the configuration release — a line like "Accounting for Kazakhstan, edition 3.0 (3.0.74.2)". Rely on this number: the location of fields and the set of operations change between releases.
3. How to fill it in
Fill in from top to bottom — this way the document pulls in the data correctly.
| Field | Why it matters and what happens on error |
|---|---|
| Organization (required) | On whose behalf the data will go to IS CED M. If the wrong turnover participant is specified, the marking system won't find the codes on the balance and will return a rejection. |
| Date (required) | The date of the aggregation operation. Enter the actual packing date: based on it, the system checks whether the codes were "in circulation" at that moment. |
| Number | Assigned automatically upon recording. Don't touch it manually — it disrupts the numbering. |
| Warehouse (required) | The place where the codes physically are. The codes must be listed at this warehouse in the marking balances. Wrong warehouse — "code not found in balances". |
| Packaging type / Aggregation level (required) | Box, pallet, etc. The level determines what can be nested into what: KM → into a box, boxes → into a pallet. An incorrect level — the nesting validation won't pass. |
| Aggregate code (KITU) (required) | The transport packaging code. You either scan a ready SSCC/KITU label or generate a new one with the button. An empty code — the document won't be posted. |
| The "Marking codes" tabular section (required) | Individual KMs (or lower-level codes) get here via scanner or upload. Each code must be in your balances and not part of another aggregate. Duplicates and "foreign" codes will be highlighted during the check. |
| Responsible person | Who prepared it. Does not affect movements, needed for control and resolving disputed shipments. |
| Comment | A free field: order number, shift, crew. |
Workflow: select the organization and warehouse → set the packaging type → scan/generate the aggregate code → scan the nested KMs into the tabular section → click "Check" (control of balances and statuses) → "Post" → "Send to IS CED M".
4. Worked example
Situation. LLP "Distributor" ships a box of labeled water to a store — 12 bottles. The goods are at the "Finished goods warehouse", the accounting cost per unit is 400 ₸, the selling price is 560 ₸ without VAT.
Actions in the document:
- Organization — LLP "Distributor", warehouse — "Finished goods warehouse", packaging type — "Box".
- Aggregate code KITU No. 046000000000000123 was generated.
- The 12 bottle KM codes were scanned into the tabular section.
- Check → Posting → Sending to IS CED M.
What's important to understand about the entries. Aggregation is a logistics, not a financial operation. The goods are not sold, not written off, ownership does not change — you merely "put 12 codes into one box". Therefore, the "Aggregation outside production IS CED M" document itself does not generate Dr/Cr accounting entries. It moves only the marking code registers (see section 6).
The entries will appear in the next document — the sale of the box. There, on these same figures:
| Operation | Dr | Cr | Amount, ₸ |
|---|---|---|---|
| Sale of 12 bottles (income) | 1210 | 6010 | 6 720 |
| VAT 16% on sale | 1210 | 3130 | 1 075.20 |
| Cost of sales written off | 7010 | 1330 | 4 800 |
Calculation: income 12 × 560 = 6,720 ₸; VAT 16% = 6,720 × 0.16 = 1,075.20 ₸; cost of sales 12 × 400 = 4,800 ₸. In the SNT and ESF for this sale, instead of 12 code lines there will be one box code — this is precisely the benefit of aggregation.
5. Types of operation
Depending on the release and the selected type, the document covers:
- Aggregation — assembling a new KITU from individual KMs.
- Re-aggregation — assembling an aggregate from lower-level aggregates (boxes → into a pallet).
- Additional nesting — adding codes to an already existing aggregate.
- Removal — removing individual codes from an aggregate (partial disaggregation).
Complete disaggregation of an aggregate is usually done with a separate "Disaggregation outside production" document.
6. What is generated upon posting
There are no Dr/Cr entries. The following are generated:
- Movements in the marking registers — linking the nested KMs to the KITU code, changing the status of the codes to "in aggregate", updating the code balances at the warehouse.
- An electronic message to IS CED M — via the "Send" button. After successful processing, the document status changes to "Accepted", the aggregate code becomes "active". Until the receipt is obtained, the aggregation cannot be considered complete.
- Readiness of the code for use in subsequent SNTs and shipment documents as a single object.
7. Printed forms
- Aggregate label (KITU) — to stick on the box/pallet, with a human-readable code and a barcode/DataMatrix.
- List of nested marking codes — the aggregate composition for reconciliation at the warehouse.
- Print of the document — the form of the aggregation document itself.
The specific composition of the "Print" button depends on the release; the aggregate label is the basic form you will use most often.
8. Common errors
| 1C message | Cause and how to fix it |
|---|---|
| "Marking code not found in balances by warehouse" | The code was not received or is at a different warehouse. Check the receipt/entry into circulation, specify the correct warehouse. |
| "Marking code is already part of another aggregate" | The bottle has already been packed in another box. First remove the code from the old aggregate, then add it to the new one. |
| "Code is not in circulation" | The code has been withdrawn, blocked, or not yet put into circulation. Clarify the status in the IS CED M personal account. |
| "Aggregate code (KITU) not filled in" | You forgot to scan/generate the packaging code. Fill in the field and re-post. |
| "Exchange error with IS CED M" / no response | A problem with the digital signature or certificate, or the service is unavailable. Check the validity period and signature profile in the exchange settings, resend. |
| "Nesting level violated" | You are trying to nest a box into a box or a KM into a pallet directly. Bring the packaging type into line with the level of the codes. |
9. FAQ
Does the document generate accounting entries? No. Aggregation is a packing operation that does not affect finances. Dr/Cr entries arise later, upon the sale of the aggregated goods (Dr 1210 Cr 6010, VAT Dr 1210 Cr 3130, cost of sales Dr 7010 Cr 1330).
How does "outside production" differ from aggregation in production? "Outside production" is for distributors and wholesalers who aggregate already finished labeled goods rather than manufacture them. The manufacturer uses the production variant of aggregation.
Can a code be added to an already sent aggregate? Yes — through additional nesting (changing the aggregate composition). The change goes to IS CED M again. You cannot simply add a line to a posted document without resending.
What should I do if the box was unpacked? Prepare a removal of codes or a disaggregation. Then the codes will again become available for separate shipment or for a new aggregate.
Is it mandatory to send data to IS CED M immediately? You can post immediately, but until the acceptance receipt arrives, the aggregate code is not considered active. Shipping the box by KITU before confirmation is risky — the SNT may not pass.
Why is it beneficial to specify the KITU instead of the codes when shipping a box? One code instead of dozens speeds up the preparation of the SNT and reduces the risk of scanning errors. The system "unfolds" the aggregate composition automatically.
Does the document affect the goods balances on account 1330? No. The quantity and cost of goods on 1330 do not change — only the "packaging" status of the marking codes changes. The write-off from 1330 occurs upon sale.
What VAT rate applies to the subsequent sale of the box? The standard VAT rate in the RK in 2026 is 16%. It is charged in the sales document, not in the aggregation.
Can a KITU code be generated directly in the document? Yes, with the aggregate code generation button. Or scan a ready SSCC label if the box is already labeled.
What should I do if the goods are not subject to marking? Then the document is not needed at all — ship with a regular sale. Aggregation is only for goods from the mandatory marking list.
10. Related documents
Entered on the basis of / after:
- "Receipt of marking codes" and "Entry into circulation IS CED M" — the codes must first end up in your balances.
- Capitalization/receipt of labeled goods.
On the basis of aggregation, the following are prepared:
- SNT (accompanying waybill for goods) — with the aggregate code specified.
- Sales of goods and services — shipment of the box to the buyer (this is where the entries and the ESF appear).
- "Disaggregation outside production" / "Removal from aggregate" — upon unpacking.
How to find out your release
"Help" → "About the program". It shows the version of the "1C:Enterprise" platform and the configuration release. This guide is compiled for release 3.0.74.2. If you have a different number, the set of fields and the composition of operations may differ; check against the built-in help (F1) for the document.
The guide is prepared for the "Accounting for Kazakhstan" configuration, edition 3.0, release 3.0.74.2.