Title Tag: Arizona R&D Tax Credit for Software Companies | KR Taxes

Meta Description: Arizona's R&D tax credit can refund up to 24% of qualified software dev costs. See who qualifies, how to claim it, and common mistakes.

Target Keyword: r&d tax credit arizona software companies

Software development doesn't automatically qualify for Arizona's R&D tax credit just because it's technical work. The credit follows federal rules that treat software you build to sell very differently from software you build to run your own business, and that single distinction determines whether a development team's salaries generate a real tax credit or nothing at all. This guide covers how the Arizona credit works, the software-specific test most companies get wrong, and how to actually claim it.

Key Takeaways

• Arizona's R&D credit is 24% of the first $2.5 million in qualifying research expenses, plus 15% of any amount above that, for tax years beginning before 2031.
• Software built for sale, lease, or license to customers gets evaluated under the standard four-part test. Software built for your own internal operations faces a much harder, additional test.
• Qualifying small businesses can get part of the credit refunded in cash, even with no tax liability to offset, but only if they apply for certification before filing.
• The credit is claimed on Arizona Form 308 or 308-I, and it can be carried forward for 10 years if you don't use it all right away.
• Routine maintenance, bug fixes, and configuration work generally don't qualify, even when performed by engineers.

How Arizona's R&D credit works

Arizona's credit for increased research activities piggybacks on the federal research credit framework. Under A.R.S. § 43-1168, the credit amount is determined under the same methodology as the federal credit in IRC Section 41, with Arizona-specific rate and threshold modifications layered on top. For tax years beginning before December 31, 2030, the credit equals 24% of the first $2.5 million in qualified research expenses above your base amount, plus 15% of anything above $2.5 million. According to the Arizona Commerce Authority's own program guidelines, those rates drop to 20% and 11% respectively for tax years beginning in 2031 and later.

Because Arizona borrows the federal definition of qualified research, the same rules that federal auditors apply to a Silicon Valley SaaS company apply to an Arizona software business claiming this credit, which is exactly where the software-specific complications start.

The test that decides everything: is your software "internal use"?

Every research activity, software or otherwise, first has to clear the federal four-part test described in IRC Section 41(d): it has to relate to a permitted purpose (developing or improving a business component), be technological in nature, aim to eliminate a genuine technical uncertainty, and involve a process of experimentation, such as systematic trial and error or modeling. According to the IRS's own audit guidance on the research credit, a business component for software purposes includes any computer software held for sale, lease, or license, or used in the taxpayer's own trade or business.

That last phrase is where software companies split into two very different situations:

If you're building software to sell, license, or lease to customers (the standard SaaS or commercial software case), your development work is evaluated under the ordinary four-part test, the same as any other qualified research.

If you're building software primarily for your own internal operations, things get harder. Software developed mainly for general and administrative functions, financial management, HR management, or internal support functions, has to clear an additional three-part "high threshold of innovation" test on top of the four-part test. Per the actual Treasury regulation governing this exclusion, internal-use software only qualifies if it's innovative in a substantial, economically significant way; involves significant economic risk, meaning the company committed substantial resources with real technical uncertainty about recovering that investment within a reasonable time; and isn't commercially available in a form that could be bought, leased, or licensed without the same kind of custom modification.

This is the single most common way software companies either overclaim or underclaim this credit. A company building custom internal tooling, an internal analytics dashboard, or a proprietary back-office system needs to specifically document how it clears the higher bar, not just the standard four-part test, or the claim is vulnerable on audit.

What about software that's part internal, part customer-facing?

Plenty of real products don't fall cleanly into either category. A platform that has customer-facing features and an internal admin backend, for instance, is treated as "dual-function" software. The regulation presumes dual-function software is primarily for internal use unless you can identify and separate out the third-party-facing portion. If you can't cleanly separate it, there's a safe harbor: when third-party use is reasonably anticipated to be at least 10% of the software's total use, you can include 25% of that dual-function software's qualifying expenses in your credit calculation without having to clear the high threshold of innovation test at all. Getting this allocation right, and documenting the basis for it at the time of development rather than after the fact, is usually the difference between a credit that survives an audit and one that doesn't.

What definitely doesn't qualify

Regardless of internal-use status, some software-adjacent work is excluded from the credit outright: research conducted after the software reaches commercial production, routine data collection, quality assurance and testing that doesn't involve resolving genuine technical uncertainty, adapting an existing product to a specific customer's requirements without new experimentation, and reverse-engineering or duplicating an existing product. A development team can log real hours on all of these activities and still generate zero qualifying research expense for the credit.

The refundable option for smaller software companies

This is often the most valuable part of the credit for early-stage software companies that don't yet owe much in state income tax. A business with fewer than 150 full-time employees worldwide can apply to the Arizona Commerce Authority for a refund of 75% of the credit that exceeds its current-year tax liability, paid in cash even if the company owes little or nothing in state tax that year. The refund is capped at $100,000 per taxpayer per year, and the ACA can approve a limited pool of these refunds statewide each calendar year, so timing matters. Critically, the ACA Certificate of Qualification has to be obtained before you file the return claiming the credit, not after; a business that files first and tries to apply for the refund afterward has already lost that option for the year.

How to actually claim the credit

Corporations and partnerships claim the credit on Arizona Form 308, while individual taxpayers, including owners of pass-through entities, use Form 308-I. Any credit that isn't used to offset the current year's tax liability, and isn't refunded under the small-business program, can be carried forward for 10 consecutive tax years for credits generated in tax years beginning after December 31, 2021. How the credit flows through, directly to the entity or out to individual owners, is worth confirming as part of your broader entity structure planning, especially for S corporations that can elect to keep the credit at the corporate level or pass it through to shareholders. Businesses that also make qualifying research payments to Arizona State University, Northern Arizona University, or the University of Arizona may be eligible for the additional University R&D tax credit, worth 10% of qualifying basic research payments on top of the general credit.

Getting your software R&D claim right the first time

The mechanics of Arizona's credit are straightforward once you understand them, but the software-specific rules around internal-use development are where most claims either leave money on the table or create real audit exposure. Getting the internal-use analysis right at the time the work is done, not reconstructed a year later when a return is due, is what makes the difference.

Talk to K&R about whether your software development qualifies for the Arizona R&D credit, and whether the refundable option makes sense for your stage of business. Our accounting team can also help set up the kind of contemporaneous project tracking that holds up if ADOR or the IRS ever asks for documentation. Book a consultation or learn more about our firm to get started.

Frequently asked questions

Does software development qualify for the Arizona R&D tax credit? It can, but the analysis depends heavily on what the software is for. Software built for sale, lease, or license to customers is evaluated under the standard four-part research test. Software built primarily for your own internal operations has to clear an additional, harder test focused on genuine innovation, significant economic risk, and the absence of a comparable commercial alternative.

What's the difference between the four-part test and the high threshold of innovation test? The four-part test applies to all research activities and asks whether the work had a permitted purpose, was technological in nature, aimed to eliminate uncertainty, and involved a process of experimentation. Internal-use software has to clear that test plus a separate three-part test proving the software was genuinely innovative, involved real financial risk in development, and wasn't already available commercially.

Can a startup with no tax liability still benefit from this credit? Yes. Qualifying small businesses with fewer than 150 full-time employees worldwide can apply to the Arizona Commerce Authority for a refund of 75% of the credit that exceeds their tax liability, subject to a $100,000 per-taxpayer cap, but the certificate of qualification must be obtained before the tax return is filed.

How long can I carry forward an unused R&D credit in Arizona? Credits generated in tax years beginning after December 31, 2021 can be carried forward for 10 consecutive tax years if not used to offset current-year liability or claimed as part of the refundable program.

Do bug fixes and routine software maintenance qualify for the credit? Generally no. Routine debugging, configuration, quality assurance testing that doesn't resolve genuine technical uncertainty, and adapting existing software to a specific customer's needs without new experimentation are excluded, even when performed by engineering staff.

Which form do I use to claim Arizona's R&D tax credit? Corporations and partnerships use Arizona Form 308. Individual taxpayers, including owners of pass-through entities claiming the credit on their personal return, use Form 308-I.