Contractors are 1099 workers and are kept as a separate record type from employees in Payroll. Some of these messages fire while Arcoro is reading a contractor record out of Payroll, because the record is missing information Arcoro needs to identify it. The rest fire while Arcoro is writing a contractor record into Payroll, because the incoming data fails a check before Payroll will accept it, such as a missing last name or a value that was already sent once this sync.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| The contractor has no metadata to read, this way it will not be processed. Correct data and run the sync again. | Payroll to Arcoro (read) | The contractor record in Payroll has no internal identifying data attached to it at all. This is internal data that Arcoro itself stamps onto a contractor record the first time it writes that contractor into Payroll; it is not a field you fill in. This only appears when the connector is not restricted to a specific list of contractor IDs. If the connector is restricted to specific contractor IDs, a contractor missing this data is left out of the sync silently instead of producing this message. | Record skipped. The contractor is not read into Arcoro at all. | Confirm the contractor was created by a Payroll sync and not added directly inside Payroll. |
| The contractor has no ContractorIdentifier available to be read on metadata, this way it will not be processed.Correct data and run the sync again. | Payroll to Arcoro (read) | The contractor record in Payroll has internal identifying data attached, but the specific value Arcoro uses to identify the contractor is blank inside it. Same restriction as above: this only appears when the connector is not restricted to a specific list of contractor IDs. | Record skipped. The contractor is not read into Arcoro at all. | Confirm the contractor was created by a Payroll sync and not added or edited directly inside Payroll in a way that cleared this value. |
| Contractor Last Name 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 contractor record being written has no value in Last Name. | Record skipped. The contractor is not written to Payroll at all. | Add a last name to the contractor in the source system feeding this sync (for example Core HR or Arcoro Time). |
| A Contractor with Source System Id '[source system ID]' has been sent to Payroll multiple times. Only the first Contractor received will be processed and saved. Correct the source data and run the sync again. | Arcoro to Payroll (write) | More than one contractor record in the same sync run has the same Source System Id. This is not a check against contractors already saved in Payroll from earlier syncs, only against other contractors seen so far in this run. The comparison ignores upper and lower case. Only the first one with that ID is kept; every later one with the same ID gets this message. | Record skipped. Every duplicate after the first is not written to Payroll. | Find and correct the duplicate record in the source system so the ID only appears once. |
| An Employee already exists in Payroll with the same Identifier '[contractor identifier]'. This record will not be synced. Correct the data in the source system and execute the sync again. | Arcoro to Payroll (write) | An employee record that already exists in Payroll, from any prior sync, has the same identifier as this contractor. This is a check against records already saved in Payroll, not against other records in the current run. The comparison ignores upper and lower case. | Record skipped. The contractor is not written to Payroll at all. | Decide in the source system whether this person should be an employee or a contractor, and correct the identifier so it is not shared between an employee and a contractor. |
| Last name exceeds the maximum length of 255 characters supported by the provider and will not be synced. | Arcoro to Payroll (write) | Last Name is longer than 255 characters. This message is generated the same way as the other write-side errors in this table even though its internal name suggests otherwise; it is a full error, not a warning, and it blocks the record the same way Last Name being required does. | Record skipped. The contractor is not written to Payroll at all. | Shorten the last name in the source system to 255 characters or fewer. |
Confirming the Error
- Open the sync execution for your Payroll connector in Sync History.
- Open the step for the Contractor entity.
- Check the Errors column for the entity. A non-zero count here means one or more of the messages above (or another Contractor error not in this article) fired.
- Open the entity row to see the list of individual errors.
- Match on the fixed wording of the sentence, not on the value inside the quotes, since that value changes per record.
- The two read-side messages in this article do not name the contractor in the message text itself. Use the entity row's own identifying label, which shows the contractor's identifier if one was found, or marks it missing, along with the first and last name Payroll returned.
- A non-zero Failures count on this entity is not explained by any message in this article. Treat it as a separate problem and escalate.
Resolving the Error
The Contractor Has No Metadata to Read/Has No ContractorIdentifier
- Ask whether this contractor was created directly inside Payroll rather than through a sync from Core HR, Arcoro Time, or another source.
- If it was created directly inside Payroll, it will not carry the identifying data Arcoro needs to read it back. See Open questions for how this case is typically resolved.
- If the connector is scoped to a specific list of contractor IDs, confirm this contractor is meant to be included in that list before assuming it is missing data.
- Re-run the sync and confirm the contractor no longer appears in the entity's error list.
Contractor Last Name Is Required/Exceeds 255 Characters
- In the source system feeding this sync, open the contractor's (or the corresponding person's) record.
- Enter a last name, or shorten the existing last name to 255 characters or fewer.
- Re-run the sync and confirm the contractor moves out of the Errors list for the Contractor entity.
A Contractor with Source System Id has been sent to Payroll multiple times
- In the source system, look for more than one record that would produce the same Source System Id for this contractor.
- Correct or remove the duplicate so only one record with that ID remains.
- Re-run the sync and confirm only one contractor with that ID appears, with no duplicate error.
An Employee Already Exists in Payroll With the Same Identifier
- In Payroll, confirm whether an employee record already exists with the identifier named in the message.
- In the source system, decide whether this person should be synced as an employee or as a contractor, since Payroll will not accept the same identifier as both.
- Correct the identifier or the record type in the source system so the conflict is resolved.
- Re-run the sync and confirm the contractor moves out of the Errors list for the Contractor entity.
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 has been corrected and the sync has been re-run.
- The log text does not match the fixed wording of any message in the table above.
- The entity row shows a non-zero Failures count, since none of the messages in this article are tied to that outcome.
- The log text is clearly passthrough from Payroll rather than one of the messages listed here.
- A contractor with no metadata or no ContractorIdentifier was confirmed to have come from a normal sync rather than being created directly inside Payroll, since that points to an unexpected data loss rather than a data entry problem.