These messages all mean Payroll could not accept part of an employee's pay setup or a piece of logged time because a value it needed either was not sent, did not match anything already configured in Payroll, or conflicts with another value already synced in the same run. Some of these fire directly on the Employee record. The rest fire while Payroll is turning time cards into paid earnings, and they still point back to the employee's or the company's compensation setup, not to the time card itself. If you arrived here from a time and expense ticket, that is why: the message is filed under Time Record in the sync log, but the fix belongs to a Rate Code, Earning Rate, or Pay Schedule.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Employee Type is required by Payroll and the provided value '[compensation type]' is missing or could not be converted to a valid type. This record will not be synced. Correct the data in the source system and execute the sync again. | Arcoro to Payroll (write) | The employee's Compensation Type field is not set to Hourly or Salary. Any other value, including a blank value, fails this check. | Record skipped. The whole employee record is not synced. | Set the employee's Compensation Type to Hourly or Salary in the source system. |
| No active pay schedule '[pay schedule name]' was found in Payroll. This record will not be synced. Correct the data and run the sync again. | Arcoro to Payroll (write) | The employee has a Pay Schedule value that is not "Terminated", and either no Pay Schedule in Payroll has that exact name (case-insensitive), or a matching Pay Schedule exists but is explicitly marked inactive in Payroll. A blank Pay Schedule value does not trigger this message; see the next row instead. | Record skipped. The whole employee record is not synced. | Create or reactivate a Pay Schedule in Payroll with that exact name, or correct the Pay Schedule name on the employee in the source system. |
| Employee Pay Schedule is required by Payroll. This record will not be synced. Correct the data in the source system and execute the sync again. | Arcoro to Payroll (write) | The employee's Pay Schedule field has no value at all (not even a blank string). An empty string is treated differently and produces the "No active pay schedule" message above instead, quoting an empty value. | Record skipped. The whole employee record is not synced. | Assign a Pay Schedule to the employee in the source system. |
| The Rate Code's Code property is required by Payroll. This record will not be synced. Correct the data in the source system and execute the sync again. | Arcoro to Payroll (write) | The Rate Code record being synced has no value in its Code field. | Record skipped. The whole Rate Code record is not synced. | Enter a Code value on the Rate Code in the source system. |
| The Rate Code's Type property is required by Payroll. This record will not be synced. Correct the data in the source system and execute the sync again. | Arcoro to Payroll (write) | The Rate Code record being synced has no value in its Type field. | Record skipped. The whole Rate Code record is not synced. | Set a Type value on the Rate Code in the source system. |
| A Rate Code with Code: [code], RateType: [type] has been sent to Payroll multiple times. Only the first Rate Code received will be processed and saved. Correct the source data and run the sync again. | Arcoro to Payroll (write) | Two or more Rate Code records in this same sync run have the same Code and Type combination (case-insensitive). This only compares records within the current run, not against Rate Codes already saved in Payroll from an earlier sync. | Record skipped. Only the second and later duplicates in the run are skipped; the first one synced normally. | Remove or rename the duplicate Rate Code in the source system so each Code and Type combination appears once. |
| The employee does not contain an Earning Rate in Payroll for '[plan name or rate code]'. The time cards for this Pay Schedule will not be processed. Either add the Earning Rate in Payroll for the Employee or modify the Source System to use a different Pay Schedule for the time cards and execute the Sync again. | Arcoro to Payroll (write). Filed under the Time Record entity, but the fix is on the employee's compensation setup in Payroll. | For one logged time entry, the employee has no active Earning Rate in Payroll whose name matches that entry's Plan Name (or its Rate Code, if no Plan Name is set). This is checked only after a matching company-level Earning Code was already found; if the company has no matching Earning Code at all, the next row's message fires instead and this one does not. An inactive Earning Rate with a matching name does not count as a match. | Collection item skipped. Only that one earning line, for that one rate code or plan, on that one time card is dropped. Other earnings on the same time card, other time cards, and the rest of the employee's payroll item still sync. Despite the message text, this is not every time card for the pay schedule. | Add or reactivate an Earning Rate for that employee in Payroll matching the Plan Name or Rate Code, or change the rate/plan used on the time entries in the source system. |
| The company does not contain an Earning Code in Payroll for '[plan name or rate code]'. The time cards for this Pay Schedule will not be processed. Either add the Earning Rate in Payroll for the Employee or modify the Source System to use a different Pay Schedule for the time cards and execute the Sync again. | Arcoro to Payroll (write). Filed under the Time Record entity, but the fix is on the company's compensation setup in Payroll. | For one logged time entry, no company-level Earning Code in Payroll has a name matching that entry's Plan Name (or its Rate Code, if no Plan Name is set). This check runs before the employee Earning Rate check above, so it fires instead of that one when the company-level code is the piece that is missing. | Collection item skipped. Only that one earning line, for that one rate code or plan, on that one time card is dropped. Other earnings on the same time card, other time cards, and the rest of the employee's payroll item still sync. Despite the message text, this is not every time card for the pay schedule. | Add an Earning Code in Payroll with that name, or correct the Plan Name or Rate Code used on the time entries in the source system. |
| No earning rates found for this employee in payroll. The time cards for this employee will not be processed. Provide the missing data in payroll for this employee and execute the Sync again. | Arcoro to Payroll (write). Filed under the Time Record entity, but the fix is on the employee's compensation setup in Payroll. | The employee has zero active Earning Rates in Payroll at all, not just a missing rate for one rate code. This is checked once for the whole time submission, before any individual time card or earning line is looked at. | Record skipped. None of this employee's time cards in this sync run are written. | Add at least one active Earning Rate for this employee in Payroll. |
| Wage Determination - Employee cannot have multiple earnings of the same type (REG, OT, DT) with different compensation amounts. Please correct the employee's compensation and execute the sync again. | Arcoro to Payroll (write). Filed under the Time Record entity, but the fix is on the employee's compensation setup. | Wage Determination and its automatic rate-setting are both enabled, and for the same Job, Labor Classification, and earning type (regular, overtime, or double time) the time entries being synced for this employee resolve to more than one distinct compensation amount. This only applies to time entries that match an active Wage Determination pay rate table and labor class rule for that job and date range. | Collection item skipped. Only the earning lines that hit the same Job, Labor Classification, and earning type conflict are dropped. Other earnings on the same time card and other time cards still sync. | Correct the employee's compensation or pay rate table in Payroll so only one rate applies for that Job, Labor Classification, and earning type, then re-run the sync. |
Confirming the Error
- Open the sync execution for your connector in Sync History.
- Find the step for the Payroll connector.
- For the Rate Code and Employee messages, locate the Employee or Rate Code entity row in that step and check its Errors column. A non-zero Errors count means at least one record failed validation.
- For the four Time Record messages, locate the Time Record entity row instead. These do not appear under Employee or Rate Code even though the fix happens there.
- Open the entity's errors list and match on the fixed part of the sentence, for example "is required by Payroll" or "does not contain an Earning Code in Payroll", not on the value shown in quotes.
- The Sync History columns for an entity are labelled Errors, Warnings, Information, Failures, Added, Updated, and Unchanged. None of the ten messages in this article are logged as a Failure; a non-zero Failures count on the same row is a separate problem and is not covered by this article.
Resolving the Error
Employee Type Is Required by Payroll
- In the source system, open the employee and find the field that maps to Compensation Type.
- Set it to Hourly or Salary. No other value is accepted.
- Re-run the sync and confirm the employee no longer appears in the Employee entity's errors list.
No Active Pay Schedule Found/Employee Pay Schedule Is Required
- In the source system, open the employee and check the Pay Schedule field. If it is blank, assign one.
- In Payroll, confirm a Pay Schedule exists with the exact same name and is active. If it does not exist or is inactive, create it or reactivate it, or correct the name on the employee in the source system so the two match.
- If every employee with a Pay Schedule value is failing this way, check whether the Pay Schedule scope for the Employee entity is enabled on this connector. If that scope is off, Payroll's list of Pay Schedules is never loaded and every employee with a Pay Schedule value will fail this check regardless of whether the schedule exists.
- Re-run the sync and confirm the employee no longer appears in the Employee entity's errors list.
Rate Code’s Code or Type Property Is Required
- In the source system, open the Rate Code record and fill in the missing Code or Type field.
- Re-run the sync and confirm the Rate Code no longer appears in the Rate Code entity's errors list.
Rate Code Has Been Sent to Payroll Multiple Times
- In the source system, find the Rate Code records sharing the Code and Type combination named in the message.
- Remove or rename all but one of them so each Code and Type combination is unique.
- Re-run the sync and confirm only one record syncs and no duplicate message appears.
Employee Does Not Contain an Earning Rate/Company Does Not Contain an Earning Code
- Note the Plan Name or Rate Code quoted in the message.
- In Payroll, check whether an Earning Code with that exact name exists at the company level. If not, add one.
- In Payroll, check whether the employee has an active Earning Rate with that exact name. If not, add or reactivate one for that employee.
- Alternatively, in the source system, change the time entries to use a rate or plan that already has a matching, active Earning Code and Earning Rate in Payroll.
- Re-run the sync and confirm the affected earning line now appears on the employee's payroll item in Payroll instead of in the errors list.
No Earning Rates Found for This Employee in Payroll
- In Payroll, open the employee's compensation setup and confirm at least one Earning Rate is present and active.
- Add an active Earning Rate if none exists.
- Re-run the sync and confirm the employee's time cards now sync instead of being skipped entirely.
Wage Determination Conflicting Rates
- Note the Job and Labor Classification named on the affected time cards.
- In Payroll, review the employee's compensation and the Wage Determination pay rate table for that Job and Labor Classification.
- Correct the setup so only one rate amount applies for a given earning type (regular, overtime, or double time) for that Job and Labor Classification.
- Re-run the sync and confirm the affected earning lines now sync instead of being skipped.
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 source data and Payroll setup have both been corrected and the sync has been re-run.
- The log text does not match any message in the table above.
- The Failures count on the entity row is non-zero; that is a different condition not covered by this article.
- The log text looks like it is passed through from Payroll itself rather than one of the Arcoro messages listed here.