Free Vendor Agreement Template for India (2026)

Why a vendor agreement template is different from an NDA or MSA

Indian counsel treat vendor agreements as the workhorse of the procurement function: they cover everything from a one-off SaaS subscription to a five-year managed-services arrangement. The drafting question is not "do we need confidentiality clauses?" — those go in by default — but "what are the operational guardrails when the vendor underperforms?" That puts the emphasis on Service Levels, remedies short of termination, and a clean exit framework. An NDA controls information flow before contracting. A mutual NDA template handles the pre-contract phase. A vendor agreement governs the live commercial relationship — typically over multiple years, with changing scope and escalating spend.

The template is built around three drafting principles that Indian in-house counsel have validated through actual disputes:

1. Specificity wins over comprehensiveness. A 60-page vendor agreement that copies every clause from a US template loses in arbitration when the parties disagree on what "best efforts" means. The template uses measurable SLA thresholds, dollar-defined liquidated damages, and explicit acceptance criteria.
2. Operational clauses go in schedules, not the body. Pricing, SLAs, security requirements, and the Statement of Work belong in numbered schedules so they can be amended by the operations teams without legal re-negotiating the master.
3. Indian-law-specific clauses are non-negotiable. Stamp duty, MSME compliance, DPDP carve-outs, and arbitration seat selection cannot be imported wholesale from a foreign template. The template embeds the Indian-specific defaults inline and flags where Indian counsel must adapt.

What this template covers

The agreement is structured as a master vendor agreement that anticipates multiple SOWs over the contract term. Operative clauses include:

• Engagement and SOW framework — defines that all work is governed by signed Statements of Work referencing the master, so adding new scope doesn't require re-papering the legal terms.
• Service levels and credits — measurable thresholds (uptime, response time, defect resolution) with monthly service credits as the pre-litigation remedy. Mirrors the structure Indian courts have upheld in technology vendor disputes.
• Pricing and invoicing — supports fixed-fee, time-and-materials, and milestone billing. Includes the MSME 45-day payment fallback that overrides longer terms under Micro, Small and Medium Enterprises Development Act, 2006 § 15Where any supplier supplies goods or renders services to any buyer, the buyer shall make payment on or before the date agreed upon between him and the supplier in writing or, where there is no agreement, before the appointed day, which shall not exceed 45 days..
• Acceptance and warranties — 30-day acceptance window with deemed acceptance unless the buyer flags specific defects. Implied warranties under Sale of Goods Act, 1930 § 16Where the buyer makes known to the seller the particular purpose for which the goods are required, there is an implied condition that the goods shall be reasonably fit for such purpose. expressly preserved.
• Intellectual property — vendor retains IP in pre-existing materials; buyer owns deliverables outright on payment. Optional licence-back for vendor's continued use of buyer customisations is bracketed.
• Indemnification — vendor indemnifies for IP infringement, breach of confidentiality, and DPDP violations. See the indemnification clause deep-dive for the underlying drafting framework.
• Limitation of liability — capped at 12 months of fees with the standard carve-outs (IP, confidentiality, gross negligence, fraud, DPDP).
• Termination — for convenience (30 days), for cause (15 days post-cure notice), and for insolvency (immediate).
• Dispute resolution — institutional arbitration under MCIA, DIAC, or ICC India rules, seated in India, conducted in English.

A practical example

Consider a Bengaluru-based fintech, Pivot Payments, onboarding a managed-services vendor, NorthStar IT, for 18 months of platform support. Pivot's procurement team negotiated commercials at ₹2 crore annual run-rate with quarterly renewals. The template gives Pivot's counsel a clean way to operationalise that deal:

• The master agreement is signed once, governs the relationship for three years.
• The Statement of Work (Schedule A) defines NorthStar's specific deliverables: 24×7 platform support, 99.5% uptime, P1 incident response in 30 minutes.
• The Pricing Schedule (Schedule B) sets ₹2 crore annual fees billed monthly, with quarterly true-up for over-and-under-utilisation.
• The Service Level Schedule (Schedule C) defines credits: 5% of monthly fees for missing uptime, 10% for missed P1 response.
• The Data Processing Schedule (Schedule D) makes NorthStar a processor under the DPDP Act, with 48-hour breach notification.

When Pivot wants to add a new workstream six months in, the operations teams sign a new SOW under the same master — no new legal review required.

Indemnification: the clause that actually matters

The indemnification clause is the single most-litigated provision in Indian vendor agreements. The template uses a layered approach. The vendor indemnifies for:

1. Third-party IP infringement by the deliverables — uncapped, with the vendor's right to procure rights, modify the work, or refund.
2. Breach of confidentiality — capped at 24 months of fees (the "super-cap" exception to the general 12-month cap).
3. Breach of DPDP obligations — uncapped where regulator penalties or data principal claims arise from the vendor's failure to meet processor obligations under Digital Personal Data Protection Act, 2023 § 8Section 8 imposes obligations on data fiduciaries and, by Section 8(5), requires them to enter into a valid contract with any data processor..
4. Gross negligence and wilful misconduct — uncapped.

Buyer-side counsel often push for additional indemnities: regulatory investigations, employment claims by vendor staff, environmental violations. The template flags these as bracketed options in Clause 12 and provides commentary on when to insist on them.

The Vendor shall defend, indemnify and hold harmless the Customer from and against any claim, suit, or proceeding brought by a third party alleging that the Deliverables, when used in accordance with this Agreement, infringe any patent, copyright, trade mark, or trade secret of such third party, and shall pay all damages and costs (including reasonable attorneys' fees) finally awarded in such claim or agreed to in settlement authorised in writing by the Vendor. This indemnification obligation shall not be subject to the limitation of liability set forth in Clause 13.

DPDP: the data processing schedule

Most vendor relationships involve some processing of personal data — even a payroll vendor handles employee data, even an analytics vendor sees hashed user identifiers. The template's Schedule D operationalises the processor obligations under Digital Personal Data Protection Act, 2023 § 8Section 8(5) requires the data fiduciary to enter into a valid contract with the data processor obligating the processor to process personal data only on the fiduciary's instructions.. For a deeper walkthrough of these obligations, see the DPDP compliance guide.

The schedule covers:

If your engagement involves sensitive personal data — health, financial, or biometric — Clause 3 should be replaced with the more stringent "Reasonable Security Practices" standard prescribed under the IT Act 43A SPDI Rules until the DPDP Rules supersede them.

Stamp duty, e-stamping, and execution

Vendor agreements in India attract ad-valorem stamp duty under each state's Stamp Act. Maharashtra and Karnataka are the highest-volume states for SaaS vendor contracts and follow these slabs:

• Maharashtra: 0.1% of contract value, capped at ₹25,000 (Article 5 of Schedule I to the Maharashtra Stamp Act, 1958).
• Karnataka: 0.1% of contract value, no cap (Article 5(d) of the Karnataka Stamp Act, 1957).
• Delhi: ₹100 fixed, since vendor agreements are treated as "agreement not otherwise provided for" under Article 5(c).
• Tamil Nadu: 1% of consideration, with a ceiling of ₹50,000.

For digital execution via DocuSign, Adobe Sign, or eMudhra, the agreement is enforceable under Section 5 of the IT Act, 2000 — but e-stamping must be completed separately on the SHCIL portal or the state e-stamping system. Many counsel paper a "stamping covenant" requiring the buyer to complete stamping within 7 days of execution; the template includes this as Clause 23.

Termination: the practical drafting question

The most-disputed termination clause in Indian vendor agreements is the data and asset transition obligation. Buyers demand a 90-day transition period at no additional cost; vendors push back because their team has already been redeployed. The template uses the market-standard compromise:

• 30-day notice for termination for convenience.
• 90-day transition period during which the vendor provides reasonable cooperation at the existing fee rate, with explicit deliverables (knowledge transfer, data export, account credentials, runbooks).
• After 90 days, transition support continues only at vendor's then-current rate card.

This three-tier structure is clearer than the typical "reasonable cooperation for a reasonable period at reasonable rates" boilerplate and courts have favoured the explicit version in disputes.

Drafting note: The template's transition clause specifically lists the data formats in which the vendor must export buyer data. If you do not specify "machine-readable, non-proprietary formats including CSV, JSON, or industry-standard equivalent," vendors have been known to deliver data in proprietary formats requiring further licence purchases. Insist on the explicit list.

What this template does not cover

A handful of vendor relationships need bespoke drafting beyond this template:

• Public-sector procurement — government departments and PSUs have GFR-mandated contract formats that this template cannot substitute. Use the GeM portal templates instead.
• Construction and EPC contracts — these need FIDIC-style or state-specific PWD frameworks. The template's commercial-services drafting is not appropriate.
• Manufacturing supply — for ongoing supply of physical goods, layer in standard purchase order terms with order acceptance mechanics. The template handles services-led engagements better than pure goods supply.
• Cross-border with foreign vendor — retain MCIA seat or shift to Singapore International Arbitration Centre; the template's tax, withholding, and FEMA compliance clauses need supplementation.

How Clauseium accelerates vendor agreement review

Once you have downloaded and customised the agreement, Clauseium will flag any deviation from your standard playbook: indemnity caps that are too low, missing MSME representations, DPDP schedules that omit sub-processor approval, termination periods outside your accepted range. For most counsel reviewing a vendor's redlines, that compresses what would be a half-day comparison into a 20-minute exception review.

Try Clauseium free →

Final checklist before signing

Before issuing the agreement to the vendor, verify:

1. The Statement of Work is filled in with measurable deliverables, not "general services to be agreed."
2. The Service Level Schedule has numerical thresholds and corresponding credits, not "best efforts."
3. The Pricing Schedule specifies invoicing cadence, payment terms, and the MSME fallback.
4. The vendor has provided MSME registration certificate or has represented non-MSME status in writing.
5. The DPDP Schedule is retained (or expressly waived) and the breach notification window is filled in.
6. The arbitration seat, institution, and rules are filled in.
7. Stamp duty is calculated for the state of execution and the stamping covenant has a deadline.
8. Both signatories have authority — for companies, board resolution; for LLPs, designated partner under the LLP Act, 2008.

A vendor agreement that gets these eight things right takes a week to negotiate and sign. One that doesn't ends up in arbitration two years later with the parties arguing what "reasonable" meant.