Track binding eIDAS 2 dates for delivery, annual reports, and trust-service transitions alongside implementing acts and non-binding programme milestones.
Use the legal trigger, affected actor, owner, and evidence for each date. A Commission publication, pilot, or Architecture and Reference Framework update is not automatically a compliance deadline.
The main delivery date is 24 December 2026: Article 5a requires each Member State to provide at least one wallet within 24 months after the relevant implementing acts entered into force on 24 December 2024. The Commission describes this as delivery by the end of 2026. Other entries below have different legal effects, including annual reporting dates, Commission adoption dates, trust-service transition dates, and non-binding technical programme milestones.
Use one calendar row per legal or programme milestone. Record the legal trigger, affected actor, internal owner, evidence to keep, and whether the date is fixed, recurring, transitional, or calculated from another act.
A date by which the Commission had to adopt an implementing act is not automatically a date by which a provider had to comply. Once an implementing regulation is adopted, read that act for its entry into force, application date, transitional rule, and referenced standards. Pilots, Architecture and Reference Framework publications, and reference implementation releases are readiness inputs rather than binding deadlines.
Sources (4)
Supports the eIDAS 2 legal trigger, wallet availability dependency, implementing-act dates, annual reporting dates, review date, and transitional trust-service dates.
within 24 months
Supports the 4 December 2024 publication milestone and the five implementing-regulation topic areas for the EUDI Wallet.
five implementing regulations
Identifies the four implementing regulations used for Article 5a(23), records Official Journal publication on 4 December 2024, and provides the entry-into-force rule used to calculate 24 December 2026.
Supports the April 2023 large-scale pilot launch, pilot continuation through 2025, and the role of the reference implementation and ARF in wallet readiness.
four large-scale pilot projects
The calendar is useful only if each row tells an owner what changed and what proof to keep. For eIDAS 2, the same date can affect different teams in different ways: a wallet provider tracks certification and core functions, an issuer tracks person identification data and attestations, a relying party tracks registration and data-request controls, and a QTSP tracks Article 24, remote QSCD, certificate, preservation, timestamp, and website-authentication standards.
For a calculated date, keep the formula and the calculation. For wallet availability, record Article 5a(1), the 24 December 2024 entry into force of the relevant acts, the resulting 24 December 2026 date, and the Commission's end-of-2026 summary.
Do not use the amended Regulation's 2025 Commission adoption deadlines as the current status. The Commission-maintained Architecture and Reference Framework lists the implementing regulations adopted during 2025. For a particular product or trust service, open the regulation itself and record its entry into force, application date, transition, and referenced-standard provisions.
Sources (4)
Supports the amended eIDAS obligations for wallet providers, relying parties, trust services, supervision, annual reporting, and transitional QTSP compliance evidence.
European Digital Identity Wallets
Supports the policy summary that Member States must provide EUDI Wallets by the end of 2026 and that wallets extend the eIDAS framework to public and private services.
by the end of 2026
Supports practical ecosystem roles, wallet use cases, implementing-act navigation, and Commission wallet readiness material for issuers and service providers.
same common specifications
Commission-maintained technical framework whose legal-context register identifies the 2024 and 2025 implementing regulations. The ARF is implementation material; the linked regulations, not the ARF itself, are the binding legal sources.
adopted Commission Implementing Regulations
Keep separate fields for fixed dates, recurring dates, and calculated dates. Fixed dates include the 21 May 2026 review and transition date and the 21 May 2027 device-transition expiry. The 31 March reports recur annually. Wallet availability and authentic-source verification are calculated from the entry into force of specified implementing acts.
For the wallet rollout, the legal formula and the Commission summary now converge: the relevant acts entered into force on 24 December 2024, producing 24 December 2026, which falls within the Commission's end-of-2026 description. Retain the formula because later amendments or a different dependent provision may use another trigger.
Sources (3)
Supports the fixed dates and dependent legal triggers that should be separated in an eIDAS calendar.
By 21 May 2025
Supports the 4 December 2024 publication date and implementing-regulation categories used as programme evidence.
Publication 04 December 2024
One of the Article 5a(23) acts; its 4 December 2024 publication and twentieth-day entry-into-force clause support the 24 December 2024 trigger date.
Before adding a new eIDAS calendar row, classify the source. EUR-Lex legal text supports binding dates and obligations. Commission wallet pages support programme milestones, ARF releases, pilots, technical specification navigation, and policy summaries. ENISA and ETSI material can support security, supervision, and standards context, but should not be used to invent statutory deadlines.
This calendar covers EU-level eIDAS and eIDAS 2 dates. Add Member State wallet launch dates, national supervisory deadlines, or sector-specific acceptance dates to your internal calendar only after confirming the applicable national or sector source, affected actor, and legal trigger.
Sources (3)
Supports the 10 February 2023 ARF v1.0.0 publication milestone and the role of ARF material as technical implementation evidence.
Publication 10 February 2023
Supports the 3 June 2021 toolbox recommendation, 22 February 2022 ARF outline milestone, and the distinction between non-mandatory outline material and binding legal acts.
non-mandatory
Supports using ENISA material as supervision context for QTSP oversight rather than as a source of new statutory calendar dates.
supervision of qualified trust service providers
Use the cited sources listed here to verify obligations and the supporting evidence requirements.
Check eIDAS 2 dates, wallet implementation dependencies, and QTSP transitions against the cited Commission and EUR-Lex sources.
Check whether your wallet, issuer, relying-party, or trust-service calendar separates legal deadlines from programme milestones and has evidence for each row.
"five implementing regulations"
"Publication 04 December 2024"
"European Digital Identity Framework"
"within 24 months"
"By 21 May 2025"
"qualified trust service providers"
"supervision of qualified trust service providers"
"by the end of 2026"
"ARF v1.0.0"
"Publication 10 February 2023"
"22 February 2022"
"non-mandatory"
"four large-scale pilot projects"
"electronic identification and trust services"
"European Digital Identity Wallets"
"adopted Commission Implementing Regulations"
"same common specifications"
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.
Official source guide to eIDAS qualified certificates, website authentication certificates, trusted lists, relying-party checks, and validation evidence.
Build an eIDAS evidence pack for qualified trust services, electronic signatures, trusted-list checks, certificate validation, supervisory records, and EUDI Wallet relying-party controls.
Official source 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.
An official source guide to eIDAS electronic-signature legal effect: SES, AES, QES, qualified certificates, QTSP trusted-list checks, validation, recognition, and evidence records.
Guide to eIDAS Article 16 fine floors, national penalty rules, supervisory action, qualified-status withdrawal, and trusted-list evidence.
How to validate a qualified electronic signature under eIDAS: certificate, QTSP, trusted-list, QSCD, integrity, validation result, and evidence records.
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.
Source-grounded guide to eIDAS remote signature controls: remote QSCD scope, server-side signing, QTSP evidence, signer authentication, certificate validation, and trusted-list checks.
Compare eIDAS signature levels by legal effect, governing form rules, qualified certificate status, QTSP evidence, QSCD use, validation, and public-service recognition.
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.
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.
Compare eIDAS with ESIGN and UETA for electronic signatures, qualified certificates, trust services, cross-border recognition, validation evidence, and source gaps.
Compare eIDAS and ETSI EN 319 401 for trust services: legal scope, QTSP supervision, conformity assessment, audits, incident evidence, and operational controls.
Compare eIDAS identity, trust-service, and EUDI Wallet rules with GDPR duties for personal-data processing, minimisation, lawful basis, evidence, security, and user rights.
Compare eIDAS trust-service and QTSP duties with NIS2 cybersecurity risk-management, incident reporting, supervision, and evidence duties for trust service providers.
Official source 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.
An official source eIDAS scope test for QTSPs, trust services, electronic signatures, seals, timestamps, QWACs, EUDI Wallet relying parties, and cross-border recognition evidence.
Checklist for eIDAS trust-service and EUDI Wallet controls: qualified status, trusted lists, certificates, signatures, seals, timestamps, validation evidence, and relying-party records.
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.
How qualified trust service providers obtain and keep qualified status under eIDAS, including conformity assessment reports, supervision, trusted lists, incidents, and evidence.
Check a qualified trust service provider under eIDAS by validating trusted-list status, qualified service scope, certificates, policies, supervision, audits, and retained evidence.
Official source guide to core eIDAS requirements for trust service providers, qualified trust services, electronic signatures, seals, time stamps, trusted lists, and EUDI Wallet relying parties.
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.
Prepare an eIDAS wallet-relying-party registration, intended-use record, access-certificate controls, attribute request, validation evidence, and intermediary safeguards.
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.
Technical guide to the EUDI Wallet architecture: ARF roles, wallet units, PID and attestations, relying parties, trust model, certificates, protocols, privacy, and security controls.
A source-grounded guide to qualified website authentication certificates under eIDAS, covering Annex IV data, trusted lists, browser recognition, validation evidence, and QTSP checks.
A source-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 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.
How EU eIDAS Trusted Lists and the Commission LOTL support QTSP and qualified trust-service validation, with practical evidence checks for relying parties.
What EUDI Wallet relying parties must do under eIDAS, when the harmonised registration rules apply, and how to control requested data, identification, validation, and 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.
How to verify QTSP status under eIDAS using the qualified service, supervisory body decision, trusted list entry, conformity assessment evidence, and service-specific records.
Plain-language FAQ on qualified website authentication certificates under eIDAS, including website identity, QTSP trusted-list checks, browser recognition, and validation evidence.