Module Navigation

Troubleshooting CMiC Integration Error: Deduction, Benefit, and Fringe

CMiC syncs write each employee's deduction and fringe benefit elections from the source system into CMiC. Before a single election can be written, CMiC needs a matching benefit setup record already in place (a code, a plan or coverage level, a carrier, and a payroll code), and the source record itself needs a complete, non-conflicting code and date range. Every message in this article is one of those checks failing for one benefit record.

This connector has two different code paths for deduction and fringe benefits, controlled by a connector setting named Use Legacy Deduction/Benefit Endpoints. Those with that setting turned on run the legacy path and can only see the legacy messages in this article. Those with it turned off run the current path and can only see the current messages. A few messages can appear from either path. Check the connector configuration before assuming a message is unexpected.

On the current path, more than one of these messages can appear for the very same benefit record in the same sync run. For example, a record missing its code will also fail the plan lookup, so both a missing-code message and a plan-not-found message can show up together. Always resolve the missing-value messages for a record first, then re-check whether a plan-not-found message for that same record is still present.

Error Messages

Message textDirectionOccurs whenOutcomeFix
A matching Benefit/Deduction was not found in CMiC: [deduction code] with a pay run code (frequency) of [pay run code] The record will not be synced.Write (Arcoro to CMiC)Legacy path only. Deduction Benefits scope. After the record passes the missing-code and overlapping-date checks, no CMiC Company Deduction record matches all of: same company, same deduction code, same payroll code (pay run/frequency), same deduction type (Flat vs Percent, derived from the source coverage type), and a CMiC start date on or before the record's effective date with no end date or an end date on or after that effective date.Collection item skipped. Only this deduction record is left out; the employee and every other benefit still sync.In CMiC, add or correct the Company Deduction setup for that code, payroll code, coverage type, and date range.
Company Fringe Benefit not found [fringe code] [effective date]-[expiration date]Write (Arcoro to CMiC)Legacy path only. Fringe Benefits scope. Same style of lookup as the deduction case above, but against CMiC Company Benefit (fringe) records: no row matches the company, fringe code, payroll code, benefit type, and a start/end date range that contains the record's effective date.Collection item skipped. Only this fringe record is left out; the employee and every other benefit still sync.In CMiC, add or correct the Company Benefit (fringe) setup for that code, payroll code, coverage type, and date range.
[Deduction/Fringe] code is required, but is missing for the benefit. The record will not be processed. Fix the data in the source and run the sync again.Write (Arcoro to CMiC)Both paths. The Deduction Code (legacy and current) or Fringe Code (current only) field on the source benefit record is null (legacy) or null/blank (current).Collection item skipped.In the source system, populate the Deduction Code or Fringe Code on the benefit election record.
Missing Fringe Code, record will be skippedWrite (Arcoro to CMiC)Legacy path only. Fringe Benefits scope. The source fringe record's Fringe Code field is null.Collection item skipped.In the source system, populate the Fringe Code on the benefit election record.
Duplicate Fringe, record will be skippedWrite (Arcoro to CMiC)Legacy path only. Fringe Benefits scope. A CMiC fringe record was matched (same code, plan, payroll code, benefit type, and start date), but that same CMiC record was already claimed by an earlier source record processed in this same sync run.Collection item skipped. Only the later duplicate source record is skipped; the first matching source record still updates that CMiC record normally.In the source system, remove or correct the duplicate benefit election so only one active record maps to that fringe code, plan, coverage level, and start date.
The benefit with [Deduction/Fringe] Code [code] and Coverage Level [coverage level] could not be matched with any existing plan in CMiC. The record will not be processed. Corrrect data in CMiC and run sync again.Write (Arcoro to CMiC)Current path only. Deduction Benefits or Fringe Benefits scope. After the code, carrier, and coverage-level checks run (regardless of whether they passed), no CMiC Company Deduction/Benefit record has both the matching Code and the matching Plan Code (the source Coverage Level value). Note the message keeps its source spelling of "Corrrect"; match on the rest of the sentence.Collection item skipped. This message can appear alongside a missing-code, missing-carrier, or missing-coverage-level message for the same record; resolve those first.In CMiC, confirm the Company Deduction/Benefit setup for that code and plan code exists, or correct the Coverage Level value in the source so it matches CMiC's plan code exactly.
The Benefit record has both Deduction Code ([deduction code]) and Fringe Code ([fringe code]) set up at the same time, which is invalid for CMiC. It only accepts a benefit as either Deduction or Fringe, not both. Please ensure the correct benefit plan setup in CoreHR and run the sync again.Write (Arcoro to CMiC)Current path only. Runs before the Deduction Benefits and Fringe Benefits scopes are processed. The same source benefit election appears in both the deduction collection and the fringe collection at once.Collection item skipped from both the Deduction Benefits and Fringe Benefits collections for that one election; every other benefit still syncs.In the source system, set the benefit plan up as either a deduction or a fringe, not both.
Carrier code is required, but is missing for the benefit. The record will not be processed. Fix the data in the source and run the sync again.Write (Arcoro to CMiC)Current path only. Deduction Benefits or Fringe Benefits scope. The source record's Carrier Code field is null or blank.Collection item skipped.In the source system, populate the Carrier Code on the benefit election.
Coverage Level is required, but is missing for the benefit. The record will not be processed. Fix the data in the source and run the sync again.Write (Arcoro to CMiC)Current path only. Deduction Benefits or Fringe Benefits scope. The source record's Coverage Level field is null or blank. This check runs independently of the code and carrier checks, so it can appear together with them for the same record.Collection item skipped.In the source system, populate the Coverage Level, matching CMiC's plan code for that benefit.
Coverage Level exceeds the maximum length of 10 characters. The record will not be processed. Fix the data in the source and run the sync again.Write (Arcoro to CMiC)Current path only. Only evaluated when Coverage Level is present. The value is longer than 10 characters.Collection item skipped.In the source system, shorten the Coverage Level value to 10 characters or fewer, matching CMiC's plan code.
The [Deduction/Fringe] Code exceeds the maximum length of 4 characters. The record will not be processed. Fix the data in the source and run the sync again.Write (Arcoro to CMiC)Current path only. Only evaluated when the Deduction Code or Fringe Code is present. The value is longer than 4 characters.Collection item skipped.In the source system, shorten the code to 4 characters or fewer, matching CMiC's code.
A Remittance Amount already exists in CMiC for the [Deduction/Fringe] Code [code]. The record will be processed, but CMiC side rules will prior the remittance amount to be used and will ignore amount set on source system. Please correct the data setup in CMiC and run the sync again if necessary.Write (Arcoro to CMiC)Current path only. Deduction Benefits or Fringe Benefits scope. The matched CMiC Company Deduction/Benefit setup record already has a Remittance Total Amount configured. On the Fringe Benefits scope this message always shows the label "Deduction" instead of "Fringe" in the code label, a known text defect; match on the fixed part of the sentence, not the label word.Field skipped only. The record itself is still added or updated in CMiC as normal; only the benefit amount is left as CMiC's existing remittance amount instead of being overwritten with the source system's value. This is the one message in this article where the record is not skipped despite the error-level severity.No source-side fix needed. If you want the source amount used instead, the remittance amount must be removed from the Company Deduction/Benefit setup in CMiC.
Carrier Code exceeds the maximum length of 8 characters. The record will not be processed. Fix the data in the source system and run the sync again.Write (Arcoro to CMiC)Current path only. Only evaluated when Carrier Code is present. The value is longer than 8 characters.Collection item skipped.In the source system, shorten the Carrier Code value to 8 characters or fewer.
Deduction code '[deduction code]' has overlapping effective date ranges across multiple source records. All records for this code will be skipped. Correct the data in the source system and run the Sync again.Write (Arcoro to CMiC)Legacy path only. Two or more source deduction records share the same Deduction Code and their effective-to-expiration date ranges overlap each other. This check compares every source record for that code against every other, with no filter for whether a record is currently active or whether today falls inside its dates; a record with no expiration date is treated as open-ended and will overlap any later record for the same code.Collection item skipped, repeated for every source record with that code, for this sync run. Existing CMiC records for that code are also left untouched, neither updated nor deleted. Other deduction codes for the employee are unaffected.In the source system, correct the effective and expiration dates so only one record per Deduction Code is active on any given date, or end-date the older record before the new one starts.
Fringe code '[fringe code]' has overlapping effective date ranges across multiple source records. No records for this code will be added, updated, or deleted. Correct the data in the source system and run the Sync again.Write (Arcoro to CMiC)Legacy path only. Same check as the deduction version above, applied to fringe records sharing the same Fringe Code.Collection item skipped, repeated for every source record with that code, for this sync run. Existing CMiC records for that code are also left untouched. Other fringe codes for the employee are unaffected.In the source system, correct the effective and expiration dates so only one record per Fringe Code is active on any given date, or end-date the older record before the new one starts.

Confirming the Error

  1. Open the sync execution in Sync History for your CMiC connector.
  2. Find the step for this connector and open the row for the Employees entity.
  3. Check the Total, Added, Updated, Unchanged, Information, Warnings, and Errors columns for that row. Every message in this article is logged at Error severity, so it appears in the Errors count, never in Warnings or Information.
  4. Failures is a step-level count and tab, not a per-entity column, so it does not appear on the entity row. A non-zero Failures count on the step is not related to any message in this article. It reflects a more severe category of problem that stopped part of the run; if Failures is non-zero, treat it as a separate issue and investigate it on its own.
  5. Open the entity row's errors list and locate the affected employee.
  6. Match the error text against the fixed part of the sentences in the table above, ignoring the bracketed values (the code, coverage level, dates, and so on are specific to your data).
  7. Confirm the connector's Use Legacy Deduction/Benefit Endpoints setting for this before assuming which messages should or should not be possible.

Resolving the Error

Missing or Invalid Code, Carrier, or Coverage Level Values

  1. Identify the employee and benefit code named in the error.
  2. In the source system, open that employee's benefit election and check the Deduction Code, Fringe Code, Carrier Code, and Coverage Level fields.
  3. Fill in any blank required field, or shorten any field that exceeds its maximum length (4 characters for Deduction/Fringe Code, 8 characters for Carrier Code, 10 characters for Coverage Level).
  4. Save the change in the source system and run the sync again.
  5. Confirm the message no longer appears for that employee in the next sync execution.

CMiC Plan or Company Benefit Setup Not Found

  1. Identify the code, coverage level or plan code, and payroll code named in the error.
  2. Confirm with your CMiC administrator that a matching Company Deduction or Company Benefit record exists in CMiC for that code, payroll code, and coverage type, and that its date range covers the employee's effective date.
  3. If it does not exist, your CMiC administrator needs to add it in CMiC.
  4. If it does exist but the Coverage Level in the source system does not match CMiC's plan code exactly, correct the value in the source system.
  5. Run the sync again and confirm the message no longer appears for that employee.

A Benefit Record Has Both a Deduction Code and a Fringe Code

  1. Identify the employee and the deduction code/fringe code pair named in the error.
  2. In the source system, open the benefit plan setup for that election and confirm it is configured as either a deduction or a fringe benefit, not both.
  3. Correct the plan setup so only one code type is populated.
  4. Run the sync again and confirm the message no longer appears for that employee.

Duplicate or Overlapping Benefit Records

  1. Identify the code named in the error and pull every benefit election for that employee with that same code from the source system, including expired ones.
  2. Check the effective and expiration dates for overlap. An overlap is possible even if one of the records is expired relative to today, since the check compares date ranges, not current status.
  3. Correct the dates, or end-date/remove the older or duplicate record, so only one record for that code is active at a time.
  4. Run the sync again and confirm the message no longer appears, and that the expected add, update, or delete occurred for that code.

CMiC Already Has a Remittance Amount Defined

  1. This message is informational: the record is still synced; only the benefit amount is affected.
  2. If you want the source system's amount used instead of CMiC's remittance amount, your CMiC administrator needs to remove the remittance amount from the Company Deduction/Benefit setup in CMiC.
  3. If you are fine with CMiC's existing remittance amount governing, no action is needed.

When to Escalate

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

  • The error text does not match any message in this article after accounting for the bracketed values.
  • The step shows a non-zero Failures count; that is a separate issue from the messages in this article.
  • You confirm the CMiC-side setup and source data both look correct, and the message still appears after a re-run.
  • The same employee record shows a different mix of legacy and current-path messages across separate sync runs without the Use Legacy Deduction/Benefit Endpoints setting having changed.
Was this article helpful?
0 out of 0 found this helpful