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. 

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.

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.

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:

• 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 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.

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

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

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

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

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

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.

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

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.

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

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

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

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

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.

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.

Calendar appointments are no longer duplicated when editing recurring appointments. 

5450

5311

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

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)

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

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)

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.

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.