Managing Software License Disputes | Practical Law

Managing Software License Disputes | Practical Law

A discussion of some of the key contract terms commonly at issue in software license litigation and the conceptual and drafting errors that tend to lead to these disputes.

Managing Software License Disputes

Practical Law Legal Update 9-584-6669 (Approx. 4 pages)

Managing Software License Disputes

by Practical Law Intellectual Property & Technology
Published on 28 Oct 2014USA (National/Federal)
A discussion of some of the key contract terms commonly at issue in software license litigation and the conceptual and drafting errors that tend to lead to these disputes.
The terms of software license agreements can lead to disputes that have significant consequences for both licensors and licensees. For a licensee, a dispute that results in the licensor's sudden suspension or termination of the licensee's authority to use the licensed software can significantly harm the licensee's ability to conduct its business.
For a licensor, disputes with a licensee can result in the licensee's nonpayment or setting off of license fees. This could deprive the licensor of significant operating revenue necessary to recoup the costs of developing the software and to invest in the development or acquisition of new products and services.
The licensing parties' counsel must therefore be aware of the license provisions that commonly lead to software license disputes to allow them to better anticipate and manage the associated risks.

Key Provisions That Lead to Software License Disputes

When negotiating and drafting the terms of a software license agreement, the parties frequently overlook how the language used to express these terms could be subject to conflicting interpretations that result in a dispute. Using unclear or ambiguous terms in the agreement can fuel material disagreement over whether a licensee is in compliance with the license terms.
The main provisions in a software license agreement that often lead to disputes include:
  • The scope of the licensee's permitted access to and use of the licensed software.
  • The payment of license fees.
  • Third-party access and use.
  • Updates, improvements and other software modifications.
  • Restrictions on the licensee's right to transfer or sublicense the software.

Scope of Permitted Access and Use

Software license agreements typically limit the scope of the license in several ways, for example, by restricting:
  • The extent to which the licensee may access the software.
  • The purposes for which the licensee may use the software.
The licensor often structures these limitations in the software license agreement to reflect the software's licensed purpose and to help segment the software's different markets and maximize its market value.

Accessing the Software

Licensors usually seek to limit the extent to which licensees can access the software. For example, they may permit a licensee to access the software only:
  • On a single computer or a specific number of computers at any given time.
  • At certain specified facilities of the licensee.
  • On computers or networks running on specific operating systems or hardware platforms.
The parties may dispute the intended scope and application of these restrictions if the software license agreement does not clearly set them out. Disputes can also occur when the agreement does not include a mechanism to accommodate a shift in how or how much the licensee uses the software.
Disputes often also arise in arrangements where the software license agreement fails to clarify if the license access limitations are meant to cap either:
  • The total number of users that may access the software.
  • The number of users that may access the software at a given point in time.

Permitted Use

Licensors typically limit the purposes for which the licensee is authorized to use the software by including a permitted use clause in the software license agreement. This clause can limit a licensee to using the software for "internal use only" or set out a detailed list of permitted uses. For example, the permitted use provision can specify that the licensee may use the software for back office processing, but not for the provision of products or services to third parties.
However, the language setting out these limitations can be vague. For example, a licensee could interpret the term "internal use only" to allow it to:
  • Provide its customers, independent contractors, advisors or other third-party consultants with access to the software (as opposed to only the licensee's employees).
  • Use the software for customer-facing web applications or to remotely interface with its customers.
  • Process information or perform tasks on behalf of its own customers.
Licensees should be wary that licensors may bring a claim for copyright infringement in addition to one for breach of contract if it is alleged that the licensee has used the licensed software for a purpose other than its permitted use.

Payment of License Fees

Pricing and payment terms are among the most common provisions in software license agreements that lead to disputes. Issues that often arise in this context relate to:
  • Vague or ambiguous price structures that can be interpreted differently.
  • The licensor's provision of additional services (for example, installation, testing or training) under unclear cost and payment terms, .
  • Lack of clarity on which party is responsible for paying sales and use taxes.
  • How interest is charged and collected on late payments.
  • The licensee's ability to dispute invoices that it deems incorrect without incurring late payment charges or other penalties.

Third-party Access and Use

Disputes can also arise in situations where the software license agreement is silent or otherwise fails to clearly identify the individuals or class of individuals permitted to access and use the software.
The most common situation involves terms that allow only the licensee's employees to access the software, excluding from access the licensee's third-party agents, contractors or advisors. This type of restriction can be impractical and troublesome for licensees that rely heavily on independent contractors to handle tasks relevant to the software's intended purpose.
In addition, conflicts often ensue when a software license agreement does not specify the means for identifying authorized users (for example, by listing specific employees in an attached exhibit), if required by the licensor.

Restrictions on Transferring or Sublicensing the Software

Software license agreements usually restrict the licensee from transferring or sublicensing the software to third parties. However, licensors sometimes permit licensees to transfer or sublicense the software, for example, if the licensee:
  • Merges with or is reorganized into other related parties, such as subsidiaries or entities that share a common owner with the licensee.
  • Must provide key third-party agents or contractors with access to the software to enable them to undertake certain operational tasks central to the licensee's business.
  • Enters into a joint venture and must sublicense the software product to the joint venture entity.
In these circumstances, conflicts often occur when:
  • The licensee sublicenses or transfers the license to a third party as permitted in the software license agreement, but fails to properly notify the licensor or take other steps required under the agreement to ensure the licensor can enforce its terms against the sublicensee or transferee.
  • A sublicensee or transferee breaches the software license agreement and the licensor and licensee disagree on when or how the licensee must indemnify the licensor for the breach.
  • The parties cannot agree on the amount or payment of additional license fees to the licensor for any third-party use of the software.
  • The licensee allegedly fails to comply with a change of control provision when assigning its license to a third party that acquires the licensee's business, whether through an asset sale or a stock acquisition.
For a more in-depth discussion of these and other contract terms that commonly arise in software license disputes and practice tips for managing the associated risks, see Practice Note, Software License Disputes: Managing the Inherent Risks.