We are proud to announce the following enhancements to our existing products and features to improve your experience.
Enhancements
Integrations Module
- Optimized Field Length Validation for Improved Efficiency:
- We’ve moved field length validation to the model level, allowing data to be pre-validated before processing. This change improves efficiency by determining upfront whether a record should be retained or trigger an error/warning, reducing unnecessary processing.
- Spectrum Beta
- We have implemented the output for employee benefits to be ingested into Spectrum.
Providers
All Providers
- Validation Added for Pay Rate in Compensation Records:
- To ensure data accuracy, we've implemented a validation check to prevent compensation records from being processed if the pay rate is 0 or less. If an invalid pay rate is detected, an error message will be triggered. This enhancement, identified during automation testing, ensures that all compensation records include a valid pay rate
Core HR
- Middle Name Can Now Be Set to Null/Empty:
- When syncing employees from X to Core HR, if the Middle Name field is present but contains a null/empty value, it will now correctly update in Core HR as null/empty instead of retaining an incorrect value.
- Worker's Compensation Code Validation:
- A new warning message has been added for unmatched Worker’s Compensation Codes. If a match is not found, the following warning will appear:
- "Core HR was unable to find a match for the Worker's Compensation Code value {0}. Other changes will still be processed."
Integrations UI
- Integration App Buttons Now Open in New Tabs:
- All menu and grid buttons in the Integration app will now open in a new browser tab for improved navigation and multitasking.
- Product Configuration Name Added to Connectors Grid:
- A new column for Product Configuration Name has been added to the Connectors Grid to make it easier to gather sync details. This column appears at the end of each row.
- Source/Destination Product Added to Sync Grid:
- To improve visibility, two new columns—Source Product and Destination Product—have been added to the Sync Grid (e.g., ExakTime, Core HR). These columns appear after the User column.
- Extended Benefit Models with Additional Fields:
- The ArcoroDeductionBenefit and ArcoroFringeBenefit models now include:
- CarrierCode = Package_BenefitPlan.PlanDesc
- CoverageLevel = Package_Option.OptionName
- The ArcoroDeductionBenefit and ArcoroFringeBenefit models now include:
- Expand/Collapse All Error and Warning Lists:
- Users can now expand or collapse all error and warning lists with a single click, making it easier to manage issues across multiple employees without manually opening or closing each list.
Acumatica
- Enhanced Sync Behavior for Terminated Employees:
- We've updated our Acumatica to Core HR sync to align with our Sage 100 and 300 integration behavior. Now, only active employees and those terminated from January 1 of the previous year to the current date will be pulled over during the sync.
- Resolved Termination Reason Lookup Issue:
- We fixed an issue where the termination reason "Medical Issues" was not syncing correctly due to a mismatch in formatting ("MedicalIssues" vs. "Medical Issues"). This discrepancy, identified during automation testing, has now been corrected to ensure accurate data transfer.
CMiC
- Improved Log Messaging for Duplicate Departments:
- We've updated the log message for duplicate "Company Level" department entries to be clearer. The new message states:
- "A duplicate department named 'Company Level' has been sent to Core HR. Only the first instance will be synced." This is a messaging improvement only—the behavior remains unchanged; only the first occurrence will be processed.
- We've updated the log message for duplicate "Company Level" department entries to be clearer. The new message states:
Sage 100
- Updated Messaging for Non-Income Tax States:
- The integration platform previously flagged warnings for missing or mismatched state tax records for all states. However, states without income tax (FL, AK, SD, TX, WA, WY, NV, TN, NH) no longer trigger a warning. Instead, an informational message will be displayed:
- "The State Tax record for {AK} will not be processed because {AK} does not have an income tax."
- This update improves clarity, aligns with state tax policies, and reduces unnecessary warning clutter.
- The integration platform previously flagged warnings for missing or mismatched state tax records for all states. However, states without income tax (FL, AK, SD, TX, WA, WY, NV, TN, NH) no longer trigger a warning. Instead, an informational message will be displayed:
Sage 300
- Middle Name Can Now Be Set to Null/Empty:
- When syncing employees from Core HR to Sage 300, if the Middle Name field is present but contains a null/empty value, it will now correctly update in Sage 300 as null/empty instead of retaining an incorrect value.
- Optimized Sync Behavior for Terminated Employees: To streamline processes and reduce manual entry, the integration will now bypass unmatched logic for terminated employees.
- When an employee is terminated, the system will not process unmatched logic for Compensation, Direct Deposit, Benefits, or Fringes.
- Demographic data will still be synced, but no changes will be made to Federal/State Taxes, Compensation, Direct Deposit, or Benefits.
- An informational log will be recorded when an employee is marked as terminated, stating: "Changes to Tax (Federal/State), Compensation, Direct Deposit, Benefits (Deduction/Fringe) will not be synced for terminated employees. Any changes required to correctly process the employee’s last payroll must be made in Sage."
- This info message will only be logged when an employee's status is updated to terminated to avoid unnecessary log noise.
Vista
- Configurable OverrideCalculation for Benefits: Previously, OverrideCalculation was defaulted to "R" for all customers. Now, this value can be set based on the selected benefit within the connector configuration.