Skip to content
Shonin
Soon

KYC File Pre-check

Every onboarding file checked for completeness and consistency before a compliance officer opens it.

The split

LLM writes
Reads and transcribes documents
System One decides
Document type, legibility, obvious tampering signals
Code executes
Field comparison, expiry dates, tier rules

Engine

Code extracts fields and compares names and dates; the brain answers typed questions about document type and legibility; people decide.

Rulebook

What correct means here, and the mistakes we've already caught. It grows one job at a time.

  1. R01Name and date comparisons happen in code, never in a model.
  2. R02The model never approves a customer; it only flags.
  3. R03Files are processed in-region and deleted after the retention period.

Intake

  • Your KYC policy and tiers
  • Accepted document types
  • 100 anonymized sample files
UNIT
One onboarding file pre-checked
REVIEW LAYER
A compliance officer makes every final decision.
DELIVERY
A pre-check result per file in your back office.
TURNAROUND
Real time

How we find buyers

  • Fintech compliance leads
  • Microfinance and cooperative networks
  • Core-banking vendors as partners

More like this