- UKG Pro exposes REST and SOAP web services that let immigration platforms read employee data without HR re-keying names, hire dates, or worksite addresses into every petition. Hire dates and demographic data flow through UKG Pro's Onboarding API; visa, work-authorization expiry, and Form I-9 detail fields are accessed via the core UKG Pro HCM Web Services.
- Form I-9 is the compliance anchor: every U.S. employer completes Form I-9 for each new hire, with Section 1 completed no later than the employee's first day of employment and Section 2 within three business days of the first day (or by the first day if employment lasts fewer than three business days), per USCIS Handbook for Employers M-274 §4.0.
- Retention rule: Forms I-9 are retained for three years after the date of hire or one year after employment ends, whichever is later. Per 8 CFR 274a.2(b)(2)(ii), ICE, DOJ-IER, or DOL provide at least three business days' notice before inspection, by which time forms are produced.
- Electronic system standards at 8 CFR 274a.2(e) through (i) require reasonable integrity, accuracy, and reliability controls; documentation; security and audit-trail controls capturing creation, completion, updating, modification, alteration, or correction of each electronic Form I-9; and electronic signature standards for both employee and employer (see USCIS M-274 §10.1).
- Typical setup timeline: 4 to 8 weeks for a production integration covering H-1B, L-1, TN, O-1, and green card populations.
- Preparation matters: Clean field mapping and service account scoping help prevent silent sync failures that often surface only during an ICE Notice of Inspection.
Connecting your immigration case management with UKG Pro (formerly UltiPro) turns a manual, email-driven process into an automated workflow that tracks every sponsored employee's work authorization, Form I-9 status, and expiration dates alongside the rest of your HR data. For HR teams running UKG as their system of record, integration helps surface an EAD expiration well in advance rather than at the moment it lapses. This guide walks HR leaders, people operations managers, and sponsored employees through the integration timeline, what each party owns, and how to stay aligned with U.S. Citizenship and Immigration Services (USCIS) and Department of Homeland Security (DHS) standards.
UKG Immigration Integration Timeline: From Scoping to Go-Live
While technical setup is the visible work, the integration also includes scoping, service account configuration, data sync, and ongoing compliance monitoring. Understanding each phase helps HR set realistic expectations and identify handoffs between HR, IT, and the immigration provider. A complete integration from kickoff to go-live typically spans 4 to 8 weeks, depending on the number of UKG modules in scope and the complexity of the sponsored population.
Phase 1: Scoping and Pre-Integration Planning
Before any API calls happen, HR defines what data flows between UKG and the immigration platform. This phase typically runs 1 to 2 weeks depending on how well-documented the existing sponsored-employee data is. Employers with clean records in UKG move faster; those tracking visas in spreadsheets need extra time to reconcile before migration.
The 2026 enforcement environment continues to emphasize accurate documentation. USCIS guidance and DHS continue to set expectations for electronic system standards, and employers who fail to properly complete or retain Forms I-9 may face civil money penalties per I-9 Central penalty guidance. Scoping is the moment to close gaps between what HR tracks in UKG and what the immigration platform needs.
Inventory items typically reviewed before kickoff:
- Sponsored employee population: Every current employee on H-1B, L-1, TN, O-1, E-3, H-1B1, or pending green card, plus anyone with a pending or future case.
- UKG modules in use: Core HR, Payroll, Onboarding, Benefits, Recruiting. An integration touching Core HR only is simpler than one spanning Recruiting and Onboarding.
- Custom fields already configured: Existing sponsorship flags, visa-type dropdowns, or expiration-date fields in UKG.
- Current workflow owners: Who tracks expiration dates today, who completes I-9 Section 2, and who coordinates with attorneys. Mapping the existing process shows what the integration can automate.
- Data privacy requirements: Regional privacy frameworks that apply to employee data, including cross-border considerations.
Strong scoping typically includes a documented inventory of every sponsored employee with current visa type, expiration date, and case stage; clearly identified UKG custom fields for sponsorship status; alignment among HR, IT, and the immigration provider on system-of-record decisions; privacy and data residency confirmed before technical work begins; and named owners for every phase with backup coverage. Weak scoping, by contrast, often appears as a spreadsheet of "about 30 sponsored employees somewhere," no decision on whether UKG or the immigration platform holds the I-9, an assumption that IT will handle the service account without a kickoff meeting, field mapping deferred to "we'll figure it out during testing," and no plan for employees whose UKG records are incomplete.
Common scoping pitfalls:
- Assuming UKG's I-9 module satisfies all electronic system standards: Configurations are typically validated against 8 CFR 274a.2(e) through (i) before going live.
- Skipping the custom field conversation: Decisions about whether sponsorship status is a yes/no flag, a visa-type dropdown, or a separate record are made upfront.
- Treating contractors like employees: Form I-9 is required for every employee hired to work in the United States. The regulation at 8 CFR 274a.1(j) uses a multi-factor right-to-control test (akin to common-law analysis) to distinguish employees from independent contractors, separate from the IRS W-2/1099 distinction; bona fide independent contractors are not covered.
- Ignoring dependents: Workflows covering spousal EADs or dependent status changes typically include those fields in scope.
Phase 2: Service Account Setup and API Configuration
Once scoping is complete, IT works with HR to create the UKG service account and configure the data flow. This phase has the most technical work but is also the most predictable when scoping in Phase 1 was thorough. UKG Pro exposes both REST and SOAP web services covering HR, payroll, talent, and workforce management data, so the immigration platform can read from UKG and, if configured, write status updates back. Hire dates flow through the Onboarding API, while I-9, visa, and work-authorization expiry fields are accessed through the core UKG Pro HCM Web Services against the employee profile.
The service account acts as the dedicated identity for the integration. Rather than running on any individual employee's login, the integration uses a credential that survives HR team turnover and maintains a clean audit trail.
Typical setup work includes:
- Creating the UKG service account through System Configuration, Security, and Service Account Administration, with access levels (Add, Delete, View, Edit) scoped only to the web services the integration requires.
- Generating the Customer API Key and base API URL from UKG's Web Services configuration, shared through a secure channel rather than email.
- Mapping UKG fields to the immigration platform schema: identity fields (legal name, DOB, home address), employment fields (hire date, job title, worksite address, FEIN), compensation (base salary, pay frequency for LCA tracking), sponsorship flags, and work authorization expiration dates.
- Configuring sync cadence and triggers: real-time webhooks for critical events like new hires flagged for sponsorship, scheduled syncs for routine refreshes, and manual triggers for edge cases.
- Setting up monitoring and alerting on the service account so failed syncs surface to HR rather than accumulating silently.
Streamlining UKG Integration with Alma: Once you engage Alma's business team, a dedicated immigration attorney coordinates directly with HR and IT leads. Alma handles field mapping, service account validation, and test data migration while your team focuses on organizational readiness. The platform includes white-glove migration from existing immigration vendors, so historical case data (past petitions, approval notices, expiration schedules) transfers without HR rebuilding it manually. Bi-weekly status calls with the lead attorney and immigration manager run during implementation, with direct platform access from day one.
Phase 3: Data Sync, Testing, and Compliance Go-Live
After service account configuration, the integration enters testing and phased rollout. This phase typically runs 1 to 2 weeks for companies with under 100 sponsored employees and can extend for larger populations with complex case histories. The goal is to validate that data flows correctly, expiration alerts fire on schedule, and electronic Form I-9 retention aligns with the standards at 8 CFR 274a.2 before cutting over from manual tracking.
Testing checkpoints for Standard Rollout:
- Timeline: 1 to 2 weeks for typical mid-market deployments
- Scope: Sandbox UKG tenant mirroring production data structures
- Validation criteria: New hire sync, expiration alert triggers, field consistency, audit trail verification
- Go-live readiness: HR, IT, and immigration provider sign-off on data accuracy
Testing checkpoints for Accelerated Rollout:
- Timeline: 3 to 5 business days for employers with clean UKG data and fewer than 25 sponsored employees
- Scope: Direct production test with limited cohort
- Validation criteria: Single-employee end-to-end test before full population migration
- Go-live readiness: Documented rollback plan if issues surface
Common sources of friction at this stage:
- Field mapping drift: UKG custom field names changed between scoping and testing, breaking the sync. A final field-mapping review before go-live helps catch this.
- Service account permission gaps: Permissions scoped too tightly block a legitimate data read. Testing every required field surfaces these gaps.
- Contractor records pulling through: The sponsorship workflow triggers on people who do not require I-9s. Confirming employee-type filters helps.
- Incomplete historical data: Migrating sponsored employees can reveal missing EAD expiration dates in UKG. Cleaning the data before depending on the sync prevents downstream alerts from misfiring.
Note: These timelines apply to integration setup itself. Ongoing case work (H-1B petitions, green card filings, RFE responses) runs on its own schedule through the immigration platform and is unaffected by integration go-live. USCIS posts case-type processing benchmarks at Case Processing Times.
Why UKG Integration Matters for Employer Compliance
Form I-9 Timing and Reverification
USCIS requires Section 1 of Form I-9 to be completed no later than the employee's first day of employment, and Section 2 within three business days of the first day (or by the first day if employment lasts fewer than three business days), per USCIS M-274 §4.0. An integration pulls the hire date from UKG and schedules the I-9 workflow automatically, reducing reliance on manual checklists.
For employees on temporary work authorization, reverification on Supplement B is completed before the expiration date. Federal anti-discrimination law at INA §274B (8 U.S.C. §1324b) prohibits employers from specifying which documents an employee must present or rejecting documents that reasonably appear genuine. Enforcement of these unfair documentary practices rules sits with the DOJ Civil Rights Division's Immigrant and Employee Rights Section (IER). As of February 2025, IER's enforcement priorities have been reoriented toward investigating discrimination against U.S. workers in favor of foreign visa workers, which is context employers factor into visa-sponsorship workflows. Employees choose which acceptable document to present, and integration surfaces deadlines without dictating the document.
Electronic Storage That Aligns With DHS Standards
UKG handles Form I-9 for many employers, but HR teams sometimes assume the HCM checkbox alone delivers full compliance. Standards at 8 CFR 274a.2(e) through (i) require any electronic system that generates, signs, or stores Form I-9 to maintain reasonable integrity, accuracy, and reliability controls; prevent unauthorized alteration; produce a secure audit trail capturing creation, completion, updating, modification, alteration, or correction of each electronic form; and retrieve forms within three business days of an inspection request. When UKG holds the I-9 and a separate platform holds visa petition data, HR teams identify which system is the system of record.
E-Verify Case Creation
Employers enrolled in E-Verify create a case no later than the third business day after the employee starts work for pay. An integration triggers E-Verify case creation from the UKG hire event, capturing Tentative Nonconfirmation responses so HR initiates the referral process instead of letting the case lapse into a Final Nonconfirmation.
E-Verify was unavailable from October 1 to October 8, 2025, during the 43-day federal shutdown that ran from October 1 through November 12, 2025. USCIS issued catch-up guidance when E-Verify resumed on October 8, 2025: employers had until October 14, 2025 to create cases for any employees hired while the system was down (using the Form I-9 hire date and the "Other" reason-for-delay code with the note "E-Verify not Available"); the days the system was offline did not count against the standard three-business-day deadline; and for mismatch and Tentative Nonconfirmation referrals during the lapse, employers added six federal business days to the Referral Date Confirmation date. The system has operated normally since.
How to Monitor Your UKG Immigration Integration
UKG Custom Field Dashboards
Writing expiration dates and visa status back to UKG custom fields keeps both data sets in the same dashboard where HR manages benefits, payroll, and performance. This avoids checking a separate platform to know which employees have work authorization expiring soon.
Tiered alert schedule (vendor and HR best practice; not a USCIS-required cadence):
- 180 days out: Evaluate extension, amendment, or change of status options.
- 90 days out: Active petition preparation window.
- 60 days out: Reverification planning for I-9 Supplement B.
- Expiration date: Hard stop; work authorization is reverified per INA §274A (8 U.S.C. §1324a).
Sync Health Monitoring
Silent sync failures are the biggest post-go-live risk. Monitoring on the service account, alerts on failed API calls, and quarterly permission reviews help catch problems early. Documenting the rotation schedule for API keys keeps credentials from expiring unexpectedly.
Pro tip: A quarterly review covering service account permissions, field mapping accuracy, and expiration alert delivery surfaces drift before it becomes a compliance gap.
UKG Integration Considerations by Company Stage
Startups (Under 50 Employees)
At this stage, most employers are sponsoring one to three employees and may not yet run UKG. A CSV-based handoff between HR and the immigration provider is often sufficient. Early-stage teams working with Alma get transparent flat-fee pricing, including O-1 New at $8,000 and EB-1A at $10,000 per the published rate card, so founders can budget before the first sponsored hire.
Growth-Stage (50 to 500 Employees)
This is where UKG integration starts paying back its setup cost. Growth-stage employers typically have mixed H-1B, TN, O-1, and green card populations, and manual tracking has caused at least one near-miss on an expiration date. Scheduled syncs, expiration dashboards, and a single attorney relationship covering all sponsored employees become essential.
Enterprise (500+ Employees)
Large employers typically have dedicated immigration program managers, multiple active LCAs, and global mobility workflows. Real-time API sync between UKG and the immigration platform is standard at this scale. Alma's enterprise offering supports volume discounts, ongoing partnerships, and monthly pricing models for larger foreign national populations.
Why Choose Alma for UKG-Powered HR Teams?
Read success stories from Alma's clients, including founders, researchers, and enterprise teams who scaled sponsored hiring without scaling legal headcount.
Traditional immigration firms send PDFs, CC paralegals, and ask HR to re-enter data the firm already has. Alma's modern immigration platform is built for HR teams that already run UKG and do not want a second system of record for employee data.
The Alma difference for UKG-powered HR:
- Integration-ready platform: Field mapping, service account validation, and historical data migration handled by Alma's team.
- Industry-high approval rate across sponsored case categories.
- Dedicated attorneys: Every case has a named attorney, not a rotating associate, so the same person HR contacts about an H-1B handles the EB-2 NIW or O-1 case too.
- Transparent pricing: Per-visa flat fees published on the pricing page, with payment plans available for businesses and volume discounts for larger populations and partner networks.
- RFE responses included in the case fee, not billed hourly.
- Bi-weekly status calls with the lead attorney and immigration manager for business clients.
Alma covers the visa stack that UKG-powered employers sponsor, including H-1B, L-1A, L-1B, TN, O-1A, O-1B, E-3, EB-1, EB-2 NIW, and EB-2 PERM.
Schedule a business consultation to scope an integration approach that fits your UKG configuration.
Frequently Asked Questions
UKG Pro includes Form I-9 functionality, and many employers use it as their I-9 system of record. Whether the configuration aligns with DHS standards depends on whether it meets the electronic system requirements at 8 CFR 274a.2 and whether the timing workflows enforce Section 1 by the first day of employment and Section 2 within three business days. A separate immigration platform typically handles visa petitions, work authorization tracking, and expiration alerts rather than replacing UKG's I-9 module, with integration keeping both systems aligned.
The work splits across all three. HR defines scope, identifies the sponsored population, and decides what data flows. IT creates the UKG service account, configures permissions, and manages credentials. The immigration provider configures the other side, maps fields, and runs testing. A typical setup takes 4 to 8 weeks from kickoff to go-live.
The immigration platform should hold case data, petitions, and expiration records independently of UKG so that switching HCM providers does not reset the immigration program. Data ownership and standard-format export are typically confirmed before signing any integration agreement. Alma supports white-glove migration from existing vendors as part of its business offering.
Employers enrolled in E-Verify and in good standing may be eligible to remotely examine I-9 documents under the DHS-authorized alternative procedure (effective August 1, 2023, and remaining in effect as of April 2026). The procedure asks the employer to examine copies of documents within three business days of the first day of employment, conduct a live video interaction during which the employee presents the same documents, check the corresponding Section 2 or Supplement B box, retain clear and legible copies, and complete required E-Verify training including fraud awareness and anti-discrimination. Otherwise, an authorized representative may physically examine documents on the employer's behalf within three business days of the hire date. The integration flags remote hires so the correct workflow (alternative procedure, authorized representative, or in-person review) is triggered automatically.
Employers who fail to properly complete, retain, or produce Forms I-9 for inspection may face civil money penalties per USCIS penalty guidance, with higher penalties for pattern-or-practice knowing-hire violations. Penalties are set within the regulatory range using five statutory factors at 8 U.S.C. §1324a(e)(5): business size, employer good faith, seriousness of the violation, whether the individual was an unauthorized alien, and history of previous violations. Beyond civil exposure, a pattern or practice of knowingly employing unauthorized workers can carry criminal consequences. Integration is not primarily about convenience; it is about making sure documentation holds up when an inspector arrives.


