Retail broking systems: order routing, margin and settlement

The four systems

Order management. Accepts the order, validates it against product rules and client permissions, checks it with risk, routes it to NSE or BSE, and tracks it through acknowledgement, partial fills, modification, cancellation and rejection. It has to be fast, correct under duplicate and out-of-order messages, and honest about state when the exchange session drops.

Risk management. Computes available margin and exposure continuously across segments, decides whether an order is permitted before it is sent, and triggers alerts and square-offs as positions move. This is the hardest real-time component in the stack and it is covered as a role in hiring a Head of Risk and RMS at a broker.

Back office and settlement. Obligations, pay-in and pay-out, holdings reconciliation against the depositories, corporate actions, contract notes, ledgers, and the client funds and securities segregation that SEBI supervises closely.

Client application. Order entry, positions, charts, funds, and increasingly the whole account relationship. It is the part customers judge the broker on and the part least related to whether the rest of the stack is sound.

The seam between them is where most incidents live. A fill that the OMS has and the back office does not, a margin released by RMS before settlement has confirmed, or holdings that disagree with the depository are all cross-system problems, which is why reconciliation is a first-class function in a broker rather than a finance task.

Margin, and why it dominates the architecture

Indian margin rules are prescriptive and enforced at the moment of order placement rather than at the end of the day, which turns margin from an accounting concept into a latency-sensitive computation.

The components a system has to hold and recompute include span and exposure margin for derivatives, VAR and extreme loss margin for cash, the broker's own additional margin where applied, and the effect of collateral after haircuts. These change as prices move, as positions change and as the exchange publishes new parameter files.

Two regulatory features drive the design:

Upfront collection. Margin must be available before the order is accepted, not arranged afterwards. The margin check therefore sits inline on the order path with a latency budget, which is why brokers run a dedicated margin engine rather than querying a database.

Peak margin reporting. Compliance is assessed against snapshots taken at random points during the day rather than against an end-of-day position. A system that is compliant on average and non-compliant intraday will be penalised. The architectural consequence is that intraday state has to be correct and recordable at every instant, not merely reconcilable at close.

Collateral adds the third dimension. Securities pledged and re-pledged under the margin pledge framework carry haircuts, change in value continuously, and have their own operational lifecycle of pledge, invocation and release. Systems that model collateral as a static value fail on volatile days, which are exactly the days the value matters.

Settlement: T+1, T+0 and the UPI block

India completed its move to a T+1 settlement cycle across all listed scrips in January 2023, ahead of most major markets, and SEBI subsequently introduced an optional T+0 same-day cycle alongside it. Eligibility for the optional cycle has been extended in phases towards the top 500 companies by market capitalisation, with access opened to foreign portfolio investors and mutual funds, and brokers permitted to charge differential brokerage for it.

T+0 is optional for the investor rather than for every broker: under SEBI's circular of 10 December 2024, Qualified Stock Brokers must put the systems and processes in place to enable it, a deadline deferred by SEBI's circular of 30 October 2025 with a revised date to be notified. For engineering, the significant point is that T+0 is parallel. A broker supporting both runs two settlement cycles concurrently on the same book, which means the obligation computation, the funds and securities movement, the client ledger and the reporting all have to be cycle-aware. This is a larger change than the move from T+2 to T+1 was, because that was a compression of one pipeline and this is two pipelines side by side.

The other structural change is the UPI block mechanism, an ASBA-like facility for the secondary market, under which client funds remain blocked in the client's own bank account and move only on settlement rather than being transferred to the broker in advance. Since 1 February 2025, Qualified Stock Brokers must offer either this or a 3-in-1 account alongside existing options, with the client choosing.

The engineering implications are substantial and frequently underestimated. Funds are no longer in the broker's account, so the margin computation has to reference a block held elsewhere, confirmed through a different rail, with its own failure modes. Block creation, modification, release and debit each become states in the order and settlement lifecycle, and a failure in any of them is customer-visible at the moment of trading.

The derivatives framework and what it does to load

SEBI's circular of 26 May 2025 standardised expiry days: weekly benchmark index contracts may expire only on a Tuesday or a Thursday, with each exchange permitted one weekly benchmark index contract. NSE moved its weekly expiry from Thursday to Tuesday and BSE moved Sensex from Tuesday to Thursday, both effective 1 September 2025. Other derivative contracts carry a minimum tenure of one month and expire on the last Tuesday or last Thursday, at the exchange's choice, and exchanges must seek SEBI's prior approval before launching or changing any contract's expiry or settlement day.

The stated intent was to space out expiry concentration through the week. For platform engineering, the practical effect is that peak load is now distributed across two named days rather than concentrated, but each of those days is still an extreme event, and the capacity planning has to be built around them rather than around average volume. A system sized for average Indian broking load fails on expiry, and expiry is when customers care most.

SEBI has also tightened intraday position limit monitoring for index derivatives, which pushes more computation into the real-time path rather than into end-of-day reporting.

Where broking systems break

Market open. The first minutes carry a disproportionate share of the day's orders, and systems that are comfortable at average load queue, time out or reject. A broker whose platform is unusable at 9:15 has a commercial problem regardless of how it performs the rest of the day.

Expiry day in RMS. Positions move fast, margin requirements change sharply, and the square-off logic executes at volume. This is where the risk system's design is tested and where errors become public.

Order state ambiguity. The order was sent, the acknowledgement did not arrive, the client retried. Did it execute once, twice or not at all? Exchange session drops, duplicate messages and timeout handling produce a small number of genuinely ambiguous cases daily, and how a system resolves them determines whether clients lose money.

Holdings against the depository. The broker's record and the depository's record must agree. Corporate actions, bonus issues, splits, buybacks, pledge movements and off-market transfers all create divergence that has to be found and fixed, usually before the client notices.

Back office as the forgotten system. Front-end investment is visible and well funded. The back office is where contract notes, ledgers, segregation reporting and regulatory extracts are produced, and where inspection findings originate. A great many Indian brokers run a modern front end on a back office that has not been meaningfully reworked in a decade.

Regulatory change cadence. The genuine structural problem in this domain. A platform that cannot absorb a margin rule change, a new reporting field or a settlement cycle variant within a release cycle will consume most of its engineering capacity on compliance work, permanently. Architecting for regulatory change, by externalising rules and parameters rather than coding them, is the single highest-leverage decision in a broking stack.

Who builds this

The honest market picture: India has a genuinely deep pool of broking technology talent by global standards, concentrated in the large discount brokers, the bank-owned brokers, the exchange and depository technology arms, and a handful of platform vendors. What is scarce within that pool is the engineer who has owned a real-time component through a volatile session and a regulatory change, rather than one or the other.

How to assess

Ask about their worst market open or expiry. The defining question for this domain. What broke, what the queue looked like, what they changed. Everyone with real exposure has an answer.

Ask how they handle an ambiguous order outcome. Sent, no acknowledgement, client retried. Strong candidates immediately discuss idempotency keys, exchange-side query and reconciliation, and what they tell the client in the meantime.

Probe a regulatory implementation. "Describe a margin or reporting change you implemented and how long it took." This reveals whether the platform externalises rules or hard-codes them, which is the most important thing to learn about any candidate's previous system.

Test the back office awareness. Ask what happens to holdings after a corporate action. Candidates from front-end teams often cannot answer, which is fine if the role is front-end and disqualifying if it is not.

Check the T+0 and UPI block thinking. "What does supporting an optional same-day cycle alongside T+1 change in your settlement design?" A candidate who has thought about it describes cycle-aware obligations. One who has not treats it as a configuration flag.