The short answer: electronic signatures are legally recognised
Electronic signatures are legally recognised across the European Union under the eIDAS framework. The practical answer is not that every electronic mark is automatically equal. It is that EU law creates a ladder of assurance, protects electronic evidence from automatic discrimination and gives the highest rung—qualified electronic signatures—the same legal effect as handwriting throughout the Union.
Start by separating three questions that are often collapsed. Did this person intend to sign? Can the recipient prove who signed and that the document was not altered? Does the transaction require a particular form under national or sector law? A signature platform can help answer the first two, but it cannot silently repeal a rule requiring a notary, a specific public portal, a witness, registration or another formality.
Simple, advanced and qualified signatures
A simple electronic signature is the broadest category: electronic data attached to or logically associated with other electronic data and used by a natural person to sign. A typed name, tick-box acceptance, drawn mark or ordinary click-to-sign flow can fit, depending on the facts. Its strength comes from the complete evidence around it—account control, authentication, consent screen, document version, timestamps, IP or device records and the provider's audit trail—not from a decorative image of handwriting.
An advanced electronic signature adds four eIDAS requirements. It must be uniquely linked to the signatory, capable of identifying that person, created using signature-creation data under the signatory's control with a high level of confidence, and linked to the signed data so a later change is detectable. Cryptographic signatures built around a certificate are the normal technical route, but the legal test concerns those properties rather than one brand or one file format.
A qualified electronic signature is an advanced signature created with a qualified signature-creation device and based on a qualified certificate for electronic signatures. The certificate links the validation data to a named or pseudonymous natural person; the secure device can be a card, token, certified local component or a remotely managed device operated by a qualified trust service provider. The combination—not the marketing label 'digital signature' by itself—creates QES status.
Legal effect and cross-border recognition
The legal effects are deliberately asymmetric. No electronic signature—simple, advanced or qualified—may be denied legal effect or admissibility as evidence solely because it is electronic or because it is not qualified. Only QES receives the automatic EU-wide equivalence to a handwritten signature. A simple or advanced signature can still form a valid contract and strong evidence; the party relying on it may simply need to prove more if identity, consent or integrity is disputed.
Cross-border recognition is one of Europe's most useful achievements. A qualified signature based on a qualified certificate issued in one member state must be recognised as qualified in every other member state. For public-sector online services, eIDAS also sets recognition duties for supported advanced and qualified formats. A recipient should not demand that an Estonian, Spanish or Belgian QES be re-created through a domestic provider merely because the provider is foreign.
Trusted lists and proper validation
Qualification is a regulated status, not a logo. EU countries supervise qualified trust service providers and publish national trusted lists; the Commission provides a common browser and machine-readable list of those lists. A provider and a specific service receive the special qualified status only when the service appears there as qualified. Check the exact certificate-issuing service and its status at the signing time rather than assuming every product sold by a listed company is qualified.
Validation means more than opening a PDF and seeing a green tick. A relying party should verify the signed bytes, certificate chain, qualified status, certificate validity and revocation information, signatory identity, signing policy and any trusted timestamp. The Commission's open-source Digital Signature Services tools explain and implement these checks, but a demonstration site or screenshot should not replace a preserved validation report from an appropriate service or system.
Preserve the original evidence
File handling can destroy useful evidence. Keep the original signed container or PDF, not only a printout, screenshot or exported copy. Do not merge, flatten, redact, re-save or convert it before preserving the original. If long-term reliance matters, use appropriate timestamping and preservation so the signature can still be assessed after a certificate expires, algorithms change or online revocation records disappear. A printed signature panel does not carry the cryptographic proof inside the file.
Signatures, seals and authority are different
An electronic seal answers a related but different question. A signature is created by a natural person and can express that person's intent; a seal is created by a legal person and supports the origin and integrity of data. A qualified seal enjoys presumptions about integrity and origin, but it does not automatically prove that a particular director approved a contract. Check whether the process needs a person's signature, an organisation's seal, or both.
The required level should follow the real risk and the governing rule. Routine low-risk transactions may be well served by a simple flow with good authentication and records. Employment, banking, public filing or high-value agreements may justify advanced or qualified assurance, while national law can require particular formalities for specific acts. eIDAS does not fully harmonise every contract's substantive validity, capacity, representation, witness rule or registration requirement.
Authority is separate from identity. A technically valid QES can establish who signed and protect document integrity, but it does not necessarily prove that the person had authority to bind a company, administer an estate or act for another individual. Check the register, mandate, power of attorney, role, transaction limit and date when representation matters. Conversely, an authorised person can still choose a weak signing process that creates avoidable evidence risk.
What to do when a signature is refused
If a recipient rejects a signature from another member state, ask for the refusal and legal basis in writing. Supply the original file, validation report, certificate details, trusted-list entry and evidence of the signer's authority. Separate a technical failure from a form requirement: an unsupported file reader, missing intermediate certificate or stale trusted-list cache is not the same as a law requiring a different procedure. For a public service, use its help desk and national supervisory or administrative remedy; for a private dispute, obtain advice under the governing contract law.
Third-country signatures require extra care. eIDAS can recognise qualified trust services from outside the EU through the framework's international-recognition mechanisms, but an ordinary foreign provider does not become an EU qualified provider merely because it uses similar cryptography. The signature may still be admissible and persuasive as an advanced or other electronic signature. Check the applicable agreement, trusted status and contract rather than upgrading it by analogy.
Security and the 2026 wallet transition
Security failures are not cured by the word qualified. Confirm the document through a known channel when money, bank details or ownership changes; protect signing credentials and recovery methods; read the final document; and stop if the signing request arrives through an unexpected message. If credentials may be compromised, notify the provider quickly so certificates or devices can be suspended or revoked, preserve evidence and tell the relying party before further action.
The revised European Digital Identity framework is designed to make QES easier to use through national EU Digital Identity Wallets, including free qualified signing for natural persons at least for non-professional purposes. On 14 October 2026, the Commission's official material still described national wallet systems as being tested ahead of launch and broadly due by the end of 2026. Treat a demo, pilot or announced wallet as available only when the responsible national authority confirms production access and the relying service accepts it.
A European trust layer for a shared digital home
Europe's common trust framework is already useful before the wallet transition finishes. It lets a person choose a supervised provider in one country, lets a recipient validate against shared trust anchors and gives QES a portable legal effect across twenty-seven legal systems. A more federal digital Europe should make validation reports, public-service acceptance and long-term preservation as ordinary as reading the document itself—while keeping national form rules visible instead of hiding them behind a signature button.