Sage 100 Construction, through the HH2 connector, is stricter about pay data than Arcoro is. It only allows one active pay rate per rate code, it does not support a future effective date on a pay rate, it requires every rate code (Pay Type) description to be unique, it requires a pay frequency from a fixed list of four, and it requires Pay Group names (Certified Classes) to be unique.
When the data coming from either system does not fit those rules, Arcoro cannot safely translate it. Depending on where the rule is broken, the result is either one compensation record being left out of an otherwise successful employee sync, one lookup record (a Rate Code or Pay Group) being left out of the read, or the whole employee not being written to Sage 100 at all. In the worst case, a broken Rate Code setup in Sage 100 stops the entire sync run before any employees are processed.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| A compensation record was found with a pay rate of 0 or less. Please review and ensure the pay rate is correctly entered before proceeding. | Write: Arcoro to Sage 100 | Employee entity, Compensations scope enabled, employee not terminated, and at least one of the employee's Compensation records in Arcoro has a Pay Rate of 0, blank, or negative. | Collection item skipped. The Error is logged once per employee; each individual compensation record with a non-positive Pay Rate is then dropped from that sync, the rest of the employee still syncs. | In Arcoro, open the employee's Compensation record and correct the Pay Rate to a value greater than 0. |
| Duplicate Compensation records received from the source system. Only the first record will be processed. | Write: Arcoro to Sage 100 | Employee entity, Compensations scope enabled, employee not terminated. After Arcoro's per Rate Code record selection, a second incoming Compensation record still matches an existing Sage 100 pay record that an earlier record in the same sync already claimed. | Collection item skipped. Only that later duplicate compensation record is dropped; the first matching record and the rest of the employee still sync. | In Arcoro, review the employee's Compensation records and remove or correct the duplicate so only one record maps to the existing Sage 100 pay record. |
| Compensation record for (RateCode-PayRate) [rate code] - [pay rate] has a future effective date. Sage 100 Construction does not support this. The compensation record will not be Synced. | Write: Arcoro to Sage 100 | Employee entity, Compensations scope enabled, employee not terminated, and the Compensation record's Pay Start Date in Arcoro is tomorrow or later. | Collection item skipped. That compensation record is dropped from the sync; the rest of the employee still syncs. | In Arcoro, remove the future dated Compensation record or change its start date to today or earlier. |
| PayType [rate code] could not be matched within HH2. The record will not be synced. | Write: Arcoro to Sage 100 | Employee entity, Compensations scope enabled, employee not terminated, the compensation record passed the other checks, but its Rate Code did not resolve to a Pay Type Id in the preloaded Sage 100 Pay Type lookup. | Collection item skipped. That compensation record is dropped from the sync; the rest of the employee still syncs. | In Arcoro, set the Compensation record's Rate Code to a value that matches an active, uniquely described Regular or Overtime Pay Type in Sage 100. |
| Compensation record for pay rate [pay rate] sent from source does not have a rate type. The compensation record will not be Synced. | Write: Arcoro to Sage 100 | Employee entity, Compensations scope enabled, employee not terminated, Pay Rate greater than 0, and the Compensation record's Rate Code (PayRateTypeCode) is blank. | Collection item skipped. That compensation record is dropped from the sync; the rest of the employee still syncs. | In Arcoro, add a Rate Code to the employee's Compensation record. |
| Pay Frequency [pay frequency] could not be matched to a valid value in HH2. This employee will not be updated in HH2. | Write: Arcoro to Sage 100 | Employee entity, checked for every employee write regardless of scope. The employee's Pay Frequency in Arcoro is not blank but does not map to Weekly, Biweekly, Semimonthly, or Monthly. | Whole record skipped. The entire employee write is rejected; no fields for that employee are sent to Sage 100 on this run. | In Arcoro, change the employee's Pay Frequency to Weekly, Biweekly, Semimonthly, or Monthly. |
| Pay Frequency is required by Sage 100 Construction. This employee will not be updated in HH2. | Write: Arcoro to Sage 100 | Employee entity, checked for every employee write regardless of scope. The employee's Pay Frequency field in Arcoro is blank. | Whole record skipped. The entire employee write is rejected; no fields for that employee are sent to Sage 100 on this run. | In Arcoro, set a Pay Frequency on the employee record. |
| [Pay frequency name] does not have a valid pay period count in HH2. Contact support to correct the issue. | Read: Sage 100/HH2 into Arcoro (Pay Schedule) | Pay Schedule entity. This entity is not read from Sage 100 or HH2 at all; it is generated from a fixed list built into the provider. Under the current list, this only occurs for a pay frequency value the provider has not yet mapped to a pay period count; it is not something current data can trigger. | Whole record skipped. That one Pay Schedule entry is left out of the read; other pay frequencies still sync. | Escalate. This is a provider defect, not a data problem you. |
| Pay Rate Type record does not have a Description property, this field is required to be unique. | Read: Sage 100/HH2 into Arcoro (Rate Code) | Rate Code entity. A Sage 100 Pay Type record has a blank Description. | Whole record skipped. That Pay Type is left out of the Rate Code read; other Pay Types still sync. | In Sage 100, add a Description to the Pay Type record. |
| A duplicate pay type description with a value of '[description]' has been detected. Descriptions must be unique to ensure accurate mapping of compensation records between systems. Modify one or more of the rate types in Sage 100 Construction with this description to ensure each value is unique and run the Sync again. | Read: Sage 100/HH2 into Arcoro (Rate Code) | Rate Code entity. A second Sage 100 Pay Type with the same Description as one already read in this same run is encountered, checked before the Regular/Overtime type filter and the archived filter, so it can occur even for a Pay Type that would otherwise be skipped. | Collection item skipped. Only that later duplicate Pay Type is left out of the Rate Code read; the first one with that description still syncs. | In Sage 100, rename one of the duplicate Pay Type Description values so each is unique. |
| A duplicate pay type description with a value of '[description]' has been detected. Descriptions must be unique to ensure accurate mapping of compensation records between systems. Modify one or more of the rate types in Sage 100 Construction with this description to ensure each value is unique and run the Sync again. | Read and write preload: Sage 100/HH2 into Arcoro (Employee, Pay Type lookup) | Employee entity. While preloading the Pay Type lookup used to resolve employee compensation, two non-archived Sage 100 Pay Types share the same Description (or the same Id turns up twice). On the read side this preload only runs when Compensations is an enabled scope; on the write side it always runs, regardless of scope. | Sync stopped. This is a preload step, not a per-record check. Every failed Pay Type in it marks the preload invalid, and once preload finishes the Employee entity throws a terminal error that halts the entire sync run before any employee is processed or written. | In Sage 100, rename the duplicate Pay Type Description values so each is unique, then run the sync again. |
| Duplicate Pay Group records were read from HH2 with Name '[name]', they may differ in casing. Correct the data in HH2 and run the sync again. | Read: Sage 100/HH2 into Arcoro (Pay Group) | Pay Group entity. Two or more non-archived Sage 100 Certified Class records share the same Name, compared without regard to casing. | Whole record skipped, for every Pay Group in the duplicate-name group, not only the one named in the message. All of them are excluded from the read until the names are made unique. | In Sage 100, rename one of the duplicate Certified Class Name values so each is unique, including casing. |
Confirming the Error
- Open the sync execution in question in the Arcoro sync history.
- Find the step for the Sage 100 connector and open it.
- For a compensation or pay frequency issue, open the Employee entity row inside that step. For a rate code issue, open the Rate Code entity row. For a pay group issue, open the Pay Group entity row. For the pay period count issue, open the Pay Schedule entity row.
- Check the Errors, Warnings, Information, Failures, Added, Updated, and Unchanged columns for that entity row. A non-zero Errors count on Employee, Rate Code, or Pay Group means individual records were skipped; the rest of that entity may still show Added or Updated counts.
- Open the entity's error list and match on the fixed part of the sentence (for example "could not be matched within HH2" or "does not have a rate type"), not on the quoted values, since those vary per employee or Pay Type.
- If the duplicate pay type description message appears and the whole run shows a Failure instead of, or in addition to, per-record Errors on Employee, this is the preload case: the entire run stopped before employees were processed, even though the message text still names one specific Pay Type description.
Resolving the Error
Compensation Record Errors (Fix in Arcoro)
- Identify the affected employee from the entity row and open their record in Arcoro.
- Open the Compensation record named in the message.
- For a 0 or negative pay rate, correct the Pay Rate to a positive value.
- For a future effective date, change the start date to today or earlier, or remove the record if it should not exist yet.
- For a missing rate type, add a Rate Code to the record.
- For a duplicate record, compare the employee's Compensation records and remove or correct whichever one should not have been sent.
- Re-run the sync and confirm the Employee entity's Errors count for this employee is gone and the record shows Added or Updated.
Rate Code (Pay Type) Errors, Including the Preload Case (Fix in Sage 100)
- In Sage 100, open Pay Type setup and find the rate type named in the message.
- If the Description is blank, add one.
- If two Pay Types share a Description, rename one so every Description is unique.
- If a compensation record could not be matched to a Pay Type, confirm the Rate Code used on the Arcoro compensation record matches an existing, uniquely described, active Regular or Overtime Pay Type in Sage 100.
- Run the sync again. If the duplicate description previously caused the whole run to stop (a Failure alongside no Employee records processed), confirm the run now completes and Employee rows show Added or Updated.
Pay Frequency Errors (Fix in Arcoro)
- Open the employee record in Arcoro.
- Set the Pay Frequency field if it is blank.
- If the Pay Frequency is set but not recognized, change it to Weekly, Biweekly, Semimonthly, or Monthly. Sage 100 Construction does not support any other frequency.
- Re-run the sync and confirm the employee is no longer skipped.
Duplicate Pay Group (Fix in Sage 100)
- In Sage 100, open Certified Class setup.
- Find the Certified Class records that share the Name given in the message. Remember the comparison ignores casing, so "Foreman" and "foreman" count as duplicates.
- Rename all but one so every Name is unique.
- Re-run the sync and confirm the Pay Group entity shows Added or Updated for all of the previously affected groups, not just the one named in the message.
Pay Schedule Missing Pay Period Count (Escalate)
- Do not attempt to fix this in either Sage 100 or Arcoro; the Pay Schedule entity is generated from a fixed internal list, not from your data.
- Escalate with the exact pay frequency name from the message.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- Any occurrence of the pay period count message, since no customer-side data change can fix it.
- A duplicate pay type description message that keeps recurring after you have renamed the Sage 100 Pay Types, especially if the run shows a Failure and no employees processed at all.
- An employee that still fails on Pay Frequency or Compensation after you confirm the Arcoro values look correct; there may be a mismatch in how Sage 100 exposes the underlying Pay Type or frequency that needs engineering review.
- Any case where the Errors or Failures count does not match what this article describes, since that may indicate a different, undocumented code path.