Types of electronic signature: SES, AES and QES under eIDAS
Under EU law there is no single thing called «an electronic signature». The eIDAS Regulation defines three levels — simple, advanced and qualified — and each carries a different weight of identity assurance, evidence and cost. Pick a level that is too low for a risky document and you may struggle to prove who signed. Pick one that is too high and you add friction, cost and abandoned signature requests for no legal gain.
This guide explains what each level actually requires, quotes the articles that matter, compares the three side by side and offers practical guidance by document type — including what changes with eIDAS 2.0 and the European Digital Identity Wallet.
What eIDAS is and why one framework matters
eIDAS is shorthand for Regulation (EU) No 910/2014, the EU regulation on electronic identification and trust services. Because it is a regulation rather than a directive, it applies directly and identically in every member state: a signature level defined in Madrid means exactly the same in Munich or Milan. Before eIDAS each country had its own signature law and cross-border recognition was messy; since 2016 one framework covers the whole single market.
The regulation does two things that matter here. First, it defines the three signature levels covered below. Second, Article 25 establishes the non-discrimination principle: a court cannot dismiss a signature just for being electronic.
An electronic signature shall not be denied legal effect and admissibility as evidence in legal proceedings solely on the grounds that it is in an electronic form or that it does not meet the requirements for qualified electronic signatures.
Regulation (EU) No 910/2014, Article 25(1)
That principle is the floor all three levels stand on. The differences between them are about how strongly you can prove who signed and that nothing changed afterwards — not about whether the signature counts at all.
Simple electronic signature (SES)
Article 3(10) of eIDAS defines an electronic signature as data in electronic form which is attached to or logically associated with other data and which is used by the signatory to sign. That is the whole definition. Curiously, the regulation never uses the word «simple» — SES is industry shorthand for any signature that meets Article 3(10) without also meeting the stricter requirements of Article 26. Common examples:
- Typing your name at the end of an email or a contract
- Drawing a signature with your finger on a touchscreen
- Ticking an «I accept» box as part of an online flow
- Pasting a scanned image of your handwritten signature into a PDF
- Clicking to sign in a platform without additional identity checks
A SES is legally valid and perfectly adequate for a large share of everyday paperwork: internal approvals, low-value orders, consent forms, meeting minutes. If a dispute is unlikely and the amounts at stake are small, the convenience of one-click signing usually outweighs the thinner evidence.
Advanced electronic signature (AES)
An advanced electronic signature is defined in Article 3(11) as one that meets the four requirements of Article 26. All four must hold at once:
- It is uniquely linked to the signatory
- It is capable of identifying the signatory
- It is created using signature creation data that the signatory can, with a high level of confidence, use under their sole control
- It is linked to the signed data in such a way that any subsequent change in the data is detectable
In practice, signing platforms implement these requirements as a bundle of controls. Identity is linked to the signatory through the personal email address that receives the link, a one-time SMS code sent to their phone and, where needed, a document-based identity check (KYC). Sole control comes from those same factors: only the person holding the inbox and the phone can complete the signature. Integrity is handled cryptographically — the signed PDF is sealed so that any later edit, even a single character, is detectable — and a timestamp fixes the moment of signing. An audit trail then records every step: sent, opened, verified, signed, from which IP address and device.
If you want the cryptography behind that integrity guarantee — hashes, certificates and why a modified document breaks the seal — we cover it in electronic signature vs digital signature. For most teams the AES is the sweet spot: strong evidence without asking signers to install anything or obtain a certificate first.
Qualified electronic signature (QES)
A qualified electronic signature is an AES with two additions, per Article 3(12): it is created by a qualified signature creation device (QSCD) — certified hardware or a certified remote signing service — and it is based on a qualified certificate issued by a qualified trust service provider (QTSP) after formally verifying the signer's identity. QTSPs are audited and appear on public EU trust lists.
The reward is Article 25(2): a QES has the equivalent legal effect of a handwritten signature, and one issued in any member state is recognised in all the others. In practical terms it also reverses the burden of proof. In Spain, for example, if a document signed through a qualified service is challenged, Article 326.4 of the civil procedure law presumes it authentic and puts the cost of proving otherwise on the challenger.
That strength comes with real friction. The signer must hold a qualified certificate before signing, which means identity proofing with a QTSP — in person or by certified video — plus cost and renewals (in Spain, Ley 6/2020 caps qualified certificates at five years). Reserve QES for cases where a specific law demands it — certain public-sector procedures, some notarial and registry interactions, specific regulated filings — or for exceptionally high-value deals where you want the strongest possible position from day one.
SES, AES and QES at a glance
The table below condenses the differences. «Legal effect» is deliberately nuanced: all three levels are admissible; what changes is how much proving you have to do if someone denies having signed.
| Level | Identity assurance | Legal effect | Typical use | Signer effort |
|---|---|---|---|---|
| SES | Basic: email access, no dedicated checks | Valid and admissible (Art. 25(1)); proof rests on the surrounding trail | Internal approvals, consents, low-value orders | Minimal: click and sign |
| AES | Strong: SMS codes, optional ID verification, cryptographic link | Valid and admissible; robust evidence package if challenged | Commercial contracts, HR documents, sales agreements | Low: one extra verification step |
| QES | Highest: qualified certificate after formal identity proofing | Equivalent to a handwritten signature (Art. 25(2)); burden of proof shifts to the challenger | Legally mandated procedures, very high-value deals | High: requires a certificate and a QSCD |
Which level do you actually need
The right question is not «which level is strongest» but «what does this document legally require, and how likely is a dispute». Matching level to risk keeps completion rates high and costs low. Some common cases:
- NDAs and internal approvals — SES is usually enough. Disputes are rare and the relationship with the counterparty is ongoing. Choose AES if the confidential material is genuinely sensitive.
- HR documents — employment contracts, policy acknowledgements and disciplinary notices are exactly where people later dispute having signed. AES with SMS verification is the sensible default.
- Sales and service contracts — AES. The identity link and the tamper seal are what you will lean on if an invoice goes unpaid and the customer denies the agreement.
- Residential rentals — in Spain a rental contract needs no special form, so AES is legally sufficient; strong identity evidence matters because landlord and tenant often meet only once.
- Public-sector and regulated filings — check the specific rule. Where a statute names a qualified signature or a certificate, only QES will do.
The honest summary: most everyday business documents are perfectly served by SES or AES, and forcing QES on them mostly produces abandoned signature requests. For the legal detail on validity and evidence, see our legal validity page; if you are comparing tools, how to choose electronic signature software walks through the criteria.
eIDAS 2.0 and the EUDI Wallet
Regulation (EU) 2024/1183, adopted on 11 April 2024 and in force since 20 May 2024, amends eIDAS to create the European Digital Identity framework. Its centrepiece is the EUDI Wallet: every member state must offer at least one wallet, free of charge, within 24 months of the key implementing acts taking effect. Those acts entered into force on 24 December 2024, which puts the member state deadline at the end of 2026.
For signatures, two changes stand out. Wallet holders will be able to create qualified electronic signatures, and the regulation requires QES to be free of charge for natural persons for non-professional purposes. Over time that should lower the cost and friction that make QES rare today. Businesses in sectors required to use strong authentication — banking, energy, telecoms and others — must accept the wallet from late 2027.
As of mid-2026 the rollout is uneven. Denmark launched its production wallet in June 2026, Germany opened a public sandbox with its state wallet expected in 2027, and Spain's Cartera Digital remains an announced project. The direction is clear but the timeline is gradual: for the next few years, SES and AES remain the workhorses of business signing.
How Signatuz fits in
Signatuz supports simple and advanced signatures, and puts its weight on the part that decides real disputes: evidence. Every completed document ships as a sealed PDF with a timestamp (RFC 3161 where available in the configured flow), IP and device capture, a complete audit trail and a signature certificate. Identity verification can be layered to match risk — email access by default, one-time SMS codes, and optional KYC identity verification for documents that warrant it. Signers need no account and no app; they sign from a secure link on any device.
To be equally clear about what we do not do: Signatuz is not a qualified trust service provider and does not offer qualified signatures. If a specific procedure requires QES, you will need a QTSP for that document. For everything else — which in our experience is most of a company's paperwork — SES and AES with a strong evidence trail are what the situation actually calls for. You can see how the signing flow works on our electronic signature page and the legal detail on validity and evidence. The Free plan includes 100 documents and 10 SMS validations, with no credit card required.
Frequently asked questions
What is the difference between a simple and an advanced electronic signature?
A simple signature only needs to show intent to sign — a typed name or a click is enough. An advanced signature must also meet the four Article 26 requirements: unique link to the signatory, capability of identifying them, sole control of the signature data, and detectability of any later change to the document. In practice, AES means identity verification plus a cryptographically sealed document.
Is a scanned image of my handwritten signature legally valid?
Yes — it qualifies as a simple electronic signature under Article 3(10) and cannot be rejected just for being electronic. The problem is proof, not validity: anyone can copy an image, so on its own it says very little about who actually placed it. If the document matters, use a platform that records who received and opened the signing link.
Do ordinary contracts require a qualified signature?
Generally no. In most EU jurisdictions, including Spain, contracts are valid whatever their form, so SES or AES is legally sufficient for ordinary commercial agreements. QES is required only where a specific law says so — typically certain public-sector, notarial or registry procedures — or chosen voluntarily for the reversed burden of proof.
What happens if an electronic signature is challenged in court?
It is admissible as documentary evidence, and the court weighs the evidence package: how the signer was identified, whether the document stayed intact, and what the audit trail shows about the process. In Spain, non-qualified signatures are assessed under Article 326.3 of the civil procedure law; qualified ones enjoy a presumption of authenticity under Article 326.4, with verification costs falling on an unsuccessful challenger.
Will the EUDI Wallet replace e-signature platforms?
Unlikely. The wallet solves identity and gives citizens free qualified signing for personal use, but businesses still need everything around the signature: templates, workflows, reminders, evidence storage, an API. The likelier outcome is that platforms adopt the wallet as one more identity and signature method.
