Master services agreement (MSA) template for India

When you need this

• When the same client and provider will run more than one project together
• When a services relationship keeps restarting from a fresh contract each time
• When an enterprise customer sends you their MSA and you need to know which clauses actually matter
• When your provider is a registered micro or small enterprise, or you are one, and the payment terms have a statutory floor under them
• Before any project where a provider will process personal data on your behalf

What this document must contain

• A precedence clause between the MSA and each statement of work — The MSA should govern unless a SOW expressly names the clause it is varying. Without that, a one-page SOW signed by a salesperson quietly overrides the liability cap you spent three weeks negotiating.
• A liability cap with real carve-outs — Confidentiality breach, IP infringement, data breach caused by the defaulting party and fraud sit outside the cap in almost every negotiated agreement. Note also that a stated sum operates as a ceiling on compensation actually proved, not as a guaranteed payout.
• IP ownership stated at the deliverable level, with a licence back for pre-existing tools — A provider who assigns everything, including its own framework and internal tooling, is either misdescribing the deal or about to be unable to work for anyone else. Separate the deliverable from the toolkit that produced it.
• Payment terms, invoicing mechanics, and the statutory override — State the invoice requirements, the payment window and what happens on late payment — then recognise that where the supplier is a registered micro or small enterprise, the statutory maximum applies regardless of what the MSA says.
• A data processing clause tied to the DPDP Act — Processing on documented instructions, reasonable security safeguards, breach notification without undue delay, and assistance with a Data Principal’s request. The obligation to the individual stays with the fiduciary, so the contract is where the processor’s duties have to be written down.
• Termination for breach and for convenience, and what happens to work in progress — Say who can end it, on what notice, what is payable up to that date, and that work in progress is delivered up. An MSA that can only end on a breach is an MSA nobody can exit cleanly.
• One dispute mechanism, with the seat named — Escalation, then arbitration, then a named seat and governing law — in one clause that does not contradict itself. Two clauses pointing at different forums produce a preliminary dispute about where the dispute happens.

The law that governs it

• MSMED Act, 2006 — ss. 15 and 16 — Where the supplier is a registered micro or small enterprise, the buyer must pay within the agreed period, which cannot exceed forty-five days from the day of acceptance or deemed acceptance. Delayed payment attracts compound interest with monthly rests at a multiple of the rate notified by the Reserve Bank. A longer payment term written into an MSA does not displace this.
• Indian Contract Act, 1872 — s. 74 — Where a sum is named in the contract as payable on breach, the party complaining is entitled to reasonable compensation not exceeding that sum, whether or not actual loss is proved. A liquidated damages figure is therefore a ceiling on what a court will award rather than an automatic entitlement to it.
• Digital Personal Data Protection Act, 2023 — s. 8(5) — A Data Fiduciary may involve a Data Processor to process personal data on its behalf only under a valid contract. The obligations owed to the Data Principal remain with the fiduciary, which is why the processing terms have to be in the MSA or in a data processing addendum executed alongside it.

Common mistakes

• Signing an MSA and then letting statements of work quietly override it, because no precedence clause was written
• Accepting an uncapped indemnity sitting next to a capped liability, which makes the cap decorative
• Assigning all intellectual property including your own pre-existing tools, and then being unable to reuse them on the next engagement
• Agreeing ninety-day payment terms with a supplier who is a registered micro enterprise, where the statute fixes a much shorter maximum
• An arbitration clause with no named seat, which turns the first hearing into an argument about where the hearings happen

Frequently asked questions

What is the difference between an MSA and an ordinary service agreement?

A service agreement governs one engagement. An MSA governs the relationship and leaves the commercial specifics of each engagement to a statement of work, so the second and third projects need a page rather than a negotiation. The trade-off is that the MSA has to be drafted well enough to survive being applied to work nobody has described yet.

If the MSA and the SOW conflict, which one wins?

Whichever the precedence clause says wins. The usual and safer position is that the MSA prevails except where a SOW expressly identifies the clause it is varying — that way a variation has to be deliberate rather than accidental.

Can I agree ninety-day payment terms with an MSME supplier?

You can write it, but where the supplier is a registered micro or small enterprise the statutory maximum applies over your term, and delayed payment carries compound interest that cannot be negotiated away. The clause does not make the exposure disappear; it just hides it until the supplier decides to raise it.

Do I still need a separate data processing agreement?

If personal data is processed on your behalf, you need the processing terms in a valid contract — either inside the MSA or in an addendum. A separate addendum is usually cleaner, because it can be updated as the processing changes without reopening the whole commercial agreement.

Related documents

• Vendor / Supplier Agreement
• Vendor Data Processing Agreement (DPA) Addendum
• Freelance / Contractor Agreement
• All templates