When employees are rehired in Prism, their rehire date is successfully pushed to Swipeclock WorkforceHub; however, their status remains inactive. This requires manual intervention to update each employee's status to active within Swipeclock, which can be time-consuming and prone to oversight, especially when processing multiple rehires.
In Prism, we retain the original termination date to preserve historical employment data. When an employee is rehired, a rehire date will be added, but we do not remove the termination date. Because Swipeclock still sees the termination date in the employee record, it maintains the status as Inactive, even though the employee is considered active again in Prism.
This automation would streamline the rehire process, reduce manual work, and improve data consistency across platforms.
Guest
We have a lot of seasonal clients, so this is critical for us to move people over to nextgen.