All new hires working in the United States and hired after November 6, 1986, must complete form I-9 to document employment authorization. Accurate and timely completion of form I-9 is a staple of the onboarding process. The I-9 and E-Verify integrated solution enables employers to initiate the I-9 process and oversee the action items related to I-9 and E-Verify all from within the Partner’s interface.

Workflow diagram

I-9 Workflow

E-Verify Workflow

Process Flow

  1. The employer or new hire will trigger the I-9 process and the Partner will request a session from the Guardian API.
  2. The Guardian API will return a session token to the Partner.
  3. The Partner will POST the new employee’s information to the Guardian API.
  4. Guardian API will respond with a URL that the employee will use to complete Section 1 of the I-9.
  5. The Partner will present the I-9 URL to new hire and the new hire will complete Section 1 within the Guardian User Interface.
  6. After the new hire completes Section 1, the Guardian API will PATCH next steps to the Partner. The Partner can display the details of the PATCH within the applicable user interface, which could include I-9 Status (i9Status), I-9 Next Step (i9NextStep), I-9 Next Step Due Date (i9NextStepDueDate), and I-9 URL (i9Url).
  7. The HR User will click the I-9 URL from the Partner site and complete Section 2 of the I-9 within the Guardian User Interface.
  8. When applicable, the I-9 data will be submitted to E-Verify after the HR User completes Section 2 of the I-9. When E-Verify is activated the Guardian API will send results back to the Partner via PATCH. The parameters used for this portion of the integrated workflow include E-Verify Status Code (eVerifyStatusCode), E-Verify Resolution Code (eVerifyResolutionCode), E-Verify Status Message (eVerifyStatusMessage), E-Verify Resolution Message (eVerifyResolutionMessage), E-Verify Next Step (eVerifyNextStep), E-Verify Next Step Due Date (eVerifyNextStepDueDate), and E-Verify URL (eVerifyUrl).
  9. The Guardian API will return I-9 PATCH status requests and E-Verify PATCH status requests to the Partner until there are no further actions.

 

Example calls


# 2. RESPONSE example
# Guardian -> Partner
# Response-Code: 202

{
    "access_token": "360c0290ca3a5fa90d7e11b67659ff3adeca8bc8",
    "token_type": "Bearer",
    "expires_in": 86399,
    "refresh_token": "30166263ca11d2ee34aa70b2aef779ce8d259feb",
    "scope": "read"
}

# 3. POST example
# Partner -> Guardian
# POST /v1/partners/i9s/section1
# Content-Type: application/json

curl -v https://sandbox.perfectcompliance.com/v1/partners/i9s/section1 \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer <Access-Token>' \
-d '{
        "firstName": "test",
        "lastName": "Smith",
        "emailAddress": "test@email.com",
        "startDate": "2015-01-01",
        "locationId": 56789,
        "onboardingType": "on-site",
        "integrationCandidateId": "A12345"
        "employeeReturnUrl": "https://partnersite.com/person/12345/home"
    }'

# 4. RESPONSE example
# Guardian -> Partner
# Response-Code: 202

{
    "i9Section1Link": "https://sandbox.perfectcompliance.com/i9/section1/somerandomeuuid",
    "id": 12345,
    "links": [
        {
            "rel": "self",
            "title": "initiate i9",
            "method": "POST",
            "url": "https: //sandbox.perfectcompliance.com/v1/partner/i9section1"
        }
    ]
}


# 6. i9 PATCH example
# Guardian -> Partner
{
    "i9Status": "Section 1 Completed",
    "i9NextStep": "Sign Section 2 (Verifier)",
    "i9NextStepDueDate": "2015-06-26",
    "i9Url": "https://sandbox.perfectcompliance.com/link-to-related-section"
}


# 8. E-verify PATCH example
# Guardian -> Partner
{
    "eVerifyStatusCode": "CRCV",
    "eVerifyResolutionCode": "EELIG",
    "eVerifyStatusMessage": "The employee continues to work for the employer after receiving an Employment Authorized result",
    "eVerifyNextStep": "No Further Action Required",
    "eVerifyNextStepDueDate": "None",
    "eVerifyUrl": "https://sandbox.perfectcompliance.com/link-to-related-section"
}