Onboarding packs checked, before accounts go live.
The KYC Agent reads entity documents — certificates, resolutions, UBO declarations, and source-of-funds statements — extracts parties and ownership percentages, compares them for internal consistency, runs watchlist screening at your thresholds, and recommends standard, enhanced, or declined disposition with a full trace.
How it works
The same pipeline you see in the live module, step by step.
- 1
Ingest the pack
Accept PDFs and pasted text from your trial upload or document repository. Classify document type and extract legal name, jurisdiction, and signatories.
- 2
Build the ownership graph
Parse UBO and cap-table statements into a graph. Flag when disclosed percentages do not sum to 100%, when a resolution names an owner missing from the UBO form, or when nested entities lack documentation.
- 3
Screen and score
Run sanctions, PEP, and adverse media checks at configured thresholds. Separate true matches from false positives with explainable match fields.
- 4
Apply policy
Map geography, industry, product type, and screening results to your risk rating model. Assign CDD or EDD paths and required evidence lists.
- 5
Route for decision
Present a disposition packet to onboarding or BSA — approve, request documents, or decline — with every check cited.
Worked example on demo data
Illustrative run on fictional Aster Bank data — not a customer result.
Halvorsen Trade Partners — undisclosed 25% owner
- The demo onboarding file for Halvorsen Trade Partners includes a UBO declaration listing Erik Halvorsen 40% and Ingrid Halvorsen 35%.
- A shareholder resolution in the same pack records Mirela Vostrik with 25% voting rights — she does not appear on the UBO form.
- The agent elevates risk to High, assigns enhanced due diligence, and holds account opening until a compliance officer reviews the graph in the live KYC module.
Checks and rules
Deterministic logic on every action; optional intelligence enriches text when configured.
- UBO percentage sum equals 100% (or documented unknown)
- Resolution signatories match director registry
- Hidden owner detection when cap table ⊃ UBO list
- Sanctions / PEP screening at institution threshold
- High-risk geography and industry policy gates
- Source-of-funds plausibility vs stated activity
What you get
Artifacts land in the shared finance record and activity log.
- Structured party and ownership graph
- Screening results with match rationale
- Risk rating and required EDD steps
- Disposition recommendation and audit trace
- Activity log for onboarding and compliance
Integrations (built during pilot)
- Document repository or trial upload intake
- Sanctions and PEP data providers (connected per pilot)
- Core banking customer onboarding APIs (read-only first)
- Case management export for audit
Questions
Does FinanceAI need live API access on day one?
No. Many pilots start with scheduled BAI2/MT940/CAMT.053 files and GL exports over SFTP. Read-only APIs come next once security review passes. The live demo uses the shared Aster Bank synthetic ledger.
What if Stellitron Intelligence is unavailable?
Every decision still runs through deterministic rules: amount matching, transposition checks, UBO percentage math, screening score thresholds, and flux materiality gates. Optional intelligence only improves extraction and narrative.
Who approves agent proposals?
Your org chart. Reconciliation journals route to treasury or accounting managers by amount. KYC dispositions require onboarding or BSA approval per your policy. Close entries respect maker-checker and each user's approvalLimit in the app.
Does FinanceAI replace our KYC platform?
It automates document reading, consistency checks, and traceable recommendations. Screening providers and the system of record for customer risk remain yours; we integrate during the pilot.
How are false positives handled?
Each hit shows matched fields and score. Analysts can clear with a documented reason; the agent never auto-clears sanctions matches above your auto-accept floor.