Payroll checked the mailing address on this record and rejected it. This is not an Arcoro validation rule. Arcoro sent the record to Payroll, and Payroll's own address check turned it down. Arcoro only rewrites Payroll's rejection into friendlier wording for this one specific case; every other rejection you see in the sync log for this record is Payroll's own wording, passed through unchanged. Because the write failed, the record itself was not created or updated in Payroll for this run.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| The Address is not valid. | Write (Arcoro to Payroll) | Payroll rejects a create or update of an employee's home address, a contractor's address, or a work location's address, and returns exactly the rejection text "Invalid Address" with no per-field detail and no suggested alternative address. | The employee, contractor, or location record is not created or updated for this run. For an employee, any data that is only written after the employee record succeeds (taxes, direct deposit, compensation, benefits) is skipped too. | Correct the street address, city, state, or postal code on the record in the source system, then re-run the sync. |
How to Recognize a Passthrough Error
This family covers every way Payroll can reject a write. Only the one message above is Arcoro's own wording. Everything else in this family is Payroll's rejection text, copied into the sync log exactly as Payroll sent it. Use this table to tell the two apart.
| What the log shows | Where it came from | What to do |
|---|---|---|
| One or more lines reading "Invalid [field name]. [detail]", one line per field, or a line with no field prefix at all. | Payroll's own field-by-field validation. Passed through by Arcoro without alteration. | Read the field name and detail exactly as shown. That is the specific field to correct in the source system. |
| A line ending in "- Suggested Alternative: [street], [city] [state] [postal code]". | Payroll rejected the address but proposed a corrected version. Arcoro appends Payroll's suggestion to Payroll's own message; Arcoro does not generate the suggestion itself. | Use the suggested address exactly as shown to correct the record in the source system, then re-run the sync. |
| A plain line of text that is not "The Address is not valid." and does not match either shape above. | Payroll's own bare rejection message, repeated by Arcoro with no rewriting at all. | Read it exactly as Payroll wrote it. There is no separate Arcoro article for this text. Escalate if it names something you edit from your side. |
| A generic message about a failure to connect or sync due to bad data, with no specific field or address named. | This one is not from Payroll at all. It is Arcoro's own engine fallback, logged only when Payroll's rejection carried no field list, no suggested address, and no message text for Arcoro to pass through or rewrite. | Escalate. There is no specific field named, so there is nothing for you to correct from the message alone. |
Confirming the Error
- Open the sync execution for your Payroll connector in Sync History.
- Open the step for this connector and find the row for the entity in question: Employee, Contractor, or Location.
- Check the Errors column for that entity row. This message and every passthrough variant in this article are logged as errors, not failures. A non-zero Failures count for this row points to a different problem and is not caused by this family.
- Open the entity row's error list and find the entry for the affected record.
- Match on the fixed part of the sentence, "The Address is not valid.", rather than any values that vary by record.
Resolving the Error
Employee
- In the source system feeding this Payroll connector, open the employee record and go to the home address on file.
- Correct the address line, city, state, or postal code. There is no separate scope switch for address; it is part of every employee create and update, so a bad address blocks the whole employee record regardless of which other scopes are enabled.
- Re-run the sync and confirm the employee record now appears under Added or Updated instead of Errors for that execution.
Contractor
- In the source system, open the contractor's 1099 record and go to the mailing address.
- Correct the address line, city, state, or postal code.
- Re-run the sync and confirm the contractor record no longer appears in the Errors list.
Location
- In the source system, open the work location's physical address.
- Correct the address line, city, state, or postal code, then re-run the sync.
- If the location already exists in Payroll, be aware that Arcoro treats its address as fixed once set: changing the address on an existing location triggers a different, earlier Arcoro message instead of reaching Payroll's own address check. This specific rejection is most likely on a brand-new location, not on an address edit to one that already synced successfully.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- The address is corrected and re-synced, and the same rejection still appears.
- The log text does not match "The Address is not valid." and does not match any of the passthrough shapes described above.
- The log shows the generic bad-data-or-connection wording described above rather than a specific address problem.
- The entity row shows a non-zero Failures count instead of Errors for this record.
- A suggested alternative address is provided but still fails when entered, or the rejection names something you have no access to change.