Qualified Electronic Seal vs Electronic Signature: Which Does Your Business Need? (2026)
Under eIDAS, qualified electronic seals (Art. 35) authenticate legal entities (companies, institutions, automated systems), while qualified electronic signatures (Art. 26/27) authenticate individuals. For IP ownership and batch document workflows, the seal offers stronger organisational authorship proof. This guide explains the legal basis, use cases, and how to obtain either via Swiss Trust Layer from CHF 5/document.
In November 2024, a Geneva-based creative agency delivered a 60-page brand identity system to a fintech startup. The deliverables included logo files, a complete UI component library, and a motion design guide. The contract had been agreed verbally, with a written version sent but never countersigned. Six weeks after delivery, the startup's newly hired design director began presenting the work as internally developed. The agency had timestamped nothing. The startup's legal team had one question: prove you made it first. The agency could not. The resulting IP dispute cost the agency CHF 340,000 in legal fees and three months of management time, for work originally billed at CHF 45,000.
That gap between creation and proof is exactly what the eIDAS qualified electronic seal closes. Understanding whether your business needs a seal or a signature determines whether your IP records hold up in court.
What Is the Difference Between a Qualified Electronic Seal and a Qualified Electronic Signature?
A qualified electronic seal (eIDAS Art. 35) is issued to a legal entity (a company, institution, or government body) and carries the legal presumption that the sealed document originated from that entity and has not been altered since sealing. A qualified electronic signature (eIDAS Art. 26/27) is issued to a natural person and is legally equivalent to a handwritten signature, proving that a specific individual approved the document. The key distinction: seals authenticate organisational origin; signatures authenticate personal approval.
What Is a Qualified Electronic Seal? (eIDAS Art. 35/36)
eIDAS Art. 35 defines a qualified electronic seal as an advanced electronic seal created by a qualified electronic seal creation device and based on a qualified certificate for electronic seal issued by an EU Trust List Qualified Trust Service Provider (QTSP). eIDAS Art. 36 provides the legal presumption: a qualified electronic seal carries the presumption of integrity of the data and correctness of the origin of that data as attributed to the legal person associated with it.
Key characteristics of qualified electronic seals:
- Subject: Legal entities (companies, institutions, automated systems), not natural persons
- Purpose: Origin authentication and integrity proof for organisational documents
- Use cases: Batch invoice sealing, automated contract issuance, machine-generated certificates, IP ownership records, API-delivered documents
- Issuer: A QTSP listed on an EU Member State's Trust List under eIDAS, or a ZertES-accredited authority in Switzerland
- Legal effect: Documents sealed with a qualified seal carry the presumption that they originated from the named legal entity and were not altered after sealing. This is admissible across all 27 EU member states
In Switzerland, an equivalent framework is provided by ZertES SR 943.03, which governs qualified certificates for legal entities under Swiss law, issued by BAKOM-accredited providers such as Swisscom Trust Services.
What Is a Qualified Electronic Signature? (eIDAS Art. 26/27)
eIDAS Art. 26 defines the requirements for a qualified electronic signature: it must be created by a qualified electronic signature creation device and based on a qualified certificate for electronic signatures. eIDAS Art. 27 states that a qualified electronic signature shall have the equivalent legal effect of a handwritten signature.
Key characteristics of qualified electronic signatures:
- Subject: Natural persons (individual employees, directors, lawyers, authors)
- Purpose: Personal approval, consent, and individual legal commitment
- Use cases: Contracts requiring individual authorisation, employment agreements, legal filings, director approvals, IP assignment agreements
- Issuer: A QTSP issuing qualified certificates to verified individuals (eIDAS) or a ZertES-accredited authority issuing regulated certificates to natural persons
- Legal effect: Legally equivalent to a handwritten signature across all 27 EU member states; rebuttably presumed to be attributable to the identified signatory
Side-by-Side Comparison
| Feature | Qualified Electronic Seal | Qualified Electronic Signature |
|---|---|---|
| Subject | Legal entity (organisation) | Natural person (individual) |
| eIDAS article | Art. 35/36 | Art. 26/27 |
| Legal presumption | Origin + integrity (entity) | Equivalent to handwritten signature |
| Who issues | QTSP (EU Trust List or ZertES) | QTSP (to verified individuals) |
| Best use case | Batch sealing, IP records, automated docs | Contracts, approvals, personal consent |
| Swiss equivalent | ZertES SR 943.03 qualified certificate (entity) | ZertES SR 943.03 qualified certificate (person) |
| STL support | Yes, available on all plans | Yes, via co-signing workflow |
What Would Have Happened Differently
If the Geneva agency had applied a qualified electronic seal under eIDAS Art. 35 to each deliverable at the moment of creation, the outcome would have been different at the first legal challenge. The sealed certificate would have carried the presumption under Art. 36 that the files originated from the agency's legal entity and had not been altered since sealing. The timestamp, issued by a QTSP via RFC 3161, would have fixed the creation date to within seconds of upload. The startup's lawyers would have faced a burden-of-proof reversal: they would have needed to disprove the seal, not the agency to prove authorship. In practice, most IP disputes settle at that point. The agency's CHF 340,000 exposure would have been a CHF 5 document seal.
Which Is Better for IP Ownership? Seals Win for Organisations
For intellectual property ownership proof, the qualified electronic seal is the stronger instrument for organisational authorship. Here is why:
- Organisational authorship is the norm in IP. In most corporate IP contexts, such as software code, design files, technical documentation, and research outputs, the legal author is the company, not an individual. A seal ties the document to the legal entity as a whole, which is what courts and IP registries examine when resolving ownership disputes.
- Seals are automation-friendly. Companies that seal hundreds of documents per day, such as API logs, version-controlled source files, and design releases, need batch sealing without requiring an individual to personally approve each one. Qualified electronic seals support fully automated workflows; individual signatures require each natural person to authenticate per document.
- Seals survive employee departure. If the individual who signed a document leaves the company, linking IP ownership to that person's signature creates legal ambiguity. A seal is permanently linked to the legal entity, which continues regardless of staff changes.
- Seals carry equivalent legal presumption for integrity. Under eIDAS Art. 36, the presumption of data integrity and origin is attached to the legal entity, which is exactly what an IP dispute examiner needs to see.
Individual qualified signatures remain the right tool when a specific person's approval matters: a director signing a contract, an inventor assigning rights, or a lawyer certifying a filing.
How to Obtain a Qualified Electronic Seal or Signature via Swiss Trust Layer
Swiss Trust Layer provides access to both instruments through its QTSP integration with Swisscom Trust Services, a BAKOM-accredited provider recognised under both ZertES SR 943.03 and eIDAS technical standards:
- Choose your document type at swisstrustlayer.com/pricing: individual documents or batch workflows
- Upload your file: only the SHA-256 hash is transmitted, and the document never leaves your environment
- Apply the qualified seal or timestamp: Swisscom Trust Services applies the RFC 3161-compliant qualified timestamp, embedding the seal credential within seconds
- Download the sealed certificate: the PAdES-format PDF contains the seal, timestamp, and QTSP attestation, ready for legal proceedings or IP registry submission
- Verify publicly: any third party can validate the seal at verify.swisstrustlayer.com without creating an account
Sealing starts at CHF 5 per document. For high-volume or API-based batch sealing, contact the Swiss Trust Layer team for an enterprise plan.
For the Geneva agency in our opening, the math is straightforward: CHF 5 per deliverable sealed at creation versus CHF 340,000 in dispute costs. The average EU IP infringement case costs EUR 250,000 to EUR 1.2 million (EUIPO, 2023). A qualified electronic seal under eIDAS Art. 35/36 is not an administrative step. It is the document that ends the argument before it starts.
This article is for informational purposes only and does not constitute legal advice. Consult qualified legal counsel for advice specific to your jurisdiction and circumstances.
Protect your work with Swiss Trust Layer AG
Seal your intellectual property with a court-proof e-Seal backed by Swisscom Trust Services.
Book a Free DemoRelated Articles
The qualified signature workflow, start to finish
A qualified electronic signature involves identity verification, signing ceremony, PAdES application, RFC 3161 timestamping, and public verification. Each step serves a specific legal purpose. This is what the process looks like from upload to verified certificate.
5 documents Swiss businesses should never sign with a basic e-signature
Swiss law specifies document types where only a qualified electronic signature carries the legal weight of a handwritten signature. Using a simple or advanced e-signature on these documents creates an enforceable gap that surfaces in disputes. Here are the five categories that matter.
DocuSign vs SealMyIdea: where a visual signature isn't enough
DocuSign provides advanced and simple electronic signatures. For real estate, IP transfers, fiduciary mandates, and employment contracts in Switzerland, only a qualified electronic signature under ZertES Art. 11 carries legal presumption. This is the gap DocuSign cannot close.
For agencies: prove you authored the work and get clean client sign-off
Creative and digital agencies lose IP disputes because they cannot prove creation date or obtain legally binding client acceptance. A qualified electronic signature for client sign-off, combined with timestamped delivery, creates the complete audit trail that courts recognise.
Blockchain proves a file existed. It doesn't prove a court will accept it.
A blockchain timestamp records that a file existed at a point in time. It carries no legal presumption under eIDAS or ZertES. A qualified electronic timestamp issued by an accredited QTSP does.