Mastering the E-Verify Web Services Interface Control Document
Why E-Verify Web Services Is a Game-Changer for HR Teams
E-verify web services is a technical access method that lets employers connect directly to the E-Verify system using custom software, instead of logging into a web browser manually every time.
Here’s a quick breakdown of what that means in practice:
- What it is: A server-to-server integration between your HR software and the E-Verify government database
- Who uses it: Employers, employer agents, and federal contractors who need to process high volumes of new hires
- How it works: Your software sends employee data automatically using SOAP or REST protocols, guided by an Interface Control Agreement (ICA)
- Why it matters: It eliminates manual data entry, reduces errors, and scales with your hiring volume
If you’re an HR manager juggling onboarding for dozens of new employees at once, manually entering each case into E-Verify’s browser portal gets old fast. It’s repetitive, time-consuming, and leaves too much room for human error.
That’s exactly the problem E-Verify Web Services was built to solve.
Rather than logging in and typing data by hand, your existing HR or I-9 software talks directly to E-Verify’s system. The data flows automatically. Cases get created faster. And your team spends less time on repetitive admin work.
The scale of adoption says it all. In fiscal year 2017, Web Services users created roughly 18.9 million E-Verify cases, accounting for about 52% of all cases that year. More than half of all verifications were handled without anyone touching a browser.
But getting there requires more than just plugging in an API. There’s an enrollment process, an Interface Control Agreement to review, software to develop and certify, and specific compliance rules to follow. This guide walks you through all of it.
Key terms for e verify web services:
Understanding Web Services vs. Browser Access
When you decide to use E-Verify, you generally have two paths to choose from. The first is the standard web browser access. This is the “manual” way. You log in to the USCIS website, type in the information from the employee’s Form I-9, and wait for a response. It works perfectly fine for small businesses hiring a few people a year, but it doesn’t scale well.
The second path is e verify web services. This method allows your company to use customized software to talk directly to the government’s computers. Think of it like a dedicated digital highway between your HR office and the Department of Homeland Security (DHS).
The biggest difference here is integration. With web services, you can extract data directly from your electronic Form I-9 system or your Applicant Tracking System (ATS). This means no more double-typing names, birthdates, or Social Security numbers. It reduces the risk of typos that lead to frustrating Tentative Nonconfirmations (TNCs).
For more details on how these systems compare, you can check out our internal guide on e-verify-web-services. While the browser method is free and requires no technical setup, web services offer a level of professional automation that high-growth companies find indispensable.
The Technical Roadmap: From MOU to E-Verify Web Services Certification
Getting started with e verify web services isn’t as simple as flipping a switch. It’s a journey that requires cooperation between your HR team and your IT developers (or a third-party software provider).
First, you must enroll in E-Verify and select the “Web Services” access method. During this process, you will sign a Memorandum of Understanding (MOU). This is a legal agreement between your company, DHS, and the Social Security Administration (SSA). It outlines exactly what you are allowed to do and what your responsibilities are.
Once the MOU is signed, the real technical work begins. You will receive the Interface Control Agreement (ICA). This document is the “rulebook” for your developers. It contains the technical specifications needed to build a software interface that E-Verify will accept.
Before you can go live and start checking real employees, your software must pass a certification test. This isn’t a test of your company, but rather a test of the software’s ability to send and receive data correctly. You’ll work through a series of test cases in a “sandbox” environment to prove your system handles every possible scenario, from immediate authorizations to complex nonconfirmations.
You can find more official details on the Web Services | E-Verify page. You typically have six months from the time you sign your MOU to get your software developed and certified.
Supported Protocols for E-Verify Web Services
If you’re talking to your dev team, they’re going to ask about protocols. E-Verify currently supports both SOAP (Simple Object Access Protocol) and REST (Representational State Transfer).
SOAP has been the traditional standard for E-Verify for years, utilizing WSDL (Web Services Description Language) files to define the communication. However, newer versions of the interface also support RESTful APIs, which many modern developers prefer for their flexibility and ease of use. Regardless of the protocol, the goal is the same: secure, server-to-server communication that keeps employee data safe while moving it quickly.
Training Requirements for E-Verify Web Services Users
Don’t let the technical talk fool you, the human element is still vital. Training for e verify web services users is actually a bit different than for those using the standard web browser.
While browser users take an online tutorial and a mastery test on the USCIS site, web services users are often trained using materials provided by their software vendor or their own internal company manuals.
We recommend that all users stay up to date through official webinars. These sessions are often eligible for professional development credits through organizations like SHRM and HRCI. It’s a great way to stay compliant while earning credits for your HR certification.
Compliance Rules and User Responsibilities
Using a high-tech automated system doesn’t exempt you from the basic rules of employment eligibility. In fact, because you’re handling data via software, the government expects you to be even more diligent about security.
The most important rule remains the “3-day rule.” You must create an E-Verify case no later than the third business day after the employee starts work for pay. You also cannot create a case before the employee has accepted a job offer and completed Section 1 of the Form I-9.
When using e verify web services, you are responsible for:
- Protecting PII: Personally Identifiable Information (PII) like Social Security numbers must be encrypted and handled with extreme care.
- Reporting Breaches: If you suspect a data breach or if a password is compromised, you must notify DHS immediately.
- Displaying Posters: Even if you don’t use the browser, you must still physically display the “Notice of E-Verify Participation” and the “Right to Work” posters in a place where prospective employees can see them.
If you are a federal contractor with a FAR (Federal Acquisition Regulation) clause in your contract, your responsibilities increase. You must ensure your software is updated to handle the specific requirements for federal contractors, such as verifying existing employees assigned to the contract. For a deep dive into these rules, the Supplemental Guide For Web Services Users is an essential read.
Handling Tentative Nonconfirmations and System Updates
One of the most sensitive parts of the E-Verify process is the Tentative Nonconfirmation (TNC). This happens when the information entered doesn’t immediately match government records.
In a web services environment, your software must be designed to display the TNC notice to the employee privately. You cannot take “adverse action” against an employee, like firing them or delaying training, just because they received a TNC. They have the right to contest the finding, and your software must be able to track that process through to a final result.
Maintenance is another big responsibility. E-Verify isn’t a “set it and forget it” system. The government frequently updates the Interface Control Document (ICD) to add new features or security patches.
When a new version is released, you generally have a six-month window to update your software. If you miss this deadline, your access to the system can be terminated. This is why having a dedicated partner or a reliable software vendor is so important, you need someone watching for those update notices so your hiring process doesn’t come to a screeching halt.
Integrating E-Verify Web Services with Your HR Ecosystem
The real magic of e verify web services happens when it’s fully integrated into your existing HR ecosystem. Imagine a world where a new hire completes their digital onboarding paperwork, and the moment they hit “submit,” the data is validated, an I-9 is generated, and an E-Verify case is created in the background.
By using RESTful API capabilities, your company can connect E-Verify to:
- HRIS/HCM Systems: Keep your employee records and verification status in one central place.
- Background Check Platforms: Many companies use third-party providers to handle both criminal checks and E-Verify at the same time.
- Single Sign-On (SSO): Your staff can access the verification tools using their standard company login, improving security and ease of use.
This seamless data flow provides real-time status updates. Instead of checking a separate portal, your recruiters can see a “Work Authorized” green checkmark directly inside their candidate dashboard. It makes the entire hiring pipeline feel like one cohesive experience rather than a series of disjointed chores.
Frequently Asked Questions about Web Services
Who is eligible to enroll in Web Services?
Almost any employer enrolled in E-Verify can choose the Web Services access method. This includes direct employers, E-Verify employer agents who perform verifications for other companies, and federal contractors. Software developers who are building products for these groups also interact heavily with web services during the testing and certification phases.
What happens if software updates are not completed on time?
If you fail to update your software within the six-month window following a new ICA release, you risk losing access to the production environment. This means you won’t be able to create new cases, which puts you out of compliance with federal law. In extreme cases, the government can terminate your MOU entirely.
How does the case creation workflow differ?
In the browser method, you are the data entry clerk. In the web services method, your software is the clerk. The software extracts data from an electronic Form I-9, packages it into a secure digital message, and sends it server-to-server. This allows for batch processing, where you can submit multiple cases at once, drastically speeding up the workflow for large hiring events.
Streamlining Your Compliance Journey
At Valley All States Employer Service, we know that technical jargon like “SOAP protocols” and “Interface Control Agreements” can sound a bit overwhelming. You’re in the business of hiring great people and growing your company, not managing government API connections.
That’s where we come in. We provide expert, impartial, and efficient E-Verify processing that takes the administrative burden off your shoulders. Whether you’re looking to integrate e verify web services into your current workflow or you need a reliable partner to handle the verifications for you, we ensure your workforce eligibility is handled with precision.
By minimizing errors and staying ahead of the six-month update windows, we help you maintain a legal workforce without the headaches of manual data entry or technical troubleshooting.