Arcoro Payroll reserves a special Pay Schedule (also shown as Pay Group on time and expense records) named Terminated, for employees who have left the company. When an employee is assigned to that Terminated pay schedule, the sync expects the employee to already be inactive in the data it receives, and to have a Termination Date that is today or earlier. If the employee is still shown as active, or the Termination Date is missing, or the Termination Date is set in the future, Arcoro Payroll will not write that employee's record, so that pay for a terminated employee cannot be mixed up with pay for an active one. The fix is always a data correction in the source system that feeds this sync step, never a setting inside Arcoro Payroll itself.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| The employee belongs to the Terminated pay schedule but is still active in the source system. The record will not be synced. Please correct the data and run the sync again. | Write (into Arcoro Payroll) | The record is on the Terminated pay schedule and the employee is not explicitly shown as inactive in the data available to this write. | Employee record skipped entirely; also skips the same employee's Expense batch, Time Off Balance update, and Time Record batch for the pay period, on whichever of those entity rows the same condition is met. Logged as an Error, never a Failure. | Mark the employee inactive in the source system feeding this sync step, then rerun. |
| The Termination Date is required for employees in the Terminated pay schedule. The record will not be synced. Please correct the data and run the sync again. | Write (into Arcoro Payroll) | The record is on the Terminated pay schedule and no Termination Date is present in the data available to this write. | Same per-entity skip pattern as the row above. Logged as an Error, never a Failure. | Add a Termination Date for the employee in the source system feeding this sync step, then rerun. |
| The Termination Date cannot be set in the future for employees in the Terminated pay schedule. The record will not be synced. Please correct the data and run the sync again. | Write (into Arcoro Payroll) | The record is on the Terminated pay schedule and a Termination Date is present but is later than today. A Termination Date of today or earlier does not trigger this. | Same per-entity skip pattern as the two rows above. Logged as an Error, never a Failure. | Correct the Termination Date so it is today or earlier in the source system feeding this sync step, then rerun. |
All three messages above can appear on any of the four entity rows below within the same sync execution, and every occurrence points to the same underlying employee data problem. How the sync decides a record is on the Terminated pay schedule is not identical across entities, which matters when comparing what you see across rows:
| Entity row | How "Terminated" is detected for this entity | Notes |
|---|---|---|
| Employees | The employee's own Pay Schedule field, sent by the source connector, equals Terminated. Checked on every Employee write, regardless of any run-time setting on the sync. | Not tied to a specific employee scope; the check runs before any scope-specific fields are written. |
| Expenses | The whole sync execution's Pay Schedule parameter (set in the Run Sync dialog) equals Terminated. This is a run-wide setting, not a per-record field. | If this run's Pay Schedule parameter is not Terminated, none of these three messages can fire on this entity row for that execution. |
| Time Off Balances | The record's own Pay Group field, populated by the source connector, equals Terminated. Checked per record, independent of the run-time Pay Schedule parameter. | Only the first of the three conditions that fails is reported for a given record; unlike the other three entities, a single Time Off Balance record cannot log more than one of these three messages in the same run. |
| Time Records | The whole sync execution's Pay Schedule parameter equals Terminated, the same run-wide setting used for Expenses. | If this run's Pay Schedule parameter is not Terminated, none of these three messages can fire on this entity row for that execution. |
None of these three messages includes the employee's name or ID in the text itself. Each error entry in Sync History is tied to that record's Friendly Identifier, a human-readable key the source connector assigns to the record (commonly the employee's name or employee number). Use the Friendly Identifier shown next to the matching error line, not the message text, to work out which employee is affected.
Confirming the Error
- Open the sync execution in Sync History.
- Open the step for the Arcoro Payroll connector.
- Find the entity row where the issue was reported: Employees, Expenses, Time Off Balances, or Time Records.
- Open that entity row's Errors list.
- Match on the fixed part of the sentence, since none of these three messages carry a variable value: "still active in the source system", "Termination Date is required", or "Termination Date cannot be set in the future".
- Note the Friendly Identifier shown with the matching error line to identify the employee.
- Check whether the same employee's identifier also appears under other entity rows (Employees, Expenses, Time Off Balances, Time Records) in the same execution. If so, correcting the employee's data in the source system clears all of them, since they share one root cause.
- A non-zero Failures count is unrelated to this family: these three messages always land in the Errors column, never in Failures. Treat a non-zero Failures count as a separate issue.
Resolving the Error
Employee Is on the Terminated Pay Schedule but Still Active
- In the source system that feeds this sync step (for example, Arcoro Time (formerly ExakTime), or the connected HR source), open the employee's record.
- Confirm whether the employee's Pay Schedule (or Pay Group) is intentionally set to Terminated.
- If it is intentional, mark the employee inactive (terminated) in that source system.
- If the Terminated assignment was not intentional, correct the employee's Pay Schedule (or Pay Group) to the correct value instead.
- Rerun the sync for the affected entity and confirm the error no longer appears for that employee.
Termination Date is Missing
- In the source system that feeds this sync step, open the employee's record.
- Enter a Termination Date for the employee.
- Rerun the sync for the affected entity and confirm the error no longer appears for that employee.
Termination Date Is in the Future
- In the source system that feeds this sync step, open the employee's record.
- Check the Termination Date. It must be today's date or earlier; any later date will always trigger this error, even for a termination that is genuinely scheduled ahead of time.
- Correct the date to reflect an already-effective termination, or wait until that date has passed before running the sync again.
- Rerun the sync for the affected entity and confirm the error no longer appears for that employee.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- The employee's Pay Schedule (or Pay Group) already correctly shows Terminated, with a valid past Termination Date, and the error still appears after a rerun.
- The error appears on an Expenses or Time Records row for an execution where the connector's Pay Schedule run parameter was not set to Terminated.
- Your source connector is not Arcoro Time (formerly ExakTime) or a connected HR source, and you cannot locate an equivalent active-status or Termination Date field to correct.
- The Sync History error entry has no Friendly Identifier, so the affected employee cannot be identified at all.