R&D Tax Credits for Telecommunications Companies
Summary
Telecommunications companies build and rewrite the systems that move data and calls across networks every day. Network engineering, protocol development, and much of the software behind the modern connectivity we use daily are all activities that potentially qualify for R&D tax credits under IRC §41.
Telecom Companies and the R&D Tax Credit
The telecommunications industry is highly technical, yet many within the industry overlook the R&D tax credit. Network buildouts, protocol testing, spectrum management, and platform development all involve technical uncertainty and experimentation that §41 was written to reward.
The Four-Part Test Applied to Telecom
To qualify as research under IRC §41, an activity must meet all four of the following elements, applied separately to each business component:
• Permitted Purpose: The activity must be intended to develop or improve the functionality, performance, reliability, or quality of a business component.
• Technological in Nature: The work must rely on engineering, physical or biological science, or computer science principles.
• Technical Uncertainty: The activity must be undertaken to discover information intended to eliminate uncertainty about the capability, method, or appropriate design of the business component.
• Process of Experimentation: Your team must have a process that evaluates alternatives through modeling, simulation, systematic trial and error, or other methods to eliminate uncertainty.
What Typically Qualifies
- Designing and testing new network architecture, including 5G and next-gen deployments
- Developing or improving wireless protocols, including work on spectrum strength and signal processing
- Building network security systems, encryption methods, or intrusion detection tools
- Developing IoT platforms, edge computing infrastructure, or systems to manage massive device connectivity
What Typically Will Not Qualify
- Routine network maintenance or upgrades that use established, known methods
- Customer support, help desk work, or troubleshooting with no new technical development
- Market research, customer surveys, or competitive analysis
- Cosmetic changes to a user interface
- Installing, configuring, or customizing vendor-supplied software without resolving a genuine technical uncertainty
The Software Piece
Much of the confusion with R&D tax credits often comes down to software. A large share of telecom R&D now happens inside software systems rather than hardware alone, and as networks become more software defined, that share keeps growing. Software may be treated differently than a physical product under the tax code, but that does not automatically disqualify a company from claiming the credit. Distinguishing which software work qualifies, and which is treated differently, becomes essential to claiming the credit properly.
Under Treas. Reg. §1.41-4, software developed primarily for a company’s own general and administrative functions (i.e. financial management, human resources, or internal support systems) is treated as internal use software. Internal use software has a higher threshold of innovation test that it must meet in addition to the standard four-part test before it qualifies.
The Three Parts of the High Threshold of Innovation Test
Once software is classified as internal use, the following three elements under Treas. Reg. §1.41-4(c)(6)(vii) must be met as well:
- Innovative: The software must be intended to produce a reduction in cost, an improvement in speed, or some other measurable improvement that is substantial and economically significant.
- Significant economic risk: The company must commit substantial resources to the development, and there must be substantial uncertainty, driven by technical risk, about whether that investment can be recovered within a reasonable period.
- Not commercially available: The software cannot be something the company could simply buy, lease, or license and use for its intended purpose without modifications that themselves would satisfy the innovation and economic risk requirements above.
There are certain exceptions that may apply to telecom companies:
- Software used in an activity that already qualifies as research on its own
- Software used directly in a production process
- Software that is an integral part of a new or improved hardware-and-software product the company builds and delivers as a single offering
Software that is not developed primarily for those internal administrative functions does not have to meet that higher threshold. Examples include:
- Software a telecom company develops and sells or licenses to customers
- Software that is an integral part of a product or service the company delivers to third parties, such as a network monitoring platform or core software running a communications service
Under Treas. Reg. §1.41-4(c)(6)(iv), software is not developed primarily for internal use if it is not developed for use in a general and administrative function. Two examples the regulation gives are software developed to be commercially sold, leased, licensed, or otherwise marketed to third parties, and software developed to enable a taxpayer to interact with third parties or to allow third parties to initiate functions or review data on the taxpayer's system. A network monitoring platform or core software running a communications service can fall into either category, which is why it is not held to the internal use software standard.
Systems that support both internal operations and outside users (dual function software) are presumed to be internal use software unless a company can identify and separate out the portion used to interact with people outside the company. Where a company can’t make that separation but reasonably anticipates that third-party use will make up at least 10 percent of the software’s use, a safe harbor allows 25% of the related qualified expenditures to be included in the credit without having to clear the additional high threshold of innovation test that would otherwise apply on top of the standard four-part test for internal use software.
Why an R&D Expert is Important
R&D tax credits are already a nuanced section of the IRC, and the rules get even more complicated when not only hardware but also software is involved, which happens quite often in telecom companies. This makes it imperative to work with an expert who understands the documentation and detail an R&D study requires.
RK Partners has a team of tax attorneys, CPAs, software engineers and consultants who do nothing but R&D tax credits, making them uniquely qualified to build a credit claim that can withstand IRS scrutiny. If you think that your company is performing activities that may qualify for the credit, please reach out. It’s worth the risk-free consultation.
