Internal use software (IUS) has always been held to a higher standard than other types of research when it comes to qualifying for the R&D credit. But the new IRS guidance clearly suggests some software development costs that were previously thought to be IUS were in fact likely to be exempt, and the new guidance also eases some requirements on IUS software when it comes to qualifying for the credit.
The new rules don’t change the four criteria that qualify an activity for the R&D Credit:
Once an activity meets these criteria, IUS must meet three additional criteria—referred to as the high threshold of innovation test—to qualify for the credit:
The concept of IUS, because of the final regulations, is going to largely be restricted to general administrative functions, such as:
The IRS has made it easier and less controversial to comply with the three additional criteria above that IUS must meet to qualify for the credit. For instance, the IRS concluded that the high threshold of innovation doesn’t require that you make a revolutionary discovery or that the software development be successful.
The IUS development involves “significant economic risk” if you commit substantial resources and there is substantial uncertainty, because of technical risks, that you might recover those resources within a reasonable period. “High threshold of innovation” is defined as resulting in a reduction of costs or an increase in speed, either of which are substantial or economically significant.
The new rules, which are largely consistent with the proposed regulations, clarify that some types of internally developed software are not IUS. For example, software you might have developed to interact with third parties or to enable third parties to initiate functions or review data on your business’ systems do not need to meet the additional IUS criteria to qualify for the R&D credit. The determination of whether the software was developed for third party use is based in large part on the intention of the company at the start of the software development effort.
Examples of software that may not qualify as IUS include:
Furthermore, software developed to be sold, leased, or licensed is generally not treated as software developed primarily for internal use.