A common question is whether regulatory compliance testing can be part of R&D for the federal R&D tax credit. The short answer is that a regulatory compliance requirement itself does not create qualified research. However, technical development undertaken to meet performance requirements may involve potentially relevant research if it includes a process of experimentation. The distinction between experimentation and routine certification is key. This page explains the framework in general terms. It is educational and is not individualized advice. For the foundational framework, see our page on qualified research.
Compliance Requirements Do Not Create Qualified Research
A regulatory compliance requirement — a requirement that a product meet a specified standard or regulation — does not by itself create qualified research. Testing a product merely to verify that it meets the regulatory requirement is generally certification testing, not qualified research. The existence of a regulatory requirement does not change the analysis; the four-part test still applies, and the work must involve a technical uncertainty and a process of experimentation. For more, see our page on certification testing.
Technical Development to Meet Performance Requirements
However, technical development undertaken to meet performance requirements — including regulatory performance requirements — may involve potentially relevant research. If a company is developing a new product to meet a regulatory performance requirement and is uncertain whether the product can achieve the required performance, the development work may involve a technical uncertainty and a process of experimentation. In that case, the work may warrant review as qualified research, provided the other elements are met.
The distinction is between:
- Routine compliance testing — testing a product to verify that it meets a regulatory requirement. This is certification, not research.
- Compliance-driven development — developing a new or improved product to meet a regulatory performance requirement, where the development involves a technical uncertainty and a process of experimentation. This may warrant review as qualified research.
Experimentation vs. Routine Certification
The key distinction is between experimentation and routine certification:
- Routine certification — the test method, the standard, and the expected result are all known. The testing verifies conformance. This is not qualified research.
- Experimentation — the work evaluates alternatives to resolve a technical uncertainty about whether a product can achieve a required performance. This may warrant review as qualified research.
For more on this distinction, see our page on routine testing vs. R&D experimentation.
Hypothetical Example
Consider a manufacturer that is developing a new product that must meet a regulatory emissions standard and is uncertain whether any available design can achieve the required emissions performance. The company evaluates alternative designs, tests each for emissions, and systematically modifies the design based on the results. This development work — evaluating alternatives to resolve a technical uncertainty about whether the product can meet the regulatory requirement — may warrant review as qualified research.
By contrast, if the same manufacturer tests production units to certify that they meet the emissions standard using a standard test method, that is routine certification, not research.
These examples are illustrative only and do not state whether any particular activity qualifies.
Documentation That May Help
Records that can help support the regulatory compliance testing analysis include records showing whether the work was routine certification or development-driven experimentation, records of the technical uncertainty (if any), records of alternatives evaluated (if any), and records showing when commercial production began. For more, see our page on R&D tax credit documentation.
Key Takeaway
A regulatory compliance requirement itself does not create qualified research. However, technical development undertaken to meet performance requirements may involve potentially relevant research if it includes a process of experimentation. The distinction between experimentation and routine certification is key. Because the distinction is fact-specific, professional review is appropriate.