EOR Hiring Eligibility

The following schema outlines three categories of signals related to EOR (Employer of Record) hiring eligibility. Each signal indicates a different status of the onboarding process for a company, guiding the necessary actions.

Signal Categories

• Green Level Signals

  Indicate that all checks have been successfully completed, allowing the onboarding process to proceed without further intervention.

• Yellow Level Signals

  Indicate that action is required from the employer in order to unblock the onboarding process.

• Red Level Signals

  Indicate that the checks have failed, and no further steps can be taken to remediate the situation.

Pass KYB checks in sandbox

The Pass KYB feature allows you to bypass KYB (Know Your Business) and credit risk checks for a company without requiring the intervention of a Remote admin.

ℹ️ This endpoint is only available for testing in the sandbox environment. If used in production, it will return a 404 Not Found response.

To use the pass KYB endpoint, you need to have:

1. Client credentials for sandbox: This is the recommended approach. For this flow, you will need to create a company in sandbox using client credentials.
2. Company and its refresh token: If you already have a company created in sandbox, you can use its refresh token to bypass verification.

To get API access token, follow these steps. This will create a token starting with ra_test which implies that it can only be used in sandbox.

To bypass KYB and credit risk checks, call the Pass KYB endpoint in sandbox by providing the company_id and a valid access token to authenticate the request.

curl --request POST \
     --url https://gateway.remote-sandbox.com/v1/sandbox/companies/5bdc2cb9-6bda-4cf7-bc6e-0b122791e52a/bypass-eligibility-checks \
     --header 'accept: application/json' \
     --header 'authorization: Bearer ra_test_30c8a4ac9f4840558a8df4b76cc5f828_b2f5eaa2109b49dab0ed8768a33fc1122'

On success, you will get a "status": "ok" response which indicates the required checks have been bypassed.

Event Descriptions

• company.eor_hiring.verification_completed: Triggered when the verification for the company is completed, indicating no further actions are required.
• employment.eor_hiring.proof_of_payment_accepted: Triggered when proof of payment is submitted and accepted for an invoice, allowing the employer to proceed with onboarding.
• company.eor_hiring.reserve_payment_requested: Triggered when a reserve payment is required to proceed with the hiring of any employee for the company.
• company.eor_hiring.additional_information_required: Triggered when additional documents or information are needed to expedite the hiring checks.
• employment.eor_hiring.invoice_created: Triggered when an invoice is created, requiring payment before the employee's onboarding can be completed.
• company.activated: Triggered when a company is activated.
• company.archived: Triggered when checks have failed, resulting in the company being archived with no further action possible.

Possible scenarios:

The diagram below visually represents possible scenarios. Circles represent user actions, while rectangles represent signals generated by the system.

Scenario: No Further Action Required

In this case, the company is created and successfully verified. Since no additional action is needed, the employer is able to proceed with employee onboarding.

Scenario: Additional Steps Required

In this case, the company needs to make a deposit to proceed with onboarding. Additionally, the company must provide documents to verify its status. Once the employer provides the necessary information, creates the employment, and submits proof of payment, onboarding can proceed after the payment is validated.