Digital corporate onboarding is attractive to banks and payment institutions because it shortens the path to an active account. But beneficial ownership verification in a Nafath eKYC flow has a structural limit: Nafath authenticates an individual, and a company's ownership structure is not something an individual's authentication can establish. This article sets out what the flow cannot collect on its own and where compliance officers should intervene.
What Nafath does and does not establish
Nafath gives you strong assurance that the person at the screen is the person they claim to be. For a corporate customer, that person is usually an authorised representative, a director or a manager.
That is necessary, but it is not sufficient. Under the SAMA AML/CTF requirements, which follow the FATF Recommendations, an institution must identify the legal entity, understand its ownership and control, and identify the natural persons who ultimately own or control it. A verified representative tells you nothing about the shareholders behind the entity, the people who hold control through other means, or whether the representative is authorised to bind the company.
The result is a common gap: the journey looks complete, the representative is authenticated, and the ownership file is thin.
Six documents your flow cannot collect automatically
Treat these as items that need manual collection or manual validation, even where the digital channel allows an upload.
- Commercial registration. The flow may capture a number or an image, but someone must confirm that the registration is current, that the activities match the stated business and that the registered details agree with the other documents.
- Shareholder register. This shows who holds shares and in what proportion. It must be current and consistent with the registration and the constitutional documents.
- Board resolutions. These evidence the decision to open the account and the authority of the named signatories. Authentication of the representative does not prove this authority.
- Trust deeds. Where a trust sits in the chain, the deed identifies settlors, trustees, protectors and beneficiaries, the people whose identities matter for ownership and control.
- Partnership agreements. For partnerships, the agreement sets out partners, contributions and control rights, which a registration extract alone rarely shows.
- Ultimate-beneficial-owner declarations. A signed declaration naming the natural persons who own or control the entity. It is a starting point for verification, not proof in itself, and must be tested against the other documents.
Three manual-review checkpoints before activation
The aim is not to remove the digital journey but to place human judgement where the automation stops. Three checkpoints work well.
Checkpoint 1: Completeness and consistency at submission
Before the file moves forward, a reviewer confirms that every document relevant to the entity type is present, in date and legible. The reviewer then compares names, percentages and addresses across documents. A shareholder register that disagrees with the declaration should stop the file here, not later.
Checkpoint 2: Ownership chain validation
This is the most important checkpoint. The reviewer traces ownership through each layer until natural persons are reached, and records the reasoning. Where the structure includes holding companies, trusts or nominee arrangements, the reviewer documents how control was assessed, not just ownership percentage. Each identified beneficial owner is then screened, including for politically exposed person status, and the file is risk-rated.
If the chain cannot be traced to natural persons, the account should not be activated. The file should be escalated, and the institution should consider enhanced due diligence.
Checkpoint 3: Approval before account activation
A second person, independent of the first reviewer, confirms that the ownership analysis is complete, that the risk rating is supported and that any enhanced due diligence has been approved at the right level. Only then should the account be activated. Configure the system so that activation is technically blocked until this approval is recorded.
Design points that prevent findings
- Make the entity type drive the document checklist, so a trust or partnership cannot proceed with only a commercial registration.
- Record the reviewer, date and rationale at each checkpoint, so the file can be evidenced to a supervisor.
- Define what happens when documents conflict, and who can approve an exception.
- Set a periodic review cycle so ownership information is refreshed and not left as it stood at onboarding.
- Sample completed files regularly to check that the checkpoints are working in practice.
Signs it is time to review your programme
An independent look at your corporate onboarding is worth considering when:
- corporate accounts can be activated without a recorded ownership analysis;
- reviewers rely on the declaration alone, without testing it against other documents;
- complex structures are handled inconsistently from one reviewer to another;
- the Nafath journey was built for individuals and extended to companies without redesign;
- file quality has not been tested across customer segments.
What a good outcome looks like
A well-run flow is fast for simple, low-risk entities and deliberately slower for complex ones. Every active corporate file shows the documents collected, the traced ownership chain, the screening results and an independent approval. The institution can explain, file by file, why it considered the beneficial owners to be who the file says they are.
How we approach it
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 steps: 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 programme fixes and a file remediation plan.
The assessment takes 4–6 weeks. It produces a KYC program assessment report, risk-rating model recommendations and a remediation plan for customer files. It covers corporate customers, including beneficial ownership and complex structures. If the review finds files that need to be corrected, we can design and run a file remediation program afterwards.
Next step
If your Nafath-based corporate onboarding is live or close to launch, a structured review of the journeys and a sample of files will show where the ownership gaps sit. Speak to CISO Consulting about a KYC, CDD and eKYC Program Review.
