Project Accounting & The R&D Tax Credit
Establishing the critical "Nexus" between financial expenses and qualified research activities (IRC §41).
The Meaning & Importance
Context: Establishing the Foundation
Project Accounting is a specialized form of financial tracking that creates a direct link—or "nexus"—between specific business activities and the costs incurred to perform them. Unlike standard General Ledger (GL) accounting, which aggregates expenses into broad functional categories like "Salaries" or "Supplies," Project Accounting assigns every dollar to a specific job code, task, or initiative. In the context of the R&D Tax Credit (IRC Section 41), this granularity is not merely a best practice; it is often the dividing line between a defensible claim and a disallowed one. IRS regulations explicitly require taxpayers to substantiate that claimed expenses are directly attributable to "Qualified Research Activities" (QRAs). Without project-level detail, companies are forced to rely on high-level estimates, which legal precedents (such as the Cohen and Shami cases) have historically scrutinized or rejected for lacking contemporaneous documentation.
The importance of Project Accounting culminates in its ability to isolate Qualified Research Expenses (QREs) from standard operational costs, thereby maximizing the credit while minimizing audit risk. For example, an engineer’s salary might be $150,000. In a GL view, the entire amount is ambiguous. However, Project Accounting might reveal that 60% of their time was charged to "New Algorithm Development" (Qualifying), while 40% was "Legacy System Maintenance" (Non-Qualifying). This precise allocation provides the "substantiation" mandated by the IRS, allowing the taxpayer to confidently calculate the credit based on the 60% portion. By implementing robust time-tracking and job-costing systems, organizations transform their R&D claim from a risky estimation into a data-backed financial asset.
The "Black Box" Problem
Most companies operate using Standard General Ledger (GL) Accounting. Expenses are dumped into large buckets. To an IRS auditor, this looks like a "Black Box."
Interact with the charts to see how shifting to Project Accounting reveals the hidden value inside your expenses.
Total Dept. Spend: $1,000,000
Without project codes, all expenses look the same.
Real World Example: "TechNova Corp"
See how data granularity changes the outcome of a tax credit claim.
The Situation
TechNova spent $1.2 Million on software engineering salaries this year. They want to claim the R&D credit.
- ✖ No Time Tracking
- ✖ Single GL Account: "Salaries"
- ✔ Manager "Estimation"
| Methodology | Claim Calculation | IRS Result |
|---|---|---|
| Top-Down Estimation "I think they spent 50% of time on R&D." | $600,000 QREs | High Audit Risk No contemporaneous nexus. |
| Project Accounting Tracking specific job codes. | $725,000 QREs Discovered hidden R&D time! | Defensible Clear audit trail exists. |
Next Steps: Building Your Audit Trail
To clarify Project Accounting and ensure compliance, implement the following workflow. Click each step for details.
The Strategic Imperative of Project Accounting for R&D Tax Credit Compliance and IRS Nexus Substantiation
Executive Summary: Project Accounting as the Foundation of R&D Credit Nexus
Project Accounting (PA) is defined as a granular methodology for tracking comprehensive financial data—including budget, costs, and revenue—for each specific, individualized project.1 Unlike traditional financial accounting, which aggregates costs across the entire entity over continuous fiscal periods, PA focuses on the temporary, finite lifecycle of a single project.1 This specialized financial monitoring system is critical for professional services firms to track specific internal labor costs, external vendor expenses, and budget variances associated with unique client scopes or developmental efforts.1 In the context of Internal Revenue Code (IRC) Section 41, which governs the U.S. Research and Development (R&D) Tax Credit, PA transitions from a useful internal management tool to an indispensable compliance mandate.4 Its primary function in this regulatory environment is to establish and document the critical financial linkage—or Nexus—between specific Qualified Research Expenses (QREs) and the individual Qualified Research Activities (QRAs) performed on an eligible business component.5
The importance of Project Accounting stems directly from the stringent documentation requirements imposed by the Internal Revenue Service (IRS). The IRS Audit Techniques Guide explicitly identifies project-based accounting as the methodology that “generally establishes the required nexus” by capturing research costs at the “business component” level.5 By tagging expenses contemporaneously to a defined project, PA provides the level of detail necessary to withstand audit scrutiny, a level of detail that aggregated cost center accounting often fails to deliver.6 Since taxpayers are required to evaluate R&D eligibility against the rigorous four-part test for each individual business component 7, Project Accounting ensures that the financial data structure aligns perfectly with the tax unit of measure. This foundational alignment allows for the precise segregation of qualifying costs (e.g., direct wages, consumed supplies) from non-qualifying costs (e.g., General and Administrative overhead), proactively mitigating the risk of credit disallowance due to insufficient substantiation.4
Section 1: Defining Project Accounting in a R&D Context
1.1 Project Accounting (PA): A Detailed Definition
Project Accounting involves the detailed monitoring of all financial metrics relevant to a specific undertaking, focusing on project budgets, costs, and overall profitability.3 The tracked elements include internal labor costs, calculated based on specific hours worked and established labor rates, as well as external vendor and contractor costs.1 PA’s objectives are manifold: monitoring project budgets to identify and correct variances; controlling cost behavior by distinguishing between direct, indirect, fixed, and variable costs; and ensuring revenue recognition aligns with project milestones and applicable accounting standards.3
This methodology stands in sharp contrast to traditional financial accounting. Financial accounting focuses broadly on the company’s overall financial health, typically following continuous fiscal years to track company-wide profit and loss.1 Project accounting, conversely, is temporary, defined by the start and end dates of the project lifecycle, and tracks budget, costs, and revenue specifically per project.1 This granular focus on specific deliverables and milestones allows project managers and finance teams to make informed decisions that support sustainable business growth at the micro-level.3
1.2 Aligning PA with the Tax Unit of Measure (Business Component)
The fundamental difference between PA and financial accounting is the level of data aggregation. PA delivers detailed insights into the revenue and cost associated with every project individually, moving beyond generalized, company-wide financial data.9 This disaggregation is crucial because the statutory requirements for the R&D tax credit mandate that research activities must meet the four-part test, and expenses must be traced, for each specific business component.7
For R&D credit purposes, Project Accounting serves as the tax-compliant data architecture. Since IRC §41 requires eligibility to be tested at the level of the business component (e.g., a specific product feature, a new manufacturing process, or a software module), the financial system must naturally organize costs around these components. Traditional financial accounting, which aggregates data at the entity level, forces taxpayers to engage in complex, often retrospective, cost reconstruction during the claim process. By contrast, implementing PA means adopting a financial structure where the tracking of project costs, expenses, and deliverables inherently aligns with the IRS’s preferred unit of analysis. The process steps of PA—such as creating clear cost estimates, tracking expenses meticulously, and monitoring performance indicators 1—are structured to continuously generate the precise transactional data required for tax substantiation, dramatically reducing the complexity and increasing the audit defensibility of the final R&D credit calculation.
Section 2: The Regulatory Environment and R&D Tax Credit Fundamentals
2.1 Overview of IRC Section 41 and Qualified Research Expenditures (QREs)
IRC Section 41 establishes the requirements for the R&D Tax Credit, allowing companies to claim credits for incremental costs incurred during the development or improvement of products, processes, techniques, formulas, or software used in their trade or business.10 Qualification is based on the performance of Qualified Research Activities (QRAs) intended to eliminate technical uncertainty through a systematic process of experimentation.12
Qualified Research Expenses (QREs) are rigidly defined and limited to three statutory categories 13:
- Wages: Compensation paid to employees for performing qualified services, which include engaging in qualified research, direct supervision, or direct support of research activities.14 The largest portion of QREs typically relates to wages.14
- Supplies: Tangible personal property used in the conduct of qualified research that is consumed or used up during the process. This explicitly excludes land, improvements to land, and any property of a character subject to depreciation (e.g., equipment or research facilities).10
- Contract Research Expenses (CRE): Sixty-five percent of amounts paid or incurred to non-employees for qualified research performed on behalf of the taxpayer.13 This limit can be 75% if paid to a qualified research consortium.15
A specialized segregation mandate is imposed by the R&D credit rules, requiring immediate separation of eligible QREs from ineligible costs. Costs such as General and Administrative (G&A) expenses, travel, meals, entertainment, license fees, and equipment rental (which are depreciable or not tangible property) are typically ineligible, even if incurred in support of qualified research.10 Standard financial accounting often aggregates these expenses, necessitating that Project Accounting implement specific expense coding and cost centers within the general ledger (GL) to immediately isolate QREs and address these statutory limits before calculations proceed.4
2.2 The Four-Part Test for Qualified Research Activities (QRA)
For an activity to be deemed “qualified research,” it must satisfy four concurrent tests applied to each business component 7:
- Permitted Purpose: The activity must be related to developing or improving the function, quality, reliability, or performance of a business component.17
- Technological in Nature: The research must fundamentally rely on the principles of physical or biological science, engineering, or computer science.17
- Elimination of Uncertainty: The taxpayer must intend to discover information that resolves uncertainty concerning the capability, methodology, or appropriateness of the development or improvement.17
- Process of Experimentation: A systematic process must be employed to evaluate alternatives and achieve the desired result.17
The structure of the R&D claim relies on a critical link between technical eligibility and financial capture. The Four-Part Test necessitates robust technical documentation confirming the uncertainty and experimentation associated with a business component, thereby establishing eligibility.17 Project accounting then provides the system for attaching verifiable costs (QREs) to that eligible narrative, utilizing the corresponding project code.5 Compliance requires seamless cross-functional alignment where the technical team’s definition of “project” (the business component) dictates the financial team’s expense coding within the Project Accounting system.
Section 3: The Critical Nexus Requirement and Audit Risk Mitigation
3.1 Establishing the “Nexus”: Why Project Accounting is Mandated by Audit Defense
The paramount challenge in defending an R&D tax credit claim is proving the direct link, or nexus, between the claimed expenditures (QREs) and the qualified research activities (QRAs). The IRS has repeatedly expressed frustration with methodologies that exhibit a “lack of nexus” between the business component and the claimed expenses, a concern raised prominently in the Audit Techniques Guides.6
Establishing this causal link is crucial because the IRS may challenge the allocation of costs if it cannot definitively verify that the expense was incurred exclusively for qualified research. The IRS Audit Techniques Guide explicitly favors project-based accounting because it captures costs at the business component level, effectively establishing the necessary nexus.5 This methodology provides an evidentiary trail that follows the expense from the initial transaction (e.g., time entry, invoice) directly to the specific technical effort that meets the four-part test. Implementing a project accounting methodology is therefore not merely a preferable calculation technique; it is recognized as the most robust and IRS-preferred risk mitigation strategy available to taxpayers for defending their claim.
3.2 Failure of Alternative Methods: The Deficiencies of Cost Center and Hybrid Accounting
Taxpayers who rely on traditional cost center accounting or arbitrary hybrid methods face significant audit risk. Cost center accounting typically aggregates costs by department (e.g., “Engineering Department”), often commingling qualified research costs with non-qualified activities such as routine maintenance, administration, or manufacturing support.5
IRS agents are instructed to disallow claims where the basis for allocating activities or expenses is deemed arbitrary, or where the cost center included non-qualified activities without corroborative evidence to support the cost allocation.5 For instance, a generalized departmental allocation relies heavily on retrospective estimates, which the IRS views as high risk. Project Accounting directly resolves this by requiring the initial categorization of every expense record—time logs, payroll records, and vendor invoices—to the lowest level of detail: the specific project (business component).16 This prevents the co-mingling of costs at the source, thus bypassing the deficiencies inherent in reconstructed, high-level allocations.
3.3 The Imperative for Contemporaneous Documentation
Successful defense of an R&D credit claim requires detailed documentation that is contemporaneous, meaning it must be created at the time the activity or expense is incurred, rather than reconstructed after the fact.19 The IRS requires taxpayers to “retain records in a sufficiently usable form and detail to substantiate that the expenditures claimed are eligible for the credit”.17
Recent IRS guidance for refund claims mandates the identification of all business components, a description of the research activities performed for each component, and the total qualified employee wage, supply, and contract research expenses.8 Project Accounting directly supports this requirement by generating system-logged, dated records. The reliance on retrospective, vague, or unsupported statements to substantiate R&D time allocation or expense linkages may result in the denial of the credit.19 The auditor must be able to clearly and easily trace the expense back to the qualifying activity.21 Therefore, Project Accounting serves to shift the substantiation burden away from fallible memory and onto reliable, dated system logs, making the information transparent and easily auditable.
Section 4: Operationalizing Project Accounting: QRE Tracking and Substantiation (Example)
Project Accounting is operationalized by integrating tracking tools that focus on the three QRE categories, ensuring the contemporaneous capture of data.
4.1 QRE Example 1: Tracking Qualified Wages and Time Allocation
Employee wages typically constitute the largest category of QREs.14 Eligibility is determined strictly by the qualified services actually performed by an employee—engaging in research, direct supervision, or direct support—regardless of their job title.13 Accurate, contemporaneous time allocation is paramount.
#### Project Accounting Implementation for Wages
Project Accounting requires utilizing integrated time-tracking software that directly links labor hours to specific R&D project codes (business components).16 This approach ensures that the total compensation for an employee can be precisely allocated between qualified and non-qualified activities.
For instance, consider a software developer at a technology firm working on a new security feature (the business component). The developer spends 80% of their time writing code and conducting systematic testing to resolve a technical uncertainty regarding performance (a QRA). The remaining 20% of their time is spent attending sales meetings and developing marketing collateral (Non-QRA). Project Accounting mandates the use of time-tracking software where the developer logs hours specifically against the R&D project code for the security feature. The system then automatically applies the employee’s unique hourly labor rate to the logged time, accumulating auditable labor costs for that specific project.22 Non-qualifying activities, such as administrative tasks, general janitorial services, or accounting for non-research expenses, must be strictly excluded from the QRE total.13
#### The Substantially All Rule and Case Law Precedent
For direct supervisors and direct support personnel, the “Substantially All” Rule (IRC §41(b)(2)(B)) applies: if substantially all (generally interpreted as 80% or more) of the services performed by an individual during the taxable year consist of qualified research services, then all their wages may qualify.23 Project Accounting time-tracking reports provide the objective data necessary to prove this 80% threshold for supervisory personnel, substantiating the time dedicated to supervision of QRAs.25
Case law provides critical context for the necessity of this detailed tracking. In Fudim, T.C. Memo. 1994-235, the Tax Court emphasized that time allocations based on unsupported statements or estimates are insufficient for substantiation.26 The taxpayer failed to produce corroborative records to prove involvement in research activities.27 A robust PA system, therefore, provides the necessary corroborative records—approved digital timesheets, technical activity notes, and associated labor costs—to defend against IRS challenges regarding arbitrary allocations.
The following table summarizes the necessity of Project Accounting documentation for the wage QRE component:
Table 1: Project Accounting for Employee Wages (QRE Substantiation)
| Employee Category | Documentation Mandate | PA System Functionality | Audit Defense Value |
| Direct Researcher | Track actual time spent on QRAs (not job title).13 | Dedicated project codes in time-tracking software; detailed notes on activities.16 | Proves the quantitative allocation of labor costs and the qualitative activity performed.19 |
| Direct Supervisor | Prove time dedicated to direct supervision of QRAs (Substantially All Rule).23 | Timesheet allocation linked to the supervised R&D project codes.25 | Substantiates the percentage allocation, mitigating the risk of arbitrary estimates.27 |
| Direct Support | Prove services directly support QRAs (e.g., lab maintenance specific to research).14 | Allocation records ensuring non-qualifying support (e.g., G&A accounting) is excluded.13 | Isolates and justifies support costs that are often challenged by auditors as general overhead.10 |
4.2 QRE Example 2: Tracking Qualified Supplies and Contract Research Expenses
The precision required for QREs extends beyond wages to materials and external costs.
Supplies: Supply QREs must be tangible properties directly used and consumed in the conduct of qualified research, such as raw materials used to fabricate and test prototypes.10 Project Accounting requires businesses to retain invoices showing the purchase of these specific materials and, crucially, linking them directly to the R&D project ID. Expense records must be systematically managed to separate non-qualifying items, such as capitalized equipment or general office supplies, from consumable supplies.18
Contract Research Expenses (CRE): Payments to third parties for qualified research are subject to the 65% limitation.13 To substantiate this expense, Project Accounting mandates that the contracts and invoices for these third-party R&D services be coded to the specific R&D project (business component). The required documentation includes the agreements, purchase orders, and invoices that verify the amounts paid and confirm the research scope, enabling the taxpayer to calculate and defend the 65% claim.13
Section 5: Project Accounting Systems Integration for Seamless Compliance
5.1 Chart of Accounts (COA) Strategy and Financial Coding
Effective R&D compliance must be anchored by a structured General Ledger (GL) and Chart of Accounts (COA). The COA structure serves as the final compliance gatekeeper, ensuring that the financial data presented to the IRS is correctly segregated and limited to eligible amounts.
A proactive strategy requires establishing unique, high-level expense accounts specifically for R&D (e.g., R&D Wages, R&D Supplies, R&D Contract Research).16 Furthermore, a dimensional accounting approach must be employed, utilizing project tracking, sub-account tags, or specialized cost centers within the GL to link transactions directly to the specific Business Component/Project ID.16 This methodical coding ensures that all costs are identifiable and retrievable, thereby reinforcing internal control over the claim.30
The implementation of a formal R&D expense approval process is essential. This workflow dictates that a manager or technical lead must verify that a supply purchase invoice or contract expense is genuinely related to an approved R&D project before the transaction is posted with the R&D GL code.16 This control prevents ineligible expenditures from being inadvertently classified as QREs.
5.2 Technology Solutions for Contemporaneous Data Capture
Robust R&D credit defense relies on the seamless integration of operational and financial technology, ensuring that data is captured and transparently linked. The IRS is increasingly utilizing technology to examine complex claims, making high data transparency a significant factor in mitigating audit exposure.31
Modern R&D-compliant Project Accounting often involves integrating three core systems: project management tools (e.g., Jira, GitHub), dedicated time tracking software (e.g., My Hours, ClickTime), and the enterprise’s General Ledger (ERP/Accounting Software).16 This integrated approach allows for the automatic or semi-automatic capture of contemporaneous data, minimizing manual data entry and human error.28
Key features of these integrated technology solutions that support Project Accounting include:
- Project Coding: The ability to set up unique project codes for R&D activities and establish tasks or sub-categories (e.g., “prototype development”) against which employees log hours.16
- Cost Calculation: Automatic calculation of accumulated labor costs by applying unique hourly labor rates to tracked time.22
- Qualitative Capture: Tools that allow users to add specific notes or fields describing the technical activities, directly addressing the qualitative requirements of the four-part test.28
- Audit Readiness: Comprehensive reporting and audit logs that compile labor hours, supply costs, and project narratives into a single, defensible package.22
By implementing these systems, the taxpayer gains access to high-transparency data generated seamlessly and consistently, which avoids the significant disruption and heightened scrutiny caused by having to manually reconstruct complex cost allocations during an audit.28
Section 6: Next Steps: Advanced Clarification and Full Implementation Strategy
To further clarify Project Accounting and ensure its utilization fully maximizes R&D tax credit compliance and minimizes audit risk, a multi-faceted implementation strategy focused on cultural, procedural, and expert validation is necessary.
6.1 Developing an “Always On” R&D Documentation Culture
The most effective method for establishing a defensible claim is to institutionalize Project Accounting processes, moving away from retrospective, annual data gathering.
Establish a Formal Cadence: A successful approach involves instituting a regular, recurring “R&D housekeeping” schedule, such as a monthly cadence.32 During this time, technical staff must finalize timesheets, technical leads must approve them, and the finance team must pull payroll and accounts payable data exports to update the cost list. This routine upkeep, rather than a year-end scramble, ensures continuous data integrity and completeness.20
Integrate into Workflow: R&D record-keeping should be incorporated into existing operational processes (e.g., project management software, standard expense reports).20 This makes the logging of time and expenses easy and reduces resistance from busy technical teams. Furthermore, regular team meetings should include a brief agenda point on R&D activity reporting to ensure contributions are logged promptly.20
6.2 Internal Training and Communication
R&D compliance requires bridging the gap between technical operations and financial requirements. This is achieved through targeted internal training.
Technical and Process Training: Employees involved in R&D must be trained on the specifics of the four-part test, with emphasis on identifying and documenting the technical “uncertainty” and the “process of experimentation”.17 Furthermore, staff must be trained on the proper use of the Project Accounting systems, emphasizing that detailed, contemporaneous logs are required not just for productivity tracking, but specifically for tax substantiation.25
Documentation Detail: Technical personnel must understand that their qualitative notes—such as the specific information they sought to discover and the details of project failures or test outcomes—are essential evidence.8 Vague or generic descriptions risk being challenged by an auditor, so training should focus on clear, specific articulations of the research performed.21
6.3 Engaging Specialized Tax Expertise and Methodology Validation
While internal systems provide the data, expert validation ensures the methodology is compliant and optimized.
Methodology Review and Validation: Taxpayers should consult R&D tax specialists to review the entire Project Accounting framework, from the initial Chart of Accounts setup to the final data allocation methodology.16 This review ensures the system aligns with current IRS Audit Technique Guides and recent legal standards regarding substantiation, such as the application of complex rules like the “substantially all” requirement.23
Proactive Audit Defense: Rather than waiting for potential IRS examination, forward-thinking companies prepare for potential audit from the outset.4 Specialists help establish a proactive defense by ensuring that the documentation package—which links the PA data (cost) to the technical data (activity)—is robust, project-specific, and immediately available to withstand scrutiny, streamlining the examination process and protecting the claimed credits.19
Table 2 provides a strategic roadmap for establishing and maintaining a robust, R&D-compliant Project Accounting system:
Table 2: Roadmap for Establishing R&D-Compliant Project Accounting Systems
| Phase | Action Item | Strategic Goal | Compliance Outcome |
| I. Identification & Baseline | Define all “Business Components” and map their corresponding QRAs. | Establish the fundamental unit of eligibility for cost tracking.7 | Master list of R&D projects meeting the Four-Part Test.17 |
| II. System Integration & Setup | Integrate time tracking software with project management tools and payroll/GL systems. | Ensure contemporaneous and auditable nexus for labor (the largest QRE).14 | Detailed, approved employee timesheets linked to wages and project IDs.28 |
| III. Financial Governance (COA) | Create distinct General Ledger (GL) codes for QRE categories (Wages, Supplies, Contract Research). | Segregate R&D costs immediately from ineligible operational expenditures.4 | Accurate and defensible QRE totals for Form 6765 calculation.8 |
| IV. Compliance Cadence | Establish monthly or quarterly R&D “housekeeping” reviews and management approvals. | Minimize retrospective reconstruction risk and guarantee data completeness.20 | Ongoing project logs, timely expense approvals, and continuous data integrity.19 |
Conclusion: Project Accounting as a Risk Management Tool
Project Accounting represents far more than an operational efficiency measure; it is the foundational infrastructure for compliance necessary to meet the demanding substantiation standards of the U.S. R&D Tax Credit under IRC Section 41. By capturing and associating all expenditures—wages, supplies, and contract research costs—with the discrete, defined business component, Project Accounting ensures the continuous establishment of the critical “nexus” favored by the IRS.5 This methodology proactively prevents the high audit risks associated with arbitrary allocations and aggregated cost center reporting.5 For financial leadership, the implementation of an integrated, “always on” Project Accounting system is the essential strategy for moving from reactive audit defense to the proactive, auditable maximization of this valuable tax incentive.
Are you eligible?
Why choose us?
Pass an Audit?
What is the R&D Tax Credit?
The Research & Experimentation Tax Credit (or R&D Tax Credit), is a general business tax credit under Internal Revenue Code section 41 for companies that incur research and development (R&D) costs in the United States. The credits are a tax incentive for performing qualified research in the United States, resulting in a credit to a tax return. For the first three years of R&D claims, 6% of the total qualified research expenses (QRE) form the gross credit. In the 4th year of claims and beyond, a base amount is calculated, and an adjusted expense line is multiplied times 14%. Click here to learn more.
Never miss a deadline again
Stay up to date on IRS processes
Discover R&D in your industry
R&D Tax Credit Preparation Services
Swanson Reed is one of the only companies in the United States to exclusively focus on R&D tax credit preparation. Swanson Reed provides state and federal R&D tax credit preparation and audit services to all 50 states.
If you have any questions or need further assistance, please call or email our CEO, Damian Smyth on (800) 986-4725.
Feel free to book a quick teleconference with one of our national R&D tax credit specialists at a time that is convenient for you.
R&D Tax Credit Audit Advisory Services
creditARMOR is a sophisticated R&D tax credit insurance and AI-driven risk management platform. It mitigates audit exposure by covering defense expenses, including CPA, tax attorney, and specialist consultant fees—delivering robust, compliant support for R&D credit claims. Click here for more information about R&D tax credit management and implementation.
Our Fees
Swanson Reed offers R&D tax credit preparation and audit services at our hourly rates of between $195 – $395 per hour. We are also able offer fixed fees and success fees in special circumstances. Learn more at https://www.swansonreed.com/about-us/research-tax-credit-consulting/our-fees/
Choose your state
