Software R&D

Commercial Software vs. Internal-Use Software for the R&D Tax Credit

Commercial software developed for sale, lease, or licensing may warrant review as qualified research, while internal-use software is generally excluded. The distinction turns on the primary purpose of the software.

A common question is the distinction between commercial software and internal-use software for the R&D tax credit. The short answer is that commercial software developed for sale, lease, or licensing may warrant review as qualified research, while internal-use software is generally excluded. The distinction turns on the primary purpose of the software. This page explains the framework in general terms. It is educational and is not individualized advice. For the foundational framework, see our page on internal-use software.

The Primary-Purpose Distinction

The distinction between commercial and internal-use software turns on the primary purpose of the software:

  • Commercial software — software developed primarily for sale, lease, or licensing to third parties. This may warrant review as qualified research, provided the other requirements are met.
  • Internal-use software — software developed primarily for the taxpayer's own internal use. This is generally excluded under Section 41(d)(4)(E) and Treasury Regulation §1.41-4(c)(6).

Software That Enables a Non-Software Business Component

Software that enables a non-software business component (e.g., a manufacturing process) may warrant review under the excepted-software rules, even if the software is used internally. The analysis depends on whether the software is an integral part of a non-software business component.

Dual-Function Software

Software with both internal and external functions (dual-function software) may be treated under special rules. The analysis depends on the specific regulatory tests in Treas. Reg. §1.41-4(c)(6).

Hypothetical Example

Consider a company that develops software to sell to other companies. This is commercial software and may warrant review as qualified research.

By contrast, if the company develops the same software for its own internal use, it may be internal-use software and excluded.

If the company develops software to control a new manufacturing process (a non-software business component), the software may warrant review under the excepted-software rules, even though it is used internally.

These examples are illustrative only and do not state whether any particular activity qualifies.

Documentation That May Help

Records that can help support the commercial vs. internal-use analysis include records showing the primary purpose of the software, whether it is sold, leased, or licensed, and whether it enables a non-software business component. For more, see our page on R&D tax credit documentation.

Key Takeaway

Commercial software developed for sale, lease, or licensing may warrant review as qualified research, while internal-use software is generally excluded. The distinction turns on the primary purpose of the software, and software that enables a non-software business component may warrant review under the excepted-software rules. Because the analysis is fact-specific, professional review is appropriate before claiming the credit.

Sources

  1. Internal Revenue Code §41

    Cornell Law Institute (LII)

    Section 41(d)(4)(E) addresses the internal-use software exclusion (not self-executing).

  2. Treasury Regulation §1.41-4

    Cornell Law Institute (LII)

    Section 1.41-4(c)(6) provides the detailed IUS, dual-function, excepted, and non-IUS software rules.

  3. Instructions for Form 6765

    Internal Revenue Service

    Summarizes qualified research and excluded activities, including internal-use software.

  4. Research Credit

    Internal Revenue Service

    IRS landing page for the Credit for Increasing Research Activities.

By R&D Ledger Editorial Team

Last reviewed: August 2026

Related educational pages

R&D Ledger

Organize your R&D documentation throughout the year.

Explore R&D Ledger