---
title: "Document \"AcceptanceTransferActISMPTK\" — Technical Description"
country: KZ
lang: en
author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti)
date: 2026-09-23
canonical: https://buhgpt.kz/suraqtar/dokument-aktpriemaperedachiismptk-tehnicheskoe-opisanie-en
source: BuhGPT
---

# Document "AcceptanceTransferActISMPTK" — Technical Description

> **TL;DR:** 1. Identification Parameter Value Object type Document (Documents) Name АктПриемаПередачиИСМПТК Full name Документ.АктПриемаПередачиИСМПТК Synonym — (not set) Configuration Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) Country Republic of Kazakhstan Settlement curr

---

1. Identification

Parameter
Value

Object type
Document (Documents)

Name
АктПриемаПередачиИСМПТК

Full name
Документ.АктПриемаПередачиИСМПТК

Synonym
— (not set)

Configuration
Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2)

Country
Republic of Kazakhstan

Settlement currency
tenge (₸)

Purpose. The document is intended for creating and registering acceptance/transfer acts of marked goods in the Information System for Monitoring Traceability of Tobacco Products of Kazakhstan (IS MPT). It is used in two directions of document flow:

- incoming acts — upon receipt of goods from a supplier who has already registered the act in IS MPT;

- outgoing acts — upon shipment of marked goods to a buyer.

The document ensures bilateral electronic document flow with the state registry, recording of marking codes (MC), and identification of discrepancies between declared and actually accepted/transferred goods. It is used daily by logistics and warehouse department staff for each operation of accepting/transferring marked products.

Where to find it in 1C: section "1C Service: Marking (IS MPT)" → "Acceptance/Transfer Act (IS MPT)". The menu commands "Acceptance/Transfer Acts (incoming)" and "Acceptance/Transfer Acts (outgoing)" are also available separately.

Navigation link: e1cib/list/Документ.АктПриемаПередачиИСМПТК

2. Header attributes and tabular sections

Header attributes

Attribute
Purpose
Required

ВидОперации
Direction of document flow (incoming / outgoing act), determines the fill-in logic and exchange with IS MPT
yes

ТипАкта
Act type: primary (acceptance/transfer act) or corrective (correction of a previously sent act)
yes

Поставщик
Counterparty-sender of goods (for an incoming act — the supplier, for an outgoing act — the transferring party)
yes

ПоставщикНаименование
Supplier name in the IS MPT act attributes
yes

ПоставщикИдентификационныйНомер
Supplier identification number (BIN/IIN) for reconciliation in IS MPT
yes

Получатель
Counterparty-recipient of goods
yes

ПолучательИдентификационныйНомер
Recipient identification number (BIN/IIN)
yes

If any of the listed fields is not filled in, 1C will not allow posting the document and will issue an error of the form "Field … is not filled in".

In addition to the required ones, the header typically contains service attributes of the exchange state: the number and date of the act in IS MPT, the document status (draft / sent / confirmed / rejected), the act identifier in the state system, as well as the date and time of the last synchronization.

Tabular section "Discrepancies"

Records the result of reconciling declared and actually accepted marking codes.

Column
Purpose
Required

СтатусСверкиКода
Status of matching the marking code: matched / missing / extra / discrepancy by product
yes

The tabular section also typically stores the marking code itself (GTIN/SGTIN), the product name, and the quantity — for generating the discrepancy report during acceptance.

Service tabular section "Typical errors"

Used to record the results of document validation before sending to IS MPT.

Column
Type
Purpose

Текст
xs:string
Validation error text

Поле
xs:string
Name of the field in which the error was detected

3. Forms

The specific composition of forms is not provided in the evidence; below is a set typical for an IS MPT exchange document.

Form
Purpose

Document form (ФормаДокумента)
Main form for viewing and editing the act: header, marking codes, "Discrepancies" tabular section, IS MPT exchange commands

List form (ФормаСписка)
Lists of incoming and outgoing acts with filtering by exchange status and operation direction

Selection form (ФормаВыбора)
Picking an act when entering on the basis of or in related processors

For IS MPT exchange documents, the document form additionally contains commands: "Send to IS MPT", "Get status", "Accept act", "Reject act", "Create corrective act", as well as a panel displaying validation errors from the service tabular section "Typical errors".

4. Key module procedures

There are no explicit BSL fragments (path:line) in the evidence, so below are the typical handlers of an IS MPT exchange document of this type.

Object module:

- ОбработкаПроверкиЗаполнения — control of the required header attributes (ВидОперации, ТипАкта, Поставщик, ПоставщикНаименование, ПоставщикИдентификационныйНомер, Получатель, ПолучательИдентификационныйНомер) and the СтатусСверкиКода column in the "Discrepancies" tabular section; populating the service tabular section "Typical errors".

- ОбработкаПроведения — generating movements over the registers of the marking subsystem (see section 5). Does not generate accounting entries.

- ОбработкаЗаполнения — filling in attributes when entering on the basis of a sales/receipt document.

Form module:

- ПриСозданииНаСервере — configuring the availability of exchange commands depending on ВидОперации and the document status.

- Exchange command handlers — serialization of act data into IS MPT format, calling the integration service, parsing the response and updating the status, automatic reconciliation of codes upon acceptance of an incoming act.

Verify the exact signature and presence of procedures against the specific build 3.0.74.2 — the composition of exchange handlers is version-dependent.

5. Posting and movements

The document does not generate accounting entries. This is an electronic document flow document with the IS MPT marking system. Movements over the ISMPTK registers (marking code registry, code statuses) are performed at the level of the IS MPT integration subsystem, not in the document itself.

Accordingly, the accounts of the standard RK chart of accounts (1210 — short-term accounts receivable from buyers, 1330 — goods, 3310 — accounts payable to suppliers, 3130 — VAT payable, 6010 — revenue from sales, 7010 — cost of sales) are not used by this document. The financial consequences of shipment/receipt and VAT (the VAT rate in RK for 2026 is 16%) are reflected by the associated goods documents (sales, receipt), on the basis of which the act is created, as well as electronic ESF (IS ESF) and SNT.

When posted, the document records:

- registration/write-off of marking codes in the MC registry of the IS MPT subsystem;

- changes in code statuses (accepted, transferred, in discrepancy);

- the reconciliation result by the "Discrepancies" tabular section.

6. Related objects and entry on the basis of

Usage scenarios (from evidence):

- 3.1. Creating an outgoing act on the basis of a goods transfer document — upon shipment of marked goods to a buyer after processing a sales document.

- 3.2. Sending an outgoing act to IS MPT — after filling in all attributes and marking codes, before the actual shipment.

- 3.3. Accepting an incoming act with automatic reconciliation of codes — upon receipt of goods from a supplier who has registered the act in IS MPT.

- 3.4. Rejecting an incoming act — upon detection of critical discrepancies or refusal of acceptance.

- 3.5. Creating a corrective act — correcting errors in a previously sent act before its confirmation by the recipient.

Entry on the basis of: the document is typically entered on the basis of goods documents (sales of goods and services — for an outgoing act; receipt of goods — for an incoming one), with automatic filling of the supplier, recipient, and the list of marking codes.

Related subsystem objects: registers of marking codes and IS MPT statuses, exchange documents with IS ESF (ESF) and SNT, catalogs of counterparties and items with an indication of the marked-goods attribute.

7. Extension points

- Event subscriptions ОбработкаПроверкиЗаполнения, ОбработкаПроведения, ОбработкаЗаполнения of the document — for adding custom marking code checks and reconciliation rules.

- Configuration extension of the document form — adding exchange commands/fields without removing from support.

- Fill-in rules on entry on the basis of — configuring the transfer of attributes from goods documents.

- IS MPT integration service — overriding the serialization/deserialization of the act and parsing of response statuses.

- Additional attributes and information (SSL mechanism) — for internal analytics on acts.

Version-specific (to be clarified for build 3.0.74.2) remains the exact format of exchange with IS MPT and the composition of exchange commands on the form — they change following the requirements of the state marking system.

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