Dayforce is effective in basic payroll and benefits, but won't work for complex organizations
October 23, 2018
Dayforce is effective in basic payroll and benefits, but won't work for complex organizations
Score 5 out of 10
Vetted Review
Verified User
Overall Satisfaction with Ceridian Dayforce
Dayforce is currently being used as a shared service platform for HR, payroll, and benefits, for my company, as well as, 20+ subsidiary companies under our service umbrella. It allows us to handle our payroll and workforce management needs, including time away from work, timesheets/timeclocks, time-off requests. Also, we use Dayforce for our benefits enrollments, and life event changes. Basic HR information is also stored.
- Payroll - We have many different pay groups and pay frequencies across the many different companies in which we provide service to. The pay process is generally reliable, and consistent across many different variables.
- Benefits - Dayforce has been able to successfully accommodate the many different plans, options, and rates. The straight-forward Open Enrollment process allows employees to easily input any benefit changes on an annual basis.
- Support Team - Over the last 12 months the quality of the Support team has greatly improved. With a unique company, we tend to have a lot or unique situations, so we end up turning to support to get advice or clarification on many items. They are generally quick, efficient, and follow up to make sure the answer is satisfactory.
- System Administration - The organizational setup including the Jobs/Positions table, and the department tables are universal for the entire platform. I wish we had the ability to separate these out by legal entity to help delegate some of the responsibility within a complex organization.
- HR Admin - The Employee Data Mapping Rules generally end up causing more problems, than the time and effort it is supposed to save. They provide only a limited number of fields to help generate other data of, it becomes nearly impossible to truly expedite the hiring process.
- Silverlight vs. HTML - I know this is an issue that they are gradually solving, but it is still a critical issue that was not solved soon enough. Especially from an administrator's point of view, I hate having to toggle between IE and Chrome. Chrome is faster and much more reliable; however, not all screens are compatible.
- Dayforce has limited our ability to provide effective support to our subsidiary companies within our service umbrella. Due to the org structure/setup, we are unable to delegate many of the desired responsibilities to the subsidiary HR personnel, which results in additional manual effort on our end.
- The whole idea of "One Set of Records in One System" is something that Dayforce over-inflates the idea of. Their are still many difficulties with having each of the different modules, "talk" to each other, whether it is Benefits and Payroll, Payroll and HR, etc
- Many of the ancillary modules that Dayforce releases are not fully thought out and developed at the time of release, which furthers the negative view of Dayforce that many our of Admins and Employee have of the system. We have tried to utilize Dayforce for their Performance Management, Recruiting, and Compensation at various points over the last three years, and all have failed us in basic ways.
Dayforce does do an effective job at enforcing payroll compliance. One of the unique aspects of our organizations, is that we operate in nearly every state in the USA. Keeping track of state and local tax laws, Overtime requirements, etc, is burdensome. Dayforce helped us setup this up correctly he first go around, and now we rarely have to worry.
I completely disagree with the way Dayforce portrays they single application and/or single record model. Their are too many aspects of the system that do not allow us to operate under this guise. Perhaps it is our multi-legal entity model, that becomes a problem for Dayforce, but we truly lack the ability to handle our workforce from multiple locations/people.
Although, I don't feel that it is effectively "one model", at least it allows us to not worry about importing/exporting data between systems on a regular basis. It is always easier to be able to jump back and forth between different modules to check on an issues, than to have to look in a completely different system.