Module Navigation

Troubleshooting CMiC Integration Error: Target System Rejected the Write

CMiC's write API answered one of our create or update requests with a rejection instead of a success response. The connector recognizes certain CMiC rejection texts and rewrites them into the friendlier messages in this article, but the underlying cause is always the same: CMiC would not accept the record as sent.

What happens next depends on which part of the employee record was being written when CMiC rejected it. A brand new hire is written to CMiC as a single all-or-nothing request, so a rejection on a new hire fails that employee completely for the run. An existing employee is written as a series of separate smaller requests, one per section of the record (address, taxes, benefits, compensation, and so on), so a rejection there only drops the section or list entry that CMiC rejected. Every other section for that employee, and every other employee in the run, is unaffected.

There are no mapping reference documents for this provider to cross-check against; this article and the underlying code are the only source of truth for CMiC behavior.

Error Messages

Message textDirectionOccurs whenOutcomeFix
This error suggests that CMiC cannot find Geocode from Address. Check employee Address. Presently the employee cannot be saved. Original error: [original CMiC error text]Write (Arcoro to CMiC)CMiC could not resolve a Vertex geocode from the employee's home address fields (the raw CMiC text begins with a string index out of range error).New hire: the whole employee record fails to save. Existing employee: only the address section fails to update; the rest of the employee's data still syncs.Correct the employee's home address (street, city, state, zip) in the source system, then run the sync again.
The Effective Date of the change is before the date the employee was created in the provider or the Hire Date is before the Birth Date. Please review the data and try your sync again. Original error: [original CMiC error text]Write (Arcoro to CMiC)occurs when adding a new hire to CMiC: the raw CMiC text is an EMH_HIRE_DATE rejection, meaning the supplied Hire Date is not valid for the employee history record CMiC is about to create (Hire Date before Birth Date, or earlier than a record CMiC believes already exists for that employee number).Whole new-hire record fails to save. No part of that employee is written this run.Correct the employee's Hire Date and Birth Date in the source system, then run the sync again.
The Effective Date of the change is before the date the employee was created in the provider. Please review the data and try your sync again. Original error: [original CMiC error text]Write (Arcoro to CMiC)occurs when adding a new hire to CMiC: the raw CMiC text is an EMH_PRN_CODE rejection reporting a missing Pay Run Code for the employee history record CMiC is about to create.Whole new-hire record fails to save. No part of that employee is written this run.Confirm the employee's Pay Frequency maps to a valid Pay Run Code in CMiC, correct the source data or the CMiC setup, then run the sync again.
The State Tax Filing Year was not accepted due to the combination of Geocode, Tax Year, and Tax Filing Status. Modify the record in your source system and run the sync again. Original error: [original CMiC error text]Write (Arcoro to CMiC)occurs while writing one state tax record in the employee's State Taxes list (the raw CMiC text is a TXX_FILING_STATUS rejection for an invalid Vertex filing status).Collection item skipped. That one state tax record is not saved; every other state tax record and the rest of the employee's data still sync.Correct the employee's state filing status or tax year for that state in the source system, then run the sync again.
The social security number already exists within FEIN number in CMiCWrite (Arcoro to CMiC)occurs while writing the employee's social security number: CMiC reports that SSN is already assigned to a different employee under the same FEIN.New hire: the whole employee record fails to save. Existing employee: only the identity fields covering this update fail; the rest of the employee's data still syncs.Confirm the SSN in the source system is correct and not a duplicate of another active employee, correct it, then run the sync again.
The social security number already exists within Company [company number] in CMiCWrite (Arcoro to CMiC)Same as above, but CMiC reports the conflict is scoped to one specific company code rather than the whole FEIN.New hire: the whole employee record fails to save. Existing employee: only the identity fields covering this update fail; the rest of the employee's data still syncs.Confirm the SSN in the source system is correct and not a duplicate of another active employee in that company, correct it, then run the sync again.
One or more benefit amounts cannot be updated because a Remittance Amount already exists in CMiC. The affected records may not sync correctly. Please correct the data setup in CMiC and run the sync again.Write (Arcoro to CMiC)Occurs while writing one benefit or deduction record in the employee's Deduction Benefits or Fringe Benefits list: CMiC already has a remittance amount recorded for that plan.Collection item skipped. That one benefit record is not saved; every other benefit or deduction record and the rest of the employee's data still sync.In CMiC, review and correct the existing remittance amount setup for that plan, then run the sync again.
The employee could not be terminated in CMiC due to an error within the CMiC system. Please update the employee's status and termination date directly in CMiC, then rerun the sync.Write (Arcoro to CMiC)Occurs while writing an employee's status and termination date: CMiC reports the employee has already been terminated on a date it will not let this update override.Field skipped. The status and termination date fields do not update; the rest of the employee's data still syncs. (A first-time sync of an employee who was already terminated in the source system before ever reaching CMiC could instead fail the whole new-hire record; this edge case is listed under Open questions.)Update the employee's status and termination date directly in CMiC, then run the sync again.
One or more benefits could not be matched to any eligible plan for employee [employee ID] on CMiC. Those unmatched records will not be processed. Please review the data in the source system and in CMiC and run the sync again.Write (Arcoro to CMiC)Occurs while writing one benefit record in the employee's Deduction Benefits or Fringe Benefits list: CMiC found no eligible plan matching what was sent for this employee.Collection item skipped. That one benefit record is not saved; every other benefit or deduction record and the rest of the employee's data still sync.Confirm the employee is eligible for that plan and that the plan is set up correctly in CMiC, correct the source data or CMiC setup, then run the sync again.
Employer Portion must be setup on CMiC before selecting some plans for Company [company ID] And Payrun [pay run]. Some records may not be processed. Fix data setup in CMiC and run the sync again.Write (Arcoro to CMiC)Occurs while writing one benefit record in the employee's Deduction Benefits or Fringe Benefits list: the plan requires an employer portion that is not configured for that company and pay run.Collection item skipped. That one benefit record is not saved; every other benefit or deduction record and the rest of the employee's data still sync.In CMiC, set up the employer portion for that plan, company, and pay run, then run the sync again.
GL Accounts must setup in Company [company ID] before selecting Deduction Code [deduction code]. Records using this code will not be processed. Fix data setup in CMiC and run the sync again.Write (Arcoro to CMiC)Occurs while writing one benefit or deduction record: the deduction code requires GL accounts that are not configured for that company.Collection item skipped. That one benefit or deduction record is not saved; every other record and the rest of the employee's data still sync.In CMiC, set up the required GL accounts for that company and deduction code, then run the sync again.
State Code [selected state code] is not compatible with Vertex State Code [zip-derived state code] in CMiC. The record will not be processed. Please, verify if the state selection matches the zip code for the same state in source system and run the sync again.Write (Arcoro to CMiC)Occurs while writing the employee's home address: the selected state does not match the state Vertex derives from the zip code.New hire: the whole employee record fails to save. Existing employee: only the address section fails to update; the rest of the employee's data still syncs.Correct the employee's state or zip code in the source system so they agree, then run the sync again.
It was not possible to match any state Code '[selected state code]' for Country '[country]' in CMiC. This record will not be processed. Please, review your data and run the sync again.Write (Arcoro to CMiC)Occurs while writing the employee's home address: CMiC has no state on file matching the supplied state and country combination.New hire: the whole employee record fails to save. Existing employee: only the address section fails to update; the rest of the employee's data still syncs.Correct the employee's state or country in the source system, or add the state to CMiC if it is genuinely missing, then run the sync again.
WCB Code [WCB code] could not be matched with any available value for Company [company] in Country [country] and State [state] in CMiC. The record will no be processed. Please correct data in source system and run the sync again.Write (Arcoro to CMiC)Occurs while writing the employee's Workers' Compensation Code field: the code does not match any value CMiC has on file for that company, country, and state.New hire: the whole employee record fails to save. Existing employee: only the work location and workers' compensation code section fails to update; the rest of the employee's data still syncs.Correct the employee's Workers' Compensation Code in the source system, or add the missing code in CMiC if it is genuinely missing, then run the sync again.
Location '[location]' could not be found for Company [company] or is inactive on CMiC. The record will not be processed. Please review the data and run the sync again.Write (Arcoro to CMiC)Occurs while writing the employee's work location field: the location code does not exist for that company in CMiC, or exists but is inactive.New hire: the whole employee record fails to save. Existing employee: only the work location and workers' compensation code section fails to update; the rest of the employee's data still syncs.Correct the employee's work location in the source system, or activate or add the location in CMiC, then run the sync again.
The [property name] ([CMiC property]) property value is missing. Verifiy if the sync has any other errors, as this may cause some properties not to be mapped. Correct all data in source system then run the sync again.Write (Arcoro to CMiC)A catch-all: occurs whenever CMiC reports any required property as missing, on any part of the employee write (new hire, an existing employee update, or a benefit, tax, or compensation list entry).Varies with where it occurs: whole new-hire record skipped, a single section skipped on an existing employee update, or one list entry skipped in a benefits, tax, or compensation collection. Check the other errors logged against the same employee to see which part of the write it came from.Fill in the named property in the source system for that employee, then run the sync again.
The employee ID [employee ID] is associated with another employee in CMiC. Please contact CMiC support to correct the data in CMiC and run the sync again.Write (Arcoro to CMiC)Occurs while writing the employee's primary employee number link: CMiC already associates that employee ID with a different employee record.New hire: the whole employee record fails to save. Existing employee: only the identity fields covering this update fail; the rest of the employee's data still syncs.Contact CMiC support to correct the conflicting employee association in CMiC, then run the sync again.

Confirming the Error

  1. Open the sync execution for the run reported in the Sync History screen.
  2. Open the step for the CMiC connector.
  3. Find the affected employee in the entity list for that step.
  4. Open the errors list for that employee row and match on the fixed part of the sentence (the wording that does not change), ignoring the specific codes, names, or dates in brackets or quotes.
  5. Check the Total, Added, Updated, Unchanged, Information, Warnings, and Errors columns for that entity row. For this family, a nonzero Errors count with the employee still counted under Added or Updated means only part of that employee's record was rejected; everything else for that employee still went through. Failures is a step-level count and tab, not a per-entity column. A nonzero Failures count on the step means something more severe interrupted the run, and it is not simply a bigger version of Errors.

Resolving the Error

Address and Geocode Issues

Covers the Geocode message, the two State Code messages, and the Employee ID / property-missing messages when they point at address fields.

  1. In the source system, open the employee's home address.
  2. Confirm the street, city, state, and zip code are complete and that the state agrees with the zip code.
  3. Save the correction and run the sync again.
  4. Confirm the fix worked by checking the same employee no longer appears in the errors list for that step.

Hire Date, Pay Run Code, and Identity Issues (New Hires)

Covers the Hire Date message, the Pay Run Code message, both SSN messages, and the Employee ID association message.

  1. In the source system, open the employee record.
  2. Confirm the Hire Date is on or after the Birth Date and is accurate.
  3. Confirm the Pay Frequency is set and maps to a valid Pay Run Code.
  4. Confirm the social security number is correct and is not already in use by another active employee.
  5. Save the corrections and run the sync again.
  6. Confirm the fix worked by checking the employee is now counted under Added or Updated and no longer appears in the errors list for that entity.

State Tax Filing Status

  1. In the source system, open the employee's state tax filing details for the affected state.
  2. Confirm the tax year and filing status are correct for that state.
  3. Save the correction and run the sync again.
  4. Confirm the fix worked by checking that state tax record no longer appears in the errors list for that employee.

Termination

  1. Open the employee directly in CMiC.
  2. Update the employee's status and termination date in CMiC to match what the source system expects.
  3. Run the sync again.
  4. Confirm the fix worked by checking the termination error no longer appears for that employee.

Benefits and Deductions (Eligible Plan, Employer Portion, GL Accounts, Remittance Amount)

  1. In CMiC, review the plan, deduction code, or remittance setup named in the error for the company and pay run mentioned.
  2. Correct the CMiC setup, or in the source system correct the plan or deduction code assigned to the employee if the setup in CMiC is actually correct.
  3. Run the sync again.
  4. Confirm the fix worked by checking that benefit or deduction record no longer appears in the errors list for that employee.

Workers’ Compensation Code and Work Location

  1. In the source system, confirm the employee's Workers' Compensation Code and work location are correct.
  2. In CMiC, confirm the code or location exists for that company, country, and state, and is active.
  3. Correct whichever side is wrong, then run the sync again.
  4. Confirm the fix worked by checking the work location section no longer appears in the errors list 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 message tells you to contact CMiC support (the Employee ID association message) and you do not have a CMiC support contact of your own.
  • You has corrected the source data or the CMiC setup as described above and the same message still appears on a rerun.
  • The property-missing message keeps appearing with no other errors logged against the same employee, so the affected section cannot be identified from the sync log alone.
  • The step shows a non-zero Failures count that you cannot explain using the errors list for the affected entity.
Was this article helpful?
0 out of 0 found this helpful