Payroll Integration Troubleshooting: Deduction, Benefit, and Fringe

David N

September 25, 2026 22:10

These messages all come from the step that writes an employee's benefit deductions and fringes into Arcoro Payroll. Before anything is written, each benefit deduction and fringe is checked for a valid amount, a valid benefit code, and a valid company benefit match. Any benefit that fails a check is left out of this sync run, and the employee still updates for everything else.

For most of these messages (all except the two duplicate messages), if this same benefit code synced successfully into Payroll on an earlier run, and the source system still sends that code this run (even though it is now invalid or fails a match), Payroll's own cleanup logic can treat the earlier synced benefit as no longer present and remove it from the employee in Payroll during this same run. This only happens on syncs sourced from Core HR. If a benefit that used to be there is now gone, this is the first thing to check, not just "was the benefit skipped."

Error Messages

Message text	Direction	Occurs when	Outcome	Fix
Another benefit with the description '[benefit code]' and type '[benefit type]' already exists for this employee with overlapping effective dates. Only one benefit with the same description and type can be active at a time. Correct the benefit in the source system and execute the sync again.	Write (into Payroll)	Two benefit deductions (or two fringes, or a deduction and a post-tax deduction) sent in the same run share the same description and the same benefit type, and their effective/expiration date ranges overlap.	Both the current benefit and the earlier one it collided with are skipped this run. Neither is created or updated. Any benefit that was already synced from a prior run is left as is; it is not deleted.	In the source system, change the description or effective dates so only one active benefit of that type overlaps at a time.
An employee may only have a single benefit per defined contribution type. A benefit of type '[benefit type]' already exists for this employee so the benefit with code '[benefit code]' will be skipped. Change this benefit code in the source system and execute the sync again.	Write (into Payroll)	Two benefit deductions, or a deduction and a fringe, both resolve to a defined-contribution company benefit type (for example 401k or HSA), and one has already been matched this run.	The second benefit code is skipped this run. See the deletion note above; a previously synced benefit for this code can be removed this run if it is still sent as invalid.	In the source system, change the benefit code so the employee has only one defined-contribution benefit of that type.
Benefit deduction '[benefit code]' must have a flat amount or percentage. Correct the benefit in the source system and execute the sync again.	Write (into Payroll)	The benefit deduction has neither an amount nor a percentage set.	The deduction is skipped this run. See the deletion note above.	In the source system, enter a flat amount or a percentage for the deduction.
The amount for benefit deduction '[benefit code]' must be greater than or equal to 0. Correct the benefit in the source system and execute the sync again.	Write (into Payroll)	The deduction uses a flat amount and that amount is negative.	The deduction is skipped this run. See the deletion note above.	In the source system, correct the flat amount to zero or higher.
The amount for benefit deduction '[benefit code]' must be less than $999,999,999,999,999.99. Correct the benefit in the source system and execute the sync again.	Write (into Payroll)	The deduction uses a flat amount and that amount is at or above $999,999,999,999,999.99.	The deduction is skipped this run. See the deletion note above.	In the source system, correct the flat amount to a realistic value under the limit.
The percentage for benefit deduction '[benefit code]' must be between 0 and 100. Correct the benefit in the source system and execute the sync again.	Write (into Payroll)	The deduction uses a percentage and that percentage is below 0 or above 100.	The deduction is skipped this run. See the deletion note above.	In the source system, correct the percentage to a value between 0 and 100.
The post-tax deduction [benefit code] has an amount that exceeds either the Total Amount or the Annual Limit in Payroll. Adjust the amount in the source system or the limits in Payroll and execute the sync again.	Write (into Payroll)	This is a post-tax deduction using a flat amount, and that amount is greater than either the Total Amount or the Annual Limit already set on the matching post-tax deduction in Payroll.	The post-tax deduction is skipped this run. If this code synced successfully before, Payroll's cleanup can remove the earlier post-tax deduction this run (Core HR sourced syncs only).	Either lower the amount in the source system, or raise the Total Amount or Annual Limit on the post-tax deduction in Payroll.
Benefit fringe '[fringe code]' must have a flat amount or percentage. Correct the benefit in the source system and execute the sync again.	Write (into Payroll)	The benefit fringe has neither an amount nor a percentage set.	The fringe is skipped this run. See the deletion note above.	In the source system, enter a flat amount or a percentage for the fringe.
The amount for benefit fringe '[fringe code]' must be greater than or equal to 0. Correct the benefit in the source system and execute the sync again.	Write (into Payroll)	The fringe uses a flat amount and that amount is negative.	The fringe is skipped this run. See the deletion note above.	In the source system, correct the flat amount to zero or higher.
The amount for benefit fringe '[fringe code]' must be less than $999,999,999,999,999.99. Correct the benefit in the source system and execute the sync again.	Write (into Payroll)	The fringe uses a flat amount and that amount is at or above $999,999,999,999,999.99.	The fringe is skipped this run. See the deletion note above.	In the source system, correct the flat amount to a realistic value under the limit.
The percentage for benefit fringe '[fringe code]' must be between 0 and 100. Correct the benefit in the source system and execute the sync again.	Write (into Payroll)	The fringe uses a percentage and that percentage is below 0 or above 100.	The fringe is skipped this run. See the deletion note above.	In the source system, correct the percentage to a value between 0 and 100.
Benefit code '[benefit code]' does not match a company benefit in Payroll. Change the benefit code in the source system or add a new company benefit in Payroll and execute the sync again.	Write (into Payroll)	No company benefit in Payroll has a description that matches this benefit code (checked for pre-tax deductions and for all fringes).	The benefit is skipped this run. See the deletion note above.	In Payroll, add a company benefit with a matching description, or in the source system change the benefit code to match an existing company benefit.
Benefit code '[benefit code]' does not match an active company benefit in Payroll. Change the company benefit's effective start and end dates in Payroll or add a new company benefit in Payroll and execute the sync again.	Write (into Payroll)	A company benefit with this description exists in Payroll, but its effective start date is after (or its effective end date is before) the employee benefit's own effective or expiration date.	The benefit is skipped this run. See the deletion note above.	In Payroll, extend the company benefit's effective start or end date to cover the employee benefit's dates, or add a new company benefit that does.
More than one company benefit with description '[benefit code]' was found in Payroll but only one is allowed. Update the company benefits in Payroll and execute the sync again.	Write (into Payroll)	More than one active company benefit in Payroll shares the same description as the benefit code, after the effective-date filtering above.	The benefit is skipped this run. See the deletion note above.	In Payroll, rename or end-date the company benefits so only one active company benefit uses that description.
Company benefits of type HSA must have the code 'SHSA' for single or 'FHSA' for family. Rename the company benefit '[benefit code]' in Payroll to 'SHSA' or 'FHSA' and execute the sync again.	Write (into Payroll)	The matched company benefit's type is HSA, and its description is not exactly 'SHSA' or 'FHSA'.	The benefit is skipped this run. See the deletion note above.	In Payroll, rename the HSA company benefit's description to 'SHSA' for single coverage or 'FHSA' for family coverage.
Company benefits of a type other than HSA may not have the code 'SHSA' or 'FHSA'. Change code '[benefit code]' to something other than 'SHSA' or 'FHSA' in the source system and execute the sync again.	Write (into Payroll)	The matched company benefit's type is not HSA, but its description is exactly 'SHSA' or 'FHSA'.	The benefit is skipped this run. See the deletion note above.	In Payroll, rename the non-HSA company benefit to a description other than 'SHSA' or 'FHSA', or correct the benefit code in the source system.

Confirming the Error

Open the sync execution in Sync History for the connector in question.
Open the step for the Payroll connector (the destination side of the sync).
Find the Employees entity row for this run and check the Errors, Warnings, Information, Failures, Added, Updated, and Unchanged columns.
Open the entity row and locate the specific employee, then open its errors list.
Match on the fixed part of the sentence (for example, "must have a flat amount or percentage" or "does not match a company benefit in Payroll"), not on the benefit code or type shown in quotes, since those values are specific to your data.
A non-zero Errors count alongside a non-zero Updated count for the employee is expected for this family. It means the employee record still synced; only one benefit deduction or fringe was left out.
A non-zero Failures count is not expected for this family. If Failures is non-zero alongside one of these messages, something else is also wrong; escalate rather than treating it as a normal benefit skip.
If the benefit that used to sync is now missing in Payroll (not just failing to update), check whether the sync source is Core HR and whether the same benefit code still appears in the source but is now failing one of the checks above. That combination can cause Payroll to remove the previously synced benefit during this run.

Resolving the Error

Amount and Percentage Validation

Identify whether the message is for a benefit deduction or a benefit fringe from the message text.
In the source system, open that employee's benefit or fringe record.
Confirm it has either a flat amount or a percentage set, not both missing.
If it uses a flat amount, confirm the amount is zero or greater and below $999,999,999,999,999.99.
If it uses a percentage, confirm the percentage is between 0 and 100.
Save the correction in the source system and run the sync again.

Benefit Code Not Matched to a Company Benefit

In Payroll, confirm a company benefit exists whose description exactly matches the benefit code sent from the source system.
If it exists, confirm its effective start date is on or before the employee benefit's effective date, and its effective end date (if any) is on or after the employee benefit's expiration date.
Confirm only one active company benefit uses that exact description. If more than one does, rename or end-date the extras in Payroll.
Add, rename, or re-date the company benefit in Payroll as needed, or correct the benefit code in the source system.
Run the sync again and confirm the error is gone for that employee.

HSA Code Naming Rules

In Payroll, find the company benefit named in the message.
If its type is HSA, its description must be renamed to exactly 'SHSA' (single) or 'FHSA' (family).
If its type is not HSA, its description must not be 'SHSA' or 'FHSA'; rename it to something else, or correct the benefit code sent from the source system.
Run the sync again and confirm the error is gone.

Duplicate Benefit on the Employee

In the source system, find the employee's benefit deductions and fringes that share the description and type named in the message.
For the duplicate description message, check whether their effective and expiration dates overlap. Adjust the dates, or end-date and remove the older one, so only one is active at a time.
For the duplicate type message, the employee has two benefit codes that both map to the same defined-contribution company benefit type (such as 401k or HSA). Change one of the codes in the source system so only one maps to that type.
Run the sync again and confirm both benefits now sync as expected.

Post-Tax Deduction Limits

In Payroll, open the matching post-tax deduction for the employee and check its Total Amount and Annual Limit fields.
Either lower the amount in the source system so it is within both limits, or raise the Total Amount or Annual Limit in Payroll.
Run the sync again and confirm the post-tax deduction updates without the error.

To confirm any of the fixes above worked, run the sync again and check that the Errors count for the employee dropped and the benefit or fringe now shows as Added or Updated instead of appearing in the errors list.

When to Escalate

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

The Failures count for the entity is non-zero alongside these messages; that is not expected for this family and points to a separate problem.
A benefit that previously synced has disappeared from Payroll, and you did not intentionally remove it from the source system, and the source is Core HR; this may need additional confirmation by us.
You have already corrected the amount, percentage, or company benefit setup as instructed above, run the sync again, and the same error still appears.
The error references a benefit code or company benefit setup that does not exist in either system, suggesting the two systems have gotten out of sync in a way that cannot be easily verified.

Module Navigation