FOR RESEARCH CREDIT, COMPUTER SOFTWARE MUST EXPAND PUBLIC KNOWLEDGE, INVOLVE UNCERTAINTY.

                               IN THE

I. BACKGROUND

[2] The facts of this case are not disputed. The parties submitted detailed stipulations with attached exhibits, including summaries of the software development projects at issue. These stipulations and summaries form the basis of the recitation that follows.

[3] USI is the nation's largest wholesaler of office supplies. In response to both rapid corporate growth and industry changes in the 1980s, it attempted to correct operational inefficiencies by automating and computerizing its business. To this end, it purchased a software package, DCS, from a consulting firm for use in developing eight separate, but related, software programs. USI chose DCS for some of its file structure and data access segments; it could not have used DCS as purchased, nor could it have purchased any other software to meet its needs without modification. Instead, USI used parts of DCS as building blocks for designing application codes specific to its needs.

[4] USI developed all eight of the software projects at issue during the fiscal year 1988. Each performs a different operational function although several work together to correct a particular inefficiency. The first program, for example, the Document Retention and Retrieval System (DRRS), maintains files, customer histories and purchase records; it is, in short, a centralized invoice data base. Customers can access certain information in DRRS and request reprints of invoices or sales histories. DRRS is integrated with the second program, the Central Invoice Project (CIP), which furnishes a paperless invoicing and record-keeping system. The goal of CIP is to print, distribute and retain all invoices at USI's corporate headquarters in order to correct inefficiencies associated with USI's far-flung warehousing and distribution network. The third project is Concept 90, a computerized marketing program developed to address increased competition from volume discounters. USI hoped that by quickly responding to competitor pricing but carefully controlling its own price concessions it could increase sales volume on certain items. Unilink, the fourth project, is a computer-to-computer order entry system through which customers can enter orders on their own computers and transmit the orders directly to USI. On Unilink, customers can review previous orders and are immediately notified if an item is out of stock. USI developed a related project, called Distributed Order Entry, to allow inter-divisional billing in the event that the division receiving the order was out of stock. USI also developed the Facility Database Project, FDP, the fifth program, to replace its outdated inventory program and as an aid in forecasting and replenishing inventories. FDP creates a hierarchy of inventory data, with information about each region's inventory first, specifics on each item in that inventory second and pricing possibilities for each item last. The sixth project was the Automated Inbound Shipment Processing Program. As its name implies, USI developed this program to replace its manual warehousing procedures with automated incoming and outgoing shipping procedures. The seventh project, the Receiving System, is integrated with this Automated Inbound Shipment Processing Program. The eighth project is called the Forecasting/Replenishment Application Project. It creates a more timely and accurate method of inventory control. This project replaced a system based largely on an individual buyer's experience in anticipating product demand.

[5] The project summaries also describe the risks and benefits of each program. Most of the summaries include a general statement about the uncertainty at the outset of achieving the projects' anticipated operational efficiencies or economic benefits. For example, the CIP summary states that "there was no guarantee at the outset of [CIP] that [USI], in centralizing the invoicing functions . . . would be able to both provide customers with accurate invoices on a timely basis and have easy access to that invoice data after they had been sent to customers." Similarly, Concept 90, the marketing program, involved "operational risk." And another project summary states that

     "[t]here was no guarantee that the FDP approach would either

[7] The district court referred the case to a magistrate judge, who issued a report determining that USI's development of the programs did not constitute qualified research and that USI was therefore not entitled to the claimed refund. See United Stationers, Inc. v. United States, No. 92 C 6065, 1997 WL 159526 (N.D. Ill. March 28, 1997) (United Stationers I). USI filed objections to this report. The district court agreed (with a minor deviation) with the magistrate judge's report. See United Stationers, Inc. v. United States, 982 F. Supp. 1279 (N.D. Ill. 1997) (United Stationers II). The district court ruled that the programs did not qualify for section 41's qualified research credit because USI neither "discover[ed] information which is technological in nature," id. at 1284, nor did so through a "process of experimentation." Id. at 1286. The district court further held that, even if the programs could meet the section 41 general requirements, they fitted within an enumerated exclusion from the allowable credit because they were for "internal use." Id. at 1287. Finally, the district court found that the programs did not qualify under an exception to this internal use exclusion. Id. at 1287-88. USI appeals these holdings.

II. DISCUSSION

[8] In this case, as with all claimed tax credits, the taxpayer bears the burden of showing entitlement to the credit. See, e.g., Interstate Transit Lines v. Commissioner of Internal Revenue, 319 U.S. 590, 593 (1943); United States v. Wisconsin Power & Light Co., 38 F.3d 329, 337 (7th Cir. 1994). To the extent entitlement turns on the legal question of interpretation of section 41, we review the district court's legal conclusions de novo. See, e.g, Resolution Trust Corp. v. Gallagher, 10 F.3d 416, 418 (7th Cir. 1993). As to questions of fact, including issues of evidentiary sufficiency, we review for clear error. See, e.g., Wisconsin Power & Light, 38 F.3d at 337.

A. THE QUALIFIED RESEARCH TAX CREDIT

[9] Section 41, the Credit for Increasing Research Activities, allows taxpayers a credit for certain expenses incurred conducting qualified research. Subsection 41(d) defines qualified research in pertinent part as follows:

     (d) Qualified research defined. -- For purposes of this

[10] Only two of these requirements are at issue here. A section 174 deduction has been allowed, satisfying the first requirement, and the government concedes the third requirement, involving usefulness for a new or improved business component. We will address the two other requirements in turn.

1. DISCOVER INFORMATION WHICH IS TECHNOLOGICAL IN NATURE

[11] Section 41(d)(1)(B)(i) requires research to be undertaken "for the purpose of discovering information which is technological in nature." The district court held that, although the programs were "technological in nature," USI did not develop the programs to discover information. United Stationers II, 982 F. Supp. at 1284. Citing dictionary definitions and the legislative history of section 41, the district court instead found that "Stationers [had] merely applied, modified, and at most, built upon, pre-existing, technological information already supplied to it." Id. USI now claims that the district court's interpretation of this prong comports with neither the Code's plain language nor its legislative history. While we do not necessarily adopt the district court's view that the issue turns on the breadth of the definition of the word "discover," we believe that the terms of the requirement in question have not been met.

[12] USI cites a dictionary which defines "discover" as "to make known (something secret, hidden, unknown, or previously unnoticed)" or "to obtain for the first time sight or knowledge of." Appellant's Br. at 15 (citing Webster's Third New International Dictionary, Unabridged 647 (1993)). USI invites us to end our definitional inquiry here, content with an interpretation which equates discovery with mere newness. We decline this invitation. Congress attempted to give further meaning to section 41(d)(1)(B)(i) and we can look to legislative history for guidance. See, e.g., Sundstrand Corp. v. Commissioner of Internal Revenue, 17 F.3d 965, 967-68 (7th Cir. 1994).

[13] The Conference Report accompanying the 1986 amendments states that research that discovers information which is technological in nature must rely on "principles of the physical or biological sciences, engineering, or computer science." H.R. Conf. Rep. No. 99-841, at II-71 (1986). Specifically, "[r]esearch does not rely on the principles of computer science merely because a computer is employed. Research may be treated as undertaken to discover information that is technological in nature, however, if the research is intended to expand or refine existing principles of computer science." Id. n.3. Thus Congress set a demanding standard. Not just any computer programming would qualify for a section 41 credit; qualifying research must go beyond the current state of knowledge in that field -- expand or refine its principles. See Norwest Corp. v. Commissioner, Tax Ct. Rep. (CCH), paragraph 52,758, at 4653-54 (U.S. Tax Ct. June 29, 1998). Therefore, in the context of section 41(d)(1)(B)(i) discovery demands something more than mere superficial newness; it connotes innovation in underlying principle. See id.

[14] This understanding of "discovery" also brings the requirements for the credit in line with the purposes of both the original statute in 1981 and the amendments in 1986. Congress first created a research and experimentation tax credit in 1981 as part of the Economic Recovery Tax Act of 1981 (ERTA). ERTA adopted section 174's definitions of "research" and "experimentation" but failed to specifically indicate how the credit applied to computer software development. Congress hoped that ERTA would energize the overall economy and specifically would stimulate business investment in technological research. See S. Rep. No. 97-144, at 76-77 (1981); H. Rep. No. 97-201, at 111 (1981). In 1986, in response to taxpayer abuse, Congress amended the research tax credit provision to include an express statutory definition of qualified research. The 1986 amendments restricted the definition of qualified research to that which "discover[s] information which is technological in nature" in an attempt to limit the deduction to only high technology research. ² Congress clearly intended, then, that qualifying research pass a high threshold of innovation and be of broad effect. See Norwest, paragraph 52,758, at 4653-54; see also TSR, Inc. v. Commissioner, 96 T.C. 903, 916-20 (1991). ³

[15] We believe that our interpretation -- as well as that of the district court -- comfortably fits the Code's language and its legislative history and compels the conclusion that USI's programs did not discover information which is technological in nature. USI's projects did not refine or expand the principles of computer science. Instead, they modified an existing software program in an attempt specifically to improve USI's inventory control system. Further, although these applications were new to USI and helped it eliminate various operational inefficiencies, they were not of broad economic effect. USI accuses the district court of imposing a "revolutionary" standard where Congress intended no more than "evolutionary" research to qualify. USI's amicus similarly cautions against raising the bar of the research tax credit too high. We are respectful of these warnings but are no less convinced of our conclusion. Wherever the line is drawn, these projects fall short. The more or less routine modification of a commercially-available software package to apply to USI's inventory control computers simply does not measure up to the demanding requirements of section 41(d)(1)(B)(i). See H. REP. No. 99- 426, at 180 (1985); compare Norwest, paragraph 52,758, at 4663-65 (examples of computer programs that meet the high standard) with id. at 4667, 4668 (examples of computer programs that do not meet the high standard).

2. PROCESS OF EXPERIMENTATION

[16] Section 41(d)(1)(C) provides that qualified research involve "substantially all of the activities which constitute elements of a process of experimentation." 26 U.S.C. section 41(d)(1)(C). The district court, again looking to dictionary definitions and legislative history for guidance, held that this test requires qualifying research to have significant design uncertainty from its outset. See United Stationers II, 982 F. Supp. at 1285. The court then found USI's claim of uncertainty "not persuasive:" "while the aspired benefits of the projects were in doubt, the development of the means that would allow [USI] to potentially achieve those benefits was not." Id. (citation omitted). USI now challenges both the district court's legal interpretation of this process of experimentation test and its factual findings regarding design uncertainty in the eight projects. We reject both challenges.

[17] USI again begins with its plain reading of the subsection. According to USI's dictionary, an experiment is ". . . a test, trial, or tentative procedure, an act or operation for the purpose of discovering something unknown or of testing a principle, supposition, etc." Appellant's Br. at 23 (citing RANDOM HOUSE COLLEGE DICTIONARY 465 (rev. ed. 1984)). The projects fit squarely within this definition, USI claims, because software development involves debugging, a process of testing and correcting computer programs. We find this argument unpersuasive. Debugging programs amounts simply to fine-tuning computer operating instructions. Although we are reluctant to establish bright-line rules -- section 41 cases will always be highly fact-intensive -- we think that a process of experimentation involves something more than simply debugging a computer program. See Norwest paragraph 52,758, at 4669 (computer programming project did not qualify because it "merely required conducting good coding and eliminating bugs through testing").

[18] The legislative history of section 41(d)(1)(C) bolsters this conclusion. The Conference Report explains the meaning of the process of experimentation test:

          The term process of experimentation means a process

[19] USI and amicus again caution that this articulation of the relevant standard is too narrow. We are not persuaded, however, and conclude that USI's projects did not involve a process of experimentation as envisaged by Congress. The eight projects involved the modification of a commercially-available software package to fit USI's particular operational needs. Most of the project summaries include general statements about the uncertainty of actually realizing the anticipated operational efficiencies and resultant economic benefits. None of the summaries, however, describes any technical uncertainty about actually developing the programs. Compare Norwest, paragraph 52,758, at 4670 (programming project did not constitute qualified research because, in part, it did not involve technical risk). Nor were there any doubts about the ability of computers to perform the invoicing, billing and marketing tasks. That is, there was simply no technical uncertainty from the outset. We therefore conclude that USI's development of the eight programs did not involve a process of experimentation and that the district court did not clearly err in concluding that the projects did not involve the level of uncertainty necessary to clear this hurdle.

B. THE INTERNAL USE EXCLUSION

[20] Section 41(d)(1) excludes from the qualified research credit any computer software developed "primarily for internal use by the taxpayer." 26 U.S.C. section 41(d)(4)(E). For lack of other authority, the district court consulted the legislative history and proposed Treasury regulations to determine what "internal use" means. See United Stationers II, 982 F. Supp. at 1286. The district judge employed a "totality of the circumstances" test and concluded that USI's programs "were the type of internal use software that Congress specifically sought to exclude from the section 41 research credit." Id. at 1287. USI, of course, contests this conclusion and constructs two elaborate arguments in an attempt to rescue the projects from this internal use exclusion. Neither argument, despite its admirable ingenuity, is particularly compelling.

[21] Again, nothing in the Code or in case law ⁴ explicitly defines internal use. We therefore plunge again into the muddy waters of legislative history. USI points us to 1981 Congressional records to support its reading of the exclusion. Only software intended exclusively for internal use, USI argues, should be excluded because the original intent of the research credit was to stimulate the economy; therefore, any program that provides a stimulus to or has an impact on the economy, however indirect or insubstantial, should escape the internal use exclusion. This proposed analysis sweeps too broadly. Congress intended the original credit to reward taxpayers for a significant contribution to the store of public technological knowledge. See S. REP. No. 97-144 (1981); H. REP. No. 97-201 (1981). To avoid this exclusion, then, a taxpayer claiming a credit for developing software must to an appropriate extent make the program available to the public. Something more than a speculative or attenuated impact on the economy is required.

[22] USI also pins its hope on the 1986 Conference Report which explicitly states that software development projects would constitute internal use software where they are "used internally, for example, in general and administrative functions (such as payroll, bookkeeping, or personnel management) or in providing noncomputer services (such as accounting, consulting, or banking services)." H.R. CONF. REP. No. 99-841, at II-73 (1986). USI relies on this language to urge us to draw elusive distinctions between the provision of general and administrative services and a taxpayer's core revenue- generating activities. Core business activities have an external impact and should not be subject to the internal use exclusion, USI asserts. It maintains that the projects at issue here -- inventory controls and the like -- are integral to its core revenue activities as a wholesale distributor. USI therefore concludes that its eight projects cannot be internal use software.

[23] We cannot accept this analysis. USI seems to be asking us to view cost accounting methodology (specifically, the difference between general overheads and directly assigned costs) as a determinative principle in identifying internal use. In effect, USI appears to be arguing that, if the programs involve activities that directly impact parties outside the taxpayer, they are not for internal use. As we stated before, however, this formulation does not fully capture the idea of contributing to the store of public technological knowledge. In any event, we agree with the district court that all the relevant facts -- the totality of the circumstances -- must be taken into account. See United Stationers II, 982 F. Supp. at 1286-87; see also Prop. Treas. Reg. section 1.41- 4(e)(4), 62 Fed. Reg. 81, 83 (Jan. 2, 1997) (Credit for Increasing Research Activities). And, on the record before us, the district court's conclusion that the software development projects were for internal use is not clearly erroneous. USI developed all of the software to help it track its huge inventory. Even the two programs to which customers have limited access, DRRS and Unilink, were developed primarily for use by USI in streamlining its operations. The services these software programs expedite -- marketing, ordering, invoicing, shipping, receiving, pricing, etc. -- even though they may have a direct impact on customers, suppliers and other third parties do not rescue the programs from the internal use exclusion.

C. INNOVATIVE AND RISKY EXCEPTION TO THE EXCLUSION

[24] The legislative history of section 41 introduces an exception to the internal use exclusion which would permit a qualified research credit for the development of internal use computer software that meets the general requirements for the credit that we have already discussed, is innovative, involves risk and results in software that is not commercially available. See H.R. CONF. REP. No. 99-841, at II-73 (1986); see also Prop. Treas. Reg. section 1.41-4(e)(5)(i)-(iii), 62 Fed. Reg. 81, 83 (Jan. 2, 1997) (Credit for Increasing Research Activities) (adopting this same standard). ⁵ The parties stipulated that all eight of the programs were not commercially available. The district court held that the programs "all fall under the plain meaning of the definition [of innovative] included in the legislative history" and therefore meet the requirements of the first prong of the special exception. United Stationers II, 982 F. Supp. at 1287-88. ⁶ However, the district judge found against USI on the second prong, concluding that the projects did not involve substantial uncertainty because of technical risk. See id. at 1288. USI now challenges the court's legal and factual disposition of the risk prong, while the government challenges the district court's factual findings as to innovativeness. We consider each of these contentions, taking the government's argument first.

[25] According to the Conference Report, computer software is innovative if it "results in a reduction in cost, or improvement in speed, that is substantial and economically significant." H.R. CONF. REP. No. 99-841, at II-73 (1986). Applying this principle, the government argues that the district court did not properly focus on the economic significance of the efficiencies generated by USI's programs. It points out that some 65% of the original investment in the projects did not produce the anticipated economic returns. But we do not think that this quantitative approach is necessarily dispositive; the facts of every case will be different. Cf. Norwest, paragraph 52,758, at 4656 (rejecting an attempt to quantify the required improvement). Instead, we believe that Congress's use of the adjectives "substantial" and "significant" indicates that internal use software to escape the exclusion must be more clearly innovative than software merely meeting the section 41 requirements in general. See id.; see also S. REP. No. 99-313, at 695 (1986) (internal use software must meet a "high threshold of innovation"); H. REP. No. 99- 426, at 178 (1986) (same). After a thorough review of the project summaries, we believe that all of the programs resulted in improvements in speed or reductions in cost. The district court concluded that these efficiencies met the more onerous requirements of the relevant test. We cannot say on this record that the district court clearly erred in finding that the programs were innovative.

[26] But the Conference Report also defines the risk necessary to meet the requirements of this exception to the internal use exclusion. The Report states that a computer software research project must involve "significant economic risk (as where the taxpayer commits substantial resources to the development and also there is substantial uncertainty, because of technical risk, that such resources would be recovered within a reasonable period)." H.R. CONF. REP. No. 99-841, at II-73 (1986). USI argues that the district court improperly focused on the uncertainty of developing the programs rather than the uncertainty that the programs would recover their costs. Whatever the focus, however, USI's projects do not meet the exception's definition because they did not involve the requisite technical risk. In the context of the general requirements for section 41, we have already found that there was little if any technical risk that USI would not succeed in developing the programs. Here, in the context of an exception to an express exclusion, Congress again employed the weighty adjective "substantial" to indicate a higher threshold of risk than for software merely meeting the section 41 requirements in general. We do not purport to define the exact contours of this test -- again, the inquiry will be fact- driven, and proposed regulations might further guide this determination -- but we can be confident that because USI's projects did not meet the less demanding general requirements of section 41's qualified research definition, they necessarily do not pass the higher threshold of risk required by the exception to the internal use exclusion. We therefore also agree with the district court on this requirement.

[27] The judgment therefore is AFFIRMED.

[28] MANION, Circuit Judge, concurring in part and concurring in result. Although I concur with the court's opinion and holding, I take issue with the analysis in part IIC which addresses the proposed exception to the statutory exclusion. Section 41(d)(4)(E) disallows the qualified research credit for computer software that is developed by or for the taxpayer "primarily for internal use by the taxpayer." 26 U.S.C. section 41(d)(4)(E). The plain meaning of the statute eliminates the eight projects for which United Stationers seeks the credit because the projects were clearly for internal use. The court expands on this exception by applying a regulation found only in the legislative history to 26 U.S.C. section 41 and proposed regulations; it is not in the statute and it has not been formally adopted by the Treasury Department. In the absence of a law passed by both houses of Congress and signed by the President, or a regulation adopted pursuant thereto, we have no basis on which to conclude that a taxpayer meeting this exception is entitled to a tax credit. While the court's analysis of this exception correctly concludes that the credit does not apply, it could send the wrong signal both to taxpayers and to the Treasury Department to invoke a regulation not legally in place. Until the regulation is made law, this court's analysis should be confined to the statute.

[29] A true Copy:

      Teste:

² The Senate Finance Committee report on these amendments well illustrates Congress's concerns:

     After reviewing available information and testimony on the

³ USI also asserts that the term "discovery" in section 41(d)(1)(B)(i) must have the same meaning as in section 174 and section 41(d)(1)(B)(ii). Legislative history suggests, however, that "Congress intended to treat the discovery test under section 41 more narrowly than the discovery test created under section 174." Norwest, paragraph 52,758, at 4653; see also id. (arguing that the timing of the enactment of the sections as well as their express language are reliable indicia that discovery means different things in sections 41 and 174).

⁴ In Norwest the parties agreed that all the programs constituted internal use software. See Norwest, paragraph 52,758, at 4650.

⁵ The concurrence correctly points out that this proposed regulation has not been formally adopted. However, the government's position on this point is as follows:

     Final regulations have not yet been issued under Section

⁶ This is the one point on which the district judge disagreed with the magistrate. Compare United Stationers I, 1997 WL 159526, at *5.