This issue may be caused by the user account in Access Evo having an email address that is set on two separate employee records in SelectHR.
SelectHR will submit a deactivate command for a user account in Access Evo if the employee has an effective status of leaver within the SelectHR system, so if their email address is on two employee records, and one of them is a leaver, this may submit the deactivate command every night.
Below are some possible causes for this issue.
The email address on the Access Evo user is not unique in SelectHR
You should check the email address on the Access Evo User is unique in SelectHR, and that it exists on only one Person record.
Log in to the SelectHR Administrator Tool.
Click Import/Export Data.
Click Create an export definition.
Click Select the data to export.
Change the database to SelectHR.
Log in.
Copy the following SQL:
Select Person.Details.[Person Number], Person.Details.[First Name], Person.Details.Surname, Person.Details.[E-Mail], Details1.[Person Number] As [Overlapping Person Number], Details1.[First Name] As [Overlapping First Name], Details1.Surname As [Overlapping Surname], Details1.[E-Mail] As [Overlapping Email] From Person.Details Inner Join Person.Details Details1 On Person.Details.[E-Mail] = Details1.[E-Mail] Where Details1.[First Name] != (Details.[First Name]) And Details1.Surname != (Details.Surname)In the top left of the data export window, click Options, Paste SQL from clipboard.
Click Data.
If the impacted employee appears in the data, then this means their email address is present on two different employee records. If one of the records is marked as a leaver, this will cause the issue.
You should log in to the SelectHR website and remove the duplicate email from the incorrect record in order to resolve this.
The SelectHR test system is submitting the deactivation to your live Access Evo
If a live to test has been completed, and Members Integration has been left on, there is a chance that your test system may continue to send out of date data to Access Evo.
To check this:
Log in to the SelectHR test website with the HR 2.0 Menu Set.
Click Configuration, the Configuration, then click Workspace Settings.
Check to ensure that the Enabled checkbox does not have a tick.
If the Enabled option is ticked, untick it and click Save.
For good measure, it is also advised to turn off the Members Integration batch job using the test Admin Tool.
Log in to the Test Admin Tool.
Click Batch Jobs, then double click SYSTEM - Members Integration.
In the Enabled row, click on the small green dot with Yes next to it - this should turn red and say No.
Click OK.
This will ensure your test system never submits data to your live Access Evo.