Which SaaS Costs Qualify as QREs

Once you know your team is doing qualifying research, the next question is the practical one: which costs actually count toward the credit? In §41 terms, those are your qualified research expenses, or QREs. They are a subset of the broader research costs covered by §174, and they fall into four defined categories. For a SaaS company, knowing how each works helps you avoid both leaving money out and claiming costs that do not belong. The Four QRE Categories The credit only reaches specific kinds of cost. Here is the full set:Wages. The W-2 taxable wages of employees who perform qualified research, supervise it, or directly support it. Supplies. Tangible items used and consumed in the research. For a pure software company this is usually minor, since most SaaS research does not consume physical materials. Contract research. 65% of amounts paid to US-based third parties who perform qualified research on your behalf. The reduction to 65% reflects that the work was done outside your company. Cloud and computer rental. Payments to rent computing power, such as AWS or GCP capacity, used for development and testing in your R&D.For most SaaS companies, three of these matter in practice: wages, cloud, and US contractors. Supplies tend to be negligible. The exact treatment of any category depends on your facts, so confirm the specifics with a CPA for your situation. Wages Are Usually the Largest Bucket For most software companies, US engineering payroll is by far the biggest source of QREs. The wages that count are the taxable W-2 wages of people who fall into one of three roles relative to qualified research: they perform it, they supervise it, or they directly support it. A few practical points shape how this works:Hands-on engineering is the obvious case, but direct supervision and direct support of qualifying research can also count, as long as the connection is real and documented. Only the portion of a person's wages tied to qualified research counts. An engineer who splits time between new development and routine maintenance is not fully allocable to research.Because payroll is usually the dominant QRE for SaaS, getting the wage allocation right has the biggest effect on the size and defensibility of a claim. Cloud and US Contractors Round It Out After wages, two categories typically add the most for a software company. Cloud and computer rental covers what you pay to rent computing power used in development and testing. This is the modern bucket that did not exist in a meaningful way when the credit was first designed. The key boundary is that the spend has to be tied to research, your development and testing environments, rather than to running your production service for paying customers. Clean billing tags that separate dev and test usage from production make this far easier to support. Contract research covers third parties doing qualified research on your behalf, counted at 65% of what you paid them. Two conditions matter most for SaaS: the work has to be performed in the US to count toward the federal credit, which is significant for teams using offshore development, and you generally need to bear the financial risk and retain rights to the results. A pure fixed-deliverable arrangement where the contractor keeps the risk and the IP usually does not qualify. Allocation and the §280C Reminder Two things tie the buckets together. First, allocation: only the portion of any cost tied to qualified research counts. Time tracking and a clear mapping of which people and resources went to which projects are what support the allocation if anyone asks. Second, a reminder from the deduction side. Under §280C, claiming the credit on your wages and other QREs generally reduces the matching deduction you take on those same costs, or you elect a reduced credit instead. You do not get the full value of both the credit and the deduction on the identical dollar. How that election plays out for you is a question for your CPA. A realistic SaaS claim usually combines a meaningful slice of US engineer payroll, the cloud spend tied to development and testing, and 65% of qualifying US contractor costs. Payroll is almost always the largest piece. The amounts that ultimately qualify depend entirely on your facts, so any specific figures should come from running your actual numbers. Pulling this picture together from payroll and engineering data is the work TaxUpside does for SaaS teams. This is general information, not tax advice. The right treatment of your wages, supplies, contractor, and cloud costs depends on your specific situation, so confirm with a qualified CPA before filing.