1. Identification of the Object
| Parameter | Value |
|---|---|
| Object Type | Document (Document) |
| Name | ApplicationOfMarkingCodesInSUSISMPK |
| Full Path | Document.ApplicationOfMarkingCodesInSUSISMPK |
| Synonym | — |
| Configuration | Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) |
| Subsystem | 1C Service: Marking (IS MPT) / Integration with IS MPTK |
| Object Class | Integration document (exchange with external GIS), without accounting entries |
Purpose. The document registers the fact of applying marking codes to tobacco products within the framework of the Kazakhstan monitoring system for tobacco production — SUS IS MPTK (Order Management Station of the Information System for Marking and Traceability of Goods). It is used by manufacturers and importers for reporting to the regulator on the use of codes issued by the state system. The document is integrational: it does not change the accounting registers of 1C and does not generate accounting entries, but serves to synchronize data between the 1C accounting system and the external SUS system. It is created based on the order of marking codes after receiving permission from the regulator. It is used periodically — with each production batch of marked products.
Where to find in 1C. Section “1C Service: Marking (IS MPT)” → “Application of marking codes (SUS)”.
Navigation link: e1cib/list/Document.ApplicationOfMarkingCodesInSUSISMPK
2. Header Attributes and Table Parts
2.1. Mandatory Header Attributes
| Attribute | Purpose |
|---|---|
Organization |
The manufacturing/importing organization on behalf of which the report is generated in SUS. Defines the participant in the turnover (registration data in IS MPTK). |
ProductType |
The type of marked product (tobacco products). Defines the commodity group and the rules for generating codes. |
ProductionBatchNumber |
The number of the production batch to which the applied codes relate. |
ExpirationDate |
The expiration date of the batch product — transmitted as part of the report in SUS. |
ProductionLineIdentifier |
The identifier of the production line on which the application was performed. |
If any of the listed attributes are not filled in, 1C will not allow the document to be processed and will issue an error “Field … is not filled in”. Additionally, the organization’s filling is controlled when entering based on (see p. 4, error “Organization not specified!”).
2.2. Table Part “Products”
| Column | Mandatory | Purpose |
|---|---|---|
GTIN |
Mandatory | Global Trade Item Number (GTIN) under which the marking codes were issued. |
IdentificationCode (marking codes) |
Filled by import/input | The actual marking codes (Data Matrix) applied to the product. The uniqueness key within the document — when re-adding a code, a duplicate message is issued. |
The table part is the main “body” of the report: it is the list of identification codes that is exported to SUS. Uniqueness is controlled by the method
FindByIdentificationCodewhen adding from a file (see p. 4).
3. Forms
| Form | Purpose |
|---|---|
DocumentForm |
Main editing form: filling in header attributes, working with the table part of codes, importing/exporting codes, sending the report to SUS and processing responses. |
ListForm |
List of documents “Application of marking codes (SUS)” filtered by organization, processing status in SUS, period. |
| Selection / Basis Form | Used to select the basis document (order of marking codes) when entering based on. |
4. Key Module Procedures
Below are the procedures confirmed by evidence (release 3.0.68.1; in 3.0.74.2 the logic is similar — current procedure names require verification during targeted refactoring).
Form module Form.DocumentForm:
AddMarkingCodeFromFile— adds marking codes from the imported file. Before adding, it checks the uniqueness of the code in the document: conditionNot FindByIdentificationCode(CodeStructure.MarkingCode) = Undefined→ issues the message “Marking code %1 was not added because it is already present in the document!”. Implements scenario 3.3 (importing codes from a file).ExportMarkingCodesToCSVAndFinish— generates and saves the list of marking codes in CSV. If it is impossible to generate the list, it issues “Failed to generate the list of marking codes for export.”. Implements scenario 3.4 (exporting codes to a file).SelectBasisDocument— selection of the basis document (order of codes). Controls the filling of the organization:Not ValueFilled(Object.Organization)→ “Organization not specified!”.
Manager module ManagerModule:
GetInformationByApplicationStatusesContinue— scheduled retrieval and synchronization of report processing statuses from SUS (scenario 3.6). In case of a failure of the scheduled task, it generates messages “Error executing scheduled task "%TaskName%":” and “%TaskName%”.
No processing handler is present. The document does not contain the procedure ProcessingHandler and does not perform movements in accounting registers (see p. 5).
Standard handlers for this type of object, not reflected in evidence, but typical:
FillingHandler(filling when entering based on),FillingCheckHandler(control of mandatory attributes), handlers for sending/receiving responses to the external system through the integration module of IS MPTK.
5. Processing and Movements
The document does not generate accounting entries and does not have the procedure ProcessingHandler. This is an integration object: it does not change the accounting registers of 1C, but serves to synchronize data with the external state system SUS IS MPTK. “Processing” here is equivalent to the fixation of the report and its sending/acceptance in the external system, rather than the formation of accounting or tax movements.
Accordingly, for this document no entries and records in accounting registers arise. No accounts from the standard chart of accounts of the RK are directly affected by the document.
Where the amounts related to the products are reflected (for reference, not movements of this document). Economic operations related to marked tobacco products are reflected by other documents of the configuration that use the standard chart of accounts of the RK:
| Operation | Document (example) | Standard Accounts of RK |
|---|---|---|
| Receipt/accounting of goods (products) | Receipt, Production Report | 1330 “Goods” |
| Sale of products | Sale of goods and services | Debit 1210 “Short-term receivables from buyers” — Credit 6010 “Revenue from sales” |
| VAT on sales | Sale / ESF | Credit 3130 “VAT payable” at the rate of 16% (VAT rate of the RK from 2026) |
| Cost of goods sold | Sale | Debit 7010 “Cost of goods sold” — Credit 1330 |
| Payment to supplier | Payment documents | Debit 3310 “Payables to suppliers” — Credit 1030 “Cash in current accounts” |
Numerical norms of the RK for 2026 (for accounting documents of the configuration, not for this document): MRP = 4,325 ₸, MZP = 85,000 ₸, VAT rate = 16%; basic tax deduction for individual income tax = 30 MRP/month (not more than 360 MRP/year); individual income tax 10% up to 8,500 MRP annual income and 15% above; OPE 10% (base ceiling 50 MZP), OPEP 3.5%, VOSMS 2%, OSMS 3%, CO 5%, social tax 6%. This document does not perform these calculations — they are provided as a country context of the configuration.
Electronic documents. To accompany the turnover of marked products in the RK, electronic invoices (ESF) and accompanying invoices for goods (SNT) are used. The marking code application document interacts specifically with the SUS IS MPTK, while ESF/SNT are formed by related documents of sale/movement.
6. Related Objects and Entry Based On
Entry based on (basis of the document):
- Order of marking codes (SUS) — the main basis document. The application is created after receiving codes from SUS and their physical application to the product (scenario 3.1). When selecting the basis, the filling of the organization is checked.
Related objects and subsystems:
- Subsystem “1C Service: Marking (IS MPT)” / integration with IS MPTK — transport of exchange, connection settings, processing responses from SUS.
- Documents of sale/movement of marked products (generate ESF, SNT) — use the results of marking in turnover.
- Scheduled task for synchronization of application statuses (scenario 3.6) — updates the statuses of sent reports.
Main working scenarios (from evidence):
- Creation of a report based on the order of marking codes (3.1).
- Sending the report to the SUS system after filling in the attributes and table part (3.2).
- Importing marking codes from a file (3.3).
- Exporting marking codes to a file / CSV (3.4).
- Processing a rejected report — in case of refusal by SUS (incorrect data, reused codes) (3.5).
- Synchronization of statuses from SUS by scheduled task (3.6).
7. Extension Points
- Configuration extension (Extensions). Borrowing the form module
DocumentFormand manager module to redefine the logic of importing/exporting codes and sending to SUS without removing from support. - Form event handlers.
BeforeWriting,AfterWriting, import/export command handlers — to add custom validation of marking codes or logging of exchanges. - Filling check. Supplementing
FillingCheckHandlerwith custom rules (for example, checking GTIN against the nomenclature/reference participant). - Exchange with SUS. Interception points in the integration module of IS MPTK: forming the report package, parsing the response, reacting to rejection (scenario 3.5) and synchronizing statuses (scenario 3.6).
- Additional attributes/information (BSP mechanism) — if necessary, to expand the data set of the batch without modifying the document metadata.
Since the document does not perform processing, extension points related to movements in registers are absent — it is necessary to expand the logic of exchange and validation.