Do You Have to Pay Stamp Duty on an Electronically Signed Contract?

Yes. E-signing a contract does not remove your stamp duty liability. Stamp duty is a tax on the instrument, the document itself, not on the mode you used to sign it. If the same agreement on paper would owe duty, the e-signed version owes the same duty; clicking "I agree" or using an Aadhaar eSign changes nothing about that. This guide (published by Adira, which makes contract lifecycle management software, so we have a commercial interest in you executing contracts correctly, but the explanation below stands on its own) walks through when duty becomes payable, which state's law decides the rate, how to actually get an e-signed agreement stamped, and what happens if you skip it.

The short answer, and why people get confused

The confusion comes from mixing up two separate legal questions: is the contract validly formed, and has the tax on it been paid. E-signing answers the first. The Information Technology Act, 2000 makes an electronically formed contract enforceable, and Indian courts do not need pen-on-paper for a binding contract to exist. Stamp duty answers a different question, governed by the Indian Stamp Act, 1899 and the state Stamp Act that applies where you executed the document.

Section 2(14) of the Indian Stamp Act defines "instrument" in language that was never written with paper in mind:

"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

Section 3 then makes every instrument listed in the Schedule "chargeable with duty of the amount indicated in that Schedule as the proper duty therefor." Section 3, Indian Stamp Act, 1899. Nothing in either section carves out documents that happen to be signed electronically. Several states have gone further and said this expressly rather than leaving it to interpretation. Maharashtra amended its own Act in 2005 to add an Explanation to Section 2(l):

"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

That is the cleanest statutory statement in the country that an e-agreement is an instrument like any other. Most other states reach the same result by treating "document" as technology-neutral under the central Act, without a matching express clause on their own books, which is why the rate and process still vary state to state. Our companion page, stamp duty on electronic contracts in India, carries the state-by-state rate table; this page focuses on the mechanics of getting an e-signed agreement stamped.

When duty becomes payable: at or before execution, not after

Timing is where most e-signed contracts go wrong, because e-signing feels instantaneous and stamping feels like paperwork you can catch up on later. You cannot. Section 17 of the Indian Stamp Act is direct about this:

"All instruments chargeable with duty and executed by any person in India shall be stamped before or at the time of execution." Source: Section 17, Indian Stamp Act, 1899

Courts read "before or at the time of execution" as practically simultaneous with signing, not a grace period. On paper, this habit is easy to keep, because someone has to physically buy stamp paper before printing the agreement on it, so stamping happens first almost by accident. E-signing removes that natural checkpoint. Two people can click "sign" from their phones in ninety seconds with nobody in the loop to ask "has this been stamped." That is the real reason e-signed contracts end up unstamped more often than paper ones, not because the law is different, but because the workflow no longer forces the question.

The test you can run right now: open the last e-signed vendor, employment, or NDA contract you were party to and search it for the word "stamp." If the word does not appear anywhere in the document or in the signing workflow that produced it, nobody in that transaction took responsibility for it, and that is usually the first thing an opposing lawyer or an arbitrator points to if the contract is ever produced as evidence.

Where: which state's law decides the rate

Stamp duty is a state subject for most instruments, so "where" the agreement is executed decides both the rate and, for some states, whether a state-specific electronic-record rule even applies. There is no single all-India rate on a general commercial agreement. Each state sets its own figure under its own residuary "Agreement" article (commonly Article 5, Article 6 in Telangana), and the number ranges from a flat Rs 100 or Rs 500 in most states to an ad valorem rate if the agreement carries a monetary value above a threshold.

For an e-signed contract, "where it was executed" is not always obvious, since there is no single room where signing happened. The safer approach, worth writing directly into the contract, is to name the state whose stamp law governs execution, rather than leaving it to be inferred from where each signatory happened to be sitting when they clicked. The full state-by-state rate table, including which states run e-stamping through SHCIL and which (Maharashtra) run their own system, is on the companion page linked above.

How to actually stamp an e-signed contract

This is the part most guides skip. Stamping an e-signed contract is not the same process as stamping a paper one, and using the wrong method is a common, avoidable mistake.

Franking is for paper. Franking is a physical process: a bank or authorized franking agent runs a printed document through a franking machine, which stamps a denomination directly onto the paper. It requires a physical document in hand, and is typically used for lower-value instruments in states that still offer it. There is no electronic equivalent of a franking machine, and you cannot frank a PDF. If your workflow still assumes franking, it was built for paper and needs to change for an e-signed agreement.

E-stamping is the electronic route, and it is what applies here. Most states route e-stamping through the Stock Holding Corporation of India Limited (SHCIL), the Central Record Keeping Agency. You, or whichever party the contract assigns the job to, apply online (or through an authorized collection centre), pay the duty, and SHCIL issues an e-stamp certificate carrying a Unique Identification Number (UIN) that can be verified independently online. That certificate, not the e-signature itself, is your proof duty has been paid. Maharashtra is the standing exception: it runs its own GRAS challan and eSBTR system through the Inspector General of Registration instead of a SHCIL certificate. Treating a Maharashtra agreement like a SHCIL state, or the reverse, is the single most common state-specific mistake here.

A worked example. Two companies execute a one-year services agreement in Karnataka, entirely by e-signature, with no monetary obligation stated in the document. Under Karnataka's residuary Article 5(j), raised from Rs 200 to Rs 500 by the 2023 Amendment Act, the duty owed is a flat Rs 500. One party logs into the Kaveri online portal (or a SHCIL-authorized collection centre), pays the Rs 500, and gets an e-stamp certificate with a UIN before the document goes out for e-signature. The certificate is attached as the first page, or its UIN is referenced in the signing block, so anyone opening the executed contract later can see both facts, signed and stamped, in one place.

The practical sequence: work out which state's stamp law applies and name it in the contract; check whether the agreement fits a specific Schedule article (lease, security document, share transfer) or the general residuary one; obtain the e-stamp certificate through SHCIL or the relevant state portal before the document goes out for signature, not after; attach the certificate, or its UIN, to the document being e-signed so the paid-duty record and the signed record are linked; and keep both together in your contract repository, since a signature audit trail with no stamp record is exactly the gap that causes problems later.

You can check right now whether a draft agreement even addresses execution mechanics, and flag what is missing, for free, using Weave, which lets you mark up a document's execution clause directly.

What happens if you skip it

Skipping stamping does not make the contract void, but it does something close to functionally void when it matters most: you generally cannot use it. Section 35 of the Indian Stamp Act is the operative provision:

"No instrument chargeable with duty shall be admitted in evidence for any purpose by any person having by law or consent of parties authority to receive evidence, or shall be acted upon, registered or authenticated by any such person or by any public officer, unless such instrument is duly stamped." Source: Section 35, Indian Stamp Act, 1899

The same section gives a way out, at a cost: an insufficiently stamped instrument can still be admitted once you pay the deficient duty plus a penalty, set at five rupees, or ten times the deficient duty where that is higher. Before that stage, Section 33 obliges anyone with authority to receive evidence, a court, an arbitrator, or certain public officers, to impound an instrument the moment they notice it is not duly stamped. Section 33, Indian Stamp Act, 1899. Impounding is what turns "we forgot to stamp this" into a real delay in the middle of a dispute, exactly when you can least afford one.

Arbitration clauses inside unstamped agreements have their own recent history. A seven-judge Constitution Bench, in In Re: Interplay Between Arbitration Agreements and the Indian Stamp Act, 1899 (Curative Petition No. 44 of 2023, decided 13 December 2023, 2023 INSC 1066), held that an arbitration agreement inside an unstamped or insufficiently stamped contract is not rendered void by that alone. Full judgment, 2023 INSC 1066. The defect is curable, and whether an instrument is duly stamped is not a gatekeeping question for the court appointing an arbitrator under Sections 8 or 11 of the Arbitration and Conciliation Act, 1996; it is for the tribunal to examine once appointed. That narrowed one specific risk, losing an arbitration clause entirely over an unstamped contract, but it did not remove the duty, the penalty, or the Section 35 admissibility problem in front of a court. Skipping stamping is still a costly mistake, just no longer a fatal one for arbitration specifically. Fuller consequences are on our page on whether an unstamped agreement is valid.

Red flags in how contracts handle e-stamping

Normal	Red flag	Why it matters
The contract names the state whose stamp law and execution rules apply	Governing-law clause is silent on where the instrument was executed	On a cross-state e-signature deal, nobody has actually decided this, and it surfaces only when someone tries to enforce the contract
A named party is responsible for e-stamping, with a deadline before signing	"Stamp duty, if applicable, shall be borne by the Parties," with no process or owner named	Nobody actually does it, because "the Parties" is not a person with a task
The e-stamp certificate's UIN is attached to or referenced in the signed document	Only a signature audit trail exists; no stamp record anywhere	An e-signed but unstamped instrument faces the Section 35 admissibility problem, which has nothing to do with whether the signature is genuine
Stamping happens before or with e-signing, as part of the same workflow	"We will sort out stamping later if we ever need to produce it"	Section 17 requires stamping before or at execution; late stamping means paying a penalty on top of the duty, and risking impounding
Duty is calculated on the real, full value of the agreement	A token or nominal value is stated to reduce the duty bill	Undervaluation is a separate violation under state Stamp Acts, independent of any duty shortfall
The correct Schedule article is identified (general agreement, lease, security document, etc.)	Nobody checked which article actually applies	A wrong article means paying a flat residuary fee where an ad valorem rate was actually owed, which surfaces as a shortfall later

Execution clause: bad versus better

Bad: "This Agreement shall come into force upon execution by both Parties in electronic form, and applicable stamp duty, if any, shall be borne by the Parties."

What is wrong with it: no state is named, so it is unclear whose stamp law even applies; "the Parties" is not one person with a deadline, so the job falls to nobody in particular; and there is no mechanism for either side to confirm the other actually did it before relying on the document.

Better: "This Agreement is executed in electronic form at [City, State]. Stamp duty is payable under Article 5 of Schedule I to the [State] Stamp Act (or, where the Indian Stamp Act, 1899 applies directly, the corresponding Schedule for [State]). [Party A] shall obtain the applicable e-stamp certificate through [SHCIL / the State's e-stamping or GRAS/eSBTR facility] before this Agreement is circulated for signature, and shall furnish [Party B] a copy, including its Unique Identification Number, before or promptly upon execution. Any deficiency in stamp duty, and any resulting penalty, shall be borne by [Party A]."

What changed: the state and Schedule are named instead of left to inference, one party carries the job with a deadline tied to signing, there is a document the other side can check, and responsibility for getting it wrong is allocated up front instead of argued about later.

How this interacts with related questions

This page assumes your document is validly e-signed; that question, and the difference between a basic e-signature and a "secure" one carrying an extra evidentiary presumption, is covered on our page on e-signature validity in India. The state-by-state rate table, and which states run SHCIL versus their own system like Maharashtra, live on stamp duty on electronic contracts in India. What happens once an unstamped instrument is impounded, and how it gets validated after the fact, is covered on whether an unstamped agreement is valid.

US and global contrast

If you are used to US or UK execution practice, this topic will feel unfamiliar, because it largely does not exist there. The United States has no general stamp duty on commercial contracts; a handful of states levy a documentary stamp tax, almost always on real estate deeds and mortgages, not a services agreement or an NDA. The federal E-SIGN Act, 2000 and the state-level Uniform Electronic Transactions Act confirm an electronic record cannot be denied legal effect merely for being electronic, and stop there; there is no tax-on-the-instrument regime layered on top. In US or UK practice, "did both sides validly click accept" is close to the whole execution question. In India, that is only half of it; paying and evidencing duty on the instrument itself is the part that trips up teams used to a signature-only mindset.

FAQ

Does e-signing a contract in India automatically pay its stamp duty? No. E-signing under the Information Technology Act, 2000 proves who agreed to the document and that they intended to be bound. Stamp duty is a separate tax on the instrument, paid and evidenced through e-stamping, and it does not happen automatically just because the signatures are electronic.

Do purely electronic contracts need stamping, or only ones that get printed? They need stamping regardless of whether anyone ever prints them. Section 2(14) defines "instrument" by what the document does, creating or recording a right or liability, not by its medium, and Maharashtra's Stamp Act expressly extends that to electronic records. Never printing the contract does not remove the liability.

How do I stamp an electronic agreement, since I cannot frank a PDF? Through e-stamping, not franking. Most states issue an e-stamp certificate with a Unique Identification Number through SHCIL or an authorized collection centre; Maharashtra runs its own GRAS/eSBTR system instead. Franking needs a physical document run through a bank's machine and has no application to a purely electronic execution.

What if the two parties e-sign from different states? A genuine grey area, since there is no single physical location where "execution" happened. The safer practice is to name, in the contract itself, the state whose stamp law and execution rules govern, rather than leaving it to be inferred later, possibly by a court taking a different view than either party expected.

If my e-signed agreement is unstamped, is it worthless? No, but it is close to unusable until fixed. Under Section 35, it generally cannot be admitted in evidence or acted upon by a court, registrar, or arbitrator until the deficient duty and penalty are paid. Since the Supreme Court's 2023 Interplay ruling, an arbitration clause inside the same document is treated separately and is not automatically void for this reason, but the instrument itself still needs curing before it can be relied on.

Does Adira handle e-stamping for e-signed contracts automatically? Its paid CLM plans (Practice $89 to $109 per seat per month, Firm $179 to $219, Enterprise on custom pricing, all with a 7-day trial, as published on adiralaw.com, last verified 4 September 2026) include execution and stamping tracking across states as part of the broader workflow. That is a paid feature; this guide and the free Weave markup tool above are useful either way.

This guide gets you to the right questions and the right process for stamping an e-signed agreement. It does not tell you the exact duty payable on your specific instrument, which depends on its category, its stated value, and the current rate in force in the relevant state, and a general guide cannot safely give you that number. Confirm the live rate on the relevant state's e-stamping or registration portal, and talk to a lawyer or a stamp duty expert before you rely on any figure for a real transaction. This is not legal advice.