# Client onboarding: AML and engagement checks

> Client onboarding: AML and engagement checks: Identity, beneficial owners, risk rating Checked: cross-checked. Produces onboarded client file, risk rating.

Source: https://www.sumarity.ai/library/client-onboarding-aml-and-engagement-checks/

Accounting, tax and Treuhand firms 

# Client onboarding: AML and engagement checks

Reads identity documents, registry extracts, the engagement letter. Produces onboarded client file, risk rating. Code works out every figure, the Judgement Engine answers the narrow questions, and whatever stays uncertain goes to a person.

Cross-checkedDocuments, onboarding and KYC
Start from this workflowMore for accounting firms  

What it decides

## Narrow questions, each with a check behind it.

Identity, beneficial owners, risk rating
Cross-checked: registries, documents. A second source has to agree: a register, a contract, a list. When it does the judgement settles; when it doesn't, a person decides.

| Reads | Identity documents, registry extracts, the engagement letter 
| Produces | Onboarded client file, risk rating 
| Who signs | A person on your team, with every figure traced to its document and every call on record 
| Process | Documents, onboarding and KYC 
| Industry | Accounting, tax and Treuhand firms    

See it run

## Every line, decided where it's safest.

An example run. Each stage lights up as a line is decided there; pick a stage to see its lines.

ReadsIdentity documents, registry extracts, the engagement letterCodeReads, matches, ties out and works out every figure.JudgementIdentity, beneficial owners, risk rating. Settles only when it clears the cutoff and a second source agrees.A personGets whatever stays uncertain, with the evidence. Their ruling tunes the next run.ProducesOnboarded client file, risk rating  
Client onboarding: AML and engagement checks · example run Example run  

| Ref | Item | Value | Decided by  
| CL-41 | Identity documents, 2 directorsValid, names match the registry |  | Code · verified 
| CL-42 | Beneficial ownerRegistry shows one owner over 25% · 0.95 |  | Engine · cross-checked 
| CL-43 | Source of fundsExplained by the sale of a business · 0.88 |  | Engine · cross-checked 
| CL-44 | Director listed on a sanctions list?Name similar, date of birth unknown |  | To a person 
| CL-45 | Engagement letterSigned by both parties |  | Code · signed  
|  

Settled 4 To a person 1 Settled wrong 0      Illustrative lines. Amber rows are the Judgement Engine's calls; each settles only above its cutoff and when its check agrees.    

What it could save

## Your volumes in. Your hours out.

In our tests, between 24% and 42% of items still went to a person after tuning. Set your own share; a pilot measures it on your data.

Items per run 
Runs per month 
Minutes per item by hand 
Cost per hour

Share of items that still need a person: 30%  

By hand today80 ha month 
With Sumarity24 ha month, for the items people decide 
Saved56 hCHF 53,760 a year    

Related

## Start from what's closest.

### Documents, onboarding and KYC in other work

Accounting firms

### Client document collection for year-end

What's missing, wrong period, unreadable

Proven by codeBanking

### Corporate KYC onboarding

Beneficial owners, documents complete, risk

Cross-checkedBanking

### Periodic KYC review

What changed; whether risk changes

Cross-checked

### More for accounting firms

### UK VAT return for a small business (pub VAT)

Each document's VAT treatment; what's missing

Proven by codeTested

### Swiss VAT (MWST) return

Rate and method per line; input tax recoverable

Proven by code

### German VAT advance return (USt-Voranmeldung)

Treatment per line, reverse charge

Proven by code  

Questions

## What buyers ask

What happens when Sumarity isn't sure?

Nothing settles below the cutoff, or when the check disagrees. The item goes to a person in the inbox with what the engine saw, its best answer and the runner-up. The person's ruling is kept and tunes the next run.

How are its judgements checked?

A second source has to agree: a register, a contract, a list. When it does the judgement settles; when it doesn't, a person decides.

Can we change it to fit how we work?

Yes. Start from this workflow and describe your differences in plain words. The design assistant revises it, the validator checks it, your expert reviews it on the canvas, and your admin publishes it.

Does it read our files as they are?

Yes: spreadsheets and CSV in any layout, PDFs, bank formats and e-mail attachments. Sumarity suggests how each column maps, proves the mapping on a sample and remembers it once a person confirms it.

Where does our data go?

Sumarity runs in Zurich. Your data, backups and logs are stored in Switzerland.

How does it get better?

Your team's rulings become an answer key. Better questions and cutoffs are proposed, tested on data they haven't seen, and published only when your admin approves. It improves itself, with permission.

## Start from this workflow. Run it on your data.

A pilot runs alongside your own process for a few weeks, at our cost, and ends in a line-by-line comparison.

Talk to usBack to the library