A qualified electronic signature (QES) is an advanced electronic signature that is created by a qualified signature creation device and based on a qualified certificate issued by a qualified trust service provider. Under the EU eIDAS Regulation, it is the only electronic signature that has the equivalent legal effect of a handwritten signature in every member state.
In digital identity and privacy practice, the QES matters because it binds a document to a verified natural person with the strongest assurance the European framework offers. It combines identity proofing, protected key storage and public key cryptography, so the signer cannot plausibly deny the act and any later change to the document becomes detectable.
How a qualified electronic signature works
A QES works by applying the signer’s private key, held inside a certified device, to a cryptographic hash of the document. The verifier uses the matching public key from the qualified certificate to confirm that the hash still matches and that the key belongs to the named person.
The process rests on three pillars. First, a qualified trust service provider (QTSP) verifies the signer’s identity, usually in person, by video identification or with a notified electronic identity means. Second, the private key lives in a QSCD, such as a smart card, a USB token or a remote hardware security module, that is certified against common criteria protection profiles. Third, the signature is packaged in a standard format so that any validator can check it years later.
The following table lists the components that must be present before a signature can count as qualified.
| Component | Role | Typical form |
|---|---|---|
| Qualified certificate | Links the public key to a verified person | X.509 certificate with qualified statements |
| Signature creation device | Protects the private key under sole control | Smart card, token or remote HSM |
| Trust service provider | Performs identity checks and issues certificates | Supervised QTSP on an EU trusted list |
| Signature format | Packages hash, certificate and attributes | PAdES, XAdES, CAdES or ASiC |
| Validation service | Confirms validity at signing time | Qualified validation service or local validator |
Electronic signature levels under eIDAS
The eIDAS Regulation defines three signature levels that differ in assurance and legal presumption. Courts may not reject a simple electronic signature only because it is electronic, yet only the qualified level carries an automatic presumption of validity across borders.
The table below compares the levels, which practitioners often confuse in contracts and procurement documents.
| Level | Key requirements | Legal effect | Typical example |
|---|---|---|---|
| Simple electronic signature | Any data attached to or associated with a document | Admissible, evidential weight assessed case by case | Typed name or scanned image |
| Advanced electronic signature | Uniquely linked to the signer, detects changes, sole control | Stronger evidence, no automatic equivalence | Software certificate signature |
| Qualified electronic signature | Advanced plus qualified certificate and QSCD | Equal to handwritten signature EU-wide | Signature with a national eID card |
An advanced signature becomes qualified only when both extra conditions are satisfied. A qualified certificate stored in ordinary software, for example, yields an advanced signature and not a QES, because the key is not protected by a certified device.
Remote signing and the eIDAS 2.0 framework
Remote qualified signing lets a QTSP hold the private key in a certified hardware security module while the signer authorizes each operation with strong authentication. This model removed the need for card readers and made the QES practical on phones and in web workflows.
The amended regulation known as eIDAS 2.0 extends this direction. Every EUDI Wallet must allow its holder to create qualified electronic signatures, and for natural persons this capability is to be free of charge for non-professional use. Signing therefore moves closer to everyday identity tools such as wallets that also handle a verifiable credential or a mobile driver’s license.
The deployment models differ in convenience, cost and the way sole control is demonstrated.
| Model | Where the key lives | Strengths | Weaknesses |
|---|---|---|---|
| Local smart card | Chip on the card | Clear sole control, offline signing | Needs reader and drivers |
| USB token | Secure element in token | Portable, works across computers | Easy to lose, setup friction |
| Remote HSM | QTSP data center | Works on any device, scales well | Depends on provider availability |
| Wallet-based signing | Wallet secure element or remote QSCD | Integrated with identity data | Ecosystem still maturing |
Privacy implications of qualified signatures
A QES discloses more personal data than many users expect, because the embedded certificate typically carries the full legal name, often a national identifier or serial number, and the issuer. Anyone who receives the signed file can read these attributes, so data minimization has to be considered before choosing a QES for routine forms.
Remote signing creates a second exposure. The QTSP processes signing logs and document hashes, which reveal when and how often a person signs. Well-designed services transmit only hashes rather than full documents, and the provider is bound by the GDPR as well as by its supervisory audits.
- Use pseudonym certificates where national law permits them and identification is not legally required.
- Send document hashes rather than content to remote signing services.
- Limit retention of signed copies containing certificate data to the legally required period.
- Prefer selective disclosure credentials when proving an attribute is enough and no signature is needed.
When to require a QES and common mistakes
A QES is justified when the law demands the written form or when the cost of a disputed signature is high. For low-risk agreements, a simple or advanced signature usually offers adequate evidence with less friction and less personal data processing.
The decision table summarizes typical situations and the reasoning behind each choice.
| Situation | Recommended level | Reason |
|---|---|---|
| Statutory written form required | Qualified | Only level equivalent to handwriting |
| Cross-border public procurement bid | Qualified or advanced | Tender rules often demand high assurance |
| Internal approval workflow | Advanced | Sufficient traceability at lower cost |
| Newsletter consent or terms acceptance | Simple | Low risk, minimal personal data |
Several errors recur in practice. Teams assume that any certificate-based signature is qualified, overlook long-term validation, or forget that a signature validated today may fail later once the certificate expires or algorithms weaken.
- Not embedding timestamps and revocation data, which makes later validation impossible.
- Relying on a provider that has lost qualified status on the trusted list.
- Treating a scanned handwritten signature as an electronic signature of higher level.
- Ignoring national exceptions, since some acts, such as certain real estate transfers, still require notarial form.
In everyday language
A qualified electronic signature is the digital version of signing a paper with a pen in front of an official who checked your passport. Before you can use one, a trusted company confirms who you are. After that, you receive a secret key locked in a secure chip or held by that company on your behalf.
When you sign, the key leaves a mathematical seal on the file. Anyone can check that seal and see that you signed it and nobody changed it afterward. Across the European Union, this kind of signature counts exactly like a handwritten one, which is why it is used for important contracts and official forms.
Seen in the real world
A small engineering firm in Austria wants to submit a bid in a public tender run by a municipality in Belgium. The tender rules state that the offer must carry a qualified electronic signature of the managing director. Printing, signing and couriering the documents would take two days the firm does not have.
The director already holds a remote QES issued by a qualified trust service provider after a one-time video identification. She uploads the 40-page PDF to the signing portal, confirms the operation with a one-time code on her phone, and receives a PAdES signed file with an embedded timestamp within a minute. The Belgian procurement platform validates the signature against the EU trusted list and accepts the bid, and the legal effect is the same as an ink signature delivered by hand.