Service Agreement: Indian Contract Act 1872 Guide

A service agreement is a contract under which one party, the service provider, undertakes to perform defined work for another, the client, in exchange for agreed consideration. It records the bargain in writing so that scope, fees, timelines and liability are not left to memory or to a chain of WhatsApp messages. In Indian practice the same instrument is often called a services contract, a consultancy agreement or a master services agreement when it sits above several statements of work, but the legal nature is identical.

The distinction worth keeping straight is between a service agreement and an employment contract. A service agreement governs an independent contractor relationship, where the provider controls the manner of work and bears its own statutory obligations on tax and provident fund. An employment contract creates a master-servant relationship that pulls in Indian labour legislation, EPF, gratuity and notice rules. Misclassifying an employee as a contractor to sidestep these obligations is one of the costliest mistakes a business can make, because the substance of the relationship, not the label on the document, decides how courts and authorities treat it. A genuine service agreement keeps the provider at arm's length: it commissions a result, not the provider's daily attendance.

Every service agreement in India lives or dies on the Indian Contract Act, 1872. Section 10 sets the threshold: an agreement becomes an enforceable contract only when it is made by the free consent of parties competent to contract, for a lawful consideration and with a lawful object. Section 11 fixes capacity, so a minor or a person of unsound mind cannot validly contract, and Section 23 strikes down any object or consideration that is fraudulent, immoral or opposed to public policy. Consideration must be real, though Indian law does not require it to be adequate; a token fee can support a binding promise so long as both sides exchange something of value. You can read the consolidated text on the official India Code portal maintained by the Ministry of Law and Justice, the authoritative source for the statutory text of the Indian Contract Act 1872.

Two further points trip up first-time drafters. The first is stamping. A service agreement does not need stamp duty to be valid, but under the Indian Stamp Act, 1899 and the State stamp laws an unstamped or under-stamped instrument is inadmissible in evidence until the duty and a penalty are paid. Stamp the agreement on the consideration value and in the State where it is executed, because rates differ from State to State. The second is restraint of trade: Section 27 of the Contract Act voids any clause that restrains a person from exercising a lawful profession or trade, which is why broad post-engagement non-compete clauses against service providers rarely survive. Confidentiality and non-solicitation survive; a blanket bar on the provider working for anyone else usually does not. Electronic execution is fully recognised under the Information Technology Act, 2000, so a service agreement signed with a valid e-signature is enforceable, with the narrow Schedule I exceptions that still demand wet ink.

The most frequent trigger is engaging a freelancer or consultant for project work. A start-up retaining a designer, a manufacturer commissioning a software build, a firm hiring an external auditor: each needs the scope, the milestones and the fee structure locked down before work begins, because the most expensive disputes are the ones where nobody wrote down what "finished" meant. The second common scenario is the recurring vendor relationship, where a master service agreement frames the commercial terms once and each new assignment runs off a short statement of work referencing it. This saves renegotiating boilerplate every quarter while keeping the binding terms consistent.

Cross-border engagements are a third case worth flagging. When an Indian client retains an overseas provider, or an Indian provider serves a foreign client, the agreement should fix the governing law and the dispute-resolution forum expressly, since silence invites a jurisdictional fight nobody wins quickly. Indian parties also use these contracts to allocate intellectual property: in the absence of a written assignment, ownership of work product can default in ways neither side intended, so the agreement is where you transfer or license the deliverables. One genuine edge case is the unpaid-but-binding pilot, where a provider does a trial build before the paid phase. Even a nominal consideration keeps that pilot enforceable, whereas a pure gratuitous promise gives the provider no remedy if the client walks away. If your engagement also touches confidential data, pair the service agreement with one of the non-disclosure and confidentiality agreement templates in the same category.

• The scope of services and deliverables is the spine of the agreement. Our template forces specificity: not "provide marketing support" but the named deliverables, the format, the acceptance criteria and what falls outside scope. Vague scope is the single largest source of service-agreement litigation in India, and a precise clause is what lets you prove non-performance later.
• The fees and payment schedule clause sets the consideration, the milestones that release each payment, the invoicing mechanics and the consequence of late payment, including interest. Because consideration is a Section 10 essential, a clear fee clause also protects the contract's enforceability, not just your cash flow.
• The timelines and milestones clause ties deliverables to dates and states whether time is of the essence, which determines whether a delay is a mere breach or a ground to terminate. It distinguishes provider delays from client-caused delays so the blame is allocated on facts, not assertion.
• The intellectual property clause assigns or licenses the work product, addressing who owns code, designs or reports on completion and on early termination. Without it, the default position can leave the client paying for output it cannot freely use.
• The confidentiality and non-solicitation clause protects information exchanged during the engagement and survives termination, drafted to stay inside Section 27 limits so it remains enforceable rather than void.
• The limitation of liability, indemnity and termination clause caps exposure, allocates risk for third-party claims and sets the notice and exit mechanics. A clause that tries to exclude all liability under Section 73 risks being struck down as against public policy, so our template caps rather than excludes.

Stamp duty is the dimension where State law genuinely diverges, so the State of execution matters for a service agreement. In Maharashtra, agreements are stamped under the Maharashtra Stamp Act, 1958, and a service or consultancy agreement typically attracts a fixed or value-linked duty under the residuary article; Mumbai's commercial volume means under-stamping is routinely caught at the evidence stage. In Karnataka, the Karnataka Stamp Act, 1957 governs, and Bengaluru's technology sector relies heavily on master service agreements for IT services, where the IP-assignment and confidentiality clauses carry disproportionate weight.

In Delhi, the Indian Stamp Act, 1899 as applied to the National Capital Territory sets the duty, and the concentration of consultancies and agencies makes the distinction between a contractor agreement and a disguised employment contract a live compliance issue. In Tamil Nadu, the State stamp schedule applies and Chennai's manufacturing and back-office base generates a steady stream of vendor and outsourcing agreements where milestone-linked payment clauses are scrutinised closely. Telangana follows its own adaptation of the stamp legislation, and Hyderabad's pharma and IT clusters lean on cross-border service agreements where governing-law and arbitration clauses are non-negotiable.

The practical takeaway across States is consistent. The Contract Act is central legislation and applies uniformly, so the validity of your service agreement does not change between Mumbai and Chennai. What changes is the stamp duty payable and the registering or adjudicating authority, which is why the agreement should be stamped in the State of execution and on the correct value. If your engagement crosses into incorporation or vendor onboarding for a company, the business and incorporation document templates cover the corporate-side paperwork that often sits alongside a service agreement.

You start by identifying the parties: the legal name and address of the service provider and the client, with the correct entity type, since a sole proprietor, an LLP and a private limited company sign differently and bind differently. From there the form walks you through the scope, prompting you to list deliverables, acceptance criteria and exclusions rather than leaving a blank "services" field that courts find unenforceable for uncertainty. Next you set the consideration and the payment schedule, attaching milestones to dates so each tranche is tied to a defined output.

The guided fields then cover term and termination, where you choose a fixed term or a rolling engagement and set the notice period for exit on either side. You handle intellectual property by selecting assignment or licence, and confidentiality by choosing a survival period that outlasts the engagement. The form prompts you to fix the governing law and the dispute-resolution route, arbitration or court, and the seat, which matters most in cross-border work. Once the fields are complete the template assembles a clean agreement ready to sign, and you can adapt any clause before execution. If you also need to issue formal correspondence around the engagement, the legal notice and compliance templates handle demand letters and statutory notices.

The first and most damaging mistake is leaving the scope loose. "Provide consulting services as required" is not a scope, it is an invitation to litigate, and Indian courts have voided clauses for uncertainty when the obligation could not be ascertained. The second is forgetting to stamp the agreement, then trying to produce it in court only to find it inadmissible until duty and penalty are paid, which can stall an otherwise strong claim for months. The third is copying a broad non-compete from a foreign template; under Section 27 a clause restraining the provider from working elsewhere is simply void in India, so the protection you thought you bought does not exist.

The fourth mistake is silence on intellectual property, which leaves the client paying for deliverables it cannot freely exploit because no assignment was recorded. The fifth, and increasingly common, is misclassifying the relationship: structuring what is really employment as a service agreement to dodge EPF, gratuity and notice obligations. Authorities and courts look at the substance, the degree of control, the integration into the business, the exclusivity, so the label on the document offers no shelter. A final practical error is omitting a clear dispute-resolution clause, which turns a quick arbitration into a slow, expensive jurisdictional skirmish. For the employment-side documents that a genuine staffing relationship needs instead, see the employment contract and HR templates.