Direct deposit records are written into Core HR from whichever source system feeds this connector, for example CMiC, Sage 300 CRE, Sage 100, Acumatica, Viewpoint Spectrum, or Viewpoint Vista. Each direct deposit record for an employee is checked on its own before it is written. If a record is missing a required value, such as an amount, an account type, or an effective date, that one record is left out of the sync while the rest of the employee's data, including other direct deposit records, still goes through. If an employee has more than one active direct deposit record with the same account number, routing number, and account type, Core HR treats that as a duplicate and will not process those records until the duplicate is removed in the source system. None of these checks stop the sync or skip the whole employee.

Error Messages

Confirming the Error

1. Open the sync execution for your Core HR connector in Sync History.
2. Find the step for this connector, then look at the Employees entity row underneath it. All nine messages in this article are logged against the Employees entity.
3. Check the Errors, Warnings, Information, Failures, Added, Updated, and Unchanged columns for that entity row. All nine messages in this article are logged as Errors.
4. Remember that an employee can appear under Updated and still have one of these errors. The employee record itself still syncs; only the affected direct deposit record is left behind.
5. Open the errors list for the Employees entity row and match on the fixed wording of the sentence, not on the account number, routing number, or other values shown in the message.
6. The account number shown in the Multiple Active Direct Deposit records message is masked to the last four digits. Use those digits together with the employee's name to identify the exact record in the source system; do not expect the full account number to appear anywhere in the sync log.
7. If there is a direct deposit record missing from Core HR after a sync, but no error, warning, or information message appears for that employee, check the source record for a blank Account Number or Routing Number before escalating. See the two rows above marked as not currently reachable in code.

Resolving the Error

Missing Amount

1. In the source system, open the affected employee's direct deposit record named in the sync log.
2. Enter a flat Amount or a Percentage on the record. Do not leave both fields empty.
3. Rerun the sync and confirm the Employees entity row no longer shows this error for that employee.

Missing Bank Account Number or Missing Routing Number

These two specific messages will not currently appear in the sync log, even when the underlying problem exists, because of a gap in the code covered under When to escalate. Use this as your working fix regardless of whether the message is present.

1. In the source system, open the affected employee's direct deposit record.
2. Enter a value for the Bank Account Number and the Routing Number if either is blank.
3. Rerun the sync and confirm the direct deposit record now appears as Added or Updated for that employee.

Missing Override Pre-Note

1. In the source system, open the affected employee's direct deposit record named in the sync log.
2. Set a value for the Override Pre-Note field.
3. Rerun the sync and confirm the Employees entity row no longer shows this error for that employee.

Missing Earning Code (Sage 300 CRE only)

1. In Sage 300 CRE, open the affected employee's direct deposit record.
2. Enter a value for Earning Code.
3. Rerun the sync and confirm the Employees entity row no longer shows this error for that employee.

Missing Priority (CMiC only)

1. In CMiC, open the affected employee's direct deposit record.
2. Enter a value for Priority.
3. Rerun the sync and confirm the Employees entity row no longer shows this error for that employee.

Null Account Type

1. In the source system, open the affected employee's direct deposit record named in the sync log.
2. Set the Account Type field to a valid value, such as Checking or Savings.
3. Rerun the sync and confirm the Employees entity row no longer shows this error for that employee.

Missing Effective Date

1. In the source system, check the affected employee's Hire Date. If it is blank, enter it.
2. If the employee's Hire Date is already correct, check the existing direct deposit record in Core HR for an Effective Date and set one directly if it is missing.
3. Rerun the sync and confirm the Employees entity row no longer shows this error for that employee.

Multiple Active Direct Deposit records

1. In the source system, open the affected employee's direct deposit records using the last four digits shown in the message and the employee's name.
2. Find the two or more active records that share the same Account Number, Routing Number, and Account Type.
3. Deactivate or remove the extra record so only one active record remains for that combination.
4. Rerun the sync and confirm the Employees entity row no longer shows this error for that employee. If the employee has more than one duplicated account, check again after the first fix; see When to escalate.

When to Escalate

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

• The source data has been corrected, the sync has been rerun, and the same error still appears for the same employee and the same direct deposit record.
• An employee's direct deposit record is missing from Core HR after a sync, and no error, warning, or information message appears for that employee at all. This matches the current code gap for a blank Account Number or Routing Number; escalate to engineering with the employee identifier and a note that the source record has a blank account or routing number.
• An employee still shows the Multiple Active Direct Deposit records error after you have removed one duplicate. The check reports only one duplicated account per sync attempt, so a second duplicate group on the same employee will not be flagged until the first is cleared. Confirm whether more than one account is duplicated before escalating.
• The Missing Effective Date error appears for an employee who clearly has a hire date on file. This can point to a data problem on the employee record in Core HR itself rather than the source system.
• An entity row shows Failures instead of Errors for one of these messages, which points to a problem beyond bad source data.