A common question is the difference between software integration and qualified research for the R&D tax credit. The short answer is that routine software integration using standard APIs and known methods generally is not qualified research. Integration that involves a technical uncertainty and a process of experimentation may warrant review, subject to internal-use software rules. 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.
Routine Integration
Routine software integration — connecting systems using standard APIs and known methods — generally is not qualified research. The characteristics include:
- Standard API — the integration uses a standard, documented API.
- Known systems — the systems being integrated are known and established.
- No technical uncertainty — there is no question about whether the integration will work.
Where all three are present, the work is routine integration, not research.
Integration That May Warrant Review
Integration may warrant review when it involves a technical uncertainty and a process of experimentation:
- New system — integrating a new system where there is uncertainty about whether the integration can achieve the required performance.
- Custom protocol — developing a custom integration where there is uncertainty about whether it can achieve the required performance.
- Scale uncertainty — integrating systems at a new scale where there is uncertainty about whether the integration can handle the required volume.
Where the integration involves evaluating alternatives to resolve a technical uncertainty, the work may warrant review, subject to the internal-use software rules under Section 41(d)(4)(E).
Hypothetical Example
Consider a company that integrates a standard payment API into its application. This is routine integration, not research.
By contrast, if the company integrates a new system with an existing system where there is uncertainty about whether the integration can achieve the required real-time performance, and evaluates alternative approaches through a structured process, the work may warrant review as qualified 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 integration vs. research analysis include records showing whether the work was routine integration or research, records of the technical uncertainty (if any), and records of the process of experimentation (if any). For more, see our page on R&D tax credit documentation.
Key Takeaway
Routine software integration using standard APIs and known methods generally is not qualified research. Integration that involves a technical uncertainty and a process of experimentation may warrant review, subject to internal-use software rules. Because the distinction is fact-specific, professional review is appropriate before claiming the credit.