When Arcoro sends an employee, contractor, or location record to Arcoro Payroll, the payroll platform runs its own validation before it will accept the write. When it turns the record down, Arcoro copies that rejection text into the sync log as it received it, rather than rewriting it in Arcoro's own words.
There is exactly one exception: when the payroll platform's entire answer is the two words "Invalid Address," Arcoro swaps in a plain Arcoro sentence instead. Every other sentence you will see logged for this family is the payroll platform's own text, not something Arcoro wrote, so do not expect it to match any other Arcoro support article.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| The Address is not valid. | Write (Arcoro to Arcoro Payroll) | Arcoro Payroll's create or update call for an Employee, Contractor, or Location record returns a rejection whose entire message is exactly "Invalid Address," with no per-field errors and no suggested alternative address attached to the same response. | Whole record skipped. Nothing else tied to that record (taxes, direct deposits, compensations, benefits, or a location's linked Hub record) is written for this run. | Correct the address in the source system so it is a complete, real, deliverable address (line 1, city, state, and postal code), then run the sync again. |
Recognizing a Passthrough Rejection
This is the point of this article. Most log entries in this family are not Arcoro validation messages at all, they are Arcoro Payroll's own rejection text, sometimes with a small amount of Arcoro framing added around it. The table below lists every shape this text can take.
| Shape of the log text | What it means | What to do |
|---|---|---|
| A single line reading exactly "The Address is not valid." | This is the one Arcoro-authored sentence in this family. Arcoro Payroll's own response was the bare phrase "Invalid Address" with nothing else attached, and Arcoro replaced it with this sentence. | Treat it as an address rejection. Skip straight to How to resolve below. |
| A line that begins with a field name, followed by a sentence (for example, a line that starts by naming the rejected field before the rest of the sentence). | Arcoro Payroll rejected one specific field on the record. The field name comes from Arcoro Payroll's own schema. The sentence after it is Arcoro Payroll's own wording, copied through unchanged; Arcoro only adds the field-name prefix. | Do not search for this exact sentence in another Arcoro article, it will not be found. Use the field name to identify what data was rejected, then follow the general passthrough steps below. |
| A single line with no field-name prefix and no other structure. | Arcoro Payroll's own rejection message, passed through with no Arcoro wrapping at all. | Same as above. Not matching any known Arcoro article is expected here and is not a sign something is missing. |
| A line that contains a suggested alternative address appended after Arcoro Payroll's own message (a corrected line 1, city, state, and postal code offered by the platform). | Arcoro Payroll rejected the address but is also offering a corrected version it considers valid. This line can appear together with a field-name-prefixed line above it, on separate lines within the same log entry. | Read the suggested alternative address and consider whether it should be used to correct the record in the source system. |
Confirming the Error
- Open the sync execution for the run in question.
- Find the step for this connector that matches the affected entity: People/Employees, People/Contractors, or Company/Locations.
- Open that step's detail and locate the affected record's row by its identifier.
- Open the errors list for that row and read the exact text logged, line by line.
- The Sync History screen shows per-entity counts in columns labelled Errors, Warnings, Information, Failures, Added, Updated, and Unchanged. For this family, expect the record to be missing from Added or Updated and reflected only in Errors instead.
- For this family, the logged text will often not match any Arcoro support article. That is itself the diagnostic signal that you are looking at passthrough text from the payroll platform, not a missing article.
Resolving the Error
- For the address message specifically: open the record in the source system and confirm address line 1, city, state, and postal code are all filled in and describe a real, deliverable address, not a placeholder.
- Make any correction in the source system, the system that feeds Arcoro, not in Arcoro Payroll itself.
- Run the sync again.
- For any other passthrough text in this family: identify what the message is naming (a field, a code, a setting). If it names something also present in the source system, correct it there. If it names something that exists only inside Arcoro Payroll and is not fed from the source system, the correction has to happen inside Arcoro Payroll itself, and tier 1 does not have access to make that change.
- To confirm the fix worked, run the sync again and check that the same record identifier now appears in Added or Updated for that step, with no error logged against it.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- The logged text is not the exact sentence "The Address is not valid." and does not obviously map to a field you can correct yourself.
- The address fields already look complete and correctly formatted in the source system, and the record still fails after a resync.
- The rejection is on a Contractor or Location record and you cannot confirm from their own view whether a corrected address will be accepted.
- Before escalating, capture the exact logged text, verbatim, do not paraphrase it. Also capture the entity type and record identifier, whether this was a create or an update, and whether the same record fails again on a second sync attempt. The raw platform text is often the only clue whoever picks up the escalation will have to identify the actual rule Arcoro Payroll is enforcing.