These three messages are the only tax-related messages in Core HR that are logged as Errors instead of Warnings. One of them occurs when an employee's Filing Status for federal withholding is missing or unset. The other two occur on Work States, which is the list of states Core HR uses for state tax setup, not on the employee record itself. In all three cases the affected item is skipped for that sync run, but the rest of the sync continues normally.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Core HR does not support Null values for FederalFilingStatus. The Federal Withholding record will not be saved. Other changes will still be processed. | Write (into Core HR) | The Federal Taxes scope is enabled for the connector, and the employee's incoming Filing Status is either not set or is the "not specified" placeholder value. | Field skipped only. The Federal Withholding record is not saved. The employee record and every other enabled scope for that employee are still written. | Set the employee's Filing Status in the source system feeding this connector, then resync. |
| Missing State. Item will not be synced to Core HR. | Write (into Core HR) | A Work State item is sent with a blank or whitespace-only Value. | Whole record skipped. That one Work State item is not written to Core HR. | Populate the state value for that Work State item at the source, then resync. |
| A Work State with Value of '[work state value]' has been sent to Core HR multiple times. Only the first Work State with this Value will be saved. Employee's associated with any of the duplicate Value will not have their Work State set correctly. Correct the source data and run the sync again. | Write (into Core HR) | Two or more Work State items sent in the same sync run have the same Value (case-insensitive). Only items sent earlier in the same run count; Core HR's existing stored Work States are not part of this check. | Whole record skipped. Every Work State item after the first with that Value is not written. The first one saves normally. | Remove the duplicate value from the source data so each Work State value appears once, then resync. |
Confirming the Error
- Open the sync execution for the run in question.
- Find the step for the Core HR connector in that execution.
- For the Filing Status message, open the entity row for Employees. For the two Work State messages, open the entity row for Work States.
- Check the Errors column for that entity row. If it is non-zero, open the errors list for that row and look for the exact message text from the table above.
Most tax-related messages in Core HR are Warnings, not Errors. If you have concerns about tax data and the entity row shows a non-zero Warnings count, but a zero Errors count, that case is not covered by this article.
Resolving the Error
Filing Status Missing
- Confirm the Federal Taxes scope is enabled for this connector step. If it is not enabled, this message cannot occur and the ticket is about something else.
- Open the employee's federal withholding setup (Form W-4 information) in the source system feeding this connector.
- Select a Filing Status value that matches their own tax setup for that employee.
- Save the change and run the sync again.
- Confirm the fix by reopening the Employees entity row for the new run and checking that the Errors count for that employee is now zero.
Missing State Value
- Open the source system feeding this connector and find the state list item with a blank value.
- Enter the state value for that item.
- Save the change and run the sync again.
- Confirm the fix by reopening the Work States entity row for the new run and checking that the Errors count is now zero and the item shows under Added or Updated.
Duplicate Work State Value
- Open the source system feeding this connector and locate all Work State items with the value named in the error message.
- Correct the source data so only one item uses that value. Only the first one sent in a run is saved; every later duplicate is skipped every run until the source data is fixed.
- Mention that any employee whose Work State/Location depends on the duplicated value may not have that field set correctly until the duplicate is resolved.
- Save the change and run the sync again.
- Confirm the fix by reopening the Work States entity row for the new run and checking that the Errors count is now zero.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- You confirm Filing Status is set correctly at the source, but the Filing Status error still occurs after a resync.
- You confirm the state value is populated at the source, but the missing state error still occurs after a resync.
- You removed the duplicate Work State value at the source, but the duplicate value error still occurs on the next run for the same value.
- The Federal Taxes scope or the Work States entity is not enabled on the connector, and you need to add it.
- Any case where confirming or fixing the value requires access to your source system screens.