A typical activity to examine
An onboarding flow receives identity information, shares selected records with a service partner and creates ongoing account or transaction records.
Questions for the responsible team
Use these prompts to describe your own operation. They are examples, not a finding about your organisation.
- Which entity decides each purpose and which partner receives what information?
- What happens when an applicant does not complete onboarding?
- Which retention decisions come from documented sector or contractual requirements?
A useful first work package
Create an onboarding-to-exit map, provider responsibility list and a set of privacy and sector-regulatory questions for the appropriate reviewers.
Ownership and scope
Include product, operations, security and the responsible regulatory or legal contacts. This example does not establish a licence, regulatory category, KYC obligation or Prahari authority to advise on every financial regulation.
Common questions
Does this industry label determine our legal obligations?
No. The activities, people, roles, geography and applicable sector requirements need review.
What should we bring to an initial discussion?
Describe one important activity, the teams and providers involved, the records already available and the question you need to resolve. Use examples with unnecessary personal details removed.
Discuss the work you need
Agree the service, deliverables, responsibilities and fees before committing to an engagement.
Related reading
This page explains topics to scope and discuss. It does not establish applicability, certify compliance or confirm a paid engagement.
← Industry examples