Contract Execution in India: Stamp Duty, Aadhaar eSign and What CLM Does Not Handle

A contract is not "executed" in India just because both sides clicked sign. Indian law checks three separate things: a valid signature, paid stamp duty on the instrument, and, for a specific list of documents, registration with a Sub-Registrar. Most global e-signature and CLM tools were built for a market where the first item is close to the whole story. In India it is one of three, and the other two are where deals quietly go wrong. This guide (published by Adira, which makes CLM software, including e-signing and e-stamping workflows, so we have a commercial interest in you trusting execution tools, but the explanation below stands on its own) walks through what each requirement demands, what an e-sign or e-stamp tool automates, and what no software can do for you.

The three-part test Indian law runs on every contract

Ask three questions about any contract before you execute it, in order, because passing the first tells you nothing about the other two: is the signature valid (wet ink, a Digital Signature Certificate, or Aadhaar eSign, used correctly for the document type)? Has stamp duty been paid on the instrument? Does the document need registration, compulsory for a specific list of property instruments but irrelevant for most commercial contracts?

A contract can pass the first test and fail the other two. An e-signed vendor MSA with a flawless DocuSign audit trail is still an unstamped instrument if nobody paid the duty, and it is still not evidence of a property transfer if the underlying deed was never registered. Each requirement sits in a different statute and is checked separately if the contract is ever produced in court or before an arbitrator.

One: does the signature actually hold up

Section 5 of the Information Technology Act, 2000 gives an electronic signature the same legal weight as a handwritten one wherever a law asks for a signature:

"Where any law provides that information or any other matter shall be authenticated by affixing the signature... such requirement shall be deemed to have been satisfied, if such information or matter is authenticated by means of electronic signature affixed in such manner as may be prescribed by the Central Government." Source: Section 5, Information Technology Act, 2000

Section 10A does the same job for the contract itself, confirming a contract formed by electronic proposals and acceptances is not unenforceable merely for being electronic. Indian courts do not need pen-on-paper for a binding contract to exist. In Trimex International FZE Ltd v Vedanta Aluminium Ltd, (2010) 3 SCC 1, the Supreme Court held that a binding contract, including a valid arbitration clause, was formed through a chain of emails alone, because the essential terms were agreed and acceptance was unequivocal. Full judgment on Indian Kanoon.

Not every electronic signature carries the same weight, though. Only a Digital Signature Certificate (DSC) and Aadhaar eSign sit inside the IT Act's Second Schedule as "secure electronic signatures," and only those get the Section 85B presumption under the Evidence Act, 1872: the court presumes the signature was affixed with intent to sign, and the other side has to prove otherwise. A typed name or click-to-accept is still valid to form a contract under Section 10A, but if the other side denies it later, you carry the burden of proof yourself. A decision flow for choosing between DSC, Aadhaar eSign, and click-to-sign is on electronic signature validity in India.

Two: has stamp duty been paid on the instrument

This is the step most e-signing workflows skip, because nothing in a click-to-sign flow forces the question. Stamp duty is a tax on the document, not the signing method. Section 2(14) of the Indian Stamp Act, 1899 defines "instrument" as:

"every document, by which any right or liability is, or purports to be, created, transferred, limited, extended, extinguished or recorded" Source: Section 2(14), Indian Stamp Act, 1899

That definition has never said "paper." Section 3 makes every listed instrument "chargeable with duty of the amount indicated in that Schedule as the proper duty therefor," Section 3, Indian Stamp Act, 1899, and some states say the electronic point expressly. The Explanation to Section 2(l) of the Maharashtra Stamp Act, 1958, added in 2005, reads:

"The term 'document' also includes any electronic record as defined in clause (t) of sub-section (1) of section 2 of the Information Technology Act, 2000." Source: Section 2(l), Maharashtra Stamp Act, 1958

Timing matters as much as liability. Section 17 of the Indian Stamp Act requires instruments executed in India to be stamped "before or at the time of execution," read by courts as practically simultaneous with signing. Section 17, Indian Stamp Act, 1899. On paper, someone has to physically buy stamp paper before printing, so stamping happens first by default. E-signing removes that checkpoint; two people can sign from their phones in under a minute with nobody asking whether duty has been paid.

Skipping it does not void the contract, but it comes close when it matters most. Section 35 bars an unstamped instrument from being "admitted in evidence for any purpose... or acted upon, registered or authenticated," unless the deficient duty and a penalty are paid first. Section 35, Indian Stamp Act, 1899. Arbitration clauses got a partial reprieve: a seven-judge Constitution Bench, in In Re: Interplay Between Arbitration Agreements and the Indian Stamp Act, 1899, Curative Petition No. 44 of 2023 (2023 INSC 1066, decided 13 December 2023), held that an arbitration agreement inside an unstamped contract is not void for that reason alone; the defect is curable, and stamping is not a gatekeeping question when a court appoints an arbitrator under Sections 8 or 11 of the Arbitration and Conciliation Act, 1996. Full judgment, 2023 INSC 1066. That narrowed one risk; it did not remove the duty, the penalty, or the Section 35 bar for the contract itself. Rates and full e-stamping mechanics are on stamp duty on electronic contracts in India and stamp duty on e-signed contracts.

Three: does this document need to be registered

Most commercial contracts, NDAs, SaaS orders, MSAs, never touch this. It bites only when a document transfers or creates a right in immovable property. Section 17(1) of the Registration Act, 1908 makes registration compulsory for, among other things, "instruments of gift of immovable property" and "non-testamentary instruments which purport or operate to create, declare, assign, limit or extinguish... any right, title or interest... of the value of one hundred rupees and upwards, to or in immovable property." Section 17, Registration Act, 1908. Skip it, and Section 49 says the document cannot "affect any immovable property comprised therein" or "be received as evidence of any transaction affecting such property," unless registered. Section 49, Registration Act, 1908. A signed and stamped sale deed that was never registered still fails to transfer title. Full detail, including the 11-month lease convention, is on when does a contract need registration.

What an e-sign or e-stamp tool automates, and what it flatly cannot touch

E-sign and e-stamp platforms are genuinely useful for the first two requirements, up to a point. They route a document to a licensed Certifying Authority (CA) or e-Sign Service Provider (ESP) for a DSC or Aadhaar eSign, capture the audit trail Section 85B disputes depend on, and, for stamping, submit an application to SHCIL or a state portal and attach the resulting certificate.

What none of them can do is decide, on their own, that a document is legally allowed to be signed this way. Section 1(4) of the Information Technology Act says plainly: "Nothing in this Act shall apply to documents or transactions specified in the First Schedule." Section 1(4), Information Technology Act, 2000. The First Schedule excludes a negotiable instrument other than a cheque, a power of attorney, a trust, a will, and, until a narrow 2022 amendment removed it, a contract for sale or conveyance of immovable property. A platform's audit trail and certificate chain do not fix a document the IT Act never recognised as electronic; they just produce a well-documented invalid signature. The full, current list is on which documents cannot be signed electronically in India.

The same limit applies downstream. An e-stamp certificate proves duty was paid; it does not decide which Schedule article applies, or whether your agreement secretly fits a higher, value-linked rate instead of the flat residuary fee. No e-sign or e-stamp tool can register a sale deed for you either, since that generally still requires the parties, or an authorised representative, to physically appear before the Sub-Registrar. A CLM built for the US or UK market makes this worse by design: with no general stamp duty there, "signed" really is the finish line, so the same tool imported here marks a contract "fully executed" the moment the last signature lands, with no prompt about duty or registration, a gap that surfaces only months later, in front of a court.

How Adira's e-signing and e-stamping fits, and what it does not remove

Adira's paid plans (Practice at $89 to $109 per seat per month, Firm at $179 to $219, Enterprise on custom pricing, 7-day trial, as published on adiralaw.com, last verified 4 September 2026) build e-signing and e-stamping around the three-part test above: routing a document to a DSC or Aadhaar eSign flow through a licensed CA or ESP where the deal calls for the Section 85B presumption, initiating e-stamping through SHCIL or the relevant state portal before signing, and tracking execution status, including whether registration applies, across states in one place.

None of that changes who owes the tax. Stamp duty is a statutory liability of the parties, set by the Indian Stamp Act and the applicable state Act. Software can make it easier to see that duty is owed and keep the certificate attached to the record. No CLM, Adira included, can pay that liability away or make an under-stamped instrument admissible by itself. You can check whether a draft contract's execution clause addresses this, for free, using Weave, which flags missing signature, stamping, or registration mechanics on the document itself.

Red flags in an execution workflow

Normal	Red flag	Why it matters
A named party owns e-stamping, with a deadline before signing	"Stamp duty, if applicable, shall be borne by the Parties," no process named	"The Parties" is not one person with a task; nobody does it
DSC or Aadhaar eSign used for a high-value or contentious contract	Only a typed name or click-to-sign used on a large deal	You lose the Section 85B presumption and carry the full burden of proving authenticity
Document checked against the First Schedule before e-signing	A power of attorney, will, or property deed e-signed without checking	The signature is legally meaningless for that document
E-stamp certificate's UIN attached to the signed document	Only a signature audit trail exists, nothing on stamp duty	The instrument still faces the Section 35 admissibility bar
Stamping happens before or with signing, same workflow	"We will sort out stamping later if we need to produce it"	Section 17 requires stamping before or at execution; late means a penalty
Registration flagged before the deal is treated as closed	A property document signed and e-stamped, registration left as an afterthought	Section 49 means it still cannot transfer title or serve as evidence

Execution clause: bad versus better

Bad: "This Agreement may be executed and delivered electronically by both Parties, and such execution shall be valid and binding for all purposes, with applicable stamp duty, if any, borne by the Parties."

What is wrong: it treats "electronic execution" as one undefined thing, names no state or Schedule article for stamp duty, assigns the duty to nobody in particular, and says nothing about registration if the deal touches property.

Better: "This Agreement is executed in electronic form at [City, State], by Digital Signature Certificate or Aadhaar eSign within the meaning of Section 3A of the Information Technology Act, 2000, except that this clause shall not apply to any document falling within the First Schedule, which shall require physical signature. Stamp duty is payable under Article 5 of Schedule I to the [State] Stamp Act, and [Party A] shall obtain the e-stamp certificate before this Agreement is circulated for signature, furnishing [Party B] a copy with its Unique Identification Number. Where this Agreement requires registration under the Registration Act, 1908, the parties shall complete it within the period prescribed under Section 23 of that Act, and [Party A] shall bear the associated costs."

What changed and why: it names the actual signature method, excludes First Schedule documents so nobody accidentally e-signs a power of attorney, assigns stamping to one party with a deadline instead of to "the Parties," and puts registration on the record instead of treating it as an afterthought.

US and global contrast

If you learned contract execution on US or UK deals, the Indian position adds two steps you may never have had to think about. The US ESIGN Act, 2000 and the state-level UETA confirm an electronic record cannot be denied legal effect for being electronic, and largely stop there; there is no general stamp duty on commercial contracts, and county-level deed recording mainly protects priority against later claims rather than gating admissibility. In the US, "did both sides click accept" is close to the whole question. In India it is one of three.

FAQ

Does e-signing a contract in India automatically make it fully executed? No. A validly signed contract can still be unstamped, and a property document can still be unregistered, even with a flawless audit trail. Signing, stamping, and registration are three separate requirements, each checked independently if the contract is produced as evidence.

Can any software remove my stamp duty liability? No. It is a statutory liability under the Indian Stamp Act and the applicable state Act, owed by the parties. Software can make it easy to see, calculate, and pay through the correct channel. It cannot waive it or make an under-stamped instrument admissible by itself.

If my document is unstamped, does that also kill an arbitration clause inside it? Not automatically, since the Supreme Court's 2023 Interplay ruling. An arbitration agreement inside an unstamped contract is not void for that reason alone; the defect is curable, and stamping is a question for the arbitral tribunal, not a gatekeeping issue when a court appoints an arbitrator. The instrument itself still needs curing before it can be relied on for anything else.

Do I need to register a contract if it was signed electronically? If it falls under Section 17 of the Registration Act, mainly transfers, gifts, assignments, and long leases of immovable property, yes, regardless of how it was signed. A 2022 amendment removed the IT Act's own bar on e-signing a property sale contract, but it did not touch the Registration Act, which generally still requires physical appearance before the Sub-Registrar.

Does Adira handle all three steps automatically? Its paid plans include e-signing routed through licensed CAs and ESPs, e-stamping initiated through SHCIL or the relevant state portal, and execution tracking that flags where registration applies. That is a paid feature; the free Weave markup tool and this guide are useful either way, and none of it removes your responsibility to get the specific number right for your document.

This guide gets you to the three questions Indian law asks at execution, and what a good tool can and cannot do about each one. It does not tell you which signature method, stamp article, or registration requirement applies to your specific document, that depends on its category, value, and the state you executed it in. Confirm the live position on the relevant state's portal, and talk to a lawyer before you rely on any execution method for a real transaction. This is not legal advice.