A software & technology licensing agreement in Nepal grants the right to use, modify, or distribute software while defining ownership, royalties, and regulatory compliance. Our firm helps you draft, negotiate, and obtain the necessary approvals from NTA, NRB and other authorities.
What is Software & Technology Licensing Agreements in Nepal?
In Nepal, a software & technology licensing agreement is a contract that authorises a licensee to use, modify, or distribute software, source code or related digital assets, while specifying ownership rights, royalty structures, and compliance with the Electronic Transactions Act, 2063 and the Copyright Act, 2059.
Key Elements of a Nepali Software Licensing Contract
- Grant of Rights: Scope of use, modification, and distribution.
- Royalty & Payment Terms: Fixed, tiered, or usage‑based fees, subject to withholding tax rules of the Inland Revenue Department.
- Compliance Clauses: Obligations under the Nepal Telecommunication Authority (NTA) for telecom‑related software or Nepal Rastra Bank (NRB) for fintech platforms.
- Dispute‑Resolution: Jurisdiction‑specific clauses enforceable in District Courts or the Supreme Court of Nepal.
When is a software licensing lawyer required in Nepal?
You need legal counsel if the software touches regulated sectors, involves cross‑border IP transfers, or requires any of the following:
- Regulatory approval from NTA or NRB.
- Foreign investment reporting under the Foreign Investment and Technology Transfer Act.
- Complex royalty structures that trigger VAT registration with the Inland Revenue Department.
- Unclear ownership or prior agreements that demand due‑diligence.
How to complete the software licensing agreement process in Nepal
- Initial Consultation & IP Audit – Verify copyright registration and confirm the licensor’s incorporation with the Office of Company Registrar. [INTERNAL LINK: company registration in Nepal → /corporate/company-registration]
- Due Diligence & Regulatory Scan – Identify NTA/NRB jurisdiction, collect any pending notices from the Department of Industry or the Cyber Bureau.
- Drafting the License – Use ETA‑approved e‑signatures, define grant scope, royalty calculations, confidentiality, and audit rights.
- Regulatory Submission (if required) – File the draft with NTA for telecom software or NRB for fintech, attaching company registration certificates and tax clearance. Incomplete tax clearance often leads to a return of the file.
- Execution & Notarization – Obtain notarized signatures; Nepali‑language notarization typically takes 5–7 business days.
- Registration & Tax Filings – Record the license with the Inland Revenue Department for royalty withholding tax and, where applicable, register the transaction with the Department of Industry for foreign technology transfer. [INTERNAL LINK: foreign investment approval process → /foreign-investment/fdi-approval]
- Post‑Execution Compliance – Monitor quarterly royalty reporting, data‑privacy safeguards under the Individual Privacy Act, and renewal of sector‑specific licences.
Our Legal Services for Software Licensing
- Conduct a thorough IP audit to confirm ownership and prior assignments.
- Draft a licence that complies with the Electronic Transactions Act, uses ETA‑approved e‑signatures, and aligns royalty calculations with the Income Tax Act.
- Negotiate and secure regulator approvals from NTA, NRB, and the Department of Industry.
- Prepare Nepali‑language translations and handle notarization to satisfy regulator requirements.
Fees, Timeline and Practical Considerations
- Technology complexity – Custom platforms increase drafting time and fees.
- Regulatory involvement – NTA or NRB clearance adds 4–8 weeks and filing costs.
- Foreign parties – Verification of overseas shareholders under the Foreign Investment and Technology Transfer Act may extend the timeline.
- Document readiness – Missing registration or tax certificates often cause a two‑week delay.
- Negotiation depth – Detailed royalty or audit clauses raise hourly billing.
Without major regulatory hurdles, most licences are drafted and executed within 3–5 weeks. When NTA or NRB approval is required, the process can stretch to 8–12 weeks, especially if additional technical details are requested.
Common Mistakes and Compliance Risks
- Incorrect company objectives – Failure to list software licensing in the company’s objectives can lead to Department of Industry rejection.
- Missing royalty tax registration – Not registering royalty payments with the Inland Revenue Department results in withholding tax penalties.
- Overlooking foreign‑ownership caps – Exceeding limits under the Foreign Investment and Technology Transfer Act may breach the law.
- Vague grant‑of‑right language – Ambiguous clauses can be interpreted against the licensee, jeopardising enforceability.
- Skipping regulator pre‑approval – Launching telecom‑related software without NTA clearance may trigger service‑blocking orders.
- Insufficient confidentiality provisions – Weak NDAs expose proprietary code, especially when the licensor is overseas.
- No Nepali translation – Regulators will reject agreements lacking a certified Nepali version.
What Clients Receive
- A fully vetted software licensing agreement signed in compliance with the Electronic Transactions Act.
- All required regulatory approval letters from NTA, NRB, or the Department of Industry.
- Tax registration certificates for royalty payments and VAT, if applicable.
- A compliance checklist outlining post‑execution obligations and reporting schedules.