Why is Avionté making an update to the E-Verify integrations?
E-verify is mandating important system updates that impact the E-Verify integrations across BOLD, AERO, and CLASSIC. According to current government deadlines, all vendors are expected to comply and use the new E-Verify solution starting on March 31, 2022 in order to maintain E-Verify services for clients.
What changed as part of the v31 update?
| Category |
E-Verify Change |
| Duplicate Case Check |
The duplicate case lookback period has been extended from 30 days to 365 days. |
|
Talent can no longer have more than one open E-Verify case at any time. |
|
|
If a talent has existing closed cases within the 365 day lookback period, the user is required to provide a Duplicate Continue Reason in order to create a new E-Verify case for the talent. |
|
| Case Delay Reason |
Awaiting response on case created with incorrect information is a new option that users will be able to select as a reason for the delay on a case. |
| Further Action Notice |
For talent with E-Verify cases in a Tentative Nonconfirmation (TNC) state, users will now be required to download the Further Action Notice before being able to refer the case. |
| Manual Case Closure |
Users will now have the ability to manually close an E-Verify case that is in a Scan and Upload status. |
How do the v31 updates translate to the E-Verify integration within Avionté?
| Category |
E-Verify Change |
Avionté Change |
| Duplicate Case Check |
The duplicate case lookback period has been extended from 30 days to 365 days. |
When a user attempts to create an E-Verify case from Avionté, the user will now see a list of duplicate cases for the talent that have been created within the last 365 days. |
|
Talent can no longer have more than one open E-Verify case at any time. |
When a user attempts to create an E-Verify case from Avionté and the talent has an open E-Verify case that was created within the last 365 days, the user will be presented with the open case list and be required to close the open case before being able to create a new one. |
|
|
If a talent has existing closed cases within the 365 day lookback period, the user is required to provide a Duplicate Continue Reason in order to create a new E-Verify case for the talent. |
When a user attempts to create an E-Verify case from Avionté and the talent has a closed E-Verify case, the user will be presented with the open case list and be required to close the open case before being able to create a new one. |
|
| Case Delay Reason |
Awaiting response on case created with incorrect information is a new option that users will be able to select as a reason for the delay on a case. |
When an E-Verify case is being created 3 or more days past the talent's first day of employment, the user will be required to provide a reason for the delay. A new delay option the user can select is, "Awaiting response on case created with incorrect information". |
| Further Action Notice |
For talent with an E-Verify cases in a TNC state, users will now be required to download the Further Action Notice before being able to refer the case. |
When an E-Verify case is in a Tentative Non-Confirmation status and a user attempts to refer the case without first downloading the Further Action Notice, the user will be stopped and prompted to download the FAN before being able to proceed. |
| Manual Case Closure |
Users will now have the ability to manually close an E-Verify case that is in a Scan and Upload status. |
When an E-Verify case is in a Scan and Upload status, a user can decide to not proceed with the case and close the case directly from Avionté. |
What Avionté platforms will be updated to v31?
All - BOLD, CLASSIC, & AERO.
When will the v31 update be delivered?
E-Verify's original deadline was 3/31/22 but Avionté has received a deadline extension from the U.S. Department of Homeland Security ("DHS" or the "Agency") to 5/31/22.
Why has Avionté received a deadline extension?
Avionté has completed the development to meet the system updates and we’ve been working through E-Verify’s mandatory testing process. We have run into issues with the testing process that require assistance from E-Verify, and we have been unsuccessful in receiving a timely response from our contacts within the Agency.
As a proactive measure, we have taken the step to formally request a deadline extension for implementation, which DHS has approved via written confirmation extending our deadline to May 31, 2022.
Do E-Verify users need to do anything in order to start using v31?
Avionté has been working directly with E-Verify throughout the implementation of the v31 update. As part of the implementation and deployment process, Avionté is coordinating with E-Verify, the migration of client accounts from v30 to v31.
Once the v31 update is deployed by Avionté, all client accounts using the integration for the deployed platform, will also be updated to v31. At which point, E-Verify users should be able to login to Avionté and use the integration per their usual process.
What happens with E-Verify cases that were opened before the v31 upgrade?
If you have cases that were opened before the v31 upgrade that are still open, the cases will continue to be processed through the v31 integration. There will be no need to close out those cases and recreate them through the v31 integration.
3rd party link Disclaimer: These links are being provided as a convenience and for informational purposes only; they do not constitute an endorsement or an approval by [The author] of any of the products, services or opinions of the corporation or organization or individual. [The author] bears no responsibility for the accuracy, legality or content of the external site or for that of subsequent links. Contact the external site for answers to questions regarding its content.
Comments
0 commentsPlease sign in to leave a comment.