🚀 What's New
Release Date: 08/30/2024
1. PSD Codes | Adjust integration service to fetch PSD code when saving an address
Improvement: AvionteClassic has been updated to populate a PSD code for talent addresses entered in BOLD when a school district code is selected.
Why? Prior to the improvement, PSD codes were not populating in back office when the talent's address with a school district code are entered in BOLD.
How does this impact you?
2. Update rapid! load cash screen to display only employees in the current supplier
Improvement: AvionteClassic has been improved to only display the employees in the current supplier when opening the rapid! load cash screen.
Why? Prior to this improvement, the screen was confusing to users. When processing payroll, only employees within the supplier are available to process. Making the load cash screen consistent with payroll will improve the user experience.
How does this impact you?
3. MFA | AUM | Unlink Bold Auth0 Accounts from AD When Email Changes
Improvement: AvionteClassic has been improved to unlink BOLD Auth0 accounts from AD when an email has been changed.
Why? Prior to the improvement, if an email was changed a user would no longer be able to login. A user would then need to submit a ticket to support and support would need to reach out to development. The improvement should eliminate the necessity for dev involvement.
How does this impact you?
4. Geocodes | Vertex decommissioned Geocodes removal in Classic
Improvement: The USPS updated a change in demographic boundaries replacing Connecticut's eight counties with nine planning regions. Geocodes had to be deactivated due to their placement within the new planning regions.
Why? Due to the change the USPS made our tax engine had to decommission geocodes.
How does this impact you?
DRMs Time Entry – Avionte Classic (zendesk.com)
- tbv_CheckForMissing WorkGeoCode
- tbv_CheckForMissing EmployeeAddress
DRMs Payroll – Avionte Classic (zendesk.com)
- pbv_CheckForMissingResident GeoCode
- pbv_CheckForMissingWork GeoCode
5. Time Entry | Add Pay Period option to field chooser to Sheet View
Improvement: AvionteClassic has been updated to include the pay period as an option under field chooser to add to the Time Entry Sheet View.
Why? Prior to the improvement, a user could only see the pay period for the transaction by going to card view. Having the pay period displayed on the sheet view allows a user to see if an employee has multiple pay periods within the same batch.
How does this impact you?
🚀 What's New
Release Date: 08/16/2024
1. Payroll | Update weighted overtime to include shift differential
Improvement: AvionteClassic has been improved to allow other pay codes to be included in calculating the regular rate of pay.
Why? Prior to the improvement, the calculation of the regular rate of pay only included Reg, OT, DT and non-discretionary bonuses.
How does this impact you?
2. Time Entry | Add Mark-up as an option on the field chooser under Sheet View
Improvement: AvionteClassic has added Markup Name as a field chooser in Time Entry | Sheet View.
Why? Prior to the improvement, a user was not able to add the Markup Name to the Time Entry Sheet View screen. To ensure they had the correct market up, they would have to look at the assignment.
How does this impact you?
3. rapid! Instant Pay | Update the rapid! Instant Pay screen to display 2 new fields
Improvement: AvionteClassic has been improved to add 2 new fields in the rapid! Instant Pay Load Cash screen. The 2 new fields are Check Date and Supplier.
Why? Prior to the improvement, the rapid! Instant Pay Load Cash screen did not provide a lot of information and was causing confusion for users. The additional fields will help users build confidence when funding employee's pay cards.
How does this impact you?
4. Statement Letter | Emails not sent if customer balance below 0
Improvement: AvionteClassic has been improved to email customers statement letters even if they have a credit balance.
Why? Prior to the improvement, if a customer's balance was less than 0, they were not receiving monthly automated statement letters.
How does this impact you?
🚀 What's New
Release Date: 08/02/2024
1. Accounting Period | Add severe DRM to check for Positive Pay file
Improvement: AvionteClassic has added a new DRM that will notify a user if a positive pay file is not created when closing the Accounting Period.
Why? Prior to the improvement, a user could close the accounting period without generating a positive pay file, which in turn ends up with banks rejecting live checks.
How does this impact you?
2. 1099 | Suite | New Standard Time Entry DRM
Improvement: AvionteClassic has been updated with a new standard time entry DRM. This DRM is to notify users if there is a mismatch between the W2 checkbox on the employee and the transaction.
Why? Prior to this improvement, a user would not have been notified if there was a discrepancy which could lead to incorrect payroll processing.
How does this impact you?
3. New Hire | Required updates for IN New Hire filing
Improvement: AvionteClassic has updated the IN New Hiring filing to match the new required fields.
Why? The State of Indiana changed the required information needed for new hire reporting. They now require 5 additional fields which are: Is Medical Insurance Available to an Employee?, Starting Pay Rate, Starting Pay/Salary Position, Job Title Position and SOC Code.
- Is Medical Insurance Available to Employee? Y/N Position 284
- Starting Pay Rate Position 561 H(hourly), A(annually), O (other)
- Starting Pay/Salary Position 562-571 No decimal, last two digits for cents. Right justify with leading zeros
- Job Title Position 572-631 Name or specific role within the organization
- SOC Code 632-637 Enter the first six digits of the SOC Code, no dashes
How does this impact you?
4. Classic | CopyToOrder when adding discounts to a customer
Improvement: Avionte Integrated clients have been improved to use the CopyToOrder function when adding discounts to a customer.
Why? Prior to the improvement this functionality did not work on integrated clients.
How does this impact you?
Comments
0 commentsPlease sign in to leave a comment.