INDUSTRY NEWS
E-Verify Announces Interface Control Agreement (ICA) Modifications
As of March 31, 2022, all companies must utilize Representational State Transfer (REST) communication protocols between E-Verify and internal web-based service software.
In a notification publicly released on Sept. 30, 2021, the U.S. Citizenship and Immigration Services (USCIS) stated that Simple Object Access Protocol (SOAP) will no longer be a supported communication protocol per ICA Version 31 (v31). Entities utilizing SOAP must convert to REST by the end of March, 2022. Companies failing to complete this conversion by then risk the possibility of losing web service to E-Verify.
Companies were initially notified of this pending change back in May, 2021. At that time, all users engaging SOAP protocols were encouraged to begin transitioning to REST. It is important to note that both the software integration and approval to use the E-Verify v31 API in the production environment by means of acceptance testing must be completed by no later than March 31, 2022.
As the industry standard, users will benefit by utilizing REST protocols in that it offers a wider variety of data formats, better support for browser clients, superior performance and a decrease in ICA adoption times for new E-Verify features/releases. E-Verify drafted and posted an improvement/benefits chart to their site, as depicted below.
|
Improvement Description |
Benefit to Users |
|---|---|
| Extended the duplicate case lookback period from 30 to 365 calendar days | Helps web services users avoid creating an unintentional duplicate case |
| Restricted users from creating a duplicate case when another case for the same employee is open | Ensures web services users follow the correct procedures for managing open duplicate cases |
| Increased the number of results returned during the duplicate case check. The default was 100 cases per page, with the option to return a minimum of 1 and a maximum of 120 per page | Allows web services users to view all duplicate cases |
| Added a new case delay reason "Awaiting response on a case created with incorrect information" | Reduces data entry burden for users |
| Provided capability to search cases by using a combination of multiple case fields at once | Provides web services users with a more robust case search capability |
| Provided capability to close a case at the Scan and Upload stage of the case creation process | Reduces the burden on the user by streamlining the process to close a case |
| Required users to download the Further Action Notice before referring a case | Ensures web services users follow the correct procedures when processing a Tentative Nonconfirmation |
Business Information Group will be prepared by March 31, 2022 to support this pending change. In the interim, please reach out to your account management team with any questions or concerns.
Posted: November 19, 2021
All Rights Reserved © 2021 Business Information Group, Inc.
This document and/or presentation is provided as a service to our customers. Its contents are designed solely for informational purposes, and should not be inferred or understood as legal advice or binding case law, nor shared with any third parties. Persons in need of legal assistance should seek the advice of competent legal counsel. Although care has been taken in preparation of these materials, we cannot guarantee the accuracy, currency or completeness of the information contained within it. Anyone using this information does so at his or her own risk.