EU KYC / KYB onboarding compliance

Audit-grade EU onboarding decisions, with citations attached.

Regulated-Admin turns manual KYC / KYB review into a human-approved compliance packet for EU institutions that need faster onboarding without dropping evidentiary quality.

  • Every recommendation carries the regulatory citation it was decided on
  • Human-in-the-loop sign-off is built in — nothing auto-finalises
  • Built for EU AML / 5AMLD / 6AMLD / FATF / sanctions workflows

How it works

From raw documents to a decision you can defend.

Three stages carry a counterparty from an inbox of PDFs to a signed, cited packet — with an immutable audit trail behind every step.

01

Document intake

Certificate of incorporation, UBO declaration, VAT registration and bank details are read out of the raw bundle into one structured counterparty record.

PDF · scanned text → record

02

Rule evaluation with citations

The record is checked against a versioned EU AML rule pack — 6AMLD, 5AMLD, FATF and sanctions. Every result comes back with the exact rule it was decided on.

Versioned rule pack · per-rule citation

03

Human review packet & audit trail

A cited recommendation routes to your reviewer queue with SLA tracking. Their sign-off produces a packet — JSON & PDF — behind a hash-chained, tamper-evident audit trail.

HITL queue · hash-chained trail

The economics

Keep the evidence. Drop the labor cost.

Manual KYC / KYB review today

€200–500

per onboarding

Reviewer hours spent reading documents, running screens by hand, and assembling the evidence trail before a decision can be defended.

Design-partner pilot

€30

per onboarding · first 500

A cited, human-signed decision packet for a fixed per-onboarding price while you prove the workflow against your own volume.

4–10×

savings band on review labor per onboarding

  • Shorter review time
  • Cleaner audit trail
  • Easier escalation

See it decide

Watch a real counterparty go through the packet.

  1. 1

    Run the TechVenture demo

    A realistic German GmbH — two UBOs, VAT number, incorporation and bank documents — enters intake.

  2. 2

    See the packet output

    Watch rules evaluate with citations and a Claude-drafted recommendation assemble into a compliance packet.

  3. 3

    Review the cited audit trail

    Open the JSON & PDF packet and the hash-chained audit trail — every claim tied back to its rule.

regulated-admin — demo

$ python -m regulated_admin.demo.run_demo
> intake TechVenture GmbH · 4 documents parsed
> rules 6AMLD · 5AMLD · FATF · Sanctions [cited]
> reasoning recommendation drafted → APPROVE
> review routed to HITL queue · awaiting sign-off
✓ compliance_packet.pdf
✓ compliance_packet.json
✓ audit_trail.json · hash-chain verified

Request a pilot

Put it against your own onboarding volume.

Tell us where your review time goes today. We'll map the packet flow to your stack and set clear success metrics for the pilot.

  • Fixed €30 per onboarding for your first 500
  • Your reviewers stay in control of every final decision
  • A cited audit trail your regulators and auditors can follow

Start a pilot conversation

15 minutes to see the packet against your onboarding flow.

We'll only use these details to scope your pilot. No spam.

Questions

What compliance leaders ask first.

What types of onboarding do you support?

EU counterparty and business onboarding — KYC and KYB — for banks, e-money institutions, PSPs and regulated crypto firms. The engine reads the document bundle and evaluates it against an EU AML rule pack.

How does human review work?

Nothing auto-finalises. The engine drafts a cited recommendation and routes it to your reviewer queue with SLA tracking. A reviewer's sign-off is what produces the final, audited decision.

How fast can a pilot start?

The workflow is demoable today on a live sample counterparty. A pilot begins once we've confirmed your volume, jurisdictions and success metrics — then runs against your first 500 onboards.

Can this be used for per-check API workflows?

The pilot is priced per onboarding. Per-check API channels are on the packaging path after a pilot — start with per-onboarding, then per-seat for ops teams, then per-check for API.