A Let Down.
February 22, 2024
A Let Down.
Score 4 out of 10
Vetted Review
Verified User
Overall Satisfaction with Paylocity
We use Paylocity for payroll, HR records, onboarding, benefit enrollment, and employee engagement. Previously, we had separate systems for each item - Paylocity has helped streamline the employee (and admin) experience.
- Payroll process.
- Customer service.
- Reports
- Benefits / Open Enrollment implementation.
- Reduced payroll errors.
- Increased Open Enrollment effort for Admins.
- Better workforce visibility.
Payroll processing time has GREATLY reduced after switching from QBS. Onboarding has become a much smoother process for both the new hire and HR team. Open Enrollment is streamlined for the employees. Open Enrollment is a nightmare for HR to implement. Reporting is not always accurate and leads to multiple errors and added frustration and time on projects.
The employee engagement pieces have not had much impact on our remote team.
Paylocity makes Quickbooks look like a dinosaur for payroll processing - and if you're thinking about switching (for payroll only), I would do it! I previously used isolved with a former employer, and their system is much more employer-hands-on, which I prefer. If you're looking for more control over timelines of implementation, stick with isolved.
Do you think Paylocity delivers good value for the price?
No
Are you happy with Paylocity's feature set?
No
Did Paylocity live up to sales and marketing promises?
No
Did implementation of Paylocity go as expected?
No
Would you buy Paylocity again?
No
Paylocity Feature Ratings
Paylocity Support
Pros | Cons |
---|---|
None | Slow Resolution Poor followup Less knowledgeable Problems left unsolved Not kept informed Escalation required Difficult to get immediate help Need to explain problems multiple times Support doesn't seem to care |
I did not know that premium support was an option - however, I find it insulting that not everyone would receive the same experience.
Yes - Benefit reports don't work - this has not been addressed or changed since 2022, when I noticed after implementation.
none exist.