Dayforce is innovative, but needs improvement on the simple things.

Timesheets do not subtract unpaid meals and breaks from the total hours. This makes our employees extremely frustrated when they can't even see their hours for the week. Without doing manual calculations on their own, they don't even know their hours. Imagine an innovative time system, that doesn't even provide a total of paid hours. Imagine being an hourly employee with that type of system. The timesheets are very confusing and not user-friendly at all! Our employees really dislike Dayforce!

We use time collection periods. Dayforce seems to shy away from that form of payment. Implementation all but forced us to change our payroll process. We found a workaround, but it doesn't work well. We can't lock paid time periods correctly because of the way the time crosses periods. So we have paid time within the timesheets remaining unlocked. That just opens up a chance for issues. Once again, Dayforce really missed the mark on this one. This is a basic function of a time/payroll system. In addition, the way the system pays the employees for overlapping dates in the timesheets compared to the time collection period does not work well. We had a pay run where some employees were paid incorrectly due to this.

Accruals show up twice in the list of entitlements with no rhyme or reason why. Administrators have to recalculate each employee's accruals when this is found, which is often. The entitlement list is very awkward and cumbersome. Also, the way the time displays to the employees is confusing and they have trouble even understanding how much time they have left to take.

Payout of unused accruals to a salaried employee is very tedious. You have to fight the system and work backwards to pay the employee correctly. The system enters negative hours to keep them at the scheduled number of hours; therefore, payroll has to data enter a positive number of hours to offset what the system is doing.

The auto-population of taxes and the Dayforce tax engine creates large messes. The system will automatically change an employee's tax withholding when there is an address change, a department change, or job change. There is no report to tell the administrator that the system did this. Therefore, every single change requires an audit of the individual's tax set-up to determine if the system changed their taxes. The auto-population is not correct and we have had instances of the system just stopping withholding, taxing an individual for two different states, determining a location is in another state even though we have the proper address entered. This function misses the mark entirely! The old Ceridian HPW was way easier to use.

The reports for auditing payroll are awful. The employee changes report for auditing during payroll processing is pages and pages of irrelevant information and multiple lines for one employee change. It's hard to read because the report lists inserted records for every single line on a screen. On the other side, the report does not give you changes that you need to know, like tax withholding changes that the system automatically changed.

The cost of services is way too much. We need a simple export with 4 fields of data, but the cost to have the export built is too much for our company.

We need an export of a report we have built in the system, but after many time consuming meetings it was determined that the system cannot do the export. For such an innovative system, we can't understand why it cannot export our data.