Compliance Alert

Two I-9 Rule Changes Collided This Summer, and Almost Nobody Connected Them

Published by Faulkner HR Solutions | Employment Law and HR Compliance

On March 16, ICE quietly moved electronic I-9 system documentation deficiencies out of the technical column and into the substantive one. On July 31, the deadline passed for updating electronic I-9 systems to the current form version. Those two events were covered separately, four months apart, by people who had no particular reason to read them together. Together they mean something neither one means alone: if your onboarding platform missed the July deadline, the ten-day window you would have used to fix it stopped existing in March.

The two dates

Take them in order, because the sequence is the whole point.

In March, ICE revised its Form I-9 Inspection fact sheet in a way that superseded key provisions of the 1997 Virtue Memorandum, the guidance that had governed I-9 enforcement for nearly three decades. It arrived with no Federal Register notice, no proposed rulemaking, and no press release. What it did was move more than ten categories of common error from technical to substantive, and one of those categories was electronic I-9 system documentation deficiencies, which had previously been largely unaddressed.

In July, the separate clock ran out. Employers running an electronic I-9 system had to be serving a form with a 05/31/2027 expiration date by July 31. The version showing an expiration of 07/31/2026 is no longer acceptable for new hires. We covered the mechanics of that in our guide to common I-9 compliance mistakes, including the detail that catches most people: the expiration date is what matters, not the edition date, and USCIS issued the same 08/01/2023 edition under two different expiration dates.

Read separately, the first is a technical enforcement story and the second is a calendar item. Read together, they describe a specific and expensive situation that a lot of Texas employers are sitting in right now without knowing it.

Why the cure period is the entire story

This is the part that is not obvious from the labels, and it is where most of the coverage stopped short.

The good-faith exception that gives an employer ten business days to correct I-9 errors has only ever applied to technical violations. It has never applied to substantive ones. So when a category of error moves from technical to substantive, the cure period does not get shorter. It disappears. A deficiency you could have fixed with a phone call in February is a fine in August, assessed per form, in a range that currently runs $288 to $2,861.

Now apply that to the July deadline. An employer whose vendor kept serving the expired version has been generating I-9s on an invalid form since August 1. Under the old framework, an electronic system documentation problem was the kind of thing you would expect to correct on notice. Under the framework that has been in force since March, it is fineable on discovery, and the count is per form rather than per incident. A company hiring twenty people a month does not have one problem. It has twenty, and the number grows every payroll cycle until somebody checks.

If you self-audited your I-9 files before March, your findings were scored under rules that no longer apply. That is worth saying plainly, because a clean audit report from January is doing nothing for you now except providing false comfort.

The vendor conversation to have this week

Do not ask your payroll or HRIS vendor whether you are on the current edition. That question has a comfortable answer that is frequently wrong, because two different printings of the 08/01/2023 edition exist and only one of them is still valid. Ask instead for written confirmation of the expiration date on the form their system is serving today, and keep the reply.

The written part is not bureaucratic instinct. Documentation, in our work, is not paperwork. It is proof of how the organization reasoned. If an inspection later asks why you believed your electronic system was compliant, a dated vendor attestation is an answer. A recollection that somebody probably handled it is not, and the difference between those two things is the difference between a defensible position and a hopeful one.

While you have the vendor's attention, ask the second question too: what happens to the I-9s completed between August 1 and whenever they patched it. You will need to know how many there are before you can decide anything else.

What this actually says about your process

Here is the uncomfortable read. An employer who got caught by this collision was not negligent about I-9 compliance. They were relying on a vendor to track a form version and on nobody in particular to verify that the vendor had. That is not a form problem. It is a workflow problem wearing a form problem's clothes, and it is the same shape as most of the compliance failures we find in Texas organizations.

The pattern is consistent enough to be diagnostic. One manager completes the form correctly, another misses the deadline, a third accepts the wrong document combination, and the organization files all of it under human error rather than admitting the system was never built to produce consistent compliance. We worked with a Texas organization that ran a late-stage internal review after a notice of inspection arrived and found errors on 27 percent of its forms, several missing entirely, with no audit trail explaining any of it. The issue was not that anyone was unaware of the requirement. The issue was process fragmentation, and it took a standardized onboarding workflow, centralized storage, and a quarterly audit cycle to get the error rate below five percent.

Compliance does not live in a legal corner away from the daily work. It lives in ordinary supervision, and in whether the same decision gets made the same way twice. A form version check is exactly that kind of decision. It is small, it is boring, it recurs, and whether it happens reliably tells you more about your exposure than any single file will.

What to do before your next hire

Open your onboarding system and start a test hire, rather than asking anyone. Look at the expiration date on the form the system actually generates. If it does not read 05/31/2027, stop hiring through that workflow until it is fixed, and count the I-9s completed since August 1.

For any that landed on the expired version, complete a fresh form on the current one, keep the original, and attach a short signed memo recording what you corrected and when. Do not backdate anything. A documented correction made before a notice arrives reads as good faith. The identical correction made after one arrives reads as cleanup, and ICE weighs good faith when it sets a penalty inside the range.

Then go further than the immediate problem, because the immediate problem is not the interesting one. Our I-9 audit preparation guide walks the full internal review, and the I-9 Audit Penalty Estimator will price your exposure across your actual file count in a couple of minutes. If the number it returns is uncomfortable, that is the point of running it now rather than during the three business days a Notice of Inspection gives you.

One thing not to do. Do not use this as an occasion to reverify employees whose documents have not expired and whose status has not changed. Deciding to re-check only the people whose paperwork you have a feeling about is discrimination, and it is a theory that plaintiffs' attorneys and the Immigrant and Employee Rights Section both know how to run. Whatever process you adopt, apply it to everyone or to no one.