Norwest Corp. v. Comm’r, 110 T. C. 454 (1998)
Internal use software development can qualify for research and experimentation tax credits if it meets stringent criteria involving technological innovation and significant economic risk.
Summary
Norwest Corporation sought tax credits for its internal software development activities from 1986 to 1991, claiming they constituted qualified research under Section 41 of the Internal Revenue Code. The court identified seven tests that must be satisfied for such activities to qualify, emphasizing a higher threshold for internal use software. Only the Strategic Banking System (SBS) customer module was found to meet all criteria, showcasing significant innovation and technical risk. The court rejected the other seven projects, classifying their efforts as routine software development lacking the necessary technological advancement.
Facts
Between 1986 and 1991, Norwest Corporation engaged in numerous software projects for its banking and financial services. These included the development of the Strategic Banking System (SBS), Trust TU, Success, General Ledger, Money Transfer, Cyborg Payroll, Trust Payment, and Debit Card systems. Norwest claimed these efforts qualified for research and experimentation tax credits under Section 41 of the IRC. The IRS challenged these claims, leading to a court examination of whether these projects met the statutory definition of qualified research, particularly focusing on the development of internal use software.
Procedural History
Norwest filed petitions contesting IRS notices of deficiency for the years 1983 through 1989, later amending these to claim R&E credits for 1986 through 1991. The court consolidated the cases for trial, briefing, and opinion solely on the issue of whether Norwest’s activities constituted qualified research. The parties agreed to use eight of Norwest’s 67 internal use software projects as representative samples to determine the outcome for all projects.
Issue(s)
1. Whether Norwest Corporation’s development of the Strategic Banking System (SBS) customer module constituted qualified research under Section 41 of the IRC?
2. Whether Norwest Corporation’s development of the Trust TU, Success, General Ledger, Money Transfer, Cyborg Payroll, Trust Payment, and Debit Card systems constituted qualified research under Section 41 of the IRC?
Holding
1. Yes, because the SBS customer module satisfied all seven tests for qualified research, demonstrating technological innovation and significant economic risk.
2. No, because the other seven systems did not meet the required tests, lacking sufficient technological advancement and primarily involving routine software development.
Court’s Reasoning
The court applied seven tests from Section 41 and its legislative history to determine if Norwest’s activities qualified for R&E credits. These tests included the Section 174 test, the discovery test, the business component test, the process of experimentation test, the innovativeness test, the significant economic risk test, and the commercial availability test. The SBS customer module was found to meet these criteria due to its innovative approach to integrating banking systems around a customer-centric model, the significant economic investment and risk involved, and its lack of commercially available alternatives at the time. The other projects were deemed routine, lacking the necessary technical risk and innovation. The court also clarified that the development of internal use software required a higher threshold of technological advancement, reflecting Congress’s intent to limit such credits to ventures into uncharted technological territory.
Practical Implications
This decision establishes a stringent standard for claiming R&E credits for internal use software, requiring a high degree of technological innovation and significant economic risk. For similar cases, practitioners must demonstrate that software development projects push the boundaries of existing technology, rather than merely applying known methodologies. The ruling may encourage businesses to document their software development processes more thoroughly to prove technological advancement and risk. Subsequent cases citing Norwest Corp. v. Comm’r have further refined these standards, emphasizing the need for a clear distinction between routine software development and true research activities.