Work Opportunity Tax Credit: 2026 Status

WOTC historically rewarded employers that hired and retained individuals from specified targeted groups, but the hiring authorization applied to workers who began work before 2026. The IRS now states that Form 8850 is no longer in use. Employers should therefore not prescreen a 2026 hire on an obsolete federal form or assume a credit exists because a worker appears to fit an old category. The current task is to preserve certified pre-2026 files, calculate eligible wages under the applicable year’s law, use the correct credit form, and monitor Congress, the IRS, and the state workforce agency for any future extension or transition procedure.

This guide is part of Steady’s Business Taxes & the IRS library. It explains the federal workflow in practical terms, but the correct result still depends on the payment year, entity, worker relationship, filing method, and state rules.

The answer in context

The start date controls current availability

The IRS WOTC page refers to qualified workers who begin work before 2026, so a 2026 hire is not currently eligible absent new law.

Form 8850 is no longer in use

The IRS updated its Form 8850 page on March 19, 2026; do not give current applicants an obsolete federal prescreening form.

Certification came from a state workforce agency

For eligible historical hires, the employer sought certification from the appropriate state agency rather than sending Form 8850 to the IRS.

The old deadline was strict

Historical procedures generally required prescreening on or before the job offer and submission to the state agency within 28 calendar days after work began.

Certification and calculation are separate

A certification supports targeted-group status, while qualified wages, hours, related-party limits, other credits, and the tax return determine the amount.

Tax-exempt organizations had narrower treatment

Qualified tax-exempt organizations could claim a payroll-tax credit for qualified veterans under the applicable historical rules.

Unused credits can affect later years

General business credit carryback and carryforward rules may make a properly supported pre-2026 credit relevant after the hire year.

A future extension needs official instructions

Retroactive extensions sometimes produce transition relief, but an employer should not invent a filing process before it is issued.

Step-by-step workflow

1. Separate hires by start date. Identify any worker who began work on or before December 31, 2025 and any later hire.
2. Locate state certifications. Match each historical certification to the employee, target group, request date, start date, and state agency.
3. Reconcile qualified wages and hours. Tie payroll detail to the applicable credit percentage, wage cap, minimum-hours rules, and exclusion tests.
4. Test overlapping incentives. Review other wage-based credits, subsidized payments, related parties, rehired employees, and tax-exempt status.
5. Prepare the applicable credit form. Use Form 5884 and Form 3800, or Form 5884-C for a qualified tax-exempt organization, as appropriate to the historical claim.
6. Track carryforwards. Reconcile the credit generated, used, limited, carried back, carried forward, and reported in each year.
7. Do not process 2026 hires under obsolete instructions. Wait for enacted law and official IRS and workforce-agency procedures.
8. Preserve the audit file. Keep the certification, prescreening record, submission proof, payroll, hours, calculation, returns, and credit rollforward.

Worked example

A company hired an eligible certified veteran in October 2025 and received state certification. The employee worked into 2026. The company does not treat the 2026 payroll as a new 2026 WOTC hire. It retrieves the original certification and timely submission proof, applies the law governing the 2025 start, reconciles qualified first-year wages and hours, and records any credit and carryforward on the proper returns.

The example is intentionally a workflow illustration, not a conclusion for every taxpayer. A strong file connects each number on the return to a source report and records why an exception, exclusion, or classification was applied.

Records to keep

Keep the source form or worksheet, contracts or engagement records, payer and recipient identity support, the detailed payment or payroll ledger, bank and processor reconciliation, calculations, correspondence about corrections, filed copies, recipient-delivery evidence, and federal and state acceptance confirmations. Store the records by tax year and keep superseded versions when they explain a correction.

A reviewer should be able to begin with the final reported amount and trace it back to transactions without rebuilding the year. Add a short review memo for judgments such as worker status, corporate exemption, payment-method exclusion, state filing, or unusual timing. That memo is often more useful than another unlabeled spreadsheet.

Common mistakes

• Advertising WOTC for every 2026 hire. The current federal authorization does not cover post-2025 start dates.
• Using obsolete Form 8850. The IRS states that the form is no longer in use.
• Claiming from demographic assumptions. Historical eligibility required the proper targeted group and state certification.
• Treating certification as the credit amount. Calculate qualified wages, hours, caps, exclusions, and tax limitations separately.
• Double counting wages. Coordinate WOTC with other wage-based benefits and funded amounts.
• Discarding an old certified file. A carryforward, amended return, or examination can keep the evidence relevant.

Final review before filing

Confirm the form and revision year, taxpayer identities, dollar fields, payment categories, withholding, filing channel, recipient statement, state obligations, due dates, and approval. Compare the final output with the source reconciliation rather than reviewing the form in isolation. If software recalculates an amount after an edit, rerun the tie-out.

Keep preparation, filing, and acceptance as three separate statuses. A draft can be complete but unfiled; a transmission can be sent but rejected; a federal return can be accepted while a state return is still missing. This status discipline prevents a polished PDF from being mistaken for finished compliance work.

How to handle a discrepancy

When a source form, ledger, payroll report, or software preview disagrees with another record, stop before filing and identify which amount represents the underlying transactions. Trace the difference by vendor or employee, date, invoice or payroll run, payment channel, and account. Common causes include a payment posted to the wrong year, a void recorded after a report was generated, a card payment included with checks, a duplicate import, an incorrect taxpayer name, or a late adjustment. Record the explanation and the correcting entry or form request.

Do not erase the trail by overwriting the original report. Save the first version, the reconciliation, the corrected version, and the approval. If a third party supplied an incorrect information return, request a formal correction and retain the correspondence. If a return was already transmitted, use the current correction procedure for that form and channel. A corrected recipient copy without a corresponding agency correction can leave the records inconsistent.

Federal filing is only one layer

Federal acceptance does not settle state or local obligations. A state may use a different threshold, worker test, filing portal, account number, transmittal, or due date. Some states receive eligible information through a combined program, while others require a direct submission. Verify the jurisdictions connected with the payer, recipient, employee, work location, withholding, and business activity. Save state confirmations separately so they are not hidden behind the federal acceptance.

Make next year easier

Turn the year-end work into a monthly control. Collect identity forms during onboarding, code payment methods consistently, reconcile payroll and vendor activity each month, and flag vendors or income streams that need special treatment. Schedule a fall review of missing forms, classification questions, state registrations, and electronic-filing access. By year-end, the team should be validating a maintained file instead of reconstructing twelve months of transactions under a deadline.

Practical implementation notes

Status date

Label every WOTC procedure with the date reviewed because authorization can change through legislation.

Legacy register

Track employee, start date, target group, state certification, qualified wages, credit, return, and carryforward.

Hiring workflow

Do not insert obsolete federal forms into current onboarding.

Monitoring

Use Congress.gov, IRS form pages, and the applicable state workforce agency for any future change.

For the next layer of context, see this related guide, the companion reporting article, and the connected workflow.

If the form, books, and filing status do not agree, Steady can help reconcile the source data and prepare a clean filing package through its specialist service.