Sage Intacct allows some fields to be blank that Arcoro requires. When a Business Unit, Cost Code, Department, or Union-type record comes out of Sage Intacct without a Name or an ID, Arcoro cannot build a usable record, so it skips that single record and keeps going with the rest.

On the General Ledger side, Arcoro is sending payroll data into Sage Intacct as a journal entry. A journal entry needs an account on every line, a payroll date, and at least two line items to balance. If any one of those is missing, Arcoro will not create the journal entry in Sage Intacct at all, even if only one line item has the problem.

Error Messages

Note: The phrase "Source System" in the Account message refers to Arcoro, not Sage Intacct, because this message fires in the write direction. This is the opposite of the two read-side messages above it, where the fix is always in Sage Intacct. Always check the Direction column.

Note: "Payroll Date is Required." is a short, generic sentence. There is a separate, unused resource string with nearly identical wording ("Payroll Date is required.", lower-case "required") that has no active code path and should never be referenced in a ticket. Match on the exact casing "Payroll Date is Required." with a capital R, and confirm the record is a General Ledger sync before treating it as this message.

Record Types That Can Appear in the Two Generic Messages

Business Unit is the only record type where the message text does not use the word "Business Unit." It literally reads "Sage Intacct Location/Arcoro Entity."

Confirming the Error

1. Open the sync execution for the run in question
2. Find the step for the Sage Intacct connector in that execution.
3. For a read-side message, open the row for the entity named in the message (Business Unit, Cost Code, Department, Union, Union Local, or Union Class). For a General Ledger message, open the General Ledger entity row.
4. Check the Errors, Warnings, Information, Failures, Added, Updated, and Unchanged columns for that row. A read-side required-field message shows as an Error on that entity row, with the record still counted toward Failures rather than Added or Updated.
5. Open the errors list for that entity row and match on the fixed part of the sentence, for example "does not have a Name" or "Account is required," not on the quoted ID, Name, or Account value, since those vary per record.
6. Read the record type out of the message (the word before "with ID" or "with Name") to know which record in Sage Intacct to open next.

Resolving the Error

Name is Required (GenericNameRequiredError)

1. Read the record type and ID out of the message.
2. Use the record type table above to find which Sage Intacct record and list it points to.
3. In Sage Intacct, open that record by its ID and enter a Name.
4. Save the record in Sage Intacct.
5. Rerun the sync and confirm the entity row no longer lists that record under Errors.

ID is Required (GenericIdRequiredError)

1. Read the record type and Name out of the message.
2. Use the record type table above to find which Sage Intacct record the list points to.
3. In Sage Intacct, open that record by its Name and enter or correct its ID.
4. Save the record in Sage Intacct.
5. Rerun the sync and confirm the entity row no longer lists that record under Errors.

Account is Required (GeneralLedgerAccountNullError)

1. Confirm this is a General Ledger sync and the error is on the General Ledger entity row, not a read-side entity row.
2. In Arcoro, review the payroll run being synced and check the GL account mapping for every pay type, deduction, or other item feeding that line.
3. Fill in the missing account mapping in Arcoro.
4. Rerun the sync and confirm the General Ledger entity row shows the journal entry as Added rather than a Failure.

Payroll Date is Required (GeneralLedgerPayrollDateRequiredError)

1. Confirm this is a General Ledger sync and the error is on the General Ledger entity row.
2. In Arcoro, confirm the payroll run selected for this sync has a Payroll Date set.
3. Correct the payroll run in Arcoro if the date is missing.
4. Rerun the sync and confirm the General Ledger entity row shows the journal entry as Added rather than a Failure.

At Least Two Line Items Are Required (GeneralLedgerJournalMinimumLineItemsError)

1. Confirm this is a General Ledger sync and the error is on the General Ledger entity row.
2. In Arcoro, confirm the payroll run selected for this sync produced at least two line items that together balance as debits and credits.
3. If the payroll run should have two or more lines but does not, treat this as a data issue in the payroll run rather than a connector problem.
4. Rerun the sync and confirm the General Ledger entity row shows the journal entry as Added rather than a Failure.

When to Escalate

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

• The record in Sage Intacct already has a Name or ID filled in, matches the record type table above, and the same error still appears after a rerun.
• The General Ledger account mapping in Arcoro looks complete for every line item on the payroll run, but Account is required still fires.
• The payroll run in Arcoro clearly has a Payroll Date and two or more line items, but the General Ledger message still fires.
• You cannot tell from the record type table above which Sage Intacct record the message refers to.