Teams deploying electronic signatures, seals, timestamps and website certificates in the EU often cannot say whether what they bought is "qualified", and that difference decides legal effect, evidential presumptions and which supervisor is watching the provider. The eIDAS Regulation (EU) No 910/2014, as amended by Regulation (EU) 2024/1183, defines trust services, sets extra requirements for qualified trust service providers (QTSPs) and gives qualified signatures, seals, timestamps and registered delivery specific legal effects. This guide covers what is in scope, the obligations on QTSPs, the legal effect of each qualified service, supervision and penalties, and how relying parties and engineering teams should choose and verify services. It complements, and does not repeat, the eIDAS 2.0 and the European Digital Identity Framework Guide, which covers the wallet. Status checked on 27 October 2026 against the consolidated text on EUR-Lex.
Key takeaways
- Qualified changes legal effect. A qualified electronic signature has the equivalent legal effect of a handwritten signature (Article 25(2)); qualified seals, timestamps and registered delivery carry presumptions of integrity, origin or accuracy.
- Status comes from the trusted list. A provider may start a qualified service only once its status appears in a Member State trusted list (Article 21(3)); marketing claims are not proof.
- QTSPs are audited every 24 months. Conformity assessment bodies audit QTSPs at least every 24 months, and the report reaches the supervisory body within three working days (Article 20(1)).
- Breaches are reported in 24 hours. Trust service providers notify the supervisory body of significant security breaches within 24 hours of becoming aware (Article 19(2)).
- Fines start at EUR 5 million. Member States must allow maximum fines of at least EUR 5,000,000 or, for legal persons, 1% of worldwide annual turnover if higher (Article 16).
Scope: who and what is covered
The amended Regulation applies to trust service providers established in the Union, alongside notified eID schemes and European Digital Identity Wallets (Article 2(1)), and is without prejudice to the GDPR (Article 2(4)). Article 3(16) defines "trust service" as a list of services (a) to (n), now including electronic attestations of attributes, electronic archiving and the recording of data in electronic ledgers, in addition to the established signature, seal, timestamp, registered delivery, website authentication, validation and preservation services.
| Qualified service | Key articles | Legal effect or presumption | Typical use |
|---|---|---|---|
| Qualified electronic signature (QES) | 25 to 34 | Equivalent legal effect of a handwritten signature (25(2)) | Contracts, regulated forms, board resolutions |
| Qualified electronic seal | 35 to 40a | Presumption of integrity of the data and correctness of its origin (35(2)) | Invoices, statements, machine-issued documents from a legal person |
| Qualified electronic time stamp | 41, 42 | Presumption of accuracy of date and time and integrity of the bound data (41(2)) | Long-term signature validity, evidence of existence at a time |
| Qualified electronic registered delivery | 43, 44 | Presumption of integrity, sender and addressee identification and accuracy of sending and receipt times (43(2)) | Legal notices, regulated correspondence |
| Qualified certificate for website authentication (QWAC) | 3(38), 45, 45a | See the QWAC section below | Identifying the legal entity behind a website |
| Qualified validation and preservation | 32 to 34 | Validation confirms the conditions in 32(1) | Automated signature checking and long-term archives |
Qualified, advanced and simple
- Simple electronic signature: cannot be denied legal effect or admissibility solely because it is electronic (25(1)), but has no presumption.
- Advanced electronic signature (AdES): uniquely linked to and capable of identifying the signatory, created with data under the signatory's sole control with a high level of confidence, and linked to the data so later changes are detectable (Article 26).
- Qualified electronic signature: an AdES created by a qualified signature creation device (QSCD) and based on a qualified certificate.
Key obligations
Obligations on all trust service providers
- Security (Article 19(1)): technical and organisational measures proportionate to the risk.
- Breach notice (Article 19(2)): notify the supervisory body within 24 hours of becoming aware of a significant breach or loss of integrity; notify affected persons without undue delay where adverse effects are likely. Non-qualified providers have matching duties in Article 19a. The supervisory body sends ENISA an annual summary (19(3)).
Additional obligations on QTSPs
| Obligation | Article | Detail |
|---|---|---|
| Initiation | 21 | Notify the supervisory body with a conformity assessment report; status granted within three months if requirements are met; start only once on the trusted list |
| Audit | 20(1), 20(1a) | Conformity assessment at least every 24 months at the provider's expense; report within three working days; notify planned audits one month ahead |
| Ad hoc audit and withdrawal | 20(2), 20(3) | Supervisory body can audit at any time and withdraw qualified status if failings are not remedied |
| Identity verification | 24(1), 24(1a) | Before issuing a qualified certificate or qualified attestation, verify identity by: (a) EU Digital Identity Wallet or notified eID at assurance level high; (b) a QES or qualified seal certificate issued under (a), (c) or (d); (c) other methods confirmed by a conformity assessment body as giving high confidence; or (d) physical presence |
| Change and cessation notice | 24(2)(a) | Notify the supervisory body one month before changes, three months before ceasing |
| Staff and resources | 24(2)(b), (c) | Trained staff; sufficient financial resources or liability insurance |
| Trustworthy systems | 24(2)(e) | Trustworthy, tamper-protected systems and products |
| Termination plan and records | 24(2)(i), (k) | Up-to-date termination plan; certificate database |
| Revocation | 24(3) | Register and publish revocations within 24 hours of the request, effective on publication |
| Status service | 24(4) | Free, automated validity or revocation status for relying parties |
Devices, remote signing and validation
- QSCD certification (Article 30): conformity with Annex II is certified by designated bodies; certification is valid for up to five years with vulnerability assessments every two years, and unremedied vulnerabilities lead to cancellation. Member States notify certifications to the Commission within one month (Article 31).
- Remote QSCD (Articles 29(1a) and 29a): only a QTSP may generate, manage or back up signature creation data on the signatory's behalf, with backups at the same security level and the minimum number of copies.
- Validation (Articles 32 and 32a): a QES validates only if the conditions in 32(1) are met, including that the certificate was qualified at the time of signing and the signature was created by a QSCD; the system must give relying parties a correct result and expose security issues.
- Qualified timestamps (Article 42(1)): bind date and time to data to prevent undetectable change, use an accurate time source linked to Coordinated Universal Time, and are signed or sealed by the QTSP.
Qualified website authentication certificates (QWACs)
Article 3(38) defines a certificate for website authentication, and Articles 45 and 45a, as replaced by Regulation 2024/1183, set the requirements for qualified and non-qualified website certificates. Recital 65 explains the policy intent: browser providers should not deny the authenticity of qualified website certificates on the ground of the link between a domain and its holder, and may take narrowly defined precautionary measures after substantiated security concerns, with notification. We could not read the replaced Article 45 text in full on 27 October 2026, so read the article itself before designing anything that depends on browser behaviour. For the operational side of TLS certificates, see the Certificate Expiry Outages and 47-Day TLS Certificates Guide.
Timeline and current status
| Date | Event |
|---|---|
| 2014 | Regulation (EU) No 910/2014 (eIDAS) adopted |
| 11 April 2024 | Regulation (EU) 2024/1183 adopted (OJ L, 30 April 2024) |
| 20 May 2024 | Date of the consolidated eIDAS text on EUR-Lex incorporating 2024/1183 |
| 21 May 2025 | Deadline for Commission implementing acts on reference standards for, among others, remote QSCD management (29a(2)), validation (32(3), 32a(3)) and qualified timestamps (42(2)) |
| 21 May 2026 | Commission assessment of implementing acts for advanced signatures (26(2)) and seals (36(2)) |
Implementing acts set the reference standards that give a presumption of compliance, so check the latest Commission implementing regulations for each service before procurement. In practice QTSPs are commonly audited against ETSI policy standards such as ETSI EN 319 401 (general requirements), EN 319 411-2 (qualified certificates) and EN 319 421 (time stamping); confirm which standards the implementing acts reference.
Enforcement and penalties
- Fines (Article 16): Member States set penalties for qualified and non-qualified providers, with maximum fines of at least EUR 5,000,000 for natural persons and, for legal persons, EUR 5,000,000 or 1% of total worldwide annual turnover in the preceding financial year, whichever is higher.
- Withdrawal of qualified status (Article 20(3)): the strongest commercial sanction, since the provider drops off the trusted list and its services lose qualified effect going forward.
- Supervision: each Member State's designated supervisory body can audit at any time (Article 20(2)) and receives breach notices and audit reports.
What it means for AI agents and non-human identities
- Seals are the machine signature: a qualified electronic seal belongs to a legal person and is the natural fit for documents issued automatically by systems, including AI pipelines, because it presumes origin and integrity without a human signatory.
- Sole control for signatures: an AdES requires signature creation data under the signatory's sole control. An AI agent triggering a QES on a person's behalf must have an explicit, auditable authorisation flow, otherwise the "sole control" condition is in doubt.
- Remote signing credentials: remote QSCD services authenticate the signer and the calling application. The API credentials of the calling service are non-human identities that must be protected, scoped and rotated. See the Machine Identity, PKI and Certificate Lifecycle Guide.
- Timestamps for AI evidence: qualified timestamps over model outputs, logs or datasets create a presumption that the data existed unchanged at that time, which is useful for audit trails of automated decisions.
- Status checking at machine speed: relying systems must check revocation via the free status service (24(4)) and the trusted list, not cache trust indefinitely.
Compliance steps
For relying parties and organisations using trust services:
- Decide the level you need. Map each process to simple, advanced or qualified based on the legal effect required and sector rules.
- Verify the provider on the trusted list. Check the specific service type, not just the company, on the national trusted list or the Commission's publication of the lists (Article 22(4)).
- Validate properly. Use a qualified validation service or a validation library that applies the Article 32(1) conditions and checks status at signing time.
- Add timestamps for long-term evidence. Apply qualified timestamps and preservation so signatures stay verifiable after certificates expire.
- Control signing authority. Define who and what may trigger signatures and seals, and log every request.
- Plan for provider exit. Ask for the QTSP's termination plan and how evidence remains verifiable if it ceases.
For providers seeking qualified status: choose an accredited conformity assessment body, prepare the conformity assessment report, notify the supervisory body under Article 21, and build the 24 hour breach process, revocation within 24 hours and the termination plan before launch.
Decision guidance
| Need | Choose | Why |
|---|---|---|
| Contract signed by a person, cross-border, minimum dispute risk | QES | Handwritten equivalence across Member States |
| High volume internal approvals | AdES | Lower cost; evidential weight without the qualified presumption |
| System-issued documents from a company | Qualified seal | Origin and integrity presumption for a legal person |
| Proving data existed at a time | Qualified timestamp | Presumption of accuracy of date and time |
| Legal notices by electronic means | Qualified registered delivery | Presumptions on sender, addressee and timing |
Detection and measurement
- Monitor: trusted list changes for your providers, certificate revocations, validation failures, signing API usage per calling application and unusual signing volumes.
- Metric: percentage of signatures and seals validated against the trusted list at signing time.
- Metric: percentage of long-term records with qualified timestamps or preservation.
- Metric: number of signing credentials (API keys, client certificates) with owner and rotation date.
- Metric: time to detect a provider's loss of qualified status.
Common failure patterns
- Believing the label: buying a "qualified" product whose specific service is not on the trusted list.
- Validating only the certificate chain: ignoring whether a QSCD was used and whether the certificate was qualified at signing time.
- No timestamps: signatures that become hard to validate once the signing certificate expires.
- Shared signing credentials: one API key used by many applications to trigger seals, so origin cannot be traced. See the Code Signing Security Guide for analogous controls.
- Ignoring provider exit: no plan for verifying evidence if a QTSP ceases or loses status.
Framework mapping
| eIDAS element | NIST CSF 2.0 | NIST SP 800-53 Rev 5 |
|---|---|---|
| Identity verification (24(1a)) | PR.AA-02 | IA-12 |
| Signature creation data and keys | PR.DS-01 | SC-12 |
| Breach notification (19(2)) | RS.CO-02 | IR-6 |
| Audit every 24 months (20) | ID.IM-01 | CA-2 |
| Provider selection and trusted list checks | GV.SC-07 | SA-9, SR-6 |
| Data integrity and timestamps | PR.DS-01 | AU-10 |
Practitioner checklist
- Map each signing or sealing process to the level of assurance it needs.
- Check each provider's specific service on the trusted list and monitor changes.
- Validate signatures with Article 32(1) conditions and status at signing time.
- Apply qualified timestamps to records that must survive certificate expiry.
- Inventory and protect API credentials used for remote signing and sealing.
- Log every signature and seal request with the calling identity.
- Obtain the QTSP's termination plan and evidence continuity arrangements.
- Read the current Article 45 text and implementing acts before relying on QWAC behaviour.
Standards and references
- EUR-Lex: Regulation (EU) No 910/2014 (eIDAS), consolidated text
- EUR-Lex: Regulation (EU) 2024/1183 establishing the European Digital Identity Framework
- European Commission: eIDAS Regulation
Related NHI Mgmt Group resources: eIDAS 2.0 and the European Digital Identity Framework Guide · Machine Identity, PKI and Certificate Lifecycle Guide · Enterprise PKI Design and CA Hierarchy Guide · Code Signing Security Guide. This guide summarises the qualified trust service provisions of the eIDAS Regulation as amended and checked on 27 October 2026 and is not legal advice.