Every deduction, benefit, and fringe record sent to Acumatica is matched to a single Deduction Code in Acumatica. That code's setup in Acumatica, whether it is a garnishment, its Contribution Type, and its Calculation Method, decides whether the record can sync and whether the amount must be a flat dollar figure or a percent. Most of the messages in this article happen because the code on the source record does not exist in Acumatica, is configured differently than the source record expects, or is missing a required field such as a code, an Effective Date, or a Coverage Type.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| The provider could not find a matching Deduction Code '[deduction code]' in Acumatica. The record will not be synced. Correct the data and run the Sync again. | Write: source to Acumatica | The benefit deduction record's code already passed the earlier supported-code check, but Acumatica's preloaded Deduction Code list still has no code matching it. | Collection item skipped | Confirm the code exists in Acumatica with an exact matching value, then run the sync again. |
| Could not match Benefit Code '[deduction code]' to a Deduction Code in Acumatica. The record will not be synced but other changes will be processed. Verify the code in both systems and run the Sync again. | Write: source to Acumatica | The benefit deduction record's code does not match any Acumatica Deduction Code whose Contribution Type is Both or Deduction Only and whose Calculation Method is not Amount Per Hour. | Collection item skipped | In Acumatica, confirm the Deduction Code exists with Contribution Type Both or Deduction Only and a Calculation Method other than Amount Per Hour, or correct the code on the source record. |
| The Deduction Code '[deduction code]' is set in Acumatica to have a calculation type of '[Fixed / Percent of Gross]' but the source system sent the Amount as '[Percent / Fixed]'. The record can not be synced. Correct the Contribution Type in one of the systems and attempt the sync again. | Write: source to Acumatica | The matched Acumatica Deduction Code's Calculation Method is Fixed Amount while the benefit record's Coverage Type is not Flat, or the Calculation Method is Percent of Gross while the Coverage Type is not Percent. | Collection item skipped | Set the benefit record's Coverage Type in the source system to match the Deduction Code's Calculation Method in Acumatica, or change the Calculation Method in Acumatica. |
| Benefit Code '[deduction code]' is missing the Coverage Type. Acumatica requires contributions be a flat amount or a percent. The record will not be synced. Correct the data and run the sync again. | Write: source to Acumatica | The benefit deduction record has no value in its Coverage Type field. | Collection item skipped | In the source system, set the Coverage Type on the benefit record to Flat Amount or Percent. |
| The Effective Date cannot be after the Expiration Date for deduction code '[deduction or fringe code]'. | Write: source to Acumatica | The record has both an Effective Date and an Expiration Date, and the Effective Date is later than the Expiration Date. Occurs for both benefit deduction records and fringe records; the message always reads "deduction code" even for a fringe record. | Collection item skipped | In the source system, correct the record so the Effective Date is on or before the Expiration Date. |
| The Deduction Code '[deduction code]' in Acumatica is not supported by the provider. Deduction codes that are Garnishments can not be Synced. Other changes to the Employee will still be processed. | Write: source to Acumatica | The benefit deduction record's code matches an Acumatica Deduction Code that is flagged as a Garnishment. | Collection item skipped | Remove garnishment-type deduction codes from the source benefit deduction feed. Garnishments are not supported by this integration and must be managed directly in Acumatica. |
| The provider encountered a Deduction Code '[deduction or fringe code]' that has an unsupported Calculation Method of Amount Per Hour. The record will not be synced. | Write: source to Acumatica | The Acumatica Deduction Code matched to the benefit or fringe record has its Calculation Method set to Amount Per Hour. This message name ends in "Warning" but the provider logs it as an error. | Collection item skipped | In Acumatica, change the Deduction Code's Calculation Method to Fixed Amount or Percent of Gross; Amount Per Hour is not supported by this integration. |
| Benefit requires a Code to sync with Acumatica. The record will not be synced. Correct the data and run the sync again. | Write: source to Acumatica | The benefit deduction record has no value (blank or whitespace) in its Deduction Code field. | Collection item skipped | In the source system, add a Deduction Code to the benefit record. |
| The Deduction Benefit with code [deduction code] has no effective date, which is a required field. This record will not be processed. Correct data in source system and run the sync again. | Write: source to Acumatica | The benefit deduction record's Effective Date field is empty. | Collection item skipped | In the source system, set an Effective Date on the benefit record. |
| The provider could not find a matching Deduction Code '[fringe code]' in Acumatica. The record will not be synced. Correct the data and run the Sync again. | Write: source to Acumatica | The fringe record's code already passed the earlier supported-code check, but Acumatica's preloaded Deduction Code list still has no code matching it. | Collection item skipped | Confirm the code exists in Acumatica with an exact matching value, then run the sync again. |
| Could not match Fringe Code '[fringe code]' to a Deduction Code in Acumatica. The record will not be synced but other changes will be processed. Verify the code in both systems and run the Sync again. | Write: source to Acumatica | The fringe record's code does not match any Acumatica Deduction Code whose Contribution Type is Both or Contribution Only and whose Calculation Method is not Amount Per Hour. | Collection item skipped | In Acumatica, confirm the Deduction Code exists with Contribution Type Both or Contribution Only and a Calculation Method other than Amount Per Hour, or correct the code on the source record. |
| Fringe Code requires a Code to sync with Acumatica. The record will not be synced. Correct the data and run the sync again. | Write: source to Acumatica | The fringe record has no value (blank or whitespace) in its Fringe Code field. | Collection item skipped | In the source system, add a Fringe Code to the fringe record. |
| The Deduction Code '[deduction code]' is set in Acumatica to have a calculation type of '[Fixed / Percent of Gross]' but the source system sent the Amount as '[Percent / Fixed]'. The record can not be synced. Correct the Contribution Type in one of the systems and attempt the sync again. | Write: source to Acumatica | The matched Acumatica Deduction Code's Calculation Method is Fixed Amount while the fringe record's Coverage Type is not Flat, or the Calculation Method is Percent of Gross while the Coverage Type is not Percent. | Collection item skipped | Set the fringe record's Coverage Type in the source system to match the Deduction Code's Calculation Method in Acumatica, or change the Calculation Method in Acumatica. |
| Fringe Code '[fringe code]' is missing the Coverage Type. Acumatica requires contributions be a flat amount or a percent. The record will not be synced. Correct the data and run the sync again. | Write: source to Acumatica | The fringe record has no value in its Coverage Type field. | Collection item skipped | In the source system, set the Coverage Type on the fringe record to Flat Amount or Percent. |
| The Fringe Code '[fringe code]' in Acumatica is not supported by the provider. Deduction codes that are Garnishments can not be Synced. Other changes to the Employee will still be processed. | Write: source to Acumatica | The fringe record's code matches an Acumatica Deduction Code that is flagged as a Garnishment. | Collection item skipped | Remove garnishment-type deduction codes from the source fringe feed. Garnishments are not supported by this integration and must be managed directly in Acumatica. |
| The Fringe Benefit with code [fringe code] has no effective date, which is a required field. This record will not be processed. Correct data in source system and run the sync again. | Write: source to Acumatica | The fringe record's Effective Date field is empty. | Collection item skipped | In the source system, set an Effective Date on the fringe record. |
Confirming the Error
- Open Sync History and locate the sync execution for the connector and date in question.
- Open the step for the Acumatica connector.
- Find the Employees entity row for that step and check the Errors, Warnings, Information, Failures, Added, Updated, and Unchanged columns to see whether the entity had Errors.
- Expand the Employees entity row to see the affected employee record.
- Open the errors list for that employee and match the fixed part of the sentence, not the values in single quotes, against the messages listed above.
- Note whether the message concerns a benefit deduction record or a fringe record, and which code appears in quotes; this is the value to look up in the source system and in Acumatica.
Resolving the Error
Code Does Not Match or Is Not Supported in Acumatica
Applies to: code not matched, code not supported (benefit or fringe versions).
- In Acumatica, open Deduction and Benefit Codes and search for the code shown in the error message.
- If the code does not exist in Acumatica, either create it or correct the code value on the source record so it points to an existing code.
- If the code exists, confirm its Contribution Type is Both, or Deduction Only for a benefit deduction record, or Contribution Only for a fringe record.
- Confirm the code's Calculation Method is not Amount Per Hour.
- Save any changes and run the sync again.
- Confirm the fix worked by checking that the employee's Errors count for this sync step is now lower and the Deduction Benefits or Fringe Benefits scope shows the record as Added or Updated.
Garnishment Deduction Codes
Applies to: garnishment code not supported (benefit or fringe versions).
- Confirm in Acumatica whether the code shown in the error is flagged as a Garnishment on the Deduction and Benefit Code record.
- If it is a garnishment, remove that code from the benefit deduction or fringe feed in the source system; garnishments must be entered and managed directly in Acumatica, not synced.
- Run the sync again and confirm the employee's other benefit and fringe records still processed normally (no change expected for the garnishment code itself).
Missing Required Fields on the Source Record
Applies to: code required, effective date required, coverage type missing, effective date after expiration date (benefit or fringe versions).
- In the source system, open the employee's benefit deduction or fringe benefit record identified in the error message.
- Add the missing field: a Deduction Code or Fringe Code, an Effective Date, or a Coverage Type of Flat Amount or Percent.
- If the error is about dates, correct the record so the Effective Date is on or before the Expiration Date.
- Save the change in the source system and run the sync again.
- Confirm the fix worked by checking that the record no longer appears in the Errors list for that employee and shows as Added or Updated instead.
Calculation Method or Coverage Type Mismatch
Applies to: calculation method not supported (Amount Per Hour), contribution type mismatch (benefit or fringe versions).
- In Acumatica, open the Deduction Code shown in the error message and check its Calculation Method.
- If the Calculation Method is Amount Per Hour, change it to Fixed Amount or Percent of Gross, since Amount Per Hour is not supported by this integration.
- If the error is a contribution type mismatch, compare the Calculation Method in Acumatica (Fixed Amount or Percent of Gross) to the Coverage Type on the source record (Flat or Percent) and make them match, changing whichever system has the wrong value for this your process.
- Run the sync again.
- Confirm the fix worked by checking that the record 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 Deduction Code exists in Acumatica, is active, has a supported Contribution Type and Calculation Method other than Amount Per Hour, and the sync still returns a code-not-matched message for it. This should not happen once a code passes the earlier supported-code check, so a persistent report here needs engineering review.
- You notice these errors on every sync run even after confirming both systems match, which may point to a problem loading Acumatica's Deduction Codes during setup; see acumatica-preload.html.
- The message text in the sync log does not match any row in this article.
- Corrections have been made in both systems, the sync has been re-run, and the same employee and code still show the error. Escalate with the sync execution date/time, the employee identifier, and the exact error text.