Module Navigation

Troubleshooting Sage 100 Integration Error: Deduction, Benefit, and Fringe

These six errors all occur while Arcoro is writing an employee's deduction benefits or fringe benefits to Sage 100 (HH2). Deduction Benefits and Fringe Benefits are two separate sync scopes, so you can have one working and the other failing.

For each benefit or fringe row on the employee, the sync checks that the row has an effective date, then tries to match its code to a Benefit/Pay Deduction or Fringe code already set up in Sage 100. If any of those checks fail, that single row is dropped from the sync. The rest of the employee's benefits, fringes, and other data still go through normally.

Both scopes are skipped entirely for terminated employees. If the employee is terminated, none of these six messages can appear for that employee, and no cleanup of previously synced benefit or fringe amounts happens for that run either.

Error Messages

Message textDirectionOccurs whenOutcomeFix
The Benefit Deduction code '[benefit code]' could not be matched with a valid Benefit/Pay Deduction in HH2. The code must be an exact match, including any spaces. The record will not be synced.Arcoro to Sage 100Deduction Benefits scope is enabled, the employee is not terminated, and the deduction row's code does not match any active Benefit/Pay Deduction code in Sage 100.Collection item skippedCorrect the code so it matches an active Sage 100 Benefit/Pay Deduction code exactly.
Benefit Code [benefit code] has IsArchived = true and cannot be updated by the Sync. To Sync this data contact support to set IsArchived = false and rerun the Sync.Arcoro to Sage 100The deduction row's code matched a Sage 100 Benefit/Pay Deduction, but this employee's existing benefit assignment for that code is archived in Sage 100.Collection item skippedEscalate to have the employee's archived benefit assignment reactivated.
The Deduction with code '[deduction code]' has an empty effective date and will not be processed by the Sync. Correct the data on the provider system and run sync again.Arcoro to Sage 100Deduction Benefits scope is enabled, the employee is not terminated, and the deduction row has no effective date value.Collection item skippedAdd an effective date to the benefit deduction row in Arcoro and rerun the sync.
The Fringe Deduction code '[fringe code]' could not be matched with a valid value in HH2. The code must be an exact match, including any spaces. The record will not be synced.Arcoro to Sage 100Fringe Benefits scope is enabled, the employee is not terminated, and the fringe row's code does not match any active Fringe code in Sage 100.Collection item skippedCorrect the code so it matches an active Sage 100 Fringe code exactly.
FringeCode '[fringe code]' has IsArchived = true and cannot be updated by the Sync. To Sync this data contact support to set IsArchived = false and rerun the Sync.Arcoro to Sage 100The fringe row's code matched a Sage 100 Fringe code, but this employee's existing fringe assignment for that code is archived in Sage 100.Collection item skippedEscalate to have the employee's archived fringe assignment reactivated.
The Fringe with code '[fringe code]' has an empty effective date and will not be processed by the Sync. Correct the data on the provider system and run sync again.Arcoro to Sage 100Fringe Benefits scope is enabled, the employee is not terminated, and the fringe row has no effective date value.Collection item skippedAdd an effective date to the fringe row in Arcoro and rerun the sync.

Confirming the Error

  1. Open the sync execution in question in Sync History.
  2. Open the step for the Sage 100 connector.
  3. Find the Employees entity row for that step. Expect it to show under Updated with a non-zero Errors count. This is normal for these messages, the employee still synced.
  4. Open the entity row's error list for that employee.
  5. Match on the fixed part of the sentence, not the value in quotes, for example match on "could not be matched with a valid Benefit/Pay Deduction in HH2" rather than the specific code.
  6. Check the Failures column. These six messages do not stop the write, so Failures should stay at zero for this employee. If Failures is non-zero, something else on the record failed and needs separate investigation.

Confirming Code from HH2

The match against Sage 100 codes is exact. It is case sensitive and does not trim leading or trailing spaces. When comparing the code in the error message to the code list in Sage 100, check for case differences and stray spaces, not just a visual match.

If the Benefit/Pay Deduction or Fringe code itself is archived in Sage 100, the sync will not find it at all during setup. That shows up as the not found message, not the archived message. The archived message is about the employee's own benefit or fringe assignment being archived, not the master code.

Resolving the Error

Code Not Found (Benefit Deduction or Fringe)

  1. In Arcoro, open the employee's Deduction Benefits or Fringe Benefits record and note the exact code, including spacing and case.
  2. In Sage 100, check the Benefit/Pay Deduction list (for the deduction message) or the Fringe code list (for the fringe message) for a code that matches exactly, and confirm it is not archived.
  3. If the code is missing or misspelled in Sage 100, add or correct it there.
  4. If the code in Arcoro does not match what Sage 100 uses, correct the code on the employee's benefit or fringe record in Arcoro.
  5. Rerun the sync and confirm the Errors count for this employee dropped and the benefit or fringe now appears in Sage 100.

Archived Assignment (Benefit or Fringe)

  1. Confirm the employee has an existing benefit or fringe assignment in Sage 100 for the code in the message, and that it is marked archived.
  2. Escalate this ticket. The message text directs you to contact support to set IsArchived to false on that record.
  3. Once the archived flag has been cleared, rerun the sync.
  4. Confirm the benefit or fringe now updates instead of erroring on the next run.

Empty Effective Date (Deduction or Fringe)

  1. In Arcoro, open the employee's Deduction Benefits or Fringe Benefits record for the code named in the message.
  2. Check the effective date field on that row. It is blank.
  3. Enter an effective date on that benefit or fringe row in Arcoro.
  4. Rerun the sync and confirm the row no longer appears in the error list and the benefit or fringe amount is updated in Sage 100.

When to Escalate

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

  • The message says the record has IsArchived = true and asks the reader to contact support to set it to false. Escalate both the benefit archived message and the fringe archived message on this basis.
  • The code appears correct and unarchived in Sage 100, matches case and spacing exactly, and the not found message still appears after a rerun.
  • The employee shows a non-zero Failures count alongside these messages. That points to a separate problem outside this family.
  • You see the same code failing on many employees at once, which may point to a setup problem in Sage 100 rather than a single employee's data.
Was this article helpful?
0 out of 0 found this helpful