Sage Intacct does not have a separate Contractor record type. Arcoro sends each contractor over as an Employee record with its employee type set to Contractor, along with a linked Contact record. Before any of that is sent, the write step checks the contractor's data for a few required conditions. If a condition is not met, that one contractor is left out of the sync and an error is written to the log instead. Every other contractor in the same run is unaffected.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Social Security Number is required when the Contractor is an Individual. Correct the data in the Source system and execute the Sync again. | Write (Arcoro to Sage Intacct) | The contractor's Contractor Type is set to Individual, and the Social Security Number field is blank, empty, or only whitespace. | Whole contractor record skipped for this sync run. | In Arcoro, add the contractor's Social Security Number, or correct the Contractor Type if this contractor is really a Business. |
| Employer Identification Number is required when the Contractor is a Business. Correct the data in the Source system and execute the Sync again. | Write (Arcoro to Sage Intacct) | The contractor's Contractor Type is set to Business, and the Employer Identification Number field is blank, empty, or only whitespace. | Whole contractor record skipped for this sync run. | In Arcoro, add the contractor's Employer Identification Number, or correct the Contractor Type if this contractor is really an Individual. |
| A Contractor with ContractorIdentifier "[Contractor Identifier value]" has been sent to Sage Intacct multiple times. Only the first Contractor with this value will be processed and the first contractor may differ on subsequent syncs. The duplicate record has a Source System ID of "[Arcoro record ID]". Correct the source data and run the sync again. | Write (Arcoro to Sage Intacct) | Two or more contractor records in the same sync run share the same Contractor Identifier value, compared without regard to upper or lower case. The check only looks at records processed earlier in the same run. It does not look at what already exists in Sage Intacct. | Whole contractor record skipped, for every record after the first one with that Contractor Identifier in the run. | In Arcoro, find the contractor records that share this Contractor Identifier and correct or remove the extra one so the identifier is unique. |
About the duplicate message specifically: which contractor record is treated as the first, and which one is treated as the duplicate, is not fixed. The check simply records the first Contractor Identifier it sees during that run and rejects every later match. Contractor records can be processed in a different order from one sync to the next, so the specific contractor that gets skipped as a duplicate can change between runs. That is what the message means when it says the first contractor may differ on subsequent syncs. Do not assume the record named in one run's log will be the same one named in the next run's log.
Confirming Error
- Open the sync execution reported in the Arcoro sync history.
- Find the step for the Sage Intacct connector.
- Find the Contractor entity row for that step.
- Check the Errors count for that row. All three messages in this article are logged as errors, not warnings, and they do not increase the Failures count. If Failures is non-zero, that is a different problem than the ones in this article and should not be treated as a contractor validation issue.
- Open the errors list for the Contractor entity and match on the fixed part of the sentence, ignoring the quoted values:
"Social Security Number is required when the Contractor is an Individual."
"Employer Identification Number is required when the Contractor is a Business."
"has been sent to Sage Intacct multiple times."
Resolving Error
Social Security Number Is Required When the Contractor Is an Individual
- In Arcoro, open the contractor record named in the sync history entity list.
- Confirm the Contractor Type field. If it is set to Individual and should not be, change it to Business instead.
- If the Contractor Type is correctly Individual, enter the contractor's Social Security Number.
- Re-run the sync and confirm the contractor no longer appears in the Contractor entity's errors list, and that it now shows under Added or Updated.
Employer Identification Number Is Required When the Contractor Is a Business
- In Arcoro, open the contractor record named in the sync history entity list.
- Confirm the Contractor Type field. If it is set to Business and should not be, change it to Individual instead.
- If the Contractor Type is correctly Business, enter the contractor's Employer Identification Number.
- Re-run the sync and confirm the contractor no longer appears in the Contractor entity's errors list, and that it now shows under Added or Updated.
Contractor Has Been Sent to Sage Intacct Multiple Times
- In Arcoro, search for contractor records that use the Contractor Identifier value quoted in the error message.
- Review each matching record. The Contractor Identifier is meant to be unique per contractor, so one of the matching records is either a duplicate entry or has an incorrect identifier copied from another contractor.
- Correct or remove the extra record so only one contractor uses that identifier.
- Re-run the sync. Confirm the Contractor entity's Errors count for this message has dropped, and that the corrected contractor now appears under Added or Updated instead of Errors.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- You confirm the Contractor Type, Social Security Number, or Employer Identification Number are already correct in Arcoro, and the same error still appears after a re-run.
- You cannot find more than one contractor record with the Contractor Identifier named in a duplicate error.
- The Contractor entity row shows a non-zero Failures count alongside these errors. That points to a different problem than a data validation issue.
- The log text does not match any of the three fixed sentences in this article. It is likely a different message, or a message passed through from Sage Intacct itself.