Audit Readiness, Corporate Tax Strategy & Fiduciary GovernancePlaybook3 min readUpdated September 2026

Documenting QREs So Your R&D Credit Actually Holds Up

The IRS doesn't accept an entire engineering department's payroll as qualified research expense just because the department is called engineering. It wants to see the connection between specific wages and specific research activities that actually pass the four-part test, at the level of an individual business component, and that connection has to exist in your records before the audit starts, not get reconstructed afterward.

Here's what documentation actually needs to look like, and the shortcuts that tend to fail.

The four-part test, applied at the business component level

Qualified research has to be technological in nature, aimed at eliminating uncertainty about the development or improvement of a product or process, involve a genuine process of experimentation, and serve a permitted business purpose. The test doesn't apply to your whole R&D function at once; it applies to each individual business component, a specific product, process, or piece of software you were developing or improving, separately. Claiming a credit based on an entire team's activity without breaking it down by component is one of the more common structural weaknesses examiners look for first.

Wages: the connection has to be to activity, not job title

An engineer's title alone doesn't establish that their wages qualify; what matters is the actual time they spent on qualifying research activities for specific components, which means some form of contemporaneous time allocation, even an estimate supported by project records, project management data, or credible testimony from the people who did the work, needs to exist. Treating one hundred percent of an engineering team's wages as qualified because the team is generally understood to do research work is exactly the kind of unsupported allocation that gets reduced or disallowed. The same logic applies to a manager who splits time between genuine research oversight and unrelated administrative work; only the qualifying portion of their time belongs in the calculation.

For example, suppose an engineering manager splits the week between reviewing prototype experiments and handling hiring and budgets. Only the time spent supervising the qualifying experiments belongs in the wage calculation, and you need something that shows that split, such as calendar entries or project tickets. A common mistake is claiming the manager's full salary because the role sounds technical. The fix is a short, recurring time allocation that the manager confirms each quarter, tied to the components being developed. As a decision rule, if you can't point to a record that connects a person's time to a specific component, treat that portion of the wages as unsupported until you can.

Supplies, contract research, and the newer cloud computing category

Supplies used in the research process, prototypes and materials consumed during experimentation, generally qualify in full, while contract research payments to a third party performing qualified research on your behalf typically qualify at a reduced percentage rather than the full amount paid. Certain cloud computing costs tied directly to research activities, a more recent addition to what can qualify, need the same activity-level nexus as wages: the cost has to tie to specific research use, not just general infrastructure spend that happens to run in the same environment as your research.

Why refund claims face a higher documentation bar

The IRS has held research credit refund claims to a heightened documentation standard in recent years, generally expecting the claim to identify the specific business components involved, the research activities performed for each, the individuals who performed them, and the information each activity sought to discover, submitted with enough specificity at the time of the claim rather than assembled afterward if questioned. A claim that reads as a total dollar figure with a general narrative attached, rather than component-by-component detail, is far more exposed under this standard than one built with that structure from the start.

Building contemporaneous records instead of reconstructing them later

The strongest QRE documentation exists because someone captured it close to when the work actually happened: project tracking systems that log which business component an engineer's time went to, experimentation notes and design iteration records showing genuine technical uncertainty being resolved, and a clear separation between research activities and routine production, testing, or customer support work that doesn't qualify. Waiting until the credit is claimed, or until an audit notice arrives, to reconstruct this from memory and generic job descriptions is the single most common reason a credit that felt solid on paper doesn't survive contact with an examiner. Building this habit into how engineering already tracks its own work, rather than layering a separate tax-only process on top of it, tends to be what actually sustains it past the first year.

Keep these records for each business component:

  • A component name tied to the engineering time log, so wages connect to a specific product, process or piece of software rather than to a whole department.
  • Contemporaneous time allocation, or estimates backed by project management data, showing what share of each person's time went to qualifying research.
  • Experimentation notes and design iteration records that show technical uncertainty being resolved through a genuine process of testing alternatives.
  • A clear separation between research work and routine production, testing or customer support, so nonqualifying time never enters the wage calculation.
  • For contract research and cloud costs, the invoices and usage records that tie each cost to a specific research activity.
Executive Capability Standard

What Good Looks Like

Wages, supplies, contract research, and qualifying cloud costs are tracked to specific business components as the work happens, so the credit's documentation already exists before a claim is ever filed.

Building The Capability (5-Stage Skill Ladder)

1. Learn:Read the four-part test and identify which of your current projects would actually qualify as business components under it.
2. Do Manually:Build a simple time allocation process that ties engineering hours to specific qualifying components, not just to a department or team.
3. Delegate:Have project leads maintain experimentation notes and design iteration records as research happens, rather than reconstructing them at tax time.
4. Automate:Tie your project tracking system's time entries to business components directly, so the QRE allocation can be pulled rather than estimated after the fact.
5. Buy:Bring in an R&D credit specialist to build your documentation structure before your next claim, especially if you're claiming a refund rather than offsetting current-year tax.

How to Get Started

Frequently Asked Questions

Can I claim R&D credit based on my whole engineering department's payroll?

Not reliably. The four-part test applies at the level of an individual business component, not the department as a whole, so you need documentation connecting specific wages to specific qualifying activities on specific components, not just a general sense that the team does research work.

Do contract research payments qualify at the full amount?

Generally not. Contract research payments to a third party performing qualified research on your behalf typically qualify at a reduced percentage of the amount paid, not the full payment, so calculate your credit using that reduced figure rather than the total invoice amount.

Why do refund claims face stricter documentation requirements?

The IRS has held research credit refund claims to a heightened standard, expecting the specific business components, activities and people involved to be identified at the time of the claim. A claim with a total dollar figure and a general narrative is far more exposed, so build component-by-component detail before you file.

What kind of time tracking actually supports a wage-based QRE claim?

Contemporaneous allocation tied to specific business components, project tracking data, or credible, detailed testimony from the people who did the work, showing what portion of their time went to qualifying research activities. A job title or department assignment alone, without that activity-level detail, doesn't establish the connection an examiner is looking for.

About the numbers

This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.

Related Guides