Submit a ticket

Avionté Suite Release Notes - June 13, 2019

Updated on Follow
0 out of 0 found this helpful

Features

Item Description
Background Check Billing:

The Employee > Background Check area now features billing functionality. As a background check is processed, users may now configure to which customer the background check will be billed, in which accounting period, and the amount of the background check. 

BGBilling2.png

 

Background Check Billing: Package Requirement on Order Level

Users are now able to select background check requirements on the order level which, in combination with an on-placement verification method DRM, prevents the placement of employees that have not fulfilled the order's background check requirements.

BGOrderRequirement2.png

Background Check Branch Permissions

The Background Check Request in the Start Page > Actions window now displays only those employees in a branch to which the active user has access. This change also affects the New Background Check Request dialog. Permission check is made against the user's available branches. The user does not have to select a branch in branch settings to view employee's from it.

Branches.png

 

Search Options & Export Data in Billing Details

With the addition of billing details to the Background Check Request window, additional search options have also been added to help facilitate an efficient billing process. Users can now perform searches with the following criteria:

BillingSearchFiedls.png

 

  • Bill Back
  • Bill to Customer
  • Accounting Period Date Range
  • Include orders without accounting period date

 

These billing details are now also included in the exported data

  • Changes made to the transaction via correction will not be displayed.
Asurint Results Document Single Sign-On (SSO)

Asurint users are now be able to configure single sign-on (SSO) to Asurint background check results documents increasing efficiency by removing the need for an additional login step during background check processing.

 

Visit the Asurint article in the Integrations - Background Check section for full details.

6293

In the Background Check Order Transaction, the employee name structure has been changed to Lastname, Firstname

Non-Resident Alien Taxation Support - US Withholding

Employers with workers classified as Non-Resident Aliens may now configure an employee's tax setup to indicate Non-Resident Alien US Withholding Type for payroll tax withholding calculation purposes. 

The US Withholding Type drop-down contains the following options:

  • Citizen/Resident
    • This is the default value and should be selected for United States Citizens or Residents in order to process payroll withholding at the standard rates.  
  • Nonresident Alien
    • This should be selected when employee indicates they are an NRA on their federal W-4.

NRA1.png

 

Visit the IRS Federal Income Tax Reporting and Withholding on Wages Paid to Aliens article for regulation details. 

San Antonio, TX Paid Sick Leave

Overview

Effective 8/1/2019 (delayed implementation for very small employers), a new sick plan has been created for the city of San Antonio, Texas

 

Highlights

Applies to businesses that do 80 hours of work (or more) in a year within San Antonio. 
Excludes independent contractors/non-employees

  • Accrual cap varies on employer size
  • Over 15 employees - 64 hour yearly accrual cap
  • 15 or fewer employees - 48 hour yearly accrual cap
  • Eligible employees earn 1 hour per 30 hours worked within the city
  • Delayed implementation for very small employers. This Article shall become effective on August 1, 2021 for employers having no more than five (5) employees at any time in the preceding twelve (12) months.

 

 

Details

Accrual Plan: Sick Leave_TX_San Antonio
Description: Sick Leave_TX_San Antonio_08012019_30_180
City: San Antonio 
State: TX
Effective Date: 8/1/2019
Hours to accrue 1 hour: 30
Days for Gap: 180
Days before can use: 0
Max Hours can use: 64
Pay Period Limit: 0 (unlimited)
Yearly Limit: 64
Allowed Carry Over: 64
Date Based On: Anniversary Date
Max Accrual Balance: 64
Initial Balance: 0
Unlimited Carryover: 0 (Allowed Carry Over value used)
Processing Method: pay_ProcessPayrollCheckAccrual_Sickleave

Visit the City of San Antonio Paid Sick Leave web page for ordinance details. 

https://www.sanantonio.gov/City-Attorney/Regulatory-Division/Paid-Sick-Leave

5482

Paid Family Leave Employer contributions reporting is now available for Washington, DC.

5237

A Paid Family Leave quarterly export is now available for Washington State. 

2210
A Paycard Payroll Processing DRM is now available in Admin Tools > System > Data Requirement Message.
Type: PaymentBatchVerification
Error Type: Warning
Message SP: pbv_CheckForPayCardBankAccountType
Message: Employee has a bank setup with account type {AccountType}. In order to include this in your ACH file you must first change the account type to Pay Card.
Active: Unchecked
When the above DRM is active, when processing a payroll batch (via Desktop Application > Payroll):
  • If an employee has bank type 'Savings' the DRM warning does not appear in the batch errors list.
  • If an employee has bank type 'Checking' the DRM warning does not appear in the batch errors list.
  • If an employee has bank type 'Pay Card' the DRM warning does not appear in the batch errors list.
  • If an employee has bank type 'Global Cash Card' the DRM warning appears in the batch errors list.
  • If an employee has bank type 'rapid! PayCard' the DRM warning appears in the batch errors list.
  • If an employee has bank type 'Money Network Card' the DRM warning appears in the batch errors list.
When the above DRM is NOT active, when processing a payroll batch (via Desktop Application > Payroll):
  • If an employee has bank type 'Global Cash Card' the DRM warning does not appear in the batch errors list.
  • If an employee has bank type 'rapid! PayCard' the DRM warning does not appear in the batch errors list.
  • If an employee has bank type 'Money Network Card' the DRM warning does not appear in the batch errors list.

Back to Top

 

 

June 13 Fixes

Item Description
6295

An arithmetic error in the PA sales tax has been corrected.

 

Previously, when processing a transaction that included pay but no bill, and the difference in pay and bill were nearly the same,  the system was forced to enter a value exceeding  the DECIMAL value for for the temp table resulting in an arithmetic overflow.

 

The temp table's limits were bumped to (20,8) to avoid having to convert the values back and forth in the calculation.

6262 Finance charges now calculate correctly when the Agent job runs at 11:00 p.m.
6260 Payroll processing no longer times out during a Vertex generation.
6190

An order's status is no longer unnecessarily updated during an order status process. The status is only updated when a change is made. 

6162 Web time for orders that do not contain a skill code now display in the employee portal as expected, even if the time is 'rejected' time.
6127 Performance timeouts are no longer experienced during an Employee Merge process.
6024 The Accounts Receivable > Get Invoices process has been optimized to improve the previous process time of 30-40 seconds per row. 
5930

A 'Bad Execution Plan' error is no longer generated when opening an existing payroll batch.

 

Previously, the process of opening an existing payroll batch via the search option had resulted in timeouts.

5798 A check for multiple supervisors on a transaction DRM now accounts for NULL values.
5742

Checks with a net-zero value no longer cause withholding to process incorrectly. 

5661

During the transaction creation process, updates to geocodes no longer cause issues due to a bad execution plan regarding site properties and overrides. 

5659 New York Withholding taxes are now importing into client environments as expected.
5628

The Mass Mail template drop-down menu is now available with consideration to user permissions. 

5585 Updating a recurring appointment in the calendar no longer creates a duplicate appointment linked to the current employee record.
5548

The employee merge message on the 'bad' employee now displays a message body.

5505 Standard Occupational Code migration now reliably inserts rows for clients.
5471 The Weekly Call and My Weekly Call counters now function based on the same calculation applying to their respective conditions. 
5350

Invalid entries are no longer able to be entered when entering daily time entry transactions.

 

Previously, after a prior update, invalid IDs were allowed to be entered into the Daily Time status for resulting in extra daily items added to the time clock punch process.

2176

When creating a new AR batch with an Invoice Line Item Type of 'invoice' and a payment is posted, followed by a second batch with an employee line item type and attempt to pay the same invoice an error stating that you cannot apply payments of both types to an invoice is now generated.

457

Calendar appointments are no longer duplicated when editing recurring appointments. 

Back to Top

 

 

May 23 Fix

Item Description
5342

 

OT and DT rates are no longer required on temporary and direct hire orders. In the event a data migration is needed from one order type to another (temp > dh), rate types will no longer inhibit the synchronization of the order data.
Previously, an option to change an order type in Connect was available for completed orders. Users were able to transition the order from 'temp' to 'direct hire', however, the events would not sync due to OT and DT rate restrictions. 
Reg, OT, and DT are not required rates for Temp Order and DH Fee is not required for DH Orders in the core application. The integration will add these rates if they're missing.

Back to Top

 

 

May 9 Features

Item Description

5450

Toggle visibility to Background Check Billing Columns based on feature flag

5311

Background check search setting allowing the exclusion of non-active records

 

Core application > Start Page > Background Check Request window > Search Options:
  • By default when this pane opens:
    • "Include non-active records" checkbox exists below the "Enter all or part..." help text (above text box)
    • "Include non-active records" checkbox is unchecked
    • "Include non-active records" checkbox exists above the drop-down multi-select list
    • "Include non-active records" checkbox is unchecked
    • Drop-down list contains:
      • All selected packages
      • All non-active packages 
    • In the Create by User section
    • In the Package section
  • I'm able limit the created by user select-able (drop-down) options to only active users, and add them to my search criteria
  • I'm able to search for all users (active and non-active), and add them to my search criteria 
  • I'm able limit the package select-able (drop-down) options to only active packages, and add them to my search criteria
  • I'm able to add non-active packages to my selected packages list, save my user search options, close the window, reopen the window, and the non-active packages are still:
    • Included in search results upon window load 
    • Included in my selected search criteria 

5245

Pay/Bill Combined Correction Process (beta)

When an invoice that has sales taxed based upon gross profit is corrected, the sales tax calculation could be off on the correcting invoice due to re-processing only the billing units in an invoice correction. The Pay/Bill Invoice Correction feature allows a user to correct both the paycheck and bill items associated with an invoice so that the gross profit can be accurately calculated.



Additionally, an option has been added allowing the user to choose if they want to create new transactions copied from the original transactions or only process the correction transactions.

4973

SOC Advanced Query

The May 2019 Avionté release makes the Get Missing SOC Data Advanced Query (AQ) available. This AQ generates a list of Job Titles missing an SOC.

 

The AQ currently searches for:

  • work performed in the last six months
  • work performed in Indiana, Louisiana, and Alaska

4787

 

 

Background Check Billing (beta)

BackgroundCheckInOrder.PNG

To increase efficiency in billing customers for employee background check orders through an integrated partner (Asurint or PeopleG2), users may now create a billable item for each order in the Background Check Request window.

 

The new functionality is available in the Core application in Order >  Background Check Requirement section.

4459

Once branch information starts coming from Connect, the Branch drop-down menu in the Core application will be disabled.
Since there is not a way to edit a branch from the Assignment screen in Connect, the Assignment branch in Core will remain editable in Core for now. 

4034

Once direct deposit is an option available in Connect and flowing to Core, the ability to add and edit bank functionality will be disabled in Core.  

3958

When a back office user creates a bill-only transaction for background checks, that transaction is now available for selection in the Billing Batch transaction selection.

3729

Background Check Requirement Notification (beta)

When placing talent to an order, a DRM now generates based on the qualification status the talent has following a background check.

 

DRM Defaults:

  • Active: No (unchecked)
  • Error Type: Warning
  • Message: Employee has not fulfilled {Background Check Package Name} order background check requirement.

 

 

Package: Address History

If an order requires a completed background check and the candidate user is attempting to place:

 

  1. has not had any background check orders created
    • =>The warning occurs: Employee has not fulfilled Address History order background check requirement.
  2. has had a background check order created, but not sent (Order Status: Open, Order Completed: 0)
    • =>The warning occurs: Employee has not fulfilled Address History order background check requirement.
  3. has had a background check sent, but is not yet completed (Order Status: Pending, Order Completed: 0)
    • =>The warning occurs: Employee has not fulfilled Address History order background check requirement.
  4. has had a background check sent, but is not yet completed (Order Status: Error, Order Completed: 0)
    • =>The warning occurs: Employee has not fulfilled Address History order background check requirement.
  5. has had a background check sent, but is not yet completed (Order Status: ActionRequired, Order Completed: 1)
    • =>The warning occurs: Employee has not fulfilled Address History order background check requirement.
  6. has had a background completed (Order Status: Completed, Order Completed: 1) for the same supplier as background check package selected on order (supplier ABC) and was completed 361 days
    • =>Employee can be placed
  7. has had a background completed (Order Status: Completed, Order Completed: 1) for a different supplier  (supplier XYZ) as background check package selected on order (supplier ABC) and was completed 361 days ago
    • =>The warning occurs: Employee has not fulfilled Address History order background check requirement.
  8. has had a background completed (Order Status: Completed, Order Completed: 1) for a different supplier  (supplier XYZ) as background check package selected on order (supplier ABC) and was completed today
    • =>Employee can be placed
  9. has had a background completed (Order Status: Completed, Order Completed: 1) for a different supplier  (supplier XYZ) as background check package selected on order (supplier ABC) and was completed 360 days ago
    • =>Employee can be placed

 

 

Package History: Criminal History 3 Year

If an order requires a completed background check, package Criminal History 3 Year (supplier ABC) which is only valid for 90 days and depending on the candidate supplier requires pass result or order completion, and the candidate user is attempting to place:

 

  1. has not had any background check orders created
    • =>The warning occurs: Employee has not fulfilled Criminal History 3 Year order background check requirement.
  2. has had a background check order created, but not sent (Order Status: Open, Order Completed: 0)
    • =>The warning occurs: Employee has not fulfilled Criminal History 3 Year order background check requirement.
  3. has had a background check sent, but is not yet completed (Order Status: Pending, Order Completed: 0)
    • =>The warning occurs: Employee has not fulfilled Criminal History 3 Year order background check requirement.
  4. has had a background check sent, but is not yet completed (Order Status: Error, Order Completed: 0)
    • =>The warning occurs: Employee has not fulfilled Criminal History 3 Year order background check requirement.
  5. has had a background check sent, but is not yet completed (Order Status: ActionRequired, Order Completed: 1)
    • =>The warning occurs: Employee has not fulfilled Criminal History 3 Year order background check requirement.
  6. has had a background completed (Order Status: Completed, Order Completed: 1) with date completed of today (repeat for 90 days ago)
    • =>The warning occurs: Employee has not fulfilled Criminal History 3 Year order background check requirement.
    • =>Employee can be placed
    • =>Employee can be placed
    • ​in ABC supplier with OrderResult value not "Verified"
    • in ABC supplier with OrderResult value "Verified"
    • in XYZ supplier
  7. has had a background completed (Order Status: Completed, Order Completed: 1) with date completed of 91 days ago
    • =>The warning occurs: Employee has not fulfilled Criminal History 3 Year order background check requirement.

 

3728

 

Background Check Package Requirement On Placement Verification (beta)

BackgroundRequirement.png

A company administrator is now able to associate a requirement with a background check package. This link is used to determine if an applicant has met the background check requirement and can be placed.

 

At the background check plugin package level, a config choice is available for and includes a 'number of days' option. Both of these values will be utilized by a DRM to determine if an employee is eligible for placement on an order.

 

A group of fields is now available in the Background Check Package area.
  • A "Valid for Number of Days" field has been added to the Background Check Package configuration
    • This field will take a positive int value (int > 0)
    • This field will be used to determine if the background check order was completed within valid date range - when no value is entered then the background check package does not expire
    • Non-required 

  • A "Required for Placement" field with options "Completed" and "Pass" has been added to the Background Check Package configuration
    • 0 = Complete 
    • 1 = Pass 
    • This radio group will input into single BIT field in suite DB 
    • Field required if requirement value is entered
    • If provider is NOT Asurint this field is non-editable and Completed option is selected

  • Pass Result Value 
    • Text value of background check result pass score 
    • Value is required if requirement (config choice) is selected AND Required For Placement selected value is 1 (Pass)
    • If provider is NOT Asurint, this field is not displayed

 

3397

3257

2896

2889

 

Background Check Enhancements (beta)

  • Users may now choose to include or exclude non-active users and packages when selecting their background check order search criteria.
  • Background check grid columns have been updated and users may now click the employee name button to directly navigate to employee record from the background check order grid.
  • The Search Options > Result list is now configurable in a client database. Any value inserted into the BackgroundCheckRequestResult table will be available to select.

 Back to Top

 


Have more questions? Submit a request

0 Comments


This space is for article feedback only. To make a request of the Avionté Support Team, please submit a ticket to https://support.avionte.com.