Date
December 2025
Service
Implementation
Client
RSAC, Inc.

Project Overview
RSAC is one of the largest metals service centers in North America, operating across dozens of locations with a large and complex workforce. Their payroll process had grown increasingly difficult to manage across disparate systems, creating reconciliation headaches and compliance risk at scale. The engagement involved a full end-to-end Dayforce Payroll implementation — mapping their existing payroll rules and pay policies, configuring multi-entity structures, managing data migration from legacy systems, and running parallel payroll cycles to validate accuracy before go-live. The result was a standardized, auditable payroll operation built on a platform capable of growing with the business.


Key Highlights
Vision
RSAC runs its payroll operations on Dayforce. When three new companies joined their Family of Companies, those entities needed to be brought into the same environment — configured correctly, validated thoroughly, and handed off to a team that could run them independently. Vurtuo was brought in to make that happen.
The Challenge
Onboarding new companies into an existing Dayforce environment is not a simple extension of what is already there. Each entity arrives with its own pay policies, compensation structures, and compliance requirements that have to be mapped, configured, and tested before a single live payroll run can occur. For RSAC, doing this across three companies simultaneously meant managing significant configuration complexity without disrupting the payroll operations already running across the rest of the Family of Companies. The margin for error was low — a misconfigured pay rule or an untested edge case does not surface quietly.
Our Approach
Vurtuo began with a thorough discovery process across all three incoming companies — documenting pay policies, compensation structures, earning codes, deduction setups, and jurisdiction-specific requirements before any configuration work began. Nothing was assumed to match existing FOC configurations. Each entity was treated as its own implementation. Configuration was built to reflect exactly what was documented. Testing followed a structured validation process against that same documentation, ensuring every rule behaved as intended before parallel runs began. The engagement closed with full documentation and direct enablement for RSAC's internal team — so that ongoing management of these entities stayed in-house.
Scope
Vurtuo delivered the full implementation scope across all three incoming companies: pay policy mapping, FOC configuration and setup within RSAC's existing Dayforce environment, testing and validation against documented requirements, parallel payroll cycle execution, and training and documentation for RSAC's internal payroll team.
What Made This Complex
Implementing payroll for three companies concurrently meant managing distinct pay policy sets, earning structures, and compliance requirements in parallel — inside a live Dayforce environment that was already running payroll for the broader FOC. Configuration decisions for the incoming entities had to be made carefully to avoid downstream impact on existing setups. Pay policies across the three companies were not identical. Each required its own mapping effort, and where edge cases existed — overtime rules, multi-state compliance, specific earning code behavior — those were surfaced early and resolved before validation began rather than discovered during parallel runs.
Technological Foundation
All implementation work was executed within RSAC's existing Ceridian Dayforce environment. Vurtuo leveraged Dayforce's FOC architecture to configure each incoming company as a distinct entity — with its own pay rules, earning codes, deduction structures, and compliance configurations — while maintaining the centralized visibility and reporting that RSAC's payroll team depends on across the broader Family of Companies. Testing was conducted against documented pay policies, not assumptions. Every configuration was validated before parallel runs began, and parallel runs were used to confirm output accuracy at the line-item level before any live processing occurred.
Comprehensive Quality Requirements
Pay policies for each of the three incoming companies were fully documented before configuration began. Earning codes, deduction setups, overtime rules, and jurisdiction-specific compliance requirements were mapped to their Dayforce equivalents and validated against source documentation at every step. Testing covered both standard and edge-case scenarios — ensuring that pay rules behaved correctly not just under normal conditions, but in the situations most likely to surface errors in a live run. Parallel payroll cycles were executed for each entity, with output compared against expected results at the line-item level. Every discrepancy was investigated and resolved before go-live.
Enablement and Sustainable Skill Building
RSAC's internal payroll team was engaged throughout the implementation — not handed a finished configuration at the end. By go-live, the team understood how each entity was built, why decisions were made, and how to manage routine changes without external support. Full documentation was delivered covering configuration logic, pay policy mapping, and operational procedures for each of the three companies. Training was conducted directly on the configured environment, giving RSAC's team hands-on familiarity with what they were inheriting before the engagement closed.
Impact and Outlook
Three new companies are now live on Dayforce, running clean payroll alongside the rest of RSAC's Family of Companies. Pay policies are configured accurately, compliance requirements are enforced at the system level, and the administrative overhead of managing these entities manually has been eliminated. RSAC's internal team owns the configuration. They have the documentation to reference, the training to act on it, and the platform to execute payroll consistently at scale. As the Family of Companies continues to grow, the foundation is in place to bring additional entities into Dayforce using the same structured approach.


