Why R&D Tax Credit Claims Get Reduced Even When the Work Clearly Qualifies

It happens more often than people expect. A company is doing legitimate qualifying research. The engineers are working on genuinely novel problems. The activities clearly satisfy the four-part test. Then an IRS examination opens, and the credit shrinks significantly or disappears outright.

Not because the work didn’t qualify. Because the documentation didn’t prove it.

This isn’t a theoretical risk. It’s a pattern that shows up regularly in R&D credit examinations. With the IRS raising substantiation standards and Form 6765 now requiring project-level disclosure starting in 2026, this problem is likely to happen more often. Here are the most consistent reasons it happens.

Retrospective Documentation Instead of Contemporaneous Records

The IRS doesn’t audit your engineering work. It audits your records. Experienced examiners recognize assembled-after-the-fact documentation immediately, and they push back hard.

Contemporaneous documentation looks like engineering notebooks, design review records from during the project, test protocols and results, software commit histories with technical annotations, architecture decision logs, and meeting records where technical uncertainty and alternative approaches came up. These are records that would exist regardless of whether the company claimed an R&D credit.

Retrospective documentation looks different. It looks like a tax professional’s notes from an interview with an engineer, conducted months or years after the project ended. Interview-based documentation isn’t inherently invalid, but it doesn’t stand on its own. Practitioners working active examinations report that examiners grow more skeptical of it as a primary record every year. We’ve written in more depth about why audit-ready R&D credits fail, and the shift from contemporaneous to retrospective documentation is consistently the most common reason.

Business Components Described Too Broadly

A business component is any product, process, software, technique, formula, or invention on which qualifying research was conducted. Each component needs specific identification, and the qualifying research needs description in the context of that specific component.

Companies sometimes aggregate too broadly. They treat an entire product line as a single business component, or they describe the component simply as “software development” or “new product research” without specifying what was actually being developed. This makes it easy for an examiner to conclude the claim lacks adequate substantiation. Vague descriptions create vague claims, and vague claims are easy to challenge.

The new Form 6765 Section G addresses this directly. For each component representing part of your top 80% of QREs, you need a description specific enough to identify what the research targeted, not just a label. If you can’t write that description now for your current projects, that’s a documentation problem worth addressing before 2026 filing becomes mandatory.

Officer Wages Without Supporting Documentation

Officer wages generate more examination attention than most companies anticipate. Officers are often highly compensated individuals who genuinely participated in R&D activities. A CTO who oversaw the engineering team working on qualifying research, a VP of Product who directed technical development priorities, a Chief Scientist who led the laboratory program: all of these people may have real, substantial QREs tied to their compensation.

But officer wages are also among the easiest line items to challenge in an examination. If contemporaneous records don’t back the claimed R&D percentage for an officer, actual calendar documentation, project records showing involvement, meeting notes that confirm participation in technical decisions, that percentage looks vulnerable. It will look like an estimate, because without those records, it is one.

Section E of the new Form 6765 now requires companies to disclose total officer wages included in QREs as a separate line item. An examiner can see that number before reviewing a single other document in the return. The answer isn’t to exclude officer wages. It’s to document them with the same rigor you’d apply to any other high-value line item.

Round Allocation Percentages

One pattern that consistently draws examiner attention: allocation percentages that look like estimates rather than measurements. Round numbers, 50%, 75%, 100% for entire departments, signal trouble. So do percentages that have stayed unchanged for several years despite obvious shifts in the work, new projects, reorganizations, changes in headcount.

Allocation methodology needs to produce percentages traceable back to something real: actual time tracking data, project records, a statistically valid methodology applied consistently. If the percentages look like someone made a judgment call at year-end and picked a number that seemed reasonable, an examiner will reach the same conclusion. That creates a credibility problem that extends beyond the specific allocation.

Including Activities That Do Not Qualify

A claim that includes non-qualifying activities doesn’t just create a problem for those specific line items. It creates a credibility problem for the rest of the claim. When an examiner finds activities that clearly don’t qualify, the entire study faces closer scrutiny. The benefit of the doubt that might have applied to ambiguous items disappears.

The categories that most often create this problem: internal-use software developed for general and administrative functions, research where the technical outcome was already known or the industry had already established the method, and activities the funded research rules exclude because a third party bears the financial risk. Getting these qualification determinations right requires genuine technical understanding of the work and legal knowledge of where the lines sit. A checklist shouldn’t make that call alone.

What a Defensible Claim Looks Like

The companies that consistently get through R&D credit examinations without material reductions share several characteristics. They build documentation during the project, not for the audit afterward. Their business component descriptions stay specific and technically grounded. Time tracking or other contemporaneous data backs their allocation percentages. And people who understand both the technology being developed and the legal framework made the qualification determinations.

That combination isn’t complicated to achieve, but it requires building the right habits into the R&D credit process from the start. Retrofitting it after the fact is significantly harder, particularly once an examination is already open.

Want to talk through whether your credit study holds up? Reach out. We would love to help you get ahead of it.

Stephen Whiteaker, CPA

As MASSIE’s Director of Controversy, Stephen specializes in audit risk assessment and quality review. His proficiency in navigating complex tax law makes him an essential resource in addressing tax technical challenges for clients. His exten...