Strata R&D Tax Group
Blog postSeptember 9, 2026

The Costs Automation Integrators Leave Out of an R&D Credit Claim

Most automation integrators assume the R&D credit is about engineer salaries. The rules count more than that, and less than some people hope. A plain-English walk through the four cost categories.

The Costs Automation Integrators Leave Out of an R&D Credit Claim

TL;DR

  • The federal R&D credit is computed on "qualified research expenses," and the rules recognize four kinds: wages, supplies, contract research, and payments for computer use. Most integrators only think about the first one.
  • Wages can include first-line supervisors and hands-on support staff, not just the engineers writing the code. Supplies can include materials consumed building and testing a cell, but not the equipment you keep.
  • Outside engineering help counts at 65 percent, and only if the contract is structured the right way. The details matter more than the headline.

The credit is built on costs, not just activities

Most conversations about the R&D tax credit start with activities: does designing a custom automation cell qualify, does integrating vision and motion control qualify, and so on. That is the right first question. But the credit itself, under IRC Section 41, is calculated on dollars. Specifically, it is calculated on "qualified research expenses," or QREs: the costs a company pays for qualified research, as defined in Treasury Regulation 1.41-4.

For a robotics or automation integrator in the $3M to $15M range, that distinction has real consequences. Two firms doing identical technical work can end up with very different credits depending on how well they identify and support the costs behind that work. In our experience, owners tend to think about one category (engineer salaries) and overlook or misjudge the rest.

The rules at Treasury Regulation 1.41-2 lay out what counts. Here is a plain-English pass through each category, with what it tends to mean on an integrator's floor.

Category one: wages, and whose time actually counts

Wages are usually the largest piece of an integrator's claim. The regulation recognizes three kinds of "qualified services," and only the first is obvious.

Engaging in qualified research. The controls engineer developing the PLC logic for a cell that has never been built before. The robotics programmer working out a path-planning approach for a part geometry the standard library cannot handle. The mechanical designer iterating on end-of-arm tooling. This is the group everyone remembers.

Direct supervision. The regulation describes this as immediate, first-line supervision of the people doing the research. An engineering manager who reviews designs, assigns experiments, and makes the technical calls on a project may fit. A higher-level executive to whom that manager reports generally does not, even if that executive is an engineer by training. Owners of smaller integrators often sit in both roles, so allocating their time carefully matters.

Direct support. This is the category integrators miss most often. The regulation's own examples include a machinist machining a part for an experimental model and a clerk compiling research data. On an automation floor, the analog may be the fabricator building a prototype fixture, the technician wiring a test panel, or the panel builder assembling a first-article cabinet for a design that is still being proven. What does not count: general administrative work, payroll, accounting, and general facility cleaning, regardless of which department those people sit in.

Two mechanics are worth knowing. First, when an employee splits time between qualified and non-qualified work, only the qualified share of their wages counts, and the default method is a time ratio. Second, there is a "substantially all" rule: if at least 80 percent of an employee's wages are attributable to research or direct supervision, the regulation treats all of that employee's services as qualified. For a firm with a small engineering team that lives inside project work, that rule can be meaningful, depending on the specific facts.

Category two: supplies, and the line between consumed and kept

The statute allows supplies "used in the conduct of qualified research." For an integrator, that can include materials consumed while building and testing a cell whose design is still uncertain: prototype fixtures, sacrificial tooling, test parts, sensors and components that get replaced during commissioning trials, and similar items.

What it does not include is the equipment you keep. The statute excludes land and property subject to depreciation, so a robot, a CNC machine, or a test bench that goes on the fixed-asset schedule is not a supply for credit purposes, even if it is used in research every day. The regulation also treats ordinary utilities and general overhead as administrative expenses rather than supplies, with a narrow exception for extraordinary utility costs that the research itself specifically required.

The practical question for a supplies claim is therefore not "what did we buy for that project?" but "what did we consume proving the design out?" Firms that separate prototype and test material from production material in their job costing tend to have a much easier time supporting this category.

Category three: contract research, and the 65 percent rule

When an integrator brings in outside help, whether a contract controls engineer, a specialty vision consultant, or a machine shop building an experimental fixture, the regulation allows 65 percent of the amount paid as a contract research expense, provided the work would have been qualified services had an employee done it.

The rules attach three conditions to a contract research expense, and they are where claims get into trouble. The agreement should be in place before the work is performed. The research should be performed on behalf of your company, which the regulation reads as your company having a right to the results. And your company should bear the cost whether or not the research succeeds. If a payment is contingent on success, the regulation treats it as a payment for a result rather than for research, and that portion does not count.

For integrators, this cuts in a second direction too. The same "on behalf of" and risk-bearing logic determines whether your own work for a customer is yours to claim or your customer's. If your contract shifts the technical risk to the customer and gives them all rights to what you develop, the work may be treated as funded research from your side, which is a separate topic and a separate conversation with your provider.

Category four: computer use and cloud costs

The statute also allows amounts paid to another party for the right to use computers in the conduct of qualified research. For an automation firm, that can come up when simulation, digital twin work, or offline programming runs on rented or cloud infrastructure rather than owned hardware. The regulation frames this narrowly (the computer must be owned and operated by someone else, located off your premises, and you must not be its primary user), so the fit depends on how the environment is actually set up. This category is usually small for integrators, but it is worth checking rather than assuming it is zero.

What this means for how you run the numbers

Three habits make the cost side of a claim easier to support, and none of them require a new system.

Track time by project, or at least by phase, for the people who touch design and commissioning. The wage allocation rules reward a defensible ratio, and a rough after-the-fact estimate is harder to stand behind than contemporaneous job hours.

Separate prototype and test material from production material in job costing. It is the difference between a supplies figure you can document and one you have to reconstruct.

Read your subcontractor agreements before you count them. If a contract was signed after the fact, or payment depends on the design working, the 65 percent may not be available for that portion.

A specialist's role is to apply these rules to your specific activities, documentation, and facts, and to coordinate the result with your CPA so it lands correctly on the return. If you are an automation integrator and have only ever thought about the credit in terms of engineer salaries, there may be more to the picture, or less, and a $0 initial assessment is the way to find out. Start the conversation here.

This post is for informational purposes only and does not constitute tax or legal advice. Consult a qualified tax professional regarding your specific circumstances.

Author

Strata R&D Tax Group

← All insights