Blog – Digital Signing, eID & Compliance | Addo Sign

Regulatory Compliance for Digital Signatures | Addo Sign

Written by Esben Emborg | 27. jul. 2026 10.15.00

To comply with legal requirements when digitally signing with an e-signature, it is important to treat compliance as a repeatable process rather than a one-time task. Start by identifying which regulations apply to your documents, then determine the signature level according to eIDAS, and finish by creating documentation that can withstand an audit. This approach to regulatory compliance makes it possible to scale the number of signatures without a corresponding increase in risk. Below, we’ll walk you through six specific steps you can take within your organization to make compliance an integral part of the signing workflow rather than a manual check that’s performed too infrequently.

Step 1: Identify the Relevant Regulatory Frameworks

Start by identifying which regulations apply to each document type. eIDAS determines the legal validity of signatures, GDPR regulates the processing of personal data, and industries such as finance and the public sector often have additional requirements. For organizations in the public sector, for example, there may be specific requirements for record-keeping and retention that must be incorporated into the process from the outset. A review by document type makes it clear where stricter requirements apply and where a standard process is sufficient. Involve legal, IT, and business stakeholders in the assessment so that you do not overlook a requirement that only becomes apparent during practical use. The result should be an overview that links each document type to the regulations it is subject to and that can be updated as the regulations change.

Step 2: Choose the Right Signature Level

Once the regulatory framework is known, you must determine whether the document requires a simple, advanced, or qualified signature. Most business agreements can be validly entered into with an advanced signature, while certain types of cases require the highest level. Use our overview of EIDAS and signature levels to match the document type with the appropriate signature level, ensuring you neither over- nor under-specify. A well-documented choice for each document type also makes it easier to justify the decision during an audit.

Step 3: Ensure lawful processing of personal data

The signature itself handles signature validity, but you must also ensure that personal data is processed lawfully. This requires a legal basis for processing, data minimization, and retention periods, which we discuss in more detail in the article on GDPR and e-signatures. If you use an external provider, a data processing agreement must be in place, and you should be aware of the chain of subprocessors so you know where the data is actually being processed. Pay particular attention to whether information is transferred to countries outside the EU, as this triggers additional requirements. When data protection is built into the workflow from the start, you avoid it becoming an obstacle every time a new document type is rolled out.

Step 4: Document Operations and Controls

Compliance requires proof, not just intent. An audit trail documents every single signature, while the underlying operations should be verified by an independent auditor. An ISAE 3000 statement provides precisely this independent evidence that controls for security and data processing work in practice and not just on paper. Together, the audit trail and the auditor’s report constitute the documentation typically required by an audit. A useful principle is that if something cannot be documented, it cannot be considered compliant; therefore, you should factor documentation into the design of a process from the very beginning. This saves time when an auditor, a customer, or a regulatory authority requests insight, because the evidence is already readily available.

Step 5: Clearly assign responsibility within the organization

Compliance often fails because no one owns it. Even if operations are outsourced to a vendor, the data controller retains overall responsibility for ensuring that the processing is lawful. Therefore, designate a specific person responsible for the signing process, determine who approves new document types, and ensure that vendor agreements are revised when changes occur. It is also beneficial to describe what should happen if a check fails, so that responsibility extends not only to day-to-day operations but also to situations where something goes wrong. A clear division of responsibilities ensures that the other steps are actually carried out and maintained, rather than falling through the cracks.

Step 6: Make compliance an ongoing routine

Legislation and signature technology are constantly changing, so compliance should be reviewed at regular intervals. Review your document types, verify that signature levels still meet requirements, and update data processing agreements in the event of changes at the provider. With a standardized digital signing platform, each of these steps becomes a built-in routine rather than a manual check, and you can document compliance on an ongoing basis rather than only during an audit. Set a fixed interval for the review—for example, once a year or whenever regulations change—and note each time what was assessed and by whom. This way, compliance becomes a visible trail within the organization rather than an assumption that no one can document afterward.