Verkflo is in early access. Book a demo

Compliance operations automation, run from your procedures

Most compliance teams already have their procedures written down. Verkflo turns each one into a versioned agent that does the routine steps and asks a named reviewer for the rest.

Book a demoSee use cases

Works with

and any system with an API via Custom REST

What compliance operations automation means here

Compliance operations is the daily casework of a financial crime team: onboarding reviews, screening hits, alert triage, periodic reviews, complaints and account closures. The steps are written in procedures, the work is done by hand, and the evidence ends up spread across inboxes, spreadsheets and case tools.

Verkflo runs that casework as reviewed agents. A procedure goes in as a document and comes out as a spec with steps, rules and review points your team can read. The spec is checked with evals, tried in the sandbox, then published to live. Published versions stay readable, so a file reviewed in March can be read against the procedure that applied in March.

This is casework automation. Verkflo does not run security certification audits, keep a policy library or test controls; GRC tools cover that work.

Who does what in compliance operations

  • The procedure

    Your procedures say which checks run, in what order, which rules decide the branch and which decisions belong to a reviewer, a team lead or your MLRO or compliance officer.

  • What the agent does

    • Runs the steps of a published procedure version for each case

    • Collects documents and data from Sumsub, ComplyAdvantage, Google Drive and REST systems

    • Applies CEL rules to choose the next step

    • Drafts notes, requests and summaries for review

  • What your team decides

    • Which procedures become agents, and when a version goes live

    • Decisions the procedure reserves for a named reviewer

    • Who holds the Admin, Author, Reviewer and Auditor roles

    • Changes to the rules after an eval or QA finding

Compliance procedures you can run today

A mix of onboarding, screening, monitoring and operations work.

Review requests and reporting

Reviews happen in the Verkflo review queue today. Review requests in Slack, Microsoft Teams and email are Coming soon. Reporting shows runs, outcomes and review times by procedure, so a team lead can see where files wait.

For the detail by area, see KYC automation, KYB automation and AML automation.

Controls your auditors will ask about

These controls apply to each agent you build. Sample data

Compliance operations questions

Do we need to rewrite our procedures first?

No. Upload the document you have. Verkflo compiles it into a spec, and your team edits the steps and rules before anything runs. The from-scratch workflow builder is Coming soon.

Is this a GRC or certification audit tool?

No. Verkflo runs operational casework such as reviews, screening and triage. It does not track policies, map controls to frameworks or prepare certification audits.

Who can change a procedure once it is live?

Access is by role: Admin, Author, Reviewer and Auditor, scoped to each workspace. A live procedure changes only when a new version is published, and its evals run before that.

Pick one procedure to start with

Bring the procedure your team spends the most hours on and we'll show it running as an agent.

Book a demo