Financial services · KYC lifecycle
KYC / Perpetual KYC Multi-Agent System
- Who this is for
- KYC / AML / financial-crime operations teams inside banks, insurers, and fintechs coordinating onboarding and ongoing customer due diligence.
- Outcome
- Coordinate identity and entity evidence, screening, event monitoring, and scheduled reviews so authorised KYC/AML staff can decide with a complete case, not chase for one.
- Boundary
- Approval, rejection, offboarding, freezing, and regulatory reporting decisions stay with authorised KYC/AML personnel. The system coordinates evidence, screening, and monitoring — it does not decide risk.
KYC is a lifecycle, not a form.
Onboarding is one moment. Perpetual KYC is the years that follow — evidence expires, ownership changes, adverse media appears, sanctions lists update, and the review that captured a customer once will not describe them tomorrow.
Operations teams spend their time waiting on documents, reconciling records across screening vendors, and rebuilding cases from scratch every review cycle. The KYC/AML analyst who owns the decision sees only the last mile.
End-to-end KYC / Perpetual KYC flow
Eight coordinated steps across onboarding and ongoing due diligence. Screening runs through approved connectors; every consequential decision stays with an authorised human.
- Open a case with the configured customer / entity schema.
- Route to the assigned KYC officer with the deadline and evidence checklist.
- Request the evidence set required by the configured schema.
- Extract and validate each document with source links via the Intelligent Document Extraction workflow.
Example reviewer states on this step
Passport MRZVerified Beneficial ownership >25%Missing
- Screen through the customer's approved sanctions, PEP, and adverse-media connectors.
- Present hits with the source, the matched attributes, and the confidence.
- Assemble the signals defined in the customer's approved risk framework.
- Do not compute a Glacien risk score; present the evidence the authorised assessor needs.
- The authorised officer approves, escalates, or rejects with the reason recorded against the case.
- Escalations route to enhanced due diligence with the assembled evidence attached.
- Monitor for the configured trigger events: sanctions changes, adverse media, ownership changes, address changes, product changes, transaction pattern breaks.
- Raise a case when a configured trigger fires.
- Send the refresh request for the specific expiring or invalidated evidence.
- Chase and track return with the same reviewer states as onboarding.
- Assemble the case: current evidence, screening results, monitoring events, prior decisions.
- The authorised officer records the review decision, reasoning, and the next-review date.
Which decisions belong to which actor
Screening and monitoring run through approved connectors and configured rules; the KYC / AML team decides.
Configured schema, deadline, and evidence-checklist enforcement.
- Onboarding schema and case creation.
- Evidence checklist and expiry tracking.
- Refresh scheduling and next-review dates.
Suggestions a person confirms.
- Screening-hit likely / not-likely triage suggestions.
- Refresh-request drafting to the customer or relationship team.
Coordination across evidence, screening, and monitoring.
- Identity, entity, and beneficial-ownership evidence coordination.
- Screening across approved connectors.
- Event monitoring for configured triggers.
- Refresh chase and re-validation on returned evidence.
All consequential KYC / AML decisions.
- Approve, escalate, reject, offboard, freeze.
- Regulatory reporting decisions.
- Whether a screening hit is a true match.
Human boundaries
Authorised KYC / AML personnel own every consequential decision on this workflow.
KYC officer
- Onboarding approval, escalation, or rejection.
- Screening-hit true / false determination.
- Ongoing review decisions.
MLRO / financial crime team
- Offboarding, freezing, and suspicious-activity reporting.
- Enhanced due diligence escalations.
Compliance officer
- Whether the customer's risk framework and screening providers are appropriate.
- Whether the workflow's configured schema meets applicable due-diligence expectations.
Reviewer states you'll see on a KYC case
The same four-state vocabulary used across the platform.
Passport MRZVerified Proof of addressNeeds review Beneficial ownership >25%Missing Company registered addressConflicting
What we measure
Operating measures agreed with the customer at the Workflow Proof stage. Public numbers are attested per customer before they appear.
Time from case open to reviewer-ready pack
Onboarding and periodic-review cases tracked separately.
Screening hit-to-decision time
Time from a screening hit surfacing to the officer recording a true / false determination.
Evidence-refresh backlog
Volume and age of outstanding refresh requests.
Trigger event coverage
Which configured trigger events are firing, and on which portfolios.
How we prove it before scaling
The first commercial unit is a Workflow Proof against one user group, one customer segment, and one measurable outcome. Deployment, residency, integration, and screening-provider decisions are made with the customer's security, technology, and compliance teams before any production data is touched.
Frequently asked
- Does this determine customer risk?
- No. The system assembles the evidence the authorised assessor needs against the customer's approved risk framework. The KYC / AML team decides.
- Which regulators does this address?
- MAS, AUSTRAC, and RBI all establish ongoing customer-due-diligence workflows and are common contexts for this pattern in APAC. Applicability to a specific jurisdiction requires a jurisdiction-specific control mapping and legal / compliance approval — Glacien does not claim regulatory compliance on a public product page.
- Which screening providers can this connect to?
- Screening runs through the customer's approved sanctions, PEP, and adverse-media providers. Connector coverage is configured during Discover and Bound; new connectors are added as customer-approved additions.
- What data does the agent see?
- The data controls, retention rules, and access boundaries agreed with your compliance and security teams during Discover, enforced by the configured tool and permission scope for each agent.
Ready to review your KYC lifecycle with us?
Pick one segment, one workflow, one measurable outcome. A Workflow Proof starts there.