This maintenance release introduces a broad set of improvements across Arcoro Integrations focused on data accuracy, validation consistency, and sync reliability. Updates in this release reduce failed syncs, prevent unintended data changes, and improve clarity when configuring or troubleshooting integrations across supported providers.

Enhancements

Integrations Module

• Company Administrators can now reliably access Edit Company settings within Integrations. This resolves prior permission gaps that prevented admins from updating configuration values.
  • Use Cases - Company admins can update integration configuration without relying on elevated internal roles and expect faster resolution when customer admins need to adjust settings during troubleshooting.
  • Impacted Users - Company Administrators, Support, Professional Services
• Company Administrators can now rerun syncs from the sync history screen.
  • Use Cases - Company admins can rerun executed syncs without relying on elevated internal roles.
  • Impacted Users - Company Administrators, Support, Professional Services
• Integrations will now prevent sync execution when the Arcoro source or destination product is disabled, avoiding misleading “successful” sync results.
  • Use Cases - Prevents syncs from running when a module is intentionally disabled. This eliminates confusion caused by syncs completing with no data movement.
  • Impacted Users - Integration Admins, Support Teams, Implementation Teams
• Multiple enhancements were delivered to improve the handling of union-specific payroll data within Integrations, including validation and processing of union attributes during sync execution.
  • Use Cases
    • Ensures union payroll data syncs correctly without manual correction
    • Reduces payroll errors tied to union pay structures and contribution rules
    • Improves reliability for customers with unionized workforces
  • Impacted Users - Union customers, Payroll admins, Implementation teams, Support
• Additional validation checks were added to prevent sync execution when required data or configuration is incomplete.
  • Use Cases
    • Reduces partial or misleading sync results
    • Improves error clarity when the configuration is invalid
  • Impacted Users - Integration Admins, Support Teams

CMiC

• Updated the CMiC integration to correct how federal and state tax exemptions are handled when syncing from CoreHR. The integration no longer updates the CMiC “Exclude” setting when an employee is marked as tax-exempt in CoreHR, ensuring wages continue to be included in taxable income calculations and reporting. When an employee is exempt, the integration now correctly sends zero tax amounts while preserving CMiC’s internal tax configuration.
  • Use Cases
    • Prevents exempt employees’ wages from being incorrectly excluded from taxable income 
    • Ensures accurate tax calculations and reporting in CMiC
    • Allows CMiC users to manage exclusion settings directly without integration interference
  • Impacted Users - CMiC customers, Payroll admins, Tax and compliance teams, Support

Sage 300

• Resolved an issue where newly auto-created federal and state tax records in Sage 300 were not being detected on subsequent syncs. The integration now properly retrieves newly created tax records each time a sync runs, ensuring federal and state tax data remains current.
  • Use Cases
    • Ensures newly created federal and state tax records in Sage 300 are detected and synced without manual intervention
    • Prevents intermittent tax sync failures caused by missing newly created tax entries
    • Improves reliability of tax data synchronization over repeated sync executions
  • Impacted Users - Payroll Admins, Implementation Teams, Support

Sage 100

• Resolved issues affecting employer retirement contribution handling, ensuring 401(k) match data syncs correctly to Sage 100.
  • Use Cases
    • Employer match amounts now calculate and post correctly
    • Reduces manual payroll reconciliation for retirement benefits
  • Impacted Users - Payroll Admins, HR Teams using Sage 100
• Updated the Integrations preload logic to respect Pay Group scope filtering. When the Pay Group scope is not included in the sync configuration, the integration now skips pay group loading and validation entirely. Existing behavior remains unchanged when the Pay Group scope is enabled.
  • Use Cases
    • Prevents unnecessary processing when pay groups are not part of the configured sync
    • Reduces noise in sync logs by avoiding irrelevant pay group warnings and messages
    • Improves performance and consistency with other scope-aware preload logic
  • Impacted Users - Integration Admins, Support Teams, Implementation Teams

Vista

• AppXChange: Additional validation was introduced to ensure required employee properties are present before exporting data to Vista.
  • Use Cases
    • Prevents malformed or incomplete employee records from exporting
    • Improves early detection of data issues
  • Impacted Users - Vista Payroll Admins, Support Teams
• Improved handling of Vista CSV export edge cases to reduce file rejections during payroll processing.
  • Use Cases
    • Fewer failed Vista imports due to formatting or missing data
    • More reliable payroll file generation
  • Impacted Users - Vista Customers, Implementation

Payroll

• Resolved an issue where the CoreHR to Payroll integration was incorrectly relying on the Pay Group employee field instead of the employee’s Pay Schedule when assigning default pay schedules in Payroll. The integration now uses the employee Pay Schedule value consistently and no longer errors when Pay Group is not assigned. This aligns Integrations behavior with existing ExakTime to CoreHR to Payroll syncs and current Hub Payroll expectations.
  • Use Cases
    • Prevents sync failures when Pay Group is not assigned on the employee record
    • Ensures employee default pay schedules in Payroll are populated from the correct Pay Schedule assignment
    • Aligns Integrations behavior with current CoreHR, ExakTime, and Hub Payroll data flow
  • Impacted Users - Payroll Admins, Integration Admins, Implementation Teams, Support 
• Resolved an issue where employees marked as terminated in CoreHR were syncing to Payroll with an active status. The integration now correctly updates employee status in Payroll when a termination status and termination date are present in CoreHR. Termination date and termination status changes are now applied consistently, ensuring terminated employees are not left active in Payroll after a sync.
  • Use Cases
    • Prevents terminated employees from appearing as active in Payroll
    • Ensures payroll processing, reporting, and compliance reflect accurate employee status
    • Eliminates the need for manual correction of employee status after syncs
  • Impacted Users - Payroll Admins, HR Teams, Integration Admins, Support
• Updated the CoreHR to Payroll integration to correctly handle inactive compensation records. When a compensation record is marked inactive in CoreHR, the corresponding earning item is now removed from Payroll, aligning with Payroll’s lack of support for inactive compensation records.
  • Use Cases
    • Prevents inactive CoreHR compensation records from continuing to affect payroll calculations
    • Ensures Payroll earnings accurately reflect current, active compensation only
    • Eliminates the need for manual cleanup of outdated earning items in Payroll
  • Impacted Users - Payroll Admins, HR Teams, Integration Admins, Support