Acumatica will not accept an employee record unless it already has a Pay Group, a Pay Schedule, and an Employee Type, and unless its compensation records do not overlap for the same pay rate code. When the source system sends an employee missing one of these fields, or sends compensation data Acumatica cannot match or that overlaps, the sync leaves that employee, or just that one compensation record, out of the write rather than send incomplete data to Acumatica. Separately, if a Pay Schedule inside Acumatica itself has no pay periods configured, the sync cannot safely process compensation and the entire sync run stops until that is corrected on the Acumatica side.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| The source system has sent compensation records that when grouped by the Rate Code have overlapping effective dates. Acumatica requires that Earning Types Start and End dates not overlap. No compensation records will be synced for this Employee. Correct the data in the source system and run the Sync again. | Write (Arcoro to Acumatica) | Only checked when the Compensation scope is enabled. Two or more of the employee's compensation records share the same Rate Code, and, sorted by start date, one record's start date falls on or before the prior record's end date. A record left with no end date is treated as never ending. | None of the employee's compensation records are sent this run. The rest of the employee record (demographics, taxes, and any other enabled scopes) still syncs. | Correct the overlapping compensation start or end dates for that pay rate code in the source system. |
| EarningCode / PayRateType '[pay rate type code]' could not be matched within Acumatica. This record will not be synced with Acumatica. Correct the source data and run the sync again. | Write (Arcoro to Acumatica) | Only checked when the Compensation scope is enabled. One compensation record's pay rate type code does not match any of Acumatica's active, regular-wage earning types. | Only that one compensation record is skipped. Other compensation records for the employee, and the rest of the employee, still sync. | Confirm the pay rate type code is active in Acumatica, or correct the code in the source system. |
| A compensation record was sent from the source without a Start Date field. Acumatica requires Start Date have a value. The compensation will not be synced to Acumatica. Correct the data and run the sync again. | Write (Arcoro to Acumatica) | Only checked when the Compensation scope is enabled. One compensation record has no Start Date value. | Only that one compensation record is skipped. Other compensation records for the employee, and the rest of the employee, still sync. Despite the word Warning in the message name, this occurs as an error and appears in the Errors column, not Warnings. | Add a Start Date to the compensation record in the source system. |
| The provider could not locate a matching Pay Frequency '[pay frequency code]' in Acumatica. The record will not be synced. Please correct the data and run the sync again. | Write (Arcoro to Acumatica) | Only checked when the Pay Group scope is enabled. The employee's Pay Frequency value does not match the code of any Pay Schedule already set up in Acumatica. | The entire employee record is skipped. Nothing for that employee is written this run. | Add a matching Pay Schedule in Acumatica, or correct the Pay Frequency value in the source system to match an existing Acumatica Pay Schedule code. |
| The provider could not locate a matching Employee Type '[employee type]' in Acumatica. The record will not be synced. Please correct the data and run the sync again. | Write (Arcoro to Acumatica) | Checked on every employee write, regardless of which scopes are enabled. The employee's Employee Type value does not map to a supported Acumatica employee type. | The entire employee record is skipped. | Correct the Employee Type value in the source system so it maps to a supported Acumatica employee type. |
| Pay Group '[pay group]' Class default value not found. Acumatica Organizational Employee and Payroll Employee Settings require default values in order to create an employee. Please ensure a PayGroup has been assigned and run the Sync again. | Write (Arcoro to Acumatica) | Checked on every employee write, regardless of which scopes are enabled, before the employee is matched or created. The employee's Pay Group value does not match any Payroll Employee Class already set up in Acumatica. | The entire employee record is skipped, before any organizational or payroll data is written. | In Acumatica, set up a Payroll Employee Class for that Pay Group, or correct the Pay Group value in the source system to match an existing Acumatica Employee Class. |
| Payroll Pay Group is required. | Write (Arcoro to Acumatica) | Checked on every employee write, regardless of which scopes are enabled. The employee's Pay Group field is blank in the source data. | The entire employee record is skipped. This check shares a single pass/fail result with the Pay Schedule and Employee Type required checks below; if any one of the three fails, the whole employee is skipped. | Add a Pay Group value to the employee record in the source system. |
| Pay Schedule is required. | Write (Arcoro to Acumatica) | Checked on every employee write, regardless of which scopes are enabled. The employee's Pay Frequency field is blank in the source data. | The entire employee record is skipped, under the same shared check as Pay Group Required and Employee Type Required. | Add a Pay Frequency value to the employee record in the source system. |
| Employee Type is required. | Write (Arcoro to Acumatica) | Checked on every employee write, regardless of which scopes are enabled. The employee's Employee Type field is blank in the source data. | The entire employee record is skipped, under the same shared check as Pay Group Required and Pay Schedule Required. | Add an Employee Type value to the employee record in the source system. |
| PayFrequency is not set in Acumatica's PayGroupYear object. Contact support for assistance in correcting your data and run your Sync again. | Read (Acumatica to Arcoro) | Checked whenever Pay Schedules are read from Acumatica, regardless of scope. At least one Pay Schedule returned by Acumatica has zero pay periods configured. | The entire sync run stops. This shows as a Failure, not as an error on one entity row. | Escalate. A Pay Group Year record in Acumatica needs its pay periods corrected. |
Confirming the Error
- Open the Sync History screen for your connector and locate the sync execution in question.
- Check the Failures column on the sync execution first. A non-zero Failures count points to the Pay Frequency Periods message, since that message stops the whole run rather than logging against one entity.
- If Failures is zero, find the row for the Employee entity, for the first nine messages in this article, or the Pay Schedule entity, for the Pay Frequency Periods message.
- Check that entity row's Errors, Warnings, Information, Added, Updated, and Unchanged columns to see whether any records were flagged.
- Open the entity's error list and match on the fixed wording of the sentence, for example "could not be matched within Acumatica" or "is required", not on the value shown in quotes, since that value is specific to one employee, pay group, or pay rate code.
- Note the employee identifier, or the Pay Schedule identifier, shown alongside the message so the fix can be applied to the correct record.
Resolving the Error
Compensation Record Problems (Overlap, Unmatched Rate Code, Missing Start Date)
- In the source system, open the employee's compensation records.
- For an overlap message, adjust the start or end date of one of the overlapping records for that pay rate code so the date ranges no longer overlap.
- For an unmatched rate code message, confirm the pay rate type code on the record is spelled correctly and is an active, regular-wage earning type in Acumatica.
- For a missing start date message, add a Start Date to the compensation record.
- Save the change in the source system and run the sync again.
- Confirm the fix worked by checking that the Employee entity row's Errors count for this message no longer includes that employee.
Pay Frequency Not Matched in Acumatica
- In Acumatica, confirm a Pay Schedule exists with a code that matches the employee's Pay Frequency value.
- If no matching Pay Schedule exists, either add one in Acumatica or correct the Pay Frequency value in the source system to match an existing Acumatica Pay Schedule code.
- Run the sync again and confirm the employee no longer appears in the Employee entity's Errors list for this message.
Employee Type Not Matched in Acumatica
- In the source system, check the Employee Type value assigned to the employee.
- Correct the value so it maps to a supported Acumatica employee type.
- Run the sync again and confirm the employee no longer appears in the Employee entity's Errors list for this message.
Pay Group Missing Acumatica Class Defaults
- In Acumatica, confirm a Payroll Employee Class exists that matches the employee's Pay Group value and has its default values set.
- If none exists, set one up in Acumatica, or correct the Pay Group value in the source system to match an existing Acumatica Employee Class.
- Run the sync again and confirm the employee no longer appears in the Employee entity's Errors list for this message.
Required Field Is Blank (Pay Group, Pay Schedule, Employee Type)
- In the source system, open the employee record and check the Pay Group, Pay Frequency, and Employee Type fields.
- Fill in whichever field the message names as required.
- Run the sync again and confirm the employee no longer appears in the Employee entity's Errors list.
Pay Frequency Periods Not Set in Acumatica
- Do not attempt to fix this in the source system; the problem is in Acumatica's own Pay Group Year setup.
- Escalate the ticket so the Pay Group Year record in Acumatica can be corrected to have a valid number of pay periods.
- Once corrected, run the sync again and confirm the sync execution completes without a Failure.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- The Pay Frequency Periods message appears at all. The fix requires changes inside Acumatica's Pay Group Year setup.
- You notice a Pay Group, Pay Schedule, or Employee Type value that already appears correct in the source system, and correctly set up in Acumatica, yet the error still occurs.
- The same employee still fails after the source data and Acumatica setup have both been corrected and a new sync has completed.