#Blog

Master Services Agreement (MSA) Template: Key Clauses for Nepali Businesses

October 28, 2025 Uncategorized by admin_lawsagar

Table of Contents

Introduction

A Master Services Agreement (MSA) is the commercial backbone for repeated services between a client and a supplier — commonly used in IT outsourcing, managed services, consulting and long-term vendor relationships. For Nepali businesses, a well-drafted MSA clarifies scope, pricing, deliverables, intellectual property, confidentiality, liabilities, termination mechanics and dispute resolution — and aligns those obligations with the National Civil Code and sectoral rules such as NRB outsourcing guidance for banks. Use an MSA template as a master contract, then attach Statements of Work (SoWs) for each project to keep terms standardised and reduce renegotiation friction.

1. What is a Master Services Agreement (MSA) and why Nepali businesses need one

A Master Services Agreement (MSA) is a standing contract that sets the legal terms governing a commercial relationship where multiple transactions or projects will occur over time. It defines baseline terms (payment, liability, IP, confidentiality, warranties, and dispute resolution), while the specific scope and pricing for each engagement are contained in individual Statements of Work (SoWs), purchase orders or work orders that “plug into” the MSA.

Why use an MSA in Nepal?

Consistency and speed: Negotiations focus on project specifics, not re-litigating basic contract terms each time.
Risk management: Standardised liability, indemnity and IP clauses protect both parties across engagements.
Regulatory alignment: For regulated sectors (banks, NBFCs), the MSA can embed sector-specific controls (data handling, audit rights, regulatory reporting) required under NRB or other regulators.

MSA use-cases common in Nepal: IT outsourcing, managed services, consulting retainer arrangements, long-term maintenance contracts for equipment, and recurring professional services.

2. Before you use a Master Services Agreement template — legal fundamentals in Nepal

Before inserting clauses from a generic MSA template, counsel must check three legal fundamentals under Nepal law: (1) contract formation & validity; (2) statutory restrictions; and (3) enforceability of core clauses.

Contract formation & validity: Under Nepal’s National Civil Code (Muluki Civil Code), contracts require offer, acceptance, lawful consideration, capacity, and lawful object. A written MSA with clear signatures satisfies the “writing” requirement for many agreements and supports enforceability.
Statutory restrictions and public policy: Certain clauses can be void if they contravene statutory prohibitions or public policy (for example, restraints on trade may be scrutinised). Also be mindful of sectoral laws (banking, insurance, telecoms) that may require additional terms or pre-clearance for outsourcing. NRB’s outsourcing guidance requires that banks evaluate operational risks and maintain oversight of outsourced functions.
Arbitration and dispute resolution: Nepalese law recognises arbitration agreements if they are in writing and refer to a defined legal relationship. Recent reforms and ordinances aim to modernise arbitration; make sure your arbitration clause is consistent with local formalities (and consider seat and enforceability issues if you pick a foreign seat).

Practical counsel tip: Always adapt the MSA template to the specific regulatory context of the client’s industry and the bargaining power between parties. A one-size-fits-all template risks regulatory non-compliance or unenforceable obligations.

3. Structure of a practical MSA template (recommended table of contents)

A robust MSA template for Nepali businesses should contain the following core sections (each expanded with detailed sub-clauses below):

Definitions and interpretation
Scope of services; SoW mechanism
Term and renewal
Fees, invoicing and payment terms
Performance standards and SLAs (service level agreements)
Change control and variation
Acceptance testing and deliverables
Intellectual property rights (background vs foreground IP)
Confidentiality and data protection
Subcontracting and third-party vendors
Warranties and representations
Limitation of liability and indemnities
Insurance requirements
Termination and exit (including transition services)
Force majeure
Dispute resolution and governing law
Notices, assignment, survival and miscellaneous clauses
Schedule/Annexes — SoWs, pricing schedules, SLAs, security checklist

This structure mirrors best-practice MSA templates used globally while leaving space for Nepal-specific content such as compliance with the National Civil Code and sectoral regulatory provisions.

4. Key clauses explained — legal drafting notes and Nepal-specific tips

Below I explain the essential clauses you should include in your MSA template, with drafting pointers for Nepal.

4.1 Definitions & interpretation

Why it matters: Precision in definitions prevents ambiguity disputes over what “services,” “deliverables,” “confidential information” or “force majeure” mean.

Drafting tips:

Define “Services”, “Deliverables”, “SoW”, “Background IP”, “Foreground IP”, “Confidential Information” and “Business Day.”
Use plain, unambiguous language and a rules-of-construction clause (headings do not affect interpretation; singular includes plural, etc.).

4.2 Scope of services and SoW mechanism

Why it matters: The MSA should not be a vague umbrella — it should state how SoWs are created, approved and become binding.

Drafting tips:

Require a signed SoW for each project, and make the SoW incorporated by reference.
Prescribe a minimum content for SoWs: scope, deliverables, milestones, acceptance criteria, price, schedule, and named personnel.
Include an escalation process for scope disputes.

SEO phrase: include “MSA template Nepal” and “MSA clauses Nepal” naturally in the paragraph.

4.3 Term and renewal

Why it matters: Parties need certainty about contract duration and the mechanism for automatic renewal.

Drafting tips:

Use an initial fixed term (e.g., 1–3 years) with renewal options.
Provide break rights for material breach with cure periods.

4.4 Fees, invoicing and payment terms

Why it matters: The practical lifeblood of the relationship; clarity avoids payment disputes.

Drafting tips:

Define currency, payment schedule, late payment interest (statutory or capped), and tax responsibilities (including withholding tax on cross-border payments).
State consequences for delayed payment (suspension rights) and a dispute resolution process for invoiced items.

Note: Cross-border payments should reflect NRB rules and any foreign exchange or remittance requirements.

4.5 Service levels (SLAs) and performance

Why it matters: If you are providing technical or time-sensitive services (IT, maintenance), SLAs quantify expectations and remedies.

Drafting tips:

Include measurable metrics (uptime %, response times) and remedies (service credits).
Cap remedies at a reasonable portion of monthly fees to balance enforceability and fairness.

4.6 Change control

Why it matters: Projects change. The MSA should force a documented change-control process to prevent scope creep.

Drafting tips:

Any change requires a written change order; price/time impacts must be assessed and agreed before execution.

4.7 Acceptance testing & deliverables

Why it matters: Avoid “accepted by silence” disputes by defining acceptance criteria and testing periods.

Drafting tips:

Define acceptance procedures, time for testing, and deemed acceptance if client fails to respond in the testing window.

4.8 Intellectual Property (Background vs Foreground)

Why it matters: IP ownership determines who can reuse code, designs, methodologies and whether the client gets full ownership or a license.

Drafting tips:

“Background IP” remains with the creator; “Foreground IP” (work product created under the SoW) should have a clear ownership regime — either assignment to the client or an exclusive/perpetual license depending on negotiations.
For software, consider source code escrow or escrow triggers (vendor insolvency, breach) to protect the client.
Include licence grants for necessary background IP with limited use rights.

4.9 Confidentiality and data protection

Why it matters: Robust confidentiality and data handling clauses protect trade secrets and personal data. Data obligations are particularly critical for financial institutions and health sector clients.

Drafting tips:

Define Confidential Information and carve out public domain.
Add specific security obligations, DPI (data protection) compliance, breach notification timelines, and assistance with regulatory investigations.
For cross-border data transfers, include compliance with applicable data protection standards and client’s instructions about data location.

Include NRB/sector-specific obligations for supervised entities (e.g., banks) that require audit rights and periodic compliance reporting.

4.10 Subcontracting and third-party vendors

Why it matters: Most service providers subcontract; the MSA must control that risk.

Drafting tips:

Require prior written consent for subcontracting material services.
Flow-down obligations (confidentiality, IP, SLAs) should be imposed on subcontractors.
Retain primary liability for acts/omissions of subcontractors.

4.11 Warranties and representations

Why it matters: Common warranties cover authority, performance to standards, non-infringement, and compliance with laws.

Drafting tips:

Keep warranties precise and tied to deliverables; avoid open-ended performance warranties that are impossible to achieve.
Include a warranty period aligned with industry practice (e.g., 90 days for services, 12 months for major deliverables).

4.12 Limitation of liability and indemnities

Why it matters: Balance risk allocation. Clients want vendor accountability; vendors want caps to prevent catastrophic damages.

Drafting tips:

Cap liability to a multiple of fees (e.g., 12 months’ fees or total fees paid in the prior 12 months). Avoid blanket caps for gross negligence or willful misconduct (courts may refuse unreasonable exclusions).
Carefully draft IP infringement indemnity and third-party claims.
Exclude consequential or indirect damages but consider carve-outs (e.g., for confidentiality breaches or IP infringement).

Practical note (Nepal): Nepalese courts may scrutinise unconscionable exclusions, particularly where bargaining power is unequal. Tailor the cap to the client’s bargaining position and sectoral risk.

4.13 Insurance

Why it matters: Insurance backstops contractual liabilities.

Drafting tips:

Specify minimum levels: professional indemnity, cyber insurance, public liability with currency and territory specifics. Require certificates of insurance on request.

4.14 Termination and exit management

Why it matters: A smooth exit minimises business disruption; this is especially important for critical IT services.

Drafting tips:

Include termination for convenience (with notice) and termination for cause (material breach with cure period).
Include transition assistance obligations: the supplier must provide reasonable transition services and data export on termination, at cost or as agreed.
Consider phased exit fees and migration timelines for complex services.

4.15 Force majeure

Why it matters: Carve out non-attributable risks (natural disasters, wars) from liability but include notice and mitigation obligations.

Drafting tips:

Define what qualifies, notice requirements, and step-in rights or suspension mechanisms. Don’t use an overly expansive clause that excuses poor performance without mitigation.

4.16 Dispute resolution and governing law

Why it matters: Decide whether disputes stay in Nepal or go to an international forum; this impacts enforceability and costs.

Drafting tips:

Arbitration: specify seat (e.g., Kathmandu or another neutral seat), rules (UNCITRAL, ICC, or local Arbitration Act), number of arbitrators, language, and interim relief mechanism. Nepal recognises arbitration agreements in writing; recent reforms aim to update the framework — consider local counsel.
Governing law: Parties can select governing law (Nepal law or foreign law). If the contract is governed by foreign law, consider enforceability issues for local assets.
Court litigation: specify exclusive jurisdiction for injunctive relief if arbitration does not provide interim relief.

4.17 Notices, assignment and survival

Why it matters: Practical administration.

Drafting tips:

Prescribe authorised representatives for notices, and prevent assignment without consent except to affiliates (or on insolvency).
List survival clauses (IP, confidentiality, indemnities remain post-termination).

5. Practical MSA template checklist — drafting & negotiation playbook

When you use an MSA template, run a short legal checklist before signature:

Compliance check: Does the MSA include sector-specific compliance for regulated clients? (e.g., NRB’s outsourcing rules).
IP ownership: Does the SoW clearly define ownership vs license for deliverables?
Limitation of liability: Is the cap proportionate and does it exclude gross negligence?
Security & data: Are security standards, audits and breach protocols included?
Acceptance & change control: Are acceptance tests, change orders and payment triggers aligned?
Exit plan: Are transition services, data handover and escrow provisions available?
Governing law & arbitration: If cross-border, have you checked seat, local enforceability and interim relief?
Insurance: Certificate of insurance and minimum levels set.
Subcontracting: Are flow-downs and vendor approval procedures present?
Language & interpretation: For bilingual contracts, which text prevails?

Use this checklist during negotiation — each item is a potential deal-breaker or a negotiated premium.

6. Special considerations for common Nepal scenarios

6.1 MSA for IT & software providers

Include source code escrow for critical software; specify escrow triggers.
Add specific service credits and measurable SLAs for system uptime.
Include software licensing mechanics, maintenance and patch delivery timelines. Relevant global MSA practices apply; local implementation must consider cross-border data transfer rules and any NRB/sector demands for data localisation.

6.2 MSA for banks and financial institutions

NRB’s outsourcing guidance demands board-level oversight, risk assessment and clear audit and reporting rights in MSAs. Ensure an audit clause, audit frequency, and liability matrix aligned with NRB expectations.

6.3 Cross-border MSAs and foreign suppliers

Address currency, tax withholding, exchange control, repatriation of fees and compliance with NRB if the counterparty receives funds abroad.
Consider the risk of a foreign law governing the contract if you’ll need enforcement in Nepal — add local enforcement mechanisms for Nepalese assets.

7. Sample MSA template outline (short-form model clauses)

Below is a compact blueprint of clauses you can copy into a template and tailor with counsel. (This is a summary — each clause requires full drafting.)

1. Parties and effective date
“Between [Client name], a company incorporated under Nepal law, and [Supplier name], a company incorporated under [jurisdiction], effective as of [date].”

2. Definitions
(Define core defined terms.)

3. Services & SoWs
“The Supplier shall provide Services as specified in SoWs. Each SoW becomes a binding part of this Agreement upon signature by authorized representatives.”

4. Fees & invoicing
“Client shall pay fees as set out in each SoW. Payments within 30 days of invoice. Currency: NPR/USD. Late payment interest at [X]% per annum.”

5. IP
“Background IP remains the owner’s. All Foreground IP created under a SoW shall be [assigned to the Client/granted under exclusive perpetual license to Client] subject to Supplier’s retained rights.”

6. Confidentiality
“Parties shall protect Confidential Information with reasonable care, not less than that used for their own confidential materials. Breach requires notice within 5 business days and remedial action.”

7. Limitation of liability
“Except for liability for willful misconduct or gross negligence, neither party’s liability exceeds [12 months’ fees]. Neither party liable for indirect or consequential damages except for confidentiality and IP indemnity claims.”

8. Indemnity
“Supplier indemnifies Client against third-party IP claims arising from Supplier deliverables, subject to notice and defence cooperation.”

9. Term & termination
“Initial term 24 months, auto-renew unless 90 days’ notice. Termination for material breach with 30 days’ cure period.”

10. Dispute resolution
“ARBITRATION: Any dispute shall be finally settled by arbitration seated in Kathmandu under [Arbitration Rules], with the language of arbitration [English/Nepali].”

11. Miscellaneous
“Assignment only with prior consent; notices in writing, survival clauses, entire agreement clause.”

This outline is a starting point — customise for sector rules, client risk tolerance and regulatory requirements.

8. Practical negotiation tips (what clients usually want and what vendors should accept)

Clients want IP assignment of deliverables, strong confidentiality, low liability caps for critical breaches, and termination rights with data return.
Vendors want fee certainty, reasonable liability caps, predictable change control to avoid scope drift, and clarity on third-party software licenses.
There is a natural negotiation trade-off: more favourable IP and termination rights for the client usually means a higher service fee or tighter acceptance criteria.

9. How to use this MSA template in your firm — process & implementation

Create a Master Template with modular clauses and comment blocks for optional language (e.g., for IP assignment vs license).
Prepare SoW templates for each service line (software development, managed services, consulting).
Establish playbook thresholds for legal exceptions (e.g., who can approve increasing liability cap).
Use version control and maintain a clause library with precedent language for quick negotiation.
Keep a regulatory watch for NRB, telecom, or other sector circulars that mandate contract terms.

10. FAQs

Q: Is an MSA enforceable under Nepal law?
A: Yes. A written MSA with clear offer and acceptance is generally enforceable under the National Civil Code; arbitration clauses are enforceable if in writing. Tailor terms for sectoral regulatory requirements.
Q: Can a liability cap be enforced in Nepal?
A: Liability caps are commonly enforced, but courts may scrutinise unconscionable or overly broad exclusions (particularly for gross negligence or where bargaining power is unequal). Draft reasonable and proportionate caps.
Q: Should the MSA be governed by Nepal law or foreign law?
A: For Nepal-based operations and asset enforcement in Nepal, Nepal law is practical. If parties opt for foreign law, also include local enforcement mechanisms (e.g., local injunctive relief) and consider seat of arbitration carefully.
Q: What data protections should be included?
A: Specify storage and transfer locations, breach notification timelines, security standards, audit rights, and compliance with sector specific rules (e.g., NRB for banks).
Q: When should we use source code escrow?
A: For mission-critical software where business continuity depends on access to source code (e.g., core banking systems), escrow protects clients if a vendor becomes insolvent or materially breaches.

Write a comment