JTJuris Tflow Direct
Guides › Contracts

Buying CLM Software in India: E-Stamping, Aadhaar eSign, the DPDP Act and Costs

A CLM platform can win the demo and still fail at signing in India: stamp duty is set state by state, and Aadhaar eSign can't execute some documents at all. Here's what to check, what it costs and how long rollout takes.

Juris Tflow Direct editorial team · November 2026 · 8 min read

Signing and stamping: what global CLM checklists leave out for India

Most CLM evaluations focus on templates, approval workflows, clause libraries and the repository. Those still matter in India. But the real test for anyone buying CLM software India is whether the tool gets a contract legally executed: stamped correctly for the right state, signed by a method the law accepts for that document type, and stored in a way that fits the Digital Personal Data Protection Act, 2023.

Global platforms assume a simple flow: draft, approve, e-sign, store. Indian execution adds steps that the software either handles or leaves to someone with a spreadsheet and a courier account. Three things global tools often treat as optional add-ons are core requirements here:

  • Stamp duty and e-stamping integration across the states where your entities and counterparties sign.
  • Aadhaar eSign and Digital Signature Certificate (DSC) support, plus firm rules for documents electronic signatures can't execute.
  • DPDP Act compliance for personal data held in contracts, counterparty KYC and signing audit trails.

Our view: a legal team that executes dozens of stamped instruments a month should treat stamping and eSign integration as a must-have. A workflow that ends in "print and buy stamp paper" is a gap you'll pay for every month, in staff time and in delays.

Advertisement

Stamp duty and e-stamping integration vary by state

Under the Constitution, the Union sets stamp duty rates for a few instruments, such as bills of exchange, cheques and promissory notes. States set them for most others. Several states, including Maharashtra and Karnataka, have their own stamp statutes; others work from the Indian Stamp Act, 1899 with local amendments. The same service agreement, NDA, lease or loan document can attract different duty, or be charged differently, depending on where it's executed. Some states also levy duty when a document signed elsewhere is brought into the state.

The consequence is practical. An unstamped or under-stamped instrument generally can't be admitted in evidence until the shortfall and a penalty are paid. Indian courts have treated the defect as curable rather than fatal, but you don't want to find it the week you need to enforce.

E-stamping also works differently across states. Many use Stock Holding Corporation of India (SHCIL) as the central record-keeping agency; others run their own treasury or franking systems. Execution platforms such as Leegality, SignDesk, Digio and NeSL's Digital Document Execution service connect to these systems, so a stamp certificate can be bought and attached inside the workflow. State coverage differs by provider and changes over time.

What to ask vendors about e-stamping

  • Which states can you issue e-stamps in today, and is that a direct integration or a manual back-office process?
  • Do you calculate duty from instrument type and contract value, or does our team enter the amount?
  • How do you handle multi-state contracts, where the first signatory is in one state and the second in another?
  • Is the stamp certificate stored with the executed contract and linked to its unique identifier?
  • Is duty passed through at cost, and what is the per-stamp convenience fee?

A red flag: a vendor that says "we support e-stamping" but can't give you a state-by-state list. Get the list in writing and check it against the states on your contract register.

What Aadhaar eSign can and cannot execute

Aadhaar eSign is a recognized electronic signature method under the Information Technology Act, 2000, delivered through eSign Service Providers within the Controller of Certifying Authorities framework. The signer authenticates through Aadhaar with an OTP or biometric, and a short-lived certificate signs the document. It suits high-volume contracts with individual signers: employment offers, consumer loan agreements, vendor onboarding and NDAs.

The limits come from the IT Act's First Schedule, which excludes certain documents from electronic execution:

  • Negotiable instruments other than cheques
  • Powers of attorney
  • Trust deeds
  • Wills and other testamentary dispositions
  • Contracts for the sale or conveyance of immovable property or any interest in it

Separately, documents that must be registered under the Registration Act, 1908, such as many longer-term leases, need a registration process that electronic signing alone doesn't complete.

Two more points. First, only individuals holding an Aadhaar can use Aadhaar eSign. Foreign signatories and many corporate authorized signatories need a DSC, often on a USB token, or another electronic signature where the law allows it. Second, the right method for a given contract is a legal call, and practice is still developing. Have Indian counsel approve a signing-method matrix by document type, then configure the CLM to enforce it, so no one can send a power of attorney out for OTP signing.

DPDP Act compliance for contract data

Contract repositories hold more personal data than teams expect: signatory names, emails and phone numbers, employee details in employment and consultancy agreements, counterparty KYC documents, and audit trails with IP addresses and device data. Under the DPDP Act, your organization is usually the data fiduciary and the CLM vendor acts as a processor on your instructions.

The DPDP Rules were notified in late 2025 and phase in over roughly 18 months, so most substantive duties bite from around 2027. Confirm current dates with counsel. The obligations that matter most to CLM buyers:

  • Security safeguards such as encryption, access controls, logging and backups, backed by a processor contract that requires the vendor to meet them.
  • Breach notification to the Data Protection Board and affected individuals. Your vendor contract needs prompt incident reporting to you.
  • Retention and erasure. Personal data should be erased once its purpose is served, unless another law requires you to keep it. Your CLM needs retention rules by contract type, not one indefinite archive.
  • Cross-border transfers. The Act allows transfers except to countries the government restricts. Sector rules can be stricter, such as RBI data localization for payment data and requirements on other regulated entities.

Penalties can reach INR 250 crore for the most serious failures, including inadequate security safeguards, so this belongs in procurement, not just IT review. Ask where data is hosted, whether an India region is available, and how Aadhaar details are handled. Many Indian eSign flows store only masked Aadhaar information; confirm that holds for yours. Processor and residency rules differ elsewhere too, for example the GDPR in Europe and the PDPL in Saudi Arabia, so global groups should settle on one baseline standard. A data protection lawyer should approve the final processor terms.

Local versus global vendors and what they cost

The Indian market splits into three groups:

  • India-native execution platforms (Leegality, SignDesk, Digio). Strongest on e-stamping and Aadhaar eSign, lighter on CLM features.
  • India-origin CLM vendors that also sell globally (SpotDraft, Volody, and Zoho Contracts with Zoho Sign at the smaller end). Fuller contract workflows, with local execution built in or partnered.
  • Global enterprise CLM (Icertis, Sirion, DocuSign CLM, Ironclad, Agiloft). Strong on scale, analytics and multi-country governance. They typically reach Indian e-stamping and Aadhaar eSign through partner integrations, so check exactly which ones.

For most Indian mid-market companies with 10 to 30 legal and contract users, an India-origin CLM is the better fit: local execution works out of the box, and support hours match yours. Multinationals already running a global CLM should usually keep it and add an Indian execution layer rather than maintain a second repository.

TierTypical buyerIndicative annual cost (INR)Approx. annual cost (USD)
eSign and e-stamp execution platformHigh-volume transactional contracts2–8 lakh plus usage2,500–9,500 plus usage
Mid-market CLM10–30 users, one or two entities6–30 lakh7,000–35,000
Enterprise or global CLMMulti-entity, multi-country50 lakh–2 crore+60,000–240,000+
Implementation (one-time)All tiers1–40 lakh1,200–48,000

These are typical 2026 market ranges. They vary by contract, user count and volume commitments, and exchange rates move, so confirm with vendors. Usage fees are often in the range of INR 15–40 per Aadhaar eSign and INR 50–200 per e-stamp in convenience fees, with stamp duty passed through at actual. Watch for minimum volume commitments, charges for extra states and per-entity licensing.

Hypothetical worked example: say a 300-employee lender executes 2,000 stamped agreements a month in four states, each with two signers. At INR 30 per eSign and INR 100 per stamp, usage alone comes to about INR 3.2 lakh a month before duty. Negotiate usage pricing as hard as the licence fee.

Rollout timelines and a buying sequence that holds up

Timelines slip most often on legal sign-off for the signing-method matrix and on migrating legacy contracts, not on configuration. Treat these as typical ranges, not promises.

ScopeRealistic timelineMain dependency
eSign and e-stamping only2–6 weeksState coverage and stamp account setup
Mid-market CLM with templates and approvals8–16 weeksTemplate standardization, approval matrix
Enterprise CLM with ERP or CRM integration and migration4–9 monthsData migration, integrations, DPDP review
  1. Pull a 12-month contract register by document type, state and signer type.
  2. Have counsel approve the signing and stamping matrix, including the excluded documents.
  3. Shortlist vendors on state e-stamping coverage first and CLM features second.
  4. Run a DPDP processor review covering hosting, retention, breach terms and sub-processors.
  5. Pilot with your two highest-volume contract types in your two busiest states.

Decision rule: if more than half your volume is stamped, individually signed contracts, start with an execution platform and add CLM later. If most of your volume is negotiated commercial agreements, buy a CLM with proven Indian execution built in.

Quick answers

Is a contract signed with Aadhaar eSign legally valid in India?

Yes, for most contracts. Aadhaar eSign is a recognized electronic signature under the Information Technology Act, 2000. It can't be used for documents the Act excludes, such as powers of attorney, wills, trusts, most negotiable instruments and contracts for the sale of immovable property. Have Indian counsel confirm the right method for each of your document types.

Do we still need to pay stamp duty if the contract is signed electronically?

Generally, yes. Stamp duty attaches to the instrument, not to how it's signed, so electronically executed contracts still need correct stamping under the relevant state's law. E-stamping integration lets you buy and attach the certificate digitally, but coverage differs by state and provider.

Can we use a global CLM platform hosted outside India under the DPDP Act?

Usually, yes. The DPDP Act permits cross-border transfers except to countries the government restricts. Sector rules, such as RBI requirements for regulated financial entities, can impose stricter localization, and you still need a processor contract with adequate safeguards and breach terms. Confirm your sector's position with a data protection lawyer before you sign.

Written by the Juris Tflow Direct editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.