These messages all occur while the sync is writing an employee's federal or state tax information into Sage 100 Construction (through the HH2 connection). Two of them are checked for every employee, whether or not Federal Taxes or State Taxes are part of this sync step, because they look at the tax details already carried on the employee record. The rest only apply when the Federal Taxes or State Taxes scope is turned on for this sync step, since those are the settings that control whether tax data is written at all. In every case, the sync found a tax value it could not translate into something Sage 100 Construction accepts, or found more than one active tax record where it expected one.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Filing Status required. This employee will not be updated in HH2. | Write (Arcoro to Sage 100) | The employee's federal filing status does not translate to a supported Sage 100 filing status. This includes a blank filing status, a status of Widow, or any unrecognized value. It is checked for every employee regardless of which scopes are enabled for this sync step. | Whole record skipped. No part of the employee is written to Sage 100 Construction for this run. | Set a supported federal filing status on the employee in the source system. |
| The employee has a federal tax record in HH2 with an unsupported Adjustment Method of [adjustment method name] and the Sync will not change this value. To have the Sync modify this, please change the value in Sage 100 Construction to a supported value (NoAdjustment, Exempt, Addon, AddonPercent, Replace, ReplacePercent) and wait for this change to be reflected or synced in HH2. | Write (Arcoro to Sage 100) | The employee's existing federal tax record already in Sage 100 Construction has an Adjustment Method of Formula or NoTax, both unsupported by this sync. Only checked when the Federal Taxes scope is enabled for this sync step. | Field skipped. Only the federal tax section is left unchanged. The rest of the employee, including state taxes, compensation, and direct deposit, still syncs. | In Sage 100 Construction, change the employee's federal Adjustment Method to one of the supported values (NoAdjustment, Exempt, Addon, AddonPercent, Replace, or ReplacePercent). |
| HH2's support for Federal Tax years prior to 2020 produces invalid results when writing to HH2 and cannot be supported. The employee will not be synced. To correct this problem, update the Employee's Federal W4 to a tax year 2020+ and run the sync again. | Write (Arcoro to Sage 100) | The employee has federal tax information, but it is not flagged as using the current (2020 and later) W-4 format. It is checked for every employee regardless of which scopes are enabled for this sync step. | Whole record skipped. No part of the employee is written to Sage 100 Construction for this run. | Update the employee's Federal W-4 in the source system to a 2020 or later version, then run the sync again. |
| Could not map filing status for [state code] [filing status] to a supported Sage value. Record will not be synced to HH2. | Write (Arcoro to Sage 100) | The employee's state filing status for that state has no equivalent Sage 100 code. This check is skipped for Alabama and New Jersey, and it is also skipped when the source filing status is already the value 0 or O. It also occurs when a filing status was set but the conversion produced only a blank code for that state. Only checked when the State Taxes scope is enabled. | Collection item skipped. Only that one state's tax record is left out. Every other state for the employee, and the rest of the employee, still syncs. | Correct the employee's filing status for that state in the source system to a value Sage 100 Construction supports for that state. |
| Filing status of Null for [state code] is not supported. Record will not be synced to HH2. | Write (Arcoro to Sage 100) | The employee's filing status for that state is blank, and that state is not one of the states allowed to have a blank filing status (AK, AZ, FL, IL, IN, MA, PA, NH, NV, SD, TN, TX, WA, WY). Only checked when the State Taxes scope is enabled. | Collection item skipped. Only that one state's tax record is left out. Every other state for the employee, and the rest of the employee, still syncs. | Set a filing status for that state on the employee in the source system. |
| Multiple records sent from source system for this state. Only the first record will be processed. | Write (Arcoro to Sage 100) | The sync already keeps only the single most recent, currently effective state tax record per state before this check runs. This message occurs when, despite that, a second record for the same state resolves to a state tax record that the sync already assigned a target to earlier in the same run. Only checked when the State Taxes scope is enabled. | Collection item skipped. The duplicate state tax record is left out. Every other state for the employee, and the rest of the employee, still syncs. | Review the employee's state tax records for that state in the source system and remove or correct the extra record. |
| Tax exemption count must be a value between 0 and 99. The record cannot be synced to HH2. | Write (Arcoro to Sage 100) | The employee's allowances (exemption count) for that state are less than 0 or greater than 99. Only checked when the State Taxes scope is enabled, and only after the filing status for that state has already been accepted. | Collection item skipped. Only that one state's tax record is left out. Every other state for the employee, and the rest of the employee, still syncs. | Correct the employee's allowances (exemption count) for that state in the source system to a value between 0 and 99. |
| The provider could not find the TaxType record in HH2 for State [state code]. Personal withholdings for this State cannot be synced to HH2. Verify that the State Tax is configured in Sage 100 Construction, ensure the Name of the tax record ends in 'Income Tax' and that the abbreviation starts with the 2-character State Code. | Write (Arcoro to Sage 100) | Sage 100 Construction has no tax type set up whose name ends in "Income Tax" and whose first two characters match the employee's state code. This check does not apply to the nine states with no personal income tax (AK, FL, NH, NV, SD, TN, TX, WA, WY). Only checked when the State Taxes scope is enabled. | Collection item skipped. Only that one state's tax record is left out. Every other state for the employee, and the rest of the employee, still syncs. | In Sage 100 Construction, set up the state income tax type for that state with a name ending in "Income Tax" and an abbreviation starting with the 2-character state code. |
Confirming the Error
- Open the sync execution for the affected run in Arcoro's Sync History screen.
- Select the step for the Sage 100 connector.
- Find the Employees entity row and check the Errors column. Any of the eight messages above appear there, not in Warnings or Information.
- Open the entity row's errors list and match on the fixed part of the sentence, not the values shown in brackets or quotes, for example, "Filing Status required" or "Multiple records sent from source system for this state."
- The Failures column is not used by any message in this article. A non-zero Failures count points to a different problem and should be treated separately.
Resolving the Error
Filing Status Required
- In the source system, open the employee's federal tax or W-4 information.
- Set the federal filing status to a supported value. A status of Widow or leaving it blank is not supported.
- Save, then re-run the sync and confirm the employee no longer appears in the Errors list for this entity.
Federal Tax Year Not Supported by HH2
- In the source system, open the employee's Federal W-4 information.
- Update the W-4 to a 2020 or later version.
- Save, then re-run the sync and confirm the employee no longer appears in the Errors list for this entity.
Unsupported Federal Adjustment Method
- In Sage 100 Construction, open the employee's federal tax setup.
- Change the Adjustment Method away from Formula or NoTax to one of NoAdjustment, Exempt, Addon, AddonPercent, Replace, or ReplacePercent.
- Re-run the sync and confirm the federal tax section for the employee updates without this message reappearing.
State Filing Status Could Not Be Mapped, or Is Null and Not Supported
- In the source system, open the employee's state tax information for the state named in the message.
- Set a filing status that Sage 100 Construction supports for that state.
- Re-run the sync and confirm that the state's tax record no longer appears in the Errors list.
Multiple Records Sent From Source System for This State
- In the source system, review the employee's state tax records for the state named in the message.
- Identify and correct or remove the extra record for that state.
- Re-run the sync and confirm only one record for that state is processed without error.
Tax Exemption Count Out of Range
- In the source system, open the employee's state tax information for the state named in the message.
- Set the allowances (exemption count) to a value between 0 and 99.
- Re-run the sync and confirm that the state's tax record no longer appears in the Errors list.
State Tax Type Not Found in HH2
- In Sage 100 Construction, open the tax type setup for the state named in the message.
- Confirm a state income tax type exists, that its name ends in "Income Tax," and that it begins with the 2-character state code.
- Create or correct the tax type if it is missing or misnamed.
- Re-run the sync and confirm that the state's tax 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 filing status, tax year, Adjustment Method, exemption count, or tax type setup has been corrected and confirmed.
- The message text in the log does not match any row in the table above.
- The Failures column for the entity is non-zero. That is a different problem than the messages in this article.
- You see the duplicate-state message but cannot find a second state tax record in the source system, since the exact matching behind that message could not be fully confirmed from the code.