Agentic AI for Commercial-Customer Onboarding in UAE Banks

Onboarding requires a supported risk judgement

Company records, ownership declarations, board resolutions and account-purpose statements describe different parts of the customer. Each record may be authentic while the combined account remains incomplete or inconsistent. A director may lack authority to operate the account, an ownership chain may end at another company rather than a natural person, or the declared activity may not explain the transactions the customer expects.

The CBUAE requires licensed financial institutions to identify and verify customers and beneficial owners using reliable, independent sources. The institution must also verify people who can act for the customer. Commercial onboarding therefore requires the reviewer to connect claims across records and decide whether the evidence supports the proposed relationship.

Represent the case before automating its preparation

The workflow needs explicit case states. These states should distinguish evidence that is missing, received, verified, contradicted, expired or awaiting authorised judgement. A file marked complete should mean that the bank has satisfied its defined evidence conditions, not that an applicant uploaded the expected number of documents.

The case model should also identify the source of each claim, the date on which the bank obtained it, the policy version used and the officer responsible for the decision. Without this structure, an agent can produce a persuasive summary while concealing an unresolved ownership or authority question.

Use deterministic checks before agentic investigation

Code should verify required fields, document dates, identifier formats, mandatory screening steps and approval limits. These checks have defined answers and should produce the same result from the same case data.

An agent becomes useful when the workflow must follow a variable evidence trail. It can compare names across records, trace an ownership chain, retrieve the applicable procedure, request a missing item and prepare a cited account of contradictions. The agent should present unresolved questions to the responsible reviewer. It should not convert a probable match or a plausible explanation into customer acceptance.

Treat beneficial ownership as a graph of claims

A corporate customer may sit beneath several legal entities, trustees, nominees or holding companies. The bank must trace the relevant ownership and control relationships until it identifies the natural persons required by its policy and applicable rules. A document checklist cannot establish this result because the significance of one record depends on the other entities and people in the chain.

The workflow should represent each ownership claim as a relationship supported by a named source. It should flag loops, gaps, conflicting percentages and ownership totals that do not reconcile. A reviewer can then examine the disputed relationship instead of rereading every document without knowing which link remains unsupported.

Keep screening evidence separate from screening decisions

Name screening can produce possible matches when people share a name, transliteration or other identifying detail. The screening result identifies a question; it does not establish that the applicant and the listed person are the same individual.

The agent may assemble dates of birth, nationality, addresses, identifiers and ownership relationships that help an authorised reviewer resolve the match. It must preserve the original result and the evidence used to disposition it. A later review should be able to reconstruct why the bank cleared, escalated or retained the alert.

Example: a complete file with an unresolved owner

A trading company applies for an operating account. The file contains a trade licence, memorandum, shareholder register, board resolution and passports for two directors. The shareholder register shows that a foreign holding company owns 80 per cent of the applicant. The application names the holding company's managing director as the ultimate owner but provides no evidence of that person's ownership or control.

Deterministic checks confirm that the required documents are present and current. The agent then traces the declared relationships, identifies that the chain stops at a legal person and requests evidence for the natural persons who ultimately own or control it. A screening result also returns a possible match for one director, so the agent assembles the identifiers that distinguish or connect the two people.

The onboarding officer reviews the ownership gap and screening evidence under the current bank procedure. The agent records the officer's decision and the supporting evidence, but it does not complete the beneficial-owner claim or clear the screening result itself. The bank can therefore reduce document handling without transferring customer acceptance to the system.

Test failures that a polished case summary can conceal

Evaluation should include an ownership chain that ends too early, percentages that do not reconcile, an expired board authority, two customers with similar names, an obsolete policy, conflicting sources and a material document added after the case summary was prepared. The test should also include an apparently complete low-risk file that contains one unsupported control relationship.

Reviewers should inspect whether the workflow found each defect, cited the correct source, kept the case open and referred the decision to the authorised role. Preparation time matters only after these conditions are satisfied. A faster summary has no value if it causes the bank to overlook the person who controls the customer.

Pilot one customer type and review route

A controlled pilot can begin with periodic review for one commercial-customer type. Closed historical cases provide known evidence and reviewer decisions, while shadow operation shows how the agent performs on current cases without changing the bank's customer records or decisions.

Management should compare evidence completeness, missed material issues, false escalation, reviewer correction, preparation time and consistency across ownership depth, jurisdiction and risk tier. The bank should expand the workflow only when the results show that faster preparation has not weakened identification, screening or approval control.

How Marketways can support the pilot

Marketways can map the selected onboarding or periodic-review route, define the case and evidence states, separate deterministic checks from agentic investigation and build controlled evaluation cases. We can also analyse errors by customer type, ownership depth and risk condition so that management can identify where the workflow remains unreliable.

Marketways provides workflow design, implementation support and technical evaluation. The bank's compliance, legal, risk and authorised business officers retain regulatory interpretation, customer acceptance, account restriction and external reporting decisions.