Credits & Incentives
Defensible credit file
R&D credit work is visualized as a file, not a claim: eligibility, QRE support, Form 6765, and examination readiness.
Audit-ready claim design
Structure the credit file around business components, technical uncertainty, experimentation, permitted purpose, and cost nexus before an IDR arrives.
Documentation and witnesses
Coordinate project records, employee interviews, technical narratives, tickets, specifications, tests, and contractor documentation.
Calculation support
Reconcile wage allocations, supplies, cloud or prototype costs, contractor amounts, exclusions, Section 280C, and Section 174A return treatment.
This page is educational and is not tax, legal, accounting, investment, insurance, or other professional advice. Client-specific work requires written scope and review by qualified professionals. Legal representation, privilege, litigation strategy, and regulated services are provided only by properly licensed or registered counsel, affiliates, or other professionals where included in scope. IRS, state, collection, appeals, penalty, and litigation-sensitive matters require deadline control, authorization review, and appropriate representative or counsel involvement. Use public forms only for non-sensitive triage. Do not submit tax returns, notices, account statements, identification documents, privileged communications, or other sensitive records through public forms; secure portal review begins only after qualification and written scope.
Exam response workflow
Prepare issue maps, document indexes, response packages, exhibit lists, and advisor roles for a clear examination process.
Professional boundaries
Tax analysis and documentation support can be coordinated by MMVFO; legal strategy, privilege, and litigation matters require qualified counsel.
R&D credit audit defense posture
Apply the test by business component
The R&D credit is analyzed against qualified research tied to a specific product, process, software item, technique, formula, or invention. Broad innovation labels are not enough; the file should show the facts for each business component.
Connect costs to qualified work
Wages, supplies, contract research, and computer rental or lease costs should be supported by records that explain who did the work, what was tested, how costs were allocated, and what was excluded.
Evidence answers the examiner's next question
Audit-ready support explains the claimed business components, qualified activities, exclusions, QRE methodology, Form 6765 inputs, and return positions from records that can be reviewed.
Defense is support, not a guarantee
A defensible file can improve consistency and response quality, but outcomes depend on facts, records, law, procedures, agency review, and professional judgment.
Qualified research expense support categories
The claim file should separate each cost category and show the source records, allocation method, and connection to qualified research.
| Category | What to support | Useful records |
|---|---|---|
| Wages | Identify employees performing, directly supervising, or directly supporting qualified services and document the allocation method. | Payroll registers, employee rosters, role summaries, time data, interviews, org charts, project records. |
| Supplies | Show the item, amount, timing, and how tangible property was used in qualified research while excluding capital items and overhead. | Invoices, purchase records, item descriptions, lab or shop usage notes, prototype records. |
| Contract research | Show who performed the work, the taxpayer's rights and financial risk, invoices, scope, and the allowable percentage under Section 41 rules. | Contracts, SOWs, amendments, vendor invoices, deliverables, rights clauses, risk terms. |
| Computer rental or lease costs | Show the amount, usage, and connection to qualified research where the statute and regulations permit inclusion. | Provider invoices, usage reports, project mapping, allocation schedules. |
| Business-component allocation | Assign QRE categories to specific components or support any permitted aggregation consistently with the reporting method. | Component registry, project mapping, Form 6765 workpapers, reviewer notes. |
| Reconciliation support | Tie QRE totals to the ledger, payroll, invoices, trial balance, Form 6765, and return positions. | GL exports, payroll summaries, invoice schedules, return workpapers, review memos. |
Defensible R&D credit file
A serious Section 41 file should be organized so a return preparer, reviewer, or examiner can trace the position from technical facts to QRE support and Form 6765.
- Business component index. List each product, process, software item, technique, formula, or invention evaluated for the claim year.
- Four-part test memos. Tie facts for each included component to permitted purpose, technological uncertainty, experimentation, and qualified research expense treatment.
- Exclusion screening. Document removal of post-commercial-production work, customer adaptation, duplication, surveys or studies, foreign research, funded research, and other excluded activities.
- QRE workpapers. Separate wages, supplies, contract research, and computer rental or lease costs, with allocation methods and source records.
- Technical substantiation. Preserve project plans, design records, tickets, sprint artifacts, lab notes, prototypes, test plans, test results, change logs, and failure analyses.
- Return reconciliation. Tie study amounts to the general ledger, payroll, trial balance, Form 6765, Section 280C treatment, and research-expense workpapers.
- Controlled-group and amendment support. Include required controlled-group attachments and, for amended claims, the refund-claim detail and signed declaration required by current IRS procedures.
Common R&D credit audit and claim risks
These are the gaps MMVFO screens before a claim is filed, amended, relied on in diligence, or defended in examination.
- Using broad department-level narratives instead of business-component analysis.
- Treating all engineering, product, software, or process-improvement work as qualified without exclusion screening.
- Claiming work after commercial production began.
- Including customer-specific adaptation, duplication, surveys, foreign research, funded research, or unsupported internal-use software work.
- Unsupported wage allocations or interviews that do not match payroll, org charts, repositories, tickets, or project records.
- Supply claims that include depreciable property, prototypes without support, general overhead, or indirect costs.
- Contract research claims without adequate contracts, risk-of-loss terms, rights terms, or vendor detail.
- Controlled-group errors, missing attachments, inconsistent methods, or incomplete Section 280C and research-expense coordination.
- Amended claims that omit required business components, research activities, QRE totals, or signed declaration support.
Diagnostic questions
- What was the specific business component being developed or improved?
- What technical uncertainty existed at the start of the work?
- Why could the answer not be determined from existing knowledge, standard practice, or ordinary implementation?
- What alternatives were considered, modeled, simulated, prototyped, or tested?
- What technical criteria were used to evaluate success or failure?
- What changed between early and later versions, and what evidence shows the iteration?
- When did commercial production begin, and what work occurred after that point?
- Was any work performed to adapt an existing product or process for one customer?
- Was any part of the work duplicated from an existing product, process, design, or code base?
- Was any research performed outside the United States or U.S. territory?
- Was any work funded by a customer, grantor, or other third party?
- Which employees directly performed, directly supervised, or directly supported the qualified work?
- What records were created during the project, and where are they retained?
- For software, was the software internal-use, dual-function, or non-internal-use, and what support exists for that classification?