Simple KYC checks
The participant-completed path — the eight statuses a check moves through, and the only two that need anything from you.
Overview
"Simple" describes the check's scope, not its difficulty. A Simple KYC gathers personal information, an identity document and a proof of address — and crucially, the participant provides them. They receive an invitation, create an account if they do not have one, complete the flow, and submit. Your team reviews and verifies.
This is the default path and the one to prefer: less work for your team, and the documents arrive from the person they belong to.
What you'll learn
What a simple check asks of the participant
The status ladder, and the only two statuses that need you
How to review a submission
What the participant experiences, so you can answer their questions
The status ladder
Status | What it means for you |
|---|---|
Initialised | The check exists. Nobody has been contacted. |
Invited to Create Account | The invitation has gone out. Now you wait. |
Account Created | They have signed up. |
Ready | They can start. |
Submitted | Your turn — review it. |
Reviewing | Under review. |
Verified | Done. |
Incomplete | Returned to them — A7.5. |
Eight statuses, but only two are yours to act on: Initialised (invite them) and Submitted (review it). The rest are waiting states.
Steps
From the project Dashboard, select Launch KYC Checks, with Simple KYC for the people concerned (A7.2).
On the dashboard, use Invite / Send Email to invite them — in bulk if there are several.
Watch the status move as they act. Where someone stalls, use Remind.
When a check reaches Submitted, open it and review the personal information and both documents.
Approve it, then verify once your process's approvals are in (A7.6).
If something is missing or wrong, mark it incomplete with a reason instead of approving (A7.5).
What the participant experiences
Worth knowing, because it determines what they will ask you:
They get an email, create an account with an invitation ID, and land on a dashboard showing a task.
The flow takes a few minutes and works on a phone.
They are asked for an identity document — front and back if it is an ID card — and a recent proof of address.
On submitting, they see confirmation that it will be reviewed by the compliance team.
If they cannot complete it — no smartphone, no recent utility bill, unwilling to use the platform — that is the case for switching to an internal check (A7.3).
What good looks like
Every simple check reaches Verified, each having been reviewed against its documents. The participant did the data entry; your team did the judging. Nobody maintained a spreadsheet.
Common problems
Nothing is happening and the status says Initialised. They have not been invited yet.
They say they never received the email. Check the address on the shareholder record, then re-invite. Also ask them to check their spam folder — an unfamiliar sender asking for identity documents is exactly what filters catch.
They are stuck at Account Created. They signed up but have not completed the check. Remind them.
The photo is unusable. Mark it incomplete with the appropriate reason. Glare is the usual cause, so the fix is to lay the document flat without flash.
You are tempted to approve something you are not satisfied with. Return it as incomplete instead. Approving converts a compliance question into a record saying you were satisfied.
Related
A7.1 — What a KYC check covers · the two levels
A7.3 — Internal KYC checks · the alternative when a participant cannot complete
A7.5 — Chasing incomplete KYC checks · returning a submission
A7.6 — KYC: approve, then verify · why those are two different things
