Arcoro builds a payroll journal entry for Sage Intacct out of one or more line items. Each line item needs a general ledger account, and most lines also carry an employee. Before Arcoro sends the entry, it checks every line's account number and employee ID against the accounts and employees Arcoro has already loaded from Sage Intacct. If even one line references an account number or employee ID that does not match, Arcoro does not send the entry at all.

One bad line is enough to lose the whole entry. Arcoro checks every line item in the journal entry, but it only keeps a single pass-or-fail flag for the entire entry. If any one line fails either of the checks below, the entire journal entry, including every other line item that was otherwise fine, is skipped for that run.

Error Messages

Confirming the Error

1. Open the sync execution that covers the payroll run in question.
2. Find the step that writes to the Sage Intacct connector.
3. Find the General Ledger entity row for that step.
4. Check the Errors and Failures columns for that row. Both above zero is a strong signal that at least one journal entry was lost because of a single bad line reference.
5. Open the errors list for the General Ledger row. For the account message, match on the fixed wording "was not found in Sage Intacct. The Journal entry will not be processed." For the employee message, match on "No employee with ID" together with "was found in Sage Intacct." Do not match on the quoted value, since it changes per record.
6. Note the account number or employee ID quoted in the matched message. That is the value to look up in Sage Intacct.

Resolving the Error

The Account With Number “[The Account Number]” Was Not Found in Sage Intacct

1. In Sage Intacct, check the chart of accounts under the entity configured on this connector for an account with that exact number. This lookup only sees accounts under that one configured entity, even if Sage Intacct has more than one entity set up.
2. If the account exists but under a different entity, either set it up under the configured entity as well, or confirm whether the connector should be pointed at that other entity instead.
3. If the account does not exist anywhere in Sage Intacct, add it under the configured entity.
4. If the account number was entered incorrectly on the Arcoro side, correct it there instead.
5. Run the sync again and confirm the payroll journal entry is now created in Sage Intacct.

No Employee With ID “[The Employee ID]” Was Found in Sage Intacct

1. In Sage Intacct, look for an employee record using that exact ID. This lookup is not limited to a single entity, so it will find the employee anywhere in the company if the employee already exists.
2. If the employee has not been created in Sage Intacct yet, make sure the Employees entity has been synced for this connector. It is not established whether an employee created earlier in the very same sync execution is visible to this lookup within that same run, so re-run the General Ledger sync as its own step after the Employees sync has finished, rather than assuming the same run will pick it up.
3. If the employee already exists under a different ID, correct whichever side has the mismatched ID so both match exactly.
4. Run the sync again and confirm the payroll journal entry is now created in Sage Intacct.

When to Escalate

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

• The message keeps appearing after you have confirmed a matching account or employee exists in Sage Intacct with the exact number or ID quoted in the message.
• The Failures count for the General Ledger row does not drop even after every account and employee error listed for that run has been corrected.
• The log text does not match either message in this article exactly. It may be a different Sage Intacct rejection rather than one of these two Arcoro checks.
• The same message is appearing for many different accounts and employees at once, which points toward the account or employee list failing to load rather than one bad reference on one record.