Module Navigation

Troubleshooting Core HR Integration Error: Deduction, Benefit, and Fringe

Core HR stores some benefit deduction codes as a single code that covers both a pre-tax and a post-tax cost, using a pipe character to separate the two parts. When an employee's election for a benefit has both a pre-tax cost and a post-tax cost, the provider expects to find that pipe character in the deduction code so it can split it into the correct pre-tax or post-tax piece. If it cannot do that split cleanly, it will not guess. It rejects that one benefit deduction record and logs an error, and leaves the rest of the employee's sync alone.

These are the only two error-level messages in this family for Core HR. The provider has other benefit and fringe messages, but they are warnings or informational notices and are not covered in this article.

Error Messages

Message textDirectionOccurs whenOutcomeFix
The Benefit with Deduction Code '[deduction code]' has both pre and post tax cost for the employee but the provider was unable to parse the pre/post Code correctly. This record will not be processed. Deduction codes with both a pre and post amount are expected to contain a '|' character. Correct the record in Core HR and execute the sync again.Read (Core HR into Arcoro)Occurs on one benefit deduction record for one employee, and only when all of the following are true. The benefit option is not waived, declined, or marked Not Eligible. The benefit's coverage is a flat dollar amount, not a percentage. The employee's election for that benefit has a pre-tax cost greater than $0 and a post-tax cost greater than $0 at the same time. After the provider tries to split the Deduction Code on its pipe character, the result comes back identical to the original code, meaning no usable pipe was found. That happens when the code has no pipe character at all, or when the pipe character is the very first or very last character in the code.Collection item skipped. Only this one benefit deduction record is left out. The employee record and the employee's other benefit deductions still sync.In Core HR, add a pipe character to the benefit's Deduction Code so it separates a pre-tax portion from a post-tax portion, then rerun the sync.
The Benefit with Deduction Code '[deduction code]' has $0 for the pre and post tax cost for the employee resulting in the provider being unable to parse the Code correctly. This record will not be processed. Correct the record in Core HR and execute the sync again. The most likely resolution for this is to run the recalculation utility in Core HR for this benefit code.Read (Core HR into Arcoro)Occurs on one benefit deduction record for one employee, and only when all of the following are true. The benefit option is not waived, declined, or marked Not Eligible. The Deduction Code still contains a pipe character after the provider processes it. The employee's election for that benefit has a pre-tax cost of exactly $0 and a post-tax cost of exactly $0 at the same time. This check applies whether the benefit's coverage is a flat dollar amount or a percentage.Collection item skipped. Only this one benefit deduction record is left out. The employee record and the employee's other benefit deductions still sync.In Core HR, review the benefit's pre-tax and post-tax cost calculation for this employee so the amounts are no longer both $0, then rerun the sync.

Confirming the Error

  1. Open the sync execution for the Core HR connector in Sync History.
  2. Find the step for this connector, then look at the Employees entity row underneath it. Both 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. Both messages in this article are logged as Errors.
  4. Remember that the affected employee can still appear under Updated. The employee record itself still syncs. Only the one benefit deduction record named in the message is missing.
  5. Open the errors list for the Employees entity row and match on the fixed wording of the sentence, not on the Deduction Code value shown in quotes.
  6. Confirm the Deduction Benefits scope is enabled for this connector before troubleshooting further. If that scope is turned off, neither message can appear and benefit data for that employee will not be read at all.

Resolving the Error

Expected a Split but No Usable Pipe Character

  1. In Core HR, open the benefit deduction code named in the error message.
  2. Confirm the code is meant to carry both a pre-tax and a post-tax portion for this employee's election.
  3. If so, correct the code so it contains a pipe character with a portion of the code on each side of it. A pipe at the very start or the very end of the code is not usable and will still fail.
  4. Rerun the sync and confirm the Employees entity row no longer shows this error for that employee.

Both Pre-Tax and Post-Tax Cost Are $0

  1. In Core HR, open the benefit deduction code named in the error message for the affected employee.
  2. Check the employee's pre-tax and post-tax cost for that benefit election. The message text states that the most likely resolution is to run the recalculation utility in Core HR for this benefit code; see Open questions, as this article cannot confirm the name, location, or steps for that utility.
  3. Once the employee has a nonzero pre-tax cost, a nonzero post-tax cost, or both, rerun the sync and confirm the Employees entity row no longer shows this error for that employee.

When to Escalate

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

  • The Deduction Code has been corrected in Core HR, the sync has been rerun, and the same error still appears for the same employee and the same benefit deduction record.
  • You cannot find a recalculation utility in Core HR, or is not sure whether one exists, for the $0 pre and post tax cost message.
  • The message text in the sync log does not match either message in the table above word for word.
  • An entity row shows Failures instead of Errors for one of these messages, which points to a problem beyond a single bad benefit record.
Was this article helpful?
0 out of 0 found this helpful