How does the system decide whether to create a new employee or update an existing one?
When you import employees from a file, the system relies only on the Employee Code column to decide what happens to each row in the file:
| Code value in the row | What happens |
|---|---|
| Code exists in the system | Updates the details of the employee with this code. |
| Code does not exist in the system | Creates a new employee. |
| Cell is empty | Creates a new employee, and the system generates their code automatically. |
The system does not use the Official ID, email address, or phone number to decide whether to create or update. To update an existing employee, enter their code in the file exactly as it appears in the system, because any difference in the code creates a new employee instead of updating the existing one.
🛈
Notes:
- When updating, you can edit all fields except the status, since the import file has no status column. New employees are created with an active status.
- If the same code is repeated in the file, the first row is imported and the following rows fail.
- When updating, if the Official ID in the row belongs to another employee, the row fails with the message Official ID already belongs to another employee. When creating, if the Official ID already exists in the system, the row fails with the message Official ID already exists in the system.
- Only creation rows count against the employee and user slots available in your subscription; update rows do not.
- The activity log records Employee Created (Import) or Employee Updated (Import), depending on the operation.