Four roles
Signers and approvers sign. Cc and viewer recipients get their own link to read the document, but are not counted when you check whether everything is done. Up to 20 recipients per send.
Part of the Offert & e-signering module E-signing
The agreement signed in the right order, before it runs out.
Upload the agreement, choose who signs and in what order, and send. Recipients confirm a one-time code from their email and sign in the browser with no account. Every step is logged with its time, IP address and browser, and when the last one has signed, everyone gets a completion certificate. In all three tiers, with no fee per signature.
What it is
What the e-signing does, plainly
A service agreement with a housing cooperative, a framework agreement with a property manager, an order with two authorised signatories. The right people have to sign in the right order before the agreement runs out, and you have to be able to show afterwards what happened.
Order enforced on the server
Recipients in the same step sign in parallel. A later step is refused until every signer and approver before it has signed — by the server, not by a hidden button. A direct call to the API is stopped too.
The last day is checked at the signature
A send can be given a last day. Once it has passed, the signature is refused at the moment somebody tries, even if the link still opens the document.
A one-time code before signing
Before they can sign or decline, the recipient enters a six-digit code sent to their email: valid for 10 minutes, five tries. It is set per document and is on by default for new documents. A forwarded link is not enough, because the code goes to the recipient's own address. A code by SMS instead is built but not yet switched on.
A trace of every step, bound to the file
The signature is stored as typed or drawn, with its time, IP address and browser; the first open and the code check are logged the same way. The file's SHA-256 fingerprint is taken when it is sent and carried in the signing events. If the stored file no longer matches, the signature is refused.
A numbered chain, checked every night
Each signing event is numbered and gets a SHA-256 hash built from its own content and the previous event's hash. Events can only be added: on PostgreSQL the database itself refuses changes and deletions. The chain is verified every night, and the audit view shows whether it holds.
A certificate when everyone has signed
When the last party signs, a completion certificate is created as a PDF: the parties, the times, IP addresses and browsers, how each signer was verified, the document's fingerprint and the head of the chain. Every party gets an email with download links to the signed document and the certificate, valid for 30 days.
A decline gives a reason
A recipient who declines has to say why. The reason goes into the chain, the document is marked declined, and you are emailed.
Reminders that stop on their own
Anyone who has not signed is reminded — by default every third day and at most three times for quotes; you set the interval and the count. Reminders stop when the recipient has signed or the send has expired.
Example
A service agreement with four recipients
Step 1 is the customer's two people: the chair signs and the treasurer approves, in either order. Step 2 is your own authorised signatory, who cannot sign until step 1 is complete. The site manager gets a read link as cc.
Below the recipients the events stand in order, numbered, each carrying the previous event's hash. That chain is what makes a later change detectable.
Agreement
Ventilation service agreement 2027
Last day to sign 2026-11-01
- Step 1Chair, customerSignerSigned
- Step 1Treasurer, customerApproverSigned
- Step 2Managing director, youSignerCan sign now
- —Site manager, youCcRead link
Events
- #1Sent10-12 09:143f9a…c21eprevious —
- #2Opened10-12 13:5581d0…77b4previous 3f9a…c21e
- #3Code confirmed10-12 14:01e07c…5a12previous 81d0…77b4
- #4Signed10-12 14:02c4e2…09fdprevious e07c…5a12
- #5Signed10-12 16:405b7e…e310previous c4e2…09fd
How it runs
From uploaded agreement to signed
- 01
Upload the agreement
Preferably as a PDF. Where the server can rasterise the PDF the document is shown page by page on the signing page; otherwise the file is shown as it is.
- 02
Add recipients and order
Name, email and role for each recipient. If the order matters, put them in steps; recipients in the same step sign in parallel.
- 03
Set a last day and send
Each recipient gets their own link by email. With the one-time code on — the default for new documents — the link alone is not enough to sign: the recipient also needs the code sent to the same address. Turn the code off and whoever holds the link can sign, so then ask recipients not to forward it.
- 04
The recipient signs
The document is shown at the top and the signature field below it. The recipient enters the code from their email, types their name or draws their signature and confirms — or declines and gives a reason. No account, no app.
- 05
Follow up
You see who has opened and who has signed, and the audit view shows whether the chain holds. When the last signer is done, everyone gets the signed document and the completion certificate by email. The signing events are not pruned with the ordinary audit log. To move the last day, send again, which replaces the old links with new ones.
eIDAS and Swedish law
What the law says, and what it does not
The eIDAS Regulation, (EU) No 910/2014, distinguishes simple, advanced and qualified electronic signatures. The requirements for an advanced signature are in Article 26, among them that it is created with data the signatory can use under their sole control. A qualified signature is an advanced one that is, in addition, created by a qualified device and based on a qualified certificate.
Article 25 says two things that are easy to run together. An electronic signature shall not be denied legal effect or admissibility as evidence solely because it is electronic or does not meet the requirements for a qualified one. But only the qualified signature has the equivalent legal effect of a handwritten one. Closepact's standard signature is an electronic signature in the sense of Article 25. We do not call it advanced, because the signer holds no signing key under their sole control; what backs it is the one-time code, the document's fingerprint, the tamper-evident chain and the completion certificate. A BankID signature, once BankID is switched on, is different: the signer signs with the key in their BankID app, which makes it advanced, though still not qualified. Closepact does not issue qualified signatures and is not on PTS's list of qualified providers.
Most agreements a service company makes carry no form requirement: even an oral agreement is binding, and the question in a dispute becomes what you can show. The exceptions are documents where Swedish law requires a physical signature. Lantmäteriet, the land registry, lists for example deeds of sale, purchase contracts, deeds of gift and exchange agreements for real property, and points out that eIDAS does not replace national form requirements.
If you sell to private individuals and the agreement is made at a distance, the customer may have a 14-day right of withdrawal, according to Konsumentverket. E-signing does not change that.
Sources
Tier and price
In all three tiers
E-signing is included in Start, 199 kr per user per month, in Väx, 379 kr, and in Pro, 429 kr. There is no fee per signature, and recipients pay nothing. Prices are per user per month with no minimum, excluding VAT on an annual agreement.
BankID signing and identification are built for Väx and Pro and are being activated; until then the options show as unavailable. Once switched on, a BankID signature costs 4.49 kr, because BankID is charged per use. The SMS one-time code, likewise waiting to be switched on, costs 0.89 kr per message.
Example: five users on Start
- Start, per user per month
- 199 kr
- Users
- 5
- Fee per signature
- 0 kr
- Per month, excl. VAT
- 995 kr
Annual agreement. A sole trader on Start pays 199 kr per month.
Honest about the edges
What the e-signing does not do
Here so you can judge, before signing anything with us, whether it is enough for your agreements.
No BankID yet. BankID signing and identification are built but wait on Closepact's BankID agreement; until they are switched on, the recipient signs with a typed or drawn signature.
No qualified electronic signature (QES). If a counterparty or a statute requires QES, you need another supplier for that agreement.
The standard signature is not an advanced electronic signature in the eIDAS sense: the signer holds no signing key of their own. A BankID signature will be advanced once BankID is switched on; until then, if a counterparty asks for an advanced or qualified signature, this is not it.
Until an SMS service is switched on, the one-time code goes by email only; the SMS code is built, and falls back to email when the recipient has no phone number. The code can be switched off per document, and then the personal link is all that identifies the recipient.
The signed file itself is not stamped or sealed. The completion certificate is a separate PDF to keep beside it, and the links in the completion email work for 30 days.
One document per send. An agreement with appendices is uploaded as one file.
Common questions
Questions about e-signing
The answers describe what is built today. If your question is missing, write to sales@closepact.com.
Is e-signing legally binding in Sweden?
Yes, for agreements with no statutory form requirement — and most orders, service agreements and framework agreements have none. Under Article 25 of eIDAS an electronic signature cannot be denied legal effect or admissibility as evidence solely because it is electronic. What is tested is the evidence: who signed, when, and whether the document changed. That is why each signer confirms a one-time code from their email, the document's fingerprint is bound to the signature, every step is stored with its time, IP address and browser, and the completion certificate gathers it in one file. The exceptions are documents where the law requires a physical signature, such as a deed of sale for real property.
Do you have BankID?
Not yet, though it is built. BankID signing — required per document or per signer — and identification with BankID before the document opens are in the product and wait on Closepact's BankID agreement; until then the options are shown as unavailable, and we do not show BankID as a delivered feature anywhere. Today the recipient signs with a typed or drawn signature through their personal link, after a one-time code by email. Once switched on, a BankID signature costs 4.49 kr on the Väx and Pro tiers, because BankID is charged per use. Ordinary e-signing stays free of any per-signature fee.
Is it an advanced or a qualified electronic signature?
The standard signature is neither, and we do not claim either. Both are defined in eIDAS. An advanced signature must be uniquely linked to and capable of identifying the signatory, created with data the signatory can use under their sole control, and linked to the document so that later changes can be detected. A qualified signature additionally needs a qualified certificate and a qualified device, and has the same legal effect as a handwritten one. Closepact's standard signature is an electronic signature under Article 25: the signer confirms a one-time code from their email and the document's fingerprint is bound to the signature, but the signer holds no signing key of their own. A BankID signature, once BankID is switched on, will be advanced — the signer signs with the key in their BankID app — and still not qualified. For most agreements a service company makes, the standard signature is enough; where a counterparty or a statute asks for more, it is not.
Can the customer sign in the wrong order?
No. When a send is split into steps, the server checks at every signature that all signers and approvers in earlier steps have signed. If not, the signature is refused, even if somebody goes round the interface and calls the API directly. Recipients in the same step sign in any order, and cc and viewer recipients never hold anyone up.
What happens if the agreement expires before everyone has signed?
Then it can no longer be signed. The last day is checked at the moment somebody signs, not only in an overnight run, and an hourly run marks overdue sends as expired. To extend it, send again: the old links stop working, new ones replace them, and the recipients get them by email.
eIDAS e-signature Audit trail Two-factor sign-in GDPR · DPA
Also in this module
Deal roomOne link per deal: the quote, documents, files from the customer, chat. Pro tier. Quote with priced lines (CPQ)Lines from your own product catalogue, discounts, VAT per line and optional lines. The customer accepts at the quote's own link, and the quote becomes a job or an invoice draft. From Väx. AI draftingBusiness cases and meeting summaries drafted from the deal. Pro tier only.
See it on your own work
Twenty minutes. We set up a quote of yours before the call.
This page describes one capability of the module. What is bought is the module — from 199 kr per user per month.