The Payroll connector needs certain values before it can talk to Payroll or process a sync step. Some of these values live on the connector itself, and some are entered each time the sync is run. When one of these values is missing, blank, or does not match anything in Payroll, the connector cannot proceed and logs one of the messages below. Depending on which value is missing, the effect ranges from skipping a single entity for that run up to stopping the entire sync.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Payroll Provider could not read the required configuration setting for the Base URL. Try the Sync again and if this problem persists contact Arcoro support. | Read and write (connector-wide) | The Base URL used to reach Payroll cannot be read from application configuration. This is checked every time the connector is built, before any entity is processed. | Sync stopped. The entire run fails immediately, before any entity is read or written. | Escalate to Arcoro support. This is not a connector field you can edit. |
| Payroll Provider could not read the required configuration setting for the API Token. Try the Sync again and if this problem persists contact Arcoro support. | Read and write (connector-wide) | The API Token used to authenticate with Payroll cannot be read from application configuration. This is checked when the connector authenticates, before any entity is processed. | Sync stopped. The entire run fails immediately, before any entity is read or written. | Escalate to Arcoro support. This is not a connector field you can edit. |
| Payroll Provider could not read the configuration setting '[setting name]'. | Read and write (connector-wide) | The named connector property is blank or missing. In Payroll the only setting that reaches this message is CompanyId. This is checked every time the connector is built, before any entity is processed. | Sync stopped. The entire run fails immediately, before any entity is read or written. | Enter a value in the CompanyId field on the connector. |
| When syncing benefits both the deductions and fringes scopes must be selected. Update the sync settings to include both scopes and execute the sync again. | Write | The Employees entity write has exactly one of the Deduction Benefits or Fringe Benefits scopes selected, not both. (If neither scope is selected, benefits are silently skipped with no message.) | Field/section skipped only. The employee record still writes; only the benefit deductions and fringes are skipped for that employee. This repeats for every employee while the scopes remain mismatched. | Select both the Deduction Benefits and Fringe Benefits scopes for the sync step. |
| The Sync execution includes General Ledger but does not specify the Pay Date. This value is required for the Provider to read data. Update the Sync to specify the Pay Date and execute the Sync again. | Read | The General Ledger entity is included in the sync step but no Pay Date value was supplied for the run. | Whole record skipped. General Ledger produces exactly one record per run, so this skips the entire General Ledger entity for this run. Other entities in the step continue. | Provide a Pay Date value when running the sync. |
| The Pay Schedule filter provided does not exist in Payroll and is invalid. Correct or remove the filter value and execute the Sync again. | Read | A Pay Schedule filter value was supplied for the run, but no pay schedule with that name exists in Payroll. Fires on the General Ledger entity and on the Pay Schedules entity. | Depends on entity. On General Ledger: whole record skipped, other entities continue. On Pay Schedules: sync stopped, the entire run fails. | Correct or remove the Pay Schedule filter value for the run. |
| The 'Pay Schedule' parameter is required when syncing Time Records. Please provide a value for the Pay Schedule when executing the sync again. | Read | The Time Cards entity read starts and the Pay Schedule value was not supplied for the run. Checked before any record is read. | Sync stopped. The entire run fails before any Time Cards record is read. | Provide a Pay Schedule value when running the sync. |
| The 'Pay Date' parameter is required when syncing Time Records. Please provide a value for the Pay Date when executing the sync again. | Read | The Time Cards entity read starts, a Pay Schedule value was supplied, but no Pay Date value was supplied for the run. Checked before any record is read. | Sync stopped. The entire run fails before any Time Cards record is read. | Provide a Pay Date value when running the sync. |
| The Sync execution includes Expenses but does not specify the Start Date and End Date. These values are required for the Provider to Sync Expenses. Update the Sync to specify these values and execute the Sync again. | Write | The Expenses entity write starts for an employee and the Pay Period Start Date and/or Pay Period End Date value was not supplied for the run. | Record skipped. Since the missing value applies to the whole run, this repeats for every employee record in the Expenses entity this run; other entities continue. | Provide both a Pay Period Start Date and a Pay Period End Date when running the sync. |
| The Sync execution includes Time Off Balance but does not specify the Start Date and End Date. These values are required for the Provider to Sync Time Off Balance. Update the Sync to specify these values and execute the Sync again. | Write | The Time Off Balances entity write starts for an employee and the Pay Period Start Date and/or Pay Period End Date value was not supplied for the run. | Record skipped. Since the missing value applies to the whole run, this repeats for every employee record in the Time Off Balances entity this run; other entities continue. | Provide both a Pay Period Start Date and a Pay Period End Date when running the sync. |
| The Sync execution includes Time Records but does not specify the Start Date and End Date. These values are required for the Provider to Sync Time Records. Update the Sync to specify these values and execute the Sync again. | Write | The Time Cards entity write starts for an employee and the Pay Period Start Date and/or Pay Period End Date value was not supplied for the run. | Record skipped. Since the missing value applies to the whole run, this repeats for every employee record in the Time Cards entity this run; other entities continue. | Provide both a Pay Period Start Date and a Pay Period End Date when running the sync. |
Confirming the Error
- Open Sync History and locate the sync execution for the date and time in question.
- Open the step for the Payroll connector (as source or destination, matching the direction in the table above).
- Check the step-level status and the Failures column first. Since most of these messages stop the whole run, expect the step to show a Failed or Cancelled status with a non-zero count in Failures if one of the connector-wide or parameter-required messages fired.
- If the step completed, open the entity row (Employees, General Ledger, Pay Schedules, Time Cards, Expenses, or Time Off Balances) and check its Errors column for a non-zero count. This is where the entity-level or record-level messages (General Ledger Pay Date, Deduction/Fringe scope pairing) show up even though the run otherwise completed.
- Open the message list for that entity or step and match the message using the fixed part of the sentence, not the values shown in quotes or brackets, since those values vary by account and by run.
Resolving the Error
Connector Properties
- Open the connector setup screen for this Payroll connector in the Arcoro platform.
- If the message names CompanyId, enter the Payroll company identifier in the CompanyId field. If a Business Unit is also selected on the connector, note that the Business Unit value is used as the effective company instead of CompanyId, so confirm the correct Business Unit is chosen if you expected it to take priority.
- If the message is about the Base URL or the API Token, do not attempt to enter a value. Neither is a field on the connector setup screen; see When to escalate.
- Save the connector and try to run the sync again.
Sync Execution Parameters
- Open the Run Sync dialog for the sync step that includes this Payroll connector.
- For a Pay Schedule message, enter a Pay Schedule value that matches an existing pay schedule name in Payroll exactly.
- For a Pay Date message, enter a Pay Date value for the run.
- For a Start Date and End Date message (Expenses, Time Off Balances, or Time Cards write), enter both a Pay Period Start Date and a Pay Period End Date. Both are required together; supplying only one still triggers the message.
- For the benefits scope pairing message, go to the sync step's scope selection for Employees and make sure both Deduction Benefits and Fringe Benefits are checked, or both unchecked.
- Execute the sync again and confirm, using the How to confirm steps above, that the affected entity or step now shows zero in Errors and Failures, with the expected counts in Added, Updated, or Unchanged.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- Any Base URL or API Token message. Both messages explicitly say to contact Arcoro support, and neither value is exposed as a connector field.
- A CompanyId message that persists after the CompanyId field has been confirmed correct and saved on the connector.
- A Pay Schedule filter message on the Pay Schedules entity (which stops the entire run) when you can confirm the pay schedule name genuinely exists in Payroll and matches exactly.
- Any message in this article that keeps recurring after your fix has been applied and the sync re-run.