A Nafath eKYC beneficial ownership PEP screening review starts from one observation: Nafath answers the question of who is present, and onboarding has several other questions to answer. Nafath authenticates a person against national identity records. It does not tell you who ultimately owns or controls a corporate customer, whether an individual is a politically exposed person, or how risky the relationship is. When those three outcomes are assumed to follow from a successful Nafath authentication, enhanced due diligence triggers are missed quietly, and the file looks complete.
This article gives MLROs, heads of compliance and digital onboarding product owners a practical method to review that gap under the SAMA AML/CTF framework.
What Nafath does and does not establish
Treat Nafath as a strong identity-verification and authentication control. It gives confidence that the person completing the journey is the person they claim to be. Under SAMA AML/CTF requirements and FATF standards, customer due diligence is wider than that. It includes:
- Identifying and verifying the customer.
- Identifying the beneficial owner and taking reasonable measures to verify that person.
- Understanding the purpose and intended nature of the relationship.
- Determining whether the customer or beneficial owner is a PEP.
- Assigning a risk rating that drives the level of due diligence and ongoing monitoring.
Only the first item is directly served by Nafath. The rest depend on data the customer declares, sources you screen against, and decisions your own rules make.
Step 1: Map the journey as it actually runs
Start with the live journey, not the policy. Walk each customer segment through the flow, whether individual, sole proprietor, or corporate, and record every screen, data field, system call and decision point. For each step, note:
- What data is captured and whether it is declared or verified.
- Which system makes a decision, and which rule it applies.
- Where a human can intervene, and where the journey cannot be stopped.
Product owners often find that the flow assumes the person authenticating is the whole story. For a corporate customer, the person who passes Nafath may be an authorised signatory with no ownership at all.
Step 2: Test each CDD element against the map
Take the CDD elements above and mark where each one is satisfied in the journey. Three areas tend to need the closest attention.
Beneficial ownership
Ask whether the journey captures ownership and control down to natural persons, or stops at the first legal entity. Check whether declared owners are verified against documents or registries, or accepted as typed. Look at how complex structures are handled: layered holdings, nominee arrangements and foreign parents should route to a person, not to a default path. A signatory who authenticates through Nafath is not evidence of who the beneficial owners are.
PEP status
Check when PEP screening runs, and against whom. Common gaps include screening only the authenticated individual and not the beneficial owners or controllers, screening only at onboarding with no re-screening, and relying on a customer self-declaration tick box. Also confirm how family members and close associates are treated, and how a potential match is dispositioned before an account is activated.
Risk rating
Establish when the risk rating is assigned and what feeds it. If the rating is computed before ownership and PEP results are known, or if those results do not feed back into it, the rating reflects only what Nafath provided. Check that the rating is recalculated when new information arrives.
Step 3: Find the missed EDD triggers
With the map and the element tests in hand, look for the points where an EDD trigger should have fired and did not. Typical triggers under a risk-based approach include a PEP or PEP-linked owner, complex or opaque ownership, higher-risk geography or activity, and unusual source-of-funds or source-of-wealth profiles. For each, ask three questions:
- Is the data needed to detect this trigger collected in the journey?
- Is there a rule that reads the data and raises the flag?
- Does the flag stop straight-through processing and create a task for a person?
A trigger fails if any of the three answers is no. Record the failure type, because the fixes differ: a missing field is a product change, a missing rule is a configuration change, and a missing stop is a control design change.
Step 4: Decide what needs a manual handoff
Not every check should be manual, and not every check can be automated. A workable decision test is to ask, for each check, whether the outcome can be reliably determined from structured data, and what the consequence is if the automated result is wrong.
Checks that usually warrant a manual handoff include:
- Any corporate customer with more than one ownership layer or a foreign owner.
- Any potential PEP match that cannot be cleared on clear identifiers.
- Any case where declared ownership conflicts with documents or registry data.
- Any customer whose risk rating moves to high after ownership or PEP information is added.
- Source-of-wealth assessments for higher-risk relationships.
Checks that can usually stay in the digital flow include identity authentication, clear-cut screening results with strong identifiers, and standard-risk individuals with simple profiles. Whatever the split, define the handoff precisely: who receives the case, what they must decide, what evidence they record, and whether the account stays restricted until they do.
Step 5: Sample files to confirm what the design review suggests
A design walkthrough shows what should happen. File testing shows what did happen. Pull a sample across segments and channels, including digitally onboarded corporate customers, and test each file for the following:
- Beneficial owners identified and verified to natural persons.
- PEP screening evidence covering owners and controllers, with dated results.
- Risk rating consistent with the file contents.
- EDD documented where triggers existed.
- Evidence of the handoff decision where one was required.
Group the findings by root cause rather than by file. A pattern of the same gap across many files points to a journey design issue, not individual error.
Step 6: Close the loop with periodic review
The digital journey is only the entry point. Confirm that the periodic review cycle re-screens owners and controllers, refreshes ownership information, and recalculates risk ratings, and that changes in customer data between reviews can trigger an earlier look. Files that were onboarded before the gaps were fixed need a remediation plan, prioritised by risk.
How the firm supports this review
Our KYC, CDD and eKYC Program Review covers customer due diligence, enhanced due diligence, beneficial ownership, PEP handling and digital onboarding through Nafath against SAMA requirements. The work follows four stages: review policies, risk rating and onboarding journeys; test a sample of customer files across segments; assess gaps in CDD, EDD, ownership and PEP controls; and plan program fixes and a file remediation plan.
The assessment takes 4–6 weeks. Deliverables are a KYC program assessment report, risk-rating model recommendations and a remediation plan for customer files. Corporate customers are in scope, including beneficial ownership and complex structures. Where files need correcting, we can design and run a file remediation program after the review.
Next step
If your digital onboarding relies on Nafath and you cannot show where beneficial ownership, PEP status and risk rating are established, start with the journey map in Step 1. If you would like an independent view, the KYC, CDD and eKYC Program Review gives you a documented assessment against SAMA AML/CTF requirements and a clear plan for what to fix.
