Free · per the Chestny ZNAK instructions
Chestny ZNAK error decoder
Enter the error number or paste its full text. We’ll show the official wording, what it means and what to do for the document to go through.
Frequent searches:
Most common
Search works in the browser: the error text, codes and INNs aren’t sent anywhere.
How to read an error report
- Open the error report and find the error number and text.
- Determine what it’s about: the code, the product, the participant or the file.
- Fix the cause; the search above suggests where to look.
- Submit a new document. The previous one can’t be corrected.
Most code errors come down to three questions: does the code exist in the system, does it belong to the sender (the code owner), and does its status fit the operation. If the answer to any of them is “no”, the document won’t go through. Whose code it is and what status it’s in is shown by marking code check in the Truemark account. Other common problems with codes and documents and their solutions are in the knowledge base section “Troubleshooting”.
Where to see the error number and text
In the Chestny ZNAK personal account: “Documents” → the document number with the status “Processed with errors” → “Error report”. If there are more than five errors, click “Download report”: an archive with a CSV file downloads, listing the document number and date, the sender’s and recipient’s INN, the identification code, the error code and its text.
If documents go out from accounting software, it shows the error number and text itself: Chestny ZNAK generates them, and the software only passes on the response.
One number, different errors
EDI documents, direct submission documents, receipts and code application reports have their own numbering. Error 14 in a UTD is a repeat document with the same invoice number and date, while in direct submission documents it’s an invalid code status. That’s why each error in the search shows its section, and a search by number shows all errors with that number.
Error texts follow the Chestny ZNAK instructions “Description of document processing errors in the personal account and via API”, version 180.0 of November 19, 2026. Explanations of common errors are based on Truemark articles and the “Code errors” window in the account. An overview with examples is in the article “Chestny ZNAK error codes”.
Reference
All errors by section
289 errors from the Chestny ZNAK instructions and OMS responses. Click an error to see its text and what to do. Each has its own address: you can send the link to a colleague.
Errors in UTDs and EDI documents
Universal transfer documents and other EDI documents that the EDI operator passes to Chestny ZNAK: original, corrected and corrective. Errors in the section: 86.
Error 3Brackets in the marking codeUTD and EDI
Error text
Brackets must not be used for application identifiers AI 01, 21, 8005 for the marking code <identification code value>
Value format check
- What it means
- The code is written with brackets around application identifiers, for example (01) and (21).
- Why it happens
- The code was copied from the caption under the DataMatrix or from a table where it’s written for people to read.
- What to do
- Remove the brackets and spaces: in the document, the code goes as one continuous string.
Details:Invalid marking code format
Error 4The document was already acceptedUTD and EDI
Error text
Document <document identifier> was registered earlier
Check by document identifier in the GIS MT database
- What it means
- A file with this name has already been accepted by Chestny ZNAK.
- Why it happens
- The same file was sent again.
- What to do
- You need a new document with a new file name, a corrected UTD or a corrective document.
Error 6The product, INN or place of business isn’t in the databaseUTD and EDI
Error text: variants
Product code <product code> not found in the database
Value lookup in the databaseData for the specified INN <organization INN searched> and KPP <KPP searched> not found
Place of business checkPlace of business for the specified INN <organization INN>, KPP <KPP>, FIAS <FIAS code> not found
Place of business check
- What it means
- Chestny ZNAK didn’t find the product code, the organization by INN and KPP, or the place of business by FIAS.
- Why it happens
- A typo in the GTIN, INN, KPP or address, or the place of business isn’t added to the profile.
- What to do
- Check the GTIN: 14 digits with a leading zero. For INN, KPP and FIAS, compare the details with the participant profile in Chestny ZNAK.
Details:GTIN in marking
Error 7No original documentUTD and EDI
Error text
The last successful TD not found for invoice No.: <invoice number>, date: <invoice date>
Search for the last successful TD for the invoice
- What it means
- No successfully processed document was found for this invoice.
- Why it happens
- The original UTD wasn’t processed or was rejected, and a correction or adjustment was sent after it.
- What to do
- The original document isn’t processed: start with it, then send the correction.
Error 8The value of field "…" isn’t in the list of allowed valuesUTD and EDI
Error text
08: The value of field "<parameter name>" isn’t in the list of allowed values
Check of values from the list
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 10The seller isn’t registeredUTD and EDI
Error text
Seller <seller name> isn’t identified (not registered)
Check of seller identification (registration) in GIS MT
- What it means
- The seller isn’t registered in Chestny ZNAK.
- Why it happens
- The supplier hasn’t registered as a participant in circulation.
- What to do
- While that’s the case, Chestny ZNAK won’t process the document: the seller needs to register.
Details:All Chestny ZNAK error codes
Error 12The buyer isn’t registeredUTD and EDI
Error text
Buyer <buyer name> isn’t identified (not registered)
Check of buyer identification (registration) in GIS MT
- What it means
- The buyer isn’t registered in Chestny ZNAK.
- Why it happens
- The recipient of the goods hasn’t registered as a participant in circulation.
- What to do
- While that’s the case, Chestny ZNAK won’t process the document: the buyer needs to register.
Details:All Chestny ZNAK error codes
Error 13The participant isn’t registeredUTD and EDI
Error text
Participant <name of the participant in circulation> isn’t identified (not registered)
Check of sender and/or recipient registration. For any TD with retirement, the recipient isn’t checked
- What it means
- The sender or recipient isn’t registered in Chestny ZNAK.
- Why it happens
- One of the document’s parties hasn’t registered.
- What to do
- While that’s the case, Chestny ZNAK won’t process the document: the party needs to register.
Details:All Chestny ZNAK error codes
Error 14A UTD with this number and date already existsUTD and EDI
Error text
UTD <document identifier> for invoice No.: <invoice number>, date: <invoice date> was registered earlier
Check for a UTD that there are no duplicate TDs with the same invoice number and date
- What it means
- A document with the same invoice number and date already exists.
- Why it happens
- The document was sent again or the number was mixed up.
- What to do
- Check the invoice number and date. To correct an accepted document, send a corrected UTD. In direct submission documents, error 14 means something else: an invalid code status.
Error 16An adjustment without a basisUTD and EDI
Error text
UKD (corrected UKD) No.: <UKD number>, date: <UKD date> (ID: <document identifier>) for invoice No.: <invoice number>, date: <invoice date> isn’t valid (the original base UTD is missing, or the document isn’t the latest)
Search for the original UTD / corrected UTD. The incoming UKD / corrected UKD is checked as an element of the document chain
- What it means
- The corrective document didn’t find the original UTD or refers to a document that isn’t the latest in the chain.
- Why it happens
- The adjustment was made to the original UTD, although a correction already followed it.
- What to do
- An adjustment must refer to the latest successfully processed document.
Error 18Marking Code … was changed by a later document: …UTD and EDI
Error text
Marking Code <identification code value> was changed by a later document: <document identifier>
Check for records in the IC history
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 19No history records for Marking Code: …UTD and EDI
Error text
No history records for Marking Code: <identification code value>
Check for records in the IC history
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 20The last history record of Marking Code: … doesn’t match the change in the document. ID…UTD and EDI
Error text
The last history record of Marking Code: <identification code value> doesn’t match the change in the document. Document ID not specified
Check that the last IC history record matches the document changes
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 21Marking Code … with parent … can’t be aggregated into …UTD and EDI
Error text
Marking Code <identification code value> with parent <current aggregate identification code value> can’t be aggregated into <new aggregate identification code value>
Check whether the specified IC can be re-aggregated
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 22The code doesn’t exist in Chestny ZNAKUTD and EDI
Error text
Marking Codes <identification code value> not found
Check that the specified ICs exist
- What it means
- Chestny ZNAK doesn’t know this code. The document won’t go through with it.
- Why it happens
- The code is written with distortions: case lost, characters missing or added. Less often, the code really isn’t in the system.
- What to do
- Check how the code is written: case, missing and extra characters. If codes get into the document by scanner, check the scanner.
Details:Error 22 explained: marking code not foundScanner check: GS, layout, AIM prefix
Error 23The code doesn’t belong to the senderUTD and EDI
Error text
Participant <name of the participant in circulation> has no authority to perform the operation with Marking Code <identification code value>
Check that the IC belongs to the participant in circulation. For a TD, the error may occur when an IC belongs to a product group not connected for the participant
- What it means
- The sender has no authority for the operation with this code.
- Why it happens
- The code is registered to another company or belongs to a product group the sender hasn’t connected.
- What to do
- Only the party the code is registered to can ship it. Check the code owner. When receiving, don’t sign with the result “Accepted”: ask the supplier to correct the document.
Details:Marking code owner
Error 24The code status isn’t suitable for transferUTD and EDI
Error text
Status <status value> of Marking Code <identification code value> doesn’t match the operation performed
Check of available actions on the IC given its status
- What it means
- The code isn’t in the right status for this operation.
- Why it happens
- The goods aren’t introduced into circulation or have already been retired: sold, written off, transferred.
- What to do
- Only a code in the “In circulation” status can be transferred under a UTD. Check the code status and remove unsuitable codes from the document.
Details:Error 24 explained: code status doesn’t match the operationMarking code statuses
Error 25Identification codes … don’t belong to product group "…"UTD and EDI
Error text
Identification codes <identification code value> don’t belong to product group "<product group name>"
Product group check. The error is shown if GIS MT finds a duplicate KITU registered earlier in another product group
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 26Participant … isn’t registered in the Unified State Register of Individual Entrepreneurs/Legal Entities as activeUTD and EDI
Error text
Participant <INN number> isn’t registered in the Unified State Register of Individual Entrepreneurs/Legal Entities as active
Check of the INN for registration in the Unified State Registers of Individual Entrepreneurs / Legal Entities
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 31Invalid package type …UTD and EDI
Error text
Invalid package type <package type value>
Package type check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 38The package is emptyUTD and EDI
Error text
Code <identification code value> has no nested items
Check for nested ICs
- What it means
- A package code was given with nothing nested in it.
- Why it happens
- The aggregate wasn’t formed or was disaggregated before shipment.
- What to do
- Form the package or transfer the product codes without it.
Details:Aggregation
Error 44The file failed the schema checkUTD and EDI
Error text
Validation error of document <document identifier> against the XSD schema
Document validation against the XSD schema
- What it means
- The XML structure doesn’t match the document format.
- Why it happens
- The accounting software or EDI operator built the file not according to the approved schema.
- What to do
- Create the document again in the accounting software. If the error repeats, write to the software developer.
Error 46Wrong file name or contentUTD and EDI
Error text
The document content or name is incorrect
Validation of the document file content and name
- What it means
- Chestny ZNAK didn’t accept the file name or its content.
- Why it happens
- The file name doesn’t match the identifier inside the file, or the document’s parties are specified incorrectly.
- What to do
- Check the file name and the file identifier inside it, the sender and recipient details, and the signatory’s data.
Error 54Correction date not filled in for document …UTD and EDI
Error text
Correction date not filled in for document <document identifier>
Correction date check. May be used for a corrected UTD
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 60The product isn’t in the National CatalogUTD and EDI
Error text
Products with GTIN <product code> aren’t registered in the National Catalog of marked goods
Check for the product code in the National Catalog
- What it means
- Products with this GTIN aren’t registered in the National Catalog.
- Why it happens
- The product card wasn’t created, or the GTIN in the document has a typo.
- What to do
- Check the product code. In a volume and grade tracking line, the entry goes: 02, the 14-digit GTIN, 37, the quantity.
Error 63A document with this number and date has already been acceptedUTD and EDI
Error text
UTD <document identifier> for invoice No.: <invoice number>, date: <invoice date> isn’t valid (registered earlier, or a corrected UTD was processed)
Check that the UTD creation and/or processing order is followed
- What it means
- A UTD from this supplier with the same number and date has already been processed; Chestny ZNAK won’t accept it again.
- Why it happens
- The chain is broken: after a corrected document, a correction was made to the original.
- What to do
- Corrections are made to the latest corrected document, not the original. When receiving, ask the supplier to send a corrected UTD.
Error 64A correction with this number already existedUTD and EDI
Error text
Corrected UTD <document identifier> for invoice No.: <invoice number>, date: <invoice date> isn’t valid (a corrected UTD with a later correction number or date was processed: No. <correction number>, date <correction date>)
Check that the document chain order is followed for the corrected UTD
- What it means
- A correction with the same or a later number and date has already been processed.
- Why it happens
- The correction number or date is wrong.
- What to do
- Check the correction number and date.
Error 68The code isn’t paidUTD and EDI
Error text
Marking Code <identification code value> isn’t paid
Marking code payment control
- What it means
- The marking code isn’t paid.
- Why it happens
- The product group balance in Chestny ZNAK didn’t have enough money.
- What to do
- Pay for the codes: check the balance in Chestny ZNAK.
Details:All Chestny ZNAK error codes
Error 69The file can’t be readUTD and EDI
Error text
The document content or name is incorrect. Couldn’t parse
Validation of the document file content and name
- What it means
- Chestny ZNAK couldn’t parse the file.
- Why it happens
- The file is damaged or in the wrong format.
- What to do
- Create the document again and send it once more.
Error 70The document is missing fieldsUTD and EDI
Error text: variants
The document content is incorrect. Missing <list of fields>
Validation of the document file content and nameThe document content is incorrect. Missing [<field name_1>, <field name_2>, …]
Check of specific document elements
- What it means
- The document lacks mandatory fields.
- Why it happens
- The accounting software didn’t fill in the fields Chestny ZNAK requires.
- What to do
- Fill in the fields listed in the error text.
Error 71The document content is incorrect. Incorrect data: no MCs with a PG that has … enabledUTD and EDI
Error text: variants
The document content is incorrect. Incorrect data: no MCs with a PG that has the recording function enabled
Comparison of the ICs in the document with the product group for which the recording function is availableThe document content is incorrect. Incorrect data: a UTD (corrected) with <КодИтога> = 3 can’t be processed
Check that the buyer title is filled in correctly. A corrected UTD buyer title can’t have <КодИтога> = 3The document content is incorrect. Incorrect data: field <parameter name> isn’t filled in.
Check for the presence and correctness of the consignee INN
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 72Incorrect document type: …UTD and EDI
Error text
Incorrect document type: <document type>
Check of the specified document type
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 75Marking Code … has an incorrect issuance typeUTD and EDI
Error text
Marking Code <identification code value> has an incorrect issuance type
Issuance type check (when introducing an MC into circulation under a TD, the MC must not have the “IMPORT” issuance type)
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 76Document with id … not foundUTD and EDI
Error text
Document with id <document identifier> not found
Check that the document exists in the system
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 77The cancellation didn’t go throughUTD and EDI
Error text
The document canceling the UTD with id <document identifier> isn’t valid
Validation of the cancellation document
- What it means
- The document canceling the UTD wasn’t accepted.
- Why it happens
- The wrong document is being canceled, or it has already been changed.
- What to do
- Check which document is being canceled.
Error 79Invalid marking codeUTD and EDI
Error text
Invalid marking code <identification code value>
Identification code check
- What it means
- The code has the wrong form.
- Why it happens
- Wrong length, invalid characters or brackets. Often it’s distortion during scanning.
- What to do
- Check the code format: break it into parts and compare with the label.
Details:Invalid marking code formatMarking code check by parts
Error 82A correction with this number already existedUTD and EDI
Error text
Corrected UTD <document identifier> for invoice No.: <invoice number>, date: <invoice date> isn’t valid (a corrected UTD with the same correction number and date was processed: No. <correction number>, date <correction date>)
Control of duplicate corrected UTDs
- What it means
- A correction with the same number and date has already been processed.
- Why it happens
- The correction was sent again.
- What to do
- Check the correction number and date.
Error 83Incorrect TD sequence for Marking Code …UTD and EDI
Error text
Incorrect TD sequence for Marking Code <identification code value>
Control of the document chain correctness
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 103The document has no codesUTD and EDI
Error text
Contains no marking codes
Check for marking codes
- What it means
- The document sent to Chestny ZNAK has no marking codes at all.
- Why it happens
- The codes didn’t get into the product lines.
- What to do
- Add marking codes to the document and send it again.
Details:UTD samples with marked products
Error 106File encoding errorUTD and EDI
Error text
Document validation error
Document encoding check
- What it means
- The document failed the check.
- Why it happens
- The file is saved in the wrong encoding.
- What to do
- Check the file encoding.
Error 108A failure on the Chestny ZNAK sideUTD and EDI
Error text
A service error occurred
- What it means
- A service error occurred.
- Why it happens
- A failure on the system side, not in the document.
- What to do
- Send it again later.
Details:All Chestny ZNAK error codes
Error 110Incorrect status of document …: …UTD and EDI
Error text
Incorrect status of document <document identifier>: <status value>
Check whether actions can be performed on the document
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 111Routing errorUTD and EDI
Error text
Routing error
Check of the document’s product group, the existence of the document being canceled and of a product group with routing turned off
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 116The code isn’t introduced into circulationUTD and EDI
Error text
Participant <INN of the participant in circulation> can’t move Marking Code <identification code value> that isn’t introduced into circulation
MC status check
- What it means
- The code is in the “Applied” status: the goods aren’t introduced into circulation yet.
- Why it happens
- The supplier didn’t introduce the goods into circulation before shipping.
- What to do
- Introduce the goods into circulation before shipping.
Error 117The code has only been issuedUTD and EDI
Error text
Marking code <identification code value> is issued
Status check: the correct status is “EMITTED” (“Issued”) or “APPLIED” (“Applied”)
- What it means
- The code is in the “Issued” status: it isn’t applied or introduced into circulation.
- Why it happens
- The code application report and introduction into circulation weren’t filed.
- What to do
- File the code application report, introduce the goods into circulation, and only then ship.
Details:Marking code statuses
Error 123The base document has an errorUTD and EDI
Error text
The base document with НомерСчФ "<invoice number>" and ДатаСчФ "<invoice date>" was processed with an error or not found. The array of codes to move is empty
Check that at least one code is passed within a UKD without a UTD
- What it means
- The base document was processed with an error or not found; there are no codes to move.
- Why it happens
- The adjustment was sent to a document that didn’t go through.
- What to do
- First get the base document processed successfully.
Error 125Wrong file name prefixUTD and EDI
Error text
Incorrect document prefix
Document prefix check
- What it means
- The file name starts with the wrong prefix.
- Why it happens
- The file is named not according to the format rules.
- What to do
- Create the document again in the accounting software.
Error 141The goods can’t be transferred without codesUTD and EDI
Error text
The product group in product card <product code> isn’t suitable for volume and grade tracking
Product group check
- What it means
- The product group doesn’t allow volume and grade tracking.
- Why it happens
- The line has a quantity instead of codes.
- What to do
- Transfer such goods with marking codes.
Details:Volume and grade tracking
Error 142A line without codes is filled in against the rulesUTD and EDI
Error text: variants
Item-level and volume and grade information can’t be used in a document at the same time
Check of the information breakdown for one product itemКолВедМарк not found (the КолВедМарк tag is mandatory when ГТИН is present)
Check of a document with OSU information and a mixed set of tags from different versionsГТИН not found (the ГТИН tag is mandatory when КолВедМарк is present)
Check of a document with OSU information and a mixed set of tags from different versions
- What it means
- A volume and grade tracking line is filled in with an error.
- Why it happens
- The GTIN or product quantity isn’t given, or codes and quantity are mixed in one line.
- What to do
- In a volume and grade tracking line, give both the GTIN and the quantity. One product line holds either codes or a quantity.
Details:Volume and grade tracking
Error 146The code has already been shippedUTD and EDI
Error text
Marking code <identification code value> has already been shipped/sold to <recipient INN>
Identification code check
- What it means
- The code has already been transferred to another recipient or sold.
- Why it happens
- The code ended up in two documents.
- What to do
- Remove the code from the document.
Details:Marking code statuses
Error 177Return of sold codesUTD and EDI
Error text
Attempt to return to the seller Marking codes: <identification code value 1>, <identification code value 2>, <identification code value 3>, … , <identification code value N>, sold by the buyer
MC status check
- What it means
- The return to the seller includes codes the buyer has already sold.
- Why it happens
- Extra codes were included in the return document.
- What to do
- Keep only the codes the buyer hasn’t sold in the return.
Error 178The presence of government contract identifier information in the UKD differs from its presence in…UTD and EDI
Error text
The presence of government contract identifier information in the UKD differs from its presence in the base document
Check that the UKD data matches the base document data
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 179Retirement information can’t be determined from the received UKDUTD and EDI
Error text
Retirement information can’t be determined from the received UKD
Check of retirement information based on the UKD
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 189Place of business … is blocked in EGAISUTD and EDI
Error text: variants
Place of business <KPP> is blocked in EGAIS
Check that the place of business isn’t blocked in EGAISParticipant <participant INN> is blocked in EGAIS
Check that the organization INN isn’t blocked in EGAIS
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 190Wrong quantity entryUTD and EDI
Error text
Incorrect IC quantity data
Check of the UTD document’s OSU value against the regular expression 02[gtin]37[count], where [gtin] is <product code> (14 digits), [count] is the product quantity in the package unit of measure (1 to 8 digits); the value is given without brackets or other separators. Example: 02046111111111113710
- What it means
- The quantity data for volume and grade tracking is specified incorrectly.
- Why it happens
- An entry with brackets, spaces or a fractional quantity.
- What to do
- The volume and grade tracking entry: 02, the 14-digit product code, 37, the quantity, without brackets. The quantity is a whole number.
Details:Volume and grade tracking
Error 196The address isn’t among the places of businessUTD and EDI
Error text
FIAS code <FIAS code> isn’t in the list of places of business for this organization with INN <organization INN>
FIAS code check
- What it means
- The FIAS code isn’t in the organization’s list of places of business.
- Why it happens
- The address isn’t added to the participant profile, or a different one is given.
- What to do
- Add the address in the profile or give the correct one.
Details:All Chestny ZNAK error codes
Error 215The document doesn’t support withdrawal from circulation for volume and grade tracking (OSU) in this product groupUTD and EDI
Error text
The document doesn’t support withdrawal from circulation for volume and grade tracking (OSU) in this product group
Check whether the product group allows withdrawal from circulation with volume and grade tracking
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 261The operation is unavailable because there’s no license for the specified product type or activityUTD and EDI
Error text
The operation is unavailable because there’s no license for the specified product type or activity
License check for tobacco product groups
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 262The operation is unavailable because the specified address isn’t in the licenseUTD and EDI
Error text
The operation is unavailable because the specified address isn’t in the license
License check for tobacco product groups
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 263The operation is unavailable because there are no active licenses for the specified activity…UTD and EDI
Error text
The operation is unavailable because there are no active licenses for the specified activity or product type
License check for tobacco product groups
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 267MCs with an incorrect work attribute "ПрТовРаб" foundUTD and EDI
Error text
MCs with an incorrect work attribute "ПрТовРаб" found
Check for MCs with an incorrect work attribute
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 268The permit document is not validUTD and EDI
Error text
<PD type>, <PD number>, <PD date> has an invalid status (status group <status group>) for marking code <identification code value>. <PD error description>
PD status check
- What it means
- The certificate or declaration is in a status that doesn’t fit the code.
- Why it happens
- The document is suspended, terminated or expired.
- What to do
- Check the certificate or declaration and give a valid document.
Details:Permit documents
Error 270Product group … isn’t suitable for volume and grade tracking when moving between participantsUTD and EDI
Error text
Product group <product group name> isn’t suitable for volume and grade tracking when moving between participants
Check of OSU information in a UTD / corrected UTD
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 271The consignee’s place of business doesn’t match the information in the original documentUTD and EDI
Error text: variants
The consignee’s place of business doesn’t match the information in the original document
Check that the place of business in the corrected UTD matches the place of business obtained when processing the UTDThe consignor’s place of business doesn’t match the information in the original document
Check that the place of business in the corrected UTD matches the place of business obtained when processing the UTD
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 272This document type is unavailable when moving between participantsUTD and EDI
Error text
This document type is unavailable when moving between participants
Check whether a direct submission UTD is available when moving between participants in circulation
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 273MC … not shippedUTD and EDI
Error text
MC <identification code value> not shipped
Check the content of the previously sent product shipment document between INNs / movement between places of business in GIS MT, or send a new shipment document
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 274MC … already shippedUTD and EDI
Error text
MC <identification code value> already shipped
Check the status of the previously sent product shipment document between INNs / movement between places of business in GIS MT
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 275The seller’s INN must match the consignor’s INNUTD and EDI
Error text: variants
The seller’s INN must match the consignor’s INN
Check of a UTD / corrected UTD that the seller’s INN matches the consignor’s INNThe buyer’s INN must match the consignee’s INN
Check of a UTD / corrected UTD that the buyer’s INN matches the consignee’s INN
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 276MC … shipped by another document …UTD and EDI
Error text
MC <identification code value> shipped by another document <document identifier>
Check of the status of the previously sent product shipment document between INNs / movement between places of business in GIS MT
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 277The document content differs from the original given at shipmentUTD and EDI
Error text
The document content differs from the original given at shipment
Check the content of the previously sent product shipment document between INNs / movement between places of business in GIS MT
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 282Couldn’t identify the consignor’s/consignee’s place of businessUTD and EDI
Error text
Couldn’t identify the consignor’s/consignee’s place of business
Check that the TD specifies only one place of business
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 294PG … in the document doesn’t support transfer via ACSUTD and EDI
Error text: variants
PG <product group name> in the document doesn’t support transfer via ACS
Send the UTD / corrected UTD without ACS informationPG <product group name> in the document doesn’t support transfer via ACS when a consignee INN different from the buyer INN is given
Check of a UTD / corrected UTD that the buyer’s INN matches the consignee’s INN
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 340The document has no goods of PGs that allow direct submission UTDsUTD and EDI
Error text
The document has no goods of PGs that allow direct submission UTDs
Check whether document submission is available for the product group
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 344The document sender’s INN must match the shipment document sender’s INNUTD and EDI
Error text
The document sender’s INN must match the shipment document sender’s INN
Check of the sender of the cancellation of the “UTD (product shipment)” document
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 359The document content is incorrect. Incorrect data: no freight transport informationUTD and EDI
Error text
The document content is incorrect. Incorrect data: no freight transport information
Check for freight transport information
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 362Batch number … not found in the Batch RegisterUTD and EDI
Error text
Batch number <batch number> not found in the Batch Register
Check for the batch number in the batch register
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 364GTIN … from the document must match the GTIN in the Batch Register
UTD and EDI
Error text
GTIN <product code> from the document must match the GTIN in the Batch Register
Check that the product code from the document matches the product code in the batch register
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 371The document date is earlier than the application date of the MCs in the documentUTD and EDI
Error text
The document date is earlier than the application date of the MCs in the document
The UTD invoice date must be equal to or later than the date of filing the code application report for the marking codes in the UTD (for tobacco product groups). The check applies to product unit codes, including those nested in an aggregate, with the issuance type “Made in Russia”, in the “Applied” status, without a special state
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 373The document contains ICs shipped by different UTDsUTD and EDI
Error text
The document contains ICs shipped by different UTDs
Check that all identification codes are shipped by one document
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 375No PD information found for MC …UTD and EDI
Error text
No PD information found for MC <identification code value>
Check for permit document information
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 383The document has no price information for the transferred (received) products in line number …UTD and EDI
Error text
The document has no price information for the transferred (received) products in line number <product line number>
Check that the product line price in the document is filled in
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 384Price below the minimumUTD and EDI
Error text
The document contains a price below the Minimum price in line number <product line number>
Check of the price by identification code against the minimum price
- What it means
- The price in the document line is below the minimum for this product.
- Why it happens
- A price error, or the goods are sold below the set minimum.
- What to do
- Check the price in the line named in the error.
Details:All Chestny ZNAK error codes
Error 386No shipment information for IC …UTD and EDI
Error text
No shipment information for IC <identification code value>
Check for a “UTD (product shipment)” document
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 393Couldn’t identify the consigneeUTD and EDI
Error text
Couldn’t identify the consignee
Check of consignee information
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 399No link between the sender and the sellerUTD and EDI
Error text
No link between the sender and the seller
Check that the EDI identifier matches the seller
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 400Field "KPP" isn’t filled inUTD and EDI
Error text: variants
Field "KPP" isn’t filled in
Check for KPP informationField "FIAS" isn’t filled in
Check for FIAS informationNo data
Check for INN information
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Errors in direct submission documents
Documents sent to Chestny ZNAK from the personal account or via API without EDI: introduction into and withdrawal from circulation, re-marking, write-off, packages and sets. Errors in the section: 179.
Error 1Field not filled inDirect submission
Error text: variants
Field "<field name>" isn’t filled in.
Field completion checkField <field name> isn’t filled in in document "<document type>".
Field completion checkAttribute "<attribute name>" isn’t given for code <identification code value> in document "<document type>".
Attribute completion check
7 more text variants are in the Chestny ZNAK instructions.
- What it means
- The document has an empty field without which Chestny ZNAK won’t accept it.
- Why it happens
- The field wasn’t filled in on the form, or the accounting software didn’t pass it.
- What to do
- Fill in the field named in the error. When introducing imports with an empty “EAEU HS code” or “Country of origin code”, see the import rejection breakdown. If permit documents aren’t given, fill in their type, number and date.
Details:Field not filled in: EAEU HS code, country of origin codePermit documents on introduction into circulation
Occurs in documents (36): Auto-introduction into circulation on import via FCS, Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Received from individuals, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. With a reason, and others.
Error 2… in document "…" doesn’t match the current participant’s dataDirect submission
Error text: variants
<field name> <field value> in document "<document type>" doesn’t match the current participant’s data.
Check of the current participant in circulation’s data<field name> <field value> doesn’t match the current participant’s data.
Check of the current participant in circulation’s data"INN of the participant in circulation" <organization INN> doesn’t match the current participant’s data.
Check of the current participant in circulation’s data
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (33): Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Received from individuals, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. With a reason, Introduction into circulation. Cross-border trade, and others.
Error 3Wrong field formatDirect submission
Error text: variants
Invalid format of field value <field value> in document "<document type>".
Value format checkInvalid format of field value "<field name>".
Field value format checkInvalid format of field value <field name> for marking code <marking code value>
Field value format check
5 more text variants are in the Chestny ZNAK instructions.
- What it means
- The field value is written in the wrong format.
- Why it happens
- A date, INN or document number isn’t written the way Chestny ZNAK expects.
- What to do
- Check the format: date, INN, document number.
Details:All Chestny ZNAK error codes
Occurs in documents (37): Auto-introduction into circulation on import via FCS, Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Received from individuals, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. With a reason, and others.
Error 4Date out of the allowed rangeDirect submission
Error text: variants
The date value in field <field name> is out of the allowed range.
Date range checkFor marking code <marking code value>, the date value in field <field name> is out of the allowed range.
Date range checkThe date value in field "<field name>" is out of the allowed range.
Date range check
3 more text variants are in the Chestny ZNAK instructions.
- What it means
- The date is too early or in the future.
- Why it happens
- A typo in the production date, document date or permit document date.
- What to do
- Check the dates in the document and send it again.
Details:Permit documents on introduction into circulation
Occurs in documents (28): Auto-introduction into circulation on import via FCS, Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Received from individuals, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, and others.
Error 5The value of field … is out of the allowed numeric rangeDirect submission
Error text: variants
The value of field <field name> is out of the allowed numeric range.
Numeric range checkThe value of field "<field name>" is out of the allowed numeric range.
Numeric range checkAn invalid weight is given for IC <identification code value>.
IC weight value check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (15): Auto-introduction into circulation on import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Withdrawal from circulation (OSU), Correction of code information, Shipment to the EAEU, and others.
Error 6INN … not found in the databaseDirect submission
Error text: variants
INN <organization INN searched> not found in the database.
Value lookup in the databaseProduct code <product code value searched> of marking code <identification code value> not found in the database.
Value lookup in the database<field name> <field value searched> not found in the database.
Value lookup in the database
13 more text variants are in the Chestny ZNAK instructions.
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (39): Auto-introduction into circulation on import via FCS, Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Received from individuals, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. With a reason, and others.
Error 7Invalid number of characters in the value of field …: …Direct submission
Error text: variants
Invalid number of characters in the value of field <field name>: <field value>.
Character count checkInvalid number of characters in the value of field <field name>: <field value> for marking code <marking code value>
Character count checkInvalid number of characters in the value of field "<field name>" <field value>.
Character count check
4 more text variants are in the Chestny ZNAK instructions.
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (33): Auto-introduction into circulation on import via FCS, Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Received from individuals, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. With a reason, and others.
Error 8The value isn’t in the referenceDirect submission
Error text: variants
The value of field <field name> in document "<document type>" isn’t in the list of allowed values.
Check of values from the listThe value of field "<field name>" isn’t in the list of allowed values.
Check of values from the listFor marking code <marking code value>, the value of field <field name> "<field value>" isn’t in the list of allowed values.
Check of values from the list
9 more text variants are in the Chestny ZNAK instructions.
- What it means
- The field value isn’t in the list of allowed values.
- Why it happens
- The value was typed by hand instead of being chosen from the reference.
- What to do
- Choose a value from the reference.
Details:All Chestny ZNAK error codes
Occurs in documents (24): Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. With a reason, Introduction into circulation. Cross-border trade, Return to circulation, Withdrawal from circulation, and others.
Error 9Invalid product card status …Direct submission
Error text
Invalid product card status <product code value>.
Check of the product card status in the National Catalog of marked goods
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Set formation.
Error 11The code belongs to another companyDirect submission
Error text: variants
Identification code <identification code value> doesn’t belong to the participant in circulation.
Checks that the document sender is the owner or holder of the marking codeMarking code <identification code value> doesn’t belong to the participant in circulation.
Checks that the document sender is the owner or holder of the marking codeThe identification code doesn’t belong to the participant in circulation.
Checks that the document sender is the manufacturer or holder of the marking code
- What it means
- The identification code doesn’t belong to the participant in circulation.
- Why it happens
- The code is registered to another company: for example, another organization ordered the codes.
- What to do
- Only your own codes can be introduced and transferred. Check that the document is sent by the company that ordered the codes.
Details:Marking code owner
Occurs in documents (28): Auto-introduction into circulation on import via FCS, Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Received from individuals, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. With a reason, and others.
Error 12No product card (GTIN) in the NC
Direct submission
Error text
No product card (GTIN) in the NC
Check for a product card in the NC
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (2): Shipment from the EAEU with IC recognition, Receiving from the EAEU.
Error 13The document has no codesDirect submission
Error text: variants
The document lists no identification codes.
Array completion checkThe document lists no products.
Array completion checkParticipant <name of the participant in circulation> isn’t identified (not registered).
Check for participant data in the database
2 more text variants are in the Chestny ZNAK instructions.
- What it means
- The document lists no identification codes.
- Why it happens
- The codes didn’t get into the document.
- What to do
- Add the codes.
Details:All Chestny ZNAK error codes
Occurs in documents (32): Auto-introduction into circulation on import via FCS, Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. With a reason, Introduction into circulation. Cross-border trade, and others.
Error 14Invalid code statusDirect submission
Error text
Invalid status of identification code <identification code value>.
Marking code status check
- What it means
- The code status doesn’t fit this document.
- Why it happens
- The code application report hasn’t been accepted yet, or the code is already in circulation or already retired.
- What to do
- Check the code status. Before introduction into circulation, make sure the code application report is accepted and the code is in the “Applied” status.
Details:Error 14 explained: invalid code statusMarking code statuses
Occurs in documents (23): Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Received from individuals, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. With a reason, Introduction into circulation. Cross-border trade, and others.
Error 16The value isn’t uniqueDirect submission
Error text: variants
The value of field <field name> isn’t unique.
Check of value uniqueness in the current arrayOne or more values in field <field name> aren’t unique
Check of value uniqueness in the current arrayThe combination of field values <field name_1> "<field value_1>" and <field name_2> "<field value_2>" isn’t unique.
Check of value uniqueness in the current array
5 more text variants are in the Chestny ZNAK instructions.
- What it means
- The document repeats a value that must be unique.
- Why it happens
- For example, one code is listed twice.
- What to do
- Remove the duplicate and send the document again.
Details:All Chestny ZNAK error codes
Occurs in documents (35): Auto-introduction into circulation on import via FCS, Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Received from individuals, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. With a reason, and others.
Error 17The value of field … in document "…" isn’t unique in the databaseDirect submission
Error text
The value of field <field name> <field value> in document "<document type>" isn’t unique in the database.
Check of value uniqueness in the database
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (2): Receiving from the EAEU, Write-off.
Error 18Invalid status of the participant found by INN … given in field "…"Direct submission
Error text: variants
Invalid status of the participant found by INN <field value> given in field "<field name>".
Check of the participant in circulation’s statusInvalid status of the participant found by INN <field value> given in field <field name>.
Check of the participant in circulation’s statusInvalid status of the participant found by INN <organization INN> given in field "<field name>".
Check of the participant in circulation’s status
2 more text variants are in the Chestny ZNAK instructions.
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (35): Auto-introduction into circulation on import via FCS, Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Received from individuals, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. With a reason, and others.
Error 19Codes of different product groupsDirect submission
Error text: variants
The product groups of the codes aren’t identical
Product group checkThe product groups of the identification codes aren’t identical.
Check that the codes’ product groups are identicalNo product groups available for introduction into circulation found
Product group check
- What it means
- The product groups of the codes don’t match.
- Why it happens
- Codes of different product groups ended up in one document.
- What to do
- One document holds codes of one product group.
Details:All Chestny ZNAK error codes
Occurs in documents (25): Auto-introduction into circulation on import via FCS, Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Received from individuals, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, and others.
Error 20The "HS code" parameter values of the identification codes aren’t identicalDirect submission
Error text: variants
The "HS code" parameter values of the identification codes aren’t identical.
Check that the EAEU HS codes are identicalThe "EAEU HS code" parameter values of the identification codes aren’t identical.
Check that the EAEU HS codes are identicalThe products’ EAEU HS codes aren’t identical.
Check that the EAEU HS codes are identical
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (8): Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Correction of code information, Re-marking, Receiving from the EAEU, Package formation.
Error 21The code is already in another aggregateDirect submission
Error text: variants
Marking Code <identification code value> with parent <current aggregate identification code value> can’t be aggregated into <new aggregate identification code value>
Check whether the IC is in another aggregateMarking Code <identification code value> can’t be aggregated into itself.
Check of value uniqueness in the current array
- What it means
- The code can’t be nested into a new package: it already has a parent.
- Why it happens
- The code is nested in another box or package.
- What to do
- Disaggregate the previous aggregate and send the document again.
Details:Aggregation
Occurs in documents (2): Shipment from the EAEU with IC recognition, Package formation.
Error 22Marking Codes … not foundDirect submission
Error text: variants
Marking Codes <identification code value> not found
IC check in the Marking SystemImpossible circulation condition for goods <identification code value>.
Goods circulation condition checkInvalid EAEU HS code of the goods in the goods declaration.
Check of the EAEU HS code in the GD
1 more text variant is in the Chestny ZNAK instructions.
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (8): Auto-introduction into circulation on import via FCS, Withdrawal from circulation, Correction of code information, Cancellation of shipment under a UTD, Reweighing report, Receiving from the EAEU, Import notice (EAEU), Package formation.
Error 23Participant … has no authority to perform the operation with Marking Code …Direct submission
Error text: variants
Participant <name of the participant in circulation> has no authority to perform the operation with Marking Code <identification code value>
Check that the IC belongs to the participant in circulationProduct group <product group name> isn’t available to the participant.
Product group check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (4): Reweighing report, Write-off (general document), Import notice (EAEU), Package formation.
Error 24The status of Marking Code … doesn’t match the operation performedDirect submission
Error text: variants
The status of Marking Code <identification code value> doesn’t match the operation performed
Check of the IC status and special stateIncorrect status <identification code value>.
IC status checkThe identification code status doesn’t match the operation performed.
Check of the IC status and special state
1 more text variant is in the Chestny ZNAK instructions.
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (10): Correction of code information, Cancellation of shipment under a UTD, Reweighing report, Connecting a keg to dispensing equipment, Write-off (general document), Import notice (EAEU), Notice of temporarily untraceable codes, Notice of code state, and others.
Error 25Identification codes don’t belong to product group …Direct submission
Error text: variants
Identification codes don’t belong to product group <product group name>.
Parameter match checkProduct codes don’t belong to product group <product group name>.
Parameter match check<field name> doesn’t match the value of field <field name>: <field value>.
Parameter match check
10 more text variants are in the Chestny ZNAK instructions.
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (34): Auto-introduction into circulation on import via FCS, Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Received from individuals, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. With a reason, and others.
Error 26Participant … isn’t registered in the Unified State Register of Individual Entrepreneurs/Legal Entities as activeDirect submission
Error text: variants
Participant <name of the participant in circulation> isn’t registered in the Unified State Register of Individual Entrepreneurs/Legal Entities as active
Check that the value matches the QES certificate dataParticipant <INN number> isn’t registered in the Unified State Register of Individual Entrepreneurs/Legal Entities as active
Check of the INN for registration in the Unified State Registers of Individual Entrepreneurs / Legal Entities
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (4): Cancellation of shipment under a UTD, Write-off (general document), Import notice (EAEU), Package formation.
Error 27The value doesn’t match the QES certificate dataDirect submission
Error text
The value doesn’t match the QES certificate data.
Check that the value matches the QES certificate data
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Return to circulation.
Error 28Filling in fields "…" and "…" at the same time isn’t allowedDirect submission
Error text: variants
Filling in fields "<field name_1>" and "<field name_2>" at the same time isn’t allowed.
Field completion checkGiving primary document data at both the document level and the product level isn’t allowed.
Primary document data checkFor MC <marking code value>, filling in permit document data at both the product level and in the specialized array isn’t allowed.
Permit document data completion check
3 more text variants are in the Chestny ZNAK instructions.
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (15): Auto-introduction into circulation on import via FCS, Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. With a reason, Introduction into circulation. Cross-border trade, and others.
Error 29Invalid format of the transferred JSON file
Direct submission
Error text: variants
Invalid format of the transferred JSON file.
Check that the csv, json or xml file matches the XSD schemaThe transferred XML file doesn’t match the XSD schema.
Check that the csv, json or xml file matches the XSD schemaInvalid format of the transferred CSV file.
Check that the csv, json or xml file matches the XSD schema
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (31): Auto-introduction into circulation on import via FCS, Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Received from individuals, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. With a reason, and others.
Error 30Identification code … isn’t the parent of identification code …Direct submission
Error text: variants
Identification code <identification code value> isn’t the parent of identification code <identification code value>.
Check that nested ICs belong to the specified aggregateThe transformed identification code <transformed identification code value> isn’t the parent of identification code <identification code value>.
Search for the moved IC in the list of the transformed code’s nested items
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (7): Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, ATK transformation, Package transformation.
Error 31Invalid code types …, …,…Direct submission
Error text: variants
Invalid code types <identification code value 1>, <identification code value 2>,…
IC (package) type checkInvalid type of code <identification code value> "<package type value>".
IC (package) type checkInvalid type of code <identification code value>: "<package type value>".
IC (package) type check
2 more text variants are in the Chestny ZNAK instructions.
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (23): Auto-introduction into circulation on import via FCS, Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. With a reason, Introduction into circulation. Cross-border trade, Return to circulation, and others.
Error 32The code already has contentsDirect submission
Error text
Identification code <identification code value> already contains nested items <nested identification code values>.
Check for nested items
- What it means
- Codes are already nested in the package.
- Why it happens
- This happens when a previous aggregation document has already been accepted.
- What to do
- Check whether the previous document has already been accepted.
Details:Aggregation
Occurs in documents (3): ATK transformation, Set formation, Package formation.
Error 33Electronic signature verification failedDirect submission
Error text
Electronic signature verification failed.
Electronic signature verification
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (8): Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Return to circulation, Cancellation of withdrawal from circulation, Write-off (general document).
Error 35Invalid type of the participant found by INN … given in field "…"Direct submission
Error text: variants
Invalid type of the participant found by INN <field value> given in field "<field name>".
Participant type checkInvalid type of the participant found by INN <organization INN> given in field "<field name>".
Participant type checkInvalid type of the participant found by INN <organization INN> given in field "INN of the participant in circulation".
Participant type check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (35): Auto-introduction into circulation on import via FCS, Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Received from individuals, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. With a reason, and others.
Error 36Invalid type of the document found by ID … given in field …Direct submission
Error text
Invalid type of the document found by ID <document identifier> given in field <field name>.
Document type check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (5): Cancellation of withdrawal from circulation, Cancellation of withdrawal from circulation (OSU), Cancellation of shipment from the EAEU, Receiving from the EAEU, Receiving from the EAEU (OSU).
Error 37Invalid status of the linked document …Direct submission
Error text
Invalid status of the linked document <document type><document identifier>.
Document status check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (4): Cancellation of withdrawal from circulation, Cancellation of withdrawal from circulation (OSU), Receiving from the EAEU, Receiving from the EAEU (OSU).
Error 38Identification code … has no nested itemsDirect submission
Error text: variants
Identification code <identification code value> has no nested items.
Check for nested ICsCode <identification code value> has no nested items.
Check for nested items
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (15): Auto-introduction into circulation on import via FCS, Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Received from individuals, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, and others.
Error 40The product group isn’t connectedDirect submission
Error text: variants
Product group <product group name> isn’t among the product groups available to the participant.
Search for the product group among those available to the participant in circulationProduct group "<product group name>" isn’t among the product groups available to the participant.
Search for the product group among those available to the participant in circulationThe product group isn’t among the product groups available to the participant.
Search for the product group among those available to the participant in circulation
- What it means
- The product group isn’t among those available to the participant.
- Why it happens
- The group isn’t added to the profile in Chestny ZNAK.
- What to do
- Connect the product group in the profile.
Details:All Chestny ZNAK error codes
Occurs in documents (35): Auto-introduction into circulation on import via FCS, Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Received from individuals, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. With a reason, and others.
Error 41The product card isn’t readyDirect submission
Error text
Insufficient description of product <product code value>.
Check of the layered product description
- What it means
- Insufficient product description.
- Why it happens
- The National Catalog card lacks the attributes of readiness for marking and circulation.
- What to do
- Bring the product card to the status “Signed” and repeat the introduction.
Details:Put into circulation
Occurs in documents (11): Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Received from individuals, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Shipment from the EAEU with IC recognition, and others.
Error 44Field … in document "…" can’t be filled inDirect submission
Error text: variants
Field <field name> in document "<document type>" can’t be filled in.
Field completion checkField "VSD identifier" in document "<document type>" can’t be filled in.
Field completion checkField <field name> can’t be filled in.
Field completion check
3 more text variants are in the Chestny ZNAK instructions.
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (23): Auto-introduction into circulation on import via FCS, Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. With a reason, Introduction into circulation. Cross-border trade, and others.
Error 46The content or name of linked document … is incorrectDirect submission
Error text
The content or name of linked document <document identifier> is incorrect.
Validation of the document content or name
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (2): Cancellation of withdrawal from circulation, Cancellation of withdrawal from circulation (OSU).
Error 47Filling in fields … at the same time isn’t allowedDirect submission
Error text: variants
Filling in fields <field name> at the same time isn’t allowed.
Check of a combination of field completionsAt least one of the fields <field name_1> and <field name_2> must be filled in in document <document name>.
Check of a combination of field completionsFor MC <identification code value 1>, <identification code value 2>, no attribute to edit is given.
Check of a combination of field completions
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (3): Correction of code information, Write-off, Package formation.
Error 48The introduction method doesn’t match the code issuance methodDirect submission
Error text: variants
Invalid method of introduction into circulation of identification code <identification code value>.
Check of the goods release methodInvalid value of the "Method of introducing goods into circulation" parameter of marking code <identification code value>.
Check of the goods release methodInvalid method of releasing goods into circulation of identification code <identification code value>.
Check of the goods release method
1 more text variant is in the Chestny ZNAK instructions.
- What it means
- Invalid method of introducing the code into circulation.
- Why it happens
- The release method in the code order doesn’t match the document type.
- What to do
- The introduction type is set by the order’s issuance type. If it was chosen incorrectly, correct the code information with a correction document.
Details:Put into circulation
Occurs in documents (17): Auto-introduction into circulation on import via FCS, Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. With a reason, Introduction into circulation. Cross-border trade, and others.
Error 49The value of field … doesn’t match the value of field … in document …Direct submission
Error text: variants
The value of field <field name> <field value> doesn’t match the value of field <linked document field name> in document <linked document type>.
Check that the values match the linked document’s parametersThe list of transferred identification codes doesn’t match the list of identification codes in the original shipment document.
IC list match checkThe value of field <field name> <field value> doesn’t match the value of field <field name> in document <document name>.
Check that the values match the document’s parameters
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (6): Return to circulation, Cancellation of withdrawal from circulation, Cancellation of withdrawal from circulation (OSU), Cancellation of shipment from the EAEU, Receiving from the EAEU, Receiving from the EAEU (OSU).
Error 51The codes have different statusesDirect submission
Error text: variants
<field name> of the identification codes aren’t identical.
Check that IC parameters are identical<parameter name> of the identification codes aren’t identical.
Check that HS codes are identical
- What it means
- The codes in the document have different values.
- Why it happens
- Codes in one document have different statuses.
- What to do
- When the statuses align, send the document again.
Details:Aggregation
Occurs in documents (12): Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Return to circulation, Receiving from the EAEU, ATK transformation, and others.
Error 52The moved identification code … is the parent of the transformed identification code …Direct submission
Error text
The moved identification code <identification code value> is the parent of the transformed identification code <transformed identification code value>.
Search for the transformed moved IC in the list of nested codes
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (2): ATK transformation, Package transformation.
Error 53Inappropriate product code range …Direct submission
Error text
Inappropriate product code range <product code value>.
Product code range check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (3): Shipment from the EAEU (OSU), Shipment from the EAEU with IC recognition, Receiving from the EAEU (OSU).
Error 54The document isn’t available for this groupDirect submission
Error text: variants
Creating a "<document type>" document isn’t available for product group <product group name>.
Check of function access in the product groupCreating a "<document type>" document isn’t available for product group <product group name> in XML format.
Check of function access in the product groupCreating a "<document type>" document isn’t available for product group <product group name> in CSV format.
Check of function access in the product group
4 more text variants are in the Chestny ZNAK instructions.
- What it means
- Creating such a document isn’t available for the product group.
- Why it happens
- This document doesn’t apply to the group. For example, introducing existing stock isn’t available for all groups.
- What to do
- Check your group’s marking conditions.
Details:All Chestny ZNAK error codes
Occurs in documents (34): Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Received from individuals, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. With a reason, Introduction into circulation. Cross-border trade, and others.
Error 55Invalid combination of the values of fields … and …Direct submission
Error text
Invalid combination of the values of fields <field name_1> and <field name_2>.
Value combination check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Introduction into circulation. Contract manufacturing.
Error 56The combination of the values of fields …, … and … is already used in the databaseDirect submission
Error text
The combination of the values of fields <field name_1>, <field name_2> and <field name_3> is already used in the database.
Check of the uniqueness of a parameter value combination
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (2): Correction of code information, Package formation.
Error 57Invalid reason for withdrawal from circulation of identification code …: …Direct submission
Error text
Invalid reason for withdrawal from circulation of identification code <identification code value>: <reason for withdrawal from circulation>.
Check of the reason for withdrawal from circulation
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Shipment from the EAEU with IC recognition.
Error 58Identification code … already has a parent identification code …Direct submission
Error text
Identification code <identification code value> already has a parent identification code <parent identification code value>.
Check for an aggregate IC
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (6): Shipment from the EAEU with IC recognition, Receiving from the EAEU, ATK transformation, Package transformation, ATK formation, Package formation.
Error 59Invalid status of product group …Direct submission
Error text: variants
Invalid status of product group <product group name>.
Check of the participant in circulation’s status in the product groupThe paid codes agreement for product group <product group name> isn’t signed by the participant.
Check of the participant in circulation’s status in the product group
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (19): Introduction into circulation. Import via FCS, Introduction into circulation. Existing stock, Introduction into circulation. Received from individuals, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Withdrawal from circulation, Correction of code information, and others.
Error 60The product isn’t in the National CatalogDirect submission
Error text: variants
Products with GTIN (<product code value>) aren’t registered in the National Catalog of marked goods.
Check for the product code in the National CatalogVSD identifier <VSD identifier> in document "<document type>" differs from the VSD identifier given in the MC order.
Check that the IC doesn’t belong to the current participant in circulation
- What it means
- Products with this GTIN aren’t registered in the National Catalog.
- Why it happens
- The card wasn’t created, or the GTIN has a typo.
- What to do
- Check the product code and the card.
Details:GTIN in marking
Occurs in documents (9): Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Shipment from the EAEU (OSU), Receiving from the EAEU, Import notice (EAEU), and others.
Error 61The participant’s INN differs from the INN of the business entity the VSD is issued to in FGIS…Direct submission
Error text
The participant’s INN differs from the INN of the business entity the VSD is issued to in FGIS "VetIS"
INN check in FGIS VetIS
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (8): Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Correction of code information, Shipment from the EAEU (OSU), Receiving from the EAEU.
Error 62… from document "…" has the status "Canceled" in FGIS "VetIS"Direct submission
Error text: variants
<field name> <field value> from document "<document name>" has the status "Canceled" in FGIS "VetIS"
VSD status check in FGIS VetISVSD identifier <VSD identifier> has the status "Canceled" in FGIS "VetIS".
VSD status check in FGIS VetISPackage type <package type value> can’t be placed into package <package type value>
Check of the package type of the ICs in the aggregate
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (10): Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Return to circulation, Correction of code information, Shipment from the EAEU (OSU), and others.
Error 63Product code … from document "…" doesn’t match the product code given in FGIS "VetIS"Direct submission
Error text: variants
Product code <field value> from document "<document name>" doesn’t match the product code given in FGIS "VetIS".
Product code checkInvalid decision code in the goods declaration. Introduction into circulation not performed.
Decision code checkProduct code <product code value> doesn’t match the product code given in FGIS "VetIS".
Product code check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (8): Auto-introduction into circulation on import via FCS, Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Correction of code information, Shipment from the EAEU (OSU).
Error 64No response from FGIS "VetIS" to the VSD information request in document …Direct submission
Error text: variants
No response from FGIS "VetIS" to the VSD information request in document <document type>
Request processing time checkNo response from FGIS "VetIS" to the VSD information request.
Request processing time check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (9): Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Correction of code information, Shipment from the EAEU (OSU), Receiving from the EAEU, and others.
Error 65The controlled-goods attribute isn’t given for the product code (or "product codes" if more than one): ……Direct submission
Error text
The controlled-goods attribute isn’t given for the product code (or "product codes" if more than one): <PC1 value> (, <PC2 value>, <PC3 value>, …..).
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (7): Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Shipment from the EAEU (OSU), Receiving from the EAEU.
Error 66… in document "…" not found in the FGIS "VetIS" databaseDirect submission
Error text: variants
<field name> <field value> in document "<document name>" not found in the FGIS "VetIS" database
Check for the controlled-goods attribute of the product codeOne or more values of field "VSD identifier" <VSD identifier> not found in the FGIS "VetIS" database.
Check for the controlled-goods attribute of the product codeAggregate <identification code value> isn’t empty.
Check for nested items
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (11): Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Return to circulation, Correction of code information, Shipment from the EAEU (OSU), and others.
Error 67Internal service errorDirect submission
Error text: variants
Internal service error
System error when accessing FGIS "VetIS"System error when accessing FGIS "VetIS".
VSD check in VetIS
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (9): Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Correction of code information, Shipment from the EAEU (OSU), Receiving from the EAEU, and others.
Error 69The document content or name is incorrect. Couldn’t parseDirect submission
Error text
The document content or name is incorrect. Couldn’t parse.
Validation of the document file content and name
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Write-off (general document).
Error 71The document content is incorrect. Incorrect data: field … isn’t filled inDirect submission
Error text: variants
The document content is incorrect. Incorrect data: field <field name> isn’t filled in.
Field completion checkThe document content is incorrect. Incorrect data: field <field name>.
Date format checkThe document content is incorrect. Incorrect data: field <field name> can’t be filled in.
Check that the field is absent
2 more text variants are in the Chestny ZNAK instructions.
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (5): Cancellation of withdrawal from circulation (OSU), Cancellation of shipment under a UTD, Write-off (general document), Import notice (EAEU), Notice of code state.
Error 72Incorrect document type: …Direct submission
Error text
Incorrect document type: <document type>
Check of the specified document type
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Cancellation of shipment under a UTD.
Error 73Incorrect issuance typeDirect submission
Error text: variants
Incorrect issuance type
Issuance type checkIncorrect issuance type. The HS code can’t be changed for an IC with the issuance type “Imported into Russia”.
Issuance type check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (2): Correction of code information, Package formation.
Error 74The statuses of the identification codes in the "Aggregation" document don’t matchDirect submission
Error text
The statuses of the identification codes in the "Aggregation" document don’t match
Check that IC parameters are identical
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Package formation.
Error 75Marking code … has an incorrect issuance typeDirect submission
Error text
Marking code <marking code value> has an incorrect issuance type
Issuance type check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (2): Import notice (EAEU), Import notice (non-EAEU).
Error 76Document with id … not foundDirect submission
Error text
Document with id <document identifier> not found
Check that the document exists in the system
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Cancellation of shipment under a UTD.
Error 79Application identifiers must be given without surrounding bracketsDirect submission
Error text: variants
Application identifiers must be given without surrounding brackets
Check of the KITU format for brackets in application identifiers AI (00, 01, 21)Invalid marking code <identification code value>
Value format checkInvalid marking code <identification code value>.
Check of the IC format for length and allowed characters
3 more text variants are in the Chestny ZNAK instructions.
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (3): Reweighing report, Write-off (general document), Package formation.
Error 89IC … is missing in PG …Direct submission
Error text
IC <identification code value> is missing in PG <product group name>.
Check that the IC matches the product group
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (2): Correction of code information, Reweighing report.
Error 107Signature validation errorDirect submission
Error text: variants
Signature validation error.
Signature validity checkThe signature isn’t valid.
Signature validity check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (2): Reweighing report, Notice of code state.
Error 110Incorrect status of document …: …Direct submission
Error text
Incorrect status of document <document identifier>: <status value>
Check whether actions can be performed on the document
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Cancellation of shipment under a UTD.
Error 113The code is inside a packageDirect submission
Error text: variants
Identification code <identification code value> is part of aggregate <parent identification code value>.
Check for an aggregate code for nested ICsThe identification code is part of aggregate <parent identification code value>.
Check for an aggregate code for nested ICs
- What it means
- The identification code is part of an aggregate.
- Why it happens
- The document was sent for a code nested in a box or package.
- What to do
- Work with the package or disaggregate it.
Details:Aggregation
Occurs in documents (11): Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Shipment from the EAEU with IC recognition, Receiving from the EAEU, and others.
Error 114Invalid parent identification code type …: …Direct submission
Error text
Invalid parent identification code type <identification code value>: <aggregate identification code type>.
Aggregate IC type check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (10): Auto-introduction into circulation on import via FCS, Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Correction of code information, Shipment from the EAEU with IC recognition, and others.
Error 115Identification code … with the controlled-goods attribute, part of aggregate …, isn’t givenDirect submission
Error text
Identification code <identification code value> with the controlled-goods attribute, part of aggregate <aggregate identification code value>, isn’t given.
Check of the aggregate’s nested codes
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (6): Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Receiving from the EAEU.
Error 118The allowed number of aggregation levels inside … is exceededDirect submission
Error text
The allowed number of aggregation levels inside <top-level aggregate identification code value> is exceeded
Aggregation level count check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (5): Shipment to the EAEU, Shipment from the EAEU with IC recognition, Receiving from the EAEU, Package transformation, Package formation.
Error 119ExpiredDirect submission
Error text: variants
The shelf life of product <identification code value> expired on <expiry date>.
Product shelf life checkThe specified date <"expirationDate" attribute value> (field "expirationDate") exceeds the product expiry date <expiry date>.
Product shelf life checkThe specified date <"expirationDate" attribute value> (field "expirationDate") exceeds the product expiry date after the keg is connected to dispensing equipment, given by the manufacturer in the product card.
Product shelf life check
1 more text variant is in the Chestny ZNAK instructions.
- What it means
- The product shelf life has expired.
- Why it happens
- The goods are expired, or the expiry date in the code information is wrong.
- What to do
- Check the expiry date in the code information.
Details:All Chestny ZNAK error codes
Occurs in documents (6): Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Cross-border trade, Return to circulation, Connecting a keg to dispensing equipment.
Error 120Not enough money on the balanceDirect submission
Error text
The participant’s balance has insufficient funds.
Balance check
- What it means
- The participant’s balance has insufficient funds.
- Why it happens
- The Chestny ZNAK balance isn’t topped up.
- What to do
- Top up the balance in Chestny ZNAK and repeat the introduction.
Details:All Chestny ZNAK error codes
Occurs in documents (7): Auto-introduction into circulation on import via FCS, Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade.
Error 121Invalid issuing country codeDirect submission
Error text
Invalid issuing country code.
Check of the IC issuing country
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Shipment from the EAEU with IC recognition.
Error 122Identification code … contains nested itemsDirect submission
Error text
Identification code <identification code value> contains nested items.
Check that there are no nested ICs
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Shipment from the EAEU with IC recognition.
Error 124The reference aggregate composition in the NCMG doesn’t match the one declared in the documentDirect submission
Error text: variants
The reference aggregate composition in the NCMG doesn’t match the one declared in the document.
Check that the reference and actual aggregate compositions matchRe-import of aggregate <identification code value> is prohibited
Check of the aggregate’s nested itemsPartial receiving of the aggregate isn’t available <identification code value>"
Check that all of the aggregate’s nested items are given
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (4): Shipment from the EAEU with IC recognition, Receiving from the EAEU, Set formation, Package formation.
Error 126The crypto tail is missing or incorrectDirect submission
Error text
The crypto tail is missing or incorrect.
Check of the marking code for a valid crypto tail
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Federal special stamp application report.
Error 128Document processing error in the EAEU Operator’s information system. Error text: …Direct submission
Error text: variants
Document processing error in the EAEU Operator’s information system. Error text: <error text received from the EAEU Operator>.
Logical document control in the EAEU Operator’s information systemThe number of array elements must not exceed <allowed range>.
Check of the number of ICs in the array
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (3): Shipment to the EAEU, Shipment to the EAEU (OSU), Reweighing report.
Error 129The data of identification codes …, …,… was updated by another documentDirect submission
Error text: variants
The data of identification codes <identification code value 1>, <identification code value 2>,… was updated by another document.
Check of IC data against the VSD in FGIS VetISField <field value> isn’t filled in.
Check that the participant in circulation’s INN is filled in
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (6): Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Reweighing report.
Error 130Field … must contain digits onlyDirect submission
Error text
Field <INN of the participant in circulation> must contain digits only.
Check of the content of field <INN of the participant in circulation>
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Reweighing report.
Error 131For identification code …, the type of the specified VSD … from the FGIS VetIS response doesn’t match the type…Direct submission
Error text: variants
For identification code <identification code value>, the type of the specified VSD <VSD type> from the FGIS VetIS response doesn’t match the introduction into circulation type.
VSD type checkThe type of the specified VSD <VSD type> doesn’t match the operation performed.
Storage conditions check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (7): Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Correction of code information, Receiving from the EAEU.
Error 132Storage conditions information doesn’t match the data in product card …Direct submission
Error text
Storage conditions information doesn’t match the data in product card <product code value>.
Storage conditions check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Correction of code information.
Error 133The data in product card … doesn’t match the data of Marking Code …Direct submission
Error text
The data in product card <product code value> doesn’t match the data of Marking Code <identification code value>.
Set composition check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (2): Set formation, Package formation.
Error 134The code is not part of the set compositionDirect submission
Error text: variants
<identification code value> can’t be aggregated into a set because the hierarchy <set identification code value> doesn’t provide for it.
Set composition check<product code value>, provided for by the hierarchy <aggregate identification code>, is missing in the aggregation document.
Set composition check
- What it means
- The code can’t be nested into a set: it isn’t part of the set composition.
- Why it happens
- The set composition in the card doesn’t match the goods being nested.
- What to do
- Compare the set composition in the product card.
Details:Aggregation
Occurs in documents (2): Set formation, Package formation.
Error 135All nested items of set … must be filled in at onceDirect submission
Error text
All nested items of set <set identification code value> must be filled in at once.
Set composition check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (2): Set formation, Package formation.
Error 137The value of field … can’t be an empty arrayDirect submission
Error text: variants
The value of field <field value> can’t be an empty array.
IC array completion checkField <field value> isn’t filled in.
IC array completion check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Reweighing report.
Error 138The value of field … isn’t unique in the current arrayDirect submission
Error text: variants
The value of field <field name> isn’t unique in the current array.
Check of value uniqueness in the current arrayThe value of field <field name> <duplicate value> isn’t unique in the current array.
Check of value uniqueness in the current array
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (2): Correction of code information, Reweighing report.
Error 139IC … is in a transactionDirect submission
Error text
IC <identification code value> is in a transaction.
IC status check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Reweighing report.
Error 140… isn’t filled inDirect submission
Error text
<QES in base64 format> isn’t filled in.
Signature completion check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Reweighing report.
Error 186More than 30,000 recordsDirect submission
Error text: variants
The number of records in the document exceeds 30,000.
Record count checkThe number of codes in the document exceeds 100,000.
Code count checkThe number of records in the document exceeds 100,000.
Record count check
2 more text variants are in the Chestny ZNAK instructions.
- What it means
- The number of records in the document exceeds 30,000.
- Why it happens
- Too many codes ended up in one document.
- What to do
- Split the document into several.
Details:All Chestny ZNAK error codes
Occurs in documents (11): Introduction into circulation. With a reason, Withdrawal from circulation, Correction of code information, Shipment to the EAEU, Shipment from the EAEU (OSU), Shipment from the EAEU with IC recognition, Connecting a keg to dispensing equipment, Write-off (general document), and others.
Error 189Participant … is blocked in EGAISDirect submission
Error text: variants
Participant <organization INN> is blocked in EGAIS.
Check that the INN isn’t blocked in EGAISPlace of business <KPP> is blocked in EGAIS.
Check that the place of business isn’t blocked in EGAISPlace of business <KPP> / <FIAS code> is blocked in EGAIS.
Check that the place of business isn’t blocked in EGAIS
2 more text variants are in the Chestny ZNAK instructions.
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (7): Auto-introduction into circulation on import via FCS, Introduction into circulation. Import via FCS, Introduction into circulation. Cross-border trade, Withdrawal from circulation, Federal special stamp application report, Connecting a keg to dispensing equipment, Notice of code state.
Error 190Incorrect IC quantity dataDirect submission
Error text
Incorrect IC quantity data
Check of the UTD document’s OSU value against the regular expression 02[gtin]37[count], where [gtin] is <product code> (14 digits), [count] is the product quantity in the package unit of measure (1 to 8 digits); the value is given without brackets or other separators. Example: 02046111111111113710
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Cancellation of shipment under a UTD.
Error 191Aggregate … matches the regular expression for OSUDirect submission
Error text
Aggregate <identification code value> matches the regular expression for OSU
Check of the KITU against the volume and grade tracking regular expressions 02[gtin]37[count] and 02[gtin]37[count]3103[netWeight], where “gtin” is <product code> (14 digits), “count” is the product quantity in the package unit of measure (1 to 8 digits), “netWeight” is the variable weight in kilograms (only for the “Dairy products” product group; given in the universal transfer document; may be absent if the weight is given in a field of the universal document; 9 digits: the first 6 are kilograms, the last 3 are grams; missing positions are filled with leading zeros)
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Package formation.
Error 193The allowed number of identification codes inside package … is exceededDirect submission
Error text
The allowed number of identification codes inside package <identification code value> is exceeded
Check of the number of the aggregate’s nested items
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (2): Shipment to the EAEU, Shipment from the EAEU with IC recognition.
Error 194The allowed number of identification codes inside the package at all levels … is exceededDirect submission
Error text
The allowed number of identification codes inside the package at all levels <marking code value> is exceeded
Check of the allowed number of ICs inside a package
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Shipment to the EAEU.
Error 195The product card must have the specialized packaging attribute (packageCharacteristic…
Direct submission
Error text
The product card must have the specialized packaging attribute (packageCharacteristic = "КЕГ").
Check of the packaging characteristic in the NCMG product card
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Connecting a keg to dispensing equipment.
Error 196FIAS code … isn’t in the list of places of business for this organization with INN …Direct submission
Error text: variants
FIAS code <FIAS code> isn’t in the list of places of business for this organization with INN <organization INN>.
FIAS code checkMore than one place of business found for the organization by the specified INN <organization INN>, KPP <KPP>, FIAS <FIAS code>.
Check of the number of places of business by KPPMore than one place of business found for the organization by the specified INN <INN of the participant in circulation>, KPP <KPP>, FIAS <FIAS code>.
Place of business check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (7): Auto-introduction into circulation on import via FCS, Withdrawal from circulation, Connecting a keg to dispensing equipment, Write-off (general document), Import notice (EAEU), Import notice (non-EAEU), Notice of code state.
Error 202The permit document isn’t in the cardDirect submission
Error text: variants
For marking code <marking code value>, the specified permit document <permit document information> is missing in the product card.
Data match checkThe permit documents given in the GD/MC don’t match product card <product code>
Data match checkThe specified permit document <permit document information> is missing in the product card.
Data match check
- What it means
- The specified permit document isn’t in the product card.
- Why it happens
- The document isn’t added to the National Catalog card.
- What to do
- Add the document to the product card, wait for moderation and sign the card. Then repeat the introduction.
Details:Permit documents on introduction into circulation
Occurs in documents (8): Auto-introduction into circulation on import via FCS, Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Cross-border trade, Correction of code information, Receiving from the EAEU, Import notice (EAEU).
Error 204Only the party that applied marking code … can edit parameter …Direct submission
Error text: variants
Only the party that applied marking code <identification code value> can edit parameter <parameter name>.
Participant in circulation checkParameter <parameter name> can be edited by the party that applied or introduced into circulation marking code <identification code value>.
Participant in circulation checkParameter <parameter name> can be edited by the importer of goods from outside the EAEU or by the party that applied marking code <identification code value>.
Participant in circulation check
1 more text variant is in the Chestny ZNAK instructions.
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Correction of code information.
Error 205… can’t be changed for an identification code nested in a KIGUDirect submission
Error text
<field name> can’t be changed for an identification code nested in a KIGU.
Check whether the IC is nested in a KIGU
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Correction of code information.
Error 209The product card lacks or has incorrect attributes for calculating the VSD balance …Direct submission
Error text
The product card lacks or has incorrect attributes for calculating the VSD balance <VSD identifier>
Check against the information given in the VSD
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (7): Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Cross-border trade, Correction of code information, Receiving from the EAEU, Receiving from the EAEU (OSU).
Error 210The maximum allowed volume/weight is exceeded when crediting to the VSD balance …Direct submission
Error text
The maximum allowed volume/weight is exceeded when crediting to the VSD balance <VSD identifier>
Check against the information given in the VSD
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (8): Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Correction of code information, Receiving from the EAEU, Receiving from the EAEU (OSU).
Error 211Incorrect data for calculating the VSD balance …Direct submission
Error text
Incorrect data for calculating the VSD balance <VSD identifier>
Check against the information given in the VSD
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (8): Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Correction of code information, Receiving from the EAEU, Receiving from the EAEU (OSU).
Error 212The expiration date does not match the VSDDirect submission
Error text
The expiry date of IC <identification code value> doesn’t match the expiry date of VSD <VSD identifier>
Check against the information given in the VSD
- What it means
- The code’s expiry date doesn’t match the date in the veterinary accompanying document.
- Why it happens
- A VSD of another batch is given, or the expiry date is wrong.
- What to do
- Check that the VSD for this very batch is given. If the VSD is correct, correct the codes’ expiry date with a code information correction.
Details:All Chestny ZNAK error codes
Occurs in documents (1): Receiving from the EAEU.
Error 213VSD identifier … given in the document must not match the identifier in MC …Direct submission
Error text
VSD identifier <VSD identifier> given in the document must not match the identifier in MC <identification code value>
Check of whether the VSD in the document matches the VSD in the IC
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Correction of code information.
Error 214Marking code … is blocked by a government authority. The operation can’t be performedDirect submission
Error text
Marking code <identification code value> is blocked by a government authority. The operation can’t be performed
IC blocking check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Connecting a keg to dispensing equipment.
Error 218GIS MT has already registered the connection of this product unit … to dispensing equipmentDirect submission
Error text
GIS MT has already registered the connection of this product unit <identification code value> to dispensing equipment.
IC special state check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Connecting a keg to dispensing equipment.
Error 243The document type isn’t given; the «type» or «ftsType» parameter is mandatory
Direct submission
Error text: variants
The document type isn’t given; the «type» or «ftsType» parameter is mandatory
Check that the permit document type is filled inA permit document parameter (type, number) is missing
Check that the permit document information is filled in
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (14): Auto-introduction into circulation on import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Return to circulation, Correction of code information, and others.
Error 244The identification code is already in the gray zoneDirect submission
Error text
The identification code is already in the gray zone.
Check whether the IC is in the gray zone
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Notice of temporarily untraceable codes.
Error 245For the following GTINs … information from the FCS is required. Use the "Import via FCS" document
Direct submission
Error text
For the following GTINs <product code value> information from the FCS is required. Use the "Import via FCS" document
Check of document availability for the GTIN
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Introduction into circulation. Production outside the EAEU.
Error 246An incorrect permit document type is givenDirect submission
Error text: variants
An incorrect permit document type is given.
Permit document type checkAn incorrect type is given for permit document "<permit document number>"
Permit document kind check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (14): Auto-introduction into circulation on import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Return to circulation, Correction of code information, and others.
Error 247The permit document date isn’t givenDirect submission
Error text: variants
The permit document date isn’t given.
Check that the permit document date is filled inThe date of permit document "<permit document number>" isn’t given
Check that the permit document date is filled in
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (14): Auto-introduction into circulation on import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Return to circulation, Correction of code information, and others.
Error 248An incorrect date is given for the permit documentDirect submission
Error text: variants
An incorrect date is given for the permit document.
Permit document date checkAn incorrect date is given for permit document "<permit document number>"
Permit document date check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (14): Auto-introduction into circulation on import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Return to circulation, Correction of code information, and others.
Error 249An incorrect permit document number is given. Position of the incorrect character: XXDirect submission
Error text: variants
An incorrect permit document number is given. Position of the incorrect character: XX.
Permit document number checkAn incorrect permit document number "<permit document number>" is given
Permit document number check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (14): Auto-introduction into circulation on import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Return to circulation, Correction of code information, and others.
Error 250The permit document number isn’t givenDirect submission
Error text: variants
The permit document number isn’t given.
Check that the permit document number is filled inThe permit document number isn’t given
Check that the permit document number is filled in
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (14): Auto-introduction into circulation on import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Return to circulation, Correction of code information, and others.
Error 251A mandatory parameter is missing: the medical device modelDirect submission
Error text
A mandatory parameter is missing: the medical device model.
Check that the medical device model is filled in
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (6): Auto-introduction into circulation on import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Cross-border trade, Receiving from the EAEU, Import notice (EAEU).
Error 252Changing MC … information is temporarily unavailable until processing of MCs introduced into circulation during…Direct submission
Error text
Changing MC <identification code value> information is temporarily unavailable until processing of MCs introduced into circulation during the VetIS emergency mode is finished
VSD identifier check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Correction of code information.
Error 253The actual number of nested items in Set … doesn’t match the reference number of goods in the SetDirect submission
Error text
The actual number of nested items in Set <number of nested items> doesn’t match the reference number of goods in the Set
Check of the actual number of nested items in a set
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (2): Set formation, Package formation.
Error 255An incorrect permit document number is given. The number is incompleteDirect submission
Error text: variants
An incorrect permit document number is given. The number is incomplete.
Permit document number checkAn incorrect permit document number "<permit document number>" is given. The number is incomplete.
Permit document number check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (14): Auto-introduction into circulation on import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Return to circulation, Correction of code information, and others.
Error 256An incorrect permit document number is given. Position of the incorrect character:…Direct submission
Error text: variants
An incorrect permit document number is given. Position of the incorrect character: XX. It’s recommended to replace the characters with Latin/Cyrillic.
Permit document number checkAn incorrect permit document number "<permit document number>" is given. The characters must be replaced with Latin or Cyrillic.
Permit document number check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (14): Auto-introduction into circulation on import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Existing stock, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Return to circulation, Correction of code information, and others.
Error 261The operation is unavailable because there’s no license for the specified product type or activityDirect submission
Error text
The operation is unavailable because there’s no license for the specified product type or activity.
License check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (10): Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Withdrawal from circulation, Receiving from the EAEU, Write-off (general document), and others.
Error 262The operation is unavailable because the specified address isn’t in the licenseDirect submission
Error text
The operation is unavailable because the specified address isn’t in the license.
License check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (10): Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Withdrawal from circulation, Receiving from the EAEU, Write-off (general document), and others.
Error 263The operation is unavailable because there are no active licenses for the specified activity…Direct submission
Error text
The operation is unavailable because there are no active licenses for the specified activity or product type.
License check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (10): Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Withdrawal from circulation, Receiving from the EAEU, Write-off (general document), and others.
Error 265Marking code … was changed by a later document: …Direct submission
Error text
Marking code <identification code value> was changed by a later document: <document identifier>.
Check that the document being canceled matches the document that last changed the code
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Cancellation of withdrawal from circulation.
Error 268The permit document is not validDirect submission
Error text
<PD type>, <PD number>, <PD date> has an invalid status (status group <status group>) for marking code <identification code value>. <PD error description>
PD status check
- What it means
- The permit document is in a status not allowed for the code.
- Why it happens
- The declaration or certificate is suspended, terminated or expired.
- What to do
- Give a valid document and repeat the introduction.
Details:Permit documents on introduction into circulationPermit documents
Occurs in documents (8): Auto-introduction into circulation on import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Introduction into circulation. Production outside the EAEU, Introduction into circulation. Cross-border trade, Correction of code information, Receiving from the EAEU, Import notice (EAEU).
Error 269The specified government contract identifier doesn’t match the information submitted at…Direct submission
Error text
The specified government contract identifier doesn’t match the information submitted at withdrawal from circulation of identification code <identification code value>.
Government contract identifier check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Return to circulation.
Error 273MC … not shippedDirect submission
Error text
MC <identification code value> not shipped
Check the content of the previously sent product shipment document between INNs / movement between places of business in GIS MT, or send a new shipment document
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Cancellation of shipment under a UTD.
Error 274MC … already shippedDirect submission
Error text
MC <identification code value> has already been shipped.
Identification code state check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (8): Introduction into circulation. Import via FCS, Withdrawal from circulation, Shipment from the EAEU with IC recognition, Receiving from the EAEU, Write-off (general document), Import notice (EAEU), Notice of code state, Package formation.
Error 276MC … shipped by another document …Direct submission
Error text
MC <identification code value> shipped by another document <document identifier>
Check of the status of the previously sent product shipment document between INNs / movement between places of business in GIS MT
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Cancellation of shipment under a UTD.
Error 282Couldn’t identify the consignor’s/consignee’s place of businessDirect submission
Error text
Couldn’t identify the consignor’s/consignee’s place of business.
Place of business uniqueness check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Federal special stamp application report.
Error 341The document has an incorrect license number formatDirect submission
Error text
The document has an incorrect license number format
License number format check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (3): Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Correction of code information.
Error 342For aggregate …, PD that doesn’t apply to any nested item is given: …Direct submission
Error text
For aggregate <aggregate marking code value>, PD that doesn’t apply to any nested item is given: <permit document number>
Permit document match check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (3): Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Receiving from the EAEU.
Error 344The document sender’s INN must match the shipment document sender’s INNDirect submission
Error text
The document sender’s INN must match the shipment document sender’s INN
Check of the sender of the cancellation of the “UTD (product shipment)” document
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Cancellation of shipment under a UTD.
Error 356Partial retirement isn’t available for this unit of measureDirect submission
Error text
Partial retirement isn’t available for this unit of measure
Data match check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Withdrawal from circulation.
Error 357Partial retirement isn’t available for this reason for withdrawal from circulationDirect submission
Error text
Partial retirement isn’t available for this reason for withdrawal from circulation.
Check whether partial retirement is available for the reason for withdrawal from circulation
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Withdrawal from circulation.
Error 358The total number of consumption units must not exceed the package capacityDirect submission
Error text
The total number of consumption units must not exceed the package capacity
Check for exceeding the package volume in partial sale
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Withdrawal from circulation.
Error 362Batch number … not found in the Batch RegisterDirect submission
Error text: variants
Batch number <batch number> not found in the Batch Register
Check for the batch number in the batch registerSet batch number <aggregate batch number> not found in the batch register
Set batch number not foundNested item batch number <nested item batch number> not found in the batch register
Nested item batch not found
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (4): Withdrawal from circulation (OSU), Correction of code information, Receiving from the EAEU, Package formation.
Error 363The document sender’s INN must match the batch owner’s INN in the Batch RegisterDirect submission
Error text
The document sender’s INN must match the batch owner’s INN in the Batch Register
Check that the sender’s INN matches the batch owner’s INN in the Batch Register
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Correction of code information.
Error 364The GTIN from the document must match the GTIN in the Batch Register
Direct submission
Error text
The GTIN from the document must match the GTIN in the Batch Register
Check that the product code from the document matches the product code in the batch register
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (2): Withdrawal from circulation (OSU), Correction of code information.
Error 366The production date in the document must equal the production date in the batch register for code…Direct submission
Error text
The production date in the document must equal the production date in the batch register for marking code <marking code value>
Comparison of the production date in the document and in the batch register
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (3): Introduction into circulation. Import via FCS, Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia.
Error 367A batch number is mandatory for KIN … of product group …Direct submission
Error text
A batch number is mandatory for KIN <marking code value> of product group <product group name>
The set batch number is mandatory with the current configuration
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Package formation.
Error 368Aggregate type … doesn’t match the one given in the unitSerialNumberType field
Direct submission
Error text
Aggregate type <identification code value> doesn’t match the one given in the unitSerialNumberType field
Aggregate package type validation
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Package formation.
Error 369Nested item codes must contain at least one code from the aggregate’s product group …Direct submission
Error text
Nested item codes must contain at least one code from the aggregate’s product group <identification code value>
Check that the product groups of the set and its nested items match
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Package formation.
Error 370Creating multi-product set … isn’t supported without describing its nested items in the product cardDirect submission
Error text
Creating multi-product set <identification code value> isn’t supported without describing its nested items in the product card
Check of the set’s product groups for multi-product content
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Package formation.
Error 374The operation isn’t available for multi-product aggregatesDirect submission
Error text
The operation isn’t available for multi-product aggregates
Check of the product groups of the set and its nested items for multi-product content
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Package transformation.
Error 376The product group isn’t allowed to form batches for gtin …Direct submission
Error text: variants
The product group isn’t allowed to form batches for gtin <product code value>
Product group checkA batch number can’t be given for product group <product group name> and/or MC type <MC type values>
Product group and MC type checkA batch number can’t be given for a package
MC type check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Shipment from the EAEU with IC recognition.
Error 377The allowed number of reserved batches is exceededDirect submission
Error text
The allowed number of reserved batches is exceeded
Check of the number of reserved batches
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Shipment from the EAEU with IC recognition.
Error 378Batch number … already existsDirect submission
Error text
Batch number <batch number> already exists
Batch number uniqueness check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Shipment from the EAEU with IC recognition.
Error 379The INN doesn’t match the batch register …Direct submission
Error text
The INN doesn’t match the batch register <batch number>
Check that the INN matches the Batch Register
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Receiving from the EAEU.
Error 380Batch identifier … must contain the production date and gtinDirect submission
Error text
Batch identifier <batch number> must contain the production date and gtin
Check that the batch number matches the structure
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Shipment from the EAEU with IC recognition.
Error 381Duplicate nested item batches … found in the set composition for batch …Direct submission
Error text
Duplicate nested item batches <nested item batch number> found in the set composition for batch <aggregate batch number>
Duplicate elements found in the set composition
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Package formation.
Error 382The batch number of IC … doesn’t match the batch number in VSD …Direct submission
Error text: variants
The batch number of IC <identification code value> doesn’t match the batch number in VSD <VSD identifier>
Batch number match checkThe reference composition for set batch <aggregate batch number> is already registered
The reference composition for the batch is already recorded
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (3): Introduction into circulation. Contract manufacturing, Introduction into circulation. Production in Russia, Package formation.
Error 385Error aggregating document …Direct submission
Error text
Error aggregating document <document identifier>
Aggregation error check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Shipment from the EAEU with IC recognition.
Error 388auto-introduction into circulation isn’t allowed for PG …Direct submission
Error text
388: auto-introduction into circulation isn’t allowed for PG <product group name>
Check of document availability for the product group
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Auto-introduction into circulation on import via FCS.
Error 389For IC …, no notice of shipping products outside Russia was submitted to the marking systemDirect submission
Error text
For IC <identification code value>, no notice of shipping products outside Russia was submitted to the marking system
IC special state check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Withdrawal from circulation.
Error 395The FCS decision code must be the same for all child ICs … within one KINU/KIGUDirect submission
Error text
The FCS decision code must be the same for all child ICs <identification code value> within one KINU/KIGU
FCS decision code check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Auto-introduction into circulation on import via FCS.
Error 396A package type not allowed for transformationDirect submission
Error text
A package type not allowed for transformation
Check of the package type of the aggregate being transformed
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Package transformation.
Error 400The document body isn’t valid JSON
Direct submission
Error text
The document body isn’t valid JSON.
Check of converting the request body to json
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Reweighing report.
Error 402The product group in the request doesn’t match the group in product card …Direct submission
Error text
The product group in the request doesn’t match the group in product card <product code value searched>
Check of the product group match in the product card
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Receiving from the EAEU.
Error 412Marking code … has the alcohol-containing product attribute; this operation requires…Direct submission
Error text
Marking code <identification code value> has the alcohol-containing product attribute; this operation requires a UTD
Alcohol content check for a product unit, an aggregate and its nested items
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Withdrawal from circulation.
Error 416Different compositions for set batch … found in the documentDirect submission
Error text
Different compositions for set batch <aggregate batch number> found in the document
A set composition conflict found in the document
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Package formation.
Error 417The set composition for batch … doesn’t match the previously registered referenceDirect submission
Error text
The set composition for batch <aggregate batch number> doesn’t match the previously registered reference
The set composition doesn’t match the previously recorded reference
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Package formation.
Error 418Couldn’t save the reference set composition for aggregation operation …Direct submission
Error text
Couldn’t save the reference set composition for aggregation operation <aggregation operation number>
Couldn’t save the reference set composition
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Package formation.
Error 419Couldn’t roll back the set composition registration for aggregation operation …Direct submission
Error text
Couldn’t roll back the set composition registration for aggregation operation <aggregation operation number>
Couldn’t roll back the reference recording
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Package formation.
Error 432Filling in the OKPD2 field isn’t allowed for product group …Direct submission
Error text
Filling in the OKPD2 field isn’t allowed for product group <product group name>
Check of field completion for the product group
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Receiving from the EAEU.
Error 433OKPD2 can be given only for product unitsDirect submission
Error text
OKPD2 can be given only for product units
Check of field completion for product units
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Receiving from the EAEU.
Error 434For marking code …, the OKPD2 value doesn’t match the one in the product cardDirect submission
Error text
For marking code <marking code value>, the OKPD2 value doesn’t match the one in the product card
Check that the value matches the product card
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Receiving from the EAEU.
Error 435OKPD2 … doesn’t match HS code … for PG …Direct submission
Error text
OKPD2 <OKPD2 code> doesn’t match HS code <HS code> for PG <product group name>
Check that OKPD2 matches the HS code for the product group
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Receiving from the EAEU.
Error 438For marking code …, all nested marking codes must belong to one GTIN
Direct submission
Error text
For marking code <identification code value>, all nested marking codes must belong to one GTIN
Check of the product code of the aggregate’s nested codes
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Notice of code state.
Error 439VSD … in the document doesn’t match the VSD for batch … in the batch structureDirect submission
Error text: variants
VSD <VSD identifier> in the document doesn’t match the VSD for batch <batch number> in the batch structure
Batch register checkProduction date <production date> in the document doesn’t match the production date in the structure of batch number <batch number>
Batch register check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Correction of code information.
Error 440The VSD for marking code … doesn’t match the VSD of batch … in the batch structureDirect submission
Error text: variants
The VSD for marking code <marking code value> doesn’t match the VSD of batch <batch number> in the batch structure
Batch register checkProduction date <production date> for marking code <marking code value> doesn’t match the production date in the structure of batch number <batch number>
Batch register check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Correction of code information.
Error 441VSD … in the document doesn’t match the VSD for the batch with marking code … in the batch structureDirect submission
Error text: variants
VSD <VSD identifier> in the document doesn’t match the VSD for the batch with marking code <marking code value> in the batch structure
Batch register checkProduction date <production date> in the document doesn’t match the production date in the batch number structure from marking code <marking code value>
Batch register check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Correction of code information.
Error 442The batch number for marking code … in the document doesn’t match the batch number in the VSD register …Direct submission
Error text
The batch number for marking code <marking code value> in the document doesn’t match the batch number in the VSD register <VSD identifier>
VSD register check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Correction of code information.
Error 443Batch number … in the document doesn’t match the batch number in the VSD register for marking code …Direct submission
Error text
Batch number <batch number> in the document doesn’t match the batch number in the VSD register for marking code <marking code value>
VSD register check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Correction of code information.
Error 444Batch number … in the document doesn’t match the batch number in the VSD register …Direct submission
Error text
Batch number <batch number> in the document doesn’t match the batch number in the VSD register <VSD identifier>
VSD register check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Correction of code information.
Error 446A batch number can’t be given for KIN … because its nested items have no batch numberDirect submission
Error text
A batch number can’t be given for KIN <marking code value> because its nested items have no batch number
The set batch number can’t be given with the current configuration
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Occurs in documents (1): Package formation.
Errors in receipts
Sale information: the checkout passes the receipt to the fiscal data operator, and it passes it to Chestny ZNAK. Errors in the section: 19.
Error 1Field "batch number" isn’t filled inReceipts
Error text
Field "batch number" isn’t filled in
Value format check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 3Invalid field value format: "batch number"Receipts
Error text
Invalid field value format: "batch number"
Value format check
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 4The receipt has already been receivedReceipts
Error text
Document <document identifier> was registered earlier
Check by document identifier in the GIS MT database
- What it means
- The document was registered earlier.
- Why it happens
- The checkout or fiscal data operator sent the receipt again.
- What to do
- There’s no need to send it again.
Details:All Chestny ZNAK error codes
Error 8The value of field paymentType "…" isn’t in the list of allowed values
Receipts
Error text
08: The value of field paymentType "<value>" isn’t in the list of allowed values
Check of values from the list
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 22The checkout passed an unknown codeReceipts
Error text
Marking Codes <identification code value> not found
Check that the specified ICs exist
- What it means
- The checkout passed a code that isn’t in the system.
- Why it happens
- Often because of the scanner: the code came without GS separators, in the Russian layout or with flipped case.
- What to do
- Check the checkout scanner with a test code and compare the code part by part with the label.
Details:Scanner check: GS, layout, AIM prefixError 22 explained: marking code not found
Error 23The goods are registered to another companyReceipts
Error text
Participant <name of the participant in circulation> has no authority to perform the operation with Marking Code <identification code value>
Check that the IC belongs to the participant in circulation. For a TD, the error may occur when an IC belongs to a product group not connected for the participant
- What it means
- The seller has no authority for the operation with this code.
- Why it happens
- The supplier didn’t transfer the codes: the UTD isn’t signed or went through with an error.
- What to do
- Ask the supplier to transfer the codes under a UTD.
Details:Marking code owner
Error 24The code status doesn’t fit a saleReceipts
Error text
Status <status value> of Marking Code <identification code value> doesn’t match the operation performed
Check of available actions on the IC given its status
- What it means
- The code isn’t in the right status.
- Why it happens
- The goods aren’t introduced into circulation or have already been sold.
- What to do
- Check the code status. Only a code “In circulation” can be sold.
Details:Error 24 explained: code status doesn’t match the operation
Error 60Products with GTIN … aren’t registered in the National Catalog of marked goods
Receipts
Error text
Products with GTIN <product code> aren’t registered in the National Catalog of marked goods
Check for the product code in the National Catalog
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 69The document content or name is incorrect. Couldn’t parseReceipts
Error text
The document content or name is incorrect. Couldn’t parse
Validation of the document file content and name
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 71The document content is incorrect. Incorrect data: …Receipts
Error text: variants
The document content is incorrect. Incorrect data: <rejection reason>
Document content checkNo freight transport information
Check of the content of the fields «НомерПеревозДок» / «ДатаПеревозДок» / «РегНомер» or «НомерПеревозЭлДок»
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 79The code is distortedReceipts
Error text
Invalid marking code <identification code value>
Identification code check
- What it means
- Invalid marking code.
- Why it happens
- The code was distorted when read.
- What to do
- Check the checkout scanner with a test code.
Details:Scanner check: GS, layout, AIM prefixInvalid marking code format
Error 100Error loading from the databaseReceipts
Error text
Error loading from the database
Check for a database loading error
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 116The goods aren’t introduced into circulationReceipts
Error text
Participant <INN of the participant in circulation> can’t move Marking Code <identification code value> that isn’t introduced into circulation
MC status check
- What it means
- A code that isn’t introduced into circulation is being sold.
- Why it happens
- The manufacturer or importer didn’t introduce the goods into circulation.
- What to do
- Contact the supplier: only goods in circulation can be sold.
Details:Marking code statuses
Error 124The reference aggregate composition in the NCMG doesn’t match the one declared in the documentReceipts
Error text
The reference aggregate composition in the NCMG doesn’t match the one declared in the document
Comparison of the reference and actual aggregate composition
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 126No verification codeReceipts
Error text
The crypto tail is missing or incorrect
Check for the crypto tail
- What it means
- The crypto tail is missing or incorrect.
- Why it happens
- The checkout passed a code without a verification code or with a damaged one. Usually the scanner loses the GS separator, and the crypto tail merges with the serial number.
- What to do
- Check the scanner with a test code: do the GS separators come through.
Error 362Batch number … not found in the Batch RegisterReceipts
Error text
Batch number <batch number> not found in the Batch Register
Check for the batch number in the batch register
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 364GTIN … from the document must match the GTIN in the Batch Register
Receipts
Error text
GTIN <product code> from the document must match the GTIN in the Batch Register
Check that the product code from the document matches the product code in the batch register
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Error 384Price below the minimumReceipts
Error text
The receipt contains a price below the Minimum price for marking code <identification code value>
Check of the receipt price information by identification code against the minimum price
- What it means
- The receipt contains a price below the minimum for this code.
- Why it happens
- The sale price is below the set minimum.
- What to do
- Check the product price at the checkout.
Details:All Chestny ZNAK error codes
Error 391No MP for the receipt item for marking code …Receipts
Error text
No MP for the receipt item for marking code <identification code value>
Check for price information. It’s recommended to check that the codes are correct and that a card exists in the National Catalog. If the information is correct, contact National Catalog support: support@national-catalog.ru. After getting a resolution, try again
- What to do
- Fix what the error text points to: the field, the value or the code in it. Submit a new document: the previous one can’t be corrected.
Code application report errors
The code application report goes through the Order Management Station (OMS). It has its own error numbers, different from Chestny ZNAK documents. Errors in the section: 5.
Error 1The code is already appliedCode application report
…дубликат кода…
A fragment of the OMS response by which the Truemark account recognizes this error
- What it means
- The OMS reports a duplicate code.
- Why it happens
- A code application report for this code has already been accepted.
- What to do
- There’s no need to apply the code again. Check the code status.
Details:Code errors in code application
Error 4The code is written offCode application report
…код уже списан…
A fragment of the OMS response by which the Truemark account recognizes this error
- What it means
- The code is already written off in Chestny ZNAK.
- Why it happens
- The code was written off, for example the label was spoiled before application.
- What to do
- A written-off code can’t be restored. Order new codes for this product and reprint the labels.
Details:Code errors in code application
Error 6Not enough money on the payment accountCode application report
…лицевой счёт…
A fragment of the OMS response by which the Truemark account recognizes this error
- What it means
- The product group’s account balance doesn’t have enough money.
- Why it happens
- The product group balance in Chestny ZNAK isn’t topped up.
- What to do
- Top up the product group balance in Chestny ZNAK. When the money arrives, send the report again.
Details:Code errors in code application
Error 12No published product cardCode application report
…отсутствует карточка товара…
A fragment of the OMS response by which the Truemark account recognizes this error
- What it means
- The OMS didn’t find the product card.
- Why it happens
- The card in the National Catalog isn’t published.
- What to do
- Check the card status in the National Catalog. If the card is published, contact Chestny ZNAK support with the GTIN and the error text.
Details:Code errors in code application
Error 338The value is out of the allowed rangeCode application report
…выходит за рамки диапазона…
A fragment of the OMS response by which the Truemark account recognizes this error
- What it means
- The weight, quantity or another value is out of range.
- Why it happens
- The value in the report is higher or lower than Chestny ZNAK allows.
- What to do
- Chestny ZNAK accepts a value only within the range from its response. Correct the value in the report and send it again.
Details:Code errors in code applicationShelf life and batch number in a code application report
Questions
Frequently asked questions about Chestny ZNAK errors
Didn't find an answer? Write to us, and an expert will reply in 15 minutes on average. More answers in the knowledge base and blog.
What does the “Processed with errors” status mean?
The document failed the Chestny ZNAK check. For codes with an error, the operation wasn’t performed: the code didn’t change status, didn’t pass to the buyer, didn’t retire. For the system, everything stayed as it was before the document was sent. A code application report may have an intermediate result “Partially processed”: codes without errors are applied, and the rest need a new report.
Where do I see the error number and text?
In the Chestny ZNAK personal account, open “Documents”, click the number of the document with the status “Processed with errors”, and in the document card, “Error report”. If there are more than five errors, a “Download report” button appears: an archive with a CSV file where each code has an error number and text.
Why does one number mean different errors?
Different document types have their own error numbers. For example, error 14 in a UTD means a document with this invoice number and date already exists, while in direct submission documents it means an invalid code status. That’s why each error in the search shows its section: UTD and EDI, direct submission, receipts or code application report.
Can a document that came back with an error be corrected?
No. Fix the cause and submit a new document: the previous one can’t be corrected. For a UTD, this may be a new document, a corrected UTD or a corrective document, depending on the error.
How do I find an error by its text?
Paste the full error text into the search field, together with the marking code and INN. The search compares it with the templates from the Chestny ZNAK instructions and shows the matching error. You can also enter a few words, for example “not found” or “status”.
Where do the error texts come from?
From the Chestny ZNAK instructions “Description of document processing errors in the personal account and via API”, version 180.0 of November 19, 2026. Explanations of common errors are based on Truemark articles and the “Code errors” window in the Truemark account.
How does Truemark help avoid such errors?
Truemark checks the status and owner of every code before the code application report, introduction into circulation, aggregation and UTDs. What Chestny ZNAK would return as error 14, 23 or 24 is visible in the account in advance, with a reason for each code. If a document is still rejected, the “Code errors” window shows the reason in plain words and what to do, and codes with errors can be downloaded to Excel.
Free tools
More checks
Documents without errors in Truemark
The status and owner of every code are checked before sending, and if Chestny ZNAK still refuses, the account explains the reason in plain words. Code orders, labels, introduction into circulation, UTDs and marketplaces in one window.
Or leave a request
We’ll answer about volumes, pricing and getting started. Leave your phone or email and your question in the request form.