This family covers pay-related sync failures for CMiC, and it runs in two directions. When Arcoro reads data from CMiC, a problem with an employee's pay setup in CMiC (missing Pay Run, missing Employee Type, wrong Rate Code) means the compensation record cannot be understood, so it is left out of that read. When Arcoro writes data out to CMiC, a problem with the employee's compensation, pay group, or pay frequency in the Arcoro source system means the write is rejected before it reaches CMiC. In both directions, you have to correct the data at its source. Two of the write-side messages exist specifically to protect CMiC's pay history: CMiC keeps every past compensation change as its own dated record, and the sync refuses to write a new pay change on the same date as the employee's Hire Date or Rehire Date because doing so would overwrite that historical record instead of adding a new one.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Rate Code "[rate code]" not supported, only "[allowed rate code]" is allowed. The employee compensation will not be synced. Correct the data in CMiC and run the Sync again. | Read (CMiC into Arcoro) | The employee's Rate Code in CMiC does not match the single Rate Code configured on the Arcoro connector. This is checked before any other compensation field. | Collection item skipped. The compensation record is left out for this employee; the employee itself and every other scope still sync. | In CMiC, set the employee's Rate Code to the value configured on the connector's Rate Code setting. |
| EmpType is not marked as either (S)alary or (H)ourly in CMiC. This property is required by the Sync to process compensation for the Employee. Correct the data in CMiC and run the Sync again. | Read (CMiC into Arcoro) | The employee's Rate Code matched, but the employee's Employee Type field in CMiC is blank. | Collection item skipped. The compensation record is left out for this employee; the employee itself and every other scope still sync. | In CMiC, set the employee's Employee Type to Salary or Hourly. |
| The Employee's compensation type is set as '[S or H]' but the property '[EmpAnnualSalary or EmpHourlyRate]' does not have a value in CMiC. The compensation record is not valid and will not be processed. Correct the compensation for this Employee and run the Sync again. | Read (CMiC into Arcoro) | Employee Type passed the prior check, but the matching pay amount field in CMiC is blank: the Annual Salary field for a Salary employee, or the Hourly Rate field for an Hourly employee. | Collection item skipped. The compensation record is left out for this employee; the employee itself and every other scope still sync. | In CMiC, enter the missing Annual Salary (Salary employees) or Hourly Rate (Hourly employees). |
| The Employee does not have a Pay Run Code assigned to them in CMiC. The employee's compensation can not be read without this and will not be processed. Correct the data in CMiC and run the Sync again. | Read (CMiC into Arcoro) | The employee has no Pay Run Code in CMiC, or the assigned Pay Run Code does not match any Pay Run Arcoro has loaded from CMiC. | Collection item skipped. The compensation record is left out for this employee; the employee itself and every other scope still sync. | In CMiC, assign a valid Pay Run Code to the employee. |
| The Employee's assigned Pay Run does not have a Pay Frequency that is understood by the provider. The compensation for the employee will not be processed. Correct the data in CMiC and run the Sync again. | Read (CMiC into Arcoro) | The employee's Pay Run Code matched a known Pay Run, but that Pay Run's Pay Frequency cannot be converted to a usable pay period count. | Collection item skipped. The compensation record is left out for this employee; the employee itself and every other scope still sync. | In CMiC, correct the Pay Frequency assigned to the employee's Pay Run so it uses a standard, supported frequency. |
| Employee Compensation is required. Employee will not be sent to CMiC. | Write (Arcoro out to CMiC) | The employee arrives at CMiC with no compensation record at all, or every compensation record present was rejected during mapping and none was left to process. | Whole record skipped. The employee is not written to CMiC this run. | In the Arcoro source system, give the employee at least one valid, active compensation record, then run the sync again. |
| A change in compensation was detected for [employee identifier], but the Start Date cannot match the Employee Hire Date on CMiC to prevent overwriting historical records. Please change the start date on source system and run the sync again. | Write (Arcoro out to CMiC) | The compensation Start Date on the changed record exactly matches the employee's Hire Date already stored in CMiC, and the Hire Date itself did not just change in this sync. | Collection item skipped. Only this compensation change is not written; the rest of the employee record still syncs. | In the Arcoro source system, change the compensation Start Date so it does not fall on the employee's Hire Date, then run the sync again. |
| A change in compensation was detected for [employee identifier], but the Start Date cannot match the Employee Rehire Date on CMiC to prevent overwriting historical records. Please change the start date on source system and run the sync again. | Write (Arcoro out to CMiC) | The compensation Start Date on the changed record exactly matches the employee's Rehire Date already stored in CMiC, and the Rehire Date itself did not just change in this sync. | Collection item skipped. Only this compensation change is not written; the rest of the employee record still syncs. | In the Arcoro source system, change the compensation Start Date so it does not fall on the employee's Rehire Date, then run the sync again. |
| A compensation record was found with a negative pay rate. Please review and ensure the pay rate is correctly entered before proceeding. | Write (Arcoro out to CMiC) | For an active (not terminated) employee, a compensation record has a pay rate below zero. | Collection item skipped: this compensation record is excluded from processing. If it was the only candidate record, this cascades into a whole record skip, reported separately as "No valid compensation". | In the Arcoro source system, correct the pay rate so it is zero or positive, then run the sync again. |
| A salary compensation record was found with a zero-amount pay rate. Please review and ensure the pay rate is correctly entered before proceeding. | Write (Arcoro out to CMiC) | For an active (not terminated) employee, a Salary-type compensation record has a pay rate of exactly zero. | Collection item skipped: this compensation record is excluded from processing. If it was the only candidate record, this cascades into a whole record skip, reported separately as "No valid compensation". | In the Arcoro source system, enter a non-zero salary amount, then run the sync again. |
| No valid compensation with Rate Code [rate code] could be found for the Employee. The record will not be processed. Please review the data on source system and run the sync again. | Write (Arcoro out to CMiC) | After removing invalid records (negative or zero-salary pay rates) and filtering to records with a Start Date on or before today, a Rate Code matching the connector's configured Rate Code, and a pay rate of zero or more, no compensation record remains. | Whole record skipped. The employee is not written to CMiC this run. | In the Arcoro source system, confirm the employee has a compensation record with a Start Date on or before today, a Rate Code matching the connector's configured Rate Code, and a pay rate that is not negative. |
| The Employee Pay Frequency is required. Employee will not be sent to CMiC. | Write (Arcoro out to CMiC) | The employee's Pay Frequency field is blank in the Arcoro source system. | Whole record skipped. The employee is not written to CMiC this run. | In the Arcoro source system, set a Pay Frequency value for the employee, then run the sync again. |
| Employee's pay frequency [pay frequency] could not match any existing value in CMiC. The record will no be synced. Correct data in source system and run the sync again. | Write (Arcoro out to CMiC) | The employee's Pay Frequency value in the Arcoro source system does not match, exactly, any Pay Frequency description configured in CMiC. | Whole record skipped. The employee is not written to CMiC this run. | Compare the Arcoro Pay Frequency value against the Pay Frequency descriptions configured in CMiC. Correct the value in the Arcoro source system to match one exactly, or ask the CMiC administrator to confirm the correct description. |
| Employee's pay group exceeds the maximum length of 4 characters supported by the provider and will not be synced. | Write (Arcoro out to CMiC) | The Pay Group scope is enabled, the employee has a Pay Group value that matches an existing CMiC pay group, and that CMiC pay group's code is longer than 4 characters. | Whole record skipped. The employee is not written to CMiC this run. | Ask the CMiC administrator to confirm the code for the employee's assigned Pay Group in CMiC. The employee's record can only accept a Pay Group code of 4 characters or fewer, so a shorter code, or a different Pay Group, is needed. |
Confirming the Error
- Open the Sync History screen for the connector and find the sync execution for the run in question.
- Open the step for the CMiC connector within that execution.
- Find the Employees entity row for that step and check its Total, Added, Updated, Unchanged, Information, Warnings, and Errors counts. Failures is a step-level count and tab, not a per-entity column, so it does not appear on the entity row.
- Open the entity row's errors list and match on the fixed part of the sentence, ignoring the values in quotes or brackets, for example "Rate Code" or "not supported" rather than the specific code shown, since the quoted or bracketed values are specific to the employee and will not repeat across employees.
- For the read-side messages in this article, the employee row itself typically still shows as Added or Updated, because only the Compensations part of that employee was skipped, not the whole employee.
- For the write-side messages marked "Whole record skipped" in this article, the employee will not appear as Added or Updated for this run; it will only appear against the Errors count.
- For the two Start Date restriction messages, the employee record itself may still show as Updated, since only the compensation change was withheld and the rest of the employee's changes could still have gone through.
Resolving the Error
Read-Side Messages (Fault Is InCMiC)
- Confirm the connector's configured Rate Code setting if the Rate Code message is the one reported.
- Open the affected employee's record in CMiC and correct the specific field named in the message: Rate Code, Employee Type, Annual Salary or Hourly Rate, Pay Run Code, or the Pay Run's Pay Frequency.
- Run the sync again once the CMiC data is corrected.
- Confirm the fix by re-checking the entity row's Errors count for that employee on the next run; the compensation record should now read in without an error.
Read-Side Messages (Fault Is Inwrite-Side Messages (Fault Is in the Arcoro Source Data)
- Identify the employee named in the message (the message text includes the employee identifier for the compensation restriction messages).
- Open that employee in the Arcoro source system and correct the field the message points to: add a compensation record, fix a negative or zero pay rate, adjust the compensation Start Date away from the Hire or Rehire Date, or set a valid Pay Frequency.
- For a Pay Frequency mismatch, confirm the exact text of the chosen Pay Frequency matches a Pay Frequency description that exists in CMiC.
- For the Pay Group length message, escalate to confirm the CMiC-side Pay Group code with your CMiC administrator, since the fix depends on the code configured in CMiC rather than a value you enter in Arcoro.
- Run the sync again once the source data is corrected.
- Confirm the fix by re-checking the entity row's Errors count and the Added or Updated count for that employee 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 Rate Code message but is unsure what Rate Code is configured on their connector, and no implementation contact is available to confirm it.
- The Pay Frequency does not match message persists after you made the value match what they see in CMiC; this may mean the CMiC Pay Frequency list itself needs a new entry, which is outside tier 1 scope.
- The Pay Group length message appears, and your CMiC administrator confirms the assigned Pay Group code is already 4 characters or fewer; this suggests the connector's Pay Group lookup data may be out of date and needs engineering review.
- The same employee reports a Start Date restriction message repeatedly across multiple runs even after the source Start Date was changed, since this points to a possible history record already written incorrectly and needs engineering review.
- No valid compensation is reported after confirming that the Rate Code, Start Date, and pay rate all look correct in the source system.