The Complete Guide to Digital Signatures for Businesses

Share this article
Share on LinkedIn

Technically speaking, a digital signature is a cryptographic link between a document, a verified identity, and a timestamp—not just an image of a signature. This digital signature guide is based on the technical and legal requirements, so you can choose the right signature level instead of guessing. We’ll go over the types of signatures under eIDAS, how identification with MitID works, which laws apply, and how to implement digital signing in practice.

The Technical Core: Hash, Certificate, and Seal

When a document is digitally signed, a cryptographic hash—a unique fingerprint of the document’s content—is first calculated. The hash is sealed together with the signer’s identity information and a timestamp. If even a single character in the document is changed afterward, the hash will no longer match, and validation will reveal that the document has been tampered with. It is this mechanism that distinguishes a genuine digital signature from a scanned signature, which is merely an image with no link to content or identity. Understanding the sealing process is crucial because it is what gives the signature evidentiary value in the event of a dispute.

At higher signature levels, a certificate is also included that links the signer’s key to a verified identity. The certificate is issued by a trusted provider and can be verified by anyone who needs to validate the document later. In practice, this means that the recipient does not have to blindly trust the sender but can verify both the identity and the integrity of the document through an independent check. It is this chain of trust—from the hash to the certificate to the timestamp—that allows a digital signature to stand alone as evidence, even several years after it was applied.

The three signature types under eIDAS: SES, AES, and QES

The eIDAS Regulation defines three levels. A simple electronic signature (SES) can be a checkbox or a handwritten name and has low evidentiary value. An advanced electronic signature (AES) must be uniquely linked to the signer, be able to identify the signer, and detect subsequent alterations—this level typically corresponds to signing with MitID. A qualified electronic signature (QES) is based on a qualified certificate from a trusted provider and is legally equivalent to a handwritten signature. You can explore the differences in more detail under the EIDAS security levels and read about when a Qualified Electronic Signature is required.

Identification with MitID, MitID Business, and Nordic eID

The strength of a Danish digital signature lies in the identification process. When an individual signs with MitID, or an employee uses MitID Business, their identity is verified by the national eID solution, and your company does not need to verify their identity itself. For Nordic signers, this is handled similarly by BankID in Sweden and Norway. This makes it possible to obtain legally valid signatures across national borders without the need for physical presence. If you’d like to see the actual process, our article on Digital Signatures with MitID walks you through every step, from submission to validation.

It’s worth noting the difference between MitID and MitID Business. MitID is used by private individuals, while MitID Business links an employee to a specific company and its rights—this is relevant when an employee needs to sign on behalf of the company rather than as a private individual. For international agreements, it also makes sense to choose a platform that supports both Danish MitID and Swedish/Norwegian BankID, so that the same document can be signed by parties in multiple countries without switching solutions. The better the eID coverage matches your actual signers, the less friction recipients experience, and the higher the completion rate will be for the documents you send for signing.

Legislation: eIDAS, GDPR, and Industry-Specific Requirements

Two sets of regulations are key. eIDAS determines whether a signature is valid and recognized across the EU, while the GDPR sets requirements for how personal data is processed and stored during the signing process. On top of that, there are industry-specific rules—such as the Accounting Act for financial documents or employment law requirements for contracts—that determine how long documents must be retained. A properly configured digital signature addresses all three layers at once: validity under eIDAS, data processing under the GDPR, and retention in accordance with the relevant sector-specific legislation.

For the public sector and regulated industries such as finance and insurance, the requirements are often more stringent. In these cases, there may be requirements for a specific signature level as well as for the provider to document its data processing agreements, including the use of any sub-processors. It is therefore a good idea to clarify early on whether the documents your company signs are subject to special rules, so that the signature solution is chosen on the correct basis from the start. It is rarely possible to retroactively correct an insufficient signature level—the validity must be in place the moment the signature is applied.

Audit trail: the documentation that makes the signature valid

An e-signature is only as strong as the documentation that accompanies it. The audit trail records who received the document, when it was opened, which eID was used, and the exact time of signing. This audit trail is what gives the signature evidentiary value and simultaneously meets the GDPR requirement for traceability. When an agreement is disputed, it is rarely the signature itself, but rather the ability to prove the sequence of events that decides the case—and therefore, the audit trail should never be optional.

Compliance and Operational Reliability: ISAE 3000

When selecting a provider, you should examine how the platform itself has been audited. An ISAE 3000 statement documents that the provider’s controls for security and data processing have been reviewed by an independent auditor—this is particularly important for public sector organizations, finance, and insurance. Together with eIDAS compliance, this forms the foundation ensuring that signatures are not only valid but also generated in an environment that meets the requirements. Learn more about what an ISAE 3000 audit covers before making your decision.

Implementation: From Mapping to Operations

Start by mapping your document flows: which documents are signed most often, by whom, and what eIDAS level does each one require? Then match the signature level to the requirement so that you neither choose too low a level and risk invalidating the document nor too high a level and create unnecessary friction. Choose a platform that supports the eIDs your signers actually use, integrates with your existing systems via API, and provides a full audit trail as well as secure archiving.

Roll out the solution one document workflow at a time—typically HR contracts or customer agreements—so employees can learn the process before it’s expanded. This provides a measurable starting point and makes it easy to adjust templates and roles before additional departments are brought on board. At the same time, be sure to define who is authorized to create and send documents for signing, and how signed files are archived, so you avoid having important agreements scattered across inboxes. Once the process is established in one place, it can be rolled out to procurement, management, and finance with minimal additional effort. With digital signing and a well-designed electronic signature system in place, the company can eliminate printing and scanning entirely while strengthening its legal position.

Esben Emborg
About the author

Esben Emborg

Product design, value creation, and security are key areas of interest for me. I have worked with digital solutions for more than 20 years at Copenhagen Airports, Visma, Twoday, and Addo Sign. Among other things, I co-authored UX-related requirements for the public tender behind MitID, Denmark’s national digital identity solution. I have also helped develop international digital certificates for seafarers in collaboration with the Danish Maritime Authority, as well as a wide range of digital case management solutions for both public and private organisations.

Today, I work at Addo Sign with communications and marketing, drawing on my experience in design and digital products to make complex topics easier to understand and more accessible.
View all posts by Esben Emborg