Why Your HCM Auto-Fills Form I-9 Section 1 — and Why That's Now a Substantive Violation Problem

If your HCM auto-fills Form I-9 Section 1 from candidate data — and Workday, SAP SuccessFactors, ADP, and UKG all do — ICE's March 16, 2026 fact sheet just changed your audit exposure. The updated Form I-9 Inspection fact sheet reclassified pre-populated Section 1 fields the employee didn't affirmatively review as substantive violations, with civil penalties of $288 to $2,861 per form and no 10-day correction window.

Every I-9 generated through your HCM's standard onboarding flow is now potentially exposed unless your tenant configuration forces explicit employee re-attestation of every pre-populated field. A 500-employee company with 200 hires and 100% pre-population is sitting on $57,600 to $572,200 in first-offense exposure — before the five statutory adjustment factors kick in. This article walks through what changed, how each major HCM auto-fills Section 1, what reconfiguration buys you, and the three options HR teams are choosing between right now.

What Pre-Populated Section 1 Means Under the New ICE Standard

The 1997 Virtue Memorandum and follow-on ICE guidance from 2008 and 2009 drew a clean line: minor paperwork errors made in good faith were technical failures, correctable within 10 business days. Substantive violations were reserved for material failures — missing forms, missing signatures, fundamental attestation gaps.

The March 16, 2026 fact sheet erased much of that line. As Holland & Knight summarized: "More than 10 error categories previously treated as correctable technical violations — eligible for the statutory 10-day cure period — are now reclassified as substantive violations subject to immediate fines of $288 to $2,861 per form."

The fact sheet also explicitly classifies electronic I-9 system failures as substantive violations. Per Morgan Lewis: "ICE is explicitly treating failures of electronic systems to meet regulatory standards as substantive violations, which puts vendor selection, system configuration, and audit trail functionality directly in the enforcement spotlight."

The piece that hits HCM customers hardest sits inside that "system configuration" phrase. Section 1 is an employee attestation under penalty of perjury — the employee attests to their citizenship or immigration status and the accuracy of every field they provide. When an HCM hands a new hire a Section 1 already populated with name, date of birth, address, and SSN from the applicant tracking record, the question ICE now asks is: did the employee affirmatively review and attest to this information, or did they sign a form that was effectively pre-completed by the employer's systems?

If the answer is the second one — and for the standard configuration of every major HCM, it is — the form is now a substantive violation. For the regulatory background and the full reclassification table, see our companion article: ICE Redefines "Substantive" I-9 Violations.

How Each Major HCM Auto-Fills Section 1

Every major HCM was built to streamline onboarding. Auto-populating Section 1 from candidate data was a feature — fewer fields to type, faster time-to-completion. In the post-March 16 environment, that feature is the exposure. Here's the current state of each platform's auto-fill behavior and what the vendor has publicly committed to about the reclassification.

The pattern is consistent: pre-population is the default, forced re-attestation is not, and none of the four has publicly committed to a configuration update tied to the March 16 fact sheet.

Why This Isn't Easily Configured Around

The first instinct for most HR leaders is "we'll just reconfigure the workflow." It's harder than it sounds. Each HCM places different limits on what administrators can change, and the I-9 module typically sits inside a stack — Recruiting feeds Onboarding feeds Compliance — where small upstream changes have unpredictable downstream effects.

The Workday side is well-documented in customer support forums. As Phenome Cloud's Workday I-9 documentation notes about routine I-9 reconfiguration: "The process of re-triggering I-9 steps should be used sparingly only if absolutely required, because onboarding I9/compliance have many moving parts." Configuration changes at the I-9 layer also flow through to Workday's E-Verify integration, where misconfiguration creates silent failures: "If you key in a future date, the E-Verify process will not start."

SAP customers face a parallel pattern. The 2H 2025 release was the first SAP version to ship an employee-initiated Section 1 correction flow — meaning until late 2025, every Section 1 correction required HR admin action or restarting onboarding. Per SAP's own release notes, the new flow "lets a new hire securely correct mistakes in Section 1 — and re-attest — without restarting onboarding or relying on ad-hoc admin work." That's the workflow primitive ICE's March 16 fact sheet now expects to be the default — and which most SAP tenants don't have configured.

SAP's Q1 2026 document-upload patch is a useful preview of what "we'll fix it on the vendor side" looks like in practice. SAP shipped a fix in early January 2026 ensuring List A and List B document uploads couldn't be skipped during Section 2. Within weeks, they rolled it back behind a configuration toggle. From the SAP Community blog: "SAP heard clear feedback from customers that document uploads should remain an employer choice — not a system-imposed requirement." Vendor incentives don't always align with the strict reading of compliance.

For UKG customers, the configuration ceiling is even lower. Per the Inova Payroll UKG E-Verify User Guide: "E-Verify does NOT automatically sync demographic changes, and this step is required to keep your E-Verify records compliant." If a new hire's last name changes between Section 1 and Section 2, UKG's connector won't sync it to E-Verify — exactly the kind of mismatch ICE's new fact sheet treats as substantive. There's no configuration toggle for this. It's a connector limitation.

The customer-experience pattern is consistent across review platforms. From Capterra's Workday HCM review aggregation: "Companies are spending significant resources on RFI/RFP processes and hiring contractors to rebuild and remake the Workday system to function for Talent Acquisition, HR, and IT." From a UKG Pro reviewer on Software Advice: "Workflows feel slow and unintuitive for new users, and certain configuration changes still require support tickets instead of being self-service, which delays projects." For an I-9 with a 3-business-day Section 2 deadline, "delays projects" is a compliance liability.

"We've reviewed records from companies on every one of these HCMs, and the pattern is the same — Section 1 comes back to us already populated, the new hire never typed any of it, and the audit trail shows a 30-second 'review' before they hit sign," says Patricia Duarte, Director of Compliance at i9 Intelligence. "Before March 16, we'd flag those as best-practice issues. After March 16, they're a fineable violation per form. The fix isn't a setting somewhere — it's a workflow that forces the employee to actually look at every field and re-attest. Most HCM configurations weren't built for that."

The Vendor Roadmap Question

The honest question for any HR leader is whether the HCM vendor will ship the configuration changes you need before your next ICE audit lands. Based on the public record as of May 2026, here's where each vendor stands.

Workday. Aneel Bhusri returned as CEO on February 9, 2026 after Carl Eschenbach was pushed out following a ~$40B value drop. Per Fortune: "Workday lost $40 billion in value. Cofounder Aneel Bhusri is back with a $139 million bet he can turn it around." The Feb 4 layoffs of ~400 customer-operations staff hit "non-revenue generating roles" in Global Customer Operations — the team most likely to handle tenant-level I-9 configuration requests. The new direction is "platform of agents," not deeper compliance configuration.

SAP SuccessFactors. The 1H 2026 release shipped — finally — a UI-based way to cancel a stuck I-9 process. Per the SAP Community release blog: "Previously, once an I-9 or E-Verify process was initiated, there was no UI-based way to cancel it, which led to inflated compliance dashboards and real audit exposure." That's the vendor admitting that until April 2026, customers couldn't cancel a stuck I-9 without a support ticket. Onboarding 1.0 was sunset May 14, 2026, and the platform customers are migrating to is still playing catch-up on basic I-9 audit-trail features.

ADP eI-9. The "Classic UI" was last redesigned December 2014 — eleven years ago. ADP has not made a public statement on the March 16 reclassification and has not committed to a forced-re-attestation workflow. One bright spot: ADP has publicly confirmed deployment of the 01/20/25 form edition ahead of the July 31, 2026 deadline — the only major HCM to do so. The form version is current. The workflow design is not.

UKG Pro. No public statement on the reclassification, no commitment to fix the demographic-sync gap or the hardcoded "Verified=Yes" connector bug, no 1H 2026 release note addressing the I-9 module specifically. No public commitment on the July 31, 2026 form edition deadline either.

The pattern is consistent: none of the four HCMs has publicly committed to a configuration or workflow change tied to the March 16 fact sheet.

Talk to a Compliance Specialist Before Your Next Audit

If your HCM auto-fills Section 1 today, the fastest way to get a real read on your exposure is a 30-minute call with our compliance team. We've reviewed records from companies on Workday, SAP, ADP, and UKG, and we know what ICE auditors look for after March 16. Schedule a free compliance call or run the numbers yourself with our I-9 risk calculator.

What HR Teams Are Doing About It

HR leaders working through this exposure are choosing between three options. None is free; the right answer depends on how much pre-population is happening, how much configuration capacity the team has, and how strategic the HCM is.

Option 1: Reconfigure the HCM to Force Explicit Re-Attestation

The lightest-touch option. Add an explicit employee review-and-attest step to Section 1 — a screen that requires the new hire to confirm or correct each pre-populated field, then re-sign. The audit trail must capture the re-attestation as a distinct event from the initial pre-population.

What it requires: a Workday business process or SuccessFactors workflow modification, a tenant-level configuration change, and (in most cases) a vendor support ticket or implementation partner engagement. The 2H 2025 SAP release shipped the workflow primitive needed; older Workday tenants and ADP eI-9 will require more bespoke work.

The trade-off: you stay on the HCM you already pay for. But you depend on the HCM's audit trail meeting 8 C.F.R. § 274a.2 standards, and you absorb the long tail of any future bugs in the HCM's I-9 stack. SAP's January 2026 patch reversal is a fair preview of how that long tail behaves.

Option 2: Layer a Compliant I-9 Platform on Top

The middle path. Keep the HCM as the system of record for HR/payroll/benefits, but route I-9 and E-Verify through a dedicated I-9 platform with a workflow built for the post-March 16 standard. The platform handles Section 1 attestation, Section 2 verification, E-Verify submission, reverification reminders, and audit trail. Data flows back to the HCM via integration.

The trade-off: you add a vendor and an integration to maintain. In exchange, you get a workflow built for I-9 specifically, audit trails purpose-built for ICE inspections, and remote Section 2 verification — capability no HCM currently matches natively.

Option 3: Fully Migrate Off the HCM I-9 Module

The heaviest lift, and the right answer when the HCM I-9 module is creating enough pain that the March 16 reclassification is just the latest reason to leave. Common triggers: SAP customers in the May 14, 2026 Onboarding 1.0 sunset (see our SAP Onboarding 1.0 I-9 migration guide), Workday customers tired of the 80-page onboarding PDF, ADP customers stuck on the 2014 Classic UI, UKG customers running the demographic-sync workaround manually.

The trade-off: the cleanest break from HCM I-9 limitations and the strongest audit-readiness posture. Implementation is days to weeks for the I-9 platform — much shorter than the 6-18 month HCM implementations customers describe in reviews. For many companies the migration cost is recovered in the first ICE audit avoided.

For a structured way to size your exposure, see our I-9 self-audit playbook.

How i9 Intelligence Handles Section 1 Differently

Our workflow treats Section 1 as the employee's act, not the system's. New hires complete Section 1 by entering their own information directly — name, date of birth, address, SSN, citizenship attestation. We don't pre-populate fields from any upstream system. The attestation, signature, and audit trail event all reflect the employee's affirmative action, with timestamps, IP capture, and field-level event logging that meet the 8 C.F.R. § 274a.2 electronic standards.

Remote Section 2 verification is built in: trained i9 Intelligence agents conduct live video verification with the new hire — no notary, no scrambling for an authorized representative. E-Verify submission, reverification reminders, and Supplement B handling sit on the same audit-ready platform. We integrate with HCMs including Workday, SAP, ADP, and UKG so the rest of the HR record flows where it needs to — but the I-9 attestation, verification, and audit trail live in a system designed for I-9 compliance. See the migration overview or schedule a free compliance call.

Frequently Asked Questions

Will reconfiguring our HCM workflow be enough?

It depends on the HCM and the audit trail capabilities. For HCMs where you can add a forced explicit re-attestation step at Section 1 — and where the audit trail records that re-attestation as a distinct event meeting 8 C.F.R. § 274a.2 standards — reconfiguration can close the gap. Where the audit trail or workflow primitives don't support that (UKG's connector demographic sync, ADP's 2014 Classic UI workflow), reconfiguration alone won't be sufficient. The honest test: can your audit trail show, for any individual I-9, that the employee personally reviewed and attested to every Section 1 field after the data was placed in the form?

What if our HCM auto-fills Section 1 but we manually verify everything?

Manual verification by HR isn't the same as employee re-attestation. Section 1 is the employee's attestation under penalty of perjury. If HR is confirming the data is correct, the form is attesting to what HR believes — not what the employee said. That's a substantive defect. The fix is a workflow where the employee personally reviews and attests, with the audit trail capturing that act.

Is this a problem for old I-9s already in our system?

Yes. ICE is enforcing the reclassification on inspections going forward, but the I-9s you already have on file were prepared under the old regime. ICE has not announced retroactive amnesty. Existing I-9s with pre-populated Section 1 fields and no documented employee re-attestation are exposed in any future audit. Internal self-audits with documented corrective action are the most direct way to reduce that exposure — see our I-9 self-audit playbook.

Should we wait for our HCM to fix this?

None of the four major HCMs has publicly committed to a workflow change tied to the March 16 fact sheet. Workday is mid-CEO-transition and customer-ops layoffs. SAP just shipped a "cancel a stuck I-9" button in 1H 2026 — eight years into Onboarding 2.0. ADP's eI-9 UI is from 2014. UKG has been silent on I-9 for two quarters. Waiting is valid only if you have low pre-population exposure and a clear vendor roadmap commitment. For most companies, neither is true. For current penalty math, see our I-9 Penalties in 2026 guide.

Need Help Reviewing Your I-9s?

Our compliance team has reviewed records from companies on every major HCM and can tell you within a 30-minute call where your real exposure sits and what the fastest path to remediation looks like. Schedule a free compliance call, run the numbers with the I-9 risk calculator, or reach our team directly:

• Phone: (713) 668-6200 (Mon–Fri, 8 AM – 5 PM CT)
• Email: support@i-9intelligence.com
• Submit a ticket: i-9intelligence.com/submit-a-ticket