Arcoro sends two separate kinds of employee benefit data to Sage 300 CRE through HH2: Fringe Benefits and Deduction Benefits. These are two different scopes, and you fix them in different places. Before Arcoro can write one of these records, it needs a valid effective date, and it needs to match the record to an existing benefit, fringe, or pay deduction code that is already set up in HH2. If either check fails, only that one benefit or fringe record is left out of the sync. The employee and every other benefit or fringe still sync normally. None of this data is sent at all for a terminated employee, since Sage 300 CRE does not accept these kinds of updates once an employee is terminated.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| 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 300 CRE (write) | The Fringe Benefits scope is enabled, the employee is active, and this fringe record has no value in its Effective Date field. This check runs before the current-effective-date filter, so it always catches a blank date, even if the record would otherwise have been treated as expired or not yet in effect. | Collection item skipped. This one fringe record is left out. The employee and every other fringe still sync. | In the source system, enter an effective date on the fringe record and run the sync again. |
| 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 300 CRE (write) | The fringe record has an effective date and is currently in effect, but its code does not exactly match an existing fringe code already set up in HH2. The match is case and space sensitive. | Collection item skipped. This message is logged at the employee level, not against the individual fringe item, so it will not appear nested under a specific fringe entry in the log. | In Sage 300 CRE (through HH2), create or correct the fringe code so it matches the source system value exactly, including spacing and case. |
| 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 300 CRE (write) | The Deduction Benefits scope is enabled, the employee is active, and this deduction/benefit record has no value in its Effective Date field. Like the fringe version, this check runs before the current-effective-date filter, so a blank date is always caught. | Collection item skipped. This one deduction record is left out. The employee and every other benefit still sync. | In the source system, enter an effective date on the deduction/benefit record and run the sync again. |
| The Benefit Deduction code '[benefit deduction 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 300 CRE (write) | The deduction/benefit record has an effective date and is currently in effect, but its code does not exactly match an existing Benefit/Pay Deduction code already set up in HH2. The match is case and space sensitive. | Collection item skipped. This one deduction record is left out. Every other benefit still syncs. | In Sage 300 CRE (through HH2), create or correct the Benefit/Pay Deduction code so it matches the source system value exactly, including spacing and case. |
| The matching Benefit Code '[benefit deduction code]' in HH2 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 300 CRE (write) | The code matched a Benefit/Pay Deduction in HH2 and is not configured as a direct deposit type, but the employee's existing deduction record already linked to that code in HH2 is flagged as archived. | Collection item skipped. This message is logged at the employee level, not against the individual benefit item. The employee and every other benefit still sync. | Have IsArchived set to false on the matching benefit record in HH2, then run the sync again. |
Confirming the Error
- In Arcoro, open Sync History and find the sync execution in question.
- Open the step for the Sage 300 CRE connector.
- Find the Employees entity row for that step.
- Check the Errors column for that row. All five messages in this article are logged at Error severity, even though three of the internal message names include the word Warning. Do not look in the Warnings column for these.
- Open the Errors list for the Employees entity row.
- Match on the fixed part of the sentence, not on the code value in quotes, since the code will be different for every company and every record.
- Tell a fringe problem from a deduction problem by the wording alone: a message that says "The Fringe with code" or "The Fringe Deduction code" belongs to the Fringe Benefits scope. A message that says "The Deduction with code" or "The Benefit Deduction code" or "The matching Benefit Code" belongs to the Deduction Benefits scope.
- If the Failures column for the Employees entity is non-zero, that is a different and more serious condition than anything in this article. These five messages skip one record each; they do not stop the sync or fail the whole entity. Treat a non-zero Failures count as a separate issue and see When to escalate.
Resolving the Error
A Fringe or Deduction Record Has No Effective Date
- Confirm which scope from the message wording: "Fringe" means Fringe Benefits, "Deduction" means Deduction Benefits.
- In the source system that feeds this sync, open the employee record and find the fringe or deduction/benefit entry with the code named in the message.
- Enter a valid effective date on that entry.
- Save the change in the source system.
- Run the sync again and confirm the record no longer appears in the Employees entity Errors list.
A Fringe or Benefit Code Does Not Match HH2
- Note the exact code text between the quotes in the message, including any leading or trailing spaces and its exact capitalization.
- In Sage 300 CRE, through HH2, open the Fringe setup (for a Fringe Benefits message) or the Pay Deduction setup (for a Deduction Benefits message).
- Check whether a code exists that matches character for character, including spacing and case.
- If no matching code exists, it needs to be created in Sage 300 CRE with the exact code from the message.
- If a similar code exists but does not match exactly, correct the spacing or case on whichever system is not the source of truth for that code.
- Run the sync again and confirm the record moves out of the Errors list.
A Benefit Code Is Archived in HH2
- Confirm the message text is the archived-code message, not the code-not-found message.
- This fix requires setting IsArchived to false on the matching benefit record in HH2.
- Escalate the ticket with the employee identifier and the benefit code from the message.
- Once IsArchived has been set to false, run the sync again and confirm the record moves out of 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 is the archived-code message. Setting IsArchived to false in HH2 is outside what can typically be done.
- The error is still present after the source data has been corrected and the matching code has been confirmed correct in Sage 300 CRE and HH2.
- The message text in the log does not match any of the five messages in the table above.
- The Employees entity shows a non-zero Failures count alongside these messages.
- Many different benefit or fringe codes are failing at once right after a new connector is set up. That pattern points to a preload or setup problem rather than a single bad record.