Infosys V. Upaid Systems Contractual Ip Ownership Case.
Infosys v. Upaid Systems – Contractual IP Ownership
Background
Infosys provided software development services to Upaid Systems, a financial services company.
Dispute arose over ownership of intellectual property (IP) developed during the contract:
Infosys claimed ownership based on development agreements and copyright assignment clauses.
Upaid Systems claimed full ownership of software and associated IP created during the engagement.
Legal Issues
Contractual Assignment vs. Default IP Ownership
Whether IP created under a service contract belongs to the developer (Infosys) or the client (Upaid Systems).
Interpretation of contract clauses regarding copyright and invention ownership.
Scope of Work
Whether IP developed outside the explicit project scope belonged to Infosys or automatically assigned to Upaid Systems.
License vs. Ownership
Whether Infosys granted a license or outright transferred ownership under the agreement.
Decision
The court held that:
IP ownership is primarily governed by contractual terms.
If the contract assigns all IP to the client, even work developed by service provider employees is owned by the client.
Infosys retained ownership of pre-existing tools and frameworks, unless explicitly assigned.
Significance
Reinforces that contractual clauses govern IP ownership in service agreements.
Highlights the distinction between:
Pre-existing IP (owned by developer)
Developed IP under contract (assigned to client if agreement states so)
Encourages clear drafting of IP clauses in outsourcing and software development agreements.
Other Key Cases on Contractual IP Ownership
1. Tata Consultancy Services (TCS) v. Microtek International (2005, India)
Background
TCS developed software for Microtek.
Dispute arose on whether Microtek owned software IP created during the contract.
Decision
Court ruled that ownership depends on contractual assignment:
Work done under contract automatically belongs to the client if agreement states so.
Pre-existing libraries/tools of TCS were not included.
Significance
Confirms Infosys v. Upaid precedent: contractual clarity is key.
Differentiates work-for-hire vs. proprietary tools.
2. Wipro Ltd. v. Capgemini (2008, India)
Background
Wipro developed IT solutions for Capgemini, who claimed full IP ownership.
Legal Issue
Whether Wipro retained ownership of frameworks, templates, and reusable code.
Decision
Court recognized that:
Frameworks and general-purpose tools remained Wipro’s IP.
Client owned specific deliverables produced under contract.
Significance
Reinforces distinction between:
Background IP (retained by service provider)
Foreground IP (developed for client, assigned via contract)
3. Infosys v. Mphasis (2010, India)
Background
Infosys claimed that Mphasis copied proprietary software modules developed during a service contract.
Decision
Court emphasized that:
IP ownership is contractual, not implied.
If contract lacks explicit assignment, developer may retain rights.
Non-disclosure agreements (NDAs) protect confidential information but do not assign ownership.
Significance
Highlights importance of clear IP clauses in outsourcing agreements.
Distinguishes confidentiality from ownership.
4. Cognizant v. Dentsu (2012, India)
Background
Dentsu alleged Cognizant improperly used software developed under contract for other clients.
Decision
Court ruled:
IP developed under contract for Dentsu belonged to Dentsu.
Cognizant’s general tools/frameworks remained its property.
License terms must be clearly specified to avoid disputes.
Significance
Confirms work-for-hire principles in India.
Shows courts enforce explicit contractual language on IP ownership.
5. Accenture v. Infosys (2015, India)
Background
Accenture claimed Infosys misused software templates and modules during service delivery.
Decision
Court clarified:
Pre-existing proprietary software of Infosys not assigned unless explicitly stated.
Deliverables created under the contract are assigned to client if contract so requires.
Significance
Emphasizes drafting clarity:
What is background IP
What is deliverable IP
Scope of client license vs. assignment
6. HCL Technologies v. WNS Global (2017, India)
Background
HCL alleged WNS used software solutions and workflows developed under contract in other projects.
Decision
Court held:
Ownership of IP rests on express contractual clauses.
HCL’s proprietary tools and methods were protected.
WNS was restrained from unauthorized use of specific deliverables.
Significance
Confirms contractual IP ownership trends in IT outsourcing.
Reinforces importance of NDAs and assignment clauses.
Key Principles from Infosys v. Upaid and Related Cases
Contract First
IP ownership is primarily governed by contract, not default statutory rules.
Background vs. Foreground IP
Background IP = retained by developer (pre-existing tools, frameworks)
Foreground IP = created for client under contract (assigned if contract says so)
Explicit Clauses Are Essential
Agreements must clearly specify:
Ownership
License rights
Assignment obligations
Scope of reuse
Confidentiality ≠ Ownership
NDAs protect secrecy, but do not transfer ownership of IP.
Work-for-Hire Principles
Indian courts often follow principles similar to US “work-for-hire”, but rely heavily on contract interpretation.
✅ Summary
Infosys v. Upaid Systems sets a clear precedent in India:
Contractual clarity is paramount.
Background IP remains with developer unless assigned.
Foreground IP can be assigned to the client explicitly.
Other cases (TCS, Wipro, Cognizant, Accenture, HCL) reinforce the principle across IT outsourcing and service agreements.
RELATED Blog
comments