Skip to content

For distribution houses

We run RMs, branches and sub-brokers and reconcile all of it by hand.

Hierarchy, mapping and split commissions that settle themselves, so month end stops depending on one person and one spreadsheet.

The problem

What this looks like today.

  • 01

    Sub-broker splits live in a spreadsheet only one person can maintain.

  • 02

    Every branch reports differently, so the consolidated number takes a week.

  • 03

    An RM leaves and nobody is quite sure what they could see.

A day on the platform

What the work actually looks like.

  1. Morning

    The whole house on one view.

    AUM and revenue by branch, by RM and by sub-broker, from the same book rather than from four returns filed at different times.

    A business MIS dashboard: total AUM, month-to-date revenue, branch count and active RMs across a dark header band, then AUM by branch and revenue by branch as horizontal bar charts split by trail, upfront and advisory, and an RM league table below with clients, AUM, net new money, revenue and a year-on-year movement against each name.
  2. Through the day

    Everyone sees their own book, and only theirs.

    An RM sees their clients, a branch head sees the branch, and the mapping that decides this is a configuration rather than an honour system.

    The organisational hierarchy: an indented tree of group, branch, relationship manager and client on the left with one RM selected, and on the right that RM’s detail — their branch and start date, their client, AUM, account and opportunity counts, a visibility panel stating that they see their own clients and neither the branch book nor other RMs’ clients, and a list of the clients mapped to them.
  3. Month end

    Splits compute with the brokerage, not after it.

    Sub-broker shares apply on the rules you set, from the same reconciled figures as your own revenue. Nobody rebuilds the calculation.

    A sub-broker payout run: the run identifier, its period and a pending-approval status across the top, then a table of sub-brokers with their code, client count, AUM, gross brokerage, split percentage and computed payout, each marked matched, variance or held. The held row carries a note that its mapping changed mid-month and the split was pro-rated.

Coverage

What is supported, class by class.

What is operationally supported for each product class
ProductOrder captureRoutingCorporate actionsValuation basisReportingCommission
Mutual FundsYes, with conditionsOnline and offlineYes, with conditionsBSE StarMFYesYes, with conditionsUnitised — units × NAVYesYes
AIFYes, with conditionsOffline order entry, with drawdownsNot supportedNot supportedYes, with conditionsNon-unitised — statement valueYesYes
PMSYes, with conditionsOffline order entryNot supportedNot supportedYes, with conditionsNon-unitised — statement valueYesYes
BondsYes, with conditionsOffline order entryNot supportedYes, with conditionsVia bond settlement engineYes, with conditionsUnitised — units × priceYesYes, with conditionsRate matrix and manual entry
Direct EquityYes, with conditionsOffline order entryNot supportedYesYes, with conditionsUnitised — units × priceYesYes, with conditionsNot modelled — brokerage, not commission
Fixed DepositsYes, with conditionsTransaction / holding uploadNot supportedNot supportedYes, with conditionsNon-unitised — statement valueYesYes, with conditionsRate matrix and manual entry
Recurring DepositsYes, with conditionsTransaction / holding uploadNot supportedNot supportedYes, with conditionsNon-unitised — statement valueYesYes, with conditionsRate matrix and manual entry
NPSYes, with conditionsTransaction / holding uploadNot supportedNot supportedYes, with conditionsSet per instrumentYesYes, with conditionsRate matrix and manual entry
InsuranceYes, with conditionsTransaction / holding uploadNot supportedNot supportedYes, with conditionsSet per instrumentYesYes, with conditionsRate matrix and manual entry
Real EstateYes, with conditionsTransaction / holding uploadNot supportedNot supportedYes, with conditionsSet per instrumentYesYes, with conditionsRate matrix and manual entry

Mutual Funds, AIF, PMS, Bonds and Direct Equity carry a full product specification. The other five are basic information only by design — held, valued and reported, with no product-specific fields planned. Valuation basis is set per instrument rather than per product, and defaults to unitised. Non-unitised positions report at value with zero units.

Security and compliance

Built for the scrutiny it will face.

What we do, and what we are certified for

  • Data residencyClient data is held in India.
  • EncryptionIn transit and at rest, with managed key rotation.
  • Access controlRole-based, scoped to the hierarchy, every sensitive action logged.
  • CertificationISO 27001 audit in progress. Status and dates are published.

How we charge stated plainly.

  1. One per-firm subscription. Everything in one licence.
  2. The price never scales with your AUM.
  3. No revenue share. No basis points. Ever.
  4. The number is quoted on your demo — and it holds.

The pricing model

  • Mutual Funds
  • AIF
  • PMS
  • Bonds
  • Fixed Deposits
  • Direct Equity
  • NPS
  • Insurance
  • BSE StarMF
  • CAMS
  • KFintech
  • AMFI
  • CVL KRA

Every product class, one book

What distribution houses ask.

How deep can the hierarchy go?

Four levels — group, family, client, account — and the organisational structure of branches and RMs maps onto it rather than sitting beside it.

Can sub-brokers log in?

Yes, scoped to exactly their own clients and nothing beyond.

What happens when an RM leaves?

Access ends with their directory account if you use your own identity provider. Their clients re-map to whoever takes over, and historical splits are not rewritten.

Do sub-brokers cost extra?

No. The subscription is per firm and does not change with how many sub-brokers you map.

See it with your own book.

Weekdays 09:30–18:30 IST