Why Most HRIS Systems Fail at I-9 Compliance

Software & Technology
1
minutes to read
Close-up of an HR professional reviewing I-9 compliance details on a laptop as part of an integrated HRIS system.

When leadership decides to consolidate onboarding into a single all-in-one HR system, the I-9 is usually an afterthought — a checkbox on a feature list that says "I-9 and E-Verify supported." But the built-in I-9 module inside most HCM platforms is a form filler, not a compliance system — and that distinction is where employers get exposed.

Workday, SAP SuccessFactors, ADP, and UKG are excellent at payroll, scheduling, and core HR. I-9 compliance is a different discipline: it's regulated by federal law, audited by ICE, and changes often. Treating it as a bolt-on feature instead of a purpose-built capability is what leaves gaps an auditor will find. Here's where those gaps show up, why they exist, and how to keep your HR system without giving up real compliance.

The I-9 Trap Inside All-in-One HR Systems

At first glance, an HCM module looks like it has Form I-9 covered: employees complete Section 1 digitally, documents get uploaded, and E-Verify cases can be created. Under the scrutiny of a U.S. Immigration and Customs Enforcement (ICE) audit, the cracks appear — because recording an I-9 and managing I-9 compliance are not the same job.

The most common gaps we see when employers move I-9s into an all-in-one HCM:

  • No remote Section 2 verification. The platform records the form, but someone still has to physically inspect a new hire's documents in person. For remote or multi-location workforces, that means finding an authorized representative at every site.
  • Reverification reminders that don't fire on migrated records. When I-9s are converted from a prior system, expiration dates frequently don't carry over in a way the new system can act on — so the reminder for an expiring Employment Authorization Document (EAD) never triggers.
  • E-Verify mismatches resolved outside the system. When E-Verify returns a Tentative Nonconfirmation (TNC), resolution typically happens on the E-Verify website, not inside the HCM — a broken workflow against a tight federal clock.
  • Silent failures. Configuration quirks — like a future-dated hire that never starts the E-Verify case — can fail with no alert. You find out at audit.
  • No built-in error checking or audit trail depth. An HCM records what's entered. It doesn't catch the missing date, the unsigned certification, or the mismatch between Section 1 and Section 2 before it becomes a violation.

Why This Is a Design Problem, Not a Bug

The issue stems from product design, not vendor incompetence. All-in-one platforms optimize for breadth and a smooth onboarding experience. Form I-9 rules are narrow, technical, frequently updated, and demand airtight, auditable records. Unless compliance is a core product pillar, it gets treated as a bolt-on — and bolt-ons don't include the error checking, reverification tracking, or remote verification service that a dedicated I-9 platform is built around.

That's also why a thriving market of third-party I-9 integrations exists on the major HCM marketplaces. If the native module fully solved the problem, those integrations wouldn't have customers. Some large institutions have stopped using their HCM's native I-9 module entirely for exactly this reason.

"An HCM will happily store an I-9 that's missing a signature or a date — it has no reason to flag it," says Patricia Duarte, Director of Compliance at i9 Intelligence. "A purpose-built system is looking for the error before the auditor does. That's the whole difference."

HCM I-9 Module vs. Dedicated I-9 Platform

The gap isn't about which vendor is "better" — it's about what each tool is built to do. Here's how a built-in HCM module compares to a purpose-built I-9 compliance platform on the capabilities that matter in an audit:

Capability Built-in HCM module Dedicated I-9 platform
Remote Section 2 verification Not included — in-person inspection required Included — trained representative via live video
Reverification alerts on migrated records Often don't fire after migration Tracked and flagged automatically
Built-in error checking Records what's entered; doesn't validate Flags missing or invalid entries before submission
E-Verify TNC handling Resolved outside the system Managed in-platform with case tracking
Electronic audit trail (8 CFR § 274a.2) Varies — gaps are now substantive violations Built to the federal standard
Data portability when you switch HR systems Re-migrate I-9s with each change I-9s stay put in a dedicated layer
Compliance expertise behind it HR software vendor I-9 and E-Verify specialists (27+ years)

Check Your Exposure in Two Minutes

Not sure whether your HR system actually covers I-9 compliance? Use our free I-9 Risk Calculator to gauge your exposure, or see the full checklist of what to look for in I-9 compliance software.

The March 2026 Enforcement Shift Raised the Stakes

On March 16, 2026, ICE issued an updated Form I-9 inspection fact sheet that reclassified a long list of common errors from technical to substantive. The distinction matters enormously: technical failures come with at least 10 business days to correct, while substantive violations carry immediate fines.

Two of those reclassifications hit HCM users directly:

  • Electronic I-9 system failures are now substantive. If your system can't meet the electronic record standards in 8 CFR § 274a.2(e)–(i) — audit trail, indexing, secure retention, retrieval — that's a substantive violation, not a technical one.
  • Late reverification (Supplement B) is now substantive. Failing to complete reverification by the employment authorization expiration date is no longer an error you get time to fix. This is exactly the failure mode created when migrated records don't trigger reminders.

For the full breakdown, see our analysis of how ICE redefined substantive I-9 violations. Paperwork penalties are assessed per individual Form I-9 and adjusted annually by the Federal Register — current ranges are in our guide to 2026 I-9 penalties.

The Migration Trap: Your I-9s Get Stuck

There's a practical cost to putting I-9s inside your HCM that rarely comes up in the sales pitch: once your I-9 records live inside your HR system, switching systems later means migrating those records all over again. Companies change payroll and HCM vendors every few years. Each switch becomes another I-9 migration — and migrated records are exactly where reverification data tends to break.

Keeping I-9s in a dedicated compliance layer means they stay put, audit-ready, no matter how many times your core HR stack changes. We cover the records side of this in detail in storing I-9s across multiple systems.

You Don't Have to Choose: Integrate, Don't Replace

Here's the part most teams miss when leadership pushes for one system: keeping purpose-built I-9 compliance doesn't mean fighting the consolidation. i9 Intelligence doesn't replace your HCM — it connects to it.

With our API and SFTP integration, your team keeps working inside Workday, SAP, ADP, or UKG for onboarding, and the I-9 compliance engine runs underneath. The integration can:

  • Auto-initiate the I-9 when a new hire is added to your HR system
  • Sync employee data so no one re-keys information
  • Push compliance status back into your HR dashboard
  • Trigger alerts for missing, expiring, or incomplete forms

And unlike a native module, our service includes remote Section 2 verification: a trained i9 Intelligence representative completes Section 2 with new hires anywhere in the U.S. over a live video call — no notary, no travel, and fully within the DHS alternative procedure (which requires E-Verify participation in good standing). Your managers do the same work; it just happens in a system built to catch what an HCM won't.

Common Questions

Does Workday (or ADP, SAP, UKG) handle I-9 and E-Verify?

They support I-9 form completion and can create E-Verify cases, but the built-in modules generally lack remote Section 2 verification, automated reverification tracking on migrated records, and proactive error checking. They record I-9s; they don't manage I-9 compliance the way a dedicated platform does.

Can we keep our HR system and still use a dedicated I-9 platform?

Yes. That's the point of an integration. Your HCM stays your system of record for HR and payroll; i9 Intelligence connects via API or SFTP and handles the compliance layer — verification, reverification alerts, audit trail, and E-Verify case management. Nothing gets ripped out.

What happens to our I-9 records if we switch HR systems later?

If your I-9s live inside your HCM, switching vendors means migrating those records again — and reverification data often breaks in migration. Keeping I-9s in a dedicated layer means they stay audit-ready regardless of changes to your core HR stack.

Is remote I-9 verification actually allowed?

Yes. Employers who participate in E-Verify in good standing may use the DHS-authorized alternative procedure to examine documents over a live video interaction, retaining copies of the documents. It must be applied consistently and without discrimination at participating E-Verify hiring sites.

Talk to a Team That Does I-9 Compliance All Day

If leadership is moving you toward an all-in-one system, get the full picture first. Our compliance team has 27+ years of I-9 and E-Verify experience and can show you exactly how the integration works. Schedule a free compliance call, or estimate what compliance gaps are costing you with our I-9 Retention Calculator.