Module Navigation

Troubleshooting Sage 300 Integration Error: Tax Setup (Federal, State, Local)

These messages all come from the step that sends an employee's tax data from Arcoro out to Sage 300 CRE through HH2. Before anything is sent, the sync checks that the Federal Tax and State Tax information on the employee record makes sense: dates are present and in order, exemption counts are in range, and each state has a matching tax setup on the Sage 300 CRE side. When a check fails, the sync leaves that data out rather than sending something Sage 300 CRE cannot use. Depending on the problem, that means the whole employee is skipped this run, just one state's tax record is skipped, or just one field on a state tax record is left blank.

Error Messages

Message textDirectionOccurs whenOutcomeFix
Employee's Federal Tax Start Date has no value. The record will not be synced.Write (Arcoro to Sage 300 CRE)The Federal Taxes scope is enabled, the employee has federal tax data, and the Federal Tax Start Date field is blank.Record skipped. The whole employee is not written this sync run.Enter a Federal Tax Start Date on the employee in Arcoro.
Employee's Federal Tax Start Date is in the future. The record will not be synced.Write (Arcoro to Sage 300 CRE)The Federal Taxes scope is enabled, the employee has federal tax data, and the Federal Tax Start Date is later than tomorrow.Record skipped. The whole employee is not written this sync run.Set the Federal Tax Start Date to today or an earlier date.
Employee's Federal Tax Start Date is greater than the End Date. The record will not be synced.Write (Arcoro to Sage 300 CRE)The Federal Taxes scope is enabled, the employee has federal tax data, and the Federal Tax Start Date is later than the Federal Tax End Date.Record skipped. The whole employee is not written this sync run.Correct the Federal Tax End Date so it is on or after the Start Date, or clear the End Date if the tax setup has no end date.
TaxExemptionCount must be a non-negative integer. The record will not be synced.Write (Arcoro to Sage 300 CRE)The Federal Taxes scope is enabled, the employee has federal tax data, and the Federal Tax exemptions or allowances value is a negative number.Record skipped. The whole employee is not written this sync run.Correct the Federal Tax exemptions or allowances value to zero or a positive whole number.
Multiple records sent from source system for this state. Only the first record will be processed.Write (Arcoro to Sage 300 CRE)The State Taxes scope is enabled, the employee is not terminated, and this state's tax record resolves to the same Sage 300 CRE tax record that another state entry already claimed earlier in the same sync run.Collection item skipped. This one state tax record is left out. The employee and every other state tax record still sync.In Arcoro, review the employee's State Tax records for this state for a duplicate or conflicting entry and remove or deactivate the extra one.
State Tax Exemption Count for [state code] needs to be a value between 0 and 99. This record will not be synced with HH2.Write (Arcoro to Sage 300 CRE)The State Taxes scope is enabled, the employee is not terminated, and this state tax record's exemption or allowance count is less than 0 or greater than 99.Collection item skipped. This one state tax record is left out. The employee and every other state tax record still sync.Correct the exemption or allowance count on that state tax record in Arcoro to a whole number from 0 to 99.
The provided Filing Status for State: "[state code]" Code: "[filing status value]" AltTax1: "[alternate tax value]" could not be mapped to a supported Sage 300 CRE value.Write (Arcoro to Sage 300 CRE)The state is not on the short list of states allowed to have no filing status, the employee's filing status for that state is set to an actual value, and that value does not translate to a filing status Sage 300 CRE supports for that state.Field skipped only. The Filing Status field on that state tax record is left blank. The rest of that state tax record, and the employee, still sync.In Arcoro, correct the employee's state filing status for that state to a value Sage 300 CRE supports.
The empty or missing Filing Status for [state code] could not be mapped to a supported Sage 300 CRE value.Write (Arcoro to Sage 300 CRE)This message is built from a broken template and, based on the surrounding code, cannot currently be reached. See Open questions.Not applicable. This message should not appear in a normal sync log.See When to escalate.
Could not find HH2 matching object EmployeeFederalAndStateTax for State [state code]. The record cannot be synced to HH2.Write (Arcoro to Sage 300 CRE)The State Taxes scope is enabled, the employee is not terminated, this state tax record's state code has no matching tax type in the Sage 300 CRE or HH2 setup data, and the state is not one of the nine states with no personal income tax.Collection item skipped. This one state tax record is left out. The employee and every other state tax record still sync.Confirm the state code on the employee's state tax record is a valid, supported state. If it is, escalate, since the Sage 300 CRE or HH2 tax setup for that state may be missing.

Confirming the Error

  1. Open Sync History and find the sync execution in question.
  2. Open the step for the Sage 300 CRE connector.
  3. Find the Employees entity row and check the Errors and Warnings columns. A non-zero Errors count means at least one employee had a problem on this run.
  4. Open the entity row to see the per-record detail, then open the errors list for the affected employee.
  5. Match the fixed part of the sentence against the Message text column above. Ignore the state code, filing status value, or exemption count shown in quotes or brackets, since those are specific to the employee.
  6. Note whether the row also shows a Failures count. None of the messages in this article are reached through a sync failure, so a non-zero Failures count on this entity points to a different problem and should be treated separately.

Resolving the Error

Federal Tax Start Date and End Date

  1. In Arcoro, open the employee's Federal Taxes record.
  2. Confirm the Federal Tax Start Date field has a value, that the value is today or earlier, and that it is not later than the Federal Tax End Date.
  3. Save the correction.
  4. Re-run the sync and confirm the employee no longer appears in the Errors list for this message.

Federal Tax Exemption Count

  1. In Arcoro, open the employee's Federal Taxes record.
  2. Set the exemptions or allowances field to zero or a positive whole number.
  3. Save the correction.
  4. Re-run the sync and confirm the employee no longer appears in the Errors list for this message.

State Tax Exemption Count

  1. In Arcoro, open the employee's State Taxes record for the state named in the message.
  2. Set the exemption or allowance count to a whole number from 0 to 99.
  3. Save the correction.
  4. Re-run the sync and confirm that state tax record no longer appears in the Errors list.

State Tax Filing Status Could Not Be Mapped

  1. In Arcoro, open the employee's State Taxes record for the state named in the message.
  2. Check the filing status value assigned for that state. If it is a status this state does not use, change it to one of the state's supported filing statuses.
  3. Save the correction and re-run the sync.
  4. If the message repeats for a filing status that looks correct, escalate with the exact state, filing status value, and AltTax1 value from the log so engineering can check whether Sage 300 CRE supports that combination.

Duplicate State Tax Record

  1. In Arcoro, open the employee's State Taxes records and look for more than one active entry tied to the state named in the message.
  2. Remove or deactivate the extra entry, keeping the one that should be current.
  3. Re-run the sync and confirm that state tax record now syncs.

State Tax Type Not Found

  1. Confirm the state code on the employee's state tax record in Arcoro is a real, correctly spelled state.
  2. If the state code is correct, this points to missing tax setup on the Sage 300 CRE or HH2 side rather than something to fix in the employee's data. Escalate.

When to Escalate

If any of the following occur, you may need to reach out to Arcoro support for additional assistance.

  • The state tax type not found message persists after confirming the state code on the employee record is correct.
  • The duplicate state tax message persists even though you confirm only one active record exists for that state in Arcoro.
  • Any log text that resembles "filing status" and "could not be mapped" but does not match the two filing status rows in the table above, especially anything that looks like raw code text rather than a plain sentence. Send the exact text to engineering, since it may be the broken message described in Open questions.
  • Any of these messages recur after the source data has been corrected and the sync re-run.
Was this article helpful?
0 out of 0 found this helpful