> Source: https://builder.ema.ai/v2/templates/kyc-document-review-ai-employee
> Title: KYC Document Review AI Employee

# KYC Document Review AI Employee

The KYC Document Review AI Employee is built from the **KYC Document Review** curated template (category: Finance). It is a form AI Employee (AIE): you submit a KYC document, and it extracts the identity information, validates it against compliance rules, and generates a structured, audit-ready review summary for your compliance team. It accelerates KYC review from manual document-by-document processing to automated extraction and validation, and ensures compliance rules are applied consistently across every review.

## Workflow

The template ships a three-agent workflow that runs left to right:

Node

Agent type

What it does

Extract Identity Data

`extraction`

Extracts name, date of birth, nationality, document type and number, issue and expiry dates, issuing authority, and address into a defined output schema, flagging fields that are illegible, expired, or potentially altered.

Compliance Check

`rule_validation`

Validates the extracted identity data against your compliance rules and reports each check as pass or fail.

Generate Review Summary

`respond`

Produces a structured compliance review summary — applicant details, each check result, an overall recommendation (approve / flag for review / reject), and notes for the compliance officer — in a formal, audit-ready tone.

A `start` node feeds the KYC document into the graph, and a `publish` node exposes the review summary. The edges run `start → extract → validate → summarize → publish`.

The Extract Identity Data node ships with an identity output schema in its `type_config`. For example:

```json
{
  "output_schema": {
    "type": "object",
    "properties": {
      "full_name":         { "type": "string", "description": "Full legal name of the individual" },
      "date_of_birth":     { "type": "string", "description": "Date of birth" },
      "nationality":       { "type": "string", "description": "Nationality or citizenship" },
      "document_type":     { "type": "string", "description": "Type of ID document (passport, drivers_license, national_id)" },
      "document_number":   { "type": "string", "description": "Document identification number" },
      "issue_date":        { "type": "string", "description": "Document issue date" },
      "expiry_date":       { "type": "string", "description": "Document expiry date" },
      "issuing_authority": { "type": "string", "description": "Authority that issued the document" },
      "address":           { "type": "string", "description": "Residential address" }
    },
    "required": ["full_name", "date_of_birth", "document_type", "document_number", "expiry_date"]
  }
}
```

The Compliance Check node ships with these rules in `type_config`:

```json
{
  "rules": {
    "operator": "AND",
    "conditions": [
      { "rule": "Document expiry_date must be in the future (not expired)" },
      { "rule": "Applicant must be 18 years or older based on date_of_birth" },
      { "rule": "Required fields (full_name, date_of_birth, document_type, document_number, expiry_date) must all be present and non-empty" },
      { "rule": "Document type must be one of: passport, drivers_license, national_id" },
      { "rule": "No tampering flags should be present in the extraction output" }
    ]
  }
}
```

## Starting configuration

The template clones in with this configuration, which you can change in the builder:

-   **Model selection** — Let Fusion Pick (EmaFusion™ chooses the model per request).
-   **Optimization priority** — Most accurate.
-   **Conversation context** — disabled (this is a single-submission form workflow, not a chat).
-   **Feedback** — enabled, with thumbs-up / thumbs-down reasons and free-text comments.
-   **Data protection** — `full_name`, `date_of_birth`, `id_number`, and `nationality` are pre-marked as protected fields.

**Recommended data sources:** connect your KYC compliance checklists and regulatory requirement documents so the agent can validate against current standards.

## How to use

After you select **Use template** and the AI Employee opens in the builder:

1.  **Customize accepted documents and fields.** Edit the accepted document types and required fields in the Extract Identity Data node.
2.  **Adjust the compliance rules.** Edit the rules in the Compliance Check node to match your regulatory requirements.
3.  **Customize the summary format.** Edit the Generate Review Summary node's Instructions to match your compliance team's review format.
4.  **Publish and submit.** Publish the workflow, then submit KYC documents and receive a structured compliance review.

> [INFO]
> **A decision aid, not the decision.** The KYC Document Review template produces an extraction, a rule-by-rule compliance check, and a recommendation for a human compliance officer. It does not approve or reject applicants on its own. Keep a human in the loop for the final decision, and review the protected-field list against your data-handling policy — see [PII and governance](/builder/v2/administration/pii-and-governance).

## Example inputs

-   A passport image, checking expiry, age, and required-field completeness.
-   A driver's license where the expiry date is hard to read (expect a flag).
-   A national ID for an applicant whose date of birth puts them under 18 (expect a failed check).

## Related

-   [Agent reference](/builder/v2/agent-reference) — the [Data Extractor](/builder/v2/agent-reference/extraction), [Rule Validator](/builder/v2/agent-reference/rule-validation), and [Respond](/builder/v2/agent-reference/respond) agent types.
-   [PII and governance](/builder/v2/administration/pii-and-governance) — protecting sensitive identity fields.
-   [Templates overview](/builder/v2/templates) — the full curated template list and the clone flow.