ComplianceLive

Match explanation

An assistant that explains to the analyst why a match counts as a hit.

Part of compliance AI: in the analyst console, it explains why a match counts as a hit. It makes suggestions, not decisions; what is defended in an audit is the analyst's decision.

Model card

Decision authority
None
Location
Analyst console
Personal data
Never sent externally
API
None
Capabilities

What does it do?

  • Match reasoning

    Explains which information matched and what differs.

  • Panel context

    Works attached to the hit record.

  • A suggestion, not a decision

    Decisions come from the decision endpoint.

  • Human decision

    The analyst reviews the evidence and decides.

  • Audit

    What is defended is the analyst's decision, not the model output.

  • Data protection

    Card, identity and biometric data are not sent to external model services.

Pipeline

How does it work, step by step?

  1. 1

    Stage 1

    Hit

    A match is opened in the panel.

  2. 2

    Stage 2

    Explanation

    AI explains the reasoning.

  3. 3

    Stage 3

    Review

    The analyst reviews the evidence.

  4. 4

    Stage 4

    Decision

    The analyst records their decision.

  5. 5

    Stage 5

    Audit

    The decision and evidence remain on record.

Meet Match explanation.

Let's review with our team how the model would work in your business.

Match explanation — AI | Lunixi