Ukrainian QES

Sign HR documents with a Ukrainian QES

eSignature / HR routes in the Kadry module

Applications, orders and P-2 cards go for signing right from the HR process. Employees sign via Diia or their own QES through ID.GOV.UA, and the company signs with its legal entity key. The signed document returns to the personnel file with a signing protocol.

Signer

Two signing methods to choose from

The method is chosen by the signer on the signing page, not by an administrator in settings. So the signer picks whatever works for them, Diia or another qualified key.

Mode 1

Diia.Signature

Works for most people: the signer already has Diia, and there is nothing to install.

  • On a computer, the signing page shows a QR code for the Diia app; on a phone, a link that opens Diia.

  • The code is valid for three minutes, with a countdown on the panel.

  • In the list of methods, this option carries a “Recommended” badge.

Mode 2

Electronic signature via ID.GOV.UA

For signers who use another qualified signature instead of Diia.

  • The ID.GOV.UA widget opens: the state electronic identification system.

  • The signer chooses the key storage and enters its details.

  • Any qualified key from a Ukrainian provider that the person already has will work.

How it works

Where signing fits in the HR process

Signing is a stage of the route that starts with an employee request and ends with a document in their personnel file.

The document is built from employee card data, goes to signers one by one, and returns signed to the employee folder and the general “Documents” section.

A document from card data

An application, order or P-2 card is generated from your template: the system fills in full name, position, legal entity, period and order number from the employee card. Fields stay editable until sending, so an HR administrator can change the order number or the legal entity name, and the document is generated with the new values.

Requests to signers in sequence

Each signer receives a link once the previous one has signed. Every request has its own link, and the protocol records exactly who signed. Everyone receives the signed copy by email once all signers listed in the document have signed. In the document list, the “E-signature” column shows the document status, and the “Signer” column shows each signer's status.

Back to the personnel file

After signing, the document row in the employee card, and in the general “Documents” section, opens and downloads the signed version. Documents sent as part of preboarding are signed right inside the form.

Result

What you get after signing

Once everyone has signed, “Download” offers two files. They answer two different needs: paper and verification.

Print version

The document with the signing protocol attached. The protocol prints as a page at the end, its stamp sits on the last page of the document, and for each signer it lists full name, individual tax number or EDRPOU code for a legal entity, signing time, certificate status and serial number. This is the file for your folder if you keep orders on paper.

Signed document in .p7s

A container that holds both the document and all qualified signatures on it. You upload it to an external verifier as is, with no separate document and no PeopleForce access needed. Both files can be downloaded from the document at any time.

When several documents are issued for one employee, each follows its own signer sequence, so documents move independently of each other.

What you need to connect

Who issues keys, how the company signs, and what the administrator does.

Keys come from a trust service provider

The signer gets a certificate where they usually do: in Diia, at a bank or from another qualified provider. PeopleForce displays the document, accepts the signature and stores the result.

Signing for a legal entity goes through ID.GOV.UA

A director or authorized person signs with the company's qualified key via ID.GOV.UA. The company key is issued by a qualified provider and stays with the company. In the protocol, this signature carries the EDRPOU code instead of an individual tax number.

eSignature credits stay untouched

Ukrainian QES signing runs separately from eSignature credits: sign as many documents as you need.

Connecting takes one toggle

An administrator turns signing on in the integrations section, with no contractor or technical integration on your side. Any employee document can be signed, and routes with applications, orders and P-2 cards live in the Kadry module.

Frequently asked questions

What HR teams ask most often in demos and support: employee QES keys, paper copies and inspections.

Step-by-step guide in the help center

What if not everyone has Diia or a QES?

What legal force does this signature have?

Do I still need to print documents?

How do I verify a signature outside the system?

How do I share signed documents with inspectors?

See HR document signing live

In the demo, we'll show the full path: from application and order to the signed document in the personnel file and the files for verification.