Background & Integrity Checks

VOG (Certificate of Good Conduct)

Validates a VOG (Verklaring Omtrent het Gedrag) for integrity verification.

{
  "checkName": "integrity-data",
  "importance": "NOT_SKIPPABLE",
  "configuration": {
    "position": "functie",
    "specialCircumstances": "",
    "screeningProfilePreset": "25",
    "screeningProfiles": [],
    "requestNewVog": true,
    "allowExistingVog": false
  }
}

VOG Options

Three ways to handle VOG verification:

1. Require New VOG (Most Secure)

{
  "requestNewVog": true,
  "allowExistingVog": false
}

Otentica prepares the VOG request
Professional guided through Justis process
Additional fraud prevention measures
Most secure option

2. Accept Existing VOG

{
  "requestNewVog": false,
  "allowExistingVog": true
}

Professional uploads existing VOG
Document authenticity check
Cross-reference with personal data
Cannot guarantee 100% validity

3. Professional Choice

{
  "requestNewVog": true,
  "allowExistingVog": true
}

Professional can choose
Less secure than requiring new VOG
Provides flexibility

Configuration Parameters

For new VOG requests only:

Parameter	Required	Description
`position`	Yes	Position/role the VOG is for
`specialCircumstances`	No	Special circumstances for the request
`screeningProfilePreset`	Yes*	Justis screening preset number
`screeningProfiles`	Yes*	Array of specific profile numbers

*Either screeningProfilePreset OR screeningProfiles required (not both)

VOG Processing Time

When requesting a new VOG, it takes minutes to hours to prepare the request at Justis. The screening is not available until preparation is complete. Wait for the READY callback before inviting the professional.

Common Screening Profiles

// Healthcare
{
  "position": "Verpleegkundige",
  "screeningProfilePreset": "25"
}

// Financial Services
{
  "position": "Financial Controller",
  "screeningProfilePreset": "45"
}

// Youth Care
{
  "position": "Jeugdzorgwerker",
  "screeningProfiles": ["84", "85"]
}

VOG Pending Flow

Feature flag — enabled per recruiter

The VOG pending flow is an opt-in feature that must be enabled for a recruiter by Otentica. When it is not enabled, the standard behaviour applies: the screening cannot be submitted until the VOG is fully completed.

Normally, a screening is submitted only after the professional has completed all steps, including uploading and verifying a VOG. When the VOG pending flow feature is enabled for a recruiter, this behaviour changes for new VOG requests.

When this applies: when the VOG pending flow is enabled for the recruiter, the VOG step has status ASYNC_WAITING (the VOG request has been submitted to Justis but the document is not yet available), and all other steps in the flow are complete — the screening is submitted without waiting for the VOG.

What happens at submission

The customer receives an initial report containing all completed checks, documents, and data. The VOG is clearly marked as Pending in this report.
The candidate receives an on-screen confirmation and a confirmation email at the moment of submission.

When the VOG is later uploaded and verified

An updated report is generated and re-delivered to the customer. The updated report is clearly distinguished from the initial report.
No further action is required from the candidate.

Existing flow is unchanged

If the candidate completes the VOG before all other steps are finished, or if the check uses an existing uploaded VOG (allowExistingVog: true), the flow behaves as before: the screening is submitted only after all steps including the VOG are complete.

API partner impact

A screening result may be reported as final and later be followed by an updated payload once the VOG is processed. Integration partners must be able to handle receiving a second result for the same screening token. The updated payload will be delivered via the same callback mechanism as the initial result.

References

Collects and verifies professional references through automated questionnaires.

{
  "checkName": "references",
  "importance": "SKIPPABLE",
  "configuration": {
    "onlyAllowCompanyEmailAddresses": true,
    "referencePeriod": "P3Y",
    "referencePeriodOffset": "P1M",
    "minNumberOfReferences": 2,
    "maxNumberOfReferences": 10,
    "questionNames": [
      "workedForCompany-yesNo",
      "position-yesNo",
      "relation-freeText",
      "agreements-yesNo",
      "careful-yesNo",
      "integrity-freeText",
      "rehire-freeText"
    ]
  }
}

Configuration Parameters

Parameter	Description	Example
`onlyAllowCompanyEmailAddresses`	Reject personal email addresses	`true`
`referencePeriod`	Period for which references are valid	`P3Y` (3 years)
`referencePeriodOffset`	Offset from current date	`P1M` (1 month)
`minNumberOfReferences`	Minimum references required	`2`
`maxNumberOfReferences`	Maximum references allowed	`10`
`questionNames`	Questions to ask referents	Array of question IDs

Reference Period Examples

// Last 3 years, excluding last month
{
  "referencePeriod": "P3Y",
  "referencePeriodOffset": "P1M"
}

// Last 5 years, no offset
{
  "referencePeriod": "P5Y",
  "referencePeriodOffset": null
}

// Last 2 years, excluding last 3 months
{
  "referencePeriod": "P2Y",
  "referencePeriodOffset": "P3M"
}

Standard Questions

Question ID	Question Text
`workedForCompany-yesNo`	Did [name] work at [company] from [start] to [end]?
`position-yesNo`	Did [name] hold the position of [position]?
`relation-freeText`	What was your professional relationship?
`agreements-yesNo`	Does [name] deliver on agreements?
`careful-yesNo`	Is [name] generally careful?
`integrity-freeText`	Any integrity risks regarding [name]?
`rehire-freeText`	Would you hire [name] again?

Reference Process

Professional enters referent contact details
Email invitation sent to referents
Referents complete questionnaire online
Flow completes when:
- All referents respond, OR
- 7 days pass without response
Responses included in flow results

PEP Check

Screens the candidate against Politically Exposed Persons (PEP) lists using an external data provider. No provider name is exposed via the API.

The check uses the candidate's name and date of birth from the identity step. No additional input is required from the candidate.

{
  "checkName": "pep-check",
  "importance": "SKIPPABLE"
}

Result Fields

Field	Type	Values / Format
`pepCheckResult`	STRING	`PEP` / `NOT_PEP` / `UNCERTAIN`
`pepCheckScore`	NUMERIC	0.0 (no match) to 1.0 (full match)
`pepCheckSource`	STRING	Audit — identifier of the data source used
`pepCheckDate`	STRING	Audit — date on which the check was performed

Match Score and Manual Review Threshold

The pepCheckScore reflects how closely the candidate's data matched an entry in the external dataset. A score of 0.7 or higher triggers a manual review flag. The threshold is configuration-driven per client and may differ from the default.

Positive match

When pepCheckResult is PEP or UNCERTAIN with a score at or above the configured threshold, an alert is generated. Client notification upon a positive match is configurable per client.

The PEP check is performed in the context of client due diligence under the Wwft (Wet ter voorkoming van witwassen en financieren van terrorisme) / KYC-AML obligations. Processing is carried out by an external data provider acting as a processor under a data processing agreement. Data used for the check is not retained by Otentica beyond the standard screening retention period. Integration partners should ensure their own processing is consistent with the Wwft purpose and applicable retention rules.

Sanctions Check

Screens the candidate against international sanctions lists using an external data provider. No provider name is exposed via the API.

The check uses the candidate's name and date of birth from the identity step. No additional input is required from the candidate.

{
  "checkName": "sanctions-check",
  "importance": "SKIPPABLE"
}

Result Fields

Field	Type	Values / Format
`sanctionsCheckResult`	STRING	`SANCTIONED` / `NOT_SANCTIONED` / `UNCERTAIN`
`sanctionsCheckScore`	NUMERIC	0.0 (no match) to 1.0 (full match)
`sanctionsCheckSource`	STRING	Audit — identifier of the data source used
`sanctionsCheckDate`	STRING	Audit — date on which the check was performed

Match Score and Manual Review Threshold

The sanctionsCheckScore reflects how closely the candidate's data matched an entry in the external dataset. A score of 0.7 or higher triggers a manual review flag. The threshold is configuration-driven per client and may differ from the default.

Positive match

When sanctionsCheckResult is SANCTIONED or UNCERTAIN with a score at or above the configured threshold, an alert is generated. Client notification upon a positive match is configurable per client.

The sanctions check is performed in the context of client due diligence under the Wwft (Wet ter voorkoming van witwassen en financieren van terrorisme) / KYC-AML obligations. Processing is carried out by an external data provider acting as a processor under a data processing agreement. Data used for the check is not retained by Otentica beyond the standard screening retention period. Integration partners should ensure their own processing is consistent with the Wwft purpose and applicable retention rules.

Best Practices

Complete Background Check

"requestedChecks": [
  {
    "checkName": "integrity-data",
    "importance": "NOT_SKIPPABLE",
    "configuration": {
      "position": "Senior Developer",
      "screeningProfilePreset": "25",
      "requestNewVog": true,
      "allowExistingVog": false
    }
  },
  {
    "checkName": "references",
    "importance": "NOT_SKIPPABLE",
    "configuration": {
      "onlyAllowCompanyEmailAddresses": true,
      "referencePeriod": "P3Y",
      "minNumberOfReferences": 2,
      "maxNumberOfReferences": 3
    }
  }
]

Risk-Based Approach

High-Risk Positions:

Require new VOG
Multiple references required
Company email addresses only

Low-Risk Positions:

Accept existing VOG
References optional
Personal emails allowed

Timing Considerations

VOG preparation can delay flow start
Reference collection takes up to 7 days
Plan screening timeline accordingly
Consider making references SKIPPABLE for urgent hires

VOG (Certificate of Good Conduct)​

VOG Options​

1. Require New VOG (Most Secure)​

2. Accept Existing VOG​

3. Professional Choice​

Configuration Parameters​

Common Screening Profiles​

VOG Pending Flow​

What happens at submission​

When the VOG is later uploaded and verified​

Existing flow is unchanged​

References​

Configuration Parameters​

Reference Period Examples​

Standard Questions​

Reference Process​

PEP Check​

Result Fields​

Match Score and Manual Review Threshold​

Privacy & Data Processing (AVG / GDPR)​

Sanctions Check​

Result Fields​

Match Score and Manual Review Threshold​

Privacy & Data Processing (AVG / GDPR)​

Best Practices​

Complete Background Check​

Risk-Based Approach​

Timing Considerations​

VOG (Certificate of Good Conduct)

VOG Options

1. Require New VOG (Most Secure)

2. Accept Existing VOG

3. Professional Choice

Configuration Parameters

Common Screening Profiles

VOG Pending Flow

What happens at submission

When the VOG is later uploaded and verified

Existing flow is unchanged

References

Configuration Parameters

Reference Period Examples

Standard Questions

Reference Process

PEP Check

Result Fields

Match Score and Manual Review Threshold

Privacy & Data Processing (AVG / GDPR)

Sanctions Check

Result Fields

Match Score and Manual Review Threshold

Privacy & Data Processing (AVG / GDPR)

Best Practices

Complete Background Check

Risk-Based Approach

Timing Considerations