Proposed rules would govern Sec. 41 credit for software

By Sally P. Schreiber, J.D.

The IRS offers a test and safe harbor for qualifying dual-function internal-use software.

The IRS issued long-awaited proposed rules on what type of internal-use software qualifies for the Sec. 41 research credit (REG-153656-03). Although the new rules are proposed, not final, the IRS says it will not challenge taxpayers’ return positions that apply these rules currently.

Final regulations (T.D. 8930) on internal-use software and the research credit were released in 2001 but caused considerable controversy among practitioners. In response, in 2004, the IRS issued an advance notice of proposed rulemaking (2004 ANPRM), announcing that it would consider the comments it had received and promulgate new proposed regulations.

Internal-use software is software developed by (or for the benefit of) the taxpayer primarily for use in general and administrative functions that facilitate or support the conduct of the taxpayer’s trade or business. General and administrative functions are limited to financial management, human resources management, and support services functions. Internal-use software generally does not qualify for the credit but can if it meets a high-threshold-of-innovation test with three requirements:

  1. The software is innovative (defined as resulting in a reduction in cost or improvement in speed or other measurable improvement that is substantial and economically significant, if the development is or would have been successful);
  2. The taxpayer incurs significant economic risk in developing the software (has committed substantial resources to develop it and, due to technical risk, there is substantial uncertainty that the costs of development will be recovered in a reasonable time); and
  3. The software is not commercially available without considerable modification (i.e., the software cannot be purchased, leased, or licensed and used for the intended purpose without modifications that would satisfy the first two requirements).

Dual-function internal-use software, which serves functions that are general and administrative and those that are not, must overcome a presumption in the proposed rules that it is developed for nonqualifying internal use. The presumption will not apply if the taxpayer “can identify a subset of elements of dual function computer software that only enables a taxpayer to interact with third parties or to allow third parties to initiate functions or review data (third party subset)” (REG-153656-03, preamble). However, if the taxpayer can identify a third-party subset of the dual-function computer software, the portion of research expenditures allocable to the third-party subset may be eligible for the research credit, provided all the other applicable requirements are met.

In addition, the rules will provide a safe harbor that applies to dual-function software if a third-party subset cannot be identified, or to the remaining subset of dual-function computer software after the third-party subset has been identified (dual-function subset). Under the safe harbor, 25% of the taxpayer’s qualified research expenditures of the dual-function subset is included in computing the amount of the credit if the taxpayer’s research activities for the dual-function subset are qualified research and the use of the dual-function subset by third parties or by the taxpayer to interact with third parties is reasonably anticipated to constitute at least 10% of the dual-function subset’s use.

Requests for comments. The IRS requested comments on all aspects of these proposed rules but is especially interested in (1) comments on the appropriate definition and treatment of connectivity software that allows multiple processes running on one or more machines to interact across a network, sometimes referred to as bridging software, integration software, or middleware; (2) for the dual-function safe harbor, comments on the ease of measuring the reasonably anticipated use of software to interact with third parties and by third parties to initiate functions or review data based on reasonable methods, such as processing time, amount of data transfer, etc.; and (3) which facts and circumstances, other than those set out in the legislative history, should be considered in determining whether internal-use software satisfies the three prongs of the high-threshold-of-innovation test.

Effective date. Although many commenters had requested that these regulations apply retroactively, the IRS decided to apply them prospectively. Therefore, they will apply to tax years ending on or after the date they are published as final in the Federal Register. However, the IRS will not challenge return positions applying these rules for tax years ending on or after Jan. 1, 2015. For tax years ending before that date, taxpayers may choose to follow either all of the internal-use software provisions of Regs. Sec. 1.41-4(c)(6) in the 2001 final regulations or all of the internal-use software provisions of Regs. Sec. 1.41-4(c)(6) in the 2001 proposed regulations.

By Sally P. Schreiber, J.D., a JofA senior editor.


Get your clients ready for tax season

These year-end tax planning strategies address recent tax law changes enacted to help taxpayers deal with the pandemic, such as tax credits for sick leave and family leave and new rules for retirement plan distributions, as well as techniques for putting your clients in the best possible tax position.


Keeping you informed and prepared amid the coronavirus crisis

We’re gathering the latest news stories along with relevant columns, tips, podcasts, and videos on this page, along with curated items from our archives to help with uncertainty and disruption.