Cazes LawBLG | Business Law Group 405.254.5005

Oklahoma software and cybersecurity employee credit: 7 facts

Cazes Law Editorial · · 9 min read

Oklahoma's software and cybersecurity employee credit is unusual among state incentives. The company doesn't get a dime. The worker claims it on an individual income tax return, $2,200 or $1,800 a year, for up to seven years.

And yet every gate to that credit is an employer-side fact: headcount, industry code, pay level, and the date the person started work in Oklahoma. In our experience that split is where employers, recruits, and their CPAs get tangled. Here are seven points worth getting straight, drawn from the Tax Commission's rule at OAC 710:50-15-117, Form 566, Form 511-CR, and the Incentive Evaluation Commission's final evaluation dated December 2, 2025.

1. The software and cybersecurity employee credit belongs to the employee

The rule describes a credit that a qualified software or cybersecurity employee may claim against Oklahoma income tax imposed under 68 O.S. § 2355. That's the individual income tax. Nothing lands on the employer's return.

Form 566 confirms the mechanic. The header asks for the name as shown on the return and the claimant's Social Security number. Part 3 computes the credit for the year, and the result carries to Form 511-CR, where line 5 of the 2025 form reads Credit for Qualified Software or Cybersecurity Employees, with Form 566 enclosed.

So why should an owner or HR director care about a credit that never touches the company's books? Three reasons we see repeatedly. The credit is a recruiting fact you can put in an offer letter, if the facts are true. The employee will come to payroll asking for information only the employer has. And whether the employee qualifies at all turns on whether the company is a qualified employer, which is the employer's problem to prove.

2. The dollar amounts are fixed, and the credit is nonrefundable

The rule sets $2,200 per year for an employee holding a bachelor's degree or higher from an accredited program, and $1,800 per year for an associate's degree or a certificate or credential from a technology center. Either amount may be claimed for up to seven years. The credit cannot reduce the taxpayer's liability below zero.

That last sentence does real work. A new graduate with a modest salary and a small Oklahoma liability may not absorb the full $2,200. The Commission's evaluation shows this in the data: in tax year 2020, claimants used about 61.4% of the dollars they claimed, and the average amount actually used was $1,281 per claimant. By preliminary 2023 figures the used share had risen to 94.3% and the average to $2,171.

Neither the rule nor the form describes a carryforward for the unused portion. Form 511-CR puts carryforward periods inside each credit's own description, and the description for line 5 lists none. Treat the unused piece as gone unless current OTC guidance says otherwise.

3. Qualified employer is a four-part test, and a letter ruling can settle it

Under the rule, an employer may request a letter ruling on whether it's a qualified employer. To get one, the employer must show four things.

  • It's a sole proprietorship, general or limited partnership, LLC, corporation, other legally recognized business entity, or a governmental entity.
  • It has at least fifteen full-time employees.
  • It operates in a qualifying industry under the most recent NAICS manual, which the rule lists as U.S. Sector Nos. 21, 22, 31-33, 48, 51, 52, 54, 55, 62, and 92.
  • It pays qualifying compensation for the county of its primary Oklahoma address.

For the compensation standard, the Commission's report fills in the statutory definition. Qualifying compensation means average annualized wages, excluding employer-provided health care and retirement benefits, of at least 110% of the average county wage as determined by the Department of Commerce using the most recent federal data. Federal employees meet a GS-5 or equivalent threshold instead. We didn't open a page listing county wage figures, so check the current Commerce table for your county before anyone relies on this.

A practitioner's observation: the fifteen-employee count and the compensation test are measured at the employer, not the employee. A brilliant hire at a twelve-person security startup doesn't qualify. The same hire at a forty-person manufacturer in Sector 31-33 might, even though the manufacturer isn't a tech company. Industry sector is about the employer's NAICS code, not the employee's job title.

4. The degree has to be the right degree

This is where the Commission found the most friction. Form 566 defines an accredited program two ways. The first is an undergraduate or graduate cybersecurity, information technology, computer science, or computer engineering degree program accredited by ABET's Computing Accreditation Commission or Engineering Accreditation Commission, at a degree-producing institution. The second is a software, cybersecurity, programming, coding, application development, computer science, or IT program requiring more than 800 hours of class time, which is the route technology center certificates and credentials take.

The Commission reported that stakeholders struggle with that language, and that OTC attributes denials generally to a claimant “having a degree but not the 'right one.'” The report's example is a master's in information systems earned through a business school: a degree that looks eligible, from a program that isn't accredited the way the statute requires. The Department of Commerce told the evaluators that the credentialing component, not the employer rules, is the limiting factor, and the report characterizes the 800-hour technology-center requirement as a high bar.

For an employer writing an offer letter, that means the recruiting pitch should be conditional. You can say the company is a qualified employer, if it is. You can't promise the credit, because the degree side belongs to the recruit and to ABET's accreditation list.

5. Form 566 asks for less than the rule requires

Form 566 for 2025 has three parts. Part 1 asks for the qualified employer's name and FEIN, and the employee's Oklahoma employment dates with that employer. Part 2 asks for the employee's name, graduation date, the city and state of the institution, the accredited program name, and the type of degree, certificate, or credential earned. Part 3 is the computation: enter $2,200 or $1,800 on line 1 and carry it to Form 511-CR. First-time claimants may be asked for proof, such as a diploma or transcript, and may enclose it.

Notice the gap between the instructions and the boxes. The form's instructions define a qualified employer, including the fifteen full-time employee count and the NAICS sector list. The form itself collects none of that: Part 1 is name, FEIN, and dates. Nothing on the form asks what the workforce is paid or which county sets the compensation benchmark, and the Commission's report doesn't describe any verification of employer wages.

Here's the point only someone who handles these files tends to make. A form's silence isn't a safe harbor. The rule conditions the credit on a qualified employer paying qualifying compensation for its county, and the OTC can test those facts in an examination whether or not the form asked about them. The Commission's report notes that audit data wasn't available and that stakeholders suggested the by-right structure and unclear eligibility may contribute to a high volume of ineligible claimants. That's the government-favorable side of this credit, and it's a fair one. A credit claimed by right on a two-page form is exactly the kind of item an agency later samples.

Documentation the employee will need from the employer therefore goes beyond what the form prints. Start and end dates in Oklahoma. The FEIN. A copy of any letter ruling on qualified-employer status, or at least a statement of the employer's NAICS code and full-time headcount for each year the credit is claimed. If the compensation test is close for your county, keep the computation.

6. The $5 million cap can shrink the credit, though it hasn't yet

For tax years beginning on or after January 1, 2022, the rule caps the total credits offset in a year at $5,000,000. The Tax Commission is to set, by the first day of each affected year, the percentage reduction needed to keep claims under the cap. If that percentage is ever published, every claimant's $2,200 or $1,800 becomes a smaller number before it reaches Form 511-CR.

So far the cap has had room. The Commission's evaluation, using OTC data, reports 46 returns claiming $95,995 in tax year 2020; 156 returns claiming $326,096 in 2021; 226 returns claiming $481,420 in 2022; and, on a preliminary basis, 939 returns claiming $2,161,712 in 2023. The report doesn't state that the cap has been reached and doesn't report any reduction percentage set by the OTC. The 2025 Form 511-CR carries no reduction note on line 5, though it does for other capped credits.

Read the trend, though. Returns grew at what the report calculates as a 173% compound annual rate, and the amount used to reduce tax grew faster. A credit that used about $2 million of a $5 million cap in 2023 and is growing at that pace is one a CPA should check each January against whatever percentage the OTC announces. The rule puts the announcement before the year starts, which means the reduction for a tax year is knowable before an employee accepts an offer that year.

That cap also changes the pitch. An employer that tells recruits the credit is worth $2,200 a year for seven years is making a prediction about the OTC's cap arithmetic through 2030. Say up to.

7. Two dates frame the whole program: November 1, 2019 and January 1, 2030

Under the rule, the credit applies to tax years beginning on or after January 1, 2020, and ending before January 1, 2030. A qualified employee is someone newly employed in Oklahoma by a qualified employer in a qualifying industry on or after November 1, 2019. Form 566 frames it the same way: employment on or after November 1, 2019, by someone who wasn't already working in Oklahoma before that date.

Put those together and the seven-year promise has an expiration problem. A graduate hired in 2026 would reach year seven in 2032. Under the rule as written, the credit stops with tax years ending before 2030 unless the Legislature extends it. The Commission recommended that the credit be retained, and also recommended an FAQ published with the tax form and a central list of eligible and ineligible programs. A recommendation isn't an extension. We checked the OTC's 2026 legislative summary and found nothing touching this credit, so as of the documents we reviewed, 2030 is still the end date.

The Commission's fiscal analysis is worth a sentence too, because it's the argument a legislator will hear. The report estimates credits used to reduce tax averaged roughly $682,000 a year from 2020 through 2023, and concludes that at least 30.4% of claimants would need to have taken their jobs because of the credit for the state to break even, a threshold the report says is likely not met. That doesn't change anyone's eligibility. It does tell you how secure the program is.

How this fits with the employer-side incentives

Think of the software and cybersecurity employee credit as a signing bonus the state pays, with the employer holding the eligibility paperwork. It sits alongside credits that do land on the company's return. The aerospace engineer credits give the employer its own credit tied to the hire, and the Small Employer Quality Jobs rebate pays the company directly on new payroll. A company hiring software talent may be looking at more than one of these at once, and the headcount, wage, and industry definitions don't line up across programs.

Where a lawyer adds value is usually before the first hire, not after the first denial. A letter ruling on qualified-employer status and an offer letter that describes the credit accurately cost far less than a recruit's seven years of disallowed credits and the conversation that follows.

If your company is building a software or security team in Oklahoma and wants the employer-side facts nailed down before recruits start claiming, reach us through the contact page or our Oklahoma City office. We'd rather spend an hour on the letter ruling now than on an examination response later.

Sources

  1. OAC 710:50-15-117, Credit for qualified software or cybersecurity employees (Cornell LII)
  2. Oklahoma Tax Commission Form 566 (2025), Credit for Qualified Software or Cybersecurity Employees
  3. Oklahoma Tax Commission Form 511-CR (2025), Other Credits Form
  4. Incentive Evaluation Commission, Software and Cybersecurity Employee Tax Credit Final Evaluation (Dec. 2, 2025) — Prepared by PFM Group Consulting for the Commission; utilization data attributed to OTC
  5. Oklahoma Tax Commission 2026 Tax Legislation Summary — Checked; does not mention this credit

This article is general information about Oklahoma, Texas, and federal law, not legal advice, and it does not create an attorney-client relationship. Facts matter; talk to a lawyer about yours.