Arcoro Time stores two lookup lists that pay depends on: Rate Codes (how an hour is paid) and Pay Schedules, also called Pay Groups (how often an employee is paid). When a Time Card cannot be matched to a valid, active Rate Code or Pay Schedule, or when a Rate Code or Pay Schedule record itself is missing required data or duplicated, the sync skips that piece rather than guessing. Some of these checks compare against other records in the same run, and some compare against what Arcoro Time already has on file — the fix is different depending on which one fired, so read the message and the table below carefully.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Time Card contains [hours type: Regular, Overtime, or Double Time] hours that are either missing a Rate Code or are assigned a value that could not be resolved to an Active Rate Code. These records will not be Synced. Correct the Employee's data in Arcoro Time and run the Sync again. | Read — Arcoro Time out into Payroll. | Only under the Time for Payroll Configuration connector configuration. Fires separately for each of the Regular, Overtime, and Double Time hour buckets on a Time Card: that bucket has hours logged, no Plan-based rate override applies to it, and its assigned Rate Code is either blank or is not an Active Rate Code in Arcoro Time. All three buckets behave identically — only the bucket named in the message differs. | Collection item skipped. Only that one hours line is dropped. The Time Card, and any other hour buckets on it, still sync. | In Arcoro Time, assign an Active Rate Code to the employee for that hours type, then re-run the sync. |
| One or more Time Cards for Employee [Employee ID] are either missing a Pay Schedule or are assigned a value that could not be resolved. These records will not be Synced. Correct the Employee's data in Arcoro Time and run the Sync again. | Read — Arcoro Time out into Payroll. | Only under the Time for Payroll Configuration connector configuration, and only after the employee was matched and has an Employee ID. In practice this fires when the Pay Schedule referenced by the employee's Time Cards for this run does not resolve to a Pay Schedule Arcoro Time has on file (an orphaned or unrecognized Pay Schedule reference); Time Cards with no Pay Schedule reference at all are excluded earlier in the run and never reach this check, so this message almost always means an unresolvable reference rather than a truly blank one. | Whole record skipped. None of that employee's Time Cards for this run are synced. | In Arcoro Time, open the employee and confirm their Pay Schedule assignment points at a Pay Schedule that still exists, then re-run the sync. |
| A Rate Code with '[Name: X, RateType: Y]' has already been read. This field must be unique and the record will not be Synced. Modify the data in Arcoro Time to make each record have a unique Name and execute the Sync again. | Read — Arcoro Time Rate Codes catalog out into the sync. | Two or more Rate Codes in Arcoro Time share the same Name and Rate Type, compared case-insensitively against every Rate Code already read earlier in this same run. | Whole record skipped. The first Rate Code with that Name and Rate Type is synced; every later duplicate is not. | In Arcoro Time, rename the duplicate Rate Code so its Name is unique for that Rate Type, then re-run the sync. |
| A Pay Group with Name: '[Name]' has already been read. This field must be unique and the record will not be Synced. Modify the data in Arcoro Time to make each record have a unique Name and execute the Sync again. | Read — Arcoro Time Pay Schedules catalog out into the sync. | Two or more Pay Schedules in Arcoro Time share the same Name, compared case-insensitively against every Pay Schedule already read earlier in this same run. | Whole record skipped. The first Pay Schedule with that Name is synced; every later duplicate is not. | In Arcoro Time, rename the duplicate Pay Schedule so its Name is unique, then re-run the sync. |
| A Pay Schedule was sent from the source system without the required Source System Id property. This record will not be processed. Contact support to have the provider corrected so this value is always set. | Write — from the connected source system into Arcoro Time. | The incoming Pay Schedule record has no Source System Id. This identifier is assigned automatically by the source system's own sync logic, not typed in by a user, so a blank value is a defect in that logic rather than a data entry problem. | Whole record skipped. The Pay Schedule is not written to Arcoro Time. | Escalate. |
| A Pay Schedule was sent from the source system without the required Name property. This record will not be processed. Correct the data in the source system and execute the Sync again. | Write — from the connected source system into Arcoro Time. | The incoming Pay Schedule record has a blank or whitespace-only Name. | Whole record skipped. The Pay Schedule is not written to Arcoro Time. | In the source system, give the Pay Schedule a Name, then re-run the sync. |
| A Pay Schedule with Name: '[Name]' has been sent multiple times from the source system. This field must be unique and only the first record will be Synced. Modify the data in the source system to make each record have a unique Name and execute the Sync again. | Write — from the connected source system into Arcoro Time. | The same Name (case-insensitive) has already been sent by the source system earlier in this same sync run. This compares only against records sent so far in this run, not against what already exists in Arcoro Time. | Whole record skipped. Only the first Pay Schedule sent with that Name this run is written to Arcoro Time. | In the source system, make sure no two Pay Schedules being sent in the same run share the same Name, then re-run the sync. |
| The Pay Schedule record includes an update to the Name property that would result in a duplicate item by Name being created in Arcoro Time. The Name '[Name]' already exists. Correct the data in the source system to have a unique Name and execute the Sync again. | Write — from the connected source system into Arcoro Time. | The incoming record is setting or changing the Pay Schedule's Name, and a Pay Schedule already existing in Arcoro Time has that same Name: on a new Pay Schedule, any existing Arcoro Time Pay Schedule with that Name blocks it; on an update to an existing Pay Schedule, it is blocked only if the Arcoro Time Pay Schedule with that Name is a different record (a different Source System Id) than the one being updated. This checks against Arcoro Time's existing data, not against other records in this run. | Whole record skipped. The Pay Schedule is not written to Arcoro Time. | Look up the Name in Arcoro Time's Pay Schedules list. Either rename the existing Arcoro Time Pay Schedule that is using that Name, or change the Name being sent from the source system so it does not collide, then re-run the sync. |
| A Rate Code was sent from the source system without the required Source System Id property. This record will not be processed. Contact support to have the provider corrected so this value is always set. | Write — from the connected source system into Arcoro Time. | The incoming Rate Code record has no Source System Id. Like the Pay Schedule equivalent, this identifier is assigned automatically by the source system's own sync logic, not typed in by a user. | Whole record skipped. The Rate Code is not written to Arcoro Time. | Escalate. |
| A Rate Code was sent from the source system without the required Code property. This record will not be processed. Correct the data in the source system and execute the Sync again. | Write — from the connected source system into Arcoro Time. | The incoming Rate Code record has a blank or whitespace-only Code. Checked only after the record's Rate Type is one of the four types Arcoro Time accepts; records with an unsupported or missing Rate Type are skipped earlier with no message at all. | Whole record skipped. The Rate Code is not written to Arcoro Time. | In the source system, give the Rate Code a Code value, then re-run the sync. |
| A Rate Code with Values: '[Code: X, Type: Y]' has been sent multiple times from the source system. This record must be unique and only the first record will be Synced. Modify the data in the source system to make each record have unique values and execute the Sync again. | Write — from the connected source system into Arcoro Time. | The same Code and Rate Type combination (case-insensitive) has already been sent by the source system earlier in this same sync run. This compares only against records sent so far in this run, not against what already exists in Arcoro Time. | Whole record skipped. Only the first Rate Code sent with that Code and Rate Type this run is written to Arcoro Time. | In the source system, make sure no two Rate Codes being sent in the same run share the same Code and Rate Type, then re-run the sync. |
Confirming the Error
- Open the sync execution in Sync History for the connector in question.
- Find the row for the affected entity: Time Cards for the two Time Card messages, Rate Codes for the Rate Code messages, or Pay Schedules for the Pay Schedule messages. Confirm the Errors column is greater than zero for that row.
- Open that entity's record detail and match on the fixed part of the sentence (for example "has already been read" or "without the required Name property"), not on the values inside the quotes, since those values are specific to one record.
- For the two Time Card messages, the message is logged against the employee-level record, not a separate row per Time Card. Open that employee's record detail and check the Additional Fields or nested Time Card detail to see which Time Card and which hours bucket or Pay Schedule reference triggered it.
- Check the Added, Updated, and Unchanged columns for the same row to confirm the rest of that entity's records still processed normally.
Resolving the Error
Rate Code or Pay Schedule Missing or Unresolved on a Time Card
- In Arcoro Time, open the employee named in the message (or the employee whose Time Card triggered the Rate Code message).
- For a Rate Code message, confirm the employee has an Active Rate Code assigned for the hours type named in the message (Regular, Overtime, or Double Time).
- For a Pay Schedule message, confirm the employee's Pay Schedule assignment points at a Pay Schedule that still exists in Arcoro Time.
- Save the correction in Arcoro Time and re-run the sync.
- Confirm the fix worked by checking that the entity's Errors count for that run is lower and the employee's Time Card now appears under Added or Updated.
Duplicate Rate Code or Pay Schedule Name Read From Arcoro Time
- In Arcoro Time, find the Rate Codes or Pay Schedules named in the message.
- Rename one of the duplicates so the Name (and, for Rate Codes, the Rate Type) is unique.
- Re-run the sync and confirm the Rate Codes or Pay Schedules row no longer shows an error for that record.
Pay Schedule or Rate Code Rejected While Being Written Into Arcoro Time
- Identify the source system connected to write into Arcoro Time for this connector.
- For a missing Name or Code message, correct that field on the record in the source system.
- For a duplicate-in-this-run message, find the other record sent in the same run with the same Name (or Code and Rate Type) in the source system and make the values unique.
- For the Pay Schedule Name-already-exists message, first check Arcoro Time's Pay Schedules list for the Name in the message. If a different Pay Schedule already holds that Name, either rename it in Arcoro Time or change the Name being sent from the source system so the two do not collide.
- Re-run the sync and confirm the record now appears under Added or Updated instead of Errors.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- Escalate immediately for "Contact support to have the provider corrected" messages (missing Source System ID on a Pay Schedule or Rate Code write). This value is assigned automatically by the source system's own sync logic and is never something you enter.
- Escalate if Time Cards silently missing from Payroll with no error logged at all; that can mean the Time Card had no Pay Schedule reference whatsoever, which is filtered out before this check runs and produces no message.
- Escalate if a Pay Schedule or Rate Code keeps failing the same duplicate or missing-field check after you corrected it in both Arcoro Time and the source system.
- Escalate if the entity row for Rate Codes or Pay Schedules does not appear as an option on the sync step at all; support may need to confirm whether that entity is enabled for your configuration.