These four messages all come from the step that writes an employee's direct deposit records out to Sage 100. They fire only for employees whose sync includes the Direct Deposits scope, and only for employees who are not terminated. Each message points to a problem with one specific direct deposit record: a missing bank account number, a direct deposit code that Sage 100 does not recognize as a direct deposit type deduction, two updates landing on the same Sage 100 record, or a Sage 100 deduction that has been archived. In every case except the archived-record case, the fix is a change to the source direct deposit data, not to Sage 100 itself.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Bank Account Number is required to create direct deposit (deduction). The record will not be processed. | Arcoro to Sage 100 (write) | The direct deposit record has no value in the Bank Account Number field, and this is the first time this direct deposit record is being sent (no matching deduction exists yet in Sage 100). Once the record exists in Sage 100, a later sync with a still-missing account number will not raise this message again. | The direct deposit is still created in Sage 100 with its deduction type, calculation method, and amount. Only the bank account number and account type are left off, despite the wording of the message. Field skipped, not the whole record. | Add the bank account number to the direct deposit record in the source system and rerun the sync. |
| [direct deposit code] - no matching Pay Deduction in HH2 found with Type NetDirectDeposit or DirectDeposit. | Arcoro to Sage 100 (write) | The direct deposit's code does not match any pay deduction configured in Sage 100 with a type of Direct Deposit or Net Direct Deposit. | Collection item skipped. This one direct deposit record is left out. The employee and every other direct deposit record still sync. | Create or correct a pay deduction in Sage 100 with a matching code and a type of Direct Deposit or Net Direct Deposit. |
| Multiple Direct Deposit updates were sent for the same record, only the first record will be processed. | Arcoro to Sage 100 (write) | Two direct deposit records in the same sync batch resolve to the same existing deduction record in Sage 100. The second one to be processed hits a record that an earlier direct deposit in the same sync already claimed. | Collection item skipped. The first-processed direct deposit record is written. The conflicting one is left out. Other direct deposit records are unaffected. | Review the employee's direct deposit records in the source system and remove or correct the duplicate so each direct deposit code maps to a distinct Sage 100 deduction. |
| DirectDeposit Code [direct deposit code] has IsArchived = true and cannot be updated by the Sync. To Sync this data contact support to set IsArchived = false and rerun the Sync. | Arcoro to Sage 100 (write) | The direct deposit's code matches an existing deduction record in Sage 100, and that existing record is flagged IsArchived = true. | Collection item skipped. This direct deposit record is left out. Other direct deposit records for the employee still sync. | Contact support to have the archived flag cleared, then rerun the sync. |
Confirming the Error
- Open the sync execution for your Sage 100 connector in Sync History.
- Find the step for the Sage 100 connector and open the row for the Employees entity.
- Check the Errors, Warnings, Information, Failures, Added, Updated, and Unchanged columns for that row. A non-zero Errors count means at least one of the messages in this article, or another employee-level error, is present.
- Open the errors list for the Employees entity row and match on the fixed part of each sentence, ignoring the bracketed values (direct deposit code) that vary per record.
- A non-zero Failures count on this row is not caused by any of the four messages in this article. None of them stop the sync or fail the employee record, so a Failures count pointing at direct deposit needs separate investigation.
- Also open the Warnings list for the same entity row. Most Sage 100 direct deposit problems log as warnings, not errors, and will not appear in the errors list at all. Look for: "Bank Routing Number is required to create direct deposit (deduction)"; "More than one active direct deposit code detected"; "doesn't have a deposit amount or percent"; "does not have a Code"; and "direct deposit records that have expired, but the record remains active in Sage 100 due to the Pre-Note status". Any of these means you have a direct deposit problem that this article does not cover.
Resolving the Error
Bank Account Number Is Required to Create Direct Deposit (Deduction)
- In the source system, open the employee's direct deposit record and confirm the Bank Account Number field is populated.
- Save the change in the source system.
- Rerun the sync and confirm the direct deposit no longer appears in the Employees entity's errors list.
No Matching Pay Deduction in HH2 Found with Type NetDirectDeposit or DirectDeposit
- In Sage 100, confirm a pay deduction exists with a code matching the direct deposit code reported in the message.
- Confirm that pay deduction's type is set to Direct Deposit or Net Direct Deposit in Sage 100.
- If the code does not exist in Sage 100 at all, this is a setup gap in Sage 100, not in the source data. Escalate if you cannot add it yourself.
- Rerun the sync and confirm the direct deposit record now syncs.
Multiple Direct Deposit Updates Were Sent for the Same Record
- In the source system, list all active direct deposit records for the employee.
- Identify which two records are resolving to the same Sage 100 deduction and remove or correct the one that should not exist.
- Rerun the sync and confirm only one direct deposit record is present for that deduction.
DirectDeposit Code has IsArchived = True
- Do not attempt to change this in the source system. The archived flag lives on the deduction record in Sage 100, and the message states it must be cleared by support.
- Escalate to have the archived flag on that Sage 100 deduction record cleared.
- Once cleared, rerun the sync and confirm the direct deposit record now syncs.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- The message is the IsArchived one. The message text itself says to contact support to clear the flag; tier 1 cannot clear it directly.
- The "no matching Pay Deduction" message persists after you the pay deduction code and type are correct in Sage 100.
- The error persists after the source data has been corrected and the sync rerun.
- The log text does not match any message in the table above, or looks like it is passed through from Sage 100 itself rather than an Arcoro message.