Transaction rules are decisive. The answer to who must use e-signature does not depend solely on job title; it varies according to the signature type required in specific electronic application, declaration, or authorization processes. Reviewing the transaction rule and signature authority before applying reduces the risk of making the wrong choice.
Who Must Use E-Signature: Scope and Options
The e-signature requirement does not arise solely from a person being a lawyer, financial advisor, or company officer. The obligation emerges when the relevant institution's electronic transaction rule requires signing with a qualified electronic certificate. Law No. 5070 on Electronic Signatures defines the legal framework of secure electronic signatures; however, it does not promise the same outcome for every document and transaction. The current condition on the transaction screen is decisive.
For example, an authorized person who will submit an electronic application on behalf of a company should first check which signature type the application accepts and how the representation authority will be demonstrated. In roles such as financial advisory, customs brokerage, or tender authorization, the obligation is tied not to the name of the profession but to the rule of the specific process being carried out. This distinction is small but forms the backbone of the decision. A wrong assumption can interrupt the document flow.
An electronic signature is a tool that associates the identity of the signer in the electronic environment; it is not the same concept as an ordinary checkbox or a typed name. The person signing the document and the person preparing the transaction within the company may be different. Therefore, authority, document type, and transaction purpose should be considered together. To understand the scope, reviewing the usage framework of electronic signatures establishes a decision-making foundation.
Who Must Use E-Signature: Conditions to Compare
The most reliable way to determine whether it is mandatory is to compare the institution's current transaction announcement and document condition. A professional card, company role, or tax status alone is not a sufficient indicator. The person making the application, the person signing, and the represented legal entity may not be the same. When these three roles diverge, matching the authorization document with the e-signature holder requires particular attention.
| Check area | Question to examine | Decision impact |
|---|---|---|
| Transaction type | Does the institution require a qualified electronic certificate? | The obligation becomes clear |
| Signature holder | Is the person signing the document authorized? | Representation risk decreases |
| Document scope | Is there a legal exception or special form requirement? | An alternative path is determined |
As of 2026, institutions' transaction conditions may change, so deciding based on an old screenshot or online comment is not reliable. Even if two people work within the same company, one may only handle preparation while the other holds signature authority. Price, certificate duration, and delivery method should also be confirmed from the current catalog. In package comparison, placing transaction frequency and authority structure side by side leads to a healthier choice.
When deciding, a short who must use e-signature checklist is useful: Is the institution's rule written, is the signer identified, does the document have a special form requirement, and does the certificate period align with the business plan? If any of these four questions is unclear, postponing the purchase step is more prudent. Duration and package selection notes help evaluate commercial terms separately.
Practical Application Steps: Comparison and Example Scenario
In an example scenario, an authorized representative of a business sees that the institution's electronic document acceptance condition requires a qualified electronic certificate. This requirement does not automatically arise for the employee preparing the document in the same business; the signing duty lies with the representative. The decision is made based on the signature authority on the document, not the job description. If there is uncertainty, the institution's current documentation and application condition should be checked.
First, confirm the electronic signature requirement of the transaction from the official announcement.
Then determine which natural person will sign the document and their representation authority.
Next, compare certificate duration, package content, and current application conditions.
Finally, complete the application with the transaction owner's information.
The balance here is clear: If there is a requirement, a certificate purchased in the wrong person's name does not solve the transaction; if there is no requirement, purchasing based solely on assumption can create unnecessary cost. Electronic signature use can simplify some document processes, but separate rules may exist for transactions with special form requirements. Check the current package content, price, and application conditions in the Nagdos e-signature catalog.
Frequently Asked Questions
Who Must Use E-Signature and Which Processes Does It Cover?
Lawyers filing lawsuits through UYAP, authorized persons submitting bids in EKAP tenders, company executives approving MERSIS records, public personnel using DYS, and customs brokers issuing customs declarations must use e-signature. The obligation depends on the digital platform's requirement rather than the job title.
What Does Who Must Use E-Signature Mean?
E-signature is issued only to natural persons; it cannot be produced directly on behalf of a legal entity. Therefore, personal certificates are obtained for company managers, board members, or specially authorized representatives who are authorized to represent the company individually or jointly in the signature circular.
Does Mobile Signature Replace E-Signature in Mandatory Transactions?
Under Law No. 5070, secure electronic signature and mobile signature have the same legal validity. However, since EKAP, UYAP, or certain customs software may only accept USB token-based Qualified Electronic Certificates (e-signature) due to technical infrastructure, the platform's technical guide should be checked.
