Chestny Znak in 1C: how to work with it, export codes, and configure cash registers in 2026

How to work with Chestny Znak in 1C in 2026: marking code export, SBIS/EDI, UTD auto-signing, POS compliance mode, and error control.

  • Marking calendar: what to check in September 2026
  • How to work with Chestny Znak in 1C: operation sequence
  • How to withdraw marking codes from 1C: sales, write-offs, and returns
  • How to connect SBIS/Saby and an EDI operator in retail for Chestny Znak

Landscape map

1C keeps the records, GIS MT confirms, the cash register retires codes from circulation

Integration works when the physical goods, the 1C document and the code status in Chestny Znak stay in sync.

Chestny Znak in 1C in 2026: How to Work and Write Off Codes
01

1C

Item master, documents, batches and accounting statuses.

02

GIS MT

The state status of the code and the right to the operation.

03

EDI and cash register

UPD/UKD, permission regime and withdrawal from circulation.

04

Monitoring

Exchange errors are visible to the responsible staff; retries run without duplicates.

  1. Chestny Znak integration with 1C is needed for daily operations: receive an UPD, match the item master with marking data, sell at checkout, process a return, or record a write-off.

  2. If 1C, EDI, GIS MT, the checkout system, and the warehouse show inconsistent statuses, the goods may be physically present while the operation is blocked or sent for manual review.

  3. As of September 12, 2026, the July EDI and retail withdrawal rules already apply to cosmetics and household chemicals.

  4. The next tasks are MOD registration for manufacturers in this group and preparing canned-goods circulation by October 1.

  5. Below are the participant calendar, the sequence of operations in 1C, and error controls.

  6. Document formats and cash-register checks are selected by product group: requirements are not enabled for the entire product range at once.

Marking calendar: what to check in September 2026

Start with the product group, the organization's role, and the operation. The same item may arrive via OSU with a GTIN and quantity, then be sold with mandatory scanning of each package code. Recording individual shipment codes and scanning them at checkout serve different purposes.

Product group and participantDate and requirementWhat to check in 1C and adjacent systems
Cosmetics, household chemicals, and personal hygiene products: suppliers and buyers in circulationEDI for volume-and-assortment accounting is effective from July 1, 2026GTIN, quantity and units in the UTD; receipt and shipment without requiring a marking-code list for volume-and-assortment accounting
Same group: retailersFrom July 1, 2026, sales data for marked goods must be transmitted through cash registersA 2D scanner, each package code in the receipt, and transmission via the OFD
Same group: manufacturersMOD registration is required from September 1, 2026; for those already registered, the deadline is October 1Add sites to the GIS MT profile: FIAS ID and, for a legal entity, its KPP; check that the status is Active and matches the organization's directories
Canned goods: manufacturers, importers, wholesalers, and retail buyersFrom October 1, 2026, circulation data must be transmitted via EDI under volume-and-assortment accountingProcess a test UTD with the GTIN and quantity; check receipt, discrepancies and the operator's response
Canned goods: storesFrom October 1, 2026, retail disposal must be processed through cash registersScan the Data Matrix on each can; check receipt transmission through the fiscal data operator

The cosmetics manufacturer's MDM is specified in the GIS MT account profile. As of the review date, including it in the withdrawal document for this group remains optional: do not treat its absence as a general write-off ban. For other goods, check the stage by TN VED/OKPD2 and your group's rules. In the September review, record separately which operations are already mandatory, which start in October, and who will verify the result in GIS MT.

How to work with Chestny Znak in 1C: operation sequence

  1. 01

    Prepare the environment

    The organization is registered in GIS MT, the QES works, the EDI operator is connected, and GTIN, HS/TN VED/OKPD2, marking flags, warehouses, and user roles are filled in 1C.

  2. 02

    Accept the UTD

    Check the group format: for volume-and-assortment accounting, match the GTIN and quantity against the receipt; for item-level accounting, check individual codes. The absence of a marking-code list in a UTD under volume-and-assortment accounting is not, by itself, an error. Document discrepancies before signing.

  3. 03

    Check warehouse movement

    A handheld terminal or WMS records receiving, aggregation, transfer, and shipment. 1C stores the accounting fact, while GIS MT confirms the official status of the code.

  4. 04

    Remove the code from circulation

    For retail sales, the code is scanned at checkout and sent through the POS terminal and fiscal data operator. For write-offs, defects, internal use, or export, a separate document with the removal reason is required.

  5. 05

    Resolve errors

    The responsible person reviews the exchange log, KM statuses, unsigned UTDs, and checkout refusals. Resubmission must be idempotent to avoid duplicates.

How to withdraw marking codes from 1C: sales, write-offs, and returns

First determine the disposal reason and the product group's accounting format. In retail sales, the cashier scans the Data Matrix, and sales data is sent through the cash register and fiscal data operator. Preliminary validation with sale blocking is used where the authorization mode is already active. For other reasons—write-off, defects, internal use or export—create a document with the reason and data in the required format: GTIN and quantity or individual codes.

WorkflowWhat 1C doesWhat IT/accounting checks
Retail saleSends the item and code to the checkout system and receives the receipt statusPOS system, OFD, applicability of permission-based mode, log, and cashier instructions
Customer returnLinks the return receipt, code, and item statusThe possibility of returning goods to circulation under the group rules, with no duplicate marking code
Write-off, defects, internal useCreates a disposal document with the reason and volume-and-assortment data or codesThe validity of the reason, mandatory details, submission to GIS MT, and processing log
Shipment to a counterpartySends UPD/UKD through EDI with the GTIN, quantity, or codesSignature, document status, and discrepancies; transmission into circulation is kept separate from retail withdrawal

From October 1, 2026, for canned goods that are defective, expired, or disposed of, withdrawal data must be submitted within three business days after the write-off report is prepared. OSU applies to most such reasons; retail, online sales, and vending require an item-level format. If the shipment arrived via OSU, individual codes for item-level withdrawal must be counted from the packages.

If there are many scenarios, design it integrating 1C with Chestny Znak as a process with logs, notifications, and an error owner.

Chestny Znak in 1C in 2026: How to Work and Write Off Codes
Discussion at a standing desk

How to connect SBIS/Saby and an EDI operator in retail for Chestny Znak

In retail, the EDI operator is needed not on its own, but as part of the overall setup:

  • UTD in the product group's format
  • signature
  • exchange with Chestny Znak
  • verification
  • code withdrawal

In practice, the sequence is this: the organization and QES certificate must be ready, the EDI operator must be linked to the legal entity, warehouses and product groups must be set up in accounting, and data exchange with GIS MT must be enabled in the marking service. In Saby/SBIS, they separately check the signature, organization, GLN for transport packages when needed, OMS ID for SUZ, token and retail validation parameters, the code removal method, and user permissions.

For 1C, this means three control points

First, incoming UPDs must reach 1C with all marking data and not be lost between the EDI operator and the accounting system. Second, outgoing documents must use the correct data format. Third, the checkout system must read the package code and link it to the correct item master; an OSU shipment may not contain individual codes.

If you need the SBIS setup specifically, see the service 1C and SBIS integrations; if the task is broader - 1C EDI and operators are better compared by process, not by name.

EDI setup for marking: operator + 1C

EDI transmits marking data within the UTD: GTIN and quantity for volume-and-assortment accounting or individual codes for item-level accounting. In 1C, configure parsing for the required format and monitoring of the GIS MT response. Choose an operator compatible with your existing systems and counterparties: we integrate Diadoc with 1C and SBIS with 1C.

If EDI has not yet been implemented or is used only for accounting, then an analysis of Diadoc and 1C integration The workflows for incoming documents, machine-readable powers of attorney and automated signing are shown. For marking, they also include the product-group format, verification of actual receipt and confirmation that the data has been processed.

How to set up auto-signing and sending of electronic documents in 1C

Auto-signing is useful only where control is clear: which documents may be signed automatically, who handles exceptions, and where it is visible that the UTD is stuck. The basic setup is this: the qualified electronic signature and permissions are configured for the organization, outbound UTDs are checked for details and codes, then a scheduled job sends the document to the EDI operator, and the log shows the statuses "created", "signed", "sent", "accepted", "rejected".

AreaWhat to automateWhat must not be handed over without control
Outgoing UTDGeneration, field validation, signing, and scheduled sendingDocuments with discrepancies in codes, price, counterparty, or warehouse
Incoming UTDImport, code matching, notify the responsible personAuto-signing without matching actual receipt
UTD corrections and amendmentsApproval workflow and resubmissionCorrections without justification or linkage to the source document
SLA for documentsAlert for unsigned and rejected documentsStuck UTDs that employees bypass with manual actions

For the business process, the important thing is not the "sign automatically" button, but the procedure: who is allowed to auto-sign, which checks are mandatory before sending, and who resolves the error before shipment is blocked.

Approval mode at the checkout: how to enable it and what to do on rejection

The authorization mode checks the code before the receipt is issued and blocks the sale when a prohibition ground is established. It applies according to the product-group calendar. For cosmetics and household chemicals, retail disposal becomes mandatory in July 2026, while the authorization mode starts on April 1, 2027. Including the code in the receipt does not, by itself, mean that all cash-register blocks are already mandatory. The PiOT technical solution is required for participants who sell through cash registers and must perform authorization checks under Resolution No. 1944.

Chestny Znak's September 10, 2026 clarification states that X-APIKEY continues to work technically after July 1, but the absence of a PIoT technical solution is recorded as a deviation. A working token does not remove the obligation to install an available compatible solution. Check the POS model, checkout software, and module version in the official calculator; if no solution is available, monitor the registry with the checkout software provider.

Checkout situationWhat the cashier doesWhat IT/the responsible person does
Code approvedSells the item in the usual wayMonitors receipt transmission and withdrawal processing
A prohibition was received in the authorization modeSets the goods aside according to instructions and does not bypass the blockChecks the specific reason, marking-code status and supply documents
No response from GIS MT/moduleOperates according to the offline-mode and timeout instructionsChecks service availability, the driver, module and log
Common refusals for the groupEscalates the issue to the responsible personMatches GTINs and releases and checks whether validations apply; under volume-and-assortment accounting, it does not require confirmation of the owner of an individual marking code, unlike item-level accounting

Check the checkout system's current POS driver, fiscal data format, product group settings, OFD connection, and response log. Analyze rejections by cause: connection errors, incorrect settings, and sales restrictions require different actions.

Integration landscape

In the working loop 1C holds the item master, batches, movement documents, code statuses and the link to source operations. The other systems cover their own areas: EDI transmits the UPD document, GIS MT stores the code state, SUZ issues codes, the cash register retires goods from circulation, scanners and WMS record actual movement.

Chestny Znak in 1C in 2026: How to Work and Write Off Codes
Integration diagram: 1C, EDI, GIS MT, SUZ, KKT, TSD and TS PIoT
Chestny Znak in 1C in 2026: How to Work and Write Off Codes
Architecture discussion at the whiteboard

Map out your integration landscape

System roles

System or layerWhat it is responsible forWhat to monitor
1C ERP / Trade Management / Retail / AccountingItem master, documents, batches, code statuses, accounting and warehouse recordsExchange errors, duplicate documents, mismatch between marking code and item master
EDIUTDs, UADs, discrepancy reports, and transmission of volume-and-assortment data or codesIncomplete marking data, unsigned incoming documents, and overdue responses
GIS MT / Chestny ZnakState status of the code: emission, entry into circulation, circulation, retirement, returnCodes are not yours, not found, already retired or awaiting confirmation
SUZOrdering and receiving marking codesTokens, OMSID, code balance, emission errors
POS / OFD / TS PIoTVerification and retirement from circulation at retail saleVerification failures, service downtime, offline mode
TSD / WMS / printersActual scanning, aggregation, label printingDataMatrix print quality, duplicate scans, lost cases and pallets
Integration layerAPI, queues, redelivery, logs, idempotencyAccumulating errors, uncontrolled resending, no trace id

Implementation stages

  1. Prepare the legal and accounting setup: registration in Chestny Znak, qualified electronic signature, EDI operator, user roles, and managers responsible for product groups.

  2. Clean up master data: item master, GTIN, HS code/OKPD2, marking attributes, units of measure, packaging, and aggregation rules.

  3. Set up integrations: 1C - EDI, 1C - Chestny Znak/SUZ, 1C - cash registers, 1C - handheld terminals/WMS, exchange logs, and error notifications.

  4. Run a test cycle: code order, printing, commissioning, receiving, shipment, retail sale, return, and write-off.

  5. Lock in operations: an update policy, error owners, an SLA for clearing stuck documents and release control for 1C/POS/data terminals.

Scenarios by role

Business roleMain scenarioWhat to automate in 1CWhere it breaks most often
ManufacturerOrdering marking codes, printing, applying, aggregation, entry into circulationEmission order, label printing, marking goods in the IS MP system, writing off defectsGTIN, print quality, defective or unused codes
ImporterObtaining codes before import and putting them into circulation after customs proceduresLinking item master, codes and receiving documentsCodes not matching the goods and document delays
Wholesale and warehouseReceiving UTDs by volume-and-assortment data or codes, preparing shipments and EDIMatch the GTIN and quantity; upload marking codes where item-level accounting is requiredIncorrect UPD format; discrepancies in quantities or codes
RetailCheckout withdrawal; permission-based mode according to the group calendarMarking code verification, exchange with cash registers/OFD, returns and correction receiptsPOS software is not ready, no TS PIoT, the code fails validation
Accounting and ITControl of documents, discrepancies and exchange errorsLogs, reports, notifications, resending without duplicatesNo incident owner, errors pile up for weeks

Common errors and how to close them

ErrorOperational symptomReasonWhat to do
UPD arrived without codesReceiving stalls, the goods cannot be sold correctlyThe supplier did not send the marking code, or the document is not matchedDo not sign until fixed, file a discrepancy report, set up inbound control
Code not found or not yours1C sees the goods, GIS MT does not confirm the right to the operationThe code belongs to another owner, has already been retired or was never put into circulationCheck the status before shipment, require a valid document from the supplier
Duplicate marking codesThe document is not sent or gets rejectedRescanning, manual entry, resending the UPDBlock manual entry without a role, enable duplicate checks and idempotent exchange
Poor DataMatrix print qualityScanner cannot read the labelPrinter, consumables, size, damage during applicationTest printing, log defects, write off unused codes
The return was not posted in the systemThe goods came back physically, but the code did not return to the right statusThe return was processed only at the warehouse or the cash registerProcess the return with a valid document, correction document (UKD) or return receipt
Exchange errors are not investigatedDocuments get stuck, staff resort to workaround operationsNo monitoring and no incident ownerSet up a log, alerts, a resolution SLA, trace id and resending
Chestny Znak in 1C in 2026: How to Work and Write Off Codes
Focused team work

Checklist before production launch

VerificationWhat must be ready
CalendarDates, accounting format, and responsible owner are recorded for each group; manufacturer MDM and October operations have been checked
Master DataGTIN, HS code/OKPD2, marking attributes, packaging, units of measure
EDIThe operator is connected, UPD/UKD go through, inbound documents are tracked against deadlines
SUZ and GIS MTOMSID, tokens, organizations and warehouses linked; exchange verified on test operations
POS and TS PIoTThe POS system and OFD transmit receipts; permission checks and the PIoT technical solution are configured for groups where they are mandatory
ScanningTSD, WMS, printers and Data Matrix quality verified on real packaging
MonitoringExchange errors, duplicates, stuck documents and marking code statuses are visible to the responsible staff
OperationsThere is an update procedure, an incident owner and a process for manually handling exceptions

If gaps remain after the checklist - assess your 1C readiness for product marking: we will review your setup and show what to resolve before going live.

What matters here to a manager, not an operator

The operator sees an error in a specific document. The manager sees something else and makes decisions based on different signals.

A marking failure does not stop accounting, it stops the sale. Authorization mode triggers at the checkout, on the sales floor, at the moment when the customer is already standing there with the item. The product is physically available, but the transaction is blocked, and this happens not at a convenient time, but at peak hours, when status mismatches between 1C, EDI, Chestny Znak, and the cash register have built up over the shift.

Manual discrepancy handling keeps people busy with work they were not hired to do. While volumes are small, one employee who "knows the workaround" can cover it. That is the main risk: the process depends on a person, not on procedure, and goes on vacation with them.

Scale breaks a manual process in predictable ways. Several legal entities, warehouses, and cash registers, and the order of operations described above as a sequence of steps no longer works the same way. From there, the question is no longer who made the mistake, but that the system chain does not check itself.

So you should not ask the team whether there were any errors. Ask three things: how many shipments a month ended up in manual review, how many people know how to resolve it, and what will happen to sales if auto-signing fails tomorrow. If the answers are unknown, the process is not observable, and therefore not manageable. What a complete setup looks like is shown above in the sections on the integration architecture and system roles.

What we do: end-to-end integration of 1C and Chestny Znak

Not customization for its own sake, but a clearly bounded setup: exchanges run through a bus, not point to point, so the next marking rule change will not stop the entire accounting system.

Exchange with GIS MT

We configure the receipt and exchange of code data: issuance, commissioning, aggregation, status, and operation confirmations without discrepancies between 1C and the state registry.

Marking codes in 1C

We map DataMatrix to the item master, batches, and movement documents - from UTD receiving to shipping, box aggregation, and pallet aggregation.

Withdrawal and commissioning

We build withdrawal scenarios: retail sale through the cash register/OFD, write-off, defects, internal use, and export - each with its own document and data submission to GIS MT.

UTD and EDI

We connect 1C with Sbis/Saby, Diadoc, or another EDI operator: signing, checking details and codes before sending, and a status log for each document.

1C environments: Retail, SMB, Accounting, ERP

We work with the current release of any configuration - retail checkout, small business on SMB, accounting, or a full ERP setup with multiple legal entities and warehouses.

Bus instead of point-to-point

We move exchanges into an integration layer with event logging, retry delivery, and idempotency - 1C remains a strong accounting system, not a single point of failure.

Case

All cases

1C + Chestny Znak

Check the marking process before production launch

We will assemble and verify the full marking lifecycle: code issuance, UPDs with codes, receiving, sales, returns, write-offs, POS approval mode, and an error log. The result is a clear setup with no duplicates, no manual workarounds, and no dependence on a single developer.

  • 1C, EDI, GIS MT, SUZ, KKT, Handheld Terminals/WMS
  • scenario testing before launch
  • instructions for cashiers and error owners
Discuss 1C and Chestny Znak integration

How to keep 1C from becoming a monolith

  1. A bad option is to hard-code all marking logic into 1C customizations without boundaries.

  2. Then any change to a rule, cash register, WMS, EDI or product group becomes a risk for the whole system.

  3. A more resilient approach is to keep 1C as the accounting hub and move data exchanges into a loosely coupled loop: API, a queue or ESB, explicit contracts, an event log, redelivery, idempotency and monitoring.

  4. This makes it easier to update separate parts, hand support to another team, and avoid keeping the business dependent on a single developer.

  5. For KT.Team this is a matter of principle: 1C must be a strong accounting system within a heterogeneous landscape, not the single platform through which every business change has to pass.

FAQ

FAQ

How do you remove marking codes from circulation in 1C?

Identify the withdrawal reason and product group format. Retail sales are transmitted through the POS system/OFD after scanning the code; permission checks apply according to the group calendar. For other reasons, prepare a document with the reason, GTIN and quantity, or individual codes, and monitor processing in GIS MT.

How do you connect SBIS/Saby in 1C:Retail for marking?

Check the organization, qualified e-signature, EDI operator, user permissions, warehouses, product groups, and integration with GIS MT. In Saby, configure the certificate, organization, GIS MT settings, token/retail verification settings, OMS ID when working with SUZ, and the code write-off method. In 1C, it is important that UTDs with codes, document statuses, and cash register operations stay aligned across systems.

Can electronic documents be automatically signed and sent in 1C?

Yes, but only after checking the details, marking codes, and signing rights. Without a policy, auto-signing speeds up errors, not the process: the UTD is sent with incorrect codes, gets stuck with the EDI operator, or comes back rejected. You need rules for which documents are signed automatically, which go for manual review, and who handles exceptions.

What to check in product marking in September 2026?

Check your group's document format against the calendar above. The next tasks are MOD registration for cosmetics and household-chemical manufacturers by October 1, and preparing EDI and cash registers for canned goods from October 1. Also check whether the authorization mode applies and whether the PiOT technical solution is compatible with your cash register.

Can Chestny Znak be connected to 1C without customization?

For standard scenarios a current 1C release, configured EDI and enabled marking functionality are often enough. Custom development appears when there is a WMS, non-standard aggregation, complex packaging, several legal entities, special warehouse rules or monitoring requirements.

Why is the code in 1C but the operation still fails?

The accounting record in 1C and the operation status in GIS MT may differ: the code may not have been introduced into circulation, may already have been disposed of, or the document may not yet be processed. Under volume-and-assortment accounting, do not check the owner of an individual code using item-level accounting rules; first match the product-group format and refusal reason.

How to tell that the integration is ready for production launch?

You need to run the full cycle on real scenarios: issuance, printing, introduction, receipt, shipment, sale, return, write-off, exchange error, and resubmission without duplicates. One successfully sent document does not prove the environment is ready.

Sources

Verification date: 12 September 2026

Discuss the article: Chestny Znak in 1C: how to work, remove...

Enter your email or phone number so we can get back to you.

Send via: