Arcoro Time (formerly ExakTime) reads several values before it will run a sync: the Hub connection, the Business Unit the connector is scoped to, the Pay Schedule and Pay Period dates used to filter data, and (for one configuration) a Time Off cost code mapping. If any of these does not check out, the connector stops before it touches a single employee, time record, or other entity. Some of these checks only ever run when you test or save the connector, never during an actual scheduled or on-demand sync. Knowing which is which tells you whether to look at the last sync run or at the connector's own test result. A separate pair of checks runs the opposite way: they only happen per Time Off record while a sync is actually reading time records, and they never stop anything; they only leave that one record's Cost Code blank when the connector's Time Off Cost Code Mapping Override cannot be resolved, so the rest of the record still syncs.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Arcoro Time Provider could not read the configuration setting '[setting name]'. | Both read and write | Two known settings use this message. An internal application setting named Arcoro Time Base URL is blank or missing. Separately, the connector's Pay Period Start Date setting is blank when the code goes looking for it. | For the Arcoro Time Base URL setting: stops the sync immediately, and also fails a connector test or save. For the Pay Period Start Date setting: does not stop anything by itself; it is added to a list of problems that is checked right after, which then stops the sync (or fails the test/save) if anything was collected. | If the setting named is Arcoro Time Base URL, escalate; this is not a user-visible field. If it is named Pay Period Start Date, set that value on the connector or in the Run Sync dialog. |
| The Connector's Pay Group value '[Pay Schedule value]' could not be matched against a valid Pay Group in Arcoro Time. Correct the Connector's Pay Group value and validate the connector again. | Read only | The connector's Pay Schedule setting is filled in, but its value does not match (ignoring upper/lower case) the name of any Pay Group Arcoro Time returns for the company. | Stops the sync at setup. Also returned as a failed result when the connector is tested or saved. | Correct the Pay Schedule value on the connector to match an existing Pay Group name in Arcoro Time exactly. |
| The Business Unit value '[value]' could not be matched against a Business Unit for this company. Select the Business Unit again and run the sync again. | Both read and write | The connector's Business Unit setting can hold one or more values, comma-separated. Each one is compared (ignoring upper/lower case) against the identifier of every Business Unit Arcoro Hub has for the company. This message fires on the first value that does not match any of them. | Stops the sync at setup. This check does not run during a connector test or save, so passing those does not confirm the Business Unit is valid. | Reselect the Business Unit on the connector from the current list, then run the sync again. |
| Business Unit '[identifier - name]' is not active, so the Sync cannot run against it. Activate the Business Unit in Arcoro, or select a different Business Unit, and run the sync again. | Both read and write | A configured Business Unit value matched a real Business Unit, but that Business Unit's active flag is explicitly set to false. A Business Unit whose active flag was never set one way or the other is treated as usable and will not trigger this message. | Stops the sync at setup. This check does not run during a connector test or save. | Reactivate the Business Unit in Arcoro, or choose a different, active Business Unit on the connector. |
| Arcoro Time Syncs require Arcoro Hub, which is not enabled for this company. Contact Arcoro Support to have Hub enabled for the company and run the sync again. | Both read and write | Arcoro Hub is checked for every real sync (not a connector test). This fires when the Hub reports that Hub is not enabled for the company. | Stops the sync at setup, before any Business Unit or entity work begins. Never appears from a connector test or save; the test path does not check Hub. | This is an internal, company-level setting you cannot change yourself. Escalate to have Hub enabled for the company. |
| The Pay Period End Date must come after the Pay Period Start Date. | Both read and write | Both a Pay Period Start Date and an explicit Pay Period End Date are set, and the End Date falls before the Start Date. An End Date equal to the Start Date is allowed and does not trigger this. | Does not stop anything by itself; it is added to a list of problems that is checked right after, which then stops the sync (or fails the test/save). | Correct the Pay Period End Date in the Run Sync dialog so it falls on or after the Start Date. |
| When Pay Period End Date is not provided the Pay Period Start Date must be at least 1 day in the past. | Both read and write | A Pay Period Start Date is set and no Pay Period End Date is given. When no End Date is given it defaults to today, so this fires when the Start Date is also today (not at least one day earlier). | Does not stop anything by itself; it is added to a list of problems that is checked right after, which then stops the sync (or fails the test/save). | Set the Pay Period Start Date to at least one day before today, or supply an explicit Pay Period End Date. |
| The Employee ID set on sync parameter could not be matched against any valid Employee in Arcoro Time. Validate if data is correct, set the Employee ID parameter value and run sync again. | Read only (Time Off Balance) | The Employee Id sync parameter is set to one or more values, and after filtering, not one employee in Arcoro Time matches any of them. If the parameter is left blank this check is skipped entirely. | Stops the sync while the Time Off Balance entity is preparing to read. | Correct the Employee Id parameter value in the Run Sync dialog to match a real employee. |
| Time Off Plans must have a valid mapping to an Intacct Cost Code | Connector test / save only, Intacct Payroll configuration | The connector's Time Off Cost Code Mapping Override has no entries at all. | Never appears in a sync run. Returned as a failed result only when the connector is tested or saved, and only for the Time for Intacct Payroll Configuration product configuration. | Add at least one Time Off Plan to Cost Code mapping entry on the connector. |
| No Cost Code with name:[Cost Code name] was found in Exak Time (the log shows this legacy wording verbatim; the product is Arcoro Time) | Connector test / save only, Intacct Payroll configuration | One of the configured Time Off Cost Code Mapping Override entries names a cost code that does not match (ignoring upper/lower case) any cost code name in Arcoro Time. Checked one mapping row at a time; the first bad row is the one reported. | Never appears in a sync run. Returned as a failed result only when the connector is tested or saved, and only for the Time for Intacct Payroll Configuration product configuration. | Correct the cost code name in that mapping row to match an existing Arcoro Time cost code. |
| No matching Cost Code was found with Name: [Cost Code name] to override default Time Off Cost Code. Review the connector mapping. | Read only. Time for Payroll Configuration (Sage Intacct Companies) or Time for Sage Intacct Configuration. | While reading a Time Off type time record, that record's original Cost Code name matches an entry in the connector's Time Off Cost Code Mapping Override, but the override's target Cost Code name does not match (ignoring upper/lower case) any Cost Code in Arcoro Time that is currently Active. A record whose original Cost Code is not covered by any mapping entry does not trigger this message. | Does not stop the sync and does not skip the record. Only the Cost Code (and its Cost Type) is left blank on that one time record; every other field on that record, and every other record in the run, is read and synced normally. | On the connector, review the Time Off Cost Code Mapping Override entry for that Cost Code name. Correct the target Cost Code name so it matches an existing, active Cost Code in Arcoro Time, or activate or add that Cost Code in Arcoro Time, then run the sync again. |
| Multiple active cost codes were found with Name: [Cost Code name]. No Cost Code will be assigned to the record. Correct the data in the source system and run the sync again. | Read only. Time for Payroll Configuration (Sage Intacct Companies) or Time for Sage Intacct Configuration. | Same setup as the row above, except more than one Cost Code that is currently Active in Arcoro Time shares the override's target name (ignoring upper/lower case). Inactive Cost Codes with that name are not counted toward this. | Does not stop the sync and does not skip the record. Only the Cost Code (and its Cost Type) is left blank on that one time record; every other field on that record, and every other record in the run, is read and synced normally. | In Arcoro Time, rename or deactivate the duplicate Cost Codes so only one active Cost Code carries that name, then run the sync again. Arcoro Time is the source system this message refers to; this check reads Cost Codes from Arcoro Time itself, not from Sage Intacct. |
Confirming the Error
- Open Sync History for the connector and find the run in question.
- Because these are configuration checks that run before any entity is read or written, a failed run in this family usually shows very few or zero entities with any Added, Updated, or Unchanged counts. Look at the entity that was running when the run stopped; do not expect a large Failures count spread across many records, since this family is mostly a whole-run stopper rather than a per-record problem.
- Open that entity's detail and read the message text. Match on the fixed wording of the sentence (for example "could not be matched against a Business Unit for this company"), not on the value inside the quotes, since the quoted value is specific to your data.
- If you instead have a problem while setting up or saving the connector, use Validate (or Save) on the Connector configuration screen. For Arcoro Time, this uses the same underlying check as testing the connector, so a failure here reads the same message text as a failed connector test.
- If you have a failed "Test Connector" result, that check runs the identical validation. Two of the messages in this article (Time Off Plans must have a valid mapping..., No Cost Code with name...) can only appear this way, and only when the product configuration is Time for Intacct Payroll Configuration; they will never show up in Sync History.
- Confirm which Errors, Warnings, Information, or Failures counts are non-zero on the relevant Sync History entity row, and pair that with the message text you found in the previous step before concluding which fix applies.
Resolving the Error
Pay Schedule
- In Arcoro Time, confirm the exact name of the Pay Group you intend to sync.
- On the Connector configuration, correct the Pay Schedule value to match that name exactly.
- Save the connector and confirm the connector test now succeeds, then run the sync again.
Business Unit
- In Arcoro, confirm the Business Unit you want to sync and whether it is active.
- If the Business Unit is inactive, either reactivate it in Arcoro or choose a different, active Business Unit.
- On the Connector configuration, reselect the Business Unit from the current list rather than retyping it.
- Run the sync again and confirm it proceeds past setup.
Pay Period Dates
- In the Run Sync dialog, confirm the Pay Period Start Date and Pay Period End Date you entered.
- If an End Date is present, make sure it falls on or after the Start Date.
- If no End Date is given, make sure the Start Date is at least one day before today.
- Run the sync again with corrected dates.
Employee ID Filter
- In the Run Sync dialog, confirm the Employee ID value you entered for the Time Off Balance sync.
- In Arcoro Time, confirm that an employee with that Employee ID actually exists.
- Correct the Employee ID parameter value and run the sync again.
Time off Cost Code Mapping Override (Intacct Payroll and Sage Intacct Configurations)
- On the Connector configuration, confirm the Time Off Cost Code Mapping Override has at least one Time Off Plan to Cost Code entry.
- In Arcoro Time, confirm each mapped cost code name exists exactly as entered.
- Correct or add mapping entries, then use Test Connector (or Save) again to confirm it now passes.
- These same mapping entries are also checked every time a Time Off record is actually synced, for both the Time for Payroll Configuration (Sage Intacct Companies) and Time for Sage Intacct Configuration connectors. Passing Test Connector does not guarantee this keeps passing during a sync, because Test Connector only confirms the mapped Cost Code name exists somewhere in Arcoro Time; it does not confirm the Cost Code is Active, and it does not check for more than one Active Cost Code sharing that name.
- If a sync run reports a missing or duplicate Cost Code for a Time Off record, in Arcoro Time confirm the mapped Cost Code name is Active and that no other Active Cost Code shares that exact name. Correct or deactivate duplicates as needed, then run the sync again.
Internal Settings
The following can only be done by Arcoro support, as these settings are not configurable by users.
- If the message names Arcoro Time Base URL, this is an internal application setting, not a field on the connector. In these situations, escalate to Arcoro Support.
- If the message is the Hub not enabled message, this is a company-level setting in Arcoro Hub that you cannot toggle yourself. Escalate to have Hub enabled for the company, then try to run the sync again.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- The message names Arcoro Time Base URL. This is an internal application setting that you cannot change.
- The message is the "Hub not enabled" message. Enabling Hub for a company is an internal action that you cannot change.
- You attempted a fix (Pay Schedule, Business Unit, Pay Period dates, Employee ID, cost code mapping) and confirmed in the source system, but the same message still recurs.
- The message text does not match any row in this article's table exactly.