We are proud to announce the following enhancements to our existing products and features to improve your experience.

Enhancements

Integrations Module

• Logging
  • Facility Code - Fixed a logging message about missing Facility Code 1 even when it existed, ensuring proper facility code evaluation during synchronization. 
  • Child Objects - Updated logging capabilities to detect and record changes in child objects, improving traceability.
  • Date Field Consistency - Updated data entry date controls across the Integrations UI for consistency and alignment with shared project standards.
• SFTP Feature
  • Extend Functionality within the Integrations module to enable secure data export to external systems using SFTP (SSH File Transfer Protocol). This includes:
    • Secure storage of credentials and connection details
    • Organized folder management
    • Input validation to ensure all required details are supplied

Providers

Acumatica

• Ethnicity Conversion - Fixed a mismatch in ethnicity conversions where Acumatica uses single-character strings (e.g. "H" for Hispanic) but the reader expected full names like "Hispanic", causing ethnicity data to revert to Null during synchronization.
• Payroll Method Matching - Updated the "MatchOrCreateEmployeePayroll" method to stop processing once a model is completed, preventing unnecessary writes and improving error logging visibility.
• Compensation Scope Disabled - Resolved a "Bad Data" error when syncing employees from Core HR to Acumatica with the Compensation scope disabled.

CMiC

• Employee Address Field
  • Improved logging for employee address fields during syncs to include readable string values instead of integers, ensuring better clarity across multiple providers.
  • Reworked provider to Core HR updates to the Home Address 2 field to be correct.

Sage 100

• Middle Name - Updated employee syncs to Sage 100 to allow middle names to be set as null or empty if no value is provided in the Core HR data.
• Indiana Filing Status - Updated the mapping of Indiana state filing statuses between Sage 100 and Core HR. Adjustments ensure marital statuses like "Married/Separate" map correctly, and warnings are generated for null values during synchronization.
• Employee Matching - Removed secondary matching logic based on birthdate in the Sage 100 MatchOrCreateEmployee function. The system now relies exclusively on the 'Employee Identifier' for matching, improving accuracy and simplicity.

Sage 300

• Federal Tax Future Dates - Updated the system to prevent processing records with future effective dates in Sage 300, as the platform does not support them. A warning will not be generated when such records are encountered.
• Address Writer - Reviewed and updated the address writer logic to ensure compliance with Sage/HH2 requirements. Fixed issues where:
  • Address 1 was improperly deleted when Address 2 had a value.
  • Both addresses set to null resulted in no logs or feedback. Added warnings to clarify changes in these scenarios.