CMiC stores federal and state withholding setup as effective-dated Tax Override and Tax Exemption records. CMiC will not let an existing override record be changed. To change withholding, a brand new record with a later effective date has to be created instead.
Because of that rule, the Arcoro write service checks two things before it sends a tax record to CMiC. First, can the employee's filing status be translated into a value CMiC accepts. Second, does the date on the source tax record actually move the record forward in time compared to what CMiC already has on file. If either check fails, Arcoro holds that record back rather than send a change CMiC would refuse. Depending on which check fails, the hold can affect the whole employee, just the federal tax section, or just one state's tax record.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| The Employee's Federal Filing Status is missing or could not be mapped to a valid CMiC value. The Employee will not be Synced. Correct the data and run the Sync again. | Write: Arcoro to CMiC | Pre-write check on the employee. Occurs in three distinct cases that read identically in the log: (1) the employee has no Federal Tax record at all in the source system, (2) a Federal Tax record exists but its filing status cannot be translated into a CMiC value for the applicable tax year, or (3) the translation step itself threw an unexpected error while processing the record. | Whole employee record skipped. The employee is not sent to CMiC at all this run. | Add or correct the employee's federal filing status in the source system, then re-run the sync. |
| Employee's federal filing status exceeds the maximum length of 2 characters supported by the provider and will not be synced. | Write: Arcoro to CMiC | Pre-write check on the employee. Occurs when the employee's federal filing status was translated to a CMiC value, but that translated value is longer than 2 characters. | Whole employee record skipped. The employee is not sent to CMiC at all this run. | See the escalation note under How to resolve. This does not point to a simple source data fix. |
| The provided Filing Status for [state code]-[filing status] could not be mapped to a supported CMiC value." | Write: Arcoro to CMiC | Per-state check within the State Taxes section. Occurs when CMiC requires a filing status for that state, the employee's state filing status could not be translated into a CMiC value, and the employee's state filing status is not set to Not Applicable. | Collection item skipped. Only that state's tax record is left out. The employee and every other state and federal tax record still sync. | Correct the employee's filing status for that state in the source system to a status CMiC supports for that state. |
| State [state code] does not have personal income tax and the record will not be synced to CMiC. | Write: Arcoro to CMiC | Per-state check within the State Taxes section. Occurs when CMiC requires a filing status for that state, no filing status could be translated, the employee's state filing status is set to Not Applicable, and that state is one of the states with no personal income tax. | Collection item skipped. Only that state's tax record is left out. The employee and every other state and federal tax record still sync. | This is normally expected, not a defect. Confirm the employee's work state is correct in the source system. If the state is correct, no action is needed. |
| CMiC does not allow changes to Federal Tax Overrides, a new record with a different Effective Date must be used. The tax record [tax code] [start date] will not be sent to CMiC. | Write: Arcoro to CMiC | Not currently reachable. The code that would raise this message is present but commented out, so under the current build it cannot appear in a sync log. | Not applicable under the current build. | If this exact text is ever seen in a log, escalate to engineering rather than troubleshooting it as a data issue. |
| CMiC does not allow changes to State Tax Overrides, a new record with a different State and Effective Date must be used. The tax record [state code] [start date] will not be sent to CMiC. | Write: Arcoro to CMiC | Not currently reachable. The code that would raise this message is present but commented out, so under the current build it cannot appear in a sync log. | Not applicable under the current build. | If this exact text is ever seen in a log, escalate to engineering rather than troubleshooting it as a data issue. |
| The record will not be synced since the start date in the source system [source start date] matches an existing effective date for Tax Overrides [existing effective date] in CMiC. | Write: Arcoro to CMiC | Occurs on the Federal Taxes section or on a single State Taxes record (two separate call sites, same wording). Occurs when the source tax record's start date is exactly equal to the effective date of the matching Tax Override already in CMiC, and that record actually has changes to send. | Federal case: the federal tax section is skipped, the rest of the employee still syncs. State case: only that one state's tax record is skipped (collection item skipped), other states and the employee still sync. | In the source system, change the start date on the tax record to a date after the date CMiC already has on file for that override. |
| The record will not be synced since the start date in the source system [source start date] precedes the effective date for Tax Overrides [existing effective date] in CMiC. | Write: Arcoro to CMiC | Occurs on the Federal Taxes section or on a single State Taxes record (two separate call sites, same wording). Occurs when the source tax record's start date is earlier than the effective date of the matching Tax Override already in CMiC, and that record actually has changes to send. | Federal case: the federal tax section is skipped, the rest of the employee still syncs. State case: only that one state's tax record is skipped (collection item skipped), other states and the employee still sync. | In the source system, change the start date on the tax record to a date after the date CMiC already has on file for that override. |
Confirming the Error
- Open Sync History and find the sync execution for the run in question.
- Open the step for the CMiC connector.
- Find the entity row for Employees and check its Total, Added, Updated, Unchanged, Information, Warnings, and Errors counts.
- Open the Employees entity row and locate the specific employee record. All eight messages in this article are logged as Errors. Failures is a step-level count and tab, not a per-entity column; a non-zero Failures count on the step points to a different kind of problem and is not one of these tax messages.
- In the errors list for that employee, match on the fixed part of the sentence (for example "does not have personal income tax" or "precedes the effective date for Tax Overrides"), not on the state codes or dates in the message, since those vary per record.
- Note whether the error is attached to the employee record as a whole, to the Federal Taxes section, or to a specific state row inside State Taxes. That placement, not the message wording, is what tells you whether a federal or a state tax record was affected for the two Source Tax Date messages, since the wording is identical for both.
Resolving the Error
Federal Filing Status Missing or Not Mappable
- In the source system (Arcoro CoreHR), open the employee's Federal Tax setup.
- Confirm a Federal Tax record exists for the employee and that Filing Status is set to a supported value, not blank.
- Save the change and run the sync again.
- Confirm the fix worked by checking that the employee no longer appears in the Employees entity Errors list, and that the employee shows under Added or Updated for that run.
Federal Filing Status Code Exceeds Two Characters
- In the source system, confirm the employee's federal filing status is set to a normal, supported value (not a status the source system flags as unusual or custom).
- If the filing status looks normal and the error persists after a resync, escalate to engineering. This message points to the translated CMiC code being longer than expected, which is a mapping condition rather than something you can correct by editing their tax setup.
State Filing Status Not Mapped
- In the source system, open the employee's State Tax setup for the state named in the message.
- Set the filing status for that state to a value CMiC supports for that state.
- Save the change and run the sync again.
- Confirm the fix worked by checking that the state no longer appears in the errors list for that employee's State Taxes.
State Has No Personal Income Tax
- In the source system, confirm the employee's work state assignment is correct.
- If the state shown in the message is correct, no change is needed. The record is expected to be left out of CMiC because that state does not levy personal income tax.
- If the state shown is wrong, correct the employee's work state in the source system and run the sync again.
Existing Federal or State Tax Override Changed
- These two messages are not produced by the current code. If either exact text appears in a log, do not treat it as a normal data-correction ticket.
- Escalate to engineering with the sync execution details so the build and code path can be confirmed.
Source Tax Start Date Matches or Precedes the Existing CMiC Effective Date
- In Sync History, confirm from the error's placement whether it is attached to Federal Taxes or to a specific state under State Taxes.
- In the source system, open the corresponding tax record (Federal Tax, or State Tax for the named state) for that employee.
- Change the start date on that tax record to a date after the effective date shown in the message as already on file in CMiC.
- Save the change and run the sync again.
- Confirm the fix worked by checking that the error no longer appears for that employee, and that the Federal Taxes section or the specific state record now shows as updated.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- The federal filing status length error recurs after confirming the employee's filing status looks normal in the source system.
- Either Existing Federal Override or Existing State Override text appears in any sync log. This message cannot be produced by the current codebase, so its appearance needs engineering to confirm what build you are running.
- A Source Tax Date match or precedes error keeps recurring for the same employee after you have moved the start date forward, especially if the effective date CMiC reports back does not match anything you can see in CMiC. This can indicate the connector's Federal Withholding Tax Code or State Withholding Tax Code setting is matching the wrong existing override record.
- An employee who should not have federal or state tax data synced at all keeps generating these errors, which may point to a Federal Taxes or State Taxes scope that is enabled when it should not be for this connector.