An employee will need to be disconnected from ezLaborManager in two different situations:
if the employee is no longer required to record their time in ezLaborManager
if the employee leaves.
If an employee is no longer to be connected to ezLaborManager, the connection should be broken by unticking the ezLaborManager flag for the employee on the Appointment page. This immediately stops the transfer of shared employee details from ADP Freedom to ezLaborManager.
For example, if an employee is appointed to a new position that does not require them to record their time in ezLaborManager, the ezLaborManager flag would not be set on the employee's new primary appointment details. When this new appointment takes effect, the connection to ezLaborManager will be stopped automatically.
Note: Resetting the ezLaborManager flag in ADP freedom does not unset the Transfer to Payroll flag in ezLaborManager (which controls whether or not timecard details are transferred from ezLaborManager to ADP freedom for the employee). That will need to be maintained separately in ezLaborManager.
You can reinstate the transfer of shared employee details at any time by resetting the ezLaborManager flag for the employee.
An employee's termination date is one of the shared employee data fields.
So, if an employee's employment ends, their termination date is sent to ezLaborManager automatically and used to terminate the employee in ezLaborManager on this date. Once a P45 has been issued for the employee in ADP freedom, the connection with ezLaborManager for this employee is permanently broken.
Note: If an employee has been added to ADP freedom (and ezLaborManager) by mistake, you can use the System > Utilities > Delete Employee utility to remove the employee. See ezLaborManager Integration Employee Deletion.