An R&D tax credit study should do more than calculate a credit. It should document what the company researched, why the research was necessary, who performed the work, and how the related expenses were determined.
That documentation becomes especially important if the IRS examines the claim. A study prepared with audit readiness in mind gives a reviewer a logical path from the company's research activities to the credit calculation.
So, what should an audit-ready R&D study actually contain?
What Is an R&D Tax Credit Study?
An R&D tax credit study identifies qualifying research activities, determines the associated qualified research expenses (QREs), and documents the basis for the credit claimed.
The process typically draws information from technical teams, employees, accounting records, project documentation, and other business records.
A well-supported study should connect five pieces:
What was being developed → What technical challenges were encountered → What research was performed → Who performed it → What expenses resulted
When those pieces line up, the basis for the credit is much easier to understand and substantiate.
5 Elements of an Audit-Ready R&D Study
1. Clear Business Component Identification
A study should clearly identify the products, processes, software, or other business components associated with the research.
This gives the study a specific foundation. Rather than describing a company's R&D activities broadly, the documentation should establish what the company was actually trying to develop, improve, or resolve.
For example, "the engineering team worked on product improvements" provides little context.
A stronger description identifies the specific product or process, the development objective, and the research activities associated with it.
The IRS's audit guidance emphasizes identifying qualified research expenses by business component, making this connection an important part of substantiating a claim.
2. Specific Technical Narratives
The technical portion of the study should explain the challenges the company faced in terms that a reviewer can understand.
That means addressing questions such as:
- What was uncertain at the beginning of the project?
- What information did the company need to discover?
- What alternatives or approaches were considered?
- How did the company test those alternatives?
For example:
Weak: The company developed a new software platform.
Stronger: The development team needed to determine whether the platform could process significantly higher data volumes without compromising response times, requiring the team to evaluate and test multiple architectural approaches.
The second description explains why research was necessary and what the team was actually trying to resolve without relying on technical jargon.
3. A Connection Between Activities and Employees
The study should establish who performed the research and what those individuals contributed.
Job titles alone aren't enough. An engineer, developer, scientist, or project manager may perform both qualifying and non-qualifying activities during the same year.
The documentation should describe employees' relevant research activities and provide a reasonable basis for determining the portion of their wages associated with qualified research.
Supporting records may include payroll information, time records, project assignments, employee interviews, project documentation, or other business records.
The objective is to support the wage expenses included in the claim with a reasonable methodology and appropriate records.
4. Supporting Documentation for the Claim
The technical narrative should be supported by the underlying business records.
Depending on the company and the research involved, useful documentation may include:
- Design and engineering records
- Technical specifications
- Test results
- Prototypes and development records
- Project management records
- Employee and payroll records
- General ledger information
- Invoices and receipts
- Contracts with research providers
- Project communications
The IRS expects taxpayers to maintain records sufficient to substantiate their research credit claims. The most useful documentation is directly relevant to the activities and expenses being claimed rather than simply accumulated as a large collection of files.
5. Consistency Between the Technical and Financial Records
The technical portion of the study and the financial calculation should tell the same story.
If the study identifies certain employees as performing research on a particular project, the wage calculation should reflect that methodology.
If supplies are included as QREs, the accounting records should support the amounts claimed and their relationship to the research.
If contract research expenses are included, the relevant agreements and payment records should support their treatment.
A reviewer should be able to trace the claim from the research activities through the supporting records to the final credit calculation.
What Can Make an R&D Study Difficult to Defend?
More pages or more documentation don’t necessarily make a study stronger. The important question is whether the records support the claim.
Common weaknesses include:
Vague Project Descriptions
Broad statements about "innovation," "product development," or "software improvements" don't establish what technical work was actually performed.
Unsupported Expense Allocations
A study may identify substantial qualified wages or other expenses, but the methodology used to calculate those amounts should be supported by appropriate records.
Heavy Reliance on Reconstructed Information
Documentation created long after the research occurred can be useful, particularly when reconstructing historical activities. Contemporaneous business records, however, can provide stronger support for what actually occurred.
Disconnects Between the Study and Business Records
If the study says one thing while payroll, accounting, project, or contract records suggest something different, the inconsistency can create questions about the claim.
Treating the Study as the Evidence
The study summarizes and analyzes the evidence. It does not replace the underlying records that support the claim.
An Audit-Ready Study Is Built Around the Evidence
Before finalizing a study, ask:
- Can we clearly identify the business components involved?
- Does the study explain the actual technical challenges?
- Can the research activities be connected to the employees and expenses claimed?
- Do the underlying records support the technical narrative and financial calculations?
- Are there inconsistencies that could raise questions about the claim?
If the answer to each is yes, the study has a much stronger foundation for supporting the credit if the claim is reviewed.
Audit readiness does not require an enormous documentation package. It requires a clear record showing what research was performed, who performed it, how the work was evaluated, and how the related expenses were determined. Building that record during the study process is far easier than trying to reconstruct it later.
Need Help Preparing an Audit-Ready R&D Tax Credit Study?
A well-supported R&D tax credit starts with identifying the right research activities and documenting how they connect to the expenses being claimed. Acena Consulting helps businesses evaluate qualifying activities, calculate eligible expenses, and build the supporting documentation needed for a defensible claim.
If you're preparing an R&D tax credit study or want to assess whether your existing documentation is sufficient, contact Acena Consulting to discuss your situation.
