WorkBright Logo
Blog
E-Verify and TNCs
Compliance management

E-Verify cases that catch teams off guard: TNC notices, reverification, and data errors

Published on May 22, 2026
Published byWorkBright
Reviewed byNina Bernardi

Most E-Verify cases resolve in under five seconds. The system pings DHS and SSA, "Employment Authorized" comes back, and nobody thinks about the case again. For a company doing 10 hires a year, that's the end of the story.

But for staffing firms, healthcare networks, and retailers running seasonal volume, the exceptions stack up fast. And the federal timelines attached to them don't bend. Here's a look at three categories of E-Verify edge cases that routinely create compliance exposure, and what managing them well requires.

Edge case #1: Tentative Nonconfirmation (TNC) response from E-Verify

An E-Verify TNC notice means the system couldn't confirm eligibility through standard database matching. It does not mean the employee is ineligible. But it triggers a specific sequence of required actions with hard federal deadlines, and this sequence has to be followed exactly.

What the timeline looks like:

  • Employers have 10 federal working days from TNC issuance to notify the employee and provide a Further Action Notice (FAN) explaining the mismatch. The employee must decide whether to contest within that same window.
  • If they contest, they have an additional 8 federal working days to contact DHS or visit an SSA office.

During the entire window, employers cannot take any adverse action based solely on TNC status. If the employee declines to contest or doesn't respond within the window, the case becomes a Final Nonconfirmation, at which point termination is legally permissible.

Where it gets tricky

The most common failure in this scenario is tracking. When you're managing 30 open TNCs at once, each on its own federal timeline, a shared spreadsheet and a calendar invite are not a compliance system. Cases slip. Deadlines pass. Adverse action happens before it's legally permitted, or termination is delayed past the point where it's documented.

The other common failure is treating a TNC as a red flag rather than a process. Employees with legitimate eligibility, whose records simply don't match because of a name change, an SSN update, or a database lag, get pushed out of jobs they're legally entitled to hold. That's a liability, not a compliance win.

Edge case #2: Data entry errors that trigger TNCs

Not every E-Verify TNC notice reflects a true employment eligibility question. A large share is caused by errors introduced during Form I-9 completion.

Important preventable errors:

  • Restricted Social Security cards: Certain SSA-issued cards include restrictions, such as: "NOT VALID FOR EMPLOYMENT" or "VALID FOR WORK ONLY WITH DHS AUTHORIZATION." These cards are not acceptable List C documents for I-9 purposes. If one is accepted and submitted to E-Verify, it generates a TNC that didn't have to happen.
  • Document attestation mismatches: The employee’s citizenship or immigration-status attestation in Section 1 affects which documentation paths and E-Verify workflows apply. If information from the Form I-9 is entered inconsistently, or if the documentation collected does not align with the employee’s attestation and government records, the E-Verify submission may not match DHS or SSA records, increasing the likelihood of a TNC.
  • SSN handling: E-Verify requires all employees to provide a Social Security number. Teams that don't catch this at intake either delay case creation or submit incomplete cases.

These errors can be caught before a case is ever submitted. The question is whether your intake process has the right controls built in to catch them.

Edge case #3: E-Verify reverification and expiring work authorization

E-Verify compliance doesn't end at hire. Employees on temporary work authorization — EADs, TPS-based documents, and certain visa categories — have documents that expire. When they do, Supplement B reverification on Form I-9 is required. Note that reverification does not require creating a new E-Verify case.

What makes this complicated:

EAD category codes matter. Not all EADs are the same. The category code printed on the card determines what reverification is required, whether automatic extensions apply, and how TPS designation changes affect the employee's continued authorization. An EAD with category code C09 is different from one with C19, and treating them the same creates gaps.

TPS designation changes. When DHS extends or redesignates Temporary Protected Status for a country, employees from that country may be eligible for automatic extensions of their EADs. But the rules are specific to each designation, and the extension periods vary. Employers who aren't tracking this can let valid authorizations lapse, requiring employees to go through unnecessary re-documentation.

The reverification window. E-Verify reverification needs to happen on or before the document's expiration date. Teams that rely on reactive tracking — someone noticing an expiration has passed — routinely miss the window, creating both I-9 violations and potential gaps in employment authorization.

What proactive tracking looks like: Outreach to the employee 90 and 60 days before expiration, initiated by your I-9 and E-Verify system, with a reverification workflow that starts before the deadline.

What these cases have in common

Each of these edge cases shares the same underlying characteristic: they're manageable with the right process, and essentially unmanageable at scale without one. A company doing 20 hires a year can survive on manual tracking. A company doing 200, or 2,000, cannot.

The difference isn't knowledge — most HR teams understand the requirements. It's bandwidth. How much of the process runs automatically versus how much lands on someone's to-do list? For TNCs, that means automated timeline tracking and notices. For data entry errors, it means document validation and restricted-card detection at intake. For reverification, it means built-in workflows to begin outreach before expiration, not after.

WorkBright's I-9 and E-Verify platform is built specifically for employers managing this kind of volume and complexity, from automatic case creation to TNC workflow management to expiration tracking across an active workforce. If your team is handling these cases manually today, see what it looks like when the process runs itself.

WorkBrightRadically simple form verification

HR compliance is complex, but it doesn’t have to be. WorkBright’s modern software and services streamline I-9s, E-Verify, and form management, while keeping your team audit-ready and aligned with ever-changing regulations. Take the guesswork out of compliance so you can focus on what matters most—your people.

Nina BernardiContent Strategy Manager

Nina has spent over seven years writing for the tech industry, transforming complex ideas, user insights, and industry research into content that informs and engages readers.

E-Verify cases that catch teams off guard: TNC notices, reverification, and data errors | WorkBright