A contract has been agreed, but the final PDF is waiting in a board member’s inbox. A candidate must sign documents before the first day of work but has no account in the company’s system. HR has prepared a series of certificates, each of which must be opened, signed, and saved separately. Simply purchasing a signature service solves none of these problems.
First, answer two questions: what legal effect and level of evidence does the document require, and how should the signature work within the entire process? Only then should the company compare providers, identity verification methods, and integration options.
This article organizes the business and technical decisions. It is not legal advice. The organization’s lawyer should confirm the required form for a specific act, representation rules, and industry exceptions.
Four terms that should not be used interchangeably
The eIDAS Regulation defines electronic signature levels, while Polish law determines the formal requirements for specific acts. Four solutions are most common in business practice.
Simple electronic signature: an easy action and basic evidence
“Simple signature” is a market term for a basic electronic signature. It can be a typed name under a message, a selected consent checkbox, or a signature drawn on a screen. Its strength depends on the full context: how the person was identified, how access was secured, how the signature was connected to a specific version of the document, and which logs were retained.
This signature can be appropriate for low-risk documents for which neither the law nor the contract requires written form. A graphic signature in a PDF should not, however, be assumed to prove identity, file integrity, and the person’s authority on its own.
Advanced electronic signature: a stronger link between the person and the document
An advanced electronic signature must identify the signatory, be uniquely linked to that person, remain under the signatory’s control, and make later changes to the signed data detectable. In B2B and HR processes, it can combine identity verification, access through an individual link, and confirmation with an SMS code.
It is a strong candidate when the organization needs more robust evidence than a simple signature provides but does not need to preserve written form. The phrase “SMS signature” alone does not determine the eIDAS level. The company must check how the provider identifies the person, protects the signature creation data, and binds the signature to the document.
Qualified electronic signature: the equivalent of a handwritten signature
A qualified electronic signature is an advanced signature based on a qualified certificate and created using a qualified signature creation device. Under Article 25 of eIDAS, it has the legal effect of a handwritten signature. Article 78¹ of the Polish Civil Code states that an electronic declaration bearing such a signature retains electronic form equivalent to written form.
A qualified electronic signature is the appropriate starting point when written form is required, a high level of certainty about identity is needed, or the document must be handled across several EU countries. Special provisions still need to be checked: not every act can use ordinary written form, and some require, for example, a notarial deed.
Electronic seal: confirms the organization, not a specific person’s decision
A natural person creates a signature. A legal entity creates an electronic seal and uses it to confirm the origin and integrity of data. Under Article 35 of eIDAS, a qualified electronic seal benefits from a presumption of data integrity and correct origin.
A seal works well for documents generated in bulk by an organization, digital reproductions, and system communications. It does not automatically replace an authorized representative’s signature on a declaration of intent. Before using one, determine whether the document must confirm its source and integrity or the individual decision of an authorized person.
When is each signature type sufficient?
One signature type should not be assigned to the entire company. Build a matrix based on document type, required form, dispute risk, and how the participant is identified.
| Situation | Starting point for the decision | What to confirm |
|---|---|---|
| Operational consent, internal report, acknowledgment of policies | simple or advanced electronic signature | whether documentary form is sufficient and how the person and content version are established |
| Contract with no statutory written-form requirement | advanced or qualified electronic signature, depending on risk | contractual provisions, evidence policy, and representation of the parties |
| Contract or declaration requiring written form | qualified electronic signature | special provisions, authority, and the required delivery method |
| Employment contract concluded electronically | qualified electronic signature from both parties as a safe way to preserve written form | current labor law requirements and the employer’s procedure |
| Documents issued in bulk by an organization | electronic seal, sometimes a person’s qualified electronic signature | whether proof of origin or a personal declaration is needed |
| Digitization of paper employee documentation | employer’s qualified electronic signature or qualified electronic seal | requirements of the Polish Labor Code and employee documentation regulations |
The practical rule is simple: do not begin by asking “which signature should we buy?” Ask “which form does the document require, and what must we be able to prove in a dispute?” Article 25 of eIDAS does not allow a signature to be rejected as evidence solely because it is electronic or not qualified. This does not mean that every level preserves the form required by law.
How does signing with a person outside the company work?
A counterparty, candidate, or employee should not need an account in an internal system just to sign one document. The process can send a personalized link, confirm access through a second channel, display the correct file version, and direct the participant to the selected signature method.
Design the entire path, not only the “Sign” screen:
- the system prepares the document from an approved template and case data;
- a rule selects the signatories, order, and permitted signature type;
- the recipient receives a link and completes the required identity verification;
- the organization decides who pays for a one-time signature;
- the signature, rejection, or expiration status returns to the process;
- the signed file enters the contract, eTeczka (electronic personnel files), or system of record.
The test should also cover no response, an incorrect phone number, a change of representative, document rejection, and the need to send a corrected version. The full document life cycle is described in the guides Contract workflow in a company and Electronic employee files.
Does the signature currently happen outside the document workflow? Show us the file source, participants, and target archive. Discuss your signature process →
Batch signing does not mean automatic consent
Opening every contract, amendment, certificate, and HR document separately creates a bottleneck. The process can prepare a batch, verify data completeness, group documents by signatory, and start batch signing.
The person signing must retain control: they should see the scope of the batch, understand the significance of the operation, and approve it consciously. An organizational seal can be more appropriate for documents generated automatically. This is a decision about responsibility and legal effect, not only user convenience.
The evidence does not end with a signed PDF
An inspection or dispute requires a consistent evidence package. In addition to the final document, the process should retain:
- the content version provided to each person and its identifier;
- signatory data, the identification method, and the person’s role;
- the certificate, its validity status, and the result of signature or seal validation;
- the date, time, and—when needed—a qualified timestamp;
- the history of sending, opening, reminders, signature, rejection, and cancellation;
- proof of file integrity and the relationship to source documents;
- information about authority and the order of signatories;
- retention, access, export, and long-term evidence recovery rules.
Storing a visible image of the signature is not enough. Certificates expire, technologies change, and a file may be verified long after the process ends. When selecting a solution, check long-term validation, timestamps, and how validation material is maintained.
How to choose a provider without locking the process into one application
SimplySign, SIGNIUS, and DocuSign demonstrate different signature models: a mobile certificate, one-time signatures for external participants, a workflow platform, and integrations with trust services. They are examples to analyze, not interchangeable products. The signature level follows from the specific service and path used in the transaction, not the provider’s logo.
When selecting a provider, check:
- which signature and seal levels are available and which file formats they support;
- whether the qualified service and its provider appear on the relevant EU Trusted List;
- how a regular user and a one-time signatory are identified;
- whether the organization can pay for an external participant’s signature without requiring that person to buy it;
- whether the API supports sending, order, statuses, errors, cancellation, and file retrieval;
- which evidence, validation reports, and timestamps can be exported;
- where data is processed and how access control and retention work;
- how the solution handles document batches, multiple companies, and substitutes;
- how the SLA, support, billing, and exit from the service work without losing the archive.
The list of qualified services matters more than a marketing claim. In Poland, it is published by the National Certification Center, and the European Commission provides a browser for EU Trusted Lists.
Pre-launch checklist
- Do we have a catalog of documents with the required form and basis for the decision?
- Has a lawyer confirmed exceptions, representation, and rules for cross-border documents?
- Has each document been assigned a simple, advanced, or qualified electronic signature or an electronic seal?
- Does the process support external participants without an account in the company’s system?
- Do the rules define the order, substitutes, deadline, and rejection method?
- Does batch signing show the user the complete scope of the batch being approved?
- Does the source system receive the signed file, status, date, and validation report?
- Does the archive preserve integrity, history, permissions, and the data required for later verification?
- Have link expiration, an integration error, a change of signatory, and resending been tested?
- Can the provider be changed or a second signature type added without rebuilding the entire process?
The role of automation: signature as a stage, not a separate inbox
In AMODIT, a document moves from preparation and approval to the correct signature and then returns to the contract, HR documentation, mailroom, or system of record. AMODIT TrustCenter supports signatures and work with external participants, while integrations connect the process with services including SimplySign, SIGNIUS, and DocuSign. The Electronic Signatures solution page describes the implementation scope.
The processes we support have handled more than 1.5 million signed documents. This scale includes employee documentation, contracts, and other documents embedded in company processes.
Before a contract is signed, the AI Agent for contract review and revision can review the content and insert proposed revisions, with a person approving the result. We process AI data in a controlled environment in EU regions; the models are not trained on client data, which ensures compliance with the GDPR and the EU AI Act. The final version approved in the process moves to signature without manual transfer between tools.
Automation manages roles, deadlines, statuses, and exceptions, but it does not choose the required legal form for the organization. The people responsible for legal, HR, security, and the process owner establish that rule; the system applies it consistently to every document.
FAQ: electronic signatures in business
Is a simple electronic signature valid?
A signature cannot be denied legal effect or evidentiary value solely because it is electronic or not qualified. That does not mean every simple signature preserves the form required for a specific act. The law, contract, and evidence of identity, intent, and document integrity all matter.
Does an SMS code make a signature advanced?
Not automatically. An SMS can be part of authentication, but the signature level depends on the entire mechanism: identification of the signatory, the person’s control over the signature creation data, and the ability to detect changes to the document.
Is a qualified electronic signature required for every contract?
No. Many contracts do not require written form, but the parties can require it in their arrangements or select a higher level because of risk. A qualified electronic signature is essential when the organization wants to preserve a form equivalent to written form electronically.
Can an electronic seal replace a board member’s signature?
That rule should not be assumed. A seal confirms the origin and integrity of the organization’s data, while a signature binds a document to the natural person making the declaration. The correct option depends on the document and representation rules.
Can several signature providers be connected in one process?
Yes. The process can route a document to different services based on the required form, country, signatory role, or certificate held. The condition is consistent integration of statuses, validation, errors, and the archive so users do not need to move files manually.