---
title: "Document \"Scanning of Goods and SMPTK\" - Technical Description"
country: KZ
lang: en
author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti)
date: 2026-09-07
canonical: https://buhgpt.kz/suraqtar/dokument-skanirovanietovarovismptk-tehnicheskoe-opisanie-en
source: BuhGPT
---

# Document "Scanning of Goods and SMPTK" - Technical Description

> **TL;DR:** 1. Identification of the Object Parameter Value Type of metadata Document (Documents) Object name ScanningGoodsAndISMPK Full path Document.ScanningGoodsAndISMPK Alias — (not set; displayed as “Scanning goods ISMPK”) Configuration Accounting for Kazakhstan, ed. 3.0.74.2 Country

---

1. Identification of the Object

Parameter
Value

Type of metadata
Document (Documents)

Object name
ScanningGoodsAndISMPK

Full path
Document.ScanningGoodsAndISMPK

Alias
— (not set; displayed as “Scanning goods ISMPK”)

Configuration
Accounting for Kazakhstan, ed. 3.0.74.2

Country of accounting
Republic of Kazakhstan, tenge (₸)

Purpose
Registration of the fact of scanning the marking codes (DataMatrix / barcodes) of marked products for subsequent transfer to the state system ISMPK (Information System for Marking and Traceability of Goods of the RK) during acceptance, shipment, and inventory.

Where to find in 1C

- Navigation link: e1cib/list/Document.ScanningGoodsAndISMPK

- Interface: section “Service → 1C: Marking (IS MPK)” → “Scanning goods ISMPK”.

The document is technical (registration) rather than financial: it records the physical act of scanning and ensures traceability, but does not generate accounting entries for cost/revenue. The cost and tax movements of the goods are performed by related trade documents (sales, receipts, inventory).

2. Attributes of the Header and Table Parts

2.1 Header Attributes (Purpose of Fields)

Attribute
Purpose

Number, Date
Standard document attributes; identification and chronology of the scanning operation.

Organization
The organization on behalf of which the operation with the marked goods is performed; determines the accounting policy and participant in ISMPK.

Warehouse
The place (warehouse/department) where the scanning was performed; used for linking to warehouse operations.

OperationType / TransactionType
Context of scanning: acceptance, shipment, inventory, withdrawal from circulation. Affects the further transfer of statuses of codes to ISMPK.

ReferenceDocument
Reference to the trade document within which the scanning is performed (receipt, sale, etc.).

Identifier
Technical identifier of the scanning session/package for synchronization with external sources (mobile application, TSD, WMS). Key integration field.

Responsible, Comment
Service attributes for audit and explanations.

2.2 Table Part “NomenclatureCoded”

The main table of the document is a line-by-line list of scanned marking codes.

Column
Purpose

MarkingCode / IdentificationCode
Read DataMatrix code (full GS1 code). Key value for forming the transfer record.

Nomenclature
Matched nomenclature item (when recognizing GTIN).

SGTIN / GTIN
Components of the code: product identifier and serial number of the item.

Status
State of the code in circulation (in circulation, withdrawn, awaiting confirmation).

Quantity
Typically = 1 for item-level marking; for aggregated packages — the number of items.

Identifier (row)
Technical key of the row for matching with the external system.

Numerical/cost indicators (price, VAT, cost) are not calculated in this document — it operates with codes, not amounts.

3. Forms

Form
Purpose

List form
View the log of scanning documents, search for a specific marking code, control staff work and operation history (scenario 3.4).

Document (object) form
Main input/editing: filling in the header and line-by-line input of codes, manual correction of incorrectly entered codes (scenario 3.3).

Selection/scanning form
Mass input of codes via reader/TSD: sequentially adding rows to “NomenclatureCoded” in streaming scanning mode (scenario 3.2).

Selection form
Selecting a document when entering based on and in related processes.

4. Key Procedures of Modules

In the attached evidence, the original BSL code of procedures is not provided, so below are typical document handlers of this type in BK 3.0. Specific lines of the module should be clarified according to version code 3.0.74.2.

Object Module

- ProcessConducting(Failure, ConductingMode) — formation of records in the register DocumentTransfer for each line of the table part “NomenclatureCoded”; queuing codes for export to ISMPK.

- ProcessFilling(FillingBasis, FillingData) — filling in the header and table of codes when entering based on the trade document.

- ProcessDeletingConducting(Failure) — removing transfer records when canceling conducting.

- CheckFilling() / ProcessCheckFilling — control of the correctness and uniqueness of marking codes, non-empty list of rows.

Form Module

- Event handlers for the scanning field (BarcodeFieldOnChange / external equipment event handling) — receiving code from the scanner/TSD, parsing DataMatrix, adding a row.

- Handlers for loading a package by Identifier — receiving data from the mobile application/WMS (scenario 3.5).

5. Conducting and Movements

5.1 Register “DocumentTransfer”

When conducting, the document generates movements in the specialized register DocumentTransfer (register of queues/facts of exchange with ISMPK):

- for each code from “NomenclatureCoded” a separate record is created;

- the following are recorded: date/time of the operation, marking code, reference to the registering document, Identifier of synchronization, transfer status (awaiting export → sent → confirmed);

- purpose — forming a queue for export to the state system and ensuring traceability.

5.2 Accounting Entries

The scanning document does not generate entries in the accounting register — it does not change the cost assessment of inventories. Accounting movements for marked goods are performed by related documents according to the standard chart of accounts of the RK. For reference (numbers and rates — RK, 2026):

Operation (related document)
Debit
Credit

Receipt of goods
1330 “Goods” / 1420 VAT to be credited
3310 “Accounts payable to suppliers”

Sale — revenue (VAT 16%)
1210 “Accounts receivable from customers”
6010 “Revenue from sales”, 3130 “VAT payable”

Sale — cost
7010 “Cost of sales”
1330 “Goods”

Receipt of payment
1030 “Cash in current accounts”
1210

For reference on RK-2026 (for related calculations, not for this document): VAT rate 16%; MRP = 4,325 ₸; MZP = 85,000 ₸; basic tax deduction for PIT = 30 MRP/month (not more than 360 MRP/year); PIT 10% up to 8,500 MRP annual income and 15% above; OPE 10% (base cap 50 MZP), OPEP 3.5%, VOSMS 2%, OSMS 3%, SO 5%, social tax 6%. Electronic document circulation: ESF (IS ESF) and SNT.

5.3 Electronic Transfer

After conducting, codes from the register DocumentTransfer are exported to ISMPK by a scheduled task/exchange processing. Statuses (confirmation of receipt of codes by the state system) are returned and updated in the register. Scanning data is also used when issuing SNT and ESF for marked products.

6. Related Objects and Input Based on

- Basis documents: documents for the receipt/sale of goods and services, transfer, inventory, withdrawal from circulation — the scanning document can be filled out from them and is linked through ReferenceDocument.

- Input based on: based on the scanning document, SNT and ESF can be formed for the scanned codes; conversely, scanning is entered based on the trade document.

- Register DocumentTransfer — receiver of movements and source of data for export to ISMPK.

- External sources: mobile scanning application, data collection terminals (TSD), WMS — exchange via the Identifier attribute.

- Directories: “Nomenclature” (matching GTIN), “Organizations”, “Warehouses”.

7. Extension Points

- Subscriptions to conducting events — additional validation of codes, integration with external marking verification services.

- Extension of the object/form module — enhancement of DataMatrix parsing, custom rules for matching codes with nomenclature, auto-filling from external packages by Identifier.

- Scheduled exchange tasks — setting the frequency and handling errors of export to ISMPK, re-sending unconfirmed codes.

- Handlers for external equipment — connecting scanners/TSD, streaming mass scanning mode.

- Additional attributes/information (BSP mechanism) — extending the header without changing the configuration.

---
_BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_