Arcoro Payroll stores each contractor (1099) record with a set of internal tracking fields called metadata, including a ContractorIdentifier that Arcoro stamps on the record the first time it is synced in. When a contractor is read out of Arcoro Payroll, the platform expects that metadata to be present so it can match the record correctly. When a contractor is written into Arcoro Payroll from a connected system, the platform checks that the required fields are present, are not too long, and that the contractor's identifier does not collide with an existing employee or another contractor already sent in the same run. Any failure of these checks removes the contractor from that sync run rather than sending partial or incorrect data.
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. | Read (Arcoro Payroll is the source) | The contractor record in Arcoro Payroll has no metadata at all: the metadata collection is empty or not present on the record. | Whole record skipped | Confirm the contractor was created or last updated through a sync rather than entered directly in Arcoro Payroll, then re-run the sync. |
| 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. | Read (Arcoro Payroll is the source) | The contractor record has metadata present, but no ContractorIdentifier entry in it, or that entry is blank. | Whole record skipped | Confirm the contractor was created or last updated through a sync rather than entered directly in Arcoro Payroll, then re-run the sync. |
| 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. | Write (Arcoro Payroll is the destination) | The incoming contractor record has no value in Last Name. | Whole record skipped | Populate Last Name for this contractor in the source system. |
| Last name exceeds the maximum length of 255 characters supported by the provider and will not be synced. | Write (Arcoro Payroll is the destination) | The incoming contractor record has a Last Name longer than 255 characters. This check only runs when Last Name has a value, so it is separate from the required-field check above. | Whole record skipped | Shorten Last Name to 255 characters or fewer in the source system. |
| 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. | Write (Arcoro Payroll is the destination) | An employee record already in Arcoro Payroll has the same identifier as this contractor's identifier. Every employee already in Arcoro Payroll is checked, including terminated and inactive employees, not only active ones. | Whole record skipped | Correct the identifier collision in the source system: the same identifier cannot belong to both an employee and a contractor in Arcoro Payroll. |
| 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. | Write (Arcoro Payroll is the destination) | Two or more contractor records in this sync run share the same Source System Id. Records are processed in parallel, so which one is treated as the first is not predictable run to run; exactly one of the matching records is kept and every other one with that same Id is skipped. | Whole record skipped | Find and correct the duplicate Source System Id in the source system so each contractor has a unique Id. |
The Last Name messages carry no contractor name or identifier in the message text itself. To identify which contractor is affected, use the label on the sync log row for that record rather than the message text; the row label is set when the record was read from the source system and is shown next to the message in the entity's error list.
Confirming the Error
- Open the sync execution in Sync History for the run in question.
- Find the step for the Arcoro Payroll connector.
- Find the Contractor entity row in that step.
- Check the Errors column for that row. Any of the six messages above will appear there, not under Warnings or Information.
- Open the errors list for the Contractor entity row and match on the fixed part of the sentence, ignoring the values inside quotes, since those vary by contractor and identifier.
A non-zero Failures count on the Contractor row is not caused by any of these six messages. Failures reflects an unhandled exception in the sync engine itself, separate from these validation errors. If Failures is non-zero, escalate instead of matching it to this article.
Resolving the Error
Contractor could not be read from Arcoro Payroll
- Check the sync log row label for the affected contractor. If it shows "ContractorIdentifier: [Missing]", the record in Arcoro Payroll is missing its tracking metadata or its ContractorIdentifier value.
- In Arcoro Payroll, confirm this contractor was created or most recently updated by a sync from a connected system. A contractor entered directly in Arcoro Payroll, or created before this sync was set up, will not have the expected metadata.
- If the contractor should be synced, have it created or refreshed through the connected source system so Arcoro Payroll receives the expected metadata, then re-run the sync.
- Confirm the fix by re-running the sync and checking that the contractor no longer appears in the Contractor entity's errors list.
Last Name is required or too long
- In the source system, open the contractor record identified by the sync log row label.
- Enter a Last Name if it is blank, or shorten it to 255 characters or fewer if it is too long.
- Re-run the sync and confirm the contractor no longer appears in the Contractor entity's errors list.
Identifier collides with an employee or another contractor
- For the employee collision message, in the source system or in Arcoro Payroll, confirm whether the same person or code is set up as both an employee and a contractor. Correct the identifier so each person has one identifier and one role.
- For the duplicate Source System Id message, in the source system, search for other contractor records sharing the same Source System Id and correct the duplicate so each contractor has a unique Id.
- Re-run the sync and confirm all of the affected contractors now appear as Added, Updated, or Unchanged rather than in the errors list.
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 identified field or identifier has been corrected and the sync has been re-run.
- The message text in the log does not match the fixed part of any sentence in the table above.
- The Failures count for the Contractor entity is non-zero.
- The contractor was created through the normal sync process but still gets a metadata or identifier read error, since that points to a platform issue rather than a data entry issue.