KYC and KYB casework, where the accounts live.
Case workflows, fraud triage and exposure views run beside the core account and transaction stores. The pattern reflects DBTEZ's consulting work in the US banking domain, where KYC and KYB orchestration is a recurring engagement.
The file re-enters the queue after onboarding.
A KYB file gets verified once, with a checklist and a deadline. Then the entity keeps changing after the checklist is done.
Intake
A trigger opens the case: a new account, an ownership change, a transaction alert.
K·01 opens the case beside the core stores
Verification
Identity and beneficial-ownership records are checked against the file. PII stays masked in the plan itself.
masks scoped to the reviewer's role
Scoring
Models score the case and attach the reasons, so a reviewer can see why row one is row one.
K·03 ranks the queue · reading it is logged
Review
An analyst clears, escalates or files. The decision lands on the ledger with the question and the rule.
one row per read, kept for the examiner
Refresh
The file re-enters the queue on a schedule or an event. Exposure views stay current in between.
periodic refresh is a scheduled K·01 job
the loop closes · stage 05 re-opens stage 01 · the examiner reads the whole trail from the ledger
What the review floor asks for first.
The refresh queue, ranked with reasons attached. Review capacity goes where the score says, and the score can explain itself.
K·03 · attention queue
Row filters and column masks are part of the query plan, scoped to role. A cleartext read is itself a logged event, so this is a ledger query.
K·03 · masking + audit
Exposure views computed over the system of record as it stands; a monthly extract cannot answer a question about today.
K·03 · live views
Where the agent sits.
KEZEL · DEPLOYMENT · BANKING & FINANCIAL SERVICES
- agent
- beside the core banking stores
- components
- K·01 workflows + K·03 analytics
- connectors
- warehouses, operational stores, CDC and legacy connectors
- audit
- orchestration ledger · question, rule, reader, timestamp
Locality, lineage and access logs are properties of the run itself: the shape an examination review asks to see.
Show us the data you are not allowed to move.
That's the workload we should discuss. Start with a demo on our sample boundary; move to a pilot in yours once your security review clears it.