--- title: "Document \"AktPriemaPeredachiISCEDM\" (IS TSEDM) — Accounting for Kazakhstan 3.0.74.2" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-08 canonical: https://buhgpt.kz/suraqtar/dokument-aktpriemaperedachiiscedm-is-cedm-buhgalteriya-dl-en source: BuhGPT --- # Document "AktPriemaPeredachiISCEDM" (IS TSEDM) — Accounting for Kazakhstan 3.0.74.2 > **TL;DR:** 1. Identification Parameter Value Object type Document (Documents) Name АктПриемаПередачиИСЦЭДМ Full name Документ.АктПриемаПередачиИСЦЭДМ Synonym — (not set in metadata) Configuration Accounting for Kazakhstan, revision 3.0.74.2 Accounting currency Tenge (₸) Purpose. The docu --- 1. Identification Parameter Value Object type Document (Documents) Name АктПриемаПередачиИСЦЭДМ Full name Документ.АктПриемаПередачиИСЦЭДМ Synonym — (not set in metadata) Configuration Accounting for Kazakhstan, revision 3.0.74.2 Accounting currency Tenge (₸) Purpose. The document is the central object of electronic document interchange of marked products in Kazakhstan through the IS CEDM system (Information System for Centralized Electronic Document Interchange of Marked Goods). It is used to register the transfer/receipt of marked goods (medicines, tobacco products, etc.) between counterparties with subsequent synchronization with the state marking system. The document operates in two modes: - Outgoing — the organization ships marked goods to a counterparty and notifies IS CEDM about the transfer of marking codes; - Incoming — the organization receives goods, the supplier has sent an act through IS CEDM, and receipt needs to be confirmed. The frequency of use is high in pharmaceutical and tobacco organizations required to work with the marking system. Where to find it in 1C: the "Sales" section → "Act of acceptance/transfer (IS CEDM)" (menu items "Acts of acceptance/transfer (incoming/outgoing) (IS CEDM)"). Navigation link: e1cib/list/Документ.АктПриемаПередачиИСЦЭДМ 2. Header attributes and tabular sections 2.1. Mandatory header attributes The fields listed below are checked for completeness when posting/writing — if left empty, 1C displays an error of the form "Field … is not filled in" and does not allow the document to be posted. Attribute Purpose ВидОперации Document mode: incoming (receipt) / outgoing (shipment). Determines the direction of exchange with IS CEDM and the roles of the parties. Поставщик The counterparty that sends the goods. ПоставщикНаименование Supplier's name (for printing and transfer to IS CEDM). ПоставщикИдентификационныйНомер Supplier's BIN/IIN. Получатель The counterparty that receives the goods. ПолучательНаименование Recipient's name. ПолучательИдентификационныйНомер Recipient's BIN/IIN. The attributes are duplicated "by value" (name + identification number) in addition to the reference to the counterparty, because the act records the parties' details at the moment of exchange — this way the document remains self-sufficient for transfer to IS CEDM even if the counterparty card is subsequently changed. 2.2. Period/status attributes (typical for IS CEDM electronic documents) In addition to the mandatory ones, a document of this kind usually contains service integration attributes: the document date/number, the organization, the document identifier in IS CEDM, the synchronization status, the date of sending/receiving. These fields ensure tracking of the act's state relative to the state system (see the "Request the act status from IS CEDM" scenario). 2.3. "Goods" tabular section (marking codes) The tabular section stores the list of goods being transferred/received with marking codes (Data Matrix / GTIN). It is filled in manually, from a basis document, or by bulk upload from a data collection terminal (DCT). 2.4. "Errors" tabular section A service tabular section for storing validation errors when sending to IS CEDM. Name Type Purpose Текст String The text of the error received during validation/sending. Поле String The path to the document field containing the error. It is filled in automatically from the response of the IS CEDM service; it serves for navigating the user to the problematic attribute. 3. Forms The exact composition of forms is determined by the object's metadata. For an IS CEDM document, the typical set is: Form Purpose Document form The main form for entering/editing the act: the header (parties, operation type), the tabular section with marking codes, service errors, IS CEDM exchange commands. List form The list of acts with filtering by operation type (incoming/outgoing) and synchronization status; from it, separate lists of incoming and outgoing acts are opened. Choice form Selecting an act from other configuration objects. Integration commands are available from the forms: sending to IS CEDM, requesting status, uploading codes from a DCT, generating a notification of discrepancies/correction. 4. Key module procedures Evidence with exact BSL paths and line numbers for this object is not attached. Below are the typical handlers for a document of this kind; the specific procedure names should be clarified against the object module of the specific delivery. Object module: - ОбработкаЗаполнения — filling in attributes when entering on the basis of a document (transferring the parties and marking codes from the basis document). - ОбработкаПроверкиЗаполнения — control of mandatory attributes (ВидОперации, Поставщик/Получатель and their names/identification numbers); generation of user errors "Field … is not filled in". - ПередЗаписью / ПриЗаписи — recording service integration attributes, updating the status. - ОбработкаПроведения — see section 5 (does not generate movements). Form module: - Handlers of IS CEDM exchange commands: sending the act, requesting status, receiving an incoming act, generating a correction/notification of discrepancies. - Handler for uploading marking codes from a DCT into the tabular section. - Filling in and displaying the "Errors" tabular section based on the service response, navigating to the problematic field by the Поле value. 5. Posting and movements The document does not generate register movements. This is an informational/electronic document for exchange with IS CEDM: it records the fact of transferring/receiving marking codes and the synchronization state, but does not produce accounting entries or records in accumulation registers. Accordingly, the document: - does not make entries on the accounts of the RK chart of accounts; - does not directly affect warehouse, inventory, or tax accounting. Accounting and tax accounting of goods movement is documented by separate primary documents (sale/receipt), to which the IS CEDM act is linked as a basis. For reference — the standard entries of the accompanying inventory documents of the "Accounting for Kazakhstan" configuration (RK figures/accounts as of 2026): Sale of marked goods (outgoing scenario, separate document): Dr Cr Content 1210 6010 Income from sales recognized (short-term accounts receivable from customers ↔ income) 6010 (incl. VAT) 3130 VAT payable at the rate of 16% 7010 1330 Cost of goods sold written off Receipt of marked goods (incoming scenario, separate document): Dr Cr Content 1330 3310 Goods received (accounts payable to suppliers) 1420/… 3310 VAT on acquisition (16%), where entitled to offset Payment is reflected through account 1030 (money in current accounts). The VAT rate in the RK for 2026 is 16%. Electronic fiscal documents (ESF in the IS ESF, SNT — the accompanying waybill for goods) are issued for inventory operations separately; the IS CEDM act operates within the marking loop and does not replace the ESF/SNT. 6. Related objects and entry on the basis Typical exchange scenarios (defining the document's links): - Creating an outgoing shipment act on the basis of a waybill — when marked goods are shipped, the act is entered on the basis of an inventory sale document/waybill, and the marking codes are transferred into the tabular section. - Accepting an incoming act from a supplier — the act arrives from IS CEDM, and receipt needs to be confirmed. - Correcting the act after discrepancies are found — in case of shortage/surplus, the recipient generates a Notification of discrepancies, and the supplier corrects the act. - Bulk upload of marking codes from a DCT — importing scanned codes into the act's tabular section. - Requesting the act status from IS CEDM — updating the synchronization status. Related objects: - Inventory accounting documents (sale/receipt) — bases/related documents; - ESF (IS ESF), SNT — accompanying electronic documents for the same inventory operation; - Counterparties — the parties of the act (Supplier/Recipient); - Exchange with IS CEDM — integration services (sending, statuses, discrepancies). Entry on the basis: the act can be entered on the basis of a shipment document/waybill (outgoing scenario) with transfer of the parties and marking codes. 7. Extension points - Posting/writing handlers (ПередЗаписью, ПриЗаписи, ОбработкаПроверкиЗаполнения) — for additional control of attributes and statuses. - Fill handler (ОбработкаЗаполнения) — for non-standard rules of entry on the basis. - Form commands for exchange with IS CEDM — extending the logic of sending/receiving/requesting status, customizing the processing of the "Errors" tabular section. - Upload from a DCT — adapting the import format of marking codes. - Event subscriptions and configuration extensions — for adding integration attributes and links to inventory documents without removing the configuration from support. Version-specific (requires verification against the specific delivery 3.0.74.2): the exact names of the module procedures, the full composition of the service integration attributes, and the set of forms — to be clarified against the object's metadata in the specific release. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_