AviontéCLASSIC Back Office Release Notes - April 2025

🚀 What's New

Release Date: 04/25/2025

1. State Field Validation DRM During Time Entry

Improvement

We have implemented a new Data Requirement Message (DRM) warning that identifies when a talent's state field is empty or invalid during time entry. This enhancement helps you catch missing or incorrect address data early in your workflow, improving data quality and reducing downstream issues.

  • tbv_CheckForValidResidentStateCode



Key Updates

  • Added a new warning DRM that triggers when a talent's state field is empty, NULL, or invalid
  • The DRM activates specifically during the time entry process
  • This validation is enabled by default upon release
  • Users have the ability to deactivate this warning if needed for their workflow



How Does This Impact You?

  • Time Entry Process: You'll now receive a warning notification when attempting to enter time for a talent with missing or invalid state information in their address
  • Data Quality: This feature helps ensure complete address information before time entries are processed, reducing errors in payroll and billing
  • User Control: While active by default, your team can deactivate this warning through standard DRM management if it doesn't align with your specific business processes
  • Early Detection: By identifying missing state data during time entry, you can address information gaps before they cause issues in downstream processes

This update focuses on improving data quality while maintaining workflow flexibility, resulting in more accurate talent information throughout your system.


KB Article - DRMs Time Entry

 

2. Payroll Process DRM For Bank Flag Validation

Improvement

We have implemented a new Data Requirement Message (DRM) warning that identifies mismatches between bank flags and payroll batch types. This enhancement helps you catch incorrect combinations of direct deposits and live checks early in your workflow, improving payroll accuracy and reducing processing errors.

  • ppv_CheckPaymentBankType

Key Updates

  • Added a new warning DRM that triggers when there's a mismatch between bank flags and payroll batch types
  • DRM activates when Generate ACH flag is set but payroll batch contains live checks
  • DRM also activates when Generate Pos Pay flag is set but payroll batch contains direct deposits
  • This validation is inactive by default upon release
  • Users have the ability to activate this warning based on their workflow needs



How Does This Impact You?

  • Payroll Processing: You'll receive a warning notification when attempting to process payroll batches with incompatible bank flag and payment type combinations
  • Error Prevention: This feature helps ensure proper separation of direct deposit and live check batches before they're processed
  • User Control: While inactive by default, your team can activate this warning through standard DRM management to align with your specific payroll processes
  • Early Detection: By identifying these mismatches during payroll processing, you can address potential errors before they cause payment issues

This update focuses on improving payroll accuracy while maintaining workflow flexibility, resulting in more reliable payment processing throughout your system.


KB Article - DRMs Payroll

 

🚀 What's New

Release Date: 04/11/2025

1. Credit Card Fields Removal

Improvement

We have enhanced our platform's security posture and streamlined the user interface by removing unnecessary credit card-related fields and functionalities across multiple areas of the system. This change directly addresses findings from our recent PCI Readiness Audit and eliminates potential security risks while simplifying workflows for users.

Key Updates

  • Removed credit card management functionality from "Customer | BackOffice Setup | Credit" section
  • Eliminated credit card field from the order form/checkout process
  • Removed Credit Card Fee field from the Time Entry Card View Detail screen
  • Discontinued ability to add new credit cards or maintain credit card aliases



How Does This Impact You?

  • Back Office and Classic Platform Users: You will no longer see options related to credit card management in the system. This includes the removal of fields for entering, viewing, or managing credit card information across multiple screens.
  • Order Processing: The order form has been simplified with the removal of credit card entry fields, streamlining the ordering experience.
  • Time Entry Workflow: The Time Entry Card View Detail screen no longer displays the Credit Card Fee field.
  • Security and Compliance: These changes strengthen our PCI compliance and reduce security risks by removing legacy fields that stored credit card information but were minimally used.

These updates focus on enhancing security while removing rarely used functionality, resulting in a more streamlined and compliant platform.

 

2. Removal of "Add New" Button from Counter Section

Improvement

The "Add New" button has been removed from the Counter section under Admin Tools, preventing users from attempting to configure counters through this interface.

Key Updates

  • Removed the "Add New" button specifically from the Counter area within Admin Tools
  • This change applies to both Back Office and Classic platforms

How Does This Impact You?

  • You will no longer see the "Add New" button when accessing the Counter section
  • This change eliminates the ability to incorrectly configure counters through this interface
  • No action is required from users; this is a preventative interface improvement

KB Article - Use and Configure Counters

 

3. ADP Integration - Tax Reporting Enhancement

Improvement

We've deployed a critical fix to ensure all salary hours are correctly included in the quarterly tax reporting files sent to ADP. This enhancement improves data accuracy and compliance with tax reporting requirements.

Key Improvements

  • Complete Salary Hours Inclusion: Fixed an issue where salary hours for certain positions were being excluded from the ADP tax reporting file
  • Enhanced Reporting Accuracy: Ensures all eligible salary hours are properly captured and reported
  • Improved Compliance: Maintains accurate data transmission to ADP for tax reporting purposes

How Does This Impact You?

If you work with salary compensation or payroll processing, you'll notice more comprehensive data in your ADP tax reporting files. Specifically:

  • All eligible salary hours are now correctly captured in the quarterly reports
  • No manual adjustments are needed to account for previously missing data
  • Tax reporting workflows are more reliable with this enhanced data integrity

Articles in this section

Was this article helpful?
0 out of 0 found this helpful
Share

Comments

0 comments

Please sign in to leave a comment.