Payroll requires a minimum set of identity fields, a last name, and a complete home address, before it will accept an employee record. It also requires that each employee arriving in a single sync run be traceable to exactly one person, both within the batch being sent and against people already saved in Payroll. When any of these checks fail, Arcoro blocks that one employee record from being written to Payroll and logs the reason. The employee record is left exactly as it was in Payroll (unchanged if it already existed, not created if it did not) until the source data is corrected.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| 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 (source to Payroll) | The employee has no address record marked as a Home address type at all (neither a primary nor a secondary Home address is present). | Record skipped | Add a Home address for 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 (source to Payroll) | A Home address exists, but its Address 1 (street) line is blank. | Record skipped | Fill in Address 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 (source to Payroll) | A Home address exists, but its City field is blank. | Record skipped | Fill in City on the employee's Home address in the source system. |
| 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 (source to Payroll) | The employee's Last Name field is blank. This check does not depend on the address checks. | Record skipped | Enter a Last Name for the employee 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 (source to Payroll) | A Home address exists, and after stripping out everything except digits (dashes and letters are removed first), the postal code has fewer than 5 or more than 9 digits. Note: a blank postal code has zero digits, so this message and the Postal Code Required message below can both appear together for the same record. | Record skipped | Enter a valid 5 to 9 digit postal code 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 (source to Payroll) | A Home address exists, but its Postal Code field is blank. | Record skipped | Enter a postal code 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 (source to Payroll) | A Home address exists, but its State field is blank. | Record skipped | Enter a State on the employee's Home address in the source system. |
| An Employee with Source System Id '[the source system's employee 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 (source to Payroll) | Two or more employees sent in the same sync run share the same Source System Id (matched without regard to upper or lower case). The first one received is kept; each later one with that same id triggers this message. | Record skipped | In the source system, make sure each employee has its own unique Source System Id, then remove or merge the duplicate. |
| A Contractor already exists in Payroll with the same Identifier '[the employee identifier]'. This record will not be synced. Correct the data in the source system and execute the sync again. | Write (source to Payroll) | The employee's Identifier (matched without regard to upper or lower case) already belongs to a Contractor record that exists in Payroll. This is checked against records already saved in Payroll, not just the current run. | Record skipped | In the source system, change the employee's Identifier so it no longer matches an existing Payroll contractor. If that is not appropriate, have the existing Payroll contractor record reviewed 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 '[the employee identifier]' will be ignored). | Write (source to Payroll) | Two or more employees in the same sync run resolve to the same existing Payroll employee record. The match is tried in this order: Arcoro User Id, then Arcoro Person Id (both matched with exact case), then Source System Id, then Employee Identifier (both matched without regard to upper or lower case). The first record to claim the match is kept; each later record that resolves to that same Payroll employee triggers this message, naming the ignored record's Employee Identifier. | Record skipped | Identify the two source records pointing at the same Payroll employee (compare Employee Identifier, Source System Id, and any Arcoro person or user id) and correct the source system so each person has one distinct identifier. |
Confirming the Error
- Open the sync execution your Payroll connector in Sync History.
- Find the step for the Payroll connector and open the Employee entity row.
- Check the Errors column for that row. A non-zero count means one or more employee records were skipped; open the errors list for the entity to see the individual messages.
- Match on the fixed part of each sentence (for example, "is required by Payroll" or "has been sent to Payroll multiple times"), not on the quoted id or name values, since those vary per employee.
- If the same employee shows more than one message (for example, both Postal Code messages), treat them as one root cause, not two separate problems.
- The Added, Updated, and Unchanged columns will not include any employee that appears in the Errors list for that run.
Resolving the Error
Last Name, Home Address, Address 1, City, State, Postal Code
- In the source system that feeds this connector (for example, Core HR or Arcoro Time (formerly ExakTime), whichever the connector is configured to read from), open the affected employee's record.
- Add or correct the missing field named in the message: Last Name, Home Address, Address 1, City, State, or Postal Code.
- For the postal code, confirm it contains between 5 and 9 digits once any dashes or letters are removed.
- Save the change in the source system.
- Re-run the sync and confirm the employee no longer appears in the Employee entity's Errors list.
Duplicate Source System ID
- In the source system, search for other employees sharing the same Source System Id shown in the message.
- Correct or remove the duplicate so each employee has a unique Source System Id.
- Re-run the sync and confirm the record now appears in Added or Updated instead of Errors.
Duplicate as Contractor
- In the source system, check whether the Employee Identifier shown in the message was meant to belong to an employee or a contractor.
- If it should be an employee, change the Identifier in the source system so it no longer collides with the existing Payroll contractor.
- If the existing Payroll contractor record is stale or wrong, escalate so the Payroll contractor record can be reviewed before the sync is re-run.
- Re-run the sync and confirm the record no longer appears in the Errors list.
Already Matched
- Note the Employee Identifier named in the message; that is the record being ignored.
- In the source system, look for another employee record with the same Employee Identifier, Source System Id, Arcoro Person Id, or Arcoro User Id as the ignored record.
- Correct the source data so each person has one, and only one, distinct identifier.
- If the duplicate cannot be identified from the source system alone, escalate.
- Re-run the sync and confirm the record no longer appears in the Errors list.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- The message persists after the source data has clearly been corrected and the sync has been re-run.
- For the Already Matched message, the second (duplicate) source record cannot be located by comparing identifiers in the source system.
- The message text in the log does not match any row in the table above.
- The log text reads like it came from Payroll itself rather than from Arcoro (for example, unfamiliar wording or a Payroll-specific error code), rather than one of the ten messages listed here.
- The entity row shows a non-zero Failures count in addition to, or instead of, Errors; that is a different condition than the record-skip behavior described in this article.