FedEx Corp. v. United States

The legal landscape governing the Research and Development tax credit, codified under Section 41 of the Internal Revenue Code, has undergone a fundamental transformation over the last two decades. Central to this evolution is the litigation history of FedEx Corporation, a multi-decade saga that encompasses both direct challenges to research credit standards and broader challenges to the administrative authority of the Internal Revenue Service and the Department of the Treasury. The 2009 decision in FedEx Corp. v. United States remains the seminal benchmark for internal-use software and the rejection of the "Discovery Test," while the 2023 and 2025 rulings involving the same parties have fundamentally altered the framework through which all tax regulations are interpreted in the post-Loper Bright era. To understand the implications for future R&D tax credit applications, one must analyze the intersection of technical software development requirements, the evidentiary standards for experimentation, and the shifting paradigms of administrative law that now empower taxpayers to challenge restrictive agency interpretations.

The Statutory Architecture of the Research Credit and the IUS Exemption

The Research and Development tax credit was introduced in 1981 to combat a perceived decline in American industrial innovation. However, the initial broadness of the credit led to significant controversy regarding what activities truly constituted "qualified research". By 1986, Congress introduced the "Four-Part Test" to ensure that the credit was applied only to activities that were technological in nature and involved a structured process of experimentation intended to eliminate technical uncertainty.

The Emergence of the Internal-Use Software Conflict

While Congress intended to reward software development, it remained skeptical of "routine" software created for internal back-office functions. This skepticism gave rise to the "Internal-Use Software" (IUS) exclusion under Section 41(d)(4)(E), which states that research on computer software developed primarily for the taxpayer's internal use is generally ineligible for the credit unless it meets a "High Threshold of Innovation" (HTI) test.

The definition of what constitutes IUS has shifted significantly across different regulatory regimes. The primary friction point between the IRS and taxpayers has been the boundary between software used for "General and Administrative" (G&A) functions and software that enables interaction with third parties.

FedEx Corp. v. United States (2009): The Rejection of the Discovery Test

The 2009 case of FedEx Corp. v. United States, No. 08-2423 (W.D. Tenn.), serves as the foundational precedent for contemporary IUS claims. The litigation arose from a massive software project initiated by FedEx in 1996 to develop a sophisticated computer-based system for tracking global billing records. The project continued until 2001, when it was ultimately abandoned after substantial expenditures had been incurred. FedEx filed for research credits for tax years 1997 through 2000, which the IRS denied on the grounds that the software failed to meet the Discovery Test and the HTI test as then interpreted by the agency.

The Discovery Test Controversy

The primary legal question was whether the IRS could require FedEx to meet the "Discovery Test," which mandated that research must be undertaken to obtain knowledge that "exceeds, expands, or refines the common knowledge of skilled professionals in a particular field of science or engineering". The IRS argued that because FedEx sought to rely on the 2001 Final Regulations (T.D. 8930), it must accept the Discovery Test contained therein. FedEx countered that the Treasury Department had elsewhere admitted the Discovery Test was inconsistent with congressional intent and that the IRS could not use an informal "Announcement" (2004-9) to force taxpayers to comply with an invalid standard.

The court ruled in favor of FedEx, granting partial summary judgment. This decision was monumental because it invalidated the Discovery Test, affirming that "discovery" under Section 41 simply means the elimination of technical uncertainty from the perspective of the taxpayer, not the global scientific community. The court found that the IRS lacked the authority to create enforceable law through an announcement that circumvented the formal rulemaking process.

The Rebirth of the High Threshold of Innovation Test

While the court discarded the Discovery Test, it clarified the High Threshold of Innovation (HTI) test that still applies to IUS today. The FedEx court approved a three-pronged HTI test:

• Innovation: The software must be intended to result in a reduction in cost, improvement in speed, or other improvement that is substantial and economically significant.
• Significant Economic Risk: The taxpayer must commit substantial resources to the development, and there must be substantial uncertainty, because of technical risk, that such resources would be recovered within a reasonable period.
• Commercial Availability: The software cannot be purchased, leased, or licensed and used for the intended purpose without modifications that would satisfy the first two requirements.

This ruling provided a massive boon to large enterprises, particularly financial institutions and logistics firms, by making it possible to qualify major software infrastructure projects that had previously been barred by the Discovery Test's "new to the world" standard.

Technical and Evidentiary Requirements for Qualified Research

The FedEx precedent did not remove the necessity of the "Four-Part Test" found in Section 41(d). For a project to qualify, it must meet all four criteria, even if it passes the HTI test. The contemporary application of these tests, particularly in the wake of Phoenix Design Group v. Commissioner (2024), reveals a critical need for granular, activity-level documentation.

The Four-Part Test Under Modern Scrutiny

The interaction between statutory language and judicial interpretation has refined the requirements for each prong of the qualified research test:

• Permitted Purpose: The research must be related to developing a new or improved business component, such as a product, process, or software.
• Technological in Nature: The process of experimentation must fundamentally rely on principles of physical or biological sciences, engineering, or computer science.
• Elimination of Uncertainty: The research must seek to resolve uncertainty about the capability, method, or appropriate design of the component.
• Process of Experimentation: This is the most frequently litigated prong. It requires a systematic evaluation of alternatives, such as modeling, simulation, or iterative testing.

The Impact of Loper Bright on IRS Rulemaking and R&D Litigation

The most significant development for future R&D tax credit applications is not found in a research credit case, but in the 2025 decision in FedEx Corp. v. United States (concerning foreign tax credits) and the Supreme Court's 2024 ruling in Loper Bright Enterprises v. Raimondo.

The Death of Chevron Deference

For forty years, the Chevron doctrine required courts to defer to "reasonable" agency interpretations of ambiguous statutes. This gave the IRS immense power to define terms like "process of experimentation" and "internal use software" through regulations that often restricted the credit more than the statutory text suggested.

The 2024 Loper Bright decision overturned Chevron, ruling that courts must exercise independent judgment to say what the law is. In the 2025 FedEx case, the District Court applied Loper Bright to reject the government's reliance on the "Regulatory Haircut Rule," stating that an agency cannot use its delegated authority to promulgate regulations that contravene the "single best meaning" of a statute as determined by a court.

Implications for Section 41 Challenges

This shift in administrative law creates a new "offensive" tool for taxpayers. Many restrictive R&D tax credit regulations are now vulnerable to challenge if they add hurdles not found in the original legislation.

• Challenging the "Shrinking-Back" Rule: While often used by taxpayers to save portions of a project, the IRS uses the rule to narrow the scope of qualified research. A court could find that the regulatory complexity of the "substantially all" and "shrinking-back" tests exceeds the statutory intent of Section 41.
• Challenging the Definition of POE: The IRS's current definition of "process of experimentation" (evaluating alternatives through a systematic process) is far more specific than the statutory phrase. Post-Loper Bright, a taxpayer could argue for a broader interpretation that includes standard industrial testing protocols.
• Challenging IUS Definitions: The 2016 regulations' definition of "general and administrative" functions as the only basis for IUS could be challenged. If a taxpayer's software doesn't fit the statutory intent of "internal use," the regulatory categories may be deemed non-binding.

Funded Research and State Law: The System Technologies Precedent

Another critical area of future litigation involves the "Funded Research" exclusion under Section 41(d)(4)(H). The IRS frequently attempts to deny credits to contractors, arguing that their research is funded by their customers.

In the 2025 case of System Technologies, Inc. v. Commissioner, the Tax Court denied the IRS's motion for summary judgment, holding that the research was not funded. The court's reasoning relied heavily on state law (Indiana's version of the Uniform Commercial Code) to determine if the taxpayer bore the financial risk of failure. This case demonstrates that future R&D applications must be supported not just by technical data, but by a sophisticated analysis of the contractual rights and remedies under state law.

Quantitative Modeling of the R&D Tax Credit

The calculation of the research credit is inherently mathematical, involving the comparison of current-year expenditures against a historical base. The "Regular Research Credit" (RRC) and the "Alternative Simplified Credit" (ASC) are the two primary methodologies used by large corporations like FedEx.

The Credit Calculation Formula

The credit is typically calculated as:

$$\text{Credit} = \text{Rate} \times (\text{QRE}_{\text{current}} - \text{Base Amount})$$

Where the Base Amount for the RRC is:

$$\text{Base Amount} = \text{Fixed-Base Percentage} \times \text{Average Gross Receipts}_{\text{last 4 years}}$$

In the 2009 FedEx case, a specific technical ruling was issued regarding this calculation: the court ruled that intercompany transactions must be included in "gross receipts" when determining the base amount. This adjustment typically increases the base amount, thereby reducing the net credit, a significant win for the IRS that highlights the importance of precise revenue accounting in R&D applications.

Section 174 Amortization and Section 41 Interaction

Starting in 2022, Section 174 requires the amortization of research and experimentation (R&E) costs over five years (or fifteen for foreign research). While this is a separate provision from the Section 41 credit, the definitions of "uncertainty" in both sections are linked. The recent Phoenix Design and Meyer, Borgman & Johnson cases emphasize that failing the Section 174 uncertainty test automatically disqualifies the Section 41 credit.

The Future of Documentation and Audit Defense

The "FedEx legacy" in tax litigation is one of procedural rigor and statutory literalism. For future R&D tax credit applications, the primary lesson is that the IRS will no longer receive the "benefit of the doubt" in court, but taxpayers will be held to an exacting standard of proof.

Lessons from Phoenix Design Group (2024)

The Phoenix Design Group ruling serves as a vital counterpoint to the legal optimism of Loper Bright. Despite the broader legal ability to challenge the IRS, PDG lost its case because its documentation was "insufficiently contemporaneous" and "activity-level" support was missing.

The court rejected the taxpayer's claim for three main reasons:

• Linear Design vs. Iterative Experimentation: The firm followed a standard six-stage engineering process that the court deemed routine rather than experimental.
• Inconsistent Narratives: Hour sheets did not align with the technical challenges described in the R&D study.
• Professional Judgment vs. Science: The court held that using "professional expertise" to solve a problem is not a "process of experimentation" unless it involves testing and evaluating alternatives.

Strategic Recommendations for Future Claimants

Based on the combined impact of the FedEx, Loper Bright, and Phoenix Design decisions, future R&D tax credit applications should adhere to the following strategic pillars:

• Adopt a "Statute-First" Defense: Do not assume that IRS Audit Technique Guides or regulations are final. If a claim meets the statutory definition of Section 41 but fails a specific regulatory "hurdle," it may be worth litigating.
• Prioritize Contemporaneous Documentation: The Tax Court is increasingly skeptical of "look-back" studies created years after the research occurred. Capturing project data, failure logs, and testing results in real-time is now the only way to ensure credit sustainability.
• File Protective Claims: Given the Corner Post decision and the shifting administrative law landscape, taxpayers should file protective claims for credits that were previously withheld due to restrictive IRS interpretations.
• Rigorous Contract Analysis: For service-based firms, ensuring that contracts explicitly place the financial risk of research failure on the provider is essential for qualifying under the "funded research" rules.

Conclusion: The New Equilibrium in Research Incentives

The litigation of FedEx Corporation has come to define the modern boundaries of the research tax credit. From the 2009 victory that dismantled the Discovery Test for internal-use software to the 2025 triumph that empowered taxpayers to challenge the very validity of Treasury regulations under Loper Bright, FedEx has consistently pushed the judiciary to reclaim its role as the final arbiter of tax law.

For future R&D applications in the United States, the implications are dual-faceted. On one hand, the legal environment is more favorable than it has been in forty years, as the era of automatic deference to the IRS has ended. On the other hand, the evidentiary bar has been raised; "professional judgment" and high-level project summaries are no longer sufficient to prove a process of experimentation. The future of the research credit belongs to those who can marry sophisticated legal challenges to regulatory overreach with meticulous, real-time documentation of their technical journey to resolve uncertainty.