What is an advanced electronic signature (AES)?
Rezvan Golestaneh
Updated · Published · 9 min read

Key takeaways
- An AES is the middle of the three EU signature levels: stronger than a simple signature, below a qualified one.
- It must be uniquely linked to the signer, identify them, be under their sole control and show any later change (Art. 26 eIDAS).
- Typical ways to sign: a one-time code sent to your phone, or a national eID such as BankID or MitID.
- It is legally binding for most contracts, but it does not replace a handwritten signature where the law requires written form.
What is an advanced electronic signature (AES)?
An advanced electronic signature (AES, sometimes AdES) is an electronic signature that meets four extra requirements set out in Article 26 of the eIDAS Regulation: it is uniquely linked to the signer, it can identify the signer, it is created with means the signer controls, and it is bound to the document so that any later change is detectable.
In practice, this means an AES proves two things a simple electronic signature (SES) cannot prove on its own: who signed and that the document has not changed since.
You have probably used one already. A typical example: you receive an NDA by email, sign it in an eSignature tool and confirm the signature with a one-time code sent to your phone by SMS. Signing with a national digital ID such as Swedish BankID or Danish MitID is another common example.
It sits between a simple signature, which needs no identity check, and a qualified electronic signature (QES), which is the only one equal to a handwritten signature.
eIDAS 2.0 (Regulation (EU) 2024/1183, in force since 20 May 2024) left the AES requirements unchanged. Switzerland has a similar “fortgeschrittene elektronische Signatur” in its ZertES, while US law (ESIGN Act and UETA) has no signature levels, so whether an electronic signature is legally binding depends on the country.
In the UK, the Electronic Communications Act 2000 makes electronic signatures admissible in court, and UK law rarely asks for a particular level. An AES there is mainly useful as stronger evidence of who signed.
The four requirements of an AES (Article 26 eIDAS)
For an electronic signature to count as advanced, it has to meet all four of the following requirements.
| Requirement (Art. 26 eIDAS) | What it means in plain language | Example |
|---|---|---|
| (a) Uniquely linked to the signatory | The signature belongs to exactly one person and cannot be attributed to anyone else. | The confirmation code goes to the signer’s own mobile number, or the signature uses a key in a certificate issued to that one person. |
| (b) Capable of identifying the signatory | The signature carries or points to evidence of who signed. | The verified phone number, an eID login such as BankID, or the name in the signer’s certificate is recorded with the signature. |
| (c) Created using signature creation data the signatory can, with a high level of confidence, use under their sole control | Only the signer can trigger the signature. | A one-time code on the signer’s phone, an eID app protected by a PIN or biometrics, or a private key on a smart card. |
| (d) Linked to the signed data so that any subsequent change is detectable | The signature is bound to this exact version of the document. | If a single word is changed after signing, validation shows that the document was modified. |
A drawn or typed signature alone meets none of these requirements, which is why it stays an SES. The identity check and the technical binding to the document are what make a signature advanced.
How an AES works
Most AES use public key cryptography: the signer’s private key seals a fingerprint (hash) of the exact document, and a certificate or the platform’s audit trail ties that key to the verified signer. Change one character after signing and verification fails. A trusted timestamp keeps the signature verifiable after the certificate expires.
AdES based on a qualified certificate
Between AES and QES sits a variant you will see in validation reports: an advanced electronic signature based on a qualified certificate (often shown as AdES/QC). The signer has a qualified certificate from a qualified trust service provider, but the signature was not created on a qualified signature creation device. Legally it is still an AES, not a QES, so it does not meet written form. Some public authorities accept it for filings where they ask for “at least an advanced signature with a qualified certificate”.
How to get an advanced electronic signature
You don’t need special hardware for an AES. There are three common ways to create one:
- Through an eSignature platform with phone verification. The signer opens the document from an email link, signs and confirms with a one-time code sent to their phone. This is the most common route for business contracts.
- With a national eID. In several countries, people already have a verified digital ID, for example BankID and Freja eID in Sweden, BankID in Norway, MitID in Denmark or SPID in Italy. Signing with it links the signature to a strongly verified identity.
- With a certificate-based digital ID. In Adobe Acrobat you can sign a PDF with “Use a certificate” and a digital ID. Whether the result counts as an AES depends on the digital ID: a self-created one protects the document against changes but says little about who you are. A digital ID issued by a trust service provider after an identity check also meets the identification requirement.
Send documents for advanced signature for free.
Advanced electronic signatures in fynk
Advanced signatures in fynk are included in every plan, the Free plan too:
- Sign in to fynk and drag and drop your document.
- Choose Advanced (AES) as the signature type and click Start signing.
- Signers confirm with a code sent to their phone by SMS or WhatsApp. They need no fynk account.


To let signers use a national eID instead, switch on Advanced with eID once in the account settings. The signer then picks their eID while signing. If they choose a qualified method, the signed document is marked QES. Every step is recorded in the audit trail.
You can clearly see who is getting reminders to sign the contract, who has signed the contract, who is next. You have documentation of activities around the tool.

These eID methods are available for advanced signatures in fynk, each with its own page in the signature method directory:
| Method | Available in |
|---|---|
| Czech Bank iD | Czechia |
| Danish MitID (Intesi) | Denmark |
| Finnish Trust Network (Intesi) | Finland |
| Freja eID Sign | Sweden |
| Italian SPID (Intesi) | Italy |
| Norwegian BankID (Intesi) | Norway |
| Swedish BankID (Intesi) | Sweden |
How to verify an advanced electronic signature
How you check an AES depends on how it was created:
- Certificate-based signatures in a PDF: open the file in Adobe Acrobat or Acrobat Reader. It shows whether the signature is valid, who the certificate was issued to and by whom, when the document was signed, and whether it was changed after signing.
- Any PAdES, XAdES or CAdES signature: upload the file to the European Commission’s free DSS validation tool. It reports whether the signature is intact and which level (AdES or QES) it reaches.
- Platform-based signatures: check the audit trail or signing certificate the platform attaches to the completed document. It lists the signers, how each one was verified, and timestamps for every step.
A valid result means the document is exactly what was signed. A warning such as “document has been modified” means the content changed after signing and the signature no longer covers it.
Advanced vs qualified electronic signature (AES vs QES)
Both are cryptographically secure, so the difference is mainly legal. A QES requires a qualified certificate from a qualified trust service provider and a qualified signature creation device, and in return it has the legal effect of a handwritten signature in every EU member state. An AES does not.
| Advanced electronic signature (AES) | Qualified electronic signature (QES) | |
|---|---|---|
| Legal basis | Art. 3(11) and Art. 26 eIDAS | Art. 3(12) and Art. 25(2) eIDAS |
| Identity check | Varies: phone code, eID, certificate | Mandatory, by a qualified trust service provider (video ident, eID, in person) |
| Certificate | Not required (common in practice) | Qualified certificate required |
| Signature device | Any device | Qualified signature creation device (today mostly a remote service run by the provider) |
| Legal effect | Admissible as evidence, cannot be rejected for being electronic (Art. 25(1)) | Equivalent to a handwritten signature (Art. 25(2)), recognised in all EU member states (Art. 25(3)) |
| Meets a statutory written-form requirement | No | Yes, unless national law excludes the electronic form |
| Typical use | Most B2B contracts, NDAs, HR documents without form requirements | Contracts that require written form by law |
Which signature for which document?
Most contracts have no form requirement, so an AES is enough. You need a QES only where national law requires written form. Examples from German law, as of October 2026:
| Document | Signature to use |
|---|---|
| NDA, B2B sales, service or SaaS contract | AES (SES is valid too) |
| Commercial lease for more than one year | AES (text form since 2025) |
| Fixed-term employment contract | QES or wet ink (§ 14(4) TzBfG) |
| Termination of employment | Wet ink only (§ 623 BGB) |
Is an advanced electronic signature legally binding?
Yes. Under Article 25(1) of eIDAS, no electronic signature, including an AES, may be denied legal effect or rejected as evidence just because it is electronic or not qualified:
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.
That makes an AES binding for every contract that has no form requirement. It is not, however, equivalent to a handwritten signature: that status is reserved for the QES (Article 25(2)). In a dispute, a court weighs the AES evidence freely. In Germany, for example, the presumption of authenticity for electronic documents in § 371a ZPO applies only to qualified signatures. This is why the identity evidence and audit trail behind an AES matter.
Benefits and limits of advanced electronic signatures
Benefits:
- Fast: signing takes minutes, with no printing, scanning or posting.
- Identity evidence: you can show who signed and how they were verified.
- Tamper detection: any change after signing is visible on verification.
- No extra hardware: a phone or an existing eID is enough.
Limits:
- An AES does not satisfy a statutory written-form requirement. For those documents you need a QES or wet ink.
- Outside the EU, how much weight an AES carries depends on local law. In the US and UK, the general rules on electronic signatures apply rather than eIDAS levels.
Searching for a contract management solution?
Find out how fynk can help you close deals faster and simplify your eSigning process – request a demo to see it in action.
Frequently asked questions
You do not need to buy anything special. You can sign with an eSignature platform that verifies you with a one-time code sent to your phone, sign with a national eID such as BankID or MitID, or sign a PDF with a digital ID issued by a trust service provider.
No. Article 26 eIDAS is technology neutral and does not require a certificate. Most AES still use certificates and public key cryptography, while some platforms verify signers by phone code or eID and seal the document instead.
The AES level is defined by eIDAS, UK eIDAS and the Swiss ZertES. Other countries, such as the US, do not use signature levels, but generally accept electronic signatures as evidence. Whether a specific document can be signed electronically always depends on the law that governs it.
It can be. A signature confirmed with a one-time code sent to the signer's own phone is uniquely linked to that person and under their sole control. Together with a sealed document that shows any later change, this meets the AES requirements of Article 26 eIDAS. A code alone, without the document seal and a record of the verification, is not enough.
Please keep in mind that none of the content on our blog should be considered legal advice. We understand the complexities and nuances of legal matters, and as much as we strive to ensure our information is accurate and useful, it cannot replace the personalized advice of a qualified legal professional.
Get a regular dose of insightful contract management content
Take control of your agreements. Move your business forward.
Run agreements the way they should run: fast, clear, and on your terms.
No setup headaches
Go live in days, not quarters
No lock-in
Full export anytime
No hidden fees
Signatures included, no envelope fee
