KYC and KYB files you can stand behind

Every new customer relationship starts with a decision: open the account, decline it, or escalate it for enhanced due diligence. Know your customer (KYC) covers individuals, and know your business (KYB) covers legal entities. In both, the file records what was verified, what was found and why the decision was made.

KYC/KYB onboarding oversight is the practice of checking those decisions and files against policy and against the evidence in them. It asks whether the identity was verified as policy requires, whether the risk rating can be explained, and whether similar customers were treated in the same way.

For compliance and onboarding, this is where the foundation is laid. Monitoring, investigations and reporting later depend on the onboarding file, so a gap here is carried into everything that follows.

A complete file shows that the customer was identified and the identity verified. Under the customer identification program rule, a bank collects at least a name, a date of birth for an individual, an address and an identification number, and verifies identity within a reasonable time.

For a legal entity, the file also shows who is behind the business. The customer due diligence rule requires the beneficial owners to be identified: each individual who owns 25 percent or more of the equity, and one individual with significant responsibility to control, manage or direct the entity.

Beyond the minimum, a good file records the customer's risk rating and the reasons for it, the results of sanctions and other screening and how each hit was resolved, and any enhanced due diligence that followed.

Onboarding runs at volume, and quality control by sampling reads only a small share of the files. A missing beneficial owner, a risk rating that does not follow policy, or a screening hit closed without a recorded reason can sit in a file outside the sample for months.

Those defects tend to surface late, when an examination reads the file, or when monitoring depends on information that was never captured properly. Reviewing every onboarding decision moves the discovery to the start of the relationship, while the gap is still easy to close.

Prisma evaluates each onboarding decision and customer file against the policy and regulatory expectations your institution has set, detecting violations and ambiguity, with the reasoning behind each finding. A violation is recorded with the reason it breaks policy. Where the situation does not allow a clear answer, Prisma flags the ambiguity and escalates it for a human decision instead of forcing certainty.

The evaluation looks at whether the required information is present, whether the risk rating follows policy, whether the rationale is recorded, and whether screening hits were resolved with a reason.

When a file falls short, oversight is followed by intervention. The weak file is escalated for review, and consequences and feedback are applied, to the person or the AI that prepared it, in time to correct the file before it stands.

Remediation turns that correction into better behavior. Consequences and feedback improve how future customers are onboarded, so the same weakness does not repeat and onboarding performance improves and stabilizes over time, for people and for AI alike. The evidence of how each decision was judged is kept.

Onboarding is increasingly automated. AI agents collect and check documents, summarize ownership structures and draft risk assessments. Prisma applies a single governance standard to work produced by people and by AI, so an AI-prepared file is read against the same policy and checked for violations and ambiguity in the same way as one prepared by hand. As automation takes on more of onboarding, the oversight stays the same.