KYC Is a Workflow, Not Just an Identity Check

The business situations in this article are fictional illustrations, not accounts of Parikh Advisory client engagements.

A customer uploads identification and sees “verified.” Their account remains unavailable because an ownership question is still under review. The screen suggests the journey is complete; operations has a different state. That mismatch is a product and control problem. In financial services, customer due diligence can involve identity, beneficial ownership, purpose of relationship and ongoing scrutiny; the exact duties depend on the jurisdiction, activity and risk profile.

Map the states people actually use

A single pass/fail field cannot express submitted, incomplete, awaiting external data, under manual review, approved with conditions, rejected, or due for periodic review. Define which transitions are automatic, which need an authorized reviewer, and which can be reversed. Keep a dated record of evidence, rule version, decision maker and reason. The product state shown to the customer can be simpler than the internal state, but it must not promise access that has not been granted.

Design the exception path first

Suppose an individual passes document verification but a business customer’s ownership information is unclear. Who asks for more information? What can the customer do while waiting? How is a false match escalated? When can a reviewer override an automated result, and who checks that override? These cases determine staffing, turnaround and auditability. A smooth upload screen alone does not settle them.

Protect the customer without exposing controls

Tell users what they need to provide, the current broad status and how to get help. Avoid disclosing sensitive screening logic that could enable evasion. Make requests specific enough to act on and prevent repeated document requests caused by disconnected teams. Define retention and access with qualified legal and compliance owners. Product designers should not invent a universal retention period or approval rule from a generic template.

Treat approval as a continuing relationship

Changes in ownership, activity or risk may require further review after onboarding. The FATF recommendations describe ongoing due diligence and scrutiny of transactions as part of the customer relationship. This is an international standard; local law and the applicable regulator determine implementation. Build a workflow that can request updated evidence, assign review, record decisions and communicate restrictions appropriately. Test it with the compliance owner before using live customer data.

A decision to take into the next meeting

Bring one actual case, name its owner and decide what evidence would justify the next investment. If the evidence is missing, make the smallest useful test the next action. Record the choice and the date to review it.

Source note: FATF Recommendations (updated June 2026). The example is illustrative; the source informs the method or control discussed, not the imagined business.