Overview

Every payroll migration has a number nobody wants to say out loud. For Ingredion's Time to Pay (T2P) program, that number was 148.

These were the configuration gaps sitting between a live Kronos UKG Dimensions time system and ADP GlobalView payroll, spread across a union-governed workforce while the company was simultaneously preparing to expand operations into Mexico.

Ingredion, with roughly 12,000 employees across the US and Canada and expansion plans into Mexico, needed to unify its time-and-attendance infrastructure without disrupting payroll for a workforce governed by union agreements.

The Challenge

The 148 configuration gaps spanned multiple downstream systems, and every one of them sat somewhere between an employee clocking in and getting paid correctly.

Closing those gaps had to happen without interrupting operations across manufacturing sites that don't pause for a system migration.

Our Approach

Stiletto coordinated the resolution of all 148 configuration gaps, reaching across ADP GlobalView, Fidelity, Sunlife, and Aon to close payroll-critical exceptions, benefits integrations, and compliance configurations.

The team then ran end-to-end testing across the full T2P ecosystem —from time entry through payroll and every connected downstream system.

On the ground, that meant deploying timeclocks across six manufacturing sites: Indianapolis, Cedar Rapids, London, Cardinal, NKC, and Argo. Some locations required 16 to 18 new devices, deployed through a sprint structure that remained on track through December.

A weekly governance cadence kept ServiceNow, RingCentral, SAP Finance, and Workday aligned—ensuring connected platforms were working together rather than operating in isolation.

Key Metrics

Key Takeaways

• Configuration gaps compound across vendors. Closing them requires one coordinated remediation plan across every downstream system—not isolated fixes made platform by platform.
• Hardware rollout and governance have to move on the same calendar. A sprint structure only holds when devices, manufacturing sites, and stakeholders are sequenced and coordinated together.
• An expansion shouldn't wait for a system to earn trust after the fact. The operating model needs to be demonstrably stable before it scales into a new country.