Paylocity Review 11.15.24

My recent experience with Tonnisha turned out well, and I hope we continue to move forward with positive momentum with upcoming payroll and Open enrollment rollouts. These are some of the issues Tonnisha addressed. Reporting and extracting information needed seems to be a continuous pain point for my staff. Reports that will break
out Nevada and/or California EE’s separately for Payroll tax preparation
and filing. We currently are doing this manually from a more extensive report


pulled from Paylocity. I am sure it is a report we can manage and create from the reports provided by Paylocity, but I need help extracting the “filter” data we need and then creating the template that we can schedule to run with each payroll. Scheduling reports that
will automatically generate with each payroll
***The answer to this was a $375.00 cost to TTL in order to create a CUSTOM REPORT which I am sure we are not the only CA/NV employer, and these reports must be a usual experience for Tax purposes.

Payroll Run issues:


One of the issues I
experienced directly this week while going through a payroll run with one
my staff members. We created the batch, and then while comparing the payroll against the time and labor report, ALL the hours were incorrect on EVERY employee. We could not find out why, we tried
multiple solutions based on the AI and Help menu

but were not able to find a solution. This took
A LOT of our time to resolve. We decided to call in and speak to our “rep,” which is rarely available and instead spoke to a defaulted rep. We could tell early on that she was new and not all that well-versed in the Paylocity functions. She ran us through creating three different batches to find what we were looking for, wanted us to configure our batch export differently, etc. Finally, we decided to scrap all of the batches and just rerun them as we had initially done, and then the batch tied out. As you can imagine when trying
to be timely with payroll that is due at 3pm that day this was a bit of a
struggle. There was not resolution, and the support team had no answer to why this happened - A bit frustrating