Choosing the right e-signature software involves more than just being able to sign a PDF. With MitID and BankID for Nordic identification and an eIDAS-based signature level, the solution should be able to verify both who signed the document and that the digital signature was created on a legally valid basis. In this overview, we’ll examine the criteria that truly distinguish the solutions, so you can make your choice based on your own document workflows rather than a list of features.
The most important criteria in a comparison
Three factors typically determine the choice: which eID methods the solution supports, how well it integrates with your existing systems, and what documentation it can provide regarding security and data processing. Add to that the pricing model and ease of use for both the sender and the signer. A platform may have all the features on paper, but if the workflow is cumbersome, actual usage will quickly decline. Therefore, start by identifying which document types you sign most frequently, who your counterparties typically are, and which systems the signing process needs to integrate with.
eID and Signature Levels According to eIDAS
eIDAS categorizes electronic signatures into three levels: simple (SES), advanced (AES), and qualified (QES). The evidentiary weight increases with the level, and the right choice depends on the document’s risk profile and legal requirements. A robust solution allows you to select the eIDAS security level per document type, ensuring that standard documents aren’t unnecessarily burdened with onerous requirements, while sensitive agreements receive the necessary security. For Nordic companies, it’s also important that the solution supports MitID, MitID Erhverv, and BankID, so that counterparties can identify themselves using an eID they already have, rather than having to create new accounts.
API Integration and Workflow Automation
An e-signature software solution should be able to integrate with the systems employees already use—such as CRM, HR systems, or case management systems. An open API makes it possible to trigger the signing process automatically, return the completed document to the correct location, and keep everything consolidated in one place rather than in a separate portal. Therefore, assess whether the solution offers documented integrations and standard connectors, and how much development work is actually required to integrate it into your workflow. The more manual steps you can eliminate, the greater the actual time savings in your day-to-day operations.
GDPR, Data Processing, and Audit Trail
Compliance is one of the most compelling factors in a comparison. Verify where data is stored, which sub-processors are involved, and how actions are logged in an audit trail. GDPR and e-signature regulations require that consent and data processing be documented at every stage, and an independent ISAE 3000 audit provides third-party confirmation that these controls are being followed in practice. Pay particular attention to whether data processing takes place within the EU/EEA, as this significantly simplifies documentation and reduces the risk associated with transfers to third countries.
Pricing Models and Total Cost of Ownership
The price of e-signature software is typically based on the number of users, the number of signatures, or a fixed subscription. The most cost-effective model therefore depends on your actual volume of documents: a department with few but complex agreements has different needs than one with many standard signatures. Also factor in add-on modules, integrations, support, and training into the total cost of ownership so that you’re comparing actual operating costs rather than list prices. A low starting price can quickly become expensive if necessary features are included in add-on modules. Therefore, request a quote that reflects your expected annual volume and the eID methods you actually need, rather than comparing based on the lowest entry price.
How to Test the Solutions in Practice
Set up a test environment with your own document types and run the entire workflow from sending to signing and archiving. Test signing with a digital signature via MitID, and evaluate the user experience for both the sender and the recipient, as a cumbersome experience for the recipient is often what slows down adoption. If you’re considering switching from an existing provider, a comparison —such as Addo Sign versus Penneo —can help clarify the differences in features, integrations, and eID coverage before you make your final decision.
Common pitfalls to avoid
The most common mistake is choosing based on a demonstration using idealized documents rather than your own, often messy real-world workflows. Another pitfall is underestimating the user experience: if customers or employees find the signing process cumbersome, the completion rate will drop, no matter how well the system is managed. Also be aware that a low list price may hide costs for integrations, additional eID methods, or higher signature levels. Finally, you should ensure that archiving and audit trails meet your documentation requirements so that signed documents can be retrieved and remain valid in the event of a dispute many years down the line.
Mikkel Thiel
I primarily share knowledge and experience on digital signing, automation and digital document processes — and on how platforms, systems and AI can work together to support businesses.
I have more than 10 years of experience in Customer Success, consulting, leadership and service. My focus on great user experiences goes back to my years at Apple, where I worked in customer service and management. This has shaped my approach to technology: it should not only work — it should be easy to use and create value for the people who use it.