Neither message describes a problem with one specific field. UnprocessableEntityError means Sage Intacct answered a request with HTTP 422; despite the wording, the code path that produces this exact sentence is the connection layer Arcoro also uses for ordinary reads, so it is not limited to the moment a record is actually submitted for saving. GetMatchError is more specific: during setup Arcoro matched a Location to an existing Sage Intacct record by name, but when it went back to fetch that exact record by its key a moment later, Sage Intacct did not return it.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| The request was rejected by Sage Intacct. This typically indicates a Business Validation error with the data. | Shared connection layer. Fires on a read of any entity from Sage Intacct, and on the lookup Arcoro runs partway through a Location update write. | Sage Intacct responds to a query or a by-key lookup with HTTP 422. This status is not on Arcoro's automatic retry list for Sage Intacct, so it is logged on the first attempt, with no retry delay beforehand. | Varies. If it happens while Arcoro is reading an entity's records from Sage Intacct, that entity's read stops for the rest of this run and is logged as a Failure; other entities in the same sync keep going. If it happens during the Location-update lookup, only that one Location is skipped and logged as an Error; other Location records continue. | In Sage Intacct, check for a recent change affecting the entity or Location named in the log: a removed custom field, a dimension change, or a permission change on the integration user. |
| The Provider could not match the record to the expected Sage intacct Item. The record will not be Synced. | Write to Sage Intacct. Location only. | The Location was matched to an existing Sage Intacct record by name during setup, but a direct lookup of that record by its key returned nothing when the update was attempted. | Whole record skipped, logged as an Error. Other Location records in the same run continue. | In Sage Intacct, confirm the Location named in the log still exists under the same name and key. If it was renamed or deleted, restore it, or let the next sync add it again as a new Location. |
Confirming the Error
- Open the sync run in Sync History and find the entity row: Company/Locations for GetMatchError, or whichever entity was being read from Sage Intacct when UnprocessableEntityError appeared.
- Check whether the count landed under Errors or Failures. Errors means one record was skipped while the rest of that entity's records were still processed; check that Added, Updated, and Unchanged on the same row look otherwise normal. Failures means Arcoro stopped partway through reading that entity for this run; other entities in the same sync are unaffected.
- Open the message detail and match the fixed sentence exactly. For GetMatchError, the lowercase "intacct" in "Sage intacct Item" is expected product wording, not a typo to chase.
- For GetMatchError, note the Location name shown with the message; that identifies the exact record affected.
Resolving the Error
- Start by gathering information rather than changing a field. Capture the exact message text, the entity or record name from the log, and whether it landed under Errors or Failures.
- For GetMatchError, search Sage Intacct for the Location by the name shown in the log. A rename or deletion between setup and the write is the most common reason the key lookup came back empty.
- For UnprocessableEntityError, this message carries no field-level detail on its own. Re-run the sync. If it fails again on the same entity or record, do not guess further; move to escalation.
- Confirm the fix by re-running the sync and checking that the previously affected entity or Location now shows under Added, Updated, or Unchanged instead of Errors or Failures.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- Escalate any UnprocessableEntityError that repeats on the same entity or record across sync runs. Capture the entity name (if it showed as a Failure) or the record name (if it showed as an Error), the exact message text, and which column it appeared under.
- Escalate if the same sync run also shows a line starting with "Sage Intacct error:" and including "SupportId:", or a line reading "Intacct error <id> - ..." near a Location save. That text is Sage Intacct's own error, passed through by Arcoro, and is not one of the two messages in this article. Capture the error code, message, and support ID if one is present; Sage Intacct support can look that ID up directly. Note that the write-side passthrough ("Intacct error...") does not always include a support ID, only the read-side passthrough consistently does.
- Escalate GetMatchError if the Location clearly still exists in Sage Intacct under the same name and the failure keeps happening.