All blogs

How to reduce risks when signing and auditing corporate documents

2026-11-12 | 8 min Digitization

Although a company may store its documents electronically, during an audit it often still has to search through emails to find approvals and verify which version was signed. Audit readiness depends on how documents are created, who makes decisions regarding them, and what supporting materials remain accessible. A managed digital document process helps preserve this context during day-to-day operations.

Management needs to document how a business case was handled. The contract is available, but the amendment is with a colleague at a branch office. Internal approval took place by email, and the document was still edited before signing. Without further verification, it is unclear whether the decision applied to the final content.

The company may eventually find all the information. Until it does, lawyers, the sales team and administration spend time on the case. The same situation can also arise during an external audit, a complaint, a dispute or an internal review.

The risk involved in signing and auditing is reduced by a process that connects

  • the specific version of the document,
  • the relevant approvals,
  • the signing documents
  • and the history of important events.

Storing a file electronically does not establish these connections. For a larger company, it is therefore important to be able to explain the course of a case even after time has passed and the team has changed. This should not depend on someone who still remembers how each document was handled.

Risk arises in everyday work

Traceability problems often become apparent only when supporting documents or an explanation need to be provided. They are usually caused by common working practices:

  • unclear version labels,
  • sending attachments outside the agreed workflow
  • or approvals that cannot be clearly linked to a document.

When there are only a few cases, the context can be pieced together through personal communication. With hundreds of contracts, multiple branches and external parties involved, this approach becomes more demanding. An employee leaving or a reorganisation can make it even harder to trace earlier decisions.

The company therefore needs to distinguish between a stored document and a verifiable record of how it was processed. Finding a file may not answer who made the decision, what content they reviewed and what happened next.

The article on the overview of document processes discusses the importance of available statuses and responsibilities. During a review, this perspective is extended to include history that helps explain previous steps.

Electronic signing requires rules based on document type

Uncertainty about the legal effects of a signature can delay the digitalisation of an entire business area. The company is unsure which documents may be signed electronically and which method is appropriate. Some documents remain on paper, while individual branches introduce their own procedures.

Under Article 25 of the eIDAS Regulation, a qualified electronic signature has the same legal effect as a handwritten signature. An electronic signature also cannot be denied legal effect or admissibility as evidence in legal proceedings solely because it is electronic or does not meet the requirements for a qualified electronic signature.

This does not mean that every method of electronic confirmation is suitable for every document. The required form of the legal act, the signatory’s identity, their authority to act and the link between the signature and the specific content all need to be assessed. The label “signature by SMS” alone does not determine the legal validity of a solution.

A practical step for management is to agree on rules for the main document groups with the legal team, IT and the people responsible for the relevant business area. Requirements may differ for customer contracts, personnel documents and service reports. Shared rules also reduce the number of cases in which the organisation has to address the same question from scratch repeatedly.

What the company needs to be able to demonstrate during a review

The supporting documents required depend on the document type, process and applicable requirements. A few basic questions can help with an initial assessment.

Question

What the company needs to keep under control

Which document was approved and signed?

The relevant version and associated attachments

Who approved the document?

The decision linked to the content that was reviewed

Who signed the document?

The signing documents and relevant authority to act

What changed during processing?

The history of important changes and decisions

When did the key events take place?

Time records with an appropriate level of reliability

Where are the supporting documents?

Availability to authorised people for the required period

 

If answering the questions requires contacting several people and searching their inboxes, there is room for the company to improve its process. An audit log, also known as an audit trail, records selected events that occur while a document is being handled.

For these records to be useful, it must be clear which case and version they relate to, who can access them and how they are protected against unauthorised changes. A standard application log with a date is not automatically a qualified electronic time stamp. The specific mechanisms should be selected according to the process requirements.

Automate Your Business Processes with SIGNATUS

Discover how digital signing can accelerate your processes, reduce paperwork, and improve the user experience for both your employees and customers.

Contact us

Weak points often emerge when a document changes

The standard process may be well managed. A document is prepared, approved and signed. Uncertainty arises only when a customer requests a change or some supporting documents are added later.

For example, the sales team revises a contract after internal approval, a payment term changes and the new wording is sent to the customer for signature. However, the original approval remains attached to the older version. During a later review, the company finds the signature and the manager’s approval. It still needs to verify whether the manager approved the terms that the customer actually signed. A controlled process should therefore define how to handle such a situation.

Situation

What the process needs to define

Document changed after approval

Which changes require a new review

Approver unavailable

Who can make the decision and within what scope

Attachment added later

How to link the attachment to the correct version

Document rejected or returned

Who will ensure the next steps are taken

Transfer between applications

Which supporting documents and identifiers must be retained

 

The goal is for the company to recognise significant exceptions, assign them to a responsible person and document how they were resolved. These rules should be part of everyday work, rather than an additional investigation before an audit.

Traceability must continue to work after organisational changes

Documents may still be needed long after the original team has changed. Responsibility for the business area should therefore not be tied only to an individual email inbox or one employee’s knowledge.

The company needs clarity on access rights, retention rules and how to retrieve supporting documents if the system or supplier changes. Relevant information must remain readable and usable for the required period.

For example, personnel processes involve data that not all employees should be able to access. In customer-related business areas, the content needs to be linked to the right person and business case. Traceability and data protection should be designed together.

The European Commission’s GDPR principles remind organisations to retain personal data only as long as necessary, considering the purpose and legal obligations. One retention period for all contracts, reports and personnel records may therefore be inappropriate.

Retention rules must also cover cases where supporting documents need to be kept for an ongoing dispute or another legal obligation. A designated person should decide how these rules apply.

Audit readiness can be checked using a sample of cases

An initial assessment can start with a few representative cases: a completed contract, a document returned for completion and a case with changed terms.

For each one, check:

  • whether the correct version of the document and its attachments are available,
  • whether the approvals relate to the relevant content,
  • whether the supporting documents for signing can be traced,
  • whether changes and exceptions can be explained,
  • how much time and how many people are needed to gather all the supporting documents.

Measure the time needed to document a case and the share of cases with missing information. These figures help prioritise changes and assess their benefits.

Assess the readiness of your company’s processes and document management

If a review repeatedly requires tracing approvals, signatures or versions, start with the business area where missing information has the greatest commercial or legal impact. SIGNATUS experts can help you assess how digital workflows support document traceability and control. Requirements should be aligned with your legal team, IT and the relevant business owners.

Frequently Asked Questions about the European Digital Identity Wallet (EUDI Wallet)

The electronic form of a signature is not, in itself, a ground for denying its legal effects. Under the eIDAS Regulation, a qualified electronic signature has an effect equivalent to that of a handwritten signature. In the case of a specific contract, it is also necessary to assess the required form, the method of signing, and the authority of the signatory to act.

An electronic signature is associated with the signing of specific content. An audit trail captures selected events during its processing, such as approval, return, or submission. An audit trail does not replace the signature; rather, it helps to explain the broader course of the document process.

A signed PDF can serve as an important piece of evidence; however, it may not necessarily explain the internal approval process, changes made prior to signing, or the authorization to act on behalf of the company. The extent of documentation required depends on the subject of the review and the specific requirements for the document in question. Therefore, the entire case must be evaluated, rather than just the final file.

There is no single retention period that applies to all documents. It depends on the type of document, its purpose, applicable legal obligations, and the need to protect legal claims. A company should establish retention policies and ensure that relevant documentation regarding signatures and processes remains accessible for the required duration.

No. A digital workflow can support approvals, access management, and traceability. However, compliance also depends on the chosen signature solution, the legal basis for data processing, retention policies, and the actual implementation of the process. The setup must be assessed in the context of the specific business function.