Agentic AI for KYC, AML and EDD operations.
The same stack that runs your rails can run the operations around them. The KYC rail gives you the checks. This is the ops layer around them: alert triage, onboarding workflows, due diligence files, policy questions and case routing, run by governed agents with a human approving anything that matters.
What the agents do
- AI-assisted alert triage and AML case support, so analysts open the alerts that deserve an analyst.
- KYC onboarding workflow automation, so document chasing and file assembly stop consuming the team.
- Enhanced due diligence structuring, so an EDD file arrives written up rather than started from scratch.
- Secure internal knowledge, so policy and procedure questions are answered from your own documents.
- Integration support, so the agents read and write in the systems your compliance team already uses.
The governance model
For a regulated compliance function the governance is the product, so it is stated on its own terms.
- Role-based access, so an agent sees what the role it acts for is allowed to see.
- Structured audit trails, so every step an agent took is reconstructable after the fact.
- Human-in-the-loop approval on sensitive steps, so no filing, decision or escalation leaves without a person.
- GDPR-conscious data boundaries, so personal data stays inside the boundary you set for it.
The EU AI Act, and the date after it
Obligations for the Annex III high-risk categories, which cover AI used in regulated workflows of this kind, apply from 2 December 2027.
Readiness is an engagement in its own right: Annex IV technical documentation, the governance framework around the deployment, and getting the audit trail into a state an examiner can read.
Source: Regulation (EU) 2024/1689 (the AI Act). Read the regulation on EUR-Lex. Dates verified 2026-08-18.
How an engagement runs
- Discovery call, where the workflow and the data boundary are agreed.
- Pilot on one workflow: pilots on the compliance-automation engagement typically run 2 to 4 weeks.
- Deploy, then scale to further workflows under the same governance.
Engagements are scoped in discovery and priced per engagement. There is no tier list and no band: the scope of the workflow sets the price, and pilots on the compliance-automation engagement typically run 2 to 4 weeks.
Deployed with Nordic regulated institutions. References available under NDA.
Where it sits in the stack
This is the ops layer on the compliance rail, not a separate product pillar. The KYC rail runs the checks; this runs the operations around them. It is also summarised on the technology page.