Banking & Financial Services

KYC File Reviewer

Finds what the onboarding file is missing, and decides nothing

Version 2Published Sep 2, 2026
Banking & Financial ServicesKnowledgeExtractclaude-opus-5Read-only · auto10 hard rules5 handover rulesResult
10hard rules
Things it must never do, enforced in every run
5handover rules
Conditions where it stops and gives the work to a person
9output fields
A structured result, not a paragraph you have to re-read
≤6steps per run
Bounded work: at most 5 tool calls, enforced by the runtime

Read-only by design. This agent has no path to sending, spending, publishing or committing anything. Where that limit is the product, removing it would remove the reason to trust the output.

Live wiring for version 2. Tool nodes are the capabilities this agent is registered to call — nothing else can run.

Overview

Onboarding files fail for boring reasons: a document that expired last month, an address that does not match the utility bill, an ownership chain that stops one company short of a natural person. Finding those is mechanical work that consumes an analyst's week.

This agent does the mechanical part. It checks the file against the customer due diligence policy in your knowledge base — which documents this customer type requires, what must be verified, what must be dated — and reports exactly what is missing, expired, inconsistent, or unresolved.

It makes no decisions. It does not accept or reject a customer, does not assign a risk rating, does not conclude anyone is a politically exposed person, and does not decide anything is suspicious. Those are regulated acts that carry personal liability, and an agent performing them would be a liability rather than a product. It produces a complete, evidenced list of what an analyst must resolve.

Benefits

Analysts stop hunting

They arrive at a file with the gaps already listed.

Consistent files

The same policy applied to the two-hundredth file as to the first.

Audit-ready

Every finding traces to a written requirement.

What it does

  • Checks against your own CDD policy

    Your requirements for this customer type, read from your knowledge base — not a generic checklist.

  • Catches expiries and mismatches

    Expired documents, names that differ, addresses that do not agree across the file.

  • Follows the ownership chain

    Reports where the chain stops short of a natural person, and at which entity.

  • Separates missing from unresolved

    A document nobody supplied and one that raises a question need different work.

  • Decides nothing

    No acceptance, no risk rating, no PEP conclusion, no suspicion. Every one of those is an analyst's regulated act.

  • An evidenced worklist

    Each gap names the policy requirement behind it.

What this changes

What this changes about your week

It takes over
Working through an onboarding file for expiries, mismatches and gaps in the ownership chain.
Done today by
Analysts, at the cost of most of their week.
How often
Every new customer, and every periodic review.
Typical manual effort
A corporate file with a layered ownership structure is an hour or more.

Why Banking & Financial Services in particular. The finding is mechanical; the decision is not. This does the mechanical half so your analysts spend their judgement where it is needed.

  • Runs unattended

    Started by you or by an event, and it finishes on its own. Nothing waits for someone to be at a desk.

  • The same standard every time

    The two-hundredth item is held to the bar the first one was. Consistency is the part people cannot sustain.

  • It cannot act on its own

    KYC File Reviewer has no path to sending, spending or committing. That limit is why its output is safe to act on.

How it runs

This agent runs server-side through the PROMIVO runtime. Each run is logged step by step and every tool call is permission-checked before it executes.

  1. 1InputValidated against the agent input schema
  2. 2Modelclaude-opus-5 with automatic fallback
  3. 3Toolssearch_knowledge, extract_structured_data
  4. 4PermissionsRuns READ actions automatically; anything higher waits for approval
  5. 5OutputStructured result matching the output schema
  6. 6LoggingTokens, duration and every step recorded

Demo

Demo dataIllustrative sample output, abridged.

Input

{
  "documents": [],
  "customerType": "company",
  "jurisdiction": "TR",
  "fileReference": "ONB-2231"
}

Output

{
  "escalate": true,
  "disclaimer": "A completeness check against your CDD policy. No decision, risk rating, PEP determination or suspicion assessment has been made, and none may be inferred from this output.",
  "policyFound": true,
  "requirements": [
    {
      "status": "expired",
      "evidence": "Utility bill on file is dated 11 months ago.",
      "requirement": "Proof of address for each beneficial owner, dated within 3 months",
      "sourceDocument": "CDD Policy v9 — section 4.2"
    }
  ],
  "ownershipChain": {
    "stopsAt": "Meridian Holdings BV — no shareholder register supplied",
    "resolvedToNaturalPersons": false
  },
  "policyDocument": "CDD Policy v9 — corporate customers",
  "inconsistencies": [
    {
      "field": "Registered address",
      "values": [
        "Levent, Istanbul (register extract)",
        "Şişli, Istanbul (application form)"
      ]
    }
  ],
  "escalationReason": "Ownership cannot be resolved to natural persons from the documents supplied.",
  "outstandingForAnalyst": [
    "Current proof of address for both beneficial owners.",
    "Shareholder register for Meridian Holdings BV.",
    "Reconcile the two registered addresses."
  ]
}

Requirements

Integrations

No integrations required.

Before you start

  • The onboarding file contents
  • A knowledge base holding your CDD/KYC policy
  • Requires the All-Access plan or higher

Use cases

New customer onboarding

Check the file before it reaches an analyst.

Periodic review

Find what has expired or changed since onboarding.

Remediation programmes

Work a backlog against one consistent standard.

Pricing

All-Access

Billed monthly through your PROMIVO subscription. Cancel at any time.

Runs consume your plan allowance for agent executions and tokens. See plan limits

FAQ

Does it approve customers?

No, and it must not. Acceptance, risk rating, PEP determination and suspicion are regulated decisions carrying personal liability for the person who makes them. This agent lists what is missing so that person can decide faster.

Does it screen against sanctions lists?

No. Screening requires licensed, continuously updated data and a documented matching process. It reports whether your file records that screening was performed, which is a documentary check.

What if our policy is not loaded?

It reports that it cannot check requirements and limits itself to internal consistency and expiry checks. It will not substitute a generic standard for your policy.

What about the personal data in these files?

It reads what you supply and transmits nothing outward. Findings reference documents rather than repeating identifying detail that the finding does not need.

Reviews

Reviews open once customers have run this agent.

Need this agent to work differently?

Tell us what to change and our team will scope a customised version for your business.

Customize this agent