## Set up Business Onboarding in the RiskOS™ Dashboard

### Before you start  
Make sure you have the following:

Access to the RiskOS™ Dashboard with the **Business Onboarding** solution enabled.

- Your account owner or administrator can enable this for you. If you're unsure who to contact, [reach out to support](mailto:support@socure.com) for assistance.

A basic understanding of RiskOS™ workflows and components.

- If this is your first time working with workflows, review the [Workflow overview](https://help.socure.com/riskos/docs/workflow-overview) to understand inputs, enrichments, routing logic, and decisions.

## How it works  
Business Onboarding evaluates both the **business entity** and its **associated individuals** in a single workflow. It applies identity verification, fraud detection, and compliance checks to determine whether a business can be safely onboarded.

At a high level, Business Onboarding:

- Validates the existence and legitimacy of the business
- Screens the business for sanctions, adverse media, and high-risk indicators
- Identifies and verifies associated individuals (UBOs, owners, or controllers)
- Applies fraud and risk scoring across business and individual signals
- Produces a final decision with reason codes and auditability

Final outcomes include:

- **Accept**
- **Manual Review**
- **Reject**

### How Business Onboarding fits into a workflow  
In RiskOS™, workflows are built by connecting reusable components. Business Onboarding is delivered as a **preconfigured use-case workflow** composed of multiple enrichments, conditions, and decisions.

Once triggered, the workflow orchestrates all required checks and returns a single decision outcome.

### Execution flow in RiskOS™  
Business Onboarding runs synchronously as part of a RiskOS™ workflow, with conditional branching based on business structure and risk signals.

1. ### Data collection  
   Collect the business information (business name, address, tax ID) and associated individuals information (first/last name, SSN, address, DOB, and email) and Digital Intelligence (DI) session token as the minimal input needed to begin the flow.

2. ### Business Onboarding API call to RiskOS™  
   RiskOS™ receives the input data and triggers the Business Onboarding API to retrieve and enrich identity information.

3. ### Risk scoring  
   Device intelligence, digital signals, and consortium data are evaluated to calculate identity and fraud risk.

4. ### Allow | Deny List checks  
   Compare input data to specific lists to automatically reject known risky actors.

5. ### Look for sole proprietorships  
   Evaluate specific signals to determine if the business in question is a sole proprietorship, and send it directly to the UBO/Individual Verification flow.

6. ### Call KYB partner API  
   If the business is not a sole proprietorship, then initiate a call to one or more of RiskOS™' KYB Partner integrations, passing the business and individual data.

7. ### Evaluate the business entity  
   Verify if the business is real and registered, the address, if the business is on a watchlist or sanctioned, if it operates in a high risk industry, if any adverse media can be found, and if any red flags can be inferred by the website.

8. ### Verify UBOs and other associated individuals  
   Send all provided individual data through the connected UBO/Individual Verification Flow in order to perform comprehensive KYC.

9. ### Evaluate signals → final decision  
   Based on the compliance and risk signals detected, the RiskOS™ workflow orchestrates the flow to make a final decision of Accept, Reject, or send to Manual Review.

### Workflow components used by Business Onboarding  
| Component | Purpose |
| --- | --- |
| Input | Collect business, individual, and session data |
| Enrichment | Run business, individual, fraud, and compliance checks |
| Partner Enrichments | Verify business entities (KYB) |
| Rule Score Cards | Aggregate risk across signals |
| Condition | Route based on structure and risk |
| Manual Review | Human review for edge cases |
| Decision | Emit final onboarding outcome |

## Configure Business Onboarding

### Enable required enrichments and feature flags  
Your Socure account team will provision access to:

**Core APIs**

- Digital Intelligence
- Verify Plus
- Sigma (Identity and Synthetic)
- Watchlist Plus

**Partner Enrichments**

- KYB partner integrations for business verification

**Feature flags**

- Associated evaluations in response (for UBO / individual verification)
- Risk APIs

### Required integrations  
- **Digital Intelligence SDK** — required to collect session telemetry

### Configure inputs and routing  
**Required business fields**

- `name`
- `address`
- `ein`

**Required individual fields (per associated person)**

- `given_name`
- `family_name`
- `email`
- `address`
- `date_of_birth`
- `di_session_token`

Routing strategies typically include:

- Declining on extreme fraud or compliance risk
- Routing conflicting or incomplete cases to manual review
- Approving when identity, ownership, and risk signals align

You can start from the **Business Onboarding – Example** workflow template to accelerate setup.

### Save and publish  
Once configuration is complete, publish the workflow to go live.

## Workflow testing checklist  
Use this checklist to confirm accuracy, resilience, and completeness before production launch.

**Input validation**:

Business name, address, and EIN are collected and validated.

Business address is parsed to a standard schema and validated with an address provider.

Associated individual identity fields (name, date of birth, address, email) are provided.

Date of birth values use ISO 8601 format and reject impossible dates.

Email addresses are RFC 5322–compliant and deliverable.

Digital Intelligence session token is collected from the SDK.

**Routing and decisioning**:

High-risk business or individual signals are detected and handled appropriately.

Sole proprietorships are routed directly to individual verification.

Conflicting risk or correlation signals route to manual review.

**Operational readiness**:

Business and individual verification results are accessible to relevant teams.

Graceful fallback paths exist when optional inputs or risk signals are inconclusive.