---
title: "What is an advanced electronic signature (AES)?"
description: "An advanced electronic signature (AES) is the middle eIDAS level. See its four requirements, how it differs from SES and QES, and where SignatureAPI fits."
canonical: "https://signatureapi.com/docs/glossary/advanced-electronic-signature"
source: "https://signatureapi.com/docs/glossary/advanced-electronic-signature.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T13:06:40Z"
---

# What is an advanced electronic signature (AES)?

An advanced electronic signature (AES) is the middle eIDAS level. See its four requirements, how it differs from SES and QES, and where SignatureAPI fits.

_Last verified against API version 1.18.0._

An **advanced electronic signature** (AES, also written AdES) is the middle of the three levels of electronic signature that **eIDAS**, the EU regulation on electronic identification and trust services ([Regulation (EU) No 910/2014](https://eur-lex.europa.eu/eli/reg/2014/910/oj)), defines.

## The four requirements

Article 26 of eIDAS lists what makes a signature advanced. It must be:

1. **Uniquely linked to the signer.**
2. **Capable of identifying the signer.**
3. **Created with signature creation data that the signer can use, with a high level of confidence, under their sole control.** In practice this means a private key that only the signer can use.
4. **Linked to the signed data so that any later change is detectable.** In practice this means a digital signature over a [hash](https://signatureapi.com/docs/glossary/document-hash) of the document.

## Where it sits

| Level               | What it is                                                                                                                                                                                                      |
| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Simple** (SES)    | Any electronic data a person uses to sign: a typed name, a drawn signature, a click.                                                                                                                            |
| **Advanced** (AES)  | Meets the four requirements above.                                                                                                                                                                              |
| **Qualified** (QES) | An advanced signature made with a qualified certificate and a qualified signature creation device. See [Qualified electronic signature](https://signatureapi.com/docs/glossary/qualified-electronic-signature). |

Each level adds requirements to the one before it. Only the qualified level has a fixed legal effect across the EU: the same as a handwritten signature. For simple and advanced signatures, eIDAS says a court can't reject them only because they're electronic or not qualified. How much weight they carry is up to the court and the evidence.

## SignatureAPI and AES

SignatureAPI produces two of the three levels:

- **Simple electronic signatures**, for every recipient type except qualified signers. The signer's identity is recorded through the ceremony's [authentication](https://signatureapi.com/docs/api/resources/ceremonies/authentication/overview), and the [audit trail](https://signatureapi.com/docs/glossary/audit-trail) records each step.
- **Qualified electronic signatures**, through a [qualified signer](https://signatureapi.com/docs/api/resources/recipients/qualified-signer) and the qualified trust service provider you choose. Qualified signatures are in public beta.

SignatureAPI doesn't produce advanced electronic signatures. If a document needs more than a simple signature, the qualified level covers every requirement of the advanced one.

**The eIDAS signature levels SignatureAPI produces**

|  | Simple (SES) | Qualified (QES) |
|---|---|---|
| [What it is](https://signatureapi.com/docs/qualified-signatures) | Any electronic data a person uses to sign: a typed name, a drawn signature, a click | An advanced signature made with a qualified certificate, from a provider that verified the signer's identity |
| Legal effect in the EU | A court can't reject it only because it's electronic or not qualified | The same legal effect as a handwritten signature in every EU member state |
| [SignatureAPI recipient type](https://signatureapi.com/docs/api/resources/recipients/object) | `signer` and every other type except `qualified_signer` | `qualified_signer` |
| Signer identity | Recorded by the ceremony's authentication | Verified by the QTSP |
| Signing certificate issued to the signer | No | Yes |
| Routing | Sequential or parallel | Sequential only |
| Deliverable | Configurable | One PDF with every document, no audit log |
| [Availability](https://signatureapi.com/docs/qualified-signatures/quickstart) | Every account | Public beta, bring your own QTSP |

- SignatureAPI operates at the SES level for all recipient types except qualified signers.
- SignatureAPI doesn't produce advanced electronic signatures (AdES). An AdES is uniquely linked to the signer and identifies them, is made with signing data under their sole control, and shows any later change to the document.
- A simple electronic signature covers most business documents. Ask your legal counsel which level each document needs.

> **Note:** This page explains terms. It is not legal advice. Ask your legal counsel which level each document needs.

## Related

- [Are electronic signatures legal?](https://signatureapi.com/docs/legal-validity/overview): ESIGN, UETA and eIDAS.
- [What are qualified signatures?](https://signatureapi.com/docs/qualified-signatures): when you need a QES, and how to request access.
- [Glossary](https://signatureapi.com/docs/glossary): other terms.
