Module Navigation

Sage Intacct Troubleshooting: Field Length or Format Invalid

Before Arcoro sends an employee or contractor record to Sage Intacct, it checks the identifier value against Sage Intacct's rules for a valid record key. This check happens inside Arcoro itself, before any call reaches Sage Intacct, so it is not a rejection coming back from Sage Intacct's own API. If the identifier fails the check, Arcoro does not send that record at all. Nothing about that employee or contractor changes in Sage Intacct until the identifier is corrected and the sync runs again.

Error Messages

Message textDirectionOccurs whenOutcomeFix
The ID "[the employee or contractor identifier]" is not valid. Sage Intacct IDs can not contain the following characters: _. It may not contain spaces or consecutive -s. This record will not be processed. Correct the ID in the source system and run the sync again.Write: Arcoro to Sage IntacctThe employee or contractor identifier contains an apostrophe, an underscore, or a space, or contains two or more hyphens in a row.Whole record skipped for that run.In the source system, remove the apostrophe, underscore, space, or consecutive hyphens from the identifier, then run the sync again.

The Complete Identifier Rule, as Enforced by the Connector

  • The identifier may not contain an apostrophe.
  • The identifier may not contain an underscore.
  • The identifier may not contain a space.
  • The identifier may not contain two or more hyphens in a row.

The message text understates this rule. It names the underscore by character, then separately calls out spaces and consecutive hyphens, but it never mentions that an apostrophe is also forbidden. The underscore named in the message is a literal forbidden character, confirmed from the connector's own list of disallowed characters. It is not a typo or a formatting artifact of the sentence. Review the identifier and check that it has no underscore, no space, and no repeated hyphen; specifically, whether it contains an apostrophe before ruling out this cause.

A blank identifier does not produce this message. An identifier that is null or a completely empty string is caught by a separate, earlier check and produces a different message about a missing identifier. An identifier made up only of spaces is not caught by that earlier check because it is not technically empty, so it falls through to this check instead and produces this same format message, since a space is one of the forbidden characters.

Confirming the Error

  1. Open the sync execution for the run in question.
  2. Find the step for the Sage Intacct connector.
  3. Find the Employees or Contractors entity row for that step.
  4. Check the Errors column for that row. A count above zero means at least one record was skipped.
  5. Open the errors list for that entity row and match on the fixed wording "is not valid. Sage Intacct IDs can not contain the following characters", not on the quoted identifier, since the identifier changes per record.
  6. Note the identifier value quoted in the message. That is the value to correct.

Resolving the Error

  1. In the source system feeding Sage Intacct, find the employee or contractor record using the identifier quoted in the message.
  2. Check that identifier field for an apostrophe, an underscore, a space, or two or more hyphens in a row.
  3. Correct the identifier in the source system so it contains none of those.
  4. Run the sync again and confirm the Errors count for that entity has dropped and the record now appears under Added or Updated.

When to Escalate

If any of the following occur, you may need to reach out to Arcoro support for additional assistance.

  • Review the identifier and confirm it contains none of the four items listed above: no apostrophe, no underscore, no space, no repeated hyphen. The connector's forbidden-character list may be different from what is documented here, so this needs engineering to confirm.
  • The identifier still fails with this same message after it has been corrected in the source system and the sync re-run.
  • The message text shown in the sync log does not match the fixed wording in this article.
  • The message appears for an entity other than Employees or Contractors.
Was this article helpful?
0 out of 0 found this helpful