Electronic Signature for Participation in Bidding: What is Needed and How to Set Up the Workplace

Without an electronic signature, participation in electronic bidding is physically impossible: applications are signed, contracts are signed, and every action on the platform is confirmed by a certificate. Most problems for newcomers arise not with the signature itself, but around it — the wrong certificate recipient, an improperly set up workplace, or the absence of a machine-readable power of attorney for the employee. Let’s break it down in order: what signature is needed, where to obtain it, how to set up the computer, and what to do to ensure the signature does not fail at the last hour of submission.

What Electronic Signature is Needed for Bidding

To participate in procurement, a qualified electronic signature (QES) is required. Simple and unqualified signatures are not suitable for bidding: platforms do not accept them, and applications signed with them do not have the legal force equivalent to a handwritten signature.

It is important to understand that the QES certificate is issued to a specific individual, not to the company “in general”:

• The head of a legal entity and an individual entrepreneur obtain the QES at the certifying center of the Federal Tax Service of Russia (or its authorized representatives) — free of charge, on a secure carrier.
• An employee who works with procurement on behalf of the company uses the QES of an individual issued by an accredited certifying center, along with a machine-readable power of attorney (MPA) from the organization.

The MPA is a separate electronic document signed by the head with their QES. It lists the employee’s powers. Without the power of attorney, the employee’s signature on the platform will not be linked to the company, and the application will not be accepted.

What to Obtain in Advance, Before the First Procurement

1. A carrier for the certificate — a secure USB token (RUTOKEN, JaCarta, and analogs). A signature on a regular flash drive or in a file is not suitable for bidding.
2. A license for cryptographic protection software — usually, CryptoPro CSP. It is needed both at the workplace and for signing on the platform.
3. The certificate itself — from the Federal Tax Service for the head, from an accredited certifying center for the employee.
4. MPA, if someone other than the head will be working.

Allocate a week for this. Issuing the certificate requires a personal visit and document verification, and the queue at the end of the quarter is traditionally longer.

Setting Up the Workplace

A typical setup for working with electronic trading platforms includes:

• the latest version of the Windows operating system;
• cryptographic protection software (CryptoPro CSP) with a valid license;
• a browser plugin that allows signing documents on the web page;
• token drivers;
• root certificates of the certifying center installed in trusted;
• a browser supported by the platform; some platforms require a browser that supports GOST encryption.

After installation, check the signature on the platform’s test page — almost every electronic trading platform has a workplace diagnostics section. This five-minute check can save hours on the submission day.

Common Mistakes That Cause the Signature to “Not Work”

• The certificate has expired. The QES is issued for a limited period — usually for just over a year. Set a reminder a month in advance: reissuing on the submission day is impossible.
• The head has changed. The certificate is tied to a specific person and their position. A change of director means a new certificate and new powers of attorney.
• No MPA or it is not issued for the correct powers. The power of attorney must cover participation in procurement and signing the application.
• Root certificates are not installed. The signature is generated, but the platform considers it untrusted.
• A browser update broke the plugin. Check the workplace after every major system update.
• One token for everyone. Transferring the carrier between employees violates the rules of signature use and sooner or later leads to disputes over who actually signed the document.

Signature and Automatic Submission

A separate question is what happens when applications are submitted not by a person, but by a system. In Atlas Procurement, the final signing and submission of the application is a product function: the certificate is installed on a secure workplace of the robot, it signs the package and sends it to the platform on time, without night shifts for the operator. The person sets the parameters: the maximum price, the list of directions and customers, and cases when confirmation is needed. Detailed mechanics are covered in the article about the application submission robot.

Checklist Before the First Submission

• The QES certificate is valid and has more than a month left until its expiration;
• The carrier is on-site, and the PIN code is known to the responsible person;
• The CryptoPro license is active;
• The browser plugin is installed, and the platform diagnostics have been passed;
• The MPA is issued and uploaded if an employee is submitting;
• A test signing has been completed not on the submission day;
• A second employee with their own signature is appointed — in case the first is on vacation or sick.

An electronic signature is an infrastructure, not a one-time purchase. Once the order is established (timelines, carriers, powers of attorney, verified workplace), it eliminates almost all emergency situations on the submission day.

The next step after obtaining the signature is registration in the ERUZ and accreditation on electronic platforms. To ensure suitable procurements are found automatically, connect monitoring: Atlas Procurement collects procedures from the EIS and commercial platforms into one stream →

The norms and requirements are provided according to the current version of the legislation on the contract system and electronic signatures. Before submission, verify with the current text of the law and the requirements of the specific platform.