Business Component Requirement for the R&D Tax Credit

The business component requirement for the R&D tax credit says that every activity you claim under IRC Section 41 must tie to a specific product, process, computer software, technique, formula, or invention that you intend to sell, lease, license, or use in your business.¹ Each of those items is a separate business component, and the IRS tests each one on its own. You cannot point at your R&D department as a whole and claim the credit; you have to identify the components, test them individually, and back each one with its own expenses and records.

What Qualifies as a Business Component

The statute gives a closed list: product, process, computer software, technique, formula, or invention.¹ Nothing outside that list counts, and the statute does not elaborate on each category, which leaves gray areas the IRS presses on during examinations.

In practice, a product is a tangible item you sell. A process is a method used in manufacturing or service delivery. Computer software includes both programs sold externally and those built for internal use. A technique is a specialized method grounded in scientific or engineering principles. A formula is a chemical or mathematical composition used in production. Invention is the broadest category and covers novel devices or systems regardless of patent status.

The research must aim to improve the component’s function, performance, reliability, or quality. Work that only changes appearance, style, or seasonal design factors does not qualify, no matter how much it cost or how technically complex it was.¹ A fabric weave engineered for durability can qualify. A new color palette for the spring line cannot.

Testing Each Component Separately

The credit hinges on a four-part test, and the business component requirement is one of the four parts. Your expenditures must qualify as research or experimental costs under Section 174. The research must be technological in nature, relying on principles of engineering, physics, biology, chemistry, or computer science. It must relate to developing a new or improved business component. And substantially all of the research must involve a process of experimentation to resolve technical uncertainty.¹

The point that trips up companies is that each part of the test applies to each component, not to your operations or your department’s annual output. If you redesigned a manufacturing process and separately developed a new software tool in the same year, those are two components, and each needs its own four-part analysis. Bundling them together in a credit claim invites the kind of scrutiny that ends in full disallowance.

When You Can Shrink Back to a Subset

Sometimes an overall project fails the four-part test even though real innovation happened inside it. The shrink-back rule addresses that. If the discrete business component does not satisfy the test at the broadest level, you drill down to the most significant subset of elements within it and apply the test there. If that subset fails too, you keep drilling down until you either find a qualifying subset or reach the most basic element and it still fails.²

Think of an entire aircraft that does not pass the test as built. You might shrink back to the propulsion system, then to the navigation module, and so on. The rule only activates when the larger component fails, and it is not a tool the IRS can use to disqualify work that would otherwise qualify.³ To use it effectively, though, you need documentation that traces the hierarchy from sub-components up to the larger project. If an examiner cannot follow how the pieces fit together, the shrink-back argument tends to collapse.

Work That Never Qualifies No Matter the Component

Even when you have identified a legitimate business component, the statute permanently excludes certain categories of work:⁴

Research after commercial production has begun, including trial runs, troubleshooting production equipment, and collecting production data.³
Adapting an existing component to one customer’s specifications.
Duplicating an existing component through reverse engineering or from public specifications.
Efficiency surveys, management studies, market research, advertising, routine data collection, and ordinary quality-control testing.
Research performed outside the United States, Puerto Rico, or U.S. possessions.
Research in the social sciences, arts, or humanities.
Funded research, where a grant, contract, or other arrangement pays for the work.

The adaptation exclusion catches more companies than any of the others. The line between adapting an existing product for a customer and developing an improved version that started from a customer request is genuinely blurry. If the request forced you to resolve real technical uncertainty and the solution broadly advanced the component’s capabilities, you likely have qualifying work. If you were configuring existing features, you do not.

The Higher Bar for Internal-Use Software

Software developed primarily for your own internal operations is treated as its own kind of component, and the statute excludes it unless it clears additional requirements.⁴ Under the Treasury Regulations, software is “internal use” when it supports general administrative functions such as financial management, human resources, or data processing.⁵

Internal-use software must meet a three-part “high threshold of innovation” test. It must be genuinely innovative, delivering substantial and economically significant improvements in cost, speed, or similar measurable outcomes. Its development must carry significant economic risk, meaning you committed substantial resources with real uncertainty about recovery. And it must not be commercially available for purchase, lease, or license without modifications that would themselves meet the first two requirements.

Software built for sale, lease, or licensing to third parties does not face this hurdle. Neither does software that lets third parties interact with your systems or initiate transactions on your platform. Classification depends on intent and the facts at the start of development. If you built something for internal use and later improved it for external distribution, the later improvements are treated as separate development for non-internal use.

Prototypes Count as Component Work

Prototypes and pilot models built during development are part of the component analysis, not something separate. The regulations define a pilot model as any representation of a product built to evaluate and resolve uncertainty during development or improvement, and this includes fully functional versions and, where the shrink-back rule applies, representations of individual components or subcomponents.⁶

What this reinforces is that uncertainty at the component level is what qualifies, not uncertainty about the finished product as a whole. Building a prototype of a new battery cell to test thermal performance is qualifying work tied to that cell as a component, even if you already know the surrounding device design will work. The prototype’s costs flow to the component it was built to evaluate.

Linking Expenses to Each Component

Identifying components is only half the job. You also need a clear line between each component and the money spent developing it. The IRS calls this the nexus between qualified activities and specific business components, and it is one of the primary points examiners use to challenge claims.

The IRS Audit Techniques Guide describes the records examiners look for:⁷

Project authorizations and budgets, including work orders and internal approval documents that initiated the research.
Progress reports, meeting minutes, board submissions, and review committee presentations related to the research.
Technical documentation such as field and lab data, design specifications, testing protocols, and prototype evaluations.
Complete copies of contracts, letter agreements, and memoranda of understanding for any research performed by or on behalf of third parties.
Brochures, press releases, research papers, and internal audit reports that reference the research.

Oral testimony from people with direct knowledge can supplement the records but does not replace them.⁷ The most reliable approach is to organize documentation by component from the start rather than reconstruct it later. Project tracking numbers and budget codes tied to specific components make examinations far easier than records kept only by department or cost center.

New Component-Level Reporting on Form 6765

For tax years beginning after 2025, Form 6765 has a new Section G that demands component-level detail on the return itself.⁸ You must report at least 80% of total qualified research expenses by individual business component, listed in descending order by expense amount, up to a maximum of 50 components. For each one, you provide the entity’s EIN, a principal business activity code, the component’s name or identifier, its type (product, process, or “all others”), and whether any software involved is internal-use, dual-function, or non-internal-use. You also break down wage expenses by category (direct research, supervision, and support), supply costs, computer rental costs, and contract research expenses.

This is a shift from prior practice. Component detail used to be something you assembled if audited. It now has to be on the return, and companies that track expenses by department rather than by component will find at filing time that they cannot populate Section G.

Refund Claims

Refund claims that include the R&D credit have their own component-level requirements. At the time of filing, the claim must identify every business component that forms the basis of the claim, describe all research activities performed for each one (boilerplate statutory language is not enough), and total each qualified expense category, with a signed declaration under penalties of perjury. For claims filed on or after January 11, 2026, missing any of the three required items means the IRS will issue a no-consideration letter and refuse to process the claim, with no opportunity to cure the defect.⁹

Penalties for Weak Component Substantiation

Failing to substantiate components does not just cost you the credit. It can trigger penalties on top of the disallowance.

The most common is the 20% accuracy-related penalty under Section 6662, which applies to underpayments caused by negligence or a substantial understatement of income.¹⁰ A large credit claimed without adequate records to tie expenses to components can be characterized as negligent, and the 20% is added to the resulting underpayment.

Where the IRS determines fraudulent intent was involved, the penalty rises to 75% of the underpayment attributable to the fraud.¹¹ Criminal prosecution for willful evasion is rare in the R&D credit context, though the statute allows fines up to $100,000 for individuals and $500,000 for corporations, and imprisonment of up to five years.¹² For most companies the realistic exposure is the 20% negligence penalty, which becomes substantial when a large credit is fully disallowed.

1
Office of the Law Revision Counsel. 26 USC 41 – Credit for Increasing Research Activities
2
eCFR. 26 CFR 1.41-4 – Qualified Research for Expenditures Paid or Incurred in Taxable Years Ending on or After December 31, 2003
3
Internal Revenue Service. Audit Techniques Guide – Credit for Increasing Research Activities IRC 41 – Qualified Research Activities
4
Office of the Law Revision Counsel. 26 U.S. Code 41 – Credit for Increasing Research Activities
5
eCFR. 26 CFR 1.41-4 – Qualified Research for Expenditures Paid or Incurred in Taxable Years Ending on or After December 31, 2003
6
eCFR. 26 CFR 1.174-2 – Definition of Research and Experimental Expenditures
7
Internal Revenue Service. Audit Techniques Guide – Credit for Increasing Research Activities IRC 41 – Substantiation and Recordkeeping
8
Internal Revenue Service. Instructions for Form 6765 (Rev. December 2025)
9
Internal Revenue Service. Updated Interim Guidance on Claims for Refund That Include a Claim for Credit for Increasing Research Activities
10
Office of the Law Revision Counsel. 26 USC 6662 – Imposition of Accuracy-Related Penalty on Underpayments
11
Office of the Law Revision Counsel. 26 USC 6663 – Imposition of Fraud Penalty
12
Office of the Law Revision Counsel. 26 USC 7201 – Attempt to Evade or Defeat Tax