Vendor Agreement in India: Key Clauses Businesses Should Review

A vendor agreement converts a supply or service relationship into a measurable operating framework. It should state what the vendor must provide, how the customer will verify performance, when payment becomes due and how risk is handled if delivery, quality, confidentiality or continuity fails.

This guide explains key clauses businesses should review in an Indian vendor agreement. The correct position will depend on the goods or services, bargaining power, applicable law, industry requirements and the operational importance of the vendor.

Vendor agreement review table

Use this table to connect the legal clauses with the procurement and operational questions that teams must administer.

What is a vendor agreement?

A vendor agreement is a contract under which a supplier provides goods, services, software, personnel or another business input. Depending on the relationship, it may be supported by purchase orders, statements of work, service-level schedules, data-processing terms and security requirements.

The document should be reviewed as one connected package. A strong main agreement can be undermined by a purchase order that changes payment terms or an online policy that the vendor may update unilaterally.

Identify the parties and contract documents

A clear contract architecture prevents disagreement about which entity and which set of terms govern a particular order.

Vendor identity and capacity

Confirm the vendor’s legal name, entity type, registration details, tax identifiers and address. Review whether it has the licences, approvals, personnel and financial capacity needed for the work. If an affiliate will perform, invoice or hold data, state that role and responsibility expressly.

Master agreement, purchase orders and statements of work

Define how orders are placed and accepted. Set an order of precedence among the master agreement, statement of work, purchase order, proposal and incorporated policies. Commercial variables may sit in an order, but core protections should not change accidentally through boilerplate.

Authority and onboarding documents

Verify signatory authority and collect relevant registrations, insurance evidence, bank verification, security documents and policy acknowledgements. The onboarding file should support both compliance and future payment verification.

Describe scope, delivery and acceptance

Performance obligations should be specific enough for procurement and operations teams to administer without reconstructing negotiations.

Specifications and deliverables

Describe goods, services, quantities, technical standards, locations, milestones and required documentation. Identify customer dependencies, assumptions and exclusions. For recurring services, define working hours, support channels, response levels and maintenance windows.

Delivery, title and risk

State the delivery point, shipping responsibility, packaging, inspection rights and when title and risk pass. For equipment or physical goods, align the contract with the actual logistics process and insurance arrangements.

Testing and acceptance

Define the acceptance period, test criteria, rejection notice and correction process. Deemed acceptance should not operate before the customer has received the information and access needed to test. For partial acceptance, explain how payment and warranty periods apply.

Set complete pricing and payment terms

Payment language should connect a valid invoice to accepted performance and should account for taxes, credits and disputed amounts.

Price, taxes and expenses

State whether prices are fixed, indexed or reviewable, and identify the documents required for any change. Allocate applicable taxes and withholding, and require pre-approval for reimbursable expenses where appropriate.

Invoices and payment milestones

Specify invoice content, submission channel, supporting records, due date and the treatment of genuine disputes. Milestones should be objective. The customer should be able to withhold a disputed portion without delaying an undisputed amount unless the transaction requires a different structure.

Micro and small enterprise status

Ask the vendor to declare and update its status under the Micro, Small and Medium Enterprises Development Act, 2006. Sections 15 to 18 of the MSMED Act establish a specific delayed-payment framework for eligible micro and small suppliers. Contract administration and payment processes should reflect any mandatory obligations that apply.

Measure performance and manage change

A practical agreement defines normal performance, the process for correction and a controlled method for changing the work.

Service levels and remedies

Choose service levels that relate to business impact, such as availability, response, resolution, accuracy or delivery time. State measurement sources, reporting frequency, exclusions and service credits. Credits should not unintentionally become the only remedy for serious or repeated failure unless that result is intended.

Warranties and correction

Require conformity with specifications, professional skill, applicable law and agreed security or quality standards. Define the warranty period and whether the vendor must repair, replace, reperform, refund or reimburse reasonable correction costs.

Change control

A change order should record the new scope, price, timeline, dependencies and effect on earlier commitments. Prevent informal requests or operational emails from changing material terms without authorised approval.

Allocate liability, indemnity and insurance

These clauses should be negotiated as a connected risk model, not copied independently from unrelated templates.

Indemnities

Identify specific risks such as third-party intellectual-property claims, bodily injury, property damage, confidentiality breaches or legal non-compliance. Define notice, control of defence, cooperation and settlement approval. Avoid wording so broad that the process becomes uncertain.

Liability limits

Review the overall cap, any separate caps, excluded losses and carve-outs. A cap linked only to a recent month of fees may be insufficient for a vendor controlling critical data or infrastructure, while unlimited exposure may be disproportionate for an ordinary low-risk supply.

Insurance

Specify relevant coverage, limits, policy duration, evidence and notice of cancellation. Insurance supports risk allocation but should not replace a clear contractual responsibility.

Protect confidentiality, data and intellectual property

Vendor access often extends beyond the immediate deliverable, so access, ownership and post-termination handling should be explicit.

Confidential information and security

Limit use to the contracted purpose, restrict disclosure to authorised recipients and require reasonable safeguards. Include incident notification, cooperation, access revocation and return or deletion duties suited to the information involved.

Data and subcontractors

Identify what data the vendor may process, where it may be accessed and which subcontractors may participate. Require the vendor to remain responsible for approved subcontractors and to flow down appropriate obligations.

Ownership and licences

Distinguish customer materials, vendor background tools, project deliverables and third-party components. The customer should receive ownership or a sufficiently broad licence for its intended use, while the vendor should retain only rights that are compatible with confidentiality and data restrictions.

Address term, termination and business continuity

The exit provisions should protect continuity and provide a controlled transition whether the agreement ends normally or because of breach.

Term and renewal

State the start date, initial period, renewal mechanics, pricing at renewal and notice deadline. Build internal reminders around renewal and certification dates.

Suspension and termination

Define when services may be suspended and require proportionate notice where practicable. Address material breach, cure periods, repeated service failure, insolvency, legal or security risk and termination for convenience where commercially needed.

Exit assistance

Require return of data and property, migration support, continued service during transition, final reconciliation and deletion certification. Set charges and time limits for assistance so the obligation remains usable.

Choose an effective dispute process

Use an escalation sequence that begins with named operational and senior representatives. If arbitration is selected, specify the seat, appointment process, number of arbitrators and language. If courts are selected, align governing law and jurisdiction. Notices should use addresses that are actively monitored.

For broader pre-signature issues, use our business contract review checklist. If vendor invoices are already overdue, see the guide to a legal notice for unpaid invoices.

Vendor agreement red flags

Red flags do not always require rejection, but they should be understood, priced and approved by the people responsible for the resulting risk.

• The scope relies on a proposal that is not attached or incorporated.
• The vendor can change price, policy or service levels without customer approval.
• Acceptance occurs automatically before meaningful testing is possible.
• The vendor may suspend a critical service for any disputed invoice.
• Customer data can be used for the vendor’s own purposes or retained indefinitely.
• There is no handover obligation for a business-critical service.

How EA Legal can assist businesses

EA Legal’s corporate lawyers in Bangalore assist companies with vendor agreements, master service agreements, statements of work, contract negotiation and practical risk review.

This article is general information, not legal advice. Vendor arrangements should be reviewed against their actual facts, sector, applicable law and operational dependencies.

Frequently asked questions

These answers provide a general overview. The contract, evidence and intended remedy should be reviewed for the particular matter.