A qualified electronic signature is not a separate technology from an advanced electronic signature: under eIDAS, a is an plus a and a .
This page helps separate the legal effect, certificate and QTSP checks, QSCD evidence, and validation records that make the difference defensible for relying parties and audit reviewers.
Under eIDAS, every must first satisfy the requirements: it must be uniquely linked to the signatory, identify the signatory, use signature creation data under the signatory's sole control with a high level of confidence, and make later changes to the signed data detectable. QES adds two qualification layers: the signature must be based on a issued by a qualified trust service provider, and it must be created by a .
Side-by-side comparison
QES vs AdES under eIDAS: practical differences
This comparison helps decide whether the record needs only evidence or the additional qualified certificate, QTSP, QSCD, and validation evidence needed for .
An advanced electronic signature created by a and based on a .
Second framework
Advanced electronic signature (AdES)
An electronic signature that meets Article 26's requirements for signer linkage, signer identification, signer-control of creation data, and detectable changes to signed data.
Article 2 preserves separate Union and national transaction formalities, while Article 25 gives QES handwritten-signature equivalence.
equivalent legal effect of a handwritten signature
Cannot be denied legal effect or admissibility only because it is electronic or not qualified, but it does not receive automatic handwritten-signature equivalence under Article 25.
Article 25 preserves admissibility for electronic signatures even when they are not qualified.
not be denied legal effect and admissibility as evidence
Use where handwritten-signature equivalence is required, but check any separate transaction formality. Use where the legal need is strong electronic evidence assessed in context.
Explains trusted-list indicators for qualified certificate and qualified service status.
Service current status
May use certificates and trust services, but status alone is not proof that the certificate is qualified or that the provider has qualified status for that service.
Article 26 defines AdES without requiring qualified certificate status.
Requirements for advanced electronic signatures
For , validate QTSP and qualified-certificate status from trusted-list evidence; for , keep certificate and identity evidence without overstating qualified status.
The validation process must confirm certificate qualification, QTSP issuance, certificate validity at signing, matching validation data, signatory data, pseudonym indication if used, QSCD creation, signed-data integrity, and Article 26 compliance.
Article 32 lists the validation conditions for qualified electronic signatures.
Requirements for the validation of qualified electronic signatures
The evidence should prove Article 26 requirements and, if the signature is based on a qualified certificate, the separate Article 32a validation conditions for that middle category.
Article 26 defines AdES; Article 32a covers AdES based on qualified certificates.
advanced electronic signatures based on qualified certificates
A validation report should be retained with trusted-list, certificate, revocation, QSCD, and signed-data-integrity evidence; records should not omit signer identity, signer control, and tamper-detection evidence.
Articles 3, 26, 28, 29, and 32 collectively define the QES evidence stack.
qualified electronic signature means an advanced electronic signature
Classify as when the evidence proves Article 26 requirements but the record does not prove every qualified certificate, QTSP, QSCD, and validation condition.
Label the signature at the level its evidence proves. A claim requires the qualified certificate, provider status, device, and validation evidence in addition to the requirements.
Article 32 requires the qualified certificate to have been valid at the time of signing.
was valid at the time of signing
review focuses on whether the Article 26 conditions were met for the signature. If the AdES is based on a qualified certificate, Article 32a adds certificate-at-signing and related validation checks even though the signature is not .
Receives the equivalent legal effect of a handwritten signature under Article 25, without displacing separate transaction formalities in applicable law.
Article 2 preserves separate Union and national transaction formalities, while Article 25 gives QES handwritten-signature equivalence.
equivalent legal effect of a handwritten signature
Cannot be denied legal effect or admissibility solely because it is electronic or non-qualified; it does not receive handwritten-signature equivalence under Article 25.
Article 25 preserves admissibility for all electronic signatures.
not be denied legal effect and admissibility as evidence
Treat as the higher legal-effect label, then check any separate formality. Treat as the evidence-based option unless a rule specifically asks for qualified status.
Choose when the request or rule calls for handwritten-signature equivalence or when the file must prove qualified status end to end, subject to any separate form requirement.
Select the minimum level that meets the legal requirement, then classify the resulting signature from its actual certificate, device, and validation evidence.
Article 2 preserves separate Union and national transaction formalities, while Article 25 gives QES handwritten-signature equivalence.
equivalent legal effect of a handwritten signature
Advanced electronic signature (AdES)
Cannot be denied legal effect or admissibility only because it is electronic or not qualified, but it does not receive automatic handwritten-signature equivalence under Article 25.
Article 25 preserves admissibility for electronic signatures even when they are not qualified.
not be denied legal effect and admissibility as evidence
Operational implication
Use where handwritten-signature equivalence is required, but check any separate transaction formality. Use where the legal need is strong electronic evidence assessed in context.
Explains trusted-list indicators for qualified certificate and qualified service status.
Service current status
Advanced electronic signature (AdES)
May use certificates and trust services, but status alone is not proof that the certificate is qualified or that the provider has qualified status for that service.
Article 26 defines AdES without requiring qualified certificate status.
Requirements for advanced electronic signatures
Operational implication
For , validate QTSP and qualified-certificate status from trusted-list evidence; for , keep certificate and identity evidence without overstating qualified status.
The QES definition in Article 3 adds QSCD status to the AdES baseline.
created by a qualified electronic signature creation device
Core obligations
Qualified electronic signature (QES)
The validation process must confirm certificate qualification, QTSP issuance, certificate validity at signing, matching validation data, signatory data, pseudonym indication if used, QSCD creation, signed-data integrity, and Article 26 compliance.
Article 32 lists the validation conditions for qualified electronic signatures.
Requirements for the validation of qualified electronic signatures
Advanced electronic signature (AdES)
The evidence should prove Article 26 requirements and, if the signature is based on a qualified certificate, the separate Article 32a validation conditions for that middle category.
Article 26 defines AdES; Article 32a covers AdES based on qualified certificates.
advanced electronic signatures based on qualified certificates
Operational implication
A validation report should be retained with trusted-list, certificate, revocation, QSCD, and signed-data-integrity evidence; records should not omit signer identity, signer control, and tamper-detection evidence.
Articles 3, 26, 28, 29, and 32 collectively define the QES evidence stack.
qualified electronic signature means an advanced electronic signature
Advanced electronic signature (AdES)
Classify as when the evidence proves Article 26 requirements but the record does not prove every qualified certificate, QTSP, QSCD, and validation condition.
Label the signature at the level its evidence proves. A claim requires the qualified certificate, provider status, device, and validation evidence in addition to the requirements.
Article 32 requires the qualified certificate to have been valid at the time of signing.
was valid at the time of signing
Advanced electronic signature (AdES)
review focuses on whether the Article 26 conditions were met for the signature. If the AdES is based on a qualified certificate, Article 32a adds certificate-at-signing and related validation checks even though the signature is not .
Article 32 and Article 32a show that the validation point is the signing moment.
at the time of signing
Legal effect and admissibility
Qualified electronic signature (QES)
Receives the equivalent legal effect of a handwritten signature under Article 25, without displacing separate transaction formalities in applicable law.
Article 2 preserves separate Union and national transaction formalities, while Article 25 gives QES handwritten-signature equivalence.
equivalent legal effect of a handwritten signature
Advanced electronic signature (AdES)
Cannot be denied legal effect or admissibility solely because it is electronic or non-qualified; it does not receive handwritten-signature equivalence under Article 25.
Article 25 preserves admissibility for all electronic signatures.
not be denied legal effect and admissibility as evidence
Operational implication
Treat as the higher legal-effect label, then check any separate formality. Treat as the evidence-based option unless a rule specifically asks for qualified status.
The QES definition is built on the AdES baseline, so evidence can be reused downward but not upgraded upward without proof.
A qualified electronic signature shall have the equivalent legal effect of a handwritten signature
Practical decision rule
Qualified electronic signature (QES)
Choose when the request or rule calls for handwritten-signature equivalence or when the file must prove qualified status end to end, subject to any separate form requirement.
Select the minimum level that meets the legal requirement, then classify the resulting signature from its actual certificate, device, and validation evidence.
Article 25 and Article 26 together support the lowest-accurate-label rule.
not be denied legal effect and admissibility as evidence
Practical decision rule
How should teams decide between QES and AdES labels?
Start with the legal or contract requirement: does it require handwritten-signature equivalence, qualified status, or only reliable electronic evidence?
If is required, collect the validation report plus evidence of qualified certificate status, QTSP issuance, certificate validity at signing, revocation status, QSCD support, and signed-data integrity.
If is sufficient, retain signer identity, authentication, signer-control, intent, audit-log, and tamper-detection evidence, and avoid qualified-status claims unless they are independently proven.
Escalate any vendor statement that says without showing the qualified certificate, trusted-list status, QSCD evidence, and Article 32 validation result.
Primary source for the QES and AdES decision criteria.
Requirements for advanced electronic signatures
Search this module
Find a question or answer quickly
3 of 3 questions
Question 1
What is the practical difference between a QES and an AdES under eIDAS?
An is the eIDAS signature level defined by the four Article 26 requirements: signer linkage, signer identification, signer-control of creation data, and data-integrity linkage. It can be strong evidence, but eIDAS does not give it automatic equivalence to a handwritten signature.
A is an that also uses a and a . eIDAS Article 25 gives a QES the equivalent legal effect of a handwritten signature, while any electronic signature remains admissible and cannot be rejected only because it is electronic or not qualified.
That handwritten-signature equivalence does not remove separate requirements that Union or national law may impose on a transaction, such as witnessing, notarisation, registration, or a prescribed form. Check the law governing the document before treating as the only formality.
Use language when the evidence question is whether the signer can be identified, the signature is linked to the signed data, and later changes are detectable.
Use language only when the record proves the qualified certificate, the qualified trust service provider, the qualified creation device, and the Article 26 requirements.
Do not call a signature merely because it uses a digital certificate, a strong login, an audit trail, or a vendor label.
Is a qualified electronic signature () just a stronger advanced electronic signature () under EU eIDAS?
Yes, in eIDAS structure: a is an that also has a and is created by a . The added qualified certificate and device requirements are what give QES its special eIDAS legal effect.
Article 2 preserves separate Union and national rules on contract and document formalities; Articles 3, 25, and 26 define AdES and QES, their legal effects, and the four AdES requirements.
A qualified electronic signature shall have the equivalent legal effect of a handwritten signature.
Question 2
What must be checked before relying on QES status?
For , the signature validation record should prove more than successful cryptographic verification. It should show that the supporting certificate was a qualified certificate at the time of signing, that it was issued by a qualified trust service provider and valid at that time, that the validation data matched what was provided to the relying party, and that the signed data's integrity was not compromised.
Trusted lists matter because eIDAS requires Member States to establish, maintain, and publish trusted lists with information about qualified trust service providers and their qualified trust services. The trusted-list interpretation rules also explain how qualified certificate and QSCD-related status can be represented through service entries, certificate statements, and qualifications.
Commission Implementing Regulation (EU) 2025/1945 has applied since 20 October 2025. It sets reference standards for validating and the middle category of based on a qualified certificate. A process that complies with those standards benefits from the regulation's presumption of compliance for the referenced validation requirements, but the result still has to distinguish QES from AdES without QSCD proof.
Keep the signed object or detached signed data with the exact signature package that was validated.
Keep the validation report showing the result, validation time or best-signature-time, certificate chain, revocation status, and security-relevant warnings.
Keep evidence that the certificate was qualified for electronic signature, issued by a QTSP, and valid at the time of signing.
Keep evidence that the signature was created by a QSCD or remote QSCD service where status is claimed.
Keep the trusted-list or LOTL evidence used to establish the QTSP, qualified service, certificate, and QSCD status.
Identifies Commission eSignature resources, including the eIDAS Dashboard, Trusted List Browser, and validation tooling for signature verification work.
creation and verification of electronic signatures
Sets the current reference standards for QES validation and for validation of AdES based on qualified certificates; it entered into force on 20 October 2025.
Question 3
When is AdES enough, and when should a team require QES?
may be enough where the applicable contract, service design, risk analysis, or law only requires strong evidence of signer identity, signer control, and document integrity. eIDAS preserves the admissibility of non-qualified electronic signatures; the weight given to that evidence depends on the applicable law and transaction record.
Require when the applicable law, public-service requirement, customer mandate, procurement clause, or organisation risk decision specifically requires qualified status or handwritten-signature equivalence. Then check separately for any witnessing, notarisation, registration, or other form requirement. A normal audit trail is incomplete for a QES claim unless it also proves the qualified certificate, QTSP, QSCD, and validation conditions.
For , document the identity proofing and authentication method, signer intent, signer-control evidence, signed-data hash or signature linkage, and tamper-detection result.
For , add qualified certificate details, QTSP/trusted-list status, QSCD or remote QSCD evidence, certificate validity or revocation status at signing, and the qualified validation result.
For advanced signatures based on qualified certificates, do not assume : eIDAS Article 32a has validation requirements for that middle case, but it lacks the QSCD requirement that distinguishes QES.
Article 25 preserves admissibility for electronic signatures generally, Article 32 validates QES, and Article 32a covers AdES based on qualified certificates.
not be denied legal effect and admissibility as evidence
Recommended next step
Build a QES or AdES evidence record that reviewers can rerun
Sorena can help convert the eIDAS distinction into a cited signature policy, validation checklist, supplier evidence request, and record-retention format for your signing workflow.
Primary legal source for QES and AdES definitions, legal effect, qualified certificates, QSCDs, trusted lists, and validation requirements.
Article 2 preserves separate Union and national rules on contract and document formalities; Articles 3, 25, and 26 define AdES and QES, their legal effects, and the four AdES requirements.
Articles 22, 28, 29, and 32 support the trusted-list, qualified-certificate, QSCD, and qualified-validation checks needed for QES reliance.
Show 20 more
Article 25 preserves admissibility for electronic signatures even when they are not qualified.
Article 25 is the legal-effect rule for the QES versus AdES distinction.
Article 3 defines qualified certificates and qualified trust service providers; Article 22 requires trusted lists.
Article 26 defines AdES without requiring qualified certificate status.
Article 26 requires signer-control of electronic signature creation data for AdES.
The QES definition in Article 3 adds QSCD status to the AdES baseline.
Article 32 lists the validation conditions for qualified electronic signatures.
Article 33 supports retaining an automated qualified-validation result for QES where a qualified validation service is used.
Articles 3, 26, 28, 29, and 32 collectively define the QES evidence stack.
Article 26 is the standalone AdES test.
Article 32 requires the qualified certificate to have been valid at the time of signing.
Article 2 preserves separate Union and national transaction formalities, while Article 25 gives QES handwritten-signature equivalence.
Article 25 preserves admissibility for all electronic signatures.
Article 25 separates admissibility from the special legal effect of QES.
QES includes the Article 26 AdES conditions plus the qualified layers.
AdES is defined separately in Article 26 and does not require QSCD status.
The QES definition is built on the AdES baseline, so evidence can be reused downward but not upgraded upward without proof.
Article 26 is the standalone AdES standard.
Article 25 and Article 26 together support the lowest-accurate-label rule.
Primary source for the QES and AdES decision criteria.
"qualified electronic signature means an advanced electronic signature"
More quoted passages
"A qualified electronic signature shall have the equivalent legal effect of a handwritten signature."
"Each Member State shall establish, maintain and publish trusted lists"
"not be denied legal effect and admissibility as evidence"
"Legal effects of electronic signatures"
"issued by a qualified trust service provider"
"Requirements for advanced electronic signatures"
"under his sole control"
"created by a qualified electronic signature creation device"
"Requirements for the validation of qualified electronic signatures"
"receive the result of the validation process"
"linked to the data signed therewith"
"was valid at the time of signing"
"equivalent legal effect of a handwritten signature"
"A qualified electronic signature shall have the equivalent legal effect of a handwritten signature"
Current reference standards for validating QES and advanced signatures based on qualified certificates.
Sets the current reference standards for QES validation and for validation of AdES based on qualified certificates; it entered into force on 20 October 2025.
Source for Commission eSignature resources and tooling, including the eIDAS Dashboard, Trusted List Browser, and validation support.
Identifies Commission eSignature resources, including the eIDAS Dashboard, Trusted List Browser, and validation tooling for signature verification work.
"creation and verification of electronic signatures"