Arcoro Payroll requires a minimum set of identity fields before it will accept an employee record: a last name and a complete home address. It also refuses to accept the same employee twice in one sync or an employee identifier that already belongs to a contractor record. When any of these checks fail, Arcoro Payroll rejects that one employee and the record is left out of the sync. Nothing is deleted or changed in Arcoro Payroll; the record simply never arrives.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Employee Last Name is required by Payroll. This record will not be synced. Correct the data in the source system and execute the sync again. | Write (Arcoro to Payroll) | The employee record has no value in the Last Name field. | Record skipped | Add a last name to the employee in the source system. |
| Employee does not have a Home Address and this is required by Payroll. This record will not be synced. Correct the data in the source system and execute the sync again. | Write (Arcoro to Payroll) | The employee has no address record of type Home (primary) and no address record of type Home (secondary) either. Arcoro Payroll looks for Home first, and only falls back to a secondary Home address if no primary Home address exists. | Record skipped | Add a Home address to the employee in the source system. |
| Employee Address 1 is required by Payroll. This record will not be synced. Correct the data in the source system and execute the sync again. | Write (Arcoro to Payroll) | A Home address record was found, but its Address Line 1 field is blank. | Record skipped | Fill in Address Line 1 on the employee's Home address in the source system. |
| Employee City is required by Payroll. This record will not be synced. Correct the data in the source system and execute the sync again. | Write (Arcoro to Payroll) | A Home address record was found, but its City field is blank. | Record skipped | Fill in City on the employee's Home address in the source system. |
| Employee State is required by Payroll. This record will not be synced. Correct the data in the source system and execute the sync again. | Write (Arcoro to Payroll) | A Home address record was found, but no State/Province is selected on it. An empty selection, not just an empty string, triggers this. | Record skipped | Select a State/Province on the employee's Home address in the source system. |
| Employee Postal Code is required by Payroll. This record will not be synced. Correct the data in the source system and execute the sync again. | Write (Arcoro to Payroll) | A Home address record was found, but its Postal Code field is blank. | Record skipped | Fill in the Postal/ZIP code on the employee's Home address in the source system. |
| Employee Postal Code is required to contain between 5 and 9 numeric characters. This record will not be synced. Correct the data in the source system and execute the sync again. | Write (Arcoro to Payroll) | A Home address record was found and Postal Code has a value, but after stripping every non-digit character (hyphens included) fewer than 5 or more than 9 digits remain. A code made only of letters counts as zero digits and also triggers this message. This is a separate check from the one above; a blank Postal Code triggers the required message instead, never this one. | Record skipped | Correct the Postal/ZIP code on the employee's Home address so it contains 5 to 9 digits. A ZIP+4 with a dash (12345-6789) is fine; the dash is ignored when counting. |
| A Contractor already exists in Payroll with the same Identifier '[employee identifier]'. This record will not be synced. Correct the data in the source system and execute the sync again. | Write (Arcoro to Payroll) | The employee's identifier matches the identifier already recorded against an existing Contractor (1099) record in Arcoro Payroll. | Record skipped | Use a different, unique identifier for the employee in the source system, or resolve the contractor duplication before re-running the sync. |
| More than one employee from the source system matched the same employee in Payroll. Only the first one will be synced (employee '[employee identifier]' will be ignored). | Write (Arcoro to Payroll) | Two or more employee records from the source system resolved to the same existing Payroll employee in this sync run. Arcoro Payroll matches in this order: a linked Arcoro user, then a linked Arcoro person, then the source system's record ID, then the employee identifier. Whichever source record claims the match first in the run wins; every later record that resolves to that same Payroll employee is ignored. The identifier named in the message is the record being ignored, not the one that was kept. | Record skipped | Identify why two source records point at the same Payroll employee (for example a duplicate employee record in the source system or a shared linking ID) and remove or correct the extra one. |
| An Employee with Source System Id '[source system record id]' has been sent to Payroll multiple times. Only the first Employee received will be processed and saved. Correct the source data and run the sync again. | Write (Arcoro to Payroll) | The same source system record ID was sent to Arcoro Payroll more than once within the same sync run. This check runs before Arcoro Payroll even tries to match the record to an existing employee, and it is not limited to active employees; any repeat of the same ID in the run triggers it. | Record skipped | Find and remove the duplicate record for that source system ID in the source system, then re-run the sync. |
The Last Name, Home Address, Address 1, City, State, and Postal Code messages carry no employee name or ID in the text itself. In the sync log, each of these appears as its own row under the employee entity for that sync step, and the row itself is labeled with that employee's identifying information from the source record. Use that row label, not the message text, to tell which employee failed. The Contractor Duplicate, Already Matched, and Duplicate Value messages do include an identifier in the message text, shown above in brackets.
Confirming the Error
- Open the sync execution for the connector and date in question.
- Find the step for the Arcoro Payroll connector.
- Open the Employee entity row for that step.
- Check the Errors column for that row. A non-zero count means at least one employee was rejected during this run; open the errors list to see the individual messages.
- In the errors list, match on the fixed part of the sentence (for example, "Employee Last Name is required by Payroll"), not on the quoted value, since the quoted value changes per employee.
- The Added, Updated, and Unchanged columns tell you how many employees did sync successfully in the same run; reporting one missing employee among many synced ones is consistent with these messages.
- These ten messages do not use the Failures column. If Failures is non-zero for this entity, that is a different condition and is outside this article; treat it separately.
Resolving the Error
Last Name
- In the source system, open the employee record named in the sync log row.
- Enter a value in the Last Name field.
- Save the record in the source system.
- Re-run the sync and confirm the employee no longer appears in the Employee entity's errors list, and instead shows up under Added or Updated.
Home Address and Postal Code
- In the source system, open the employee record named in the sync log row.
- Confirm the employee has an address record marked as Home (not Work). If none exists, add one.
- Fill in Address Line 1, City, and select a State/Province on that Home address.
- Enter a Postal/ZIP code with 5 to 9 digits. A ZIP+4 with a dash is acceptable.
- Save the record in the source system.
- Re-run the sync and confirm the employee moves out of the errors list into Added or Updated.
Duplicate as Contractor
- Note the employee identifier quoted in the message.
- In Arcoro Payroll, confirm whether a Contractor (1099) record already uses that same identifier.
- Decide whether the identifier on the employee record in the source system should change, or whether the existing contractor record needs to be corrected first.
- Re-run the sync after the identifier conflict is resolved and confirm the employee moves out of the errors list.
Already Matched and Duplicate Value
- Note the identifier quoted in the message.
- For Already Matched, look in the source system for more than one employee record that could resolve to the same Payroll employee, for example, two records sharing the same linking ID or employee identifier.
- For Duplicate Value, look in the source system for more than one employee record sharing the exact same source system record ID.
- Remove or correct the extra record in the source system so only one record maps to that Payroll employee.
- Re-run the sync and confirm only one employee record appears for that identifier, with no error against it.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- The error persists after the source data has been corrected and the sync re-run.
- The log text does not match any message in the table above.
- You cannot tell which of two records is the intended one for an Already Matched or Duplicate Value error, or dispute which record should be treated as the duplicate.
- A Contractor Duplicate error appears, but no contractor with that identifier should exist in Arcoro Payroll.