1. Identification
| Parameter | Value |
|---|---|
| Object Type | Document (Document) |
| Name | NotificationOfWithdrawalFromCirculationAndMPTK |
| Full Name | Document.NotificationOfWithdrawalFromCirculationAndMPTK |
| Synonym | Notification of withdrawal from circulation (MPT) |
| Configuration | Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) |
| Country | Kazakhstan (₸) |
Purpose. The document is intended for the formation and sending of notifications about the withdrawal of marked goods from circulation to the Information System for the Marking and Traceability of Goods in Kazakhstan (MPT). It is used by accountants and logisticians when writing off, destroying, recycling, or returning marked products to the supplier. It operates in exchange mode with the external state system: it supports the formation of outgoing notifications with subsequent status control and validation error handling.
Key feature: this is an information exchange document, not an accounting one. It records the fact of withdrawal of marking codes from circulation and synchronizes the status with the MPT, but does not directly affect accounting and inventory registers. Value and quantity movements are performed by the underlying document (for example, "Write-off of goods").
Where to find in 1C: section "Nomenclature and Warehouse" → "Notification of Withdrawal from Circulation (MPT)".
Navigation link: e1cib/list/Document.NotificationOfWithdrawalFromCirculationAndMPTK
2. Header Attributes and Table Parts
2.1. Header Attributes
| Attribute | Type (typical) | Purpose |
|---|---|---|
Number |
String | Document number (configuration numbering) |
Date |
Date | Date of notification formation |
Organization |
ReferenceDirectory.Link.Organizations | Organization on behalf of which the codes are withdrawn from circulation |
Supplier |
ReferenceDirectory.Link.Counterparties | Counterparty-supplier of the withdrawn products. Mandatory |
SupplierName |
String | Name of the supplier (for transmission to MPT). Mandatory |
SupplierIdentificationNumber |
String | BIN/IIN of the supplier. Mandatory |
WithdrawalType / Reason |
Enumeration | Reason for withdrawal: write-off, recycling, defect, expiration, return to supplier |
Status |
Enumeration/String | Current state of exchange with MPT (draft, sent, accepted, rejected) |
UnderlyingDocument |
Document.Link | Document on the basis of which the notification is created (for example, "Write-off of goods") |
Comment |
String | Arbitrary comment |
The attributes
Supplier,SupplierName,SupplierIdentificationNumberare mandatory: if not filled, 1C will not allow the document to be processed/saved and will issue an error "Field ... is not filled".
2.2. Table Part "Marking Codes" (goods)
List of marked products withdrawn from circulation.
| Column (typical) | Type | Purpose |
|---|---|---|
Nomenclature |
ReferenceDirectory.Link.Nomenclature | Product item |
MarkingCode / KIZ |
String | Identification code (GTIN + serial number) of the withdrawn unit |
Quantity |
Number | Number of units |
CodeStatus |
String/Enumeration | Result of checking the code status on the MPT server |
2.3. Table Part "Errors" (typical errors)
Storage of validation errors and responses from MPT.
| Name | Type | Purpose |
|---|---|---|
Text |
String | Error message text |
Field |
String | Name of the field/attribute to which the error relates |
3. Forms
| Form | Purpose |
|---|---|
| Document Form (DocumentForm) | Main form for entering attributes, filling in marking codes, sending to MPT, and viewing status/errors |
| List Form (ListForm) | Viewing and searching notifications; opened via link e1cib/list/Document.NotificationOfWithdrawalFromCirculationAndMPTK |
| Selection Form (SelectionForm) | Selecting a document from other configuration objects |
| Code Upload Form (if available) | Uploading marking codes from an external file for large volumes (see scenario 3.5) |
4. Key Module Procedures
The attached evidence does not provide the source code of the procedures (path: line). Below are typical handlers for the exchange document with MPT of this configuration.
BeforeRecording/ValidationCheckProcessing— control of filling in mandatory attributes (Supplier,SupplierName,SupplierIdentificationNumber) and non-empty table part of codes.ProcessingHandler— absent. The document is processed "in vain" or is not processable: it does not generate movements in the registers (see section 5).- Form commands for exchange with MPT (form/manager module):
- formation and sending of notification to MPT (scenario 3.2);
- updating status from MPT (scenario 3.3);
- preliminary check of code status on the server (scenario 3.6);
- uploading marking codes from a file (scenario 3.5).
- Processing MPT response — parsing the service response, filling the table part "Errors" (
Text,Field) in case of rejection and setting the corresponding status.
Work Scenarios
| No. | Scenario | When applied |
|---|---|---|
| 3.1 | Creating a notification based on a write-off document | Write-off of marked goods: defect, expiration, recycling |
| 3.2 | Sending a notification to MPT | After creating and verifying the correctness of the document |
| 3.3 | Updating status from MPT | Synchronizing the document state after sending |
| 3.4 | Correcting a rejected notification | When MPT rejected the notification with reasons |
| 3.5 | Uploading marking codes from a file | Large volume of withdrawn goods, manual input is impractical |
| 3.6 | Checking the status of marking codes on the MPT server | Preliminary check of code correctness before sending |
5. Processing and Movements
The document does not generate entries and movements in the registers — the handler ProcessingHandler is absent. This is an information exchange document with MPT; it records the fact of withdrawal of marking codes from circulation but does not directly affect accounting and inventory registers.
All accounting movements are performed by the underlying document. For example, when writing off marked goods, the accounting entries are generated by "Write-off of goods", while the notification only confirms the withdrawal of codes from circulation in the state system.
Typical entries of the underlying document "Write-off of goods" (chart of accounts of the RK):
| Dr | Cr | Content |
|---|---|---|
| 7010 "Cost of sales" (or expense/other expense account) | 1330 "Goods" | Write-off of the cost of marked goods being withdrawn from circulation |
Rates and limits of the RK for 2026 (for related calculations in underlying documents): VAT 16%, MRP 4,325 ₸, MSP 85,000 ₸. VAT payable account — 3130, revenue from sales — 6010. This document does not perform these calculations.
6. Related Objects and Input on the Basis
- Underlying document (input "on the basis of"): "Write-off of goods" and other documents for the withdrawal of marked products (recycling, return to supplier). From the basis, the organization, nomenclature, and marking codes are filled in (scenario 3.1).
- Counterparties — attribute
Supplier(BIN/IIN for transmission to MPT). - Nomenclature — product items of the withdrawn codes.
- External MPT system — receiver of outgoing notifications and source of statuses/errors.
- Related electronic documents of the RK: ESF (ESF IS) and CNT — issued as separate objects; the notification of withdrawal from circulation is not directly related to them but is part of the overall marking and traceability framework.
7. Extension Points
- Configuration extension: adding handlers
BeforeRecording,ValidationCheckProcessingfor additional validation rules before sending. - Document event subscriptions — for integration logic (auto-filling from the basis, logging of exchanges).
- Common modules for exchange with MPT — overriding request/response formats and error parsing.
- Additional attributes and information (BSP mechanism) — for storing service attributes of exchange without changing metadata.
- Processing filling on the basis — expanding the list of underlying documents.
Requires verification for specific release 3.0.74.2: exact names of attributes/table parts and the presence of the "Processing" property in the document — clarified in the configurator, as the composition of metadata of integration objects with MPT changes between versions.