November 2025

What is the improvement?

The SyncStream export integration has been renamed to Selerix to better reflect the actual service provider. Additionally, Selerix exports now run automatically on a scheduled basis, eliminating the need for manual file generation and transmission.

Why?

Previously, the integration was labeled as "SyncStream Export" in Admin Tools and Weekly Process, which caused confusion since the files are actually transmitted to Selerix for ACA compliance management. We've updated all references throughout the system to use the correct "Selerix" naming for clarity and consistency.

The manual export process required users to run exports from Weekly Process and handle file transmission via SFTP. By automating this process, we've removed the administrative burden and reduced the risk of missed or delayed file transmissions, ensuring timely and consistent data delivery to Selerix for ACA compliance reporting.

How does this impact you?

• Admin Tools > Import/Export/Mapping: The mapping group is now labeled "Selerix Export" instead of "SyncStream Export." All existing mappings remain intact and functional—only the display name has changed.
• Automated Export Schedule: Selerix Employee Census and Payroll exports now run automatically twice per week (Tuesday and Saturday evenings) and are transmitted directly to Selerix without user intervention.
• Weekly Process: Manual export functionality has been removed from the Export/Import tab in Weekly Process. Users no longer need to generate and transmit Selerix files manually.
• Data Validation: If required data is missing or incomplete during an automated export run, the file will still be transmitted to Selerix. Selerix will notify you if any data issues prevent proper processing. You can then correct the data in Avionte's Back Office, and the updated information will automatically be included in the next scheduled export run.
• DRM Warnings: Data Requirement Message (DRM) warnings for unmapped values (Employee Status, Rate of Pay Type, and Rehire Gap) will still appear on the Start Page to help ensure data accuracy. If mappings are not configured, the system will use default values when generating export files.

KB Article: Serelix | Automated File Transmission

What is the improvement?

Avionte Classic now includes a new configuration option that gives payroll processors control over whether partner benefit deductions and contributions are automatically flagged during payroll processing. Previously, these items were always flagged by default, requiring manual work to unflag them before running payroll. This new option eliminates that repetitive task, streamlining the payroll process and saving valuable time.

Key Updates:

A new configuration setting named FlagPartnerBenefitEnrollmentDeductionAndContribution is now available in Back Office. This configuration controls the automatic "Flag During Payroll" behavior for partner benefit enrollments and updates within the talent benefit enrollment and update processes.

The configuration includes the following specifications:

• Configuration Name: FlagPartnerBenefitEnrollmentDeductionAndContribution
• Type: Boolean (True/False)
• Default Value: True (preserves current behavior)
• Location: Back Office configuration options

How It Works:

When enabled (True), partner benefit deductions and contributions will automatically be flagged during payroll, maintaining the current behavior. When disabled (False), these items will not be automatically flagged, allowing payroll to run smoothly without the need for manual unflagging.

How does this impact you?

If you process payroll with partner benefit deductions and contributions, this new configuration option can eliminate the repetitive task of manually unflagging these items before each payroll run. By setting the configuration to False, payroll processors will save time and improve efficiency by not having to manually unflag partner benefit deductions and contributions, streamlining the payroll process.

Important Notes:

• The default value is True, preserving existing behavior for all current users
• Configuration changes only apply to new API calls; existing records are not modified
• This configuration is specific to partner benefit integration endpoints only

Configuration Instructions:

1. Navigate to Back Office configuration settings
2. Locate the FlagPartnerBenefitEnrollmentDeductionAndContribution option
3. Set to True to automatically flag partner benefit deductions/contributions during payroll (default, preserves current behavior)
4. Set to False to prevent automatic flagging and process payroll without manual unflagging intervention

What is the improvement?

Avionte Classic now includes automatic sequence number management for BIC (Benefits In a Card) benefit deductions created through the enrollment API. All BIC deductions for an employee are now automatically assigned to the same sequence number, ensuring that "All or Nothing" deduction logic applies to the total BIC benefit amount. This means either all BIC deductions are processed or none are processed if insufficient funds exist, preventing partial deduction scenarios.

Key Updates:

Enhanced logic has been added to the Add Talent Benefit Enrollment endpoint when called by the BIC partner. The endpoint now intelligently determines the appropriate sequence number for BIC deductions based on the employee's existing deduction configuration.

The sequence assignment includes the following logic:

• If employee has existing BIC deductions: The new BIC deduction is automatically assigned to the same sequence as the existing BIC deductions
  • If multiple BIC deductions exist with different sequences, the lowest sequence number is used
• If employee has no existing BIC deductions but has other deductions: The new BIC deduction is assigned to the next available sequence (max + 1)
• If employee has no existing deductions: The new BIC deduction is assigned to sequence 1
• Advance Bank deductions are excluded from sequence identification to prevent conflicts

Affected Endpoint:

• POST /v1/talent-benefit/enroll (Add Talent Benefit Enrollment) - When called by BIC partner

How It Works:

When the BIC partner creates a new benefit deduction through the enrollment API, the system automatically:

1. Checks if the employee has any existing BIC deductions (Benefits in a Card Transaction Type Group)
2. Assigns the appropriate sequence number based on the logic above
3. Groups all BIC deductions under the same sequence for "All or Nothing" processing

This ensures that during payroll processing, if insufficient funds are available to cover the total BIC deduction amount, none of the BIC deductions will be processed, preventing partial payments.

How does this impact you?

If you process payroll for employees with BIC benefit deductions, this enhancement ensures more reliable and predictable deduction processing:

• Prevents partial deductions: All BIC deductions are processed together as a single unit
• Automatic configuration: No manual sequence assignment needed for BIC deductions
• Improved accuracy: "All or Nothing" logic ensures employees either receive full BIC benefits or none at all

Example Scenarios:

Scenario 1: First BIC Deduction

• Employee has no existing deductions
• First BIC deduction is created via API
• System assigns sequence 1 to the new BIC deduction

Scenario 2: First BIC with Existing Non-BIC Deductions

• Employee has existing deductions in sequences 1, 2, and 3 (none are BIC)
• First BIC deduction is created via API
• System assigns sequence 4 (max + 1) to the new BIC deduction

Scenario 3: Additional BIC Deduction

• Employee already has a BIC deduction in sequence 4
• Additional BIC deduction is created via API
• System assigns sequence 4 to the new BIC deduction (same as existing)
• Both BIC deductions now share sequence 4

Scenario 4: "All or Nothing" Processing

• Employee has three BIC deductions in sequence 4: $50 + $50 + $50 = $150 total
• During payroll, only $120 is available for deductions
• Result: None of the three BIC deductions are processed (insufficient funds for full amount)

Important Notes:

• This logic applies only to BIC deductions created through the Add Talent Benefit Enrollment endpoint when called by the BIC partner
• Non-BIC deductions are not affected and retain their own sequence assignment logic
• Existing deductions created before this enhancement will not be automatically reassigned
• The Advance Bank deduction is excluded from sequence calculations
• Manual deduction entries in Back Office follow standard sequence rules