Lotus Comply / Platform & governance / Reusable KYC
Your KYC profile. Ready when you are.
Create and maintain your KYC profile in one secure place, then choose the institution, purpose and information you authorise for each share. Submitted versions stay fixed, and each institution makes its own compliance decision.
Owner choice → frozen share → independent review
Alex Morgan · Owner-controlled profile
Current private draft · Not submitted or shared
Review and submit a version → separately authorise each institution
Submitted Version 1 · Immutable
Bank A
- Customer consent
- Alex Morgan · 10 Oct 2026
- Purpose
- Account onboarding
- Permitted scope
- Identity and address evidence
- Share access
- active · 10–24 Oct 2026
- Delivery
- Subject to configured institution channel
- Institution decision
- Independent review · no outcome recorded
Institution-read-only frozen snapshot
Submitted Version 2 · Immutable
Insurer B
- Customer consent
- Alex Morgan · 16 Oct 2026
- Purpose
- Policyholder due diligence
- Permitted scope
- Identity, updated address and occupation declaration
- Share access
- active · 16–30 Oct 2026
- Delivery
- Subject to configured institution channel
- Institution decision
- Independent review · no outcome recorded
Institution-read-only frozen snapshot
Private edit → newly submitted Version 2 → separate Insurer B consent. Bank A’s Version 1 remains unchanged.
Inside the capability
Connected context, explicit responsibilities.
Know what the view connects, what remains outstanding and who can take the next step.
Individual customer
Three real paths into the experience
Start independently in the customer portal, follow an institution website deep link to that portal, or respond to an institution’s invitation. The invited application is distinct from owner-controlled sharing.
- Autonomous signup, prepare and share
- Website deep link into customer portal
- Secure single-use invitation path
Profile owner
Prepare private evidence in one place
Keep personal information and documents in an owner-controlled profile. Edit privately, review the evidence and submit a version when ready. Submission fixes that version; sharing still requires your separate authorisation.
- Personal and contact information
- Private evidence upload and replacement
- Profile preparation in the customer portal
Profile owner
Choose the recipient and reason
Authorise a named institution for a specific purpose and permitted scope. Each consent creates a read-only frozen snapshot from a submitted version, not unlimited access to your private profile. Access permission and delivery are recorded separately.
- Named bank, insurer, fintech or SACCO
- Defined evidence scope
- Explicit authorisation before sharing
Institution reviewer
Keep received versions fixed
Each share references an immutable submitted version. Updating your draft does not submit a new version or change an earlier snapshot. Submit a new version and authorise another share when you want to provide updated evidence.
- Versioned received evidence
- Separate later authorisation
- Institution retention obligations remain
Receiving institution
Expect an independent institution review
The institution assesses freshness, suitability, enabled checks and mandatory requirements. It may ask for additional evidence; another institution’s decision is not automatically accepted.
- Current address or additional declarations
- Selected checks under institutional policy
- Human review and final authority
Owner & records officer
Understand updates and withdrawal
Keep your profile current and manage each share’s access window. Active, revoked and expired describe access permission, not delivery or approval. Withdrawal stops future access while institutions may lawfully retain records already received.
- No retroactive snapshot edits
- Future access limited on removal
- Lawful retention handled separately
Start your way
Three entry paths. Two distinct evidence journeys.
Direct customer start
Create or update your own profile in the customer portal.
Institution portal link
Follow a website or application link to the same portal-based profile path.
Institution invitation
Complete a specific invited application with its requested evidence.
Customer-owned sharing path
Profile & evidence → named-institution permission and scope → frozen authorised share.
Invited application path
Requested information & evidence → institution-specific application submission.
Check applicable evidence, screening and risk requirements → request information or record an authorised decision. No global KYC approval.
Start to finish / Reusable KYC
A clear route, including the exceptions.
- 01
Choose entry path
Independent portal, institution link or invitation.
- 02
Prepare information
Owner profile and private evidence.
- 03
Review permission
Named institution, purpose and scope.
- 04
Submit & authorise
Freeze a version; consent to a scoped institution share.
- 05
Institution reviews
Freshness, suitability and mandatory checks.
- 06
Maintain & share again
Edit privately, submit a new version and authorise a later share.
Review requirements met
Receiving institution can make its own authorised decision.
Additional evidence needed
Stale or unsuitable records require customer follow-up.
Permission or check unavailable
Restricted access or source hold does not imply approval or rejection.
Inside the workspace
Records, follow-up and review history.
Explore connected evidence, review history and the work available to authorised teams.
Alex Morgan
Owner-controlled profile- Owner
- Alex Morgan
- Current profile
- Private draft · not submitted or shared
- Submitted versions
- Version 1 and Version 2 · immutable
- Institution shares
- Separate consent for Bank A and Insurer B
- Submitted Version 1
- 2026-10-10 · Immutable
- Submitted Version 2
- 2026-10-16 · Immutable
Draft edits remain private. A new version must be submitted before a separately authorised share can reference it.
How it works in practice
One owner profile, two independent institutions
- 01
Inputs
Alex Morgan submits Version 1, then separately authorises Bank A to access identity and address evidence for account onboarding within the agreed access window.
- 02
Controls & actions
Alex later updates the private draft, submits Version 2 and separately authorises Insurer B for policyholder due diligence with its own evidence scope and access window. Bank A’s Version 1 snapshot stays unchanged.
- 03
Outcome & exceptions
The sample shares are active, but delivery awaits configured institution channels; no receipt or approval is recorded. Each institution reviews independently once evidence is available. Withdrawal stops future access without erasing lawfully retained prior records.
Connect the relevant services
Select what your programme needs.
Choose commercial services independently to match your programme. People 360, Business 360 and Reusable KYC are shared platform capabilities. Agree service scope, commercial terms and any required source connections for your institution.
Customer-led profiles and independent onboarding decisions.
Identity evidence, enabled checks and exception handling.
Business evidence, ownership layers and associated people.
Bring person information, identity checks, current KYC, screening, risk and company relationships into one authorised view. Follow the evidence and decisions behind each status, see outstanding work and understand how one person connects to multiple businesses — without duplicating their identity.
Questions & answers
Before you choose Reusable KYC.
Can I start without an invitation?
Yes. Customers can sign up and prepare independently in the customer portal. An institution portal link and invitation-backed application are additional distinct paths.
Will every institution accept the profile?
No. Each institution independently reviews suitability, freshness and its requirements, and may request additional evidence.
Does removing consent delete past records?
It limits future access. Legally retained institution-held compliance records and earlier frozen shares are separate.
Does active share access mean delivery is complete?
No. Active, revoked and expired describe permission within an access window. Delivery is tracked separately as awaiting a configured channel, delivered or failed. Institution channels require configuration and validation; an active share does not establish receipt or approval.