If an employee is added to ADP freedom by mistake and the ezLaborManager integration module is enabled then, because ADP freedom is the point of entry for new starters for both applications, it is assumed that the employee was also added started erroneously in ezLaborManager.
So, when you delete the employee from ADP freedom (using System > Utilities > Delete Employee) a corresponding delete employee instruction is sent to ezLaborManager.
How ezLaborManager responds to this instruction depends upon whether or not any timecard data has already been entered for the employee. If it has, the employee will be treated as terminated as opposed to just being removed.
Note: There is a utility in ezLaborManager (System utilities > Delete timecards) that can be used to clear down the timecards. If you wish to remove the employee from both applications, you should first use this utility to clear down the timecards in ezLaborManager and then use the System > Utilities > Delete employee utility in ADP freedom to delete the employment.
ADP freedom does not instruct ezLaborManager to delete an employee that is marked as a ‘no show’. Changing the employment status of an existing employee to ‘no show’ will result in an update being sent to ezLaborManager to make the employee inactive. If you subsequently choose to remove the employee from ADP freedom they should use the Delete utility.
Tip: If you do not wish to delete the employee from ADP freedom but wish to disconnect the employee from ezLaborManager, see How to disconnect an employee from ezLaborManager.