CIP Verification demo

What the demo shows

Account opening teams resolve customer identification exceptions with examiner-ready reasons

An Application Reader agent reads the application and the ID document. A Source Comparison agent pulls the credit bureau header and a non-documentary database, compares name, date of birth, address and ID number across every source, and explains each discrepancy in plain words. A Resolution agent proposes only what a step of the institution's own CIP procedure allows, and cites the step. A Member Request agent chooses the one confirmation or document that closes the file, drafts it and reads the reply. A Screening agent records OFAC and 314(a) results on the same file, a Service Level agent escalates after 4 business hours, and an Examiner Pack agent writes each record in the rule's four parts. The Member Service Representative proposes, a BSA Analyst approves, and nothing is written to the core until then.

Transcript

1. 0:00CIP Verification helps banks and credit unions resolve customer identification exceptions, with reasons examiners can read.
2. 0:10At Norrell Federal Credit Union, about 32 new members a day hit one.
3. 0:17Each used to wait a day for the BSA team, and the file rarely said why.
4. 0:24Ahmad Rezaei is at Dana's desk. Agents compare four fields across four sources.
5. 0:32The address matches: the license just drops the unit, as Procedure 4.2 allows.
6. 0:40But the date of birth has the day and month swapped.
7. 0:45Dana sends a one-tap check, and Ahmad confirms July 3rd on his phone.
8. 0:52The agent proposes the fix under Procedure 4.5, and Dana submits it.
9. 1:00Dana can't approve her own. Marcus, the BSA Analyst, checks and approves.
10. 1:08Every source, list check and approval is kept in the rule's four parts.
11. 1:15Ahmad's membership opens two minutes after the proposal, not a day later.
12. 1:21Built on Botminds: agents, data, screens and governance on one platform.

The narration as written for the film. Captions are on the player.