Navigating the Exclusion: Internal-Use Software Qualification for the Illinois R&D Tax Credit

Executive Summary: The Core of the IUS Exclusion

Research expenditures for computer software intended primarily for a taxpayer’s internal general and administrative functions are generally ineligible for the Illinois R&D credit. This exclusion is waived only if the software development successfully meets the stringent three-part High Threshold of Innovation test.

The Illinois Research and Development (R&D) Tax Credit (Credit Code 5340), mirroring federal provisions under Internal Revenue Code (IRC) Section 41, places a strict limitation on qualifying research related to computer software developed primarily for a taxpayer’s internal operations, commonly referred to as Internal-Use Software (IUS).1 Companies in specialized sectors such as financial services, insurance, and large retail—which often maintain extensive internal IT departments—face this exclusion directly when attempting to claim the state’s tax incentive for developing sophisticated back-office or administrative systems.2 Successfully navigating this exclusion requires proving that the development meets a “high threshold of innovation” (HTI) test, demanding meticulous project classification and robust documentation that substantiates both technical uncertainty and significant economic commitment from the project’s inception.1

Section 1: Context and Statutory Foundation of the Illinois R&D Tax Credit

1.1. Overview of the Illinois R&D Credit Structure and Mechanics

The Illinois Research and Development Credit is a crucial non-refundable state incentive designed to encourage innovation within the state.4 This credit is available to Corporations and Flow-through entities, including partnerships and S corporations, with the credit flowing through to the owners in the latter case.4

The credit is calculated as 6.5% of the taxpayer’s Qualified Research Expenditures (QREs) for research activities performed within Illinois.4 However, this percentage is applied not to the total QREs, but to the incremental increase in QREs over a defined base amount.5 The base amount is calculated as the average of the QREs incurred during the three taxable years immediately preceding the current tax year.7 This incremental structure means that companies with stable or decreasing QREs may realize minimal benefit, while growing companies or startups (which often have a zero base amount) can qualify a larger proportion of their current expenses.5

The credit, claimed using Schedule 1299-D (for corporations and fiduciaries) or Schedule 1299-A/C (for pass-through entities and individuals), provides a non-refundable offset against corporate income tax liability.4 Unused portions of the credit may be carried forward for up to five years.4 Recent legislation has ensured the longevity of this incentive, with Public Act 103-0595 extending the Research and Development tax credit until tax years ending on or before December 31, 2031.9

1.2. Reliance on Federal Definitions and the Exclusion Mandate

A critical aspect of the Illinois R&D credit is its comprehensive reliance on federal tax law definitions. Qualified research is defined by referencing IRC Sections 41(d) and 41(e).7 This incorporation means that activities must first satisfy the federal four-part test for qualified research, which requires proving activities were intended to develop or improve a product, process, technique, or software, and involved a systematic process of experimentation aimed at eliminating technical uncertainty.4

Furthermore, the Illinois Department of Revenue (IDOR) administrative rules and tax form instructions explicitly incorporate the list of federal exclusions from qualified research.8 Among the excluded activities are research conducted after the beginning of commercial production, surveys or studies, research conducted outside Illinois, and—most relevantly—research relating to certain internal-use computer software.8 This statutory adoption of federal exclusions establishes the necessity of applying the rigorous federal regulations governing IUS to claims for the Illinois R&D credit.

Section 2: Defining and Categorizing Internal-Use Software (IUS)

Accurate classification of software development activities is the primary determinant of whether the stringent HTI test must be applied. Misclassification is a common compliance risk.

2.1. The Scope of “Internal Use”: General and Administrative Functions

Internal-use software is defined as software developed primarily for the taxpayer’s use in general and administrative (G&A) functions that support or facilitate the trade or business.3 The final regulations categorize these functions into three broad areas 12:

• Financial Management Functions: These include activities essential for financial control and record-keeping, such as accounts payable, accounts receivable, budgeting, financial reporting, tax systems, and inventory management (when the software is used purely for internal tracking).12
• Human Resource Management Functions: These encompass all activities related to managing the workforce, including hiring, training, payroll processing, and benefits administration.12
• Support Services Functions: This category covers activities that support the daily operations, such as facility management, security services, data processing, and, critically, marketing.12

Companies must document their intent and the facts and circumstances surrounding the software development at its inception to determine if it falls under these G&A categories.3

2.2. The Critical Distinction: The Third-Party Exception

The IUS exclusion does not apply to software developed primarily for external customers or third parties. Software developed to enable a third party (the customer) to interact directly with the taxpayer’s business systems is generally exempted from the IUS exclusion and is only subject to the standard four-part test.3

• Non-IUS Qualification: Software is not considered IUS if it is developed to allow customers to initiate functions (e.g., placing orders, scheduling appointments) or access data (e.g., tracking a shipment, reviewing account history) on the taxpayer’s system.3 The expansion of this exception to cover customer-facing SaaS platforms and websites has significantly eased R&D credit qualification for e-commerce and digital service providers since the final regulations were issued.14
• The Marketing Trap: A common misclassification involves marketing software. If a web application merely displays information—such as product catalogs, pricing, office hours, and directions—but does not allow the potential customer to initiate a transaction or communicate directly, it is classified as a G&A support service (IUS). The regulations deem any benefit provided to third parties by such pure marketing functions to be collateral and secondary, meaning the HTI test is still required.13
• Vendor and Supplier Exclusion: A nuanced element of the definition is the exclusion of vendors and suppliers from the term “third parties”.13 If a manufacturing company develops a sophisticated web application that allows its vendors to access the company’s inventory management system to track product levels and initiate automated replenishment orders, the application is still classified as IUS. Because the recipient (the vendor) is not a customer, the high threshold of innovation test must be satisfied to qualify for the credit.13

Section 3: The High Threshold of Innovation (HTI) Test

If a project is classified as Internal-Use Software, it must pass a three-part High Threshold of Innovation (HTI) test, in addition to the standard four-part test, for its development costs to be eligible for the Illinois R&D credit.1

3.1. Prerequisite: Satisfying the Standard Qualified Research Activities (QRA) Test

Before the HTI is even considered, the IUS development must meet the foundational requirements for qualified research under IRC §41. This requires demonstrating that the activity was: for a permitted purpose (new or improved performance); intended to eliminate technical uncertainty; involved a process of experimentation (e.g., modeling, simulation, or trial-and-error methodology); and was technological in nature.4

3.2. Requirement 1: Innovative

The first requirement demands that the anticipated outcome of the software development be truly transformative.1

• Standard Definition: The software must be intended to be innovative, resulting in a reduction in cost, an improvement in speed, or some other measurable improvement that is both substantial and economically significant if the development is successful.12
• Substantiality: Simple incremental improvements or routine efficiency gains, such as those achieved by adopting industry best practices or minor configuration changes, are insufficient. The expected improvement must represent a paradigm shift in the G&A function’s capability.14 This measurable improvement provides the necessary financial justification for Requirement 2, as a substantial expected return helps validate the commitment of substantial resources and the recovery of risk capital within a reasonable period.15

3.3. Requirement 2: Significant Economic Risk

This requirement is typically the most difficult to substantiate and document, necessitating a clear focus on technical, rather than commercial, risk.14

• Standard Definition: The development must involve significant economic risk. This is established if the taxpayer commits substantial resources to the project and, due to technical risk, there is substantial uncertainty that those committed resources would be recovered within a reasonable period.15
• Technical Uncertainty: The uncertainty must be technical in nature, concerning the capability or methodology of the design or development. Uncertainty related to market adoption, financial funding, or internal reorganization does not qualify.15 For software, this often involves the inability to determine the appropriate design or methodology required to achieve the desired substantial improvement at the project’s start.10
• Documentation Necessity: Companies must document the substantial resources committed and the specific technical problems encountered. This is particularly crucial since the tax definition of economic risk for R&D credit purposes is distinct from financial accounting standards (like ASC 730), which generally do not include specialized requirements such as the HTI test.17

3.4. Requirement 3: Not Commercially Available

The taxpayer must prove that the development activity was essential because no off-the-shelf solution existed that could fulfill the business need.

• Standard Definition: The software cannot be purchased, leased, or licensed and used for the intended purpose without modifications that would, themselves, satisfy the Innovation and Significant Economic Risk requirements.15
• Avoiding the Purchase Trap: This means that simply purchasing a commercial Enterprise Resource Planning (ERP) system and configuring it for a company’s standard operations does not qualify. If a company must develop a unique, high-risk, technically uncertain component to bolt onto a commercial system to achieve the substantial, innovative improvement, only the costs associated with the development of that specific, novel component may be eligible for the credit.15

Section 4: Illinois Department of Revenue (IDOR) Guidance and Compliance

While Illinois relies on federal definitions for the technical rules, the Illinois Department of Revenue (IDOR) issues guidance regarding the administration, calculation, and documentation of the credit specific to state law.

4.1. IDOR Administrative Rules and Calculation

The Illinois R&D credit, governed by 35 ILCS 5/201(k) and detailed in 86 Ill. Adm. Code 100.2160, reinforces the incremental calculation method.8 The base period is defined as the three taxable years immediately preceding the current year.18 Special rules address situations where a taxpayer was only conducting business in Illinois for part of a base period year, requiring proration of qualifying expenditures.18

The IDOR’s guidance, published in the instructions for Schedule 1299-D, clearly states the exclusion for “research relating to certain internal-use computer software,” making the HTI test a non-negotiable compliance requirement for affected activities.8

4.2. Geographic Nexus and Qualified Research Expenses (QREs)

The Illinois credit is only available for QREs that are attributable to research activities performed within Illinois.4 This mandates careful geographic tracking of costs. QREs typically include wages for qualified services, the cost of supplies used in the research, contract research expenses, and rental or lease costs of computers used directly in the R&D activity.8

This requirement poses a critical documentation challenge, especially for modern, remote-based software development teams. Taxpayers must be able to allocate wages and computer lease costs specifically to the portion of qualified research physically conducted by personnel within Illinois.8

4.3. State Audit Focus and Documentation Rigor

IDOR auditors have noted recurring issues with the substantiation of income tax credits, including R&D claims.19 The primary vulnerability is the failure to maintain records sufficient to verify the expenditures and activities claimed.19

For R&D claims, the lack of detail in documenting wage expenses is a known problem.8 Although materials and facilities costs might be easily traceable, wage expenses require precise support. Companies must detail how much time each employee spent compiling data and conducting activities directly related to the HTI-qualifying research.8 The expectation is that companies establish clear cost centers or time-tracking logs that capture the basis of the credit, ensuring that non-qualified activities (e.g., maintenance, training) are segregated from the qualified research time associated with the innovative software development.8

Section 5: Case Studies and Practical Application of the HTI Test

The practical application of the IUS exclusion dictates that two identical projects—in terms of cost and complexity—may have vastly different eligibility outcomes based solely on the user profile (customer vs. vendor) and the level of technical risk.

5.1. Example: Development of a Proprietary Logistics Optimization System (IUS Qualifying for HTI)

Scenario: A large Illinois-based retailer (RetailCo) commits significant resources to developing a new, in-house Warehouse Management System (WMS). This WMS is designed to automate and optimize the scheduling and routing of internal inventory movements using a machine learning model that predicts stocking needs based on volatile real-time variables (weather, external traffic data, unexpected promotions). No commercially available WMS offers this predictive capability with the necessary real-time processing speed, requiring RetailCo to invent novel algorithms to achieve a guaranteed 40% reduction in fulfillment errors, a highly substantial and economically significant target.12

HTI Analysis:

1. Classification: Warehouse management is generally a G&A support service function, thus classifying the WMS as IUS.2 HTI is mandatory.
2. Innovative: Yes. The 40% error reduction is a substantial and economically significant improvement over existing systems, meeting the first prong.12
3. Significant Economic Risk: Yes. The commitment of substantial resources to developing and testing the novel machine learning algorithms represents significant technical uncertainty regarding the feasibility of the proposed speed and accuracy requirements.15 The potential non-recovery of resources due to technical failure substantiates the economic risk.
4. Not Commercially Available: Yes. The core innovation—the machine learning engine—cannot be purchased. The retailer must demonstrate that standard WMS software, even with extensive configuration, could not meet the novel speed and accuracy requirements without creating modifications that satisfy the HTI test themselves.15

Conclusion: The QREs associated with the research and development of the core proprietary algorithms and modules qualify for the Illinois R&D credit.

5.2. Example: Customizing an Enterprise Resource Planning (ERP) System (IUS Failing HTI)

Scenario: A financial services company in Illinois (FinCorp) spends $5 million and two years customizing a standard, licensed ERP system to handle its internal accounts payable, tax reporting, and budgeting functions. The goal is to achieve industry-standard compliance and improve processing speed by 5%. The project involves standard coding practices to integrate the ERP with existing legacy databases, a technically complex but standard integration challenge.

HTI Analysis:

1. Classification: Accounts payable and tax reporting are financial management functions, classifying the customization as IUS.13 HTI is mandatory.
2. Innovative: No. A 5% speed improvement, while beneficial, is unlikely to meet the standard of being substantial and economically significant required by the regulations.14 Furthermore, achieving industry-standard compliance is a routine business goal, not an innovation.
3. Significant Economic Risk: No. The project involves integration complexity and budget risk, but not fundamental technical uncertainty regarding capability or methodology that cannot be resolved by experienced IT staff using known computer science principles.15
4. Not Commercially Available: No. The foundation of the system was licensed and purchased. The modifications, involving standard data integration and configuration, do not meet the innovation or economic risk prongs on their own.

Conclusion: The customization costs are excluded from the R&D credit calculation because the project fails to meet the High Threshold of Innovation.

Section 6: Documentation and Risk Mitigation Strategies

Successfully claiming the R&D credit for IUS expenditures requires stringent, proactive documentation that goes beyond standard financial records, focusing on technical substance to mitigate state and federal audit risk.

6.1. Establishing Contemporaneous Evidence of Intent and Uncertainty

The intent of the taxpayer at the beginning of development is the determinative factor for IUS classification.3 Documentation must capture the technical justification for the development process.

• Risk Evaluation and Requirements Documentation: Companies claiming the HTI exception must develop and maintain initial project documents, such as technical requirements surveys, risk identification and mitigation plans, and critical design review memoranda.21 These artifacts must clearly articulate the inherent technical risks encountered and the specific process of experimentation used to eliminate the uncertainty, such as modeling, simulation, or systematic trial-and-error.10
• Proof of Unavailability: To satisfy the Not Commercially Available prong, documentation should include market research, vendor proposals, and detailed technical specifications proving that commercial products could not fulfill the intended purpose without HTI-level modifications.15

6.2. Granular Time Tracking for Illinois QREs

The necessity of accurately capturing qualified research expenses performed within Illinois requires meticulous detail, especially concerning labor costs.8

• Detailed Time Logs: The strongest defense against an IDOR audit is contemporaneous time tracking logs that specify the time spent by each employee on qualified R&D tasks (e.g., designing the novel algorithm, performing simulations for the process of experimentation) versus non-qualified activities (e.g., management, administration, maintenance, testing that does not resolve technical uncertainty).8
• Computer Lease Allocation: Since computer rental and lease costs can be eligible QREs, documentation must connect these expenses directly to the qualified research activity, often through usage logs and invoices that align with the R&D periods.8 This allocation must also adhere to the “in Illinois” geographic requirement.

6.3. The Importance of Technical Testimony and Documentation Synthesis

An R&D credit audit demands a synthesis of financial records and technical narratives.20 Technical documentation—such as architecture documents, rapid development risk evaluations, and iteration plans—is essential for substantiating that the project involved genuine technical uncertainty and a systematic process.21 Furthermore, technical leaders must be prepared to provide oral testimony, supported by these documents, explaining the technical hurdles that established the Significant Economic Risk component of the HTI test.20 This level of documentation is critical to avoid potential audit adjustments, which the IDOR is known to impose when substantiation is lacking.8

Conclusion

The Illinois R&D tax credit offers substantial savings through its 6.5% incremental calculation mechanism, but only for activities that meet rigorous federal standards. For companies developing software for general and administrative functions, the application of the Internal-Use Software exclusion acts as a crucial barrier. To overcome this default exclusion, the research must satisfy the three-part High Threshold of Innovation test: the software must be innovative, involve significant economic risk, and not be commercially available without requiring HTI-level modification.

Successfully claiming this credit demands integration of tax compliance into the development life cycle. Companies must strategically classify software components (IUS vs. non-IUS) at project initiation and maintain contemporaneous documentation that substantiates the technical uncertainty and substantial economic commitment required by the HTI test. Furthermore, due to explicit IDOR audit scrutiny, meticulous geographic allocation and granular time tracking of qualified wages in Illinois are essential for maximizing the credit and mitigating audit exposure. Through this proactive and technically rigorous approach, Illinois taxpayers can responsibly leverage the state’s extended R&D incentive for their complex internal technological advancements through 2031.

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/