Software Licensing Agreement SaaS SLA Bangladesh: Legal Guide

Executive Summary & Statutory Authority

Bangladesh does not possess a single, unified "Software Contracts Act." Instead, Software Licensing Agreements and Software-as-a-Service (SaaS) contracts are governed by a composite legal architecture drawn from general contract law, IP statutes, cyber law, taxation statutes, and — for regulated entities — Bangladesh Bank's ICT security mandates. The foundational instrument remains the Contract Act, 1872, whose Sections 10, 23, 27, 28, 73, and 74 determine the enforceability of license grants, restrictive covenants, dispute forum clauses, and — critically — the enforceability of SLA service credits and liquidated damages. Overlaid upon this is the Copyright Act, 2023 (repealing the 2000 Act), which expressly classifies "computer programme" as literary work under Section 2(8) and imposes strict formalities for IP assignment under Sections 15, 18, and 19 — including a dangerous default 5-year reversion period and a 1-year non-exploitation lapse rule that can silently strip a paying client of its software ownership. The Information and Communication Technology Act, 2006 (Sections 7–10, 16, 65–66) confers legal validity upon electronic contracts, e-signatures, and digital audit logs — essential for SaaS transactions executed entirely online and for evidentiary reliance on uptime monitoring data in SLA disputes. For regulated financial institutions, Bangladesh Bank's ICT Security Guidelines mandate tripartite source code escrow arrangements, audit rights, and data localization compliance. Cross-border SaaS subscriptions additionally trigger the Foreign Exchange Regulation Act 1947, Income Tax Act 2023 withholding provisions, and VAT Act 2012 reverse-charge mechanisms.

This treatise provides the definitive doctrinal and procedural roadmap for structuring, negotiating, executing, and enforcing software licensing and SaaS agreements under Bangladeshi law, with particular emphasis on SLA uptime enforceability, IP allocation traps, source code escrow for regulated sectors, and cross-border remittance compliance.

Section 1: Legal Characterization — License vs. SaaS vs. Services Contract

1.1 The Doctrinal Distinction

Bangladeshi courts and regulators do not treat "software licensing" as a monolithic category. Three distinct legal characterizations arise, each carrying different statutory consequences:

1. Perpetual/Term License (On-Premise): A grant of a limited, non-exclusive right to use compiled software installed on client infrastructure. This resembles a chattel-lease hybrid under general contract principles and typically triggers ad valorem stamp duty considerations if bundled with an outright IP transfer.
2. Software-as-a-Service (SaaS): A pure services contract wherein no code is delivered or installed; the client merely receives remote access credentials to vendor-hosted infrastructure. Under Section 10 of the Contract Act, 1872, this is treated as a continuing services obligation rather than a conveyance of property, materially affecting how breach remedies (Sections 73–74) are calculated.
3. Custom Development / Contract for Services: Where a vendor builds bespoke software for a client, ownership defaults to the developer/author absent an express written assignment — a principle affirmed judicially (see Section 2 below).

1.2 Why Characterization Matters

The characterization dictates: - Stamp duty treatment (Schedule I, Article 5(c) — flat BDT 300 vs. Article 23 — ad valorem on assignment consideration); - VAT treatment (imported SaaS access is a "service" attracting reverse-charge VAT under Section 15, VAT & SD Act 2012, whereas perpetual license purchase may be treated differently for customs/import valuation purposes if delivered on physical media); - Foreign exchange remittance routing (operational SaaS subscription fees are typically remitted as ordinary business expenditure through Authorized Dealer banks, whereas royalty/technical fee characterization triggers BIDA's 6% threshold scrutiny).

1.3 Drafting Implication

Counsel must expressly state in the recitals and definitions section of every agreement whether the arrangement is a "License," a "Subscription Service," or a "Development Engagement." Ambiguous hybrid drafting — common in Bangladeshi SME technology contracts — creates downstream disputes over tax characterization, IP ownership, and remedy availability. Best practice mandates a standalone "Nature of Agreement" clause stating: "This Agreement constitutes a services engagement for cloud-hosted access and does not convey, sell, or transfer any ownership interest in the underlying Software, source code, or infrastructure."

Section 2: Intellectual Property Allocation — Ownership, Assignment, and the Statutory Reversion Trap

2.1 Statutory Foundation

The Copyright Act, 2023 governs software IP allocation in Bangladesh. Section 2(8) expressly includes "computer programme" within the definition of "literary work," extending full copyright protection to source code, object code, and — per evolving interpretation — associated database schemas and API architecture.

2.2 First Ownership: Employee vs. Independent Contractor

Section 15 establishes that the author is generally the first owner of copyright. Section 17 creates the critical "work made for hire" carve-out:

• Contract of Service (Employment): Where software is created by an employee in the course of employment, the employer is the first owner, absent a contrary agreement.
• Contract for Services (Independent Contractor/Vendor): Where an external developer, freelancer, or vendor is engaged, ownership remains with the creator/vendor unless expressly assigned in writing to the commissioning client.

This distinction was judicially affirmed in Dr. A.L.M. Abdur Rahman v. Director General, Bangladesh Rice Research Institute (BRRI), 48 DLR (HCD) 487, where the High Court Division held that absent an express written assignment, the creator of intellectual work retains fundamental copyright even where the institutional client provided funding, unless the creator was a regular employee acting within assigned duties. Application: Bangladeshi SaaS companies engaging third-party contractors or offshore development shops for microservices must obtain explicit written IP assignment deeds — funding alone does not confer ownership.

2.3 The Statutory Reversion Trap (Sections 18–19)

This is the single most dangerous latent risk in Bangladeshi software contracting:

• Duration Default: If an assignment agreement fails to specify a duration, Section 19 deems the assignment to last only 5 years from the date of assignment, after which rights revert to the assignor.
• Territorial Default: If territory is unspecified, the assignment is presumed limited to Bangladesh only.
• Non-Exploitation Lapse: If the assignee fails to exercise the assigned rights within 1 year of assignment, the assignment is deemed to have lapsed and reverts automatically to the original author/vendor.

Commercial Consequence: A Bangladeshi enterprise that commissions a custom SaaS platform under a poorly drafted development contract may discover — five years later — that its external developer has regained full ownership of the codebase, potentially enjoining continued use or demanding re-licensing fees.

2.4 Moral Rights (Section 24)

Moral rights (paternity and integrity) are non-assignable under Bangladeshi law; they can only be waived by express covenant. Software maintenance necessarily involves modification, refactoring, and rebranding of code — all of which could trigger integrity-right claims absent an explicit waiver clause from the original developer(s).

2.5 Model Mitigation Clause

"Pursuant to the Copyright Act, 2023, the Assignor hereby expressly, unconditionally, and irrevocably waives the application of Sections 18 and 19. This assignment of all Intellectual Property Rights is perpetual, worldwide, royalty-free, and irrevocable, and shall not lapse, expire, or revert to the Assignor notwithstanding non-exercise within one (1) year or the expiry of any statutory default period. The Assignor further irrevocably waives all moral rights under Section 24 in respect of modification, adaptation, and integration of the Work."

Section 3: Service Level Agreements — Uptime Guarantees & Enforceability Under Section 73–74

3.1 SLA Architecture Components

A commercially robust SLA schedule in a Bangladeshi B2B tech contract must define:

1. Availability Metric: Typically expressed as 99.9% ("three nines," permitting ~43 minutes monthly downtime) or 99.99% ("four nines"). The formula: Uptime % = (Total Minutes in Month − Excluded Downtime) / Total Minutes in Month × 100.
2. Excluded Downtime: Scheduled maintenance windows (typically off-peak, Bangladesh Standard Time UTC+6), force majeure events, third-party ISP/DNS failures, and client-caused outages.
3. Severity Classification Matrix: Sev-1 (Critical/System Down), Sev-2 (Major/Degraded), Sev-3 (Minor), each with defined response and resolution SLAs (e.g., Sev-1: 30-minute response, 4-hour resolution target).
4. Service Credits: Financial remedies expressed as a percentage rebate of monthly subscription fees, scaled to the severity of the breach.

3.2 The Liquidated Damages Ceiling — Section 74 Contract Act

Sections 73 and 74 of the Contract Act, 1872 govern the enforceability of SLA financial remedies. Section 74 provides that where a contract names a sum payable upon breach, the aggrieved party is entitled to receive "reasonable compensation not exceeding the amount so named" — the named sum operates as a ceiling, not an automatic entitlement.

Landmark Authority: M/S Rahman & Co. v. Bangladesh, 28 DLR (AD) 55 — the Appellate Division held that liquidated damages provisions are not self-executing; courts retain discretion to award only "reasonable compensation" based on demonstrated loss, even where a contract stipulates a specific penalty figure. This has direct application to SLA service credit clauses: if a client attempts to enforce a punitive service credit (e.g., 50% fee forfeiture for one hour of downtime) that grossly exceeds actual commercial loss, a Bangladeshi court may reduce the award to a "reasonable" figure.

Persuasive Authority: Province of West Pakistan v. Mistri Patel & Co., 21 DLR (SC) 499 confirms that genuine pre-estimates of damage do not require strict proof of actual loss, but clauses purporting to exclude liability for gross negligence or willful misconduct may be struck down under Section 23 (unlawful object/public policy).

3.3 Drafting Strategy: Price Adjustment, Not Penalty

Senior counsel structures SLA credits as contractual price adjustments (a mechanism for recalibrating the fee actually earned for degraded service) rather than "damages for breach." This reframing substantially insulates the clause from Section 74 judicial scrutiny, since price adjustment mechanisms are not "penalties" in the classical sense — they represent the parties' agreed valuation of the service actually delivered.

Model Clause: "Service Credits constitute an agreed adjustment to the Fees payable for the Service Period in which the SLA target was not met, reflecting the reduced value of degraded Service, and do not constitute liquidated damages, a penalty, or an admission of breach. Service Credits are the Client's sole and exclusive financial remedy for failure to meet the Uptime Commitment, save in cases of Vendor gross negligence or willful default."

3.4 Evidentiary Reliance on Uptime Logs

Under the ICT Act 2006, Sections 7–9, electronic records — including automatically generated cloud monitoring logs (uptime dashboards, incident tickets, APM tool exports) — are admissible evidence. The State v. Md. Golam Mostafa & Others, 2018 CLR (HCD) 341 confirmed that electronic records and audit logs are admissible to substantiate contractual obligations and breach claims, provided system integrity and chain of custody are demonstrated. SLA schedules should therefore designate the vendor's monitoring system as the "agreed source of truth" for uptime calculation, subject to client audit rights.

Section 4: Source Code Escrow — Regulated Sector Mandates

4.1 Bangladesh Bank ICT Security Guidelines

For Scheduled Banks, Non-Bank Financial Institutions (NBFIs), and Payment Service Providers, Bangladesh Bank's Guideline on ICT Security for Scheduled Banks and Financial Institutions (Version 3.0/4.0), Section 3.3.4, imposes mandatory third-party management obligations, including:

• Comprehensive SLAs for mission-critical software (Core Banking Solutions, RTGS, NPSB, Mobile Financial Services platforms);
• Mandatory tripartite source code escrow agreements ensuring continuity of access upon vendor default, insolvency, or cessation of support;
• Mandatory audit rights permitting internal auditors and Bangladesh Bank inspection teams to examine vendor and cloud-hosting infrastructure;
• Data localization — regulated financial data must not be hosted outside Bangladesh without specific Bangladesh Bank approval.

4.2 Escrow Agreement Architecture

A compliant tripartite escrow structure requires:

1. Parties: Vendor (Licensor), Client (Licensee/Bank), and an independent Escrow Agent (e.g., a vetted local custodian or international escrow house).
2. Deposit Package: Full source code, build/compile scripts, third-party library manifests, container/image definitions, configuration files, and architecture/API documentation — deposited semi-annually or upon each major release.
3. Verification Protocol: The Escrow Agent conducts technical verification (build testing) to confirm the deposited materials actually compile into functioning software matching the production environment.
4. Release Trigger Events: Vendor insolvency or winding-up petition, material and uncured SLA breach leading to termination, or failure to provide maintenance/support for more than 30 consecutive business days.
5. Post-Release License: Upon a valid release trigger, the Client automatically receives a perpetual, royalty-free internal-use license to compile, modify, and self-host the software to maintain business continuity.

4.3 Compliance Certification

Bangladesh Bank inspection teams require confirmation of escrow validity during annual on-site ICT audits. Failure to maintain a valid, tested escrow arrangement for mission-critical vendor software exposes the regulated entity to supervisory action, including restrictions on continued use of the non-compliant system.

Section 5: Cross-Border Remittance, Taxation, and Foreign Exchange Compliance

5.1 Foreign Exchange Regulation Act, 1947 (FERA)

Outward remittance of SaaS subscription fees, software license fees, or royalty payments to foreign vendors must be routed through an Authorized Dealer (AD) Bank. Two regulatory pathways exist:

• Standard SaaS/Software Operational Expenditure: Processed via Form TM as an ordinary business expense, subject to invoice and tax documentation.
• Royalty/Technical Assistance Fees Exceeding Threshold: Where remittances exceed 6% of the previous fiscal year's sales or project cost, prior approval from the Bangladesh Investment Development Authority (BIDA) and Bangladesh Bank's Foreign Exchange Policy Department is mandatory.

Unauthorized circumvention (e.g., direct corporate credit card auto-debit to foreign SaaS providers without AD Bank routing) constitutes a violation of Sections 5 and 8, FERA 1947 — a non-bailable cognizable offense under Section 23, carrying imprisonment up to 2 years, fines, and fund confiscation.

5.2 Withholding Tax (Income Tax Act, 2023)

Sections 119 and 120 mandate Tax Deducted at Source (TDS) on royalty and technical service fee payments to non-resident vendors, generally at 20%, subject to reduction under applicable Double Taxation Avoidance Agreements (DTAA) upon production of a Tax Residency Certificate from the vendor's home jurisdiction.

5.3 Reverse-Charge VAT

Under Section 15 of the VAT and Supplementary Duty Act, 2012, imported SaaS/cloud services are subject to 15% VAT on a reverse-charge basis, obligating the local corporate purchaser (not the foreign vendor) to self-assess, withhold, and deposit the VAT via Treasury Challan/Mushak 6.3 before remittance can be processed by the AD Bank.

Section 6: Dispute Resolution, Limitation of Liability, and Jurisdictional Strategy

6.1 Limitation of Liability (LoL) Clauses

LoL clauses excluding consequential/indirect damages and capping aggregate liability (commonly to 12 months' fees paid) are generally enforceable under Bangladeshi contract law, provided they do not purport to exclude liability for gross negligence, willful misconduct, or fraud — such exclusions risk invalidation under Section 23 (unlawful object/public policy) of the Contract Act, 1872. Best practice carves out "Super-Caps" (higher or uncapped liability) for IP indemnity breaches, confidentiality violations, and data breach incidents.

6.2 Choice of Forum and Foreign Arbitration

Section 28 of the Contract Act, 1872 voids agreements that absolutely restrain a party's right to sue, but exclusive foreign jurisdiction and arbitration clauses are enforceable where the foreign forum has genuine nexus to the transaction. Bangladesh Air Transport v. Singapore Airlines, 47 DLR (HCD) 560 confirmed that exclusive foreign jurisdiction clauses are valid unless unconscionable or wholly detached from the transaction. Domestic courts will stay proceedings under Section 7 of the Arbitration Act, 2001 in favor of a valid foreign arbitration clause (e.g., SIAC, LCIA), and foreign arbitral awards are enforceable via the New York Convention through the High Court Division.

6.3 Limitation Periods — The Strict Bar

Under the Limitation Act, 1908: - Article 115: Suits for breach of an unregistered contract — 3 years from the date of breach. - Article 116: Suits for breach of a registered contract — 6 years. - Section 5 delay-condonation ("sufficient cause") applies to appeals/applications but not to the original institution of civil suits under Articles 115/116 — courts are statutorily bound under Section 3 to dismiss time-barred suits even absent a limitation defense being raised.

Statutory Document Checklist

• [ ] Master Software License / SaaS Agreement — clear license grant vs. cloud-access characterization, defined Authorized Users/Transaction Volume, term and renewal mechanics
• [ ] SLA Schedule — uptime percentage, exclusions, severity matrix, service credit formula, sole-remedy language
• [ ] IP Assignment Deed — Section 18/19 compliant written assignment; explicit waiver of statutory reversion (5-year) and non-exploitation lapse (1-year); moral rights waiver under Section 24
• [ ] Tripartite Source Code Escrow Agreement (mandatory for banks/FIs) — Vendor, Client, Escrow Agent; deposit schedule; release triggers; verification protocol
• [ ] Data Processing Addendum — cross-border transfer controls, Cyber Security Act 2023 compliance, data localization for regulated data
• [ ] Board Resolution / Power of Attorney — corporate authority for signatories, stamped if executed by attorney-in-fact
• [ ] Non-Judicial Stamp Paper (BDT 300) — or Collector of Stamps validation within 90 days for overseas-executed agreements
• [ ] Copyright Registration Form-II filing (optional, DPDT) — source code extracts, flowcharts, assignment deeds
• [ ] Authorized Dealer Form TM — for outward remittance of subscription/license fees
• [ ] Withholding Tax Challan — proof of TDS deduction under Sections 119/120, Income Tax Act 2023
• [ ] VAT Mushak 6.3 Challan — proof of 15% reverse-charge VAT deposit
• [ ] BIDA Outward Remittance Approval — required if royalty/technical fee exceeds 6% of prior year's revenue

Regulatory Fees, Timelines & Penalty Matrix

Frequently Asked Questions

<div style="margin-bottom:12px; padding-bottom:12px; border-bottom:1px solid #1E293B;">
  <a href="https://dpdt.gov.bd/" target="_blank" rel="noopener noreferrer" style="color:#C5A059; font-weight:600; font-size:14px; text-decoration:underline;">Department of Patents, Designs and Trademarks (DPDT) &nearr;</a>
  <p style="color:#94A3B8; font-size:12px; margin:4px 0 0 0; line-height:1.4;">Official Trademark Journal, Patent Applications & IP Opposition Gazettes</p>
</div>

<div style="margin-bottom:12px; padding-bottom:12px; border-bottom:1px solid #1E293B;">
  <a href="https://copyrightoffice.gov.bd/" target="_blank" rel="noopener noreferrer" style="color:#C5A059; font-weight:600; font-size:14px; text-decoration:underline;">Copyright Office Bangladesh &nearr;</a>
  <p style="color:#94A3B8; font-size:12px; margin:4px 0 0 0; line-height:1.4;">Software, Literary, Artistic & Musical Works Copyright Registration</p>
</div>

<div style="margin-bottom:12px; padding-bottom:12px; border-bottom:1px solid #1E293B;">
  <a href="https://www.wipo.int/" target="_blank" rel="noopener noreferrer" style="color:#C5A059; font-weight:600; font-size:14px; text-decoration:underline;">World Intellectual Property Organization (WIPO) &nearr;</a>
  <p style="color:#94A3B8; font-size:12px; margin:4px 0 0 0; line-height:1.4;">International IP Systems, Madrid Protocol & PCT Regulations</p>
</div>