Please resume emailing the details of E-Verify outages. We are unable to see the details of the outages in the referenced "My Web Services" link and had relied on those emails to determine when outages would occur.
Why do the Web APIs require certification, but more importantly, why are we required to implement every method in the API rather than just the one want to use? We just want to submit new cases (EmpInitBPVerif) to avoid data entry issues, and then use the E-Verify Web Site for everything else. But we are told by CSC that we must implement the entire API, unlike any other API we have ever developed against in the past ...more »
Add the option to have a radio button that automatically populates today's date as the hire date.
This would speed up the process instead of doing the drop down menu for each column.
Since we can now retrieve various letters(PDF) from DHS rather than generate them ourselves using templates provided by DHS, would it be possible to add the ability to retrieve the Case Details once a case is closed. We have been instructed that we can no longer use the EmpGetCaseDetails method in the production environment, therefore, generating an accurate Case Details is more difficult.
When a new version of the Interface Control Agreement is published it would be helpful if change/revision bars were used to indicate what has changed between versions.
The new functionality is easy to spot, but clarification of older functionality is sometimes inserted and is not easily spotted within the document.
Since 2005 employer agents with an electronic I-9 product have been allowed to use electronic signatures on TNC documents. Having E-Verify provide the TNC document PDFs without electronic signatures is a problem since the employer agents software will now need to figure out how to apply the electronic signatures. Either the employer agent system should generate the TNC documents or E-Verify should generate the TNC documents ...more »
Add a field to the E-Verify Web Services interface to identify the end user that is processing the E-Verify case. Today, the only user identified is the individual who is the Employer Agent contact.
Add an E-Verify Web Services topic to E-Verify Listens. There are a number of enhancements that could improve this interface.
I think there should be a webservice to be able to Advance Cases on EVerify side for statuses that don't have Closure Codes like 'Case in Continuance' so we can always call EmpCloseCase to cleanup data.
Sometimes a case gets opened or was opened via web services but a confirmation with the case number was not received by the submitting agent's system. In this situation a second case is created making the original case an orphan. Since the agent's system may only allow one active case at a time, the orphaned case is never closed. Providing a list of orphaned cases to the agent would allow those cases to be investigated ...more »
For employer agents using web services, the "User Audit Report" cannot be run per company. The "User Audit Report" has more details/fields in the output than the "Quick Audit Report". Additionally, during a recent audit, the Notice of Inspection specifically requested the E-Verify "User Audit Report". This request is to run the User Audit Report by company for Employer Agents Using Web Services.
Would like WebServices to include adding/creating employer cases as well as managing the MOU process. This would automate the employer registration process for Employer Agents using Web Services, and reduce the need to manage that from the E-Verify portal.