KRA Lifecycle Complexity
Fresh KYC, KRA fetch, modification, status tracking — the KRA lifecycle is non-trivial and tightly coupled to onboarding outcomes. Most platforms treat it as an afterthought.
SEBI Debarred Screening
Every applicant must be screened against the SEBI debarred list before account approval — with the result auditable. Manual screening is unsustainable at scale.
Joint & Corporate Accounts
Multi-holder accounts mean parallel KYC checks, signature mandate capture, and beneficial-owner workflows — rarely supported cleanly by generic KYC platforms.
NRI Onboarding Edge Cases
OCI/PIO docs, FATCA self-cert, overseas address proofs, PINS routing — NRI flows have a long tail of edge cases that most platforms hand back to ops as exceptions.
Same-Day Activation Pressure
Customers expect to start trading the day they sign up. KYC platforms that take days to push KRA submissions are out of step with market expectations.
RM-Assisted vs Self-Serve
Full-service brokers run RM-led journeys; discount brokers run pure self-serve. Both need to be supported — sometimes for the same institution.
Native KRA Integration
Fetch existing KRA records, initiate fresh KYC for first-time investors, submit modifications when customer details change — one connector, full lifecycle.
SEBI Debarred Screening
Built-in screening against the SEBI debarred entities list as a journey step. Result is captured in the audit trail with timestamp and matched-against version.
Multi-Account Journeys
Joint holder, corporate, and NRI flows are first-class — not bolted on. Each applicant goes through parallel checks while the journey orchestrates the whole thing.
Broker Enterprise Module
First-to-market enterprise module for broker workflows — bulk onboarding, sub-broker enrolment, RM-assisted journeys with maker-checker. Built alongside NDML.
Predictable KRA Cycle
End-to-end KRA submission handled inside the platform with full status visibility. No black-box waits and no manual reconciliation between systems.
RM & Self-Serve in One
The same journey runs as self-serve for app users and as RM-assisted in a branch — with operator productivity features layered on top when needed.
