Product film · recorded on the live platform
A day in the Financial Crime Unit on AIState
Eight people at a Frankfurt bank, one working day. Each does one real job: cataloguing the data, onboarding a customer, approving, deciding what is reported, screening, checking the work. Eleven chapters, every screen the real product, narrated and subtitled.
Chapters
- 1The data estate0:00
- 2The team lead's morning7:11
- 3Onboarding a customer9:19
- 4Approval and ownership13:30
- 5The MLRO decides17:20
- 6Who may see what23:06
- 7The case in time, and a report24:45
- 8Screening28:43
- 9The afternoon: the whole estate31:47
- 10Quality assurance36:18
- 11Which cases lean on each other38:58
Who you will see
- KevinIT administrator
- RuthTeam lead
- PriyaKYC analyst
- Thomasz WiśniewskiSenior analyst, case approver
- Marcus GrantMLRO, reporting officer
- Sophie GrantRelationship manager, not on the investigation
- Lena BaumannScreening analyst
- Daniel OseiQuality assurance, the fourth eye
Subtitles are on by default; switch them off or on in the player's captions menu.
Chapter 01 · Kevin · IT administrator
The data estate
The day starts with the data. The Knowledge Fabric catalogues where the bank's information comes from and reads each system where it lives. Kevin opens one source, checks who may read it, how good it is and what is built from it, then looks at the rules and the agents the platform runs.
Features shown
Knowledge Fabric
A catalogue of the bank's own systems, each read in place. Ten internal systems are listed, with owners, tiers, tags and a data-quality verdict.
Source State Graph
Everything built from one source drawn as a graph: the entities and links that come from it.
Lineage and quality
A table drawn in context with the tables around it and the processes it feeds, and its checks, all green or not.
Rules and agents
Detection and agentic rules, and a chain of agents that answers a relationship manager's question. Every agent here only proposes.
Scene by scene
-
Welcome
Welcome. This film follows one day in the Financial Crime Unit of Meridian Bank in Frankfurt, seen through AIState. Each person you meet does one real job.
-
Who this is, and what we do now
The day starts with Kevin, the I T administrator at Meridian Bank. He looks after where the bank's data comes from. Here, he will explore the data catalogue, open one source and the graph built from it, and then see the rules and agents the platform runs.
-
Kevin signs in to AIState
Kevin signs in to AIState.
-
He opens the Knowledge Fabric, the catalogue of where Meridian's data comes…
He opens the Knowledge Fabric, the catalogue of where Meridian's data comes from.
-
On the Data Assets card, ten tiles are Meridian's own systems, from…
On the Data Assets card, ten tiles are Meridian's own systems, from Authentication and Cards to Core banking, Customer master and Payments.
-
He opens Core banking
He opens Core banking. The platform profiles the source where it lives, which takes a moment.
-
The chips say it is live, read in place, with nothing copied
The chips say it is live, read in place, with nothing copied.
-
Access lists who may read it: the data owner, fraud operations and the second…
Access lists who may read it: the data owner, fraud operations and the second line.
-
Columns lists the fields in both tables, loans and accounts
Columns lists the fields in both tables, loans and accounts.
-
Data Quality shows thirty-one tests, all passed, none failed
Data Quality shows thirty-one tests, all passed, none failed.
-
Read by names the workspace that uses the source, Meridian Bank AG, FCU
Read by names the workspace that uses the source, Meridian Bank AG, FCU.
-
The Source State Graph draws everything built from this source: two hundred…
The Source State Graph draws everything built from this source: two hundred and seven entities and four hundred and sixty-four links. Each dot is an account, a person or a company.
-
In Explore, Kevin searches the whole catalogue for customers
In Explore, Kevin searches the whole catalogue for customers. Each result shows its owner, tags and row count.
-
He opens the Customers table: gold tier, owned by Miriam Schulte, in the KYC…
He opens the Customers table: gold tier, owned by Miriam Schulte, in the KYC domain, with just over four thousand rows.
-
The Schema tab lists its fourteen fields, from customer ID and legal name to…
The Schema tab lists its fourteen fields, from customer ID and legal name to risk rating and next KYC review.
-
Lineage draws the table in context
Lineage draws the table in context. Customers sits beside loans, accounts and cards. Together they feed the Customer 360 load, then the review scheduler, monitoring and screening, and finally the estate graph and a dashboard.
-
Data Quality lists eight checks, all green
Data Quality lists eight checks, all green. Ownership and tags names the owner, tier and domain.
-
Activity lists the recent edits to this record, with who made them and when
Activity lists the recent edits to this record, with who made them and when.
-
Under Govern, the Ontologies list holds the models the platform speaks
Under Govern, the Ontologies list holds the models the platform speaks. Kevin opens the one discovered from Meridian's own estate.
-
On the left is a graph of how its concepts link
On the left is a graph of how its concepts link. On the right are the schemas, each with a status.
-
Clicking a node opens an editor for it
Clicking a node opens an editor for it. Kevin cancels, because this is only a look.
-
Kevin leaves the catalogue for the Meridian Bank workspace
Kevin leaves the catalogue for the Meridian Bank workspace. Its overview shows open cases, deadlines and risk at a glance.
-
The Resolution tab holds look-alike records waiting for a person
The Resolution tab holds look-alike records waiting for a person. Two pairs are listed.
-
Nordvik Shipping UK Limited sits beside Nordvik Shipping AS from core…
Nordvik Shipping UK Limited sits beside Nordvik Shipping AS from core banking, and Helios Holding Limited beside Helios Trade G m b H. Nordvik had twelve records in nine systems; eleven already became one customer. This look-alike waits for a person.
-
Next, Settings, where the rules live
Next, Settings, where the rules live. Kevin searches for detection rules and opens them. Thirty published rules run on their own.
-
The second tab holds the agentic rules
The second tab holds the agentic rules. There are forty-six of them: chains of steps where agents assess, checks run and people approve.
-
He picks Source of wealth, for a PEP behind a 25 % holder
He picks Source of wealth, for a PEP behind a 25 % holder. Read from the top. Who holds 25 % or more. Is that person a PEP, on the EDD route. Then require source of wealth, the second line reviews, and business senior management approves.
-
Then he opens the Inventory, everything this deployment can call
Then he opens the Inventory, everything this deployment can call.
-
The Agencies tab lists chains of agents, among them case intake, financial…
The Agencies tab lists chains of agents, among them case intake, financial crime workup, investigation, monitoring, narrative, quality, screening and the KYC Case Advisor for relationship managers.
-
He opens the KYC Case Advisor
He opens the KYC Case Advisor. It answers what a customer may be told about a case, and whether a group company is an issue, from the file and the cases around it.
-
Studio opens it as a set of steps
Studio opens it as a set of steps. First comes its purpose: answer the relationship manager, and every agent step only proposes. Nothing is written on the case.
-
Step two shows the workflow as boxes: the file as it stands, the cases around…
Step two shows the workflow as boxes: the file as it stands, the cases around it, a case summary, group companies, what is still outstanding, and the note to the relationship manager.
-
On the Runs tab he picks a real case to test on, Aurelia Fintech Limited, and…
On the Runs tab he picks a real case to test on, Aurelia Fintech Limited, and types the question: what do I tell the customer regarding this case, and is there an issue with the group company Helios?
-
He presses Run
He presses Run. The first two steps are plain tool calls. They read the file as it stands, and the cases around it, in a fraction of a second.
-
Then the case summary step starts thinking
Then the case summary step starts thinking. The panel counts its thinking steps and tool calls as it goes, so nothing happens out of sight.
-
Now two branches run side by side
Now two branches run side by side. One maps the group companies and who is behind them. The other lists what is still outstanding for the customer.
-
Last, the relationship step pulls it together into an executive brief
Last, the relationship step pulls it together into an executive brief. Every agent here only proposes. A person reviews before anything is written.
-
The run finishes, with all eight steps completed
The run finishes, with all eight steps completed.
-
Every step can be opened, to see exactly what it read and what it returned
Every step can be opened, to see exactly what it read and what it returned. That is how Kevin shows where each answer comes from. Next, Ruth opens the morning.
Chapter 02 · Ruth · Team lead
The team lead's morning
Ruth runs the FCU team's daily work. She opens the team's workspace, reads the day at a glance, and looks into one customer, Nordvik, whose records come from many systems.
Features shown
Workspace overview
Cases open, priorities, the pipeline and the deadlines ahead, on one screen.
What we already know
Every earlier record that resolves to the customer, with its source.
Resolution
A look-alike record left for a person to decide, never merged by guesswork.
Related articles
News found under the name, each marked with its kind of risk and a check on whether it is about our customer.
Scene by scene
-
Who this is, and what we do now
Next is Ruth, the team lead. She runs the daily work of the F C U team. Here, she opens the team's workspace, reads the day at a glance, and looks into one customer, Nordvik.
-
Ruth starts her morning by signing in
Ruth starts her morning by signing in.
-
She opens the workspace Meridian Bank AG, FCU
She opens the workspace Meridian Bank AG, FCU.
-
The Overview shows the day at a glance
The Overview shows the day at a glance. Six cases are open, one critical and two high. The pipeline, the priorities and the deadlines ahead are all here, so she knows where the pressure is.
-
In the Cases tab: Nordvik, Aurelia, Kessler and Roth, Helios, Baltic and Ade…
In the Cases tab: Nordvik, Aurelia, Kessler and Roth, Helios, Baltic and Ade Balogun. Ruth opens Nordvik first.
-
At the top, What we already know
At the top, What we already know. Nordvik is not new to us, as ten earlier records are already matched to this customer. Below are the synopsis, Ruth as case agent, and the risk score.
-
In the Resolution tab, every record from every system that is this customer…
In the Resolution tab, every record from every system that is this customer is listed with its source. The small graph beside it shows how they connect.
-
One row is different, Nordvik Shipping, UK, Limited
One row is different, Nordvik Shipping, UK, Limited. It looks like our customer, but it is left for a person to decide.
-
Then Related Articles
Then Related Articles. Four news items were found under this name, each marked with its kind of risk.
-
Ruth opens the first one, an opinion piece rated adverse, high
Ruth opens the first one, an opinion piece rated adverse, high. It opens in a reader.
-
On the right, a check asks whether this is about our customer
On the right, a check asks whether this is about our customer. The answer is possibly. The country and industry match our record, but it is not enough to be sure, so a person decides.
-
She closes the reader and is back on the case with the morning picture in her…
She closes the reader and is back on the case with the morning picture in her head.
Chapter 03 · Priya · KYC analyst
Onboarding a customer
A retail current account for Ade Balogun is assigned to Priya. She reads what the bank already knows, what the agents have done, meets each requirement with a note under her name, and proposes the decision.
Features shown
Resolution and related cases
Two earlier records resolve to the same person, including an earlier declined application and its discounted near-match.
Agent timeline
What the investigation and screening agents did before the analyst touched the case, in order.
KYC case outcomes
Six requirements for the route; two met from case facts, four attested with a note.
A second person approves
Priya proposes CLEAR-CDD; she has no Approve button, and the case moves to the approver by itself.
Scene by scene
-
Who this is, and what we do now
Now meet Priya, a K Y C analyst. She checks new customers before the bank takes them on. Here, she picks up a new onboarding request and works through it.
-
Priya signs in to AIState, to pick up the request that has just been assigned…
Priya signs in to AIState, to pick up the request that has just been assigned to her.
-
Her bell shows two new messages
Her bell shows two new messages. One says a case has been assigned to her: a retail current account for Ade Balogun. She opens it.
-
At the top is a box called What we already know
At the top is a box called What we already know. Ade Balogun is not new to the bank. Two earlier records resolve to him: a dormant savings account and a declined card application from 2023.
-
On the Resolution tab there are three records: today's request, the 2023 card…
On the Resolution tab there are three records: today's request, the 2023 card application, and the dormant savings account, listed as A. Balogun. They share a date of birth, a national identification number and a device, so the system treats them as one person.
-
Under Related Cases sits the earlier application, closed in March 2023
Under Related Cases sits the earlier application, closed in March 2023. She opens it.
-
That application was declined on affordability, and its synopsis mentions a…
That application was declined on affordability, and its synopsis mentions a discounted PEP near-match on a namesake.
-
On its timeline is the screening step itself: a PEP near-match on a namesake…
On its timeline is the screening step itself: a PEP near-match on a namesake, marked discounted, with the reason written beside it. That decision carries forward, so nobody has to re-check the alias.
-
Back returns her to Ade's own case
Back returns her to Ade's own case.
-
Ade's own timeline shows what the agents have already done before Priya…
Ade's own timeline shows what the agents have already done before Priya touched the case.
-
Reading from the bottom, the investigation agent first locked the policy…
Reading from the bottom, the investigation agent first locked the policy: prohibition check clear, scope declared, sole trader, and the CDD checks loaded.
-
Next it classed the passport as the primary document, identity verified, with…
Next it classed the passport as the primary document, identity verified, with the registration certificate as secondary proof of address.
-
The screening agent found nothing on the resolved person and carried the 2023…
The screening agent found nothing on the resolved person and carried the 2023 decision forward.
-
Last, the route: CDD, with no simplified due diligence
Last, the route: CDD, with no simplified due diligence.
-
Back on the Overview, a strip called KYC case outcomes says two of six…
Back on the Overview, a strip called KYC case outcomes says two of six requirements are met.
-
Opened, it lists the CDD requirements
Opened, it lists the CDD requirements. Two are met from the case facts: screening in the last six months, and no unresolved sanctions match. The other four need Priya to attest.
-
For identity she attests with a note: Personalausweis, primary source
For identity she attests with a note: Personalausweis, primary source. The note is kept against the requirement, under her name.
-
For the address she records the registration certificate, the…
For the address she records the registration certificate, the Meldebescheinigung.
-
For beneficial owners, this is an individual with no other owner, so she…
For beneficial owners, this is an individual with no other owner, so she notes exactly that.
-
Last, source of funds: salary, with payslips seen
Last, source of funds: salary, with payslips seen. The strip now says six of six requirements are met, and Propose CLEAR-CDD turns green.
-
She proposes CLEAR-CDD and gives a short reason: screening came back nil
She proposes CLEAR-CDD and gives a short reason: screening came back nil.
-
The outcome now sits on the record as proposed, waiting for a second person
The outcome now sits on the record as proposed, waiting for a second person.
-
And the header has changed by itself
And the header has changed by itself. The case agent is now Tomasz Wiśniewski, the senior analyst who approves, and his bell has just rung.
-
Priya has no Approve button
Priya has no Approve button. The strip says outcomes are approved by a case approver or the MLRO, never the person who proposed them. She cannot approve her own work.
Chapter 04 · Thomasz Wiśniewski · Senior analyst
Approval and ownership
The approver decides what the team proposes. Thomasz approves Priya's decision on Ade Balogun, then takes a harder corporate case, Aurelia Fintech, follows its ownership, raises the route to enhanced due diligence and escalates to the MLRO.
Features shown
Approval by name
The outcome reads approved by name, with the time, on the audit trail.
Ownership hierarchy
The chain from the company to its ultimate owners, with the evidence behind each holding.
Route raised by a person
Enhanced due diligence raises the requirement list; a person raised it, and the case says so.
Escalation
The case is handed to the MLRO with the reason recorded.
Scene by scene
-
Who this is, and what we do now
Next is Thomasz Wiśniewski, a senior analyst. He approves what the team proposes. Here, he approves Priya's decision, then studies a harder case, Aurelia Fintech, and escalates it to the M L R O.
-
Priya has proposed her decision on Ade Balogun, and the case has moved on by…
Priya has proposed her decision on Ade Balogun, and the case has moved on by itself. Now it is Tomasz's turn.
-
His bell shows new items
His bell shows new items. At the top is an approval request: Approve CLEAR-CDD on Ade's case, sent by Priya. Below it, the case itself is assigned to him.
-
He opens the request, and Ade Balogun's retail onboarding case comes up
He opens the request, and Ade Balogun's retail onboarding case comes up.
-
The strip called KYC case outcomes says CLEAR-CDD is proposed, with all six…
The strip called KYC case outcomes says CLEAR-CDD is proposed, with all six requirements met. Tomasz opens it to see what Priya recorded.
-
The decision is waiting for approval
The decision is waiting for approval. An approval window opens with an optional note, and he confirms.
-
Now it reads approved by Thomasz Wiśniewski, with the time
Now it reads approved by Thomasz Wiśniewski, with the time. Approved by name, on the audit trail, and Priya's bell now says CLEAR-CDD approved.
-
Next is Aurelia Fintech
Next is Aurelia Fintech. From the workspace, he opens the Cases tab and picks the corporate onboarding for Aurelia Fintech Limited.
-
The box at the top says what we already know
The box at the top says what we already know. Caspian Ventures, a proposed sixty-eight percent holder, shares an address in Majuro and a director with a party on another case, Helios Trade.
-
On the Hierarchy tab, Aurelia Holdings owns the company in full
On the Hierarchy tab, Aurelia Holdings owns the company in full. Mark Ellison holds thirty-two percent, and Caspian Ventures sixty-eight. Caspian's source is in red: insufficient data, no public register in the Marshall Islands.
-
Beneath Caspian sits Aurimas Petrauskas, who owns it entirely
Beneath Caspian sits Aurimas Petrauskas, who owns it entirely. That comes from a certified share register returned by the Reach-out agency. He is the spouse of the PEP director.
-
The Timeline lists everything that has happened on the case, newest first
The Timeline lists everything that has happened on the case, newest first.
-
The Investigation agency planned the work
The Investigation agency planned the work. The Corporate Structure agency found Caspian verified only by the customer's own chart. Then the Reach-out agency came back with the share register naming Petrauskas.
-
Back on the Overview, Tomasz opens the KYC case outcomes strip again
Back on the Overview, Tomasz opens the KYC case outcomes strip again. This time nothing is recorded yet.
-
None of the requirements are met
None of the requirements are met. The outcomes he can record are listed underneath.
-
He raises the route to enhanced due diligence, and gives the reason: a PEP…
He raises the route to enhanced due diligence, and gives the reason: a PEP behind the sixty-eight percent holder.
-
The route now reads EDD, raised by a person
The route now reads EDD, raised by a person. The list grows to eight requirements, including ownership verified and source of wealth of the beneficial owner.
-
Then he records ESCALATE-COMPLIANCE
Then he records ESCALATE-COMPLIANCE. The reason is simple: there is no register to check for the Marshall Islands, so the entity cannot be resolved.
-
Saved
Saved. The escalation hands the case to the MLRO. The case agent in the header now reads Marcus Grant, and his bell has just rung.
Chapter 05 · Marcus Grant · MLRO
The MLRO decides
The escalation lands with the money-laundering reporting officer. Marcus sees how Aurelia links to a sanctions case through a shared director, asks the assistant who is really behind the case, declines a request for a provisional clear, and resolves the escalation.
Features shown
Linked cases
A restricted sanctions case is visible to the MLRO and linked through a shared director.
The assistant shows its working
Who is behind the case, step by step, with a gap it flags rather than hides.
A decision with a reason
A request is declined with a note; the escalation is resolved and goes back to the person who raised it.
Blocking requirements
Nobody can clear the case early: the provisional clear stays greyed out until the blocking requirements are met.
Scene by scene
-
Who this is, and what we do now
Now meet Marcus Grant, the M L R O, the money-laundering reporting officer. He decides the hardest cases. Here, he picks up Tomasz's escalation on Aurelia Fintech.
-
Tomasz's escalation has just landed with Marcus, so he signs in to pick it up
Tomasz's escalation has just landed with Marcus, so he signs in to pick it up.
-
His bell shows what is waiting: Tomasz's escalation, the case assigned to…
His bell shows what is waiting: Tomasz's escalation, the case assigned to him, and Sophie's request for a provisional clear.
-
He opens Aurelia Fintech
He opens Aurelia Fintech. A banner says it is linked to a sanctions case on Helios Trade, through a shared director, Ilona Vaitkus.
-
On the Related Cases tab, the Helios Trade case is listed: open, with a…
On the Related Cases tab, the Helios Trade case is listed: open, with a synopsis about sanctions on the intermediate parent. Marcus may see this restricted case. Other staff will not even see that it exists.
-
The Hierarchy tab draws the ownership chain
The Hierarchy tab draws the ownership chain. Caspian Ventures holds 68 percent, with insufficient data behind it. Mark Ellison holds 32. Aurimas Petrauskas stands behind Caspian.
-
Marcus opens the case's chat panel and picks the suggested question: who is…
Marcus opens the case's chat panel and picks the suggested question: who is really behind this case, and what else do they touch?
-
The assistant now reads the case, its ownership graph and its links, showing…
The assistant now reads the case, its ownership graph and its links, showing each step it takes. Here it works through a thinking step and several tool calls, and it takes only a few seconds.
-
It shows its working in five steps: the immediate owner, the ultimate owners…
It shows its working in five steps: the immediate owner, the ultimate owners, a source gap, other touchpoints and a cross-case overlap, plus a small ownership graph and the one other case they touch.
-
Its closing lines name one related case, where Ilona Vaitkus is shared as a…
Its closing lines name one related case, where Ilona Vaitkus is shared as a director, and flag the gap: Caspian's 68 percent has no public register behind it, only the customer's own structure chart.
-
Behind this case, the owners resolve to Aurimas Petrauskas at 68 percent…
Behind this case, the owners resolve to Aurimas Petrauskas at 68 percent, through Caspian and Aurelia Holdings, and Mark Ellison at 32 percent. Ilona Vaitkus is a director of Caspian. Rasa Petrauskienė, a director of Aurelia, is linked as spouse of Aurimas.
-
Back on the Overview, further down, is the squad discussion
Back on the Overview, further down, is the squad discussion. Sophie's comment is there: can she have a provisional clear for a pending payment? Marcus can approve or decline.
-
He declines it, typing the reason: pending the client providing source of…
He declines it, typing the reason: pending the client providing source of wealth.
-
The comment now shows declined, by Marcus Grant, with his note beneath it
The comment now shows declined, by Marcus Grant, with his note beneath it.
-
Next, the case outcomes strip
Next, the case outcomes strip. The escalation Tomasz recorded is still open, with his reason: unable to resolve entity, as no register for Marshall Islands. Below are the EDD requirements, none of the eight met yet.
-
Marcus resolves the escalation
Marcus resolves the escalation. He writes: approved subject to EDD, and approval does not remove the outstanding UBO source of wealth requirement.
-
Resolved
Resolved. The outcome now reads resolved by Marcus Grant, and the case goes back to the person who escalated it: the case agent in the header is Thomasz again.
-
Provisional CLEAR-EDD stays greyed out, because blocking requirements are not…
Provisional CLEAR-EDD stays greyed out, because blocking requirements are not met. Nobody can clear the case early.
-
Back in the workspace, the Cases tab lists the open cases
Back in the workspace, the Cases tab lists the open cases. Helios Trade, rated critical, has Marcus as its lead.
-
Now the restricted Helios case
Now the restricted Helios case. Its summary records sanctions on the intermediate parent, Helios Holding, and says the detail is held with the MLRO only.
-
In the outcomes strip, two holds are open: block sanctions, and SAR…
In the outcomes strip, two holds are open: block sanctions, and SAR consideration. One of the six requirements is met, that every party was screened; no unresolved sanctions match on any party is not.
-
The Hierarchy tab shows Helios Holding at 100 percent, with two senior…
The Hierarchy tab shows Helios Holding at 100 percent, with two senior managing officials: Ilona Vaitkus, who also sits on Caspian in the Aurelia case, and Matthias Brandl.
-
Beneath it sit three holders: Marenco Nominees in Cyprus at 40 percent…
Beneath it sit three holders: Marenco Nominees in Cyprus at 40 percent, Pelagos Holdings at 35, and Daugava Investments at 25. Behind Marenco is Marenco Corporate Services, and behind Daugava are two Latvian individuals, Oleg Marchenko at 20 and Ingrida Ozola at 5.
-
Last, Nordvik Shipping, a periodic review rated high
Last, Nordvik Shipping, a periodic review rated high. The banner says it is not new: ten earlier records, from the CRM archive to core banking, were resolved to this one party.
-
On Contained Items, the second line's note records the adverse media as read…
On Contained Items, the second line's note records the adverse media as read, relied on and discounted, against the relationship, and sets a ninety-day monitoring clock. Below it are the customer master's notes and the credit committee's approval. That completes Marcus's part of the day.
Chapter 06 · Sophie Grant · Relationship manager
Who may see what
Sophie looks after the client but is not on the investigation. She reads the MLRO's answer, then the film shows what she can and cannot see.
Features shown
A reply on the record
The MLRO's answer to her request, with the reason.
A case that is simply not there
A restricted case is not greyed out or locked: for her it does not exist.
A link without a name
The linked case is not named, and related cases stay empty. She learns that something exists, never what.
Case not found
Opening it by its address gets the same answer as a case that does not exist.
Scene by scene
-
Who this is, and what we do now
Sophie Grant is the relationship manager. She looks after the client, but is not on the investigation. Here, she reads Marcus's answer, and we see what she is allowed to see.
-
Sophie signs in to read Marcus's answer
Sophie signs in to read Marcus's answer.
-
Her bell shows it
Her bell shows it. Marcus Grant, the MLRO, declined her comment.
-
She had asked for a provisional clear on a pending payment
She had asked for a provisional clear on a pending payment. His reply says to wait for Source of Wealth. So the answer is no.
-
Now she checks what else she can see, starting with the workspace Cases tab
Now she checks what else she can see, starting with the workspace Cases tab.
-
Five cases are listed
Five cases are listed. The Helios case is not among them. It is not greyed out or locked. For Sophie, it is simply not there.
-
She goes back into the Aurelia case
She goes back into the Aurelia case.
-
A note says this case is linked to a matter she cannot see
A note says this case is linked to a matter she cannot see. It does not name that matter.
-
Related Cases is empty
Related Cases is empty. She learns that something exists, never what.
-
If she tried to open the Helios case by its address, the platform would…
If she tried to open the Helios case by its address, the platform would simply answer: Case not found. It never confirms that a restricted case exists, and her attempt is written to the case's audit trail. The restricted case stays out of sight. The wall holds.
Chapter 07 · Thomasz Wiśniewski · Senior analyst
The case in time, and a report
The escalation has come back resolved. Thomasz reads the case in time, asks the assistant how it evolved and why each step was taken, then opens Kessler and Roth, a customer refusing to give ownership information, and reports a concern to the second line.
Features shown
Timeline
Dated items over about five weeks: case changes, risk levels and outcomes.
Case evolution
The assistant reads the whole case record and explains how and why it changed, week by week.
Questions to the customer
Requests for information sent to the customer, newest first.
Suspicious activity report
The form goes to the nominated officer only and must not be discussed with the customer; the grounds and the subjects are recorded.
Scene by scene
-
Who this is, and what we do now
Back with Thomasz. The M L R O has answered his escalation. Here, he reviews how the Aurelia case evolved, then reports a concern on Kessler and Roth to the second line.
-
The MLRO has dealt with the escalation, so Tomasz signs in to see what has…
The MLRO has dealt with the escalation, so Tomasz signs in to see what has come back to him.
-
His bell lists the news
His bell lists the news. Marcus Grant has resolved the escalation on Aurelia, the case is assigned back to Tomasz, and a push mentions Kessler and Roth.
-
Aurelia Fintech opens with a note that Caspian Ventures shares an address and…
Aurelia Fintech opens with a note that Caspian Ventures shares an address and a director with another case. Eleven subjects, six exhibits, and a risk of forty-one, medium.
-
On the Timeline tab are fifty-four dated items over about five weeks: case…
On the Timeline tab are fifty-four dated items over about five weeks: case changes, risk levels, outcomes, tasks, activities and evidence, with a review due on the twenty-first.
-
Then he opens the case chat and picks the first suggestion: show me how this…
Then he opens the case chat and picks the first suggestion: show me how this case evolved, and why each step went the way it did.
-
The assistant now reads the whole case record, calling tools and thinking…
The assistant now reads the whole case record, calling tools and thinking through each step. That takes up to a minute.
-
At the end of its answer are follow-up questions, and a note that no stored…
At the end of its answer are follow-up questions, and a note that no stored snapshot comparison exists yet, so the evolution is built from timestamps on the case.
-
The route to EDD came from a politically exposed person behind the…
The route to EDD came from a politically exposed person behind the sixty-eight percent holder, not a plain list hit.
-
Below is the case evolution: eleven subjects, six documents and all three…
Below is the case evolution: eleven subjects, six documents and all three tasks done, across seven weekly chapters. Each circle is a subject, placed at the chapter it joined.
-
Six steps explain why: the case opened from intake, subjects were screened…
Six steps explain why: the case opened from intake, subjects were screened, and risk came out medium, forty-one.
-
Back at the bell, Tomasz picks the push about Kessler and Roth
Back at the bell, Tomasz picks the push about Kessler and Roth.
-
Kessler and Roth GmbH is a periodic review, risk ten, low
Kessler and Roth GmbH is a periodic review, risk ten, low. The synopsis says the customer refuses mandatory information, and replied that it will not provide the share register, on principle, because the previous extract was accepted.
-
On the Questions tab are three requests for information sent to the customer…
On the Questions tab are three requests for information sent to the customer, newest first. The latest asks why the older register extract is not enough, and the answer is that they will not provide it. The first confirmed Hans Weber as a significant shareholder. All three were answered through the portal.
-
From the More menu he opens Second line, where suspicious activity reports…
From the More menu he opens Second line, where suspicious activity reports are kept. This case has none yet, so he starts a new SAR.
-
The form reminds him it goes to the nominated officer only, and must not be…
The form reminds him it goes to the nominated officer only, and must not be discussed with the customer.
-
He writes what he saw: the customer refuses mandatory UBO information, the…
He writes what he saw: the customer refuses mandatory UBO information, the certified share register for Hans Weber's sixty-one percent, so a prohibition assessment is needed.
-
Then he picks the two subjects, Kessler and Roth, and Hans Weber
Then he picks the two subjects, Kessler and Roth, and Hans Weber.
-
He sends it to the second line
He sends it to the second line. The SAR now shows as Considering, raised by Tomasz, with the grounds he wrote and his two chosen subjects marked.
-
Below is a narrative box, written for the FIU, the financial intelligence…
Below is a narrative box, written for the FIU, the financial intelligence unit, and the actions Start drafting, Send for decision and Withdraw are ready for the next step.
Chapter 08 · Lena Baumann · Screening analyst
Screening
Lena checks the bank's customers against sanctions and watch lists and decides what each hit really means. She reads last night's screening in plain words, reviews the overnight exceptions, and records a decision.
Features shown
Screening history
Thirty days of screenings, hits and alerts; every screening is a row with a disposition and a rationale.
Overnight exceptions
Records that changed at source overnight, such as a new date of birth or alias, and a change that can be reverted.
A decision with a reason
A hit from the bank's own sanctions list is confirmed as the same subject, with the reason on the record.
It carries forward
The decision holds while the hits stay the same, and the counts move by one.
Scene by scene
-
Who this is, and what we do now
Now meet Lena Baumann, a screening analyst. She checks the bank's customers against sanctions and watch lists. Here, she reads last night's screening, and decides what one hit really means.
-
She starts her morning by looking at last night's screening
She starts her morning by looking at last night's screening.
-
She asks the assistant for the screening history, in plain words, and presses…
She asks the assistant for the screening history, in plain words, and presses enter.
-
The assistant works out which view answers the question
The assistant works out which view answers the question.
-
Here is the screening history
Here is the screening history. The tiles on top give the last thirty days: screenings, total hits, alerts, how many were cleared, how many escalated, and how many identities are unchanged. One tile, changed since last screening, is highlighted for review.
-
Below, every screening is a row, with a Disposition and a Rationale column
Below, every screening is a row, with a Disposition and a Rationale column. On page two, Ade Balogun was discounted, because all seven hits are below the confidence threshold of seventy-five percent. Hovering over the row opens a card with every hit, its list and its score.
-
Now the overnight exceptions
Now the overnight exceptions. She opens the changed tile, and three customers appear, each marked record changed.
-
Karim Ahmed has a new date of birth, taken from Companies House
Karim Ahmed has a new date of birth, taken from Companies House. It now matches a list entry.
-
Ostmark Trading has a new alias, Ostmark Handels GmbH
Ostmark Trading has a new alias, Ostmark Handels GmbH.
-
And Verity Holdings had its registration number corrected at source
And Verity Holdings had its registration number corrected at source.
-
On Verity she presses Revert
On Verity she presses Revert. A wrong change at source can be undone, and the undo is on the record too, with her name and the time.
-
She goes back to the full list and returns to page two
She goes back to the full list and returns to page two.
-
Next, Helios Holding
Next, Helios Holding. She opens the row and screens it again against the lists.
-
The hit comes from Sanctions determinations, the bank's own list kept by the…
The hit comes from Sanctions determinations, the bank's own list kept by the MLRO. It scores one hundred, and nothing beyond the name contradicts it.
-
She chooses Record decision, and picks Confirm: this is the same subject
She chooses Record decision, and picks Confirm: this is the same subject.
-
She gives her reason: name, country and parent relationship agree
She gives her reason: name, country and parent relationship agree. A decision always carries a reason, so that anyone can read later why it was made.
-
The decision is recorded, confirmed by Lena, and it carries forward while the…
The decision is recorded, confirmed by Lena, and it carries forward while the hits stay the same. She sees the hit, but not how Helios is linked to the bank's customers. That stays with the MLRO.
-
Back in the history, Helios now shows as Confirmed at the top, and the counts…
Back in the history, Helios now shows as Confirmed at the top, and the counts have moved by one. Last night's screening is dealt with.
Chapter 09 · Ruth · Team lead
The afternoon: the whole estate
Ruth is back for three checks before the day ends. The Estate graph shows every customer and connection across the workspaces. A red alert leads her to one company, its case and its changes; then an incident on another case.
Features shown
Estate graph
The best-connected entities across twelve investigations, with the alerts pushed to her on the left.
Perpetual KYC
Changes at the customer, such as a move of country and of operations, listed as they happen.
An answer as a widget
The assistant builds the verification cohort as a chart and counts, not a paragraph.
An incident on the timeline
A trade executed while a case was open, found on the case's timeline of dated events.
Scene by scene
-
Who this is, and what we do now
It is the afternoon, and Ruth is back. Here, she checks the whole estate, follows a red alert to Baltic, and reads an incident on Aurelia.
-
She signs back in, with three things to check before the day ends, starting…
She signs back in, with three things to check before the day ends, starting with the whole estate.
-
She opens the Estate graph
She opens the Estate graph. It shows the 1,480 best-connected of 4,990 entities, drawn from twelve investigations in five workspaces.
-
On the left, Pushed to you lists today's alerts
On the left, Pushed to you lists today's alerts. The red one is Baltic.
-
She picks Baltic
She picks Baltic. The canvas jumps to it and the details panel opens: an organization, a customer, with 34 connections and three ultimate owners.
-
Closed again, the canvas shows Baltic's neighbourhood
Closed again, the canvas shows Baltic's neighbourhood. Baltic is the large dot in the middle, because it has the most links. Every other dot is something directly connected to it.
-
Each line carries a label that says what the link is
Each line carries a label that says what the link is. Owns and directs tie the company to its owners and directors, and located at ties it to its address. Transacted with marks the trading partners, such as Tampere Power Modules, Gdansk Elektronika and Brno Konektory.
-
Vanguard Precision Dynamics and Apex Automation Components sit on the same…
Vanguard Precision Dynamics and Apex Automation Components sit on the same canvas, and so does Kenya, the country Baltic's operations moved to.
-
From the rail she opens the Meridian workspace, then its Cases tab, and picks…
From the rail she opens the Meridian workspace, then its Cases tab, and picks the Baltic review.
-
The case opens with What we already know
The case opens with What we already know. Baltic is in Kenya, a country under increased monitoring. It trades with four counterparties there, with the payment totals listed. And another Meridian customer, Elbe Kreditbank, trades with two of them.
-
The synopsis says it in one line: operations moved to Kenya, and two of the…
The synopsis says it in one line: operations moved to Kenya, and two of the four counterparties are also Elbe Kreditbank's.
-
Recent activity lists what was found, and the Customer card opens the company…
Recent activity lists what was found, and the Customer card opens the company page.
-
The company page shows 34 connections, one case and three ultimate owners…
The company page shows 34 connections, one case and three ultimate owners, the largest holding 38.5 percent. Below, all three owners are traced.
-
On the pKYC tab are the changes
On the pKYC tab are the changes. The country moved from Lithuania to Kenya, and principal operations now read Kenya. Both come from Companies House, so nobody had to notice by hand.
-
Next, the owners
Next, the owners. Ruth starts a new conversation and asks for the entity verification cohort for the Meridian workspace.
-
She presses Enter, and the assistant looks up the cohort and builds the…
She presses Enter, and the assistant looks up the cohort and builds the answer as a widget.
-
The answer is a widget
The answer is a widget. Of 2,412 records, 1,471 are verified from a primary source and 212 through evidence on a related node. The other 729 have gone to reach-out. There, 271 responses are back, 41 are in process, 18 are exceptions, and 399 are still pending, with 30 days left.
-
Last, the bell
Last, the bell. A push from 15:00 reports an incident, INC-26-0088, and it opens Aurelia's case.
-
She opens the Timeline of Aurelia's case: fifty-five dated events, in time…
She opens the Timeline of Aurelia's case: fifty-five dated events, in time order, covering case changes, risk levels, tasks and evidence.
-
Here is the entry
Here is the entry. The monitoring agency recorded at 10:31 a foreign exchange trade, executed while the case stood at insufficient data. A provisional clear was refused and an incident raised. The platform caught a trade against a case that was not cleared, and nobody had to spot it.
Chapter 10 · Daniel Osei · Quality assurance
Quality assurance
Daniel is the fourth eye: the person who checks finished work before it stands. A pushed alert leads him to the KYC file on Aurelia Fintech, which he reviews field by field.
Features shown
An alert read from the graph
A connected party with no screening edge, found in the graph and not in documents.
Risk from rules
The score is worked out from written rules, and the explanation always equals the score.
The fourth-eye checklist
Every field the analyst filled in is listed with what was recorded, to be passed or marked as a finding.
A finding changes the result
A single major finding is enough to change the score; set back to pass, it returns.
Scene by scene
-
Who this is, and what we do now
Last to sign in is Daniel Osei, from quality assurance. He is the fourth eye: he checks finished work before it stands. Here, he reviews the K Y C file on Aurelia Fintech.
-
Daniel signs in
Daniel signs in.
-
His bell holds two messages
His bell holds two messages. One was pushed at half past three, before Daniel samples: a connected-party node on Aurelia Fintech has no screening edge. It was read from the graph, not from documents.
-
Aurelia's case opens on its overview
Aurelia's case opens on its overview. It is the corporate onboarding, linked to a sanctions case through a shared director. Below sits the customer card: Aurelia Fintech Ltd, with one screening hit.
-
From the customer card he opens the company page itself, where the whole…
From the customer card he opens the company page itself, where the whole customer is gathered in one place.
-
At the top, the KYC review banner reads: waiting for the fourth eye
At the top, the KYC review banner reads: waiting for the fourth eye. The analyst has submitted, and the fourth eye is next in line.
-
Underneath, the risk is worked out from rules: forty-five, medium
Underneath, the risk is worked out from rules: forty-five, medium. One sanctions-list match adds the points, and two rules could not be judged for lack of data. Two ultimate owners are traced, the largest holding sixty-eight percent.
-
He presses Review as fourth eye
He presses Review as fourth eye. The KYC review tab opens with the checklist: zero of ten fields checked, and a pass mark of ninety-five. Finish QC is ready for when he is done.
-
Every field the analyst filled in is listed with what was recorded: identity…
Every field the analyst filled in is listed with what was recorded: identity, financial, risk and compliance, and other. For each one Daniel can mark Pass, Major, Minor, Housekeeping or not applicable.
-
He ticks the legal name as a pass, and the score reads one hundred
He ticks the legal name as a pass, and the score reads one hundred.
-
The registration number passes as well
The registration number passes as well. Marking the source of wealth as a major finding drops the score to ninety-four, under the pass mark, so the sample fails.
-
Set back to pass, the score returns to one hundred
Set back to pass, the score returns to one hundred. A single major finding is enough to change the result.
-
Below the checklist, a trail records that Thomasz Wiśniewski submitted this…
Below the checklist, a trail records that Thomasz Wiśniewski submitted this cycle, and every value is listed with the source it came from.
Chapter 11 · Marcus Grant · MLRO
Which cases lean on each other
One last question for the MLRO: which of the bank's cases lean on each other? He looks at the case book, then asks the assistant the same question in plain words.
Features shown
Book of cases
Every case a dot on a ring; a line joins two cases that share something.
The strongest joins
Which subjects, addresses and intermediaries two cases share, case by case.
The assistant, as the person asking
It reads the case book with only his access, and every step is shown.
An answer you can act on
Tiles, a table of case pairs and a plain-words reading of where the weight is.
Scene by scene
-
Who this is, and what we do now
One last time, we are with Marcus. He has one more question: which of the bank's cases lean on each other? Here, he looks at the case book, then asks the assistant in plain words.
-
Marcus signs in again, with one more question: which of the bank's cases lean…
Marcus signs in again, with one more question: which of the bank's cases lean on each other?
-
He opens Workspaces and goes into Meridian Bank AG, the Financial Crime…
He opens Workspaces and goes into Meridian Bank AG, the Financial Crime Unit's workspace, where all of today's cases live.
-
The overview shows six open cases and seven in all
The overview shows six open cases and seven in all. Marcus goes to the Book of cases tab.
-
Every case is a dot on the ring, seven in all
Every case is a dot on the ring, seven in all. A line joins two cases that share something, and there are five lines.
-
The strongest joins Ade Balogun's card application and his retail onboarding…
The strongest joins Ade Balogun's card application and his retail onboarding: three subjects, twelve links.
-
Below, each case has its own constellation of subjects and links, and each…
Below, each case has its own constellation of subjects and links, and each card counts its connections to other cases.
-
Back at the ring, the thinner lines matter too
Back at the ring, the thinner lines matter too. Kessler and Roth and Nordvik share a freight forwarder, Hanseatic Freight Services. Baltic links to both, and Aurelia ties to Helios.
-
Now Marcus asks the same question in plain words
Now Marcus asks the same question in plain words. He opens Conversations and starts a new one.
-
He limits it to the Meridian workspace, so it reads only the case book
He limits it to the Meridian workspace, so it reads only the case book.
-
He types: which cases are inferring from each other today, and where is the…
He types: which cases are inferring from each other today, and where is the weight? Then he sends it.
-
While the assistant works, it reads the case book as Marcus himself, with…
While the assistant works, it reads the case book as Marcus himself, with only his access, and every step it takes is shown.
-
First the tiles arrive: three cases with live overlaps, a strongest pair with…
First the tiles arrive: three cases with live overlaps, a strongest pair with two shared entities, and a next pair with one.
-
Then a table of case pairs and what links them
Then a table of case pairs and what links them. Ade Balogun and an address in Offenbach carry two shared entities, Hanseatic Freight Services one, and Aurelia Fintech has no overlap.
-
In words, the answer says the weight is concentrated on one hub case, with…
In words, the answer says the weight is concentrated on one hub case, with the Ade Balogun case its strongest feeder.
-
That was the day: the data estate, resolution, onboarding and ownership…
That was the day: the data estate, resolution, onboarding and ownership, sanctions, who may see what, screening and pKYC, the SAR, the incident, quality assurance, and now the network of cases. Everything checked within your policy.