When Arcoro writes an employee to Sage 100, it first matches the employee to an existing Sage 100 employee using the Employee Identifier field. If two different employees coming from the source system both resolve to the same existing Sage 100 employee, only the first one processed is written. Every later employee that matches that same already claimed Sage 100 employee is skipped entirely for this run, and this message is logged in its place.
This only happens when the Employee Identifier matches an existing, active Sage 100 employee. It does not happen when two new hires with the same identifier are both being created for the first time, because each new hire gets its own blank Sage 100 record and cannot collide with another new hire in the same way.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Duplicate Employee updates sent from source system matched on [match field, always "Employee Identifier"]. Source Employee [Employee Identifier of the skipped record], Sage 100 Employee [Sage 100 employee code that was already claimed]. | Write (Arcoro to Sage 100) | Two source employees resolve to the same existing, active Sage 100 employee by Employee Identifier. The one processed first is written normally; this message is logged for every later one that matches the same target. | Record skipped | Give the two colliding source employees unique Employee Identifier values, or deactivate the duplicate source record. |
Other Duplicate Messages and Where They Live
| If the log says | Go to |
|---|---|
| Duplicate Compensation records received from the source system, only the first record will be processed. | Sage 100: Compensation, pay rate, pay group, pay frequency |
| Multiple Direct Deposit updates were sent for the same record, only the first record will be processed. | Sage 100: Direct deposit and banking |
| Multiple records sent from source system for this state, only the first record will be processed. | Sage 100: Tax setup (federal, state, local) |
| Duplicate Employee, Employee Status, Employee Type, Fringe, Pay Group, Position, or Union records read back from Sage 100 while the sync was setting up its lookup data, or multiple active employees found with the same version while loading employees for matching. | Sage 100: Preload or lookup data setup failure |
Confirming the Error
- Open the Sync History entry for the run in question.
- Open the step for the Sage 100 connector.
- Find the Employees entity row for that step. Note the Errors, Warnings, Information, Failures, Added, Updated, and Unchanged counts shown for that row.
- Open the Employees row's errors list and look for a message that starts with "Duplicate Employee updates sent from source system matched on Employee Identifier." Match on this fixed opening text, not on the values that follow it, since those values change per employee.
- Read the two values in the message. Both the "Source Employee" value and the "Sage 100 Employee" value will show the same Employee Identifier. This is expected and is not a typo. It is the identifier of the employee record that was already claimed by an earlier employee in the same run. The message does not tell you which other source employee claimed it first.
- To find the other, earlier employee, search the same run's Employees results for a different employee whose Employee Identifier matches the value shown in this message and whose outcome was Added or Updated rather than an error.
- A non-zero Failures count on this row is not caused by this message. This condition logs as an Error, and the record's outcome is a skip, not a Failure. Treat a non-zero Failures count as a separate issue.
Resolving the Error
- In Arcoro, find both employees that share the Employee Identifier value shown in the message.
- If the two employees are meant to be two different people: correct the Employee Identifier on whichever one should not be matching the existing Sage 100 employee, so each employee has its own unique identifier.
- If the two employees are actually the same person represented twice (for example, a duplicate profile created during onboarding or a rehire): deactivate or merge the duplicate Arcoro employee record so only one active record with that identifier remains.
- Re-run the sync for Employees.
- Confirm the fix worked by checking that the Employees row's Errors count no longer includes this message, and that the previously skipped employee now shows under Added or Updated.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- There is only one employee with that Employee Identifier and cannot find a second one in Arcoro, even after checking inactive or terminated employee records. The duplicate is on the Arcoro (source) side, not in Sage 100, since Sage 100 records the sync matches against exclude archived employees entirely. If a thorough search of Arcoro, including inactive and terminated employees, still turns up only one record, escalate to engineering with the sync log entry.
- You correct or deactivate one of the two employees, but the same message reappears on the next run for the same identifier.
- The overall Employees step failed completely instead of skipping a single employee. That points to the preload duplicate condition, not this one. Route to the preload article and escalate only if it is unclear which condition applies.