Qualified — ZertES and eIDAS
Every signature can be issued as a qualified electronic signature (QES) — via an official Swiss CA under ZertES or an EU / DE CA with QTSP status under eIDAS. Legally equivalent to a handwritten signature.
Qualified electronic signatures under ZertES and eIDAS — through official Swiss CAs and EU / DE QTSPs. Legally equivalent to a handwritten signature, straight from any procedure.
Preferably with pure trust-service providers: the certificate comes to us, the document stays with you.
We preferably work with pure trust-service providers that deliver the qualified certificate to our application — typical representatives are Swisscom Trust Services and SwissSign. The document stays in your tenant's perimeter; server signing happens on the hash, not on the content.
On request we also integrate platform-based providers — Skribble, DocuSign and other listed QTSPs — where the document is hosted, routed and signed inside the provider's workflow. The same platform, the same case — a different route.
Legally binding under ZertES and eIDAS — preferably via the direct certificate route, alternatively via the platform workflow.
Every signature can be issued as a qualified electronic signature (QES) — via an official Swiss CA under ZertES or an EU / DE CA with QTSP status under eIDAS. Legally equivalent to a handwritten signature.
We preferably work with interfaces that deliver the qualified signature certificate directly to the application — Swisscom Trust Services and SwissSign for instance — so the document never leaves your tenant's perimeter.
On customer request we also integrate platform-based trust-service providers like Skribble or DocuSign — with document hosting, reminders, multi-party routing and audit trail at the provider.
One architecture, many providers. Any QTSP on the Bundesnetzagentur trusted list, the EU LOTL or recognised by OFCOM is connectable — the choice is made by the tenant, not the platform.
We rely exclusively on certification services that are listed in official registers — either with OFCOM (recognition through KPMG among others) for Switzerland or in the Bundesnetzagentur trusted list or the EU LOTL for the EU area.
Federal act on certification services in the area of electronic signature
Regulation (EU) No 910/2014 on electronic identification and trust services
Our preferred choice are trust-service providers that deliver the certificate and leave the document with the customer. Platform-based providers with their own workflow we integrate on tenant request as well — the choice is the tenant's.
Pure remote QES providers · server signing under eIDAS Annex II / ZertES Art. 6 — the document does not leave the customer's perimeter.
Remote QES provider with server signing under ZertES Art. 6 and eIDAS Annex II. Delivers the qualified signature certificate to the application — the original document does not permanently leave the customer's perimeter.
Swiss QTSP / CA recognised under ZertES. Pure trust service: the certificate is handed to the signing application; the document stays in the tenant's Absidion environment.
Platform-based trust-service providers with eIDAS QTSP or ZertES status — the document is hosted in the provider's workflow.
Platform workflow: the document is hosted at the provider, parties are invited, signing happens in the provider's portal. The end product flows back into the file signed.
Platform workflow with an underlying EU QTSP for QES. Offers routing, reminders and audit trail at the provider; the signed document is replayed into the platform.
Other providers with eIDAS QTSP or ZertES status are connected on tenant request — either directly via trust-service API or via their platform workflow.
Rulings, contracts, decisions, applications — wherever written form is required or authenticity must be proven beyond doubt.
A ruling is created in the specialised process, signed qualified and delivered via the portal — legally sound and without media breaks.
A contract is signed by multiple parties: internal owners via the direct certificate route, external partners via the platform workflow if needed.
Meeting minutes and resolutions are signed qualified directly from meeting management by entitled persons.
An external person fills in a form in the portal and signs qualified — identity proven via a trust service.
Employment contracts and personnel decisions are signed qualified — with a clear audit trail in the tenant, not in someone else's inbox.
Outbound documents are signed qualified before dispatch — authenticity verifiable at the recipient, without calling us back.
Six areas — from signature quality through both architectures, identification and triggering, integration into the platform to the compliance frame.
From simple to qualified — graded per document type, in a consistent frame.
Highest level under ZertES Art. 6 and eIDAS Annex II — legally equivalent to a handwritten signature, issued by a recognised QTSP.
Person-bound, forgery-proof and tamper-resistant — suitable where there is no statutory written-form requirement.
For internal confirmations and releases, documented in the platform's audit trail.
PDF Advanced Electronic Signatures — embedded signature, verifiable in any PAdES-capable reader, with a visible or invisible signature field.
For XML and container formats, XAdES and CAdES are available as signature formats — depending on tenant requirements.
Embedding of timestamp and revocation information so that the signature remains verifiable after the certificate expires.
Pure remote QES providers deliver the certificate — the document stays in the tenant's perimeter.
The qualified signature creation device (QSCD) lives at the QTSP — the signature is requested by us; the document does not leave our environment.
Smart Registration Service and All-in Signing Service — certificate issuance per case, without permanent provider storage of the original.
Swiss QTSP / CA recognised under ZertES; the signing application receives the qualified certificate.
Only the hash of the document is handed over — the document itself never has to leave the tenant environment.
One account and one contract per tenant at the trust service — no shared provider account, no mixed supervision.
Content, attachments and metadata do not go to the QTSP — only the hash and the minimum identity data the qualified signature requires.
When the tenant expressly requests it — provider portal with document hosting and routing.
Direct API integration for QES under ZertES and eIDAS — the case is started from Absidion, signing happens in the provider portal, the finished document comes back into the file.
EU QTSP backend for QES; platform workflow with multi-party routing, reminders and compliance reports.
Invitations, follow-up reminders and status notes run via the provider — traceable in the case's audit trail.
Sequential or parallel signing orders, with roles per participant — the case in Absidion follows the status.
Once completed, the signed document is replayed into the tenant and filed on the case — with a validation report.
Each platform provider has a separate data-processing agreement — also visible in the tenant's data-protection documentation.
Who signs is unambiguous — and how it is triggered depends on the use case.
First identification of the signing person per QTSP requirements — video ID, on-site ID or via an accepted eID.
eIDs of listed providers are accepted for the two-factor trigger — e.g. Mobile ID, eID apps and comparable means.
Every single qualified signature is released with a second factor — push confirmation or one-time code, depending on QTSP.
On request with a visible signature spot in the document — name, role, date, validation status at a glance.
Every signature can carry a qualified timestamp from a recognised TSA provider.
Release multiple documents in one case — one two-factor step per case instead of one per document.
The signature is a platform service — available to every process, every workflow and every form.
Case, contract, meeting, event — wherever a document is created, the signature can be requested directly.
In the workflow designer "sign" is its own step — with participants, order and escalation, identical for both architectures.
A form response can be signed qualified at submission — for applications, declarations, submissions.
The signed document hangs on the record — with validation report and audit entry — retrievable exactly where it was created.
The platform shows the validation status directly in the reader — certificate, revocation status, timestamp — without switching to another tool.
Cases can be searched by signature status — open, signed, rejected, expired.
Both architectures follow the platform's same security and data-protection frame.
When a trust service is configured we check against the EU LOTL, the BNetzA list and OFCOM recognition — no provider without active status.
Hosting of the platform and routing of signature calls within Switzerland or the EU, depending on tenant — no unintended third-country transfer.
The platform service runs in the same certified management system as the rest of the Absidion platform.
Private keys of the signing person live in the QSCD at the QTSP — not at us, not in the browser, not in a file.
Who handed what to signature when, released or rejected — fully in the platform's audit trail.
Signed documents are retained per tenant specification and can be exported with their validation report — also after a provider switch.
Wherever a case produces a binding document, the platform service takes over — without every procedure having to maintain its own trust-service integrations.
"Sign" is its own workflow step — with participants, order and escalation, identical for both architectures.
Responses from forms can be signed qualified at submission — applications, declarations, submissions.
Documents sent via the encrypted channel can be signed qualified — the same case, protected throughout.
External persons trigger qualified signatures from the portal — with the accepted eID of their provider.
Rulings are signed on the case — with validation report and audit entry on the record.
Contracts go through multi-party signing — internals via the direct route, externals possibly via the platform workflow.
From any Absidion page, navigate to every other process and to the services that work across all of them.
A short demo where we're happy to answer your questions in person. No commitment, no sales theatre.