Skip to main content
5 documents Swiss businesses should never sign with a basic e-signature
Legal

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.

S
Swiss Trust Layer Editorial Team· Swiss Legal Compliance
·July 18, 2026·Last updated July 18, 2026· 8 min read
5 documents Swiss businesses should never sign with a basic e-signature — Swiss Trust Layer

Most electronic signatures are legally effective for most documents. NDAs, supplier agreements, consultancy contracts, internal approvals: an advanced electronic signature (AES) or even a simple click-to-sign is sufficient for the vast majority of routine business documents in Switzerland.

But Swiss law contains specific provisions that require written form, and under ZertES Art. 11, only a qualified electronic signature (QES) is the electronic equivalent of that written form. Using a basic signature on these documents does not make them illegal, but it can make them challengeable in ways that expose the signing parties to real risk.

Here are five categories of documents where Swiss businesses should default to QES.

1. Employment contracts with non-compete clauses

A non-compete clause binds an employee after their employment ends, restricting where they can work and for whom. Under Art. 340a of the Swiss Code of Obligations (OR), a non-compete clause is only valid if it is recorded in writing and the employer has a legitimate interest that justifies the restriction.

An AES does not satisfy the written form requirement under Swiss law in all circumstances. If a departing employee challenges the non-compete, and the underlying contract uses AES rather than QES, the enforceability of the clause becomes a live question. A QES eliminates that question: under ZertES Art. 11, it is the written form equivalent, and the challenge cannot be sustained on signature grounds alone.

2. IP transfer and assignment agreements

In Switzerland, copyright in creative and technical works belongs to the author by default under the Federal Act on Copyright (URG). An IP transfer agreement moves that right to another party, such as a client or employer. The legal effect of that transfer depends on the agreement being enforceable.

Where the value of the IP is material, or where the transfer is between parties in different countries, a QES provides the strongest foundation for enforceability. The signature carries legal presumption. A challenge to the transfer cannot be sustained simply by questioning whether the agreement was properly executed.

3. Real estate and lease agreements requiring written form

Under Art. 216 of the Swiss Civil Code (ZGB), contracts for the transfer of ownership of real estate require public notarisation. Commercial lease agreements of significant value, and certain pledge agreements, require written form. For documents in these categories that are executed electronically without notarisation, QES is the appropriate signature tier.

4. Fiduciary mandate agreements and declarations of trust

Swiss fiduciaries manage significant assets and liabilities on behalf of clients. A fiduciary mandate agreement establishes the scope of authority, the obligations of each party, and the conditions under which the mandate can be terminated. These agreements carry substantial legal and financial exposure.

For fiduciary mandates, QES provides the legal foundation that protects both parties. If the client later disputes what was agreed, or if the scope of authority is challenged in a regulatory proceeding, a QES-signed mandate agreement carries presumptive legal weight. A basic AES does not.

5. Cross-border data processing agreements with liability clauses

Switzerland's revised Federal Act on Data Protection (nDSG), effective September 2023, requires data controllers to establish data processing agreements (DPAs) with processors that access personal data. Where these agreements contain specific liability clauses for data breaches or processing failures, the signature on the agreement becomes relevant in any enforcement or litigation context.

For cross-border DPAs, particularly those involving EU processors subject to GDPR in parallel, QES provides a signature tier that is recognised in both Swiss and EU jurisdictions. The same applies to agreements where Swiss law and EU law may both apply to a dispute.

The common thread

Each of these document categories shares the same characteristic: the legal exposure if the document is challenged outweighs the additional effort of using QES instead of a basic signature. In each case, the question is not whether AES is technically capable of producing a signature. It is whether that signature can withstand a legal challenge in the specific context.

Where the answer is uncertain, QES is the document type's appropriate tier. The identity verification required for QES, combined with the legal presumption it carries under ZertES Art. 11, removes that uncertainty at the point of signing.

Review your current document workflows against these five categories and confirm which are using QES where it is warranted.

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 Demo

Related Articles

Agencies: who owns the AI-assisted work you hand to a client?
Legal

Agencies: who owns the AI-assisted work you hand to a client?

When an agency hands AI-assisted work to a client, ownership gets harder to prove, not easier. What a dated, independently verifiable record adds before handoff, and why a contract clause alone doesn't settle who made what, when.

August 16, 2026Read more →
Sealing a whole content library: batch proof for teams
Legal

Sealing a whole content library: batch proof for teams

Six years of client work does not mean six years of proof. A practical plan for teams and agencies to seal a whole content library: a forward habit for new work and a triage plan for what is already sitting in the backlog.

August 15, 2026Read more →
Qualified timestamps explained, and why the time matters more than the signature
Legal

Qualified timestamps explained, and why the time matters more than the signature

A qualified electronic timestamp does not tell you who created something. It tells you when a specific file existed, attested by an independent trust service provider, which is usually the fact most authorship disputes actually turn on.

August 12, 2026Read more →
Screenshots, emails and file dates: why your usual evidence fails
Legal

Screenshots, emails and file dates: why your usual evidence fails

The evidence most people reach for in a dispute, a screenshot, a forwarded email, a file's own modified date, is generated and stored on a system the claimant controls. Here is why none of it holds up, and what actually does.

August 11, 2026Read more →
What makes a digital proof hold up: hash, timestamp, signature, certificate
Legal

What makes a digital proof hold up: hash, timestamp, signature, certificate

Four things decide whether a record survives being challenged: a hash that binds it to one exact file, an independent timestamp, a signature tied to a real identity, and a certificate anyone can check without contacting you. What each one actually does.

August 9, 2026Read more →