Appearance
Intake
Getting a merchant into Verity and getting the first evidence on file.
Creating an entity
Entities → New entity. You need entity.create.
Two fields matter at creation:
| Field | Notes |
|---|---|
| Registration number | Validated against the country's format rule. Saudi Arabia requires the 10-digit unified number beginning with 7 (7XXXXXXXXX) — not the 1010-style CR number. |
| Country | Must have an active country configuration on your account, or creation is refused. |
On save, Verity immediately runs the checks configured as intake defaults for that country. You do not queue them by hand. Which checks those are is an admin setting — see Country defaults.
Why the unified number
Wathq returns both a crNumber (1010-style) and a crNationalNumber (7-prefixed unified number). Verity stores the unified number in registration_number and the CR number in registration_national_number — the column names read as inverted relative to Wathq's field names, which has caused real bugs. If you are debugging a lookup, check which one you are holding.
What happens next
The entity page opens on Draft with:
- Verification coverage — blank until the first checks return
- Risk — Risk not assessed, and it stays that way until an assessment runs
- Intake posture — one of three states
Intake posture
| Posture | Meaning |
|---|---|
| Needs initial checks | No check has completed yet |
| Initial checks failed | The most recent run of some check type failed |
| Review ready | At least one check completed and none of the latest runs failed |
Posture reads only the most recent run of each check type. A failure that a later retry superseded no longer counts — it is history, not the current state.
Operator inputs
Four fields Verity cannot obtain from a registry and an operator must supply:
- Website — also the input to the domain intelligence and website content checks
- Social — a public profile, where relevant
- Business activity summary — a short description of the operating model
- IBAN — required before the IBAN verification check is offered
They are edited inline on the entity page and require entity.update. The "Next steps" panel counts what is still missing.
Starting a review
Once the entity is review-ready, Start review opens an initial review. The button is disabled while the intake posture blocks it, and the tooltip says which posture.
Create periodic review opens a periodic review instead. Periodic reviews deliberately do not require the intake checks to have completed — they exist for merchants already onboarded. Approval is still gated by blockers, so this is not a way around the checks.
Sorting the entities list
The list is newest first by default. The sort control under the filter bar switches between:
| Option | Order |
|---|---|
| Newest | Most recently created first (default) |
| Oldest | Earliest created first |
| Recently updated | Most recently touched first — useful for picking up work in flight |
| Least recently updated | Stalest first — useful for finding forgotten files |
The choice is carried in the URL, so a sorted, filtered view can be bookmarked or shared. Switching sort keeps your search and filters and returns you to page 1, since page 4 of one order has nothing to do with page 4 of another.
Common intake problems
"Country is not configured for this account." The country has no active configuration. An admin adds one under Settings → Country defaults.
Registration number rejected. For Saudi Arabia it must match 7XXXXXXXXX. If you are holding a 1010-style number, that is the CR number, not the unified number.
Checks failed immediately. Open the check row and then the provider evidence. The fetch run holds the sanitised request and response including the provider's status code and message. Provider credentials are filtered out of the snapshot.
Nothing ran at all. The country configuration has no intake checks selected. That is a configuration state, not a failure, and the posture says Needs initial checks rather than implying anything passed.