Financial Services
Investment & Wealth Management
How investment and wealth platforms actually run: order routing, portfolio accounting, SIPs, rebalancing, market data, compliance, and the operational state that sits behind every trade and client recommendation.
Last updated:
₹68L Cr+
India MF AUM
17 Cr+
Demat Accounts
$120T+
Global AUM
$62B
WealthTech Market
What Engineers Miss When They First Enter Investment & Wealth Management
Most people think investment apps are just charts, buy buttons, and portfolio percentages. In production, the harder work is keeping every holding, cash balance, order, execution, and tax event aligned across exchanges, fund houses, custodians, and broker back offices.
A good wealth platform has to answer simple user questions with defensible data: what do I own, how much is it worth, what changed since yesterday, why did this order fail, and what exactly happened at settlement. Those answers depend on state that is distributed across market data feeds, OMS, PMS, RTA systems, and compliance engines.
This is why the domain is more than a finance wrapper on top of a database. It is an operational system where every trade has pre-trade checks, every mutual fund transaction has cut-off timing, every recommendation needs suitability evidence, and every report must survive audit.
What Teams Actually Do Day To Day
- 1Build order-routing and execution flows that can handle market, limit, stop-loss, partial fills, cancellations, and exchange acknowledgements without losing traceability.
- 2Maintain portfolio and holdings truth across trades, mutual fund allotments, corporate actions, dividends, splits, and daily valuation updates.
- 3Implement SIP, mandate, KYC, and investor onboarding journeys that work across brokers, AMCs, RTAs, and payment rails.
- 4Encode risk, suitability, concentration, and regulatory constraints so investment recommendations and trades remain within policy.
- 5Support statements, tax reports, client communications, and advisor workbenches that explain performance in language users and regulators can trust.
One End-to-End Flow: A SIP Order Becomes Units in an Investor Folio
A SIP is not a single API call. It passes through onboarding, mandate setup, cut-off handling, order registration, AMC processing, NAV application, and investor notification before the investment can be treated as complete.
Investor completes onboarding and risk profiling
The platform captures identity, PAN or KYC status, bank account details, and a risk questionnaire. The goal is not just sign-up; it is to decide what products the investor is eligible for and what advice can be shown.
Systems Involved
Mobile app, KYC service, advisory engine, investor master
Where It Usually Breaks
A weak identity or KYC state can let the app look ready while the AMC or fund platform refuses the transaction later.
A mandate is created for recurring debit
The investor approves NACH, UPI AutoPay, or another e-mandate so the platform can collect money on a recurring schedule. The mandate becomes the operational dependency for the whole SIP lifecycle.
Systems Involved
Mandate service, payment gateway, bank integration, eNACH rails
Where It Usually Breaks
If mandate status is not synchronized, the SIP looks active in the app but will silently fail on the next due date.
The SIP registration reaches the fund platform
The broker or investment platform sends the SIP registration to the AMC or RTA with scheme code, amount, frequency, first debit date, and folio linkage.
Systems Involved
MF transaction platform, RTA, AMC API, folio master
Where It Usually Breaks
Duplicate or delayed registrations can create multiple SIP instructions for the same investor if idempotency is weak.
Debit happens on the scheduled date
On the SIP date, the mandate rail attempts collection. If the debit succeeds before cut-off, the money is converted into a purchase order at the applicable NAV; if it fails, the SIP cycle must record the reason and preserve retry or pause logic.
Systems Involved
Mandate processor, banking rail, order scheduler, fund platform
Where It Usually Breaks
A payment success without order registration creates a cash-and-trace mismatch that operations teams have to reconcile later.
NAV is applied and units are allotted
The AMC calculates the applicable NAV after market close and allots units to the investor folio. The investor can only be shown a final position once allotment is confirmed from the source of truth.
Systems Involved
AMC allotment engine, NAV service, folio accounting, statement generator
Where It Usually Breaks
Customers often see money debited before units appear, so support teams need status states that distinguish debit, processing, and allotment.
Portfolio and tax views are updated
The platform updates holdings, returns, contribution history, and statements so the investor and advisor can see the new position in the portfolio dashboard.
Systems Involved
PMS, portfolio valuation, reports, notifications
Where It Usually Breaks
If valuation lags allotment, portfolio screens and tax reports can show stale positions even though the transaction is already confirmed.
Where Production Incidents Usually Happen
Order status and holdings drift apart
Symptom: The app shows a completed buy order, but the holdings view is missing or shows an older quantity.
Why it happens: Execution, settlement, and portfolio update events were processed in different services without a single reconciled state model.
What good teams do: Use explicit lifecycle states and reconciliation jobs that compare exchange or AMC confirmations against holdings and cash books.
Cut-off handling produces the wrong NAV expectation
Symptom: A user expects same-day NAV, but the order is allotted at the next day’s price.
Why it happens: The platform mishandled submission time, payment completion time, or AMC cut-off rules.
What good teams do: Model cut-off as first-class business logic and explain the expected NAV or settlement date before the user submits.
Mandate active, but SIP silently fails later
Symptom: Recurring investments stop while the mandate still appears valid in the UI.
Why it happens: Mandate status, bank retry state, and SIP instruction state are not synchronized across systems.
What good teams do: Track mandate, debit attempt, order registration, and allotment as separate events and expose failure states clearly to users and ops.
Data Model Hotspots
Investor Profile And Suitability
Suitability and eligibility depend on who the investor is, what products they can access, and what disclosures or restrictions apply.
Order, Trade, And Fill Trail
Investing systems need a durable timeline from intent to execution to settlement so every user action can be explained after the fact.
Portfolio And Tax Position
Portfolio truth is not just holdings quantity. Cost basis, tax lot, corporate actions, and realized/unrealized gains all matter to reporting and advice.
Integration Realities
The platform depends on several external truths
Exchange feeds, depositories, AMCs, RTAs, KYC agencies, mandate rails, and market data vendors each control part of the workflow. No single service owns the whole lifecycle.
Settlement and reporting are different problems
A trade can be executed quickly but still be missing in the back office or statement system until settlement and reconciliation finish.
Advisory systems need explainability
Robo-advisory and recommendation engines are only useful if the platform can explain why an allocation was suggested and what constraint or profile drove it.
Batch jobs still drive core business outcomes
NAV publication, end-of-day holdings, corporate actions, tax statements, and SIP processing are still batch-heavy even in modern mobile-first products.
Regulation Changes The Software Shape
- SEBI, AMFI, exchange, and depository rules influence order handling, disclosures, KYC, suitability, and record retention.
- Robo-advisory and model portfolios need clear suitability and recommendation logic so the platform can defend what it suggested.
- T+1 settlement and cut-off rules change user expectations and require explicit time-based business logic in the product layer.
- Regulatory and tax reporting depends on accurate cost basis, transaction lineage, and corporate-action handling.
Common Misconceptions New Engineers Have
- ×"A wealth app is just a polished UI on top of brokerage APIs." In practice it is a multi-system workflow that has to keep orders, holdings, cash, tax, and compliance in sync.
- ×"If an order is executed, the job is done." Execution is only one stage; settlement, position update, and reporting still need to complete safely.
- ×"SIP logic is trivial recurring billing." SIPs combine mandate status, cut-off timing, scheme registration, allotment, and failure recovery, which makes them operationally brittle.
- ×"Robo-advice is just recommendation ranking." The platform also has to preserve risk profile evidence, constraints, rebalancing history, and communication trails.
Technology Architecture — How Investment & Wealth Management Platforms Are Built
The diagram below reflects how production Investment & Wealth Management systems are structured at scale — nine layers from client channels through edge security, API gateway, domain microservices, polyglot data stores, async event streaming, analytics, external partners, and cloud infrastructure. Solid arrows show synchronous REST/gRPC calls; dashed arrows show async event flows via Kafka or a message queue.
Industry Players & Real Applications
🇮🇳 Indian Companies
Zerodha
Discount Broker
Python, Go, AWS
India's largest broker by active clients, built Kite platform in-house
Groww
Investment App
Java, React Native, AWS
50M+ users, stocks + MF + Gold
Upstox
Discount Broker
Java, Kotlin, AWS
Backed by Tiger Global, 1.5 Cr+ clients
SBI Mutual Fund
AMC
Java, Oracle, Angular
Largest AMC by AUM in India
HDFC AMC
AMC
Java, SQL Server, React
Top private sector AMC
Paytm Money
WealthTech
Java, React Native
Integrated with Paytm super-app
INDmoney
Wealth Platform
Python, React Native
US stocks + India investments
CAMS / KFintech
RTA
Java, Oracle
Registrar & Transfer Agents for MF industry
🌍 Global Companies
BlackRock (Aladdin)
USAAsset Manager
Java, Aladdin Platform
Manages $10T+, Aladdin used by 200+ firms
Vanguard
USAAsset Manager
Java, Custom Platform
Pioneer of index investing
Fidelity
USAFull-Service Broker
Java, .NET, AWS
40M+ customers, robo-advisor launch
Betterment
USARobo-Advisor
Python, React, AWS
Pioneer robo-advisor, $45B AUM
Robinhood
USACommission-Free Broker
Python, React Native
Democratized retail investing
Charles Schwab
USAFull-Service Broker
Java, .NET
Acquired TD Ameritrade
eToro
Israel/UKSocial Trading
C#, React
Copy trading pioneer
Wealthfront
USARobo-Advisor
Python, Java, AWS
$50B+ AUM automated platform
🛠️ Enterprise Platform Vendors
SimCorp
Dimension — Portfolio management, compliance, settlement
Tier-1 investment management platform
Charles River IMS
Portfolio management, trading, compliance
Acquired by State Street
SS&C Advent
Geneva, APX, Axys
Portfolio accounting and reporting
Broadridge
Order Management, Investor Communication
Back-office and communication tech
FIS Investran
Private equity and hedge fund administration
Fund accounting specialist
Morningstar
Direct, Advisor Workstation, Data
Investment data and analytics platform
Real World Use Cases
Portfolio Management
Portfolio construction, performance measurement, attribution, and rebalancing systems for wealth managers
Explore →Trading & Broking
Retail and institutional trading platforms, order management, and exchange connectivity
Explore →Robo-Advisory & WealthTech
Automated investment advisory platforms using algorithms for goal-based investing and auto-rebalancing
Explore →Fund Administration & Compliance
Back-office for mutual funds — NAV calculation, unit allotment, RTA operations, and SEBI compliance
Explore →Core Systems
These are the foundational systems that power Investment & Wealth Management operations. Understanding these systems — what they do, how they integrate, and their APIs — is essential for anyone working in this domain.
Business Flows
Key Business Flows Every Developer Should Know.Business flows are where domain knowledge directly impacts code quality. Each flow represents a real business process that your code must correctly implement — including all the edge cases, failure modes, and regulatory requirements that aren't obvious from the happy path.
The detailed step-by-step breakdown of each flow — including the exact API calls, data entities, system handoffs, and failure handling — is covered below. Study these carefully. The difference between a developer who “knows the code” and one who “knows the domain” is exactly this: the domain-knowledgeable developer reads a flow and immediately spots the missing error handling, the missing audit log, the missing regulatory check.
Technology Stack
Real Industry Technology Stack — What Investment & Wealth Management Teams Actually Use. Every technology choice in Investment & Wealth Managementis driven by specific requirements — reliability, compliance, performance, or integration capabilities. Here's what you'll encounter on real projects and, more importantly, why these technologies were chosen.
The pattern across Investment & Wealth Management is consistent: battle-tested backend frameworks for business logic, relational databases for transactional correctness, message brokers for event-driven workflows, and cloud platforms for infrastructure. Modern Investment & Wealth Managementplatforms increasingly adopt containerisation (Docker, Kubernetes), CI/CD pipelines, and observability tools — the same DevOps practices you'd find at any modern tech company, just with stricter compliance requirements.
⚙️ backend
Java/Spring Boot
OMS, portfolio management, compliance engines
Python
Quant analytics, ML-based advisory, risk models
Go
High-frequency trading systems, low-latency APIs (Zerodha)
C++
Ultra-low-latency algorithmic trading engines
🖥️ frontend
React / Next.js
Wealth dashboards, investor portals
React Native / Flutter
Mobile trading and investment apps
Angular
Internal fund manager workbenches
🗄️ database
PostgreSQL
Portfolio data, transactions, investor records
InfluxDB / TimescaleDB
Time-series market data and pricing
Redis
Real-time quotes caching, session management
Oracle
Enterprise fund accounting and administration
🔗 integration
FIX Protocol
Industry standard for order routing to exchanges
Apache Kafka
Real-time market data streaming, trade events
REST / GraphQL APIs
Client apps, third-party data integration
SWIFT
Cross-border fund transfers and settlements
☁️ cloud
AWS
Most WealthTechs and modern platforms (Groww, Betterment)
Azure
Enterprise asset managers (institutional platforms)
GCP
ML/AI workloads for quant analytics
Co-location
Low-latency trading — servers co-located at NSE/BSE data centre
Interview Questions
Q1.What is the difference between a PMS and an OMS in investment management?
PMS (Portfolio Management System) tracks what you own — holdings, performance, risk, P&L. OMS (Order Management System) handles what you're doing — creating, routing, executing, and allocating trades. They integrate tightly: PMS identifies need to rebalance, OMS executes those orders. After trade settles, OMS sends confirmation back to PMS to update positions.
Q2.Explain T+1 settlement and its technical implications.
T+1 means trades settle 1 business day after trade date (India moved to T+1 in Jan 2023, one of first globally). Technical implications: 1) Tight SLA — all matching, confirmation, and position updates must complete same day, 2) Straight-through processing is critical — no manual intervention, 3) Fund managers need same-day NAV and margin availability, 4) Requires real-time integration between broker, NSCCL/ICCL clearing, and CDSL/NSDL depository.
Q3.How does NAV calculation work for mutual funds?
NAV = (Total Assets - Total Liabilities) / Number of Units Outstanding. Calculated daily after market close: 1) Mark-to-market all equity/debt holdings at closing prices, 2) Add accrued income (dividends, interest), 3) Subtract expenses (expense ratio accrual), 4) Divide by units outstanding. Published by AMFI by 9 PM. Investors who transact before cut-off (3 PM equity, 1 PM debt) get that day's NAV.
Q4.What is the FIX protocol and why is it important?
FIX (Financial Information eXchange) is an industry-standard messaging protocol for electronic trading. Key message types: New Order Single (place order), Execution Report (fill confirmation), Order Cancel Request, Mass Quote (for market makers). Important because it's universally accepted by exchanges and brokers globally — enables interoperability. India's NSE and BSE support FIX API for direct market access.
Q5.Explain how SIP works technically end-to-end.
1) Investor registers SIP → stored in platform DB and registered with AMC via BSE StAR MF / CAMS. 2) eMandate/UPI AutoPay registered with bank for auto-debit. 3) On SIP date: NACH/AutoPay debits investor account. 4) Platform creates purchase transaction. 5) Sent to AMC (directly or via RTA). 6) AMC allots units at that day's NAV after 3 PM cut-off. 7) Units credited to investor folio. 8) Confirmation sent. SIP can be modified or stopped by cancelling mandate.
Glossary & Key Terms
AUM
Assets Under Management — total market value of investments managed
NAV
Net Asset Value — per-unit value of a mutual fund, calculated daily
SIP
Systematic Investment Plan — regular fixed amount investment in MF
XIRR
Extended Internal Rate of Return — return metric for irregular cash flows
OMS
Order Management System — manages trade order lifecycle
FIX
Financial Information eXchange — messaging protocol for electronic trading
RTA
Registrar and Transfer Agent — processes MF transactions (CAMS, KFintech)
SEBI
Securities and Exchange Board of India — capital markets regulator
AMFI
Association of Mutual Funds in India — MF industry body
VaR
Value at Risk — maximum expected loss at a given confidence level
TWR
Time-Weighted Return — portfolio return eliminating effect of cash flows
CDSL/NSDL
Central Depository Services Ltd / National Securities Depository Ltd — hold demat securities