The situation
The client operated with an established internal employee ID standard that had been in use long enough to be deeply embedded in downstream systems and business processes. When the organization moved to ADP Workforce Now (WFN), a fundamental incompatibility surfaced: ADP WFN could not natively accommodate the client's existing ID format.
Abandoning the ID standard was not a viable option. Doing so would have required extensive remediation across Active Directory and other dependent systems, creating risk and operational disruption that outweighed any benefit of conforming to ADP's native identifier scheme.
How we approached it
RJ Reliance designed and built a custom integration layer that sits between ADP Workforce Now and Active Directory. Rather than forcing the client to adopt ADP's native ID convention, the solution translates and maps identifiers at the integration level, ensuring that the client's ID standard is preserved end-to-end.
The engineering work focused on reliability and maintainability: the integration handles the identity mapping consistently across employee lifecycle events—new hires, changes, and terminations—so that records remain synchronized across both platforms without manual intervention.
The solution was built to be transparent to end users and administrators. ADP WFN continues to function as the system of record for workforce data, while Active Directory reflects the client's own ID convention, keeping access management and downstream processes stable.
The outcome
The client was able to adopt ADP Workforce Now without sacrificing the internal ID standard that their broader systems infrastructure depended on. The custom integration resolved what had been a hard blocker in the implementation.
Ongoing identity synchronization between ADP WFN and Active Directory now occurs without manual reconciliation, reducing the administrative overhead that would otherwise have accompanied any mismatch between the two platforms.
By engineering around the platform constraint rather than working against established business logic, the client retained continuity in their identity and access management practices while gaining the capabilities of a modern HCM platform.