1. Identification
| Parameter | Value |
|---|---|
| Object Type | Document (Documents) |
| Name | AggregationOfLabelingCodesSUSISMPK |
| Full Name | Document.AggregationOfLabelingCodesSUSISMPK |
| Synonym | — (set in the interface as “Aggregation of labeling codes (SUS)”) |
| Configuration | Accounting for Kazakhstan, ed. 3.0.74.2 |
| Subsystem | Integration with the Goods and Codes Labeling and Traceability System (ISMPK) |
Purpose. The document is intended for the formation and submission to the SUS (Order Management System / product lifecycle) of reports on the aggregation of labeling codes of goods in Kazakhstan. Aggregation is the process of combining individual units of goods, each with its own unique labeling code (LC), into a group package: box, pallet, transport unit. The document records the actual composition of the aggregate (which LCs are included in which package) before the shipment or movement of labeled products.
The exchange with SUS occurs in real-time with status tracking: Draft → Sent → Processed → Rejected. The document is of a reference-registration nature: it serves as a data transport for labeling to the external state system and is not a financial/accounting document.
Where to find in 1C: section “1C Service: Labeling (IS MPK)” → “Aggregation of labeling codes (SUS)”.
Navigation link: e1cib/list/Document.AggregationOfLabelingCodesSUSISMPK.
2. Header Attributes and Table Parts
2.1 Header Attributes
| Attribute | Purpose | Mandatory |
|---|---|---|
| Number, Date | Standard document identification | Automatically filled |
| Organization | The organization on behalf of which the aggregation is performed and the report is submitted to SUS | Mandatory |
| OrganizationIdentificationNumber | IIN/BIN of the organization under which the exchange with SUS takes place | Mandatory |
| ProductType | Product group of labeled goods (footwear, tobacco, water, etc.). Determines the rules for checking LCs | Mandatory |
| Status | Current state of the report in SUS: Draft, Sent, Processed, Rejected | Service |
| DocumentBasis | Document-basis for aggregation (production order, planned task, etc.) | Optional |
| Comment | User's arbitrary text | Optional |
If a mandatory attribute is not filled, the platform will not allow saving/conducting the document and will display the message “Field … is not filled”.
2.2 Table Parts
| Table Part | Purpose | Key Columns |
|---|---|---|
| LabelingCodes | Composition of the aggregate — list of individual LCs included in the package | IdentificationCode, GTIN, Nomenclature, AggregateCode (parent package), Status |
| Packages / Aggregates | List of created group packages (box/pallet) and their codes | PackageCode, PackageType, NumberOfAttachments |
The exact composition of the columns is version-specific — please check with the configurator of the specific release.
3. Forms
| Form | Purpose |
|---|---|
| DocumentForm | Main working form: header input, manual scanning/input of LCs, file upload, filling by GTIN, submission to SUS, status update, printing |
| ListForm | Journal of aggregation documents filtered by organization, date, processing status |
| Selection Form | Selecting a document from other objects (input based on, selection of basis) |
4. Key Module Procedures
Below are the handlers confirmed by evidence (release 3.0.68.1); signatures may differ in 3.0.74.2.
| Procedure / Module | What it does |
|---|---|
ManagerModule.GetInformationByAggregationStatusesContinue |
Asynchronously polls SUS by scheduled task and updates the statuses of sent reports. In case of failure, it writes to the log “Error executing scheduled task "%TaskName%"” |
Form.DocumentForm.AddNewCode |
Adds scanned/input LC to the table. Checks the compliance of the product group of the code with the document group; if they do not match — “Code belongs to product group %1, filling by product group %2 is expected” |
Form.DocumentForm.LoadLabelingCodesFromFileWithSeparatorsCompletion |
Parses a text file with LCs by separator. If the separator is not found (SeparatorPosition = 0) — “The specified file does not match the expected structure, data loading was not performed!” |
Form.DocumentForm.AddLabelingCodeFromFile |
Adds a single LC from the file with a check for duplicates via FindByIdentificationCode; if repeated — “Labeling code %1 was not added, as it is already present in the document!” |
Typical document handlers of this type (not confirmed by evidence, but characteristic):
FillingProcessing (filling by basis/GTIN), BeforeSaving/OnSaving (validation of LCs and statuses), form commands SendToSUS, UpdateStatus, Print.
5. Conducting and Movements
The document does not have conducting processing and does not generate movements in the registers. It is a reference-registration document for exchange with the external SUS system; it does not directly affect accounting and inventory records.
Accordingly, the document does not create accounting entries and records in accumulation registers. The financial consequences of operations with labeled goods are reflected by other documents of the configuration according to the typical chart of accounts of the RK, for example:
| Operation (other document) | Debit | Credit |
|---|---|---|
| Receipt of goods | 1330 “Goods” / 1420 “VAT to be refunded” | 3310 “Accounts payable to suppliers” |
| Sale: revenue | 1210 “Short-term receivables from customers” | 6010 “Revenue from sales” |
| Sale: VAT | 1210 | 3130 “VAT payable” (rate 16 %, 2026) |
| Sale: cost of goods sold | 7010 “Cost of goods sold” | 1330 “Goods” |
| Payment from the customer | 1030 “Cash in current accounts” | 1210 |
Numerical norms of the RK for 2026 for related calculations: VAT 16 %, MRP 4,325 ₸, MZP 85,000 ₸, basic deduction for PIT — 30 MRP/month (not more than 360 MRP/year), PIT 10 % (15 % over 8,500 MRP annual income), OPE 10 % (base ceiling 50 MZP), OPEP 3.5 %, VOSMS 2 %, OSMS 3 %, SO 5 %, social tax 6 %. They are not applied to the aggregation document itself, but are provided for the context of the RK configuration.
6. Related Objects and Input Based On
- Document-basis. Aggregation can be performed based on a production order, planned task, or another document of the movement of labeled goods (attribute
DocumentBasis, scenario 3.7). - Nomenclature / GTIN. Labeling codes are matched with the nomenclature directory via GTIN; filling by GTIN — group addition of units with one GTIN and different individual LCs (scenario 3.5).
- Electronic documents of the RK. In the turnover chain of labeled goods, the document is linked to the issuance of electronic invoices (ESF) (IS ESF) and SNF (accompanying invoices for goods) — but they are formed as separate configuration objects, not by this document.
- External SUS system. The main external counterparty for exchange; statuses are updated by scheduled task via
ManagerModule.
7. Extension Points
- Scheduled task for polling statuses (
GetInformationByStatuses…) — a point for refining the logic of retries, logging, and processing subscription limits. - Loading LCs from file — extendable parser (
LoadLabelingCodesFromFileWithSeparators…): new formats/separators can be added. - Product group check in
AddNewCode— a point for additional validation of LCs by types of products. - FillingProcessing / filling by GTIN — extension of group addition rules and nomenclature matching.
- Print forms — adding custom layouts of the aggregate composition summary (scenario 3.6) through extension or BSP printing mechanism.
The recommended way to refine is to extend the configuration by subscribing to form events and overriding the procedures of the manager module, without removing the configuration from support.