HDVerityLawVerityLaw Docs
Help Center

Working in Verification

SOP manual for the Verification area covering dashboard review, KYC, KYB, bank verification, monitoring, and direct verification-detail routes.

publicusers

Working in Verification

This page shows internal users how to use the current Verification routes safely. The current module mixes real review screens with form shells, so it is important to know which pages are already useful for evidence and which are still thin after submit.

Product: VerityLaw
Module: Verification
Role: Onboarding analyst, KYC/KYB operator, risk reviewer, monitoring analyst
Difficulty: Beginner to Intermediate
Time: 10 minutes
Last Updated: 2026-03-10
Version: Current repo baseline

Before You Start

  • Sign in to the internal VerityLaw dashboard.
  • Know whether you are running identity, business, bank, or monitoring work.
  • Keep the correct person, company, or entity reference close at hand.

What is the Verification area?

The Verification area is where VerityLaw groups identity checks, business checks, bank checks, monitoring, and direct verification detail screens. It helps you separate verification work from general client or compliance administration.

When do you use this?

Use this module when you need to start a verification, review recent results, inspect a verification record, or monitor an entity after onboarding. Do not assume every form already produces a persisted visible result from the same page.

Where do you find it?

Primary path: Dashboard -> left sidebar -> Verification

Current routes:

  • /dashboard/verify
  • /dashboard/verify/identity
  • /dashboard/verify/business
  • /dashboard/verify/bank
  • /dashboard/verify/monitoring
  • /dashboard/verify/status/[id]
  • /dashboard/verify/risk/[entityId]

The status and risk routes are usually opened from a known record or deep link rather than from the sidebar.

How do you work in Verification?

Start from the verification dashboard

  1. Open Verify.
  2. Review Total Verifications, Passed, Failed, and Pending.
  3. Check Recent Verifications for the latest entity, type, date, and status.
  4. Check Active Monitoring for alert counts and last-checked dates.

Use the identity form

  1. Open Identity.
  2. Enter the first name, last name, date of birth, ID type, ID number, and country.
  3. Decide whether PEP & Sanctions Screening should stay enabled.
  4. Submit the form only after confirming the person details are correct.

The current page shows a submit action and loading state, but it does not show a stored result, redirect, or visible completion record on the same page after submit.

Use the business form

  1. Open Business.
  2. Enter the company name, registration number, and country.
  3. Select the checks you need, such as registration, directors, VAT, and beneficial ownership.
  4. Submit only after confirming the company identity.

Like the identity page, this route is currently a form shell after submission. It does not show a completed server-side result in the same UI.

Use the bank form

  1. Open Bank.
  2. Enter the account holder name, account number, branch code, and country.
  3. Submit only when you are certain the account data is correct.

This page also behaves as a capture form with a loading state. It does not show a stored verification outcome in the current route after submit.

Review continuous monitoring

  1. Open Monitoring.
  2. Switch between Monitored Entities and Alert History.
  3. In the entity view, check Type, Country, Frequency, Status, Last Checked, and Alerts.
  4. In the alert view, review severity, alert type, title, description, and acknowledgement state.

The current UI exposes Add Subscription, Pause/Resume, and Acknowledge controls, but this page does not show a visible persisted outcome for those actions yet. Treat it mainly as a monitoring and review screen.

Review a direct verification record

  1. Open a verification detail route such as /dashboard/verify/status/[id] when you already have a verification ID.
  2. Review the entity details, timestamps, result, risk score, and checks performed.
  3. Open /dashboard/verify/risk/[entityId] when you need the entity risk view.
  4. Use the risk page to review composite score and verification history.

The risk page currently includes a Score History placeholder area. Use the live scores and history list rather than waiting for a full chart.

What if something does not look right?

"I submitted a form and nothing obvious happened"

What it means: The KYC, KYB, and bank pages are still thin after submit in the current UI.

What to do: Treat the submit as a capture step only, then check whether a separate verification record becomes available through your environment.

"The monitoring page has buttons, but I cannot confirm a change"

What it means: The page is stronger as a review screen than as a fully wired action console.

What to do: Use it to inspect state and alerts, and verify any operational change through the team that manages monitoring subscriptions.

"The status or risk route says the record is missing"

What it means: The direct route only works when a matching verification or entity record already exists.

What to do: Confirm the ID first, then return to the main Verify dashboard if needed.

What's Next

Related Pages

Still Stuck?

  • Start from Verify again if you are unsure which sub-route you need.
  • Use the functionality gap map before promising fully automated verification flows.
  • Contact support: support@veva.co.za

Was this page helpful? [Yes] [No]