--- title: "QES vs AdES under EU eIDAS: legal effect, certificates, QTSPs, and validation evidence" canonical_url: "https://www.sorena.io/artifacts/eu/electronic-identification-and-trust-services-regulation/faq/qes-vs-ades" source_url: "https://www.sorena.io/artifacts/eu/electronic-identification-and-trust-services-regulation/faq/qes-vs-ades" author: "Sorena AI" description: "Compare qualified electronic signatures (QES) and advanced electronic signatures (AdES) under EU eIDAS, including legal effect, qualified certificates, QTSP status, QSCDs, and validation evidence." published_at: "2026-05-09" updated_at: "2026-05-09" keywords: - "EU eIDAS Regulation" - "QES" - "AdES" - "qualified electronic signature" - "advanced electronic signature" - "qualified certificate" - "QTSP" - "QSCD" - "trusted lists" - "validation evidence" - "qualified trust service provider" --- **[SORENA](https://www.sorena.io/)** - AI-Powered GRC Platform [Home](https://www.sorena.io/) | [Solutions](https://www.sorena.io/solutions) | [Artifacts](https://www.sorena.io/artifacts) | [About Us](https://www.sorena.io/about-us) | [Contact](https://www.sorena.io/contact) | [Portal](https://app.sorena.io) --- # QES vs AdES under EU eIDAS: legal effect, certificates, QTSPs, and validation evidence Compare qualified electronic signatures (QES) and advanced electronic signatures (AdES) under EU eIDAS, including legal effect, qualified certificates, QTSP status, QSCDs, and validation evidence. *FAQ* *EU eIDAS* ## QES vs AdES under the EU eIDAS Regulation A qualified electronic signature is not a separate technology from an advanced electronic signature: under eIDAS, a QES is an AdES plus a qualified certificate for electronic signatures and a qualified electronic signature creation device. Use this page to 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 QES must first satisfy the AdES 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 qualified certificate for electronic signatures issued by a qualified trust service provider, and it must be created by a qualified electronic signature creation device. ## QES vs AdES under eIDAS: practical differences Use this comparison to decide whether the record needs only AdES evidence or the additional qualified certificate, QTSP, QSCD, and validation evidence needed for QES. - **Qualified electronic signature (QES)**: An advanced electronic signature created by a qualified electronic signature creation device and based on a qualified certificate for electronic signatures. - **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. | Dimension | Qualified electronic signature (QES) | Advanced electronic signature (AdES) | Operational implication | Sources | | --- | --- | --- | --- | --- | | Scope boundary | Has the equivalent legal effect of a handwritten signature under eIDAS Article 25. | 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. | Use QES where handwritten-signature equivalence is required; use AdES where the legal need is strong electronic evidence assessed in context. | [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 25 is the legal-effect rule for the QES versus AdES distinction. | | Covered actors | Requires a qualified certificate for electronic signatures issued by a qualified trust service provider, and the trusted-list record should support that status. | May use certificates and trust services, but AdES status alone is not proof that the certificate is qualified or that the provider has qualified status for that service. | For QES, validate QTSP and qualified-certificate status from trusted-list evidence; for AdES, keep certificate and identity evidence without overstating qualified status. | [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 26 defines AdES without requiring qualified certificate status.
[Commission Implementing Decision (EU) 2015/1505 on trusted lists](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX%3A32015D1505&ref=sorena.io) - Supports using trusted-list evidence to distinguish qualified and non-qualified certificate status. | | Trigger | Requires creation by a qualified electronic signature creation device. Remote QSCD management must be performed as a qualified service by a qualified trust service provider. | Requires creation data that the signatory can use under sole control with a high level of confidence, but Article 26 does not require a QSCD. | QES evidence must include QSCD or remote QSCD support; AdES evidence should focus on signer control and integrity without claiming device qualification. | [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - The QES definition in Article 3 adds QSCD status to the AdES baseline. | | Core obligations | 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. | 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. | A QES validation report should be retained with trusted-list, certificate, revocation, QSCD, and signed-data-integrity evidence; AdES records should not omit signer identity, signer control, and tamper-detection evidence. | [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 33 supports retaining an automated qualified-validation result for QES where a qualified validation service is used. | | Evidence record | Classify as QES only when the evidence proves AdES requirements, qualified certificate status, QTSP issuance, QSCD creation, and a valid QES validation result. | Classify as AdES when the evidence proves Article 26 requirements but the record does not prove every qualified certificate, QTSP, QSCD, and QES validation condition. | Use the lowest accurate label. Calling an AdES a QES creates a certificate, provider-status, device, and validation-evidence gap. | [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Supports using separate labels for AdES, AdES based on qualified certificates, and QES. | | Validation timing | QES validation is time-sensitive: the record has to prove qualified status at the time of signing, not just at review time. | AdES review focuses on whether the Article 26 conditions were met at signing; there is no QES-only timing layer to prove. | Keep timestamps, revocation evidence, and validation output for QES. For AdES, keep enough evidence to show the Article 26 conditions at the signing moment. | [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 32 and Article 32a show that the validation point is the signing moment. | | Legal effect and admissibility | Receives the equivalent legal effect of a handwritten signature. | Stays admissible as evidence, but it does not get handwritten-signature equivalence by itself. | Treat QES as the higher legal-effect label. Treat AdES as the evidence-based option unless a rule specifically asks for qualified status. | [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 25 separates admissibility from the special legal effect of QES. | | Overlap and reuse | A valid QES record normally already contains the proof needed to satisfy the AdES baseline. | An AdES record does not automatically prove the extra qualified certificate and QSCD layers required for QES. | Reuse QES evidence when you only need AdES proof, but do not upgrade an AdES label to QES without the extra qualified-status evidence. | [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - The QES definition is built on the AdES baseline, so evidence can be reused downward but not upgraded upward without proof. | | Practical decision rule | Choose QES when the request or rule calls for handwritten-signature equivalence or when the file must prove qualified status end to end. | Choose AdES when the business or legal need is strong electronic evidence, but qualified-status proof is not required. | Start from the legal requirement, then label the signature at the lowest level that the evidence supports. | [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 25 and Article 26 together support the lowest-accurate-label rule. | Sources for Scope boundary - Qualified electronic signature (QES): - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 25 gives QES handwritten-signature equivalence. - Quote: "equivalent legal effect of a handwritten signature" Sources for Scope boundary - Advanced electronic signature (AdES): - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 25 preserves admissibility for electronic signatures even when they are not qualified. - Quote: "not be denied legal effect and admissibility as evidence" Sources for Scope boundary - operational implication: - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 25 is the legal-effect rule for the QES versus AdES distinction. - Quote: "Legal effects of electronic signatures" Sources for Covered actors - Qualified electronic signature (QES): - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 3 defines qualified certificates and qualified trust service providers; Article 22 requires trusted lists. - Quote: "issued by a qualified trust service provider" - [Commission Implementing Decision (EU) 2015/1505 on trusted lists](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX%3A32015D1505&ref=sorena.io) - Explains trusted-list indicators for qualified certificate and qualified service status. - Quote: "Service current status" Sources for Covered actors - Advanced electronic signature (AdES): - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 26 defines AdES without requiring qualified certificate status. - Quote: "Requirements for advanced electronic signatures" Sources for Covered actors - operational implication: - [Commission Implementing Decision (EU) 2015/1505 on trusted lists](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX%3A32015D1505&ref=sorena.io) - Supports using trusted-list evidence to distinguish qualified and non-qualified certificate status. - Quote: "the certificate is not to be considered as qualified" Sources for Trigger - Qualified electronic signature (QES): - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Articles 29 and 29a cover QSCD and remote QSCD requirements. - Quote: "qualified electronic signature creation devices shall meet" Sources for Trigger - Advanced electronic signature (AdES): - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 26 requires signer-control of electronic signature creation data for AdES. - Quote: "under his sole control" Sources for Trigger - operational implication: - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - The QES definition in Article 3 adds QSCD status to the AdES baseline. - Quote: "created by a qualified electronic signature creation device" Sources for Core obligations - Qualified electronic signature (QES): - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 32 lists the validation conditions for qualified electronic signatures. - Quote: "Requirements for the validation of qualified electronic signatures" Sources for Core obligations - Advanced electronic signature (AdES): - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 26 defines AdES; Article 32a covers AdES based on qualified certificates. - Quote: "advanced electronic signatures based on qualified certificates" Sources for Core obligations - operational implication: - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 33 supports retaining an automated qualified-validation result for QES where a qualified validation service is used. - Quote: "receive the result of the validation process" Sources for Evidence record - Qualified electronic signature (QES): - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Articles 3, 26, 28, 29, and 32 collectively define the QES evidence stack. - Quote: "qualified electronic signature means an advanced electronic signature" Sources for Evidence record - Advanced electronic signature (AdES): - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 26 is the standalone AdES test. - Quote: "linked to the data signed therewith" Sources for Evidence record - operational implication: - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Supports using separate labels for AdES, AdES based on qualified certificates, and QES. - Quote: "Validation of advanced electronic signatures based on qualified certificates" Sources for Validation timing - Qualified electronic signature (QES): - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 32 requires the qualified certificate to have been valid at the time of signing. - Quote: "was valid at the time of signing" Sources for Validation timing - Advanced electronic signature (AdES): - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 26 is the underlying AdES test, with no separate qualified-validation timing rule. - Quote: "Requirements for advanced electronic signatures" Sources for Validation timing - operational implication: - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 32 and Article 32a show that the validation point is the signing moment. - Quote: "at the time of signing" Sources for Legal effect and admissibility - Qualified electronic signature (QES): - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 25 gives QES handwritten-signature equivalence. - Quote: "equivalent legal effect of a handwritten signature" Sources for Legal effect and admissibility - Advanced electronic signature (AdES): - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 25 preserves admissibility for all electronic signatures. - Quote: "not be denied legal effect and admissibility as evidence" Sources for Legal effect and admissibility - operational implication: - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 25 separates admissibility from the special legal effect of QES. - Quote: "Legal effects of electronic signatures" Sources for Overlap and reuse - Qualified electronic signature (QES): - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - QES includes the Article 26 AdES conditions plus the qualified layers. - Quote: "qualified electronic signature means an advanced electronic signature" Sources for Overlap and reuse - Advanced electronic signature (AdES): - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - AdES is defined separately in Article 26 and does not require QSCD status. - Quote: "Requirements for advanced electronic signatures" Sources for Overlap and reuse - operational implication: - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - The QES definition is built on the AdES baseline, so evidence can be reused downward but not upgraded upward without proof. - Quote: "A qualified electronic signature shall have the equivalent legal effect of a handwritten signature" Sources for Practical decision rule - Qualified electronic signature (QES): - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 25 gives QES handwritten-signature equivalence. - Quote: "equivalent legal effect of a handwritten signature" Sources for Practical decision rule - Advanced electronic signature (AdES): - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 26 is the standalone AdES standard. - Quote: "Requirements for advanced electronic signatures" Sources for Practical decision rule - operational implication: - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 25 and Article 26 together support the lowest-accurate-label rule. - Quote: "not be denied legal effect and admissibility as evidence" ### 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 QES 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 AdES 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 QES without showing the qualified certificate, trusted-list status, QSCD evidence, and Article 32 validation result. Sources for the practical decision rule: - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Primary source for the QES and AdES decision criteria. - Quote: "Requirements for advanced electronic signatures" ## What is the practical difference between a QES and an AdES under eIDAS? An AdES 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 QES is an AdES that also uses a qualified certificate for electronic signatures and a qualified electronic signature creation device. 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. - Use AdES 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 QES language only when the record proves the qualified certificate, the qualified trust service provider, the qualified creation device, and the Article 26 AdES requirements. - Do not call a signature QES merely because it uses a digital certificate, a strong login, an audit trail, or a vendor label. Sources for this answer: - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 3 defines AdES and QES, Article 25 states the legal effects, and Article 26 lists the four AdES requirements. ## What must be checked before relying on QES status? For QES, 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. - 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 QES status is claimed. - Keep the trusted-list or LOTL evidence used to establish the QTSP, qualified service, certificate, and QSCD status. Sources for this answer: - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Articles 22, 28, 29, and 32 support the trusted-list, qualified-certificate, QSCD, and qualified-validation checks needed for QES reliance. - [Commission Implementing Decision (EU) 2015/1505 on trusted lists](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX%3A32015D1505&ref=sorena.io) - Explains how Member State trusted lists identify qualified trust services, qualified certificate status, and QSCD-related qualifiers. - [European Commission eSignature building block](https://ec.europa.eu/digital-building-blocks/sites/spaces/DIGITAL/pages/467109036/eSignature?ref=sorena.io) - Identifies Commission eSignature resources, including the eIDAS Dashboard, Trusted List Browser, and validation tooling for signature verification work. ## When is AdES enough, and when should a team require QES? AdES 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, but their probative value is assessed from the evidence around the transaction. Require QES when a law, public-service requirement, customer mandate, procurement clause, or organization risk decision specifically requires qualified status or handwritten-signature equivalence. In that case, a normal AdES audit trail is incomplete unless it also proves the qualified certificate, QTSP, QSCD, and validation conditions. - For AdES, document the identity proofing and authentication method, signer intent, signer-control evidence, signed-data hash or signature linkage, and tamper-detection result. - For QES, 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 QES: eIDAS Article 32a has validation requirements for that middle case, but it lacks the QSCD requirement that distinguishes QES. Sources for this answer: - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Article 25 preserves admissibility for electronic signatures generally, Article 32 validates QES, and Article 32a covers AdES based on qualified certificates. ## Primary sources - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj?ref=sorena.io) - Primary source for the QES and AdES decision criteria. - Quote: "Requirements for advanced electronic signatures" - [Commission Implementing Decision (EU) 2015/1505 on trusted lists](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX%3A32015D1505&ref=sorena.io) - Supports using trusted-list evidence to distinguish qualified and non-qualified certificate status. - Quote: "the certificate is not to be considered as qualified" - [European Commission eSignature building block](https://ec.europa.eu/digital-building-blocks/sites/spaces/DIGITAL/pages/467109036/eSignature?ref=sorena.io) - Source for Commission eSignature resources and tooling, including the eIDAS Dashboard, Trusted List Browser, and validation support. - Quote: "creation and verification of electronic signatures" ## Topic Guides - [eIDAS 2 deadlines and compliance calendar for EUDI Wallet and trust services](/artifacts/eu/electronic-identification-and-trust-services-regulation/deadlines-and-compliance-calendar.md): Calendar of grounded eIDAS and eIDAS 2 milestones for EUDI Wallet delivery, implementing acts, annual supervision reports, QTSP transitions, pilots, and ARF evidence. - [eIDAS 2.0 vs eIDAS: EUDI Wallet and trust-service changes](/artifacts/eu/electronic-identification-and-trust-services-regulation/eidas2-vs-eidas.md): Compare the original eIDAS electronic identification and trust-service framework with the eIDAS 2.0 amendments for EUDI Wallets, relying parties, attestations, QWACs, and supervision. - [eIDAS Certificates and Authentication: qualified certificates, QWACs, and validation checks](/artifacts/eu/electronic-identification-and-trust-services-regulation/certificates-and-authentication.md): Grounded guide to eIDAS qualified certificates, website authentication certificates, trusted lists, relying-party checks, and validation evidence. - [eIDAS checklist and evidence pack for trust services, signatures, and EUDI Wallet relying parties](/artifacts/eu/electronic-identification-and-trust-services-regulation/checklist-and-evidence.md): Build an eIDAS evidence pack for qualified trust services, electronic signatures, trusted-list checks, certificate validation, supervisory records, and EUDI Wallet relying-party controls. - [eIDAS compliance guide for trust services, QTSPs, signatures, and EUDI Wallet relying parties](/artifacts/eu/electronic-identification-and-trust-services-regulation/compliance.md): Grounded eIDAS compliance guide for trust-service classification, QTSP supervision evidence, qualified signatures, seals, time stamps, certificates, trusted-list validation, and EUDI Wallet relying-party records. - [eIDAS electronic signatures: SES, AES, QES legal effect and evidence](/artifacts/eu/electronic-identification-and-trust-services-regulation/electronic-signatures-and-legal-effect.md): A grounded guide to eIDAS electronic-signature legal effect: SES, AES, QES, qualified certificates, QTSP trusted-list checks, validation, recognition, and evidence records. - [eIDAS penalties and fines for trust service providers](/artifacts/eu/electronic-identification-and-trust-services-regulation/penalties-and-fines.md): Grounded guide to eIDAS Article 16 penalties, administrative fine mechanics, supervisory bodies, qualified-status withdrawal, and trusted-list evidence. - [eIDAS QES validation checks for relying parties](/artifacts/eu/electronic-identification-and-trust-services-regulation/qes-validation.md): How to validate a qualified electronic signature under eIDAS: certificate, QTSP, trusted-list, QSCD, integrity, validation result, and evidence records. - [eIDAS Qualified Trust Services: QTSP Selection](/artifacts/eu/electronic-identification-and-trust-services-regulation/qualified-trust-services-and-qtsp-selection.md): How to select an EU eIDAS qualified trust service provider: identify the qualified service type, verify trusted-list status, review supervision evidence, and retain certificate-policy records. - [eIDAS remote signature and cloud HSM controls for QTSPs](/artifacts/eu/electronic-identification-and-trust-services-regulation/remote-signature-and-cloud-hsm-controls.md): Grounded guide to eIDAS remote signature controls: remote QSCD scope, server-side signing, QTSP evidence, signer authentication, certificate validation, and trusted-list checks. - [eIDAS signature legal effect selector: SES, AES, AES-QC, or QES](/artifacts/eu/electronic-identification-and-trust-services-regulation/signature-legal-effect-selector-workflow.md): Select the right eIDAS signature level by legal effect, risk, qualified certificate status, QTSP evidence, QSCD use, validation result, and cross-border recognition. - [eIDAS trust service role scoping workflow: TSP, QTSP, validator, relying party, or QTSP customer](/artifacts/eu/electronic-identification-and-trust-services-regulation/trust-service-role-scoping-workflow.md): Classify an eIDAS role by evidence: trust service provider, qualified trust service provider, signature or seal validator, EUDI Wallet relying party, relying party, or customer of a QTSP. - [eIDAS trusted list validation: LOTL, QTSP status, and evidence](/artifacts/eu/electronic-identification-and-trust-services-regulation/trust-list-validation.md): How to validate EU eIDAS trusted-list evidence: start from the Commission LOTL, confirm QTSP and qualified-service status, check certificate path and revocation data, and retain validation reports. - [eIDAS vs ESIGN and UETA: EU qualified signatures vs U.S. e-signature laws](/artifacts/eu/electronic-identification-and-trust-services-regulation/eidas-vs-esign-and-ueta.md): Compare eIDAS with ESIGN and UETA for electronic signatures, qualified certificates, trust services, cross-border recognition, validation evidence, and source gaps. - [eIDAS vs ETSI EN 319 401: legal supervision and TSP policy requirements](/artifacts/eu/electronic-identification-and-trust-services-regulation/eidas-vs-etsi-en-319-401.md): Compare eIDAS and ETSI EN 319 401 for trust services: legal scope, QTSP supervision, conformity assessment, audits, incident evidence, and operational controls. - [eIDAS vs GDPR for identity data: wallet, trust-service, and privacy obligations](/artifacts/eu/electronic-identification-and-trust-services-regulation/eidas-vs-gdpr-identity-data.md): Compare eIDAS identity, trust-service, and EUDI Wallet rules with GDPR duties for personal-data processing, minimisation, lawful basis, evidence, security, and user rights. - [eIDAS vs NIS2 for trust service providers: QTSP and cybersecurity obligations](/artifacts/eu/electronic-identification-and-trust-services-regulation/eidas-vs-nis2-trust-services.md): Compare eIDAS trust-service and QTSP duties with NIS2 cybersecurity risk-management, incident reporting, supervision, and evidence duties for trust service providers. - [Electronic Attestations of Attributes under EU eIDAS: EAA, QEAA, issuers, wallets, and validation](/artifacts/eu/electronic-identification-and-trust-services-regulation/electronic-attestations-of-attributes.md): Grounded guide to electronic attestations of attributes under amended EU eIDAS: EAA, QEAA, public-sector authentic-source attestations, wallet use, issuer checks, relying-party validation, revocation, and legal effect. - [EU eIDAS Applicability Test for Trust Services, Wallets, and Certificates](/artifacts/eu/electronic-identification-and-trust-services-regulation/applicability-test.md): A grounded eIDAS scope test for QTSPs, trust services, electronic signatures, seals, timestamps, QWACs, EUDI Wallet relying parties, and cross-border recognition evidence. - [EU eIDAS attribute attestations: EAA, QEAA, wallet, and relying party checks](/artifacts/eu/electronic-identification-and-trust-services-regulation/faq/attribute-attestations.md): What electronic attestations of attributes mean under eIDAS, how QEAAs differ from public-sector and non-qualified attestations, and what issuers, wallets, and relying parties should verify. - [EU eIDAS checklist for signatures, trust services, and wallets](/artifacts/eu/electronic-identification-and-trust-services-regulation/checklist.md): Checklist for eIDAS trust-service and EUDI Wallet controls: qualified status, trusted lists, certificates, signatures, seals, timestamps, validation evidence, and relying-party records. - [EU eIDAS FAQ: signatures, QTSPs, trusted lists, QWACs, wallets, and validation](/artifacts/eu/electronic-identification-and-trust-services-regulation/faq.md): FAQ on eIDAS trust services and the European Digital Identity framework, covering advanced and qualified electronic signatures, QTSP status, trusted lists, QWACs, EUDI Wallet relying parties, attestations of attributes, and validation evidence. - [EU eIDAS QTSP authorization and supervision guide](/artifacts/eu/electronic-identification-and-trust-services-regulation/qtsp-authorization-and-supervision.md): How qualified trust service providers obtain and keep qualified status under eIDAS, including conformity assessment reports, supervision, trusted lists, incidents, and evidence. - [EU eIDAS QTSP Due Diligence Workflow for Trusted Lists, Certificates, and Evidence](/artifacts/eu/electronic-identification-and-trust-services-regulation/qtsp-due-diligence-workflow.md): Check a qualified trust service provider under eIDAS by validating trusted-list status, qualified service scope, certificates, policies, supervision, audits, and retained evidence. - [EU eIDAS Requirements for Trust Services, Signatures, Seals, Wallets, and Evidence](/artifacts/eu/electronic-identification-and-trust-services-regulation/requirements.md): Grounded guide to core eIDAS requirements for trust service providers, qualified trust services, electronic signatures, seals, time stamps, trusted lists, and EUDI Wallet relying parties. - [EU eIDAS Trusted Lists FAQ: LOTL, QTSP status, and validation evidence](/artifacts/eu/electronic-identification-and-trust-services-regulation/faq/trusted-lists.md): How EU eIDAS Trusted Lists and the Commission LOTL support QTSP and qualified trust-service validation, with practical evidence checks for relying parties. - [EUDI Wallet readiness for service providers under eIDAS](/artifacts/eu/electronic-identification-and-trust-services-regulation/eudi-wallet-readiness.md): Readiness guide for organisations preparing to request or verify data from European Digital Identity Wallets: roles, registration, ARF alignment, selective disclosure, implementing acts, and evidence. - [EUDI Wallet Relying Parties under eIDAS](/artifacts/eu/electronic-identification-and-trust-services-regulation/faq/eudi-wallet-relying-party.md): What EUDI Wallet relying parties must do under eIDAS: register, declare intended wallet use and requested data, identify themselves to users, and keep request evidence. - [EUDI Wallet Relying Party Onboarding Workflow under eIDAS](/artifacts/eu/electronic-identification-and-trust-services-regulation/wallet-onboarding-workflow.md): A grounded onboarding workflow for organisations that want to request data from European Digital Identity Wallet users as eIDAS wallet relying parties. - [EUDI Wallet Relying Party Registration Under eIDAS](/artifacts/eu/electronic-identification-and-trust-services-regulation/eudi-wallet-relying-party-registration.md): What eIDAS Article 5b and the EUDI Wallet ARF say about wallet relying party registration, intended uses, attribute requests, certificates, evidence, and Member State gaps. - [EUDI Wallet Technical Architecture Guide under eIDAS](/artifacts/eu/electronic-identification-and-trust-services-regulation/eudi-wallet-technical-architecture-guide.md): Technical guide to the EUDI Wallet architecture: ARF roles, wallet units, PID and attestations, relying parties, trust model, certificates, protocols, privacy, and security controls. - [QWACs under eIDAS: website authentication certificates](/artifacts/eu/electronic-identification-and-trust-services-regulation/qwacs.md): A grounded guide to qualified website authentication certificates under eIDAS, covering Annex IV data, trusted lists, browser recognition, validation evidence, and QTSP checks. - [What eIDAS Covers: eID, Trust Services, EUDI Wallet, and QWACs](/artifacts/eu/electronic-identification-and-trust-services-regulation/what-eidas-covers.md): A grounded guide to the systems and services covered by EU eIDAS: notified electronic identification, trust services, signatures, seals, time stamps, registered delivery, website authentication, trusted lists, the EUDI Wallet, and attribute attestations. - [What is a qualified trust service provider under eIDAS?](/artifacts/eu/electronic-identification-and-trust-services-regulation/faq/qualified-trust-service-provider.md): How to verify QTSP status under eIDAS using the qualified service, supervisory body decision, trusted list entry, conformity assessment evidence, and service-specific records. - [What is a QWAC under the EU eIDAS Regulation?](/artifacts/eu/electronic-identification-and-trust-services-regulation/faq/qwac.md): Plain-language FAQ on qualified website authentication certificates under eIDAS, including website identity, QTSP trusted-list checks, browser recognition, and validation evidence. *Recommended next step* *Placement: before sources* ## 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. - [Open Research Copilot for eIDAS](/solutions/research-copilot.md): Ask cited questions about QES, AdES, QTSPs, trusted lists, QSCD evidence, and validation records using the sources on this page. - [Talk through implementation](/contact.md): Review your signature levels, vendor evidence, validation reports, and retention approach with Sorena. --- [Privacy Policy](https://www.sorena.io/privacy) | [Terms of Use](https://www.sorena.io/terms-of-use) | [DMCA](https://www.sorena.io/dmca) | [About Us](https://www.sorena.io/about-us) (c) 2026 Sorena AB (559573-7338). All rights reserved. Source: https://www.sorena.io/artifacts/eu/electronic-identification-and-trust-services-regulation/faq/qes-vs-ades