This page provides a practical guide to the internal-use software (IUS) exclusion and its exceptions for the R&D tax credit under Section 41. The IUS rules are complex and involve detailed regulatory analysis. 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 Internal-Use Software Exclusion
Under Section 41(d)(4)(E) and Treasury Regulation §1.41-4(c)(6), software developed primarily for the taxpayer's internal use is generally excluded from qualified research. The statute is not self-executing; the regulatory rules in Treas. Reg. §1.41-4(c)(6) govern the analysis.
What Is Internal-Use Software?
Software is generally internal-use if it is developed primarily for the taxpayer's internal use — for example, software used in the taxpayer's own business operations. Whether software is internal-use is a facts-and-circumstances determination.
Exceptions
The IUS exclusion has exceptions. Software may warrant review if:
- Software for sale, lease, or licensing — software developed for sale, lease, or licensing to third parties may not be internal-use.
- Software enabling 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.
- Dual-function software — software with both internal and external functions may be treated under special rules.
The specific exceptions and their requirements involve detailed regulatory analysis under Treas. Reg. §1.41-4(c)(6).
The High-Threshold-of-Innovation Test
For software that is internal-use, the regulations may require a higher threshold of innovation. This test generally requires that the software involve significant economic risk or technological innovation. The specific requirements are set out in the regulations.
Hypothetical Example
Consider a company that develops software for its own internal payroll processing. This is generally internal-use software and may be excluded.
By contrast, if the company develops software to sell to other companies for their payroll processing, the software may not be internal-use and may warrant review. Similarly, 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.
These examples are illustrative only and do not state whether any particular activity qualifies.
Documentation That May Help
Records that can help support the IUS analysis include records showing whether the software is internal-use, whether an exception applies, and records of the technical uncertainty and process of experimentation. For more, see our page on R&D tax credit documentation.
Key Takeaway
Internal-use software is generally excluded from qualified research, but exceptions may apply for software developed for sale, lease, or licensing, or software that enables a non-software business component. The analysis involves detailed regulatory tests under Treas. Reg. §1.41-4(c)(6). Because the IUS rules are complex and fact-specific, professional review is appropriate before claiming the credit.