# Contracts and e-signature for a Swiss Einzelfirma

Source: https://www.solory.ch/features/contracts

Last reviewed: 2026-09-26

Draft from nine preset instruments, price the positions inside the contract body, send a one-time signing link, and keep the exact PDF your client signed. Contracts and the e-signature flow are on the Professional and Business plans.

- 9 - Preset contract instruments
- 5 - Languages for titles and clauses
- 2 - Signatures per contract: client and you
- 7–30 - Days a signing link stays valid, or no expiry at all

## Nine instruments, five languages, one clause corpus per language

A contract starts from a preset instrument rather than from a blank page.

The nine presets are a Service Agreement (MSA), a Statement of Work, a Werkvertrag, a Mandate, Recurring services, B2C terms, Brokerage, an NDA and a Licence. Each carries its own document title in all five languages, so the German PDF is headed DIENSTLEISTUNGSVERTRAG and the Italian one CONTRATTO DI PRESTAZIONE DI SERVIZI, rather than an English title with translated paragraphs underneath.

The clause corpus is per language too. English, German, French, Italian and Hungarian each have their own clause file, so the wording your client reads was written in their language instead of being pushed through a translation at render time. German is Swiss Standard German throughout: ss, never the eszett.

The body is edited in a rich-text editor with headings, bold, italic, underline and lists, stored as markdown. Only a draft can be edited: a contract that has been sent must be reverted first, so nobody quietly changes the document a client is reading right now.

## Priced positions inside the contract body

Prices belong in the contract, not in an attachment nobody signs.

Positions with quantities and prices are written into the contract itself and print as a real table inside the body text. The money maths, the grouping and the table live in one place, and each language supplies only its words - which is how a rounding rule stays the same in German and in Italian instead of being right in one document and wrong in the other.

- Arbitrary priced positions in the contract body, printed as a table rather than pasted in as prose
- A declaration about the Swiss VAT registration threshold of CHF 100'000 (Art. 10 para. 2 lit. a MWSTG) can be written into the contract text, so the PDF, the preview and the signing page all carry it - in the primary language always, and in the second language too when bilingual mode is on
- A contract can record the estimate it was drafted from; an estimate belonging to another account is stored as nothing rather than as a dangling reference
- Images and PDFs attached as annexes are appended to the downloaded contract PDF - images one per page scaled to fit, PDF annexes page for page

Before an annex is merged into the PDF, its storage key is re-checked against the account that owns the contract. A path that points somewhere else is refused rather than rendered.

## Bilingual contracts and the authoritative version

A Swiss contract often has to exist in two languages at once, with one of them deciding.

In bilingual mode the PDF is rendered in two columns, in both selected languages, on the same page. The contract names an authoritative version explicitly: the version that prevails if the two languages differ. That sentence is part of the document, so the question is answered on the paper rather than in a later email.

> **Note: The languages are chosen on the contract**
> A contract has a primary and an optional secondary language, picked on the contract itself. There is no per-contract language chain that inherits from the client record the way an invoice does, so a bilingual German and French contract stays German and French no matter whose screen it is opened on.

## Sending a contract for signature

Your client does not create an account and does not get a password. They get one link.

1. **Finish the draft** - Text, priced positions, annexes and languages. A draft re-renders on demand, so what you see is the current document, not a stored copy from last week.
2. **Send the signing link** - A private one-time link, valid for 7, 14 or 30 days, or with no expiry; 14 days is the default. Only a fingerprint of the token is stored, not the token itself, so the database never holds a link that would work.
3. **The signer confirms their address** - A six-digit code is emailed to the signer and is valid for 10 minutes, with a 45-second cooldown between sends and six attempts per code. Only a fingerprint of the code is stored, not the code itself, and a signature is refused until the code has been verified.
4. **The client signs** - They type their full legal name, draw a signature, and tick an explicit consent box. The consent wording is on the page, in plain words, before anything is submitted.
5. **You countersign** - You draw your own signature from the contract page. The contract only becomes signed once both parties have signed - it does not flip to signed on the client's submission alone.
6. **The signed PDF is archived** - At the moment of signature the typeset document is stored byte for byte and served back verbatim from then on.

## What the signed PDF proves, and what it does not

The audit trail is specific, and the legal grade is stated plainly rather than implied.

- **Typed name**: The signer's full legal name exactly as they typed it, up to 200 characters.
- **Drawn signature**: The drawing itself, stored with the signature record.
- **Time, IP address and device**: When the signature was submitted, from which IP address, and the browser user agent that submitted it.
- **Content fingerprint**: A fingerprint of the exact contract text shown at signing. If the text changes afterwards, the fingerprint no longer matches it.
- **Contract version**: Which saved version the signed text belongs to. Version history keeps every wording read-only, with author, timestamp and fingerprint, and flags the versions a signature was taken against.
- **Verified email**: Evidence that the code sent to the signer's address was entered correctly before the signature was accepted.

The signature is consumed atomically. A second submission on the same link, or one that arrives after the link has expired, cannot slip through.

> **Warning: This is not a qualified electronic signature**
> The signing page says it in these words: "By signing here you are providing a simple electronic signature... A simple electronic signature can carry evidentiary value, but it is not a qualified electronic signature and may not satisfy form requirements that specifically require one." Where a form requires a qualified signature, that needs a qualified trust service provider, which this product is not and does not include.

## The byte-exact signed archive

Your client signed a typeset document, not markdown.

Re-rendering the same words later is not the same document: change a font, a margin or a line break and the same contract produces different bytes. So the PDF is archived exactly as it stood at the moment of signature, and that file is what is downloaded from then on.

- The archived bytes are served verbatim; the signed contract is never re-rendered
- The upload refuses to replace bytes that already exist
- A database trigger rejects any update that moves a pointer already set - including a request sent straight through the API, not only one that comes from the app
- Unsigned contracts are deliberately not archived: a draft re-renders on demand, and a stale stored copy would prove nothing while consuming your storage quota

> **Warning: Contracts signed before the archive shipped are not retro-archived**
> The byte-exact archive is written at the moment of signature. Contracts that were already signed when the feature arrived were deliberately not back-filled, because a copy re-rendered afterwards would be a different document presented as the original one.

## Statuses, versions and expiry

Four statuses, and one of them is deliberately not automatic.

| Status | What it means | What you can do |
| --- | --- | --- |
| Draft | Being written; nobody outside has seen it | Edit freely, render a PDF on demand, send for signature |
| Sent | A signing link is out with the client | Revert to draft to change the text, or wait for the signature |
| Signed | Both parties have signed | Download the archived PDF; the wording is fixed |
| Expired | You have marked it as no longer in force | Set by you; a valid-until date alone does not change it |

A contract carries valid-from and valid-until dates and the calendar shows a contract-expires entry on the day, alongside invoice due dates, VAT filing dates and the rest. No job flips the status: expiry is a decision you record, not something the system decides on your behalf.

## What contracts here do not do

The honest list, so you can rule this out quickly if it is not what you need.

- No qualified electronic signature. The in-app signature has an audit trail, and it is explicitly not a QES.
- No legal advice. The nine presets are starting points drafted to be useful, not an opinion on your situation, and they do not replace a lawyer or a Treuhänder.
- Contracts and the signing flow are on the Professional and Business plans. Free and Starter accounts do not have them.
- Contracts do not appear in the read-only client portal, which shows invoices, estimates and shared documents. Signing uses its own one-time link.
- No automatic expiry. Nothing flips a contract to expired on its valid-until date.
- No retro-archiving of contracts signed before the byte-exact archive existed.
- Sealing, with a tamper-evident fingerprint of the content and of the PDF, is an invoice feature. A contract's equivalent is the archive written at signature.
- The AI assistant can propose creating a contract or setting its status as a step in a plan you read and confirm first. It never sends a contract, an email or anything else to a client, and there is no step in its vocabulary that could.

## Questions and answers

**Is an e-signature from Solory valid in Switzerland?**

The signing page states the answer in its own words: you are providing a simple electronic signature, which can carry evidentiary value, but it is not a qualified electronic signature and may not satisfy form requirements that specifically require one. What is recorded alongside it is a verified email address, the typed name, the drawn signature, the time, the IP address, the device and a fingerprint of the exact text shown at signing. Where a form requires a qualified signature, that needs a qualified trust service provider; ask your legal adviser which category your contract falls into.

**Which plan do I need for contracts and signing?**

Professional at CHF 49 per month and Business at CHF 89 per month include contracts and the e-signature flow. Free and Starter do not. Prices are per account per month in Swiss francs and are stated without Swiss VAT, because the operator is below the Swiss VAT registration threshold and is not VAT-registered.

**Does my client need an account to sign?**

No. They open a private one-time link, receive a six-digit code at their email address, enter it, type their full legal name, draw a signature and tick a consent box. There is no client login and no password anywhere in the flow. Only a fingerprint of the link token and a fingerprint of the code are stored, so neither can be read back out of the database.

**What happens if the contract text is changed after signing?**

The fingerprint taken at signing no longer matches the changed text, which is exactly what the fingerprint is for. The signed PDF itself is untouched: the archived bytes are what is served, the upload refuses to replace them, and a database trigger rejects any attempt to re-point the archive. A signed contract is also not editable in the app - only drafts are.

**Can I issue a contract in two languages?**

Yes. Pick a primary and a secondary language and the PDF renders in two columns, both languages side by side, with an explicit statement of which version prevails if the two differ. Titles and clauses exist in English, German, French, Italian and Hungarian, and the German wording uses ss throughout rather than the eszett.

**Do contracts expire on their own?**

No. A contract holds valid-from and valid-until dates and the calendar shows a contract-expires entry on the day, but no background job changes the status. You set a contract to expired yourself. This is deliberate: a date in a field is not the same as a decision that an agreement has ended.

**Can the AI assistant draft and send a contract for me?**

It can propose creating a contract or changing a contract's status as steps in a plan you see in full and confirm before anything runs. It cannot send a contract, an invoice, an estimate or a reminder to a client, because no send step exists in what it is allowed to propose. Planning is read-only; execution happens only after your confirmation and goes through the same validated actions the forms use.

## Related pages

- [/features/invoicing](https://www.solory.ch/features/invoicing)
- [/features/crm](https://www.solory.ch/features/crm)
- [/pricing](https://www.solory.ch/pricing)
- [/security](https://www.solory.ch/security)
