In 2026, if a marking code error occurs in 1C, the accountant must check the product group, the document details, its status, and the result of data exchange with the IS MPT server. If, following the review, the tax authority makes a decision, the procedure for making it and the deadlines for its submission and execution are determined by the TC RK, while the decision itself must contain the mandatory information, including the number, date, title, and identification details of the tax authority and the taxpayer.
What the Product Group Message Means
When working with marking codes, 1C may display the following message: “The code belongs to product group %1; completion for product group %2 is expected”. This means that the product group identified from the entered code does not match the group expected by the document or the corresponding field.
This check is performed when a new code is added to the “Marking Code Aggregation (OMS)” document. The object can be found at: “1C Service: Marking (IS MPT)” → “Marking Code Aggregation (OMS)”.
The accountant should not attempt to bypass the check by arbitrarily replacing the code. The following should first be compared:
- the actual product and its item card;
- the product group selected in the document;
- the marking code applied to the specific product;
- the details of the line to which the code is being added;
- the transaction type and purpose of the document.
If `%1` and `%2` are displayed in the message instead of names, these are template parameters in the error text. In the working interface, the program should normally substitute the corresponding values for them. The template itself does not make it possible to determine which specific groups conflict; this must be checked directly in the document and the product card.
Why the Code Data Is Not Loaded
Another possible 1C message is: “Data for code %1 could not be obtained from the server. Information about the code hierarchy will be available only after the document is accepted”. It relates to obtaining information on aggregate marking codes through integration with the IS MPT.
Under the described procedure, the message appears when the document has the status “Awaiting acceptance”. Therefore, the absence of hierarchy information at this stage does not necessarily mean that the code itself is incorrect. The program expressly indicates that the required data will become available after the document is accepted.
In this situation, the accountant should distinguish between two problems:
- product group mismatch — the code has been recognized, but its group differs from the expected group;
- server data unavailable — information about the code or its hierarchy has not yet been received through the integration.
These are different causes, so the item data should not be corrected merely because server data is temporarily unavailable. First, check the document status and wait for the prescribed processing stage, then review the data exchange result again.
What the Accountant Should Check in 1C
Start with the document itself. Make sure that the correct transaction is open and that the correct company, item, and product group have been selected. Then compare the code in the document with the code on the packaging or in the supplier’s source data.
A practical verification procedure may be as follows:
- Open the document that generated the message when it was saved or processed.
- Find the line containing the problematic code and check the associated item.
- Compare the product group in the line with the group to which 1C assigns the code.
- If an aggregation document is used, open it through the “1C Service: Marking (IS MPT)” section.
- Check the document status. If the status is “Awaiting acceptance”, hierarchy information may appear only after acceptance.
- After the status changes, check the code information and the integration data exchange result again.
Before manually correcting the data, it is useful to save the message text and record the document, the item line, and the current status. This will help distinguish a completion error from a situation in which the server response has not yet been received.
Do not replace the code with a random value, change the product group without checking the actual product, or post the document merely to make the warning disappear. Such actions may conceal the original cause and create discrepancies between the product, the marking code, and the accounting records.
The technical timeframe for obtaining hierarchy information is determined by the document processing stage in the IS MPT: when the status is “Awaiting acceptance”, the data is checked again after acceptance. If the situation involves a decision by the tax authority, that decision must specify its number and date, title, and the identification details of the tax authority and the taxpayer; the procedure for making the decision and the deadlines for its submission and execution are established by the TC RK.
Frequently Asked Questions
What does “code in 1C” mean in this situation? — This refers to the product marking code processed in documents integrated with the IS MPT. It is neither program code in the configuration nor a ledger account.
Why does 1C say that the code belongs to another product group? — The program identified one group from the code, while the document or its field expects another. Check the item, the product group, and the entered code itself.
Can the error be corrected by replacing the product group? — Only after checking it against the actual product and its marking. An arbitrary replacement may cause the accounting records to differ from the actual product.
What should I do if the code data has not been received from the server? — Check the document status. If it is awaiting acceptance, information about the code hierarchy may become available after the document is accepted.
Where is the code aggregation document located? — The described procedure specifies the following path: “1C Service: Marking (IS MPT)” → “Marking Code Aggregation (OMS)”.