KYB dashboard migration guide
KYB results are now worked as KYB cases. This page is for the people who review KYB in the dashboard: what moved, what behaves differently, and what to set up before relying on the new pages. Existing results were migrated: each one is now a case with the same ID, and its history is kept.
If you integrate through the API or the SDK, see the SDK migration guide as well.
What changed at a glance
| Before | Now |
|---|---|
| KYB Results was a table of every result | Cases to work on groups open cases by what they need: ready for review, action required, waiting for input, processing. Show all results keeps the full table. |
Statuses ACQUIRING, ENRICHING, PENDING_MODERATION, REVIEW_REQUIRED, SUCCESS, FAILED | Case statuses OPEN, PROCESSING, WAITING_INPUT, ACTION_REQUIRED, READY_FOR_REVIEW, APPROVED, REJECTED, CANCELLED. See How a KYB case works. |
| Clean companies could be approved automatically | Nobody approves automatically. A clean company reaches Ready for review and a reviewer (or the KYB agent in Auto-pilot) decides it. |
| Approving could acknowledge open barriers | Each blocker is covered by an exception with a reason and an expiry. See Exceptions. |
| A rejection could be recorded without a reason | Every rejection needs a reason, and can carry a reason code. |
| Anyone who could moderate decided alone | Your approval matrix says who may decide at each rating, and when a second signature is needed. See Approval matrix. |
| A decision was the end of the result | A decision is never rewritten, but the case can be reopened by a resubmission, a quality review, or a periodic re-review. |
| Assignment was per result | Assignment is per company, and applies to every case of that company. |
| The activity log and the agent activity were separate lists | Case activity shows what the case is waiting for, the steps and runs, coverage, exceptions, decisions, and agent reviews; Audit trace keeps the full event log. |
| Screening matches | A false positive needs a discriminator (date of birth, nationality, ID number, address, gender, or another reason). See Company screening. |
| Documents were configured with fixed built-in slots | Each country has a document catalog; you mark documents required, optional, on demand, or off, and add your own. See Required documents. |
New pages
- Compliance policy (Settings → Compliance policy): screening rules, admitted fallbacks, the approval matrix, quality-review sampling, and approval validity. Versioned: publish a draft, put it in force in the sandbox, then in production.
- Quality reviews: decisions drawn for a second look.
- Metrics: how your KYB decisions were taken over a period.
Who can do what
KYB cases can now be worked by ORG_OPERATOR and AML_OFFICER users as well as ORG_ADMIN. The compliance policy and the KYB orchestration rules are edited by ORG_ADMIN and AML_OFFICER. What each person may decide is set by your approval matrix.
Before you go live
- Review your compliance policy. Organizations that existed before this release start with a first version in force, which admits name-only screening as a fallback. Check it against your procedure (or upload the procedure and let Zyphe read it), then publish your changes and put them in force in the sandbox before production.
- Decide who signs. Add approval-matrix rows for the ratings where you want specific roles or a second signature.
- Check your webhooks.
verification.kyb.reviewis now also sent when an approved company is reopened, and every decision sends exactly one webhook, including decisions taken from the dashboard. See Webhook lifecycle. - Check the case planner of each KYB flow. Flows keep the fixed order of checks unless you choose your organization's rules or AI proposals on the Know Your Business step.