Internal Use Software ("IUS") and the R&D Credit
How we typically address IUS
To be considered a qualified research activity eligible for the research credit, the development of software created by (or for the benefit of) the taxpayer primarily for the taxpayer's internal use must satisfy the three-prong, high-threshold-of-innovation test in addition to the standard four-part test. Whether software will be considered to be developed primarily for internal use depends on the intent of the taxpayer and the facts and circumstances at the beginning of software development.
Given the high bar for any IUS project to qualify, we are generally avoiding qualifying any IUS projects unless the taxpayer is highly confident the project would meet the much more stringent qualification requirements. As such, when we are helping the taxpayer to identify potentially qualifying business components, we have the taxpayer categorize all projects as either IUS, non-IUS, or dual-function. To the extent any project is included and labeled as IUS or dual-function, we then work with the taxpayer to also apply three additional tests (collectively referred to as the "High-threshold-of-innovation test") to ensure the taxpayer is confident they will be able to demonstrate this much higher threshold of innovation.
It is also important to note what is Not IUS
The following types of internal-use software are not required to satisfy the high-threshold-of-innovation test:
Software for use in an activity that constitutes qualified research;
Software for use in a production process; or
Software that is an integral part of a new or improved hardware and software package developed together by the taxpayer as a single product (or the costs to modify an acquired software and hardware package), of which the software is an integral part, used by the taxpayer in providing services in its trade or business (Regs. Sec. 1.41-4(c)(6)(ii)).
Software is developed by (or for the benefit of) the taxpayer primarily for internal use if the taxpayer develops the software for use in general and administrative functions that facilitate or support the conduct of the taxpayer's trade or business. The final regulations limit general and administrative functions to:
Financial management functions,
Human resource management functions, and
Support service functions that support day-to-day operations such as data processing or facilities services (Regs. Sec. 1.41-4(c)(6)(iii)).
Non-internal-use software for purposes of Sec. 41
Regs. Sec. 1.41-4(c)(6)(iv) clarifies and expands the exceptions to the definition of internal-use software by providing that software is not developed primarily for internal use by the taxpayer if it is not developed for use in general and administrative functions that facilitate or support the conduct of a taxpayer's trade or business. The final regulations provide two specific examples of software that is not internal-use software under this rule:
Software developed to be sold, leased, licensed, or otherwise marketed to third parties; and
Software developed to enable a taxpayer to interact with third parties or to allow third parties to initiate functions or review data on the taxpayer's system.
The development of such software may be eligible for the Sec. 41 research credit if the development activities satisfy the four-part test under Sec. 41(d).
