Key takeaways
- India's core eSignature exclusions are listed in the First Schedule to the Information Technology Act, 2000.
- Blocked categories include powers of attorney, trusts, wills, testamentary documents, negotiable instruments other than cheques, and property sale or conveyance contracts.
- Screen the legal effect of a document, not just its title or file name.
- Use a three-outcome workflow: approved for eSignature, legal review required, or prohibited from standard eSignature.
- ZiaSign can support the safe execution workflow for agreements that pass screening by combining contract intelligence, signing, tracking, and document evidence.
Which documents cannot be signed electronically in India in 2026?
In India, most business agreements can be signed electronically, but a few document categories are expressly excluded under the Information Technology Act, 2000. The core list is in the First Schedule to the Act, available through the official India Code repository: negotiable instruments other than cheques, powers of attorney, trusts, wills and testamentary dispositions, and contracts for sale or conveyance of immovable property or any interest in such property.
For founders, legal teams, and contract administrators, the practical rule is simple: do not send these documents through a standard eSignature flow unless Indian counsel has confirmed a legally acceptable route. For background on validity outside these exclusions, see our practical guide to whether electronic signatures are legally valid in India.
Electronic signature: a legally recognised method of authenticating an electronic record, subject to the Information Technology Act and applicable rules.
Digital signature: a specific type of electronic signature based on asymmetric cryptography and certificates issued under the Indian framework. The distinction matters in workflow design; this related guide explains digital signature vs electronic signature in India.
The excluded categories, translated into contract-team language
| Excluded category under Indian law | Common examples teams see | Workflow decision |
|---|---|---|
| Negotiable instruments other than cheques | Promissory notes, bills of exchange | Do not route through ordinary eSignature. Get legal and finance review. |
| Power of attorney | General POA, special POA, authority to represent before a registrar or bank | Use wet ink and required notarisation, stamping, registration, or institutional process where applicable. |
| Trusts | Trust deed, declaration of trust, amendment creating or changing trust obligations | Keep outside standard eSignature unless counsel approves a specific electronic process. |
| Wills and testamentary dispositions | Will, codicil, document distributing assets after death | Do not eSign. These usually require formal execution and witnesses. |
| Contracts for sale or conveyance of immovable property or any interest in it | Sale deed, agreement to sell land or flat, conveyance deed, mortgage or transfer of property interest | Treat as excluded or high-risk. Follow stamp, registration, and physical execution requirements. |
| Other classes notified by government | Any future notified exclusion | Check the latest official text before changing policy. |
First Schedule: the part of the Information Technology Act that lists transactions and documents to which the Act does not apply. If a document falls inside this schedule, the general legal recognition given to electronic records and electronic signatures under the Act is not enough.
A cheque is carved out from the negotiable-instrument exclusion, but that does not mean every cheque-related process can be handled like an ordinary SaaS contract. Banking law, bank procedures, and RBI-regulated payment systems may apply; teams should verify current requirements through official sources such as the Reserve Bank of India.
Why are these documents excluded from eSignature?
The excluded categories share one feature: they usually affect high-value rights, third-party reliance, inheritance, property title, or formal authority. Indian law has historically required additional safeguards for these documents, such as witnesses, stamping, registration, notarisation, or presentation before a public office.
The Information Technology Act gives legal recognition to electronic records and signatures, but it does not override every older formality. The Ministry of Electronics and Information Technology maintains the broader electronic governance and IT law context through MeitY, while licensed digital signature infrastructure is overseen by the Controller of Certifying Authorities.
This distinction prevents a common mistake: assuming that a stronger signature method automatically makes every document eSignable. Even a cryptographic digital signature may not cure a document that the Act excludes or a document that must be registered, stamped, witnessed, or executed in a prescribed physical form.
Can related commercial agreements still use eSignature?
Yes, many related business agreements can still use eSignature if they do not fall into an excluded category and no sector-specific rule requires another method. The label on the document is less important than what legal rights it creates.
Use this decision table before sending:
| Document | Usually suitable for eSignature? | Main caveat |
|---|---|---|
| SaaS subscription agreement | Yes | Check authority, data protection, and stamp duty treatment where relevant. |
| NDA | Yes | Ensure signer identity and audit trail are captured. |
| Employment offer letter | Yes | Check internal HR policy and any state-specific employment documentation. |
| Vendor services agreement | Yes | Confirm it does not include a POA, property transfer, or negotiable instrument. |
| Board consent or shareholder approval | Often, but review | Company law filings or MCA processes may impose separate requirements; verify through the Ministry of Corporate Affairs. |
| Lease, sale deed, agreement to sell, mortgage, or conveyance | High-risk or excluded | Documents creating or transferring property interests need legal review and often registration. |
Property-related documents need special care. A facilities management contract for office cleaning is not the same as a lease deed. A software implementation agreement for a real-estate company is not the same as an agreement to sell a flat. Screen the legal effect, not the industry.
For a broader procurement checklist, see our guide on how to choose eSignature software in 2026.
How should teams screen agreements before sending them for eSignature?
A good screening workflow is short enough for operations teams to follow and strict enough to stop prohibited documents. Use it before a document enters any signing tool.
- Identify the document type. Ask whether it is a contract, instrument, deed, declaration, authority, consent, notice, or statutory form.
- Check for exclusion triggers. Look for property transfer, POA language, trust creation, testamentary language, promissory payment language, or bill of exchange wording.
- Check formalities outside eSignature law. Ask whether stamping, registration, notarisation, witnesses, board process, government filing, or bank process applies.
- Confirm signer authority. Verify whether the signer is authorised under board resolution, employment role, delegation matrix, or POA. If authority itself depends on a POA, pause.
- Choose the signing method. Use electronic signature only if the document passes the exclusion and formality checks.
- Preserve the evidence. Store the final document, audit trail, signer identity data, timestamps, and approval history.
The workflow should have three outcomes: approved for eSignature, legal review required, or prohibited from standard eSignature. Do not create a vague fourth bucket called urgent. Urgency is not a legal category.
If your approval path is inconsistent across teams, start with the roles and controls in this contract approval workflow guide.
What controls reduce accidental misuse of eSignature?
The main risk is not that a legal team intentionally eSigns a will or sale deed. The real risk is that an operations user uploads a document with a harmless-looking file name and sends it before legal review.
Add these controls:
- Intake questions before upload: document type, counterparty, purpose, property involvement, POA involvement, payment instrument involvement, and jurisdiction.
- Block words and review words: will, testament, codicil, power of attorney, POA, trust, sale deed, conveyance, immovable property, mortgage, promissory note, bill of exchange.
- Mandatory legal approval for red-flag documents: do not let business users override the result.
- Separate templates: keep approved eSign templates distinct from deed, property, estate, and authority documents.
- Audit trail retention: preserve who uploaded, approved, sent, viewed, and signed the document.
Audit trail: a record of events that shows how a document moved through the signing process, including timestamps, signer actions, and completion status. For implementation details, read what an eSignature audit trail should contain.
AI can help classify documents and surface risky clauses, but it should not be the final legal authority for excluded categories. Use human approval for red flags, and apply the controls in our AI legal document risk checklist.
Where ZiaSign fits in this workflow
ZiaSign is Zettaura's live AI contract intelligence and eSignature platform for sending, signing, tracking, and understanding agreements in one secure workflow. Its role in this problem is not to make excluded documents magically valid. Its role is to help teams build a safer front door for contract execution.
Use ZiaSign as the execution layer after your screening policy is defined:
- Route ordinary agreements such as NDAs, vendor contracts, offer letters, and service agreements through a consistent signing workflow.
- Use AI contract intelligence to understand agreement content before send, especially document type, parties, dates, and obligations.
- Track signing status centrally instead of relying on email forwards and chat screenshots.
- Preserve the completed agreement and signing evidence in the same workflow.
- Keep legal and operations teams aligned on which documents are eligible for eSignature and which must be escalated.
For teams moving from manual files to structured document operations, this connects naturally with broader document workflow automation for small business. Zettaura builds focused AI products for everyday workflows; you can see the wider product context at Zettaura products.
Where this leaves you
Your eSignature policy should begin with the exclusion list, not with tool selection. Mark negotiable instruments other than cheques, powers of attorney, trusts, wills, testamentary documents, and property sale or conveyance contracts as blocked or legal-review-only.
Next step: turn the list into a one-page intake checklist and apply it before every send. Once the workflow is clear, use ZiaSign for the agreements that pass screening and need a secure, trackable signing process.
Frequently asked questions
Are electronic signatures legally valid in India?
Yes, electronic signatures are generally recognised in India under the Information Technology Act, 2000. The main exception is that the Act does not apply to the document categories listed in its First Schedule, such as wills, powers of attorney, trusts, certain negotiable instruments, and property sale or conveyance contracts.
Can a power of attorney be signed electronically in India?
A power of attorney is one of the excluded categories under the First Schedule to the Information Technology Act. Treat it as unsuitable for ordinary eSignature and follow the applicable wet-ink, stamping, notarisation, registration, or institutional process after legal review.
Can an agreement to sell property be eSigned in India?
Contracts for sale or conveyance of immovable property, or any interest in such property, are excluded under the Information Technology Act. An agreement to sell land or a flat should therefore be treated as blocked or legal-review-only for eSignature workflows.
Can NDAs and vendor agreements be eSigned in India?
Most NDAs and vendor service agreements can be eSigned if they do not include excluded elements such as POA language, property transfer, trust creation, testamentary terms, or negotiable-instrument obligations. Teams should still check signer authority, stamp duty treatment, and audit trail requirements.
Does using a digital signature make an excluded document valid?
Not by itself. A digital signature is a stronger form of electronic signature, but it does not override exclusions in the Information Technology Act or separate requirements for stamping, registration, witnesses, notarisation, or government filing.
ZiaSign is live today. Learn more about ZiaSign or explore the full Zettaura portfolio.
