Before Arcoro sends an employee to Acumatica, it checks that the employee record has a Facility (Branch) value and a Department value. These two checks look at the employee data on the Arcoro side, not at anything inside Acumatica itself. If either value is blank, that employee is not sent to Acumatica at all. Both checks run in the same validation pass as several other required-field checks, such as identity and employment status, so one employee can show more than one of these messages in the same sync run.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Branch / Facility is required in Acumatica. The employee record will not be synced. Please correct this in the source system and try the sync again. | Write (Arcoro to Acumatica) | The employee's Facility field is null or an empty string. A value made up only of spaces is not caught by this check and will pass it. | Whole record skipped. The employee is not written to Acumatica this run. | Enter a Facility (Branch) value on the employee record in the source system, then re-run the sync. |
| Department is required in Acumatica. The employee record will not be synced. Please correct this in the source system and try the sync again. | Write (Arcoro to Acumatica) | The employee's Department field is null or an empty string. A value made up only of spaces is not caught by this check and will pass it. | Whole record skipped. The employee is not written to Acumatica this run. | Enter a Department value on the employee record in the source system, then re-run the sync. |
Confirming the Error
- Open Sync History and find the sync execution for the run in question.
- Find the step for the Acumatica connector and the Employees entity row within that step.
- Check the Errors column for that entity row. A non-zero count means at least one employee failed validation.
- Open the entity row to see the per-employee error list, and find the employee in question.
- Match the message against the fixed wording above (for example, is required in Acumatica), since these two messages carry no employee-specific values.
- While you are in that employee's error list, check for any other errors on the same employee, such as identity or employment status messages. All of these checks run together in one validation pass, so fixing only the Facility or only the Department value will not release the employee if another required field is still missing.
- Also check the Warnings, Information, and Failures columns for that entity row so you have the full picture.
Resolving the Error
- Identify the source system that feeds employee data into this Acumatica sync step. This is whatever Arcoro product is configured as the source connector for the sync.
- In that source system, open the employee record named in the sync log.
- Set a value for the field that maps to Facility (Branch). Set a value for the field that maps to Department. Both may need to be set if both messages appeared.
- Save the change in the source system.
- Re-run the Acumatica sync, or wait for the next scheduled run.
- In Sync History, open the new run and confirm the employee now appears under Added or Updated for the Employees entity, and 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.
- You confirm both Facility and Department are populated on the source record, a fresh sync has run, and the same error still appears.
- You cannot identify which field in your source system maps to Facility or Department.
- The employee still fails after this fix, and the remaining error is not one of the two messages in this article.