PMS Software Development: Build for India PMS & AIF

AI Summary: PMS software development in India supports the operations of registered portfolio managers and AIF managers rather than replacing their registrations. Investor onboarding, custodian integrations, portfolio or fund views, capital flows and statements require clear product-specific controls. Disclosures, fee transparency, role-based access and audit trails are central to a dependable investor platform. |
Portfolio Management Services (PMS) and Alternative Investment Funds (AIFs) sit in a different product class from retail apps. Investors write larger tickets, assets are usually held with an independent custodian, and SEBI expects disclosures, fee clarity and audit trails that a generic wealth dashboard does not provide. Most teams that come to us are not trying to invent a new asset class. They want a reliable investor portal and operations stack for a SEBI-registered portfolio manager or AIF manager: onboarding, capital flows, portfolio or fund views, statements and compliance reporting.
This guide is for founders and product teams building that stack in India. It covers the licence routes, what the regulations turn into software requirements, a reference architecture, key APIs, compliance features, and the drivers of cost and timeline. For the wider licence map, see our Fintech Licensing Requirements 2026 guide. If your product is advisory rather than discretionary management, start with our SEBI RIA investment advisory app guide. For brokerage connectivity, see stock broking app development in India.
PMS software development: What a PMS / AIF investor platform actually does
A PMS investor platform usually serves discretionary, non-discretionary or advisory portfolio relationships. The investor owns securities in their own demat and bank accounts (with a custodian arrangement as required), while the portfolio manager runs strategy, rebalancing and reporting. An AIF investor platform serves limited partners in a pooled fund vehicle: onboarding and KYC, subscription and drawdown notices, capital account statements, NAV packs and waterfall or distribution notices.
In both cases the software has to satisfy three audiences at once:
Investors who need transparent holdings, fees, documents and support
Front-office and middle-office teams who need workflows that match the investment process
Compliance and the regulator who need evidence that disclosures, segregation and reporting happened as required
Generic portfolio trackers fail when fee calculations cannot be reconstructed, when custodian and broker positions disagree, or when capital-call history is scattered across email.
Licence and regulatory route
SEBI Portfolio Managers Regulations
PMS in India is regulated under the SEBI (Portfolio Managers) Regulations, 2020. SEBI's investor education material summarises the core expectations: registration with SEBI, a minimum investment of ₹50 lakh, regular disclosures to investors, engagement of an independent custodian to hold assets, and a compliance officer (SEBI Investor: Portfolio Management Services). The same page describes the three common PMS types: discretionary (manager decides), non-discretionary (manager recommends, investor decides) and advisory (advice only, investor executes). Those types are not cosmetic. They change who can place orders, what consent screens you need and how you store decision evidence.
Always read the current consolidated regulations and circulars before you hard-code ticket sizes, fee rules or disclosure frequencies. SEBI amends these instruments; your rules engine should treat thresholds as configurable policy, not constants buried in code.
SEBI AIF Regulations
AIFs are regulated under the SEBI (Alternative Investment Funds) Regulations, 2012. Category, strategy and investor eligibility drive product design. As a working baseline, an AIF generally cannot accept an investment below ₹1 crore, with limited exceptions set out in the regulations (for example for certain employees/directors and specific social-impact fund cases). Treat those exceptions as counsel-confirmed configurations, not marketing copy. Fund documents, private placement memorandum disclosures, side-letter handling and drawdown mechanics are first-class product requirements for any serious AIF portal.
Own registration vs technology for a registered entity
Most software teams fall into one of three patterns:
Route | Who holds the SEBI registration | What you build | Best for | Trade-offs |
Own PM / AIF registration | Your company (or group entity) | Full investor portal, ops, compliance reporting | Asset managers building proprietary distribution | Capital, compliance team, longer time to first client |
Technology / white-label for a registered PM or AIF manager | Partner firm | Multi-tenant portal branded for the manager | Fintechs and SaaS vendors | Partner concentration; you must not hold out as the portfolio manager or AIF if you are not |
Hybrid | Group entity registered; platform shared | Shared core with firm-specific policies and branding | Groups with multiple strategies or entities | Strong tenancy and data segregation; complex change control |
If you are only technology, your contracts, UI copy and onboarding flows must make the registered entity clear. Investor confusion about who manages money is a compliance problem, not a UX preference.
What the regulations turn into software
Regulatory expectation | What you build |
Minimum ticket and eligibility | Configurable gates for PMS ₹50 lakh / AIF ₹1 crore baselines, accredited or exception paths with counsel-approved rules, hard block on funding below policy |
Client agreement and disclosures | Versioned templates, e-sign with audit trail, delivery logs for disclosure packs and fee schedules |
Custodian segregation | Account mapping investor → custodian → demat/bank, daily position and cash reconciliation |
Discretionary vs non-discretionary vs advisory | Role-based order authority, recommendation vs execution records, investor approval workflows where required |
Fee transparency | Fee ledger with management, performance and other charges, invoice history investors can download |
AIF capital calls and distributions | Drawdown notices, funding status, capital account statements, distribution waterfalls as configured in fund docs |
Ongoing reporting | Scheduled portfolio/fund reports, corporate action notices, complaint and query logs |
Compliance officer oversight | Maker-checker on sensitive changes, immutable audit logs, export for inspections |
Side letters and special fee deals are common in AIF land. Model them as structured overrides with effective dates, not free-text emails that never reach the fee engine.
Reference architecture
Layer | Components | Notes |
Channels | Investor web/mobile, RM console, ops console, partner APIs | Separate experiences for LP/investor, RM and compliance |
Onboarding | KYC, KRA upload/download (securities intermediaries), CKYC where applicable, risk profiling, agreement e-sign | Block funding until KYC and agreement states are complete |
Cash and subscriptions | Virtual accounts or collection rails, NACH/e-mandate where used, capital call funding tracker | Match every credit to an investor and product |
Trading / allocation (PMS) | Broker or OMS connectivity, allocation engine, pre-trade checks | Aligns with how you connect brokers; see our broking API vs membership guide |
Custodian and demat | Position, cash and corporate action feeds | Source of truth for holdings; portal must reconcile to it |
Portfolio / fund accounting | Lots, valuations, NAV (AIF), performance, fees | Independent calculation paths you can audit |
Investor portal | Holdings, documents, capital account, messages, fee statements | Read models fed from accounting, not spreadsheet uploads |
Compliance and reporting | Disclosure scheduler, SEBI/APMI reporting workflows, complaint desk | Policy version tags on every report |
Security | RBAC, encryption, session controls, privileged access monitoring | Investor and RM roles must not share credentials or views |
Event-driven updates between custodian feeds, accounting and the portal avoid the classic failure mode where the investor sees yesterday's spreadsheet while ops has already booked today's trades.
Key APIs and integrations
Identity and KYC: PAN validation, KRA connectivity for securities intermediaries, CKYC search/upload where your entity type requires it, video KYC or offline KYC as per applicable rules
Agreements: e-sign with full audit trail and template versioning
Banking: collection accounts, payouts for distributions or withdrawals, reconciliation files
Broker / OMS: order placement and fills for PMS strategies that trade listed securities
Custodian: positions, cash, corporate actions, settlement status
Market data and corporate actions: for valuations and investor notices
Document vault: PPMs, agreements, statements, tax packs, with access logs
Notifications: email/SMS/in-app for capital calls, disclosures and mandate events, with consent records
Reporting channels: whatever file or portal interfaces your compliance team uses for SEBI/APMI submissions — keep generation auditable even if submission is semi-manual at launch
For teams that also advise US clients under a different licence, the product shape differs; our US RIA robo-advisor guide covers that market separately and should not be mixed into an Indian PMS stack.
Compliance features to build
Build these as product modules, not after-the-fact spreadsheets:
Eligibility and suitability: capture risk profile, investment objectives and ticket size before funding; store the version of the questionnaire used
Clear entity presentation: every screen and email names the SEBI-registered portfolio manager or AIF
Disclosure delivery: track what was sent, when, and which template version
Fee audit trail: recompute fees from holdings and policy; show investors the same numbers ops uses
Related-party and conflict flags: surface where policy requires disclosure or restriction
Complaint and query management: timestamps, owners, resolution codes — inspections ask for this
Access control and maker-checker: especially for fee overrides, bank account changes and report releases
Retention and export: ability to produce a clean pack for an investor, auditor or regulator without engineering heroics
Do not invent performance claims in the portal. Show calculated figures with methodology notes that counsel and compliance have approved.
Cost and timeline drivers
We do not quote generic build prices. These factors move cost and time most:
Driver | Why it matters |
Route | Own registration adds legal and compliance programme work; pure tech for a partner is faster to first tenant but needs multi-tenancy |
PMS vs AIF vs both | AIF capital calls, NAV and waterfall logic are a different product surface from PMS portfolio views |
Custodian and broker landscape | Each custodian feed and broker API has its own quirks; plan reconciliation early |
Fee complexity | Simple management fee is quick; high-water marks, hurdles and side letters expand testing |
Reporting maturity | Manual upload of regulator files at launch is fine if generation is auditable; full straight-through reporting takes longer |
Data migration | Moving existing investors from spreadsheets or a legacy PMS needs careful holdings and fee history cutover |
Security and exam readiness | Pen-tests, access reviews and runbooks often sit on the critical path to go-live with a registered firm |
Build plan
Lock the product scope: PMS, AIF or both; discretionary rules; who is the registered entity
Map regulations to backlog: ticket gates, disclosures, custodian, fees, capital calls
Choose custodian and broker partners and obtain sample feeds before you finalise the data model
Build the core ledger and portal around reconciliation, not around marketing screens
Compliance dry-run: regenerate a month of fees, statements and disclosure logs end-to-end
Pilot with a small investor set, then open wider distribution
FAQs
Do I need a SEBI portfolio manager registration to build PMS software?
Not if you are only a technology provider to a SEBI-registered portfolio manager and you do not manage portfolios or solicit investors as if you were the manager. The registered entity remains responsible for regulatory obligations. Your contracts and UI must make that split obvious.
What is the minimum investment for PMS in India?
SEBI's investor material states a ₹50 lakh minimum investment for PMS. Confirm the current rule and any accredited-investor or other exceptions in the latest Portfolio Managers Regulations and circulars before you encode it.
What is the usual minimum commitment for an AIF?
As a general rule under the AIF Regulations, an AIF cannot accept an investment below ₹1 crore, subject to limited exceptions in the regulations. Confirm the current text for your category and investor type with counsel.
Can one platform serve both PMS and AIF?
Yes, if you separate product modules, legal entities, fee engines and investor experiences carefully. Shared KYC and document vaults are common; shared "portfolio" screens that blur fund interests with separately managed accounts create confusion and control failures.
How is this different from a robo-advisory or RIA app?
RIA and advisory apps centre on advice and suitability under the Investment Advisers framework. PMS software must support discretionary or non-discretionary portfolio operations, custodian reconciliation and fee constructs typical of managed accounts. AIF software adds fund-level capital accounting. See our RIA app guide when advice is the product.
How long does a first launch take?
It depends on whether you already have a registered partner, how many custodian/broker feeds you need, and fee complexity. Plan legal/compliance and technology in parallel, and treat reconciliation accuracy as the launch gate rather than UI polish.
Build your PMS / AIF platform with Fintegration
Fintegration builds investor portals and operations stacks for SEBI-regulated wealth and alternatives businesses: onboarding, custodian-aligned portfolio views, AIF capital accounting, fee ledgers and compliance-ready reporting. Talk to our team to scope your PMS or AIF investor platform.





