Many companies exporting to Russia hit their first obstacle at the very beginning of trying to register products in the Chestny Znak (Честный ЗНАК) mandatory labelling system: the platform requires a Russian qualified electronic signature before you can do anything at all. Without it you cannot register, request DataMatrix marking codes, or sign documents. This article explains that first, critical condition — the UKEP signature — from the exporter’s point of view, because most guides skip it.
What is UKEP?
UKEP (Russian: УКЭП) is Russia’s qualified electronic signature, the highest security level available. It works on the same logic as a qualified e-signature elsewhere: applied digitally, it is legally equivalent to a handwritten signature. In Russia it is the legal identity used on official state portals, in tax procedures and in electronic document flow (EDI).
UKEP consists of two elements:
- The signature certificate — the digital certificate verifying the identity of the holder, a person or a company.
- A physical crypto token — dedicated USB-style hardware in which the certificate is stored securely (Rutoken, JaCarta) together with the cryptographic software that runs it (CryptoPro CSP).
Why is an electronic signature mandatory for Chestny Znak?
Chestny Znak is a Russian state traceability system, and every action in it is legally binding. Everything you enter — the registration application, the participant agreement, a code request, a transfer of ownership — counts as an official act. The system therefore permits no step at all until the party performing it has been verified through UKEP. The electronic signature is, in short, the key to the system’s door.
Is a foreign e-signature the same as UKEP?
No — and this is one of the most common mistakes. A qualified electronic signature obtained in your own country is valid under your own legal system; it does not work in Russia’s Chestny Znak. UKEP is issued only by accredited certification centres (удостоверяющий центр) inside Russia, under Russian legislation. For company directors the signature is issued through the certification centre of the Russian Federal Tax Service (ФНС).
That brings an important precondition with it: obtaining a UKEP usually requires a Russian tax number (INN) and a legal or representative structure recognised in Russia.
How is UKEP obtained? The basic steps
- Prepare identity and company documents: the holder’s identity and the company’s Russian registration details (INN and similar) are required.
- Apply to an authorised certification centre: an accredited centre in Russia, or the Federal Tax Service for a company director.
- Obtain the physical token: the crypto token (Rutoken or JaCarta) onto which the certificate will be loaded.
- Install the cryptographic software: software such as CryptoPro is installed and configured so the signature works.
- Load the certificate onto the token and activate: the signature is tested and becomes usable for logging into the Chestny Znak personal cabinet.
UKEP is often assumed to be permanent; in fact it has a defined validity period and must be renewed when it expires. If the renewal is forgotten, your labelling operations stop without warning.
How does a foreign exporter obtain UKEP?
For companies without a legal entity in Russia — an importing company of their own, for instance — the most common and practical route is to run the process through an authorised representative or importer in Russia. In that structure:
- the authorised party in Russia obtains and uses the UKEP,
- Chestny Znak registration, code requests and document signing all go through that signature,
- you, as the manufacturer, supply the product and GTIN information and coordinate the process end to end with a partner.
With our Moscow office and our partner network in Russia we set up, run and follow this signature and registration process on behalf of companies abroad — so you become compliant without building a physical presence in Russia.
Where exactly is UKEP used?
- Registration and login: access to the Chestny Znak personal cabinet and signing the participant agreement.
- Marking code requests: ordering and issuing DataMatrix codes.
- Electronic document flow (EDI): signing the universal transfer documents that report changes of ownership.
- Reporting: confirming entry, exit and circulation reports.
Common mistakes
- Assuming a home-country e-signature will be valid in Russia.
- Not tracking the UKEP validity period, so operations stop when it expires.
- Installing the crypto token and cryptographic software incompletely and being unable to log in.
- Assigning signing authority to the wrong person and being unable to sign documents later.
Where UKEP belongs in your export timetable
Obtaining the signature — from the application to the certification centre through token delivery and software installation — can take several working days, and missing documents or wrong guidance can stretch that into weeks. So UKEP should be addressed much earlier than the date of your first shipment. In practice we recommend this order:
- First establish whether your products are in Chestny Znak scope and which category they fall into.
- Decide your representation or import structure in Russia — your own legal entity or an authorised representative.
- Complete the UKEP application and the token and software installation at this stage, before requesting codes.
- Once the signature is ready, register in the system, sign the participant agreement and request the marking codes.
Companies that skip this order and go straight for the codes usually get stuck at the signature stage and have to postpone production and shipping plans.
Frequently asked questions
Can you use Chestny Znak at all without UKEP?
No. Registration, login and every binding action require identity verification with a qualified electronic signature. Without one you can only look at general information; you cannot act.
Can one signature be used by several people?
UKEP is assigned to a specific holder and carries that person’s or company’s authority. Assigning signing authority to the right person matters, so that document signing does not become a problem later.
What happens when the signature expires?
No action is possible with an expired signature; code requests and document flow stop. The renewal date therefore has to be tracked in advance.
A correct start means a smooth process
Because the electronic signature is the first step of the Chestny Znak journey, a mistake here delays your whole labelling and export timetable. Setting up UKEP — the most technical and most Russia-specific part of the process — goes far faster and with far less risk with expert support.
To set up your Russian electronic signature and Chestny Znak registration correctly from the start, get in touch. Our end-to-end labelling offering is on the Solutions page, and our other guides on Russian labelling are under News.
