Overseas Verification Process

• AuthBridge builds trust through data

Police Verification Process

• Seeks to verify a candidate's criminal history, consulting provided information in the Background Verification Form (BVF)
• Authenticity of documentary evidence is confirmed
• Verification conducted by vendors, who provide their findings
• The documented procedure outlines the standard steps and exceptions in police verification, targeted at users familiar with background verification terminology

Requirements

• Training covers classroom instruction on processes and Bridge/Opus usage
• Applications used are Bridge and Opus
• Input required includes candidate's name, DOB, father’s name, ID numbers, and supporting documents
• Other considerations are not applicable

Terminology:

• CASE refers to a collection of checks established during a process, adhering to Standard/Non-Standard guidelines
• Check includes candidate or client details from BVF/EAF/JAF, categorized into varying sets termed "Checks"
• ARS Number is client code, and the remaining six record the number of cases received from the client
• ARN (Authorization Release Note) refers to authorization release note
• Bridge encompasses the application used on computer to handle a case's complete life cycle for background verification and requires unique logins for different roles/users
• INT is the abbreviation used for internal teams, INT1 and INT2
• OVS refers to Overseas
• CCC refers to "Case Closed by Client"
• SI (Special Instruction) refers to special instructions for particular checks

Reference Verification Process

• Verifier updates PVT error log, and PVT makes necessary corrections if needed
• Department assigns Overseas PV checks to the Overseas window
• Checks include both police record verification via Law Firm and Criminal Litigation Database Check
• Verifier selects a check
• The verifier then confirms provided details are correct, moving the check to the next stage
• The system loops back when details are incorrect
• Database department selects the appropriate disposition in OPUS to close the check
• Check reverts to Departments
• Verifier check mandatory details and documentation
• Process pauses to raise Insufficiency
• Updates the Verification response in Vendor allocation tracker and proceeds with vendor allocation for verification
• Database department closes the check
• Once insufficient data is provided the verifier updates the antecedent in OPUS
• The response documents also get attached in Bridge
• Verifier updates the Antecedent in Bridge, specifically for the Criminal Litigation DB Check

Procedure

• Essential items before starting include cost approval for overseas, a duly signed BVF, a signed authorization letter, and identity proof
• Police Record Verification through Law Firm (OPUS) and Criminal Litigation Database Check (Bridge) are verified during police verification
• Overseas Verifier completes the verification and sends it back to the department for closure
• Criminal Litigation Database Check - overseas verifier completes the verification and closes the check in Bridge

Tagging in Police Verification

• Discrepant: Match is found in Police Records/any Criminal History
• Attention Required: Where Partial Address or Partial Name is found in Police Records/any Criminal History
• Insufficient: the verification could not be completed due to absence of mandatory information or document
• Response not Received: no response if received from the source
• Clear: no match is found in police records

Verifier's Role

• Verification is achieved through external verification processes and relevant vendors, with verifiers allocating checks and overseas verifiers acting accordingly upon receiving vendor responses in OPUS or Bridge
• Approval from the client is required for subcontracting and vendors for specific clients, and checks are allocated only to approved vendors with instructions on Bridge and a list via email or other communication

Verification Process

• Post-quality check, the check goes to the allocator window and allocators check verification source, allocating it to an overseas window for processing
• Overseas teams get their check in overseas window for further execution
• Before allocating, the verifier do preliminary checks for Vendors
• Then verifier teams handle two distinct PV checks

Police Record Verification Via Law Firm

• The check is located in OPUS

Overseas Verifier Window

• A check is listed in the overseas verifier's window details include candidate name, verification source, and other specifics

Verifier Action

• The verifier reviews information before initiating the verification process
• Overseas cost approval must be given prior to verifying

Signed ARN

• There is a need for a signed authorization letter for the candidate to authorize their background check, with the right to deny if they wish

Validating Documents

• The verifier is responsibile for cross-validating all documents.

Verifier Actions when there are Missing items

• In case of missing info, the team should raise the Insuff in OPUS
• Insufficiency leads to an updated antecedent marked "Not applicable," with the check closed due to insufficiency
• After sufficient information is provided, the verifier then start the verification process

Vendor Allocation and Communication

• The overseas team needs to process vendor allocation
• Send the relevant documents to the vendor

Updating Checks

• Need to add the comment in the check with the queue

Vendor Allocation Tracker

• The verifier must update the vendor allocation tracker

Reports

• The verifier must send reports to the correct format

Verifier side

• After getting the response from Vendors, Verifier needs to update the Antecedents in OPUS
• Attach support documentation in Bridge

Post-Verification Procedure

• The check moves from the overseas window to the DB department for closing
• After verifying using Opus, verifiers attach documents in Bridge

Closing

• The DB department verifies and closes the check as determined by the overseas verifier

Criminal Litigation Database Check

• Overseas teams must check Bridge, verify details and information and update the antecedent in Bridge
• Log in from the Bridge window for Overseas allocation for the PV check

Verifier Actions

• After review the below details and information, Verifier needs to review the below details before initiating the verification
• Sign ARN must be followed for the countries indicated in the document
• All details must be validated documents

Insufficiency Handling

• Then the bridge team can follow up regarding any insufficiencies.

Vendor Allocation

• Overseas teams can allocate all the vendors
• Document checklist must be checked

Comments

• Add comments in the queue

Reports

• The vendor must submit reports on a certain schedule time

Updation

• Overseas verifiers must update the Bridge

Bridge Attachment

• Documents related to the response from vendors must be attached to bridge.

Final Check

• To complete process, verifiers must carefully check the basis of disposal

Action after closing Check

• If there are any discrepancies or missing items raise the issue
• There is also and attach / delete button

Vendor Process

• Also provide feedback from Vendors, eligibility threshold is 70%

Vendor Evaluation Process

• Vendor performance is tracked and evaluated at certain fixed frequency

Initial stage schedule

• For audit schedule, vendors are given 7 days but can also be offered 3-4 day extensions
• If there are any issues the HOD is made aware and a risk tracker will be updated

This quiz covers the steps and requirements for overseas verification. It includes necessary approvals, handling insufficiencies, using PVT error logs, initial verifier tasks, vendor communication, the role of police verification, system updates, tool functions, vendor response formats, and required police verification information.