Every benefit deduction and fringe benefit record is checked before it is sent to Viewpoint Spectrum. Each record needs an effective date, a code, an amount, and a coverage type, and the code has to match something Spectrum already has set up for that company. If any of those checks fail, Arcoro leaves that one record out of the sync. The employee record itself, and every other benefit the employee has, still goes through.
Some of these checks depend on deduction and fringe (addon) codes that Arcoro loads from Spectrum before the sync runs. If that lookup did not succeed for the employee's company, every deduction or fringe code will appear to not exist in Spectrum, even if it is set up correctly there.
Error Messages
Benefit Deduction Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Benefit Deduction Effective Date is required. | Write (Arcoro to Spectrum) | The benefit deduction record has no Effective Date. This is the first check run on the record. If it fires, none of the other nine benefit deduction checks below run for this record on this pass. | Collection item skipped | Add an Effective Date to the benefit deduction record in the source system. |
| Benefit Deduction Code is required. | Write (Arcoro to Spectrum) | The Effective Date is present, and the Deduction Code field is blank or missing. | Collection item skipped | Add a Deduction Code to the benefit deduction record in the source system. |
| Benefit Deduction Cost is required. | Write (Arcoro to Spectrum) | The Effective Date is present, and the Deduction Cost field has no value. | Collection item skipped | Add a Deduction Cost to the benefit deduction record in the source system. |
| Benefit Deduction Coverage Type is required. | Write (Arcoro to Spectrum) | The Effective Date is present, and Coverage Type is not set to Flat or Percent. | Collection item skipped | Set the Coverage Type to Flat or Percent on the benefit deduction record in the source system. |
| The benefit deduction cost for code [deduction code] exceeds the maximum value of 99,999 supported by Spectrum. The employee will be synced without this record. | Write (Arcoro to Spectrum) | The Effective Date is present, Coverage Type is Flat, Deduction Cost has a value, and that cost is greater than 99,999. | Collection item skipped | Lower the Deduction Cost to 99,999 or less in the source system. |
| The benefit deduction percent for code [deduction code] exceeds the maximum value of 100% supported by Spectrum. The employee will be synced without this record. | Write (Arcoro to Spectrum) | The Effective Date is present, Coverage Type is Percent, Deduction Cost has a value, and that percent is greater than 100. | Collection item skipped | Lower the Deduction Cost percent to 100 or less in the source system. |
| The benefit deduction code [deduction code] exceeds the maximum length of 10 characters supported by Spectrum. The employee will be synced without this record. | Write (Arcoro to Spectrum) | The Effective Date and Deduction Code are both present, and the Deduction Code text is longer than 10 characters. This can fire together with the "not a valid code" message below on the same record, because Spectrum is still checked for the oversized code. | Collection item skipped | Shorten the Deduction Code to 10 characters or fewer in the source system. |
| The benefit deduction code [deduction code] is not a valid code in Spectrum. The employee will be synced without this record. Please update the deduction code(s) in Core HR or Spectrum to match the expected value. | Write (Arcoro to Spectrum) | The Effective Date and Deduction Code are both present, and the code (matched without regard to upper or lower case) is not one of the deduction codes Arcoro loaded from Spectrum for the employee's Company Code before the sync ran. This cannot fire on the same record as either calculation method message below, since those only run when the code was found. | Collection item skipped | Create the matching deduction code in Spectrum, or correct the Deduction Code in Core HR to match an existing Spectrum code. |
| The coverage type Flat does not match the calculation method in Spectrum for benefit deduction code [deduction code]. The employee will be synced without this record. The supported calculation methods for this coverage type are: (F)ixed Amount, (R)egular Equivalent Hours, (O)vertime Equivalent Hours, (A)ll Hours, (U)ser Defined Formula. Please update the coverage type in Core HR or the calculation method in Spectrum to match the expected value. | Write (Arcoro to Spectrum) | The Effective Date and Deduction Code are present, the code was found in Spectrum, Coverage Type is Flat, and Spectrum's calculation method for that code is not Fixed Amount, Regular Equivalent Hours, Overtime Equivalent Hours, All Hours, or User Defined Formula. | Collection item skipped | In Spectrum, set the deduction code's calculation method to one of the Flat-supported methods, or change the Coverage Type in Core HR to Percent if that matches the code's existing calculation method. |
| The coverage type Percent does not match the calculation method in Spectrum for benefit deduction code [deduction code]. The employee will be synced without this record. The supported calculation methods for this coverage type are: Percent of (G)ross Amount, Percent of (N)et Amount, Percent of (S)traight Time Equivalent, (P)ercent of Related Code, (U)ser Defined Formula. Please update the coverage type in Core HR or the calculation method in Spectrum to match the expected value. | Write (Arcoro to Spectrum) | The Effective Date and Deduction Code are present, the code was found in Spectrum, Coverage Type is Percent, and Spectrum's calculation method for that code is not Percent of Gross Amount, Percent of Net Amount, Percent of Straight Time Equivalent, Percent of Related Code, or User Defined Formula. | Collection item skipped | In Spectrum, set the deduction code's calculation method to one of the Percent-supported methods, or change the Coverage Type in Core HR to Flat if that matches the code's existing calculation method. |
Fringe Benefit Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Fringe Benefit Effective Date is required. | Write (Arcoro to Spectrum) | The fringe benefit record has no Effective Date. This is the first check run on the record. If it fires, none of the other nine fringe benefit checks below run for this record on this pass. | Collection item skipped | Add an Effective Date to the fringe benefit record in the source system. |
| Fringe Benefit Code is required. | Write (Arcoro to Spectrum) | The Effective Date is present, and the Fringe Code field is blank or missing. | Collection item skipped | Add a Fringe Code to the fringe benefit record in the source system. |
| Fringe Benefit Amount is required. | Write (Arcoro to Spectrum) | The Effective Date is present, and the Fringe Amount field has no value. | Collection item skipped | Add a Fringe Amount to the fringe benefit record in the source system. |
| Fringe Benefit Coverage Type is required. | Write (Arcoro to Spectrum) | The Effective Date is present, and Coverage Type is not set to Flat or Percent. | Collection item skipped | Set the Coverage Type to Flat or Percent on the fringe benefit record in the source system. |
| The fringe benefit amount for code [fringe code] exceeds the maximum value of 99,999 supported by Spectrum. The employee will be synced without this record. | Write (Arcoro to Spectrum) | The Effective Date is present, Coverage Type is Flat, Fringe Amount has a value, and that amount is greater than 99,999. | Collection item skipped | Lower the Fringe Amount to 99,999 or less in the source system. |
| The fringe percent for code [fringe code] exceeds the maximum value of 100% supported by Spectrum. The employee will be synced without this record. | Write (Arcoro to Spectrum) | The Effective Date is present, Coverage Type is Percent, Fringe Amount has a value, and that percent is greater than 100. | Collection item skipped | Lower the Fringe Amount percent to 100 or less in the source system. |
| The fringe benefit code [fringe code] exceeds the maximum length of 10 characters supported by Spectrum. The employee will be synced without this record. | Write (Arcoro to Spectrum) | The Effective Date and Fringe Code are both present, and the Fringe Code text is longer than 10 characters. This can fire together with the "not a valid code" message below on the same record, because Spectrum is still checked for the oversized code. | Collection item skipped | Shorten the Fringe Code to 10 characters or fewer in the source system. |
| The fringe benefit code [fringe code] is not a valid code in Spectrum. The employee will be synced without this record. Please update the fringe code(s) in Core HR or Spectrum to match the expected value. | Write (Arcoro to Spectrum) | The Effective Date and Fringe Code are both present, and the code (matched without regard to upper or lower case) is not one of the fringe (addon) codes Arcoro loaded from Spectrum for the employee's Company Code before the sync ran. This cannot fire on the same record as either calculation method message below, since those only run when the code was found. | Collection item skipped | Create the matching fringe code in Spectrum, or correct the Fringe Code in Core HR to match an existing Spectrum code. |
| The coverage type Flat does not match the calculation method in Spectrum for fringe benefit code [fringe code]. The employee will be synced without this record. The supported calculation methods for this coverage type are: (F)ixed Amount, (R)egular Equivalent Hours, (O)vertime Equivalent Hours, (A)ll Hours, (U)ser Defined Formula. Please update the coverage type in Core HR or the calculation method in Spectrum to match the expected value. | Write (Arcoro to Spectrum) | The Effective Date and Fringe Code are present, the code was found in Spectrum, Coverage Type is Flat, and Spectrum's calculation method for that code is not Fixed Amount, Regular Equivalent Hours, Overtime Equivalent Hours, All Hours, or User Defined Formula. | Collection item skipped | In Spectrum, set the fringe code's calculation method to one of the Flat-supported methods, or change the Coverage Type in Core HR to Percent if that matches the code's existing calculation method. |
| The coverage type Percent does not match the calculation method in Spectrum for fringe benefit code [fringe code]. The employee will be synced without this record. The supported calculation methods for this coverage type are: Percent of (G)ross Amount, Percent of (N)et Amount, Percent of (S)traight Time Equivalent, (P)ercent of Related Code, (U)ser Defined Formula. Please update the coverage type in Core HR or the calculation method in Spectrum to match the expected value. | Write (Arcoro to Spectrum) | The Effective Date and Fringe Code are present, the code was found in Spectrum, Coverage Type is Percent, and Spectrum's calculation method for that code is not Percent of Gross Amount, Percent of Net Amount, Percent of Straight Time Equivalent, Percent of Related Code, or User Defined Formula. | Collection item skipped | In Spectrum, set the fringe code's calculation method to one of the Percent-supported methods, or change the Coverage Type in Core HR to Flat if that matches the code's existing calculation method. |
Confirming the Error
- Open the sync execution for the Viewpoint Spectrum connector in the Arcoro sync history.
- Find the step for the Viewpoint Spectrum connector, then locate the Employees entity row within that step.
- Check the Errors column for that row. A non-zero Errors count is where these messages show up. None of the twenty messages in this article use the Failures outcome, so a non-zero Failures count on the Employees row is a different, more serious problem and is not explained by this article.
- Open the errors list for the Employees entity and look for the fixed part of the message text from the tables above. Match on the wording, not on the deduction or fringe code shown in the message, since that value is specific to your data.
- Note the employee and the code named in the message. Every other benefit and the rest of that employee's record still synced; only the named benefit record was left out.
- If the employee has any benefit record that is not currently in effect, Arcoro re-checks every benefit deduction or fringe benefit record on that employee a second time in the same run. It is normal to see the exact same message appear twice for one employee in that case. Two identical lines are one problem, not two.
Resolving the Error
Required Field Messages
Applies to Effective Date, Code, Cost or Amount, and Coverage Type required messages, for both benefit deductions and fringe benefits.
- In the source system, open the employee's benefit deduction or fringe benefit record named in the sync log.
- Fill in the missing field named in the message: Effective Date, Code, Cost or Amount, or Coverage Type.
- Save the record and re-run the sync.
- Confirm the fix by checking that the employee's Employees row in the next sync execution no longer lists this message, and that the benefit record now appears in the Added or Updated count.
Maximum Value Exceeded Messages
Applies to the cost or amount exceeding 99,999 (Flat) or 100% (Percent).
- In the source system, open the benefit deduction or fringe benefit record named in the sync log.
- Lower the Cost or Amount value to be within the Spectrum limit shown in the message (99,999 for Flat, 100 for Percent).
- Save the record and re-run the sync.
- Confirm the fix by re-running the sync and checking that the record no longer appears in the errors list.
Code Too Long or Code Not Found in Spectrum
- In the source system, check the Deduction Code or Fringe Code on the record named in the sync log.
- If the code is longer than 10 characters, shorten it to 10 characters or fewer.
- If the code is not found in Spectrum, either create a matching deduction or addon code in Spectrum, or correct the code in the source system so it matches an existing Spectrum code exactly (the comparison ignores upper and lower case, but the characters must match).
- Re-run the sync and confirm the record now appears in the Added or Updated count for the employee instead of the Errors list.
Calculation Method Does Not Match Coverage Type
- In Spectrum, open the deduction or addon code named in the sync log and check its calculation method.
- If the Coverage Type on the source record is Flat, the code's Spectrum calculation method must be Fixed Amount, Regular Equivalent Hours, Overtime Equivalent Hours, All Hours, or User Defined Formula.
- If the Coverage Type on the source record is Percent, the code's Spectrum calculation method must be Percent of Gross Amount, Percent of Net Amount, Percent of Straight Time Equivalent, Percent of Related Code, or User Defined Formula.
- Either update the calculation method on the code in Spectrum, or change the Coverage Type on the source record to the option that matches the code's existing calculation method.
- Re-run the sync and confirm the record now appears in the Added or Updated count for the employee instead 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 error persists after the named field has been corrected and the sync has been re-run.
- The log text does not match any message text in the tables above.
- Every deduction and fringe code for your company shows "not a valid code in Spectrum," even for codes you confirm exist in Spectrum. This points to the deduction and addon code lookup failing during setup rather than any one record being wrong, and needs a developer to check the connector's preload step.
- The Employees row shows a non-zero Failures count alongside these errors. That is a different, sync-stopping problem, not one of the twenty messages in this article.