HCSS requires every employee to have a valid Occupation value, and that value must match an active Pay Class code that exists in HCSS. Arcoro checks this on every employee write, for every employee, regardless of which sync scopes are turned on. If the Occupation value is missing, too long, or does not match any active Pay Class in HCSS, the employee record is rejected, and nothing for that employee is written to HCSS.

Messages in this article

Both messages are paired with a general message on the same employee stating that the employee has one or more validation errors and will not be synced. That paired message is expected whenever either of the two messages above appears and does not need separate troubleshooting.

Confirming the Error

1. Open the sync execution in Sync History for the connector and date in question.
2. Open the step for the HCSS connector.
3. Find the Employees entity row. Check the Errors column; either message in this article will show as at least one error on that row. A Failures count does not apply to this family; these are per-employee validation errors, not connection failures.
4. Open the entity row to see the errors list for that employee.
5. Match on the fixed part of the sentence, not the value in quotes. For the first message, match on "exceeds max length of 100. Record will not be synced." Note the message spells Occupation as "Ocuppation" in the shipped text. Search using that exact spelling, or the search will not find a match. For the second message, match on "with a Pay Class in HCSS. Record will not be synced."

Resolving the Error

Occupation Exceeds Max Length of 100

1. In Arcoro, open the employee record and find the Occupation field.
2. Shorten the value to 100 characters or fewer.
3. Save the change in Arcoro.
4. Re-run the sync and confirm the employee now appears under Added or Updated instead of Errors.

Could Not Match Occupation with a Pay Class in HCSS

1. Confirm what Occupation value is set on the employee in Arcoro. If the message shows "Not Set" in place of a value, no Occupation is set on the employee at all; you must enter one.
2. Compare that value to the Pay Class codes configured in HCSS. The match is not limited to the employee's own facility or Business Unit; it checks the Pay Class codes across every Business Unit in your HCSS company. Leading and trailing spaces and letter case are ignored when matching.
3. If a Pay Class with that code does not exist in HCSS at all, it must be created in HCSS before it can match.
4. If a Pay Class with that code already exists in HCSS but is marked inactive, it is treated the same as not existing. Only active Pay Classes are eligible to match. You must either activate that Pay Class in HCSS or point the employee's Occupation value to a different, active Pay Class code.
5. If the Pay Class code is correct and active in HCSS, correct the Occupation value in Arcoro to match the HCSS Pay Class code exactly (aside from case and leading/trailing spaces).
6. Re-run the sync. There is no separate waiting period; re-running the sync reloads the current list of Business Units and Pay Classes from HCSS before it re-checks the employee.
7. Confirm the fix by checking that the employee entity row no longer lists this error and the employee appears 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.

• You confirm the Pay Class code is active in HCSS and spelled exactly as it appears in Arcoro, but the error still occurs after re-running the sync.
• The sync fails before any employee rows appear at all, rather than producing per-employee errors. That points to a preload failure (no Business Units or no active Pay Classes could be loaded from HCSS at all), which is addressed here.