Viewpoint Spectrum will not accept an employee record unless it has a valid pay frequency, and it will not accept a compensation record unless that record has a type, a pay rate, a start date, and annual hours worked. If the employee's own pay frequency is missing or does not match anything in Spectrum, the entire employee is held back and nothing is sent for that employee this sync. If the problem is only on one compensation record, such as a missing pay rate or a rate that is too high for its type, only that one compensation record is left out. The employee and every other compensation record for that employee still sync normally. There is one exception worth knowing by heart: if two compensation records end up sharing the exact same start date, Spectrum logs an error, but the sync still writes the employee and both records anyway, so this particular message needs a manual data fix even though the sync itself did not hold anything back.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Pay Frequency is required. | Write (Arcoro to Spectrum) | The employee's Pay Frequency field is empty. | Whole employee record skipped. The employee is not synced this run. | Enter a Pay Frequency on the employee in Core HR, then rerun the sync. |
| Pay Frequency [pay frequency] could not be matched to a value within Spectrum. Please update the employee and rerun the sync. | Write (Arcoro to Spectrum) | The employee has a Pay Frequency value, but it is not one of the values Spectrum recognizes: Weekly, BiWeekly, SemiMonthly, Monthly, Annually, Quarterly, or Daily. | Whole employee record skipped. The employee is not synced this run. | Change the employee's Pay Frequency in Core HR to one of the supported values, then rerun the sync. |
| Compensation Type is required. | Write (Arcoro to Spectrum) | A compensation record has no Compensation Type set. Only checked for compensation records that are currently effective or dated in the future. Expired records are silently left out of the sync before this check ever runs, so an expired compensation record will not show this error. | Collection item skipped. That one compensation record is left out; the employee and its other compensation records still sync. | Set a Compensation Type of Hourly or Salary on the compensation record in Core HR, then rerun the sync. |
| Pay Rate is required. | Write (Arcoro to Spectrum) | A compensation record has no Pay Rate value. Only checked for compensation records that are currently effective or dated in the future. | Collection item skipped. That one compensation record is left out; the employee and its other compensation records still sync. | Enter a Pay Rate on the compensation record in Core HR, then rerun the sync. |
| Pay Start Date is required. | Write (Arcoro to Spectrum) | A compensation record has no Pay Start Date value. Only checked for compensation records that are currently effective or dated in the future. | Collection item skipped. That one compensation record is left out; the employee and its other compensation records still sync. | Enter a Pay Start Date on the compensation record in Core HR, then rerun the sync. |
| Invalid Type - The Compensation Type of [compensation type] is not supported by Spectrum. The employee will be synced without this compensation record. | Write (Arcoro to Spectrum) | A compensation record has a Compensation Type set, but it is not Hourly or Salary, the only two types Spectrum supports. | Collection item skipped. That one compensation record is left out; the employee and its other compensation records still sync. | Change the compensation record's type to Hourly or Salary in Core HR, then rerun the sync. |
| The [compensation type] Pay Rate of [pay rate] exceeds the Spectrum supported maximum value of [maximum value]. The employee will be synced without this compensation record. | Write (Arcoro to Spectrum) | The compensation record's Pay Rate exceeds the Spectrum maximum for its type: 999.9999 for Hourly, or 9,999,999.99 for Salary. | Collection item skipped. That one compensation record is left out; the employee and its other compensation records still sync. | Correct the Pay Rate in Core HR so it is within the Spectrum limit for that compensation type, then rerun the sync. |
| A compensation record was found with a negative pay rate. The record will not be synced. Please correct the pay rate in the source system and run the sync again. | Write (Arcoro to Spectrum) | The compensation record's Pay Rate is less than 0. | Collection item skipped. That one compensation record is left out; the employee and its other compensation records still sync. | Correct the negative Pay Rate to a zero or positive value in Core HR, then rerun the sync. |
| The Compensation Annual Hours Worked is required. The employee will be synced without this compensation record. Please update the compensation record and rerun the sync to update. | Write (Arcoro to Spectrum) | The compensation record's Annual Hours Worked value is empty or is set to 0. Both are treated the same way, an empty value is not treated any differently from a zero. | Collection item skipped. That one compensation record is left out; the employee and its other compensation records still sync. | Enter a non-zero Annual Hours Worked value on the compensation record in Core HR, then rerun the sync. |
| Syncing compensations for the following employees would create multiple active compensation records with the same start date, which is not supported by Spectrum. Please manually update the compensation records in Spectrum or Core HR to ensure they are aligned. | Write (Arcoro to Spectrum) | After every other compensation check above has already passed, two or more of the employee's compensation records still share the exact same Pay Start Date. | Not skipped. This check runs after the compensation records have already been accepted for writing. The employee and the duplicate-start-date records are still synced to Spectrum; the error is logged as a flag for manual cleanup, nothing is held back automatically. | In Core HR or directly in Spectrum, give each active compensation record for the employee a distinct Pay Start Date, then rerun the sync to confirm the error clears. |
Confirming the Error
- Open Sync History and find the sync execution for your Viewpoint Spectrum connector on the date in question.
- Find the step for the Employees entity within that execution and check its Errors column. All ten messages in this article log at the Error level, so they show up in Errors, not Warnings or Information.
- Check the Failures column for that same entity row. Failures reflects a separate, step-level problem such as a connection or processing failure. A non-zero Failures count does not mean one of these ten messages fired, and a zero Failures count does not rule them out. Rely on the Errors column and the Added, Updated, and Unchanged columns instead.
- Open the Employees entity row to see the per-employee detail, and locate the specific employee by name or employee identifier.
- Open that employee's list of errors and match on the fixed part of the sentence, not on the bracketed values. For example, match on "is not supported by Spectrum" or "exceeds the Spectrum supported maximum value of" rather than the specific compensation type, rate, or limit quoted in that instance.
- If the employee's Added, Updated, or Unchanged count is 0 for this run, the whole employee record was skipped, which points to one of the two Pay Frequency messages. If the employee otherwise synced normally, the issue is isolated to one compensation record.
Resolving the Error
Pay Frequency Is Required, or Pay Frequency Could Not Be Matched
- In Core HR, open the employee record and go to the compensation or pay setup section where Pay Frequency is set.
- Enter a Pay Frequency if it is blank, or change it to one of the values Spectrum recognizes: Weekly, BiWeekly, SemiMonthly, Monthly, Annually, Quarterly, or Daily.
- Save the change in Core HR and rerun the sync for this connector.
- Confirm the fix by reopening Sync History for the new execution and checking that the employee now has an Added or Updated count instead of appearing in the Errors list.
Compensation Type, Pay Rate, Pay Start Date, or Annual Hours Worked Is Missing or Out of Range
- In Core HR, open the employee record and go to the compensation record that the error identifies (the message will name the compensation type and, for the rate and max-value errors, the values involved).
- Fill in the missing field, or correct the value so it is within the Spectrum limit for that compensation type: 999.9999 for Hourly, or 9,999,999.99 for Salary. Pay rates must not be negative.
- Confirm the compensation record's type is Hourly or Salary. Spectrum does not support any other compensation type.
- Save the change in Core HR and rerun the sync.
- Confirm the fix by checking that the employee's Errors list no longer includes that message, and that the compensation record appears in the synced output for that employee.
Duplicate Compensation Start Dates
- In Core HR, review the employee's active compensation records and identify which two (or more) share the same Pay Start Date.
- Change the Pay Start Date on one of the records in Core HR so that each active record has a distinct start date. If you manage this directly in Spectrum instead, the same correction can be made there.
- Rerun the sync and confirm the fix by checking that this error no longer appears for the employee. Because the employee still synced while the error was present, there is no "record now appears" signal to check here, only that the error message is gone on the next run.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- The Pay Frequency value in Core HR already matches one of the seven supported values (Weekly, BiWeekly, SemiMonthly, Monthly, Annually, Quarterly, Daily) exactly, but the error persists after a rerun.
- You needs a Compensation Type other than Hourly or Salary supported in Spectrum. This is a product limitation, not a data issue.
- An employee shows the duplicate start date error even after you confirm the start dates are distinct in both Core HR and Spectrum.
- Any of these messages appear for an entity other than Employees, or appear alongside a non-zero Failures count, since that suggests a different underlying issue than what is documented here.