Broker Process Narrative

Where this fits. This is the Broker Process Narrative — the operator’s chronological story of an active client account. It starts where Onboarding ends (mobile OTP → ACTIVE) and runs through first trade, a full trading day (BOD → trading hours → EOD → overnight), settlement, daily reporting, recurring cycles (weekly / monthly / quarterly / annual), and lifecycle events. For depth on any specific topic (margin, surveillance, audit, settlement), branch into Operations Deep Dives. For per-scenario walkthroughs (re-KYC, modifications, closure), see Lifecycle events. For the obligation inventory, see Compliance Blueprint.

TL;DR

• What this is: narrative continuation of onboarding — picks up at ACTIVE, walks through first trade, a full trading day operator-view (BOD → trading hours → EOD → overnight), settlement, daily reporting, recurring cycles (weekly / monthly / quarterly / annual), and lifecycle events.
• Audience: operators, new hires, and reviewers who need an end-to-end mental model before drilling into specific systems.
• What this is NOT: how-to build the systems (separate future sub-project), vendor selection (see Vendor Atlas), regulatory primer (see Regulatory Circulars and Compliance Blueprint).
• AI-generated synthesis. Verify any specific provision against the linked circulars before acting.

Conceptual overview

Indian stock broking operations run on a daily clock. A trading day starts hours before the market opens — back-office scripts pull files from exchanges and depositories — and ends hours after it closes, with settlement obligations submitted, ledgers updated, and regulatory reports filed. Around this central rhythm sit weekly, monthly, quarterly, and annual cycles. Around the broker’s operational rhythm sits the client’s account lifecycle — onboarding, first trade, ongoing modifications, eventual dormancy or closure. This page tells that story.

1. From ACTIVE to First Trade

The final gate of onboarding flips three independent flags to green — KRA Registered, BO (Beneficiary Owner) Active at the depository, and UCC (Unique Client Code) Approved at every elected exchange — and only then does the application status machine transition to ACTIVE. Most of what happens next is invisible to the client but takes the broker’s back-office an evening to complete.

Day 0 evening — the welcome cascade

Within minutes of ACTIVE, the broker’s back-office runs a “welcome cascade” routine. A status notification is pushed to the client’s app and SMS / email via DLT-approved templates (every transactional message must be sent against a header and template ID pre-approved with the telecom DLT registry, per SEBI’s December 2024 communications mandate). A welcome kit is emailed: account-opening confirmation letter, MITC (Most Important Terms and Conditions) document signed during eSign, DP (Depository Participant) details and BO ID, segment activation status (CM live by default; F&O / CD / COM live if elected during Screen 6), brokerage and charges schedule, and quick-start links.

Behind the scenes, two more things happen. First, the client’s record is propagated to the broker’s back-office — TechExcel, Mihir, Shilpi, Aastha, or whatever the broker uses — with margin parameters, segment activation flags, and limit allocations. Second, RMS initializes the per-client margin envelope: available margin starts at zero (no funds transferred yet), exposure margin parameters are loaded from the day’s SPAN scanrange, and the client’s name appears in the surveillance NORMS roster as an active retail account.

Day 1 morning — first login

The client logs in. Their dashboard shows account number, BO ID, segment activations (typically CM live; F&O / CD / COM pending margin), fund balance (zero unless they’ve already transferred), available margin (also zero), and an empty holdings list. To trade, they need to transfer funds — typically via the broker’s payment partner (UPI Block, AutoPay, NEFT, IMPS, or directly from a linked bank). For Qualified Stock Brokers, ASBA-style UPI Block is mandatory since February 2025: funds aren’t actually transferred to the broker’s pool, they’re blocked in the client’s bank account and debited only on trade execution, which both earns the client interest and reduces the broker’s counterparty risk.

Placing the first order

Order capture happens via web, mobile, dealer terminal, or API. Whatever the entry point, the order traverses an identical pre-trade RMS pipeline before the broker’s OMS releases it to the exchange:

1. Segment activation check. Is the segment (CM / F&O / CD / COM) live for this client? Hard-block if not.
2. Available margin lock. Does the client have enough margin for the order? For cash-segment buys, margin = SPAN + ELM + exposure + additional + delivery (where applicable); for sells, margin is computed against the client’s existing holdings or upfront margin per SEBI rules. The required margin is reserved against the client’s available margin balance.
3. MWPL check (derivatives only). If the order would breach the Market-Wide Position Limit, hard-block at the OMS layer.
4. Order-type validation. NRML (carry-forward), MIS (intraday, auto-square-off at 15:20), CO (cover order), BO (bracket order). Each has its own risk profile and time-cut.
5. GSM / ASM / restricted-stock check. Is the security on a surveillance restriction list? Some symbols are tradeable only with 100% upfront margin (T2T), some only in cash segment, some not at all for retail.

If everything clears, the OMS releases the order to the exchange via leased line + FIX gateway (typical for institutional brokers) or ETI / Connect2NSE / BEFS (typical for member-broker integration with NSE / BSE). The exchange returns an order acknowledgement with an exchange-generated order ID, which the OMS persists. If the order matches, the trade confirmation comes back; the client sees their first execution.

Note

Why pre-trade margin lock happens before exchange acknowledgement. SEBI mandates that brokers cannot release any order to the exchange without confirming sufficient client margin (the rule has been progressively tightened since 2020, and peak-margin reporting captures snapshots throughout the day to enforce it). If the broker’s OMS skips the margin check, the broker’s own funds end up funding the order — which is a violation of client funds segregation rules and exposes the broker to credit risk.

After the first trade

Trade booking happens immediately in the back-office: brokerage, STT (Securities Transaction Tax), exchange transaction charges, SEBI turnover fee, GST on brokerage + exchange charges, and stamp duty are all computed and attached to the contract. Intraday MTM accrues on the open position throughout the day. By T+24h (typically the evening of the trade day), the contract note is generated as a signed ECN (Electronic Contract Note), the broker’s Digital Signature Certificate is applied, and the document is dispatched via SMS link and email per the DLT-approved templates. The client’s first trade is, from the system’s perspective, just one of thousands of trades that will pass through the same pipeline; for the operator on the back end, it’s a checkpoint that confirms the onboarding pipeline actually delivers a trading account.

2. A Trading Day — operator’s view

A trading day looks like a few hours of market activity bracketed by a few hours of file movement, system checks, and reconciliation. From the operator’s seat, the day starts at 06:00 IST and ends past 23:00 IST. The customer sees only 09:15 to 15:30; everything else makes that window possible.

BOD (06:00–08:30)

The Beginning-of-Day phase is mostly file ingestion. Each exchange and clearing corporation publishes a set of files that the broker must download, validate, and apply before the market can open. Most ops teams arrive by 07:30; the market services / IT team initiates BOD scripts as early as 06:00 to leave buffer for failure.

From the exchanges, per segment (CM, F&O, CD, and COM if MCX is elected), the BOD downloads include:

• Holiday calendar — published annually and refreshed for any mid-year amendment. Drives the trading-day check on every BOD.
• Contract files — the day’s tradable symbols, lot sizes (for derivatives), tick sizes, market-lot rules. Without this file, the OMS cannot validate orders.
• SPAN scanrange files from the clearing corporation — margin parameters (SPAN, ELM ratios, exposure margins) for derivatives. Applied for the entire day; never re-issued mid-day. The clearing corp publishes these, not the exchange, because margin computation is a clearing-side responsibility (NSCCL for NSE, ICCL for BSE, MCXCCL for MCX).
• Circuit-filter file — per-stock daily price band (typically 2 / 5 / 10 / 20 %, occasionally no-band for index constituents). The OMS rejects any order at a price outside this band.
• Member files — the exchange’s list of active members, including any suspensions or trading-disabled flags issued overnight.
• MTM T-1 file — yesterday’s close prices and per-position MTM, needed for accurate overnight margin computation on carried-forward derivative positions.

From the depositories (CDSL and / or NSDL, depending on the broker’s primary), the BOD pulls in prior-day obligation files (any settlement items due to be honoured today), pledge status updates, DDPI activations finalized overnight, transmission updates, and any account-modification reflections from yesterday’s UCC / KRA / depository uploads.

RMS parameter reload. With the SPAN scanrange and ELM ratios in hand, the RMS recomputes per-client margin envelopes. Available margin, blocked margin, and free balance are recalculated based on each client’s outstanding positions, fund balance from last night’s payin / payout, and today’s parameter set. This snapshot is then published to the OMS for pre-trade margin checks. The reload typically completes by 08:30 — leaving 45 minutes of buffer before the pre-open begins.

Surveillance start-of-day. GSM (Graded Surveillance Measure) lists, ASM (Additional Surveillance Measure) lists, LT-ASM lists, T2T (Trade-to-Trade) segment lists, and restricted security lists are pulled from the exchanges and ingested into the surveillance filter. Market surveillance systems re-arm their alert rules — concentrated position thresholds, OTR (Order-to-Trade Ratio) accumulators, illiquid-security monitoring, social-media surveillance feeds — for the day’s trading.

Operational health checks. The market services team confirms FIX session login to each exchange, CTCL approval status for any modified order-type configurations, trading-software heartbeat to exchange gateways, DR-site replication confirmation (per BCP / DR requirements), and CSCRF log-feed verification (per the cyber security mandate). Any anomaly here — a failed FIX session, a missed scanrange file, a stale heartbeat — is escalated immediately; the broker can’t trade if BOD doesn’t complete cleanly.

Caution

If BOD fails to complete by 09:00, the broker cannot trade. Operations teams maintain a runbook with an escalation path: failure to ingest scanrange → escalate to clearing corp helpdesk; missed contract file → re-download from a known alternate path (NSE has multiple FTP endpoints); stale RMS parameter → run a manual reload script. Most large brokers have on-call rotation covering 05:30–09:00 specifically for BOD failures. The cost of missing pre-open is real: orders sitting in queue overnight (AMOs) fail to release, clients see error messages, and revenue is lost for the day.

Note

Why SPAN scanrange comes from the clearing corporation, not the exchange. The exchange (NSE / BSE / MCX) runs the order-matching engine and surveillance. The clearing corporation (NSCCL / ICCL / MCXCCL) is the central counterparty that takes the settlement risk and computes margins. SPAN — Standard Portfolio ANalysis of Risk — is a margin methodology owned by the clearing layer because that’s where credit exposure lives. The exchange consumes SPAN parameters from its sibling clearing corp to validate order-level margin during the trading session, but the file’s authoritative source is the clearing layer.

Pre-open (09:00–09:15)

Pre-open is a 15-minute call-auction window where the day’s opening price is discovered. Order entry runs from 09:00 to 09:08; orders entered are accumulated and matched at 09:08–09:12 to produce a single uncrossed opening price; from 09:12 to 09:15 the market is in “buffer” mode (no new orders, just system synchronization) before continuous trading begins at 09:15.

The broker’s OMS routes pre-open orders identically to continuous-trading orders, with the same pre-trade RMS pipeline applied. The wrinkle is that AMOs (After-Market Orders placed by clients the previous evening, typically between 15:45 and 08:59) are released into pre-open as a batch at 09:00 — the OMS holds them overnight, then submits them in priority order at market open. Pre-trade RMS still applies; some AMOs may be rejected if the client’s margin position has changed overnight (e.g., a held position incurred MTM loss large enough to consume previously-available margin).

For the operator, pre-open is mostly a watch-and-wait phase. If anything in the BOD ingestion was incomplete, the symptoms surface here: orders rejected with cryptic codes, the OMS reporting unrecognised contracts, surveillance flags firing on clean orders. The on-call team has roughly 15 minutes to triage anything visible at 09:00 before continuous trading begins.

Trading hours (09:15–15:30)

Continuous trading runs from 09:15 to 15:30, six hours and fifteen minutes during which the OMS, RMS, and surveillance systems are operating at their highest load. Operationally, the broker’s responsibilities in this window cluster around four things: pre-trade validation, intraday margin reporting, real-time surveillance, and intraday compliance events.

Pre-trade validation. Every order goes through the same RMS pipeline described in Section 1 — segment / margin / MWPL / order-type / surveillance checks — applied at single-digit-millisecond latency. The OMS releases approved orders to the exchange; rejected orders return to the client with reason codes. Most large brokers process tens of thousands of order events per second at peak; performance and reliability of the RMS layer is one of the biggest investments in the broker’s tech stack.

Intraday peak margin snapshots. This is the most operator-load-heavy item in the trading window. The clearing corporation captures four peak-margin snapshots during the trading session — at 11:30, 12:30, 13:30, and 14:30 IST. At each snapshot, every member-broker is expected to have sufficient client-collected margin covering all client positions. The broker generates and submits the Daily Margin File (DMF) post-EOD reconciling these four snapshots; the clearing corp issues a peak-margin response file flagging any shortfall. Penalties for shortfall are real and material — they scale with the size and frequency of the breach and have suspension consequences for repeated patterns. The RMS must keep margin position stable across each snapshot window, which means avoiding settlement-driven swings (e.g., a payout received mid-day shouldn’t relieve a position that needed margin at the 11:30 snapshot).

Real-time surveillance. NORMS at the exchange runs continuously; the broker’s surveillance system mirrors much of this server-side. Order-to-Trade Ratio (OTR) accumulators tick up with every order entry / modification / cancellation; if a client’s OTR breaches the threshold, additional margin or order-rate-limit is imposed. GSM / ASM list-based intervention happens at the order-entry layer — orders for stocks on the highest GSM stage may require 100% upfront margin or be restricted entirely. Social-media surveillance, mandated since April 2024, monitors public channels for evidence of manipulative coordination (pump-and-dump, ramping). Manipulative-trade flagging tags self-trades, wash trades, layering, and spoofing for post-EOD review.

Block-deal windows. Two windows allow block deals: the morning window from 08:45 to 09:00 (before continuous trading) and the afternoon window from 14:35 to 15:05. Block deals have distinct reporting requirements — minimum quantity, price-band, and disclosure rules — and feed into a separate reporting flow.

MWPL checks. Derivatives have Market-Wide Position Limits at the contract level. The OMS rejects orders that would breach MWPL; the surveillance layer monitors approach to MWPL and may issue advisories ahead of breach.

Intraday compliance events. Some compliance items are time-bound during the trading window: a technical glitch report to SEBI within prescribed minutes if there’s a member-side outage; surveillance alert escalation to the exchange within prescribed timing; CSCRF incident reporting to CERT-In within six hours.

Closing window (15:30–15:40)

The market session ends at 15:30 with the trading bell. From 15:30 to 15:40 the closing auction runs — a brief call-auction window that produces the official settlement price for each security. The settlement price is the volume-weighted average of trades in the last half-hour for most stocks, or the closing-auction-determined price where the auction is active. This price is what feeds into MTM end-of-day, contract note brokerage computation, and overnight margin recomputation.

The final peak-margin snapshot for the day is captured at 14:30, before the closing window, so margin behavior post-15:30 doesn’t affect the day’s peak-margin record. From the operator’s view, the closing window is the cleanest part of the trading day — no new orders, no MTM swings of consequence, just price discovery.

EOD (15:40–19:00)

EOD is reconciliation and reporting time. Three or four hours of back-office work to close out the trading day.

Trade booking. Every trade executed during the day is reconciled in the broker’s back-office system. The back-office receives end-of-day trade files from each exchange (CM, F&O, CD, COM trade files in their respective formats), matches them against orders captured by the OMS, computes brokerage and charges (brokerage per the client’s schedule, STT, exchange transaction charges, SEBI turnover fee, GST on brokerage + exchange charges, stamp duty by state), and posts the trades to the client’s ledger.

Contract note generation. By T+24h (typically the evening of the trade day, though SEBI rules allow up to next-day-by-12-noon dispatch), the broker generates a signed ECN (Electronic Contract Note) for each client who traded today. The format is prescribed (ICAI and SEBI specify the columns and disclosures); the broker’s Digital Signature Certificate is applied to the PDF; the document is dispatched as a link via SMS (per DLT-approved templates) and as an attachment via email.

MTM end-of-day. All outstanding derivative positions and pending-settlement equity positions are marked-to-market against the day’s closing prices. MTM gains and losses are realized in the back-office ledger; the realized P&L feeds the next day’s available-margin calculation.

Position files. The back-office generates position files for each segment — open interest at the client level, the broker level, and aggregated for clearing-corp reporting. These flow to the clearing corp via SFTP.

Obligation files flow inbound from the clearing corp — payin amounts the broker must deliver tomorrow morning (funds for buys settling, securities for sells settling), and payout amounts the broker will receive (funds for sells, securities for buys). The back-office processes these and prepares the next-day settlement instructions.

Peak margin response file. The clearing corp publishes the peak-margin response file in the EOD window. The back-office reconciles this against the DMF the broker will submit, flags any shortfall to the compliance team, and computes the penalty exposure.

Member compliance reporting. CAR (Compliance Audit Report) submissions, DPC (Designated Principal Compliance) updates, and any inspection-mandated reports are submitted to the exchange via BEFS (BSE) / ENIT (NSE) / MCX member portal. Some items are intraday; most batch out at EOD.

Settlement & overnight (19:00–06:00)

Past 19:00, the broker’s focus shifts to settlement and overnight prep.

Payin obligation. For trades settling tomorrow (T+1), the broker must honour the payin obligation: funds from the client’s funds bank account to the clearing bank, securities from the broker’s depository pool (or, post-direct-payout, directly from the client’s demat) to the clearing pool. Payin cut-off is typically 11:00 the next morning, but most brokers pre-stage instructions overnight.

Payout from clearing. For trades the broker is owed (sells delivered, buys funded), the clearing corp releases funds and securities. Post the SEBI June 2024 direct-payout-to-demat mandate (phased in two stages — November 2024 phase 1, January-February 2025 phase 2), securities flow directly from the clearing pool to the client’s demat without parking in the broker’s pool account. Funds still settle to the broker’s client-funds bank account.

Daily client funds upstreaming. Per the June 2023 SEBI mandate, brokers upstream client funds to the clearing corp on a daily basis — funds, FDRs, MFOS instruments, or other eligible collateral. The intent is to remove client funds from the broker’s balance sheet to the maximum possible extent, reducing client exposure to broker default. The actual upstreaming runs overnight or first-thing-next-morning depending on the broker’s bank cut-offs.

Bank reconciliation. The broker’s client-funds bank book (three or four bank accounts: BA1 for client funds, BA2 for own funds, BA3 for settlement, etc., per the segregation framework) is reconciled against bank confirmations and clearing-corp acknowledgements. Discrepancies are flagged for compliance review the next morning.

KRA daily upload. Any KYC modifications captured during the day — address changes, bank account updates, nominee changes, segment additions — are uploaded to the relevant KRA (CVL / NDML / DOTEX / CAMS / KFintech) overnight. Similarly, any new clients onboarded today (who flipped ACTIVE during business hours) are pushed to KRA.

CKYC upload. Within seven days of any KYC change, the broker must upload to CKYC (Central KYC Registry, operated by CERSAI). Most brokers run a daily upload to stay within the seven-day window comfortably.

Ledger update. The back-office runs a nightly batch updating every client’s ledger with the day’s trades, charges, MTM accruals, MTM realizations, settlement entries, and any corporate-action entries that fell on today’s record date.

Prep for next BOD. System health checks confirm overnight-batch completion. Log rotation runs (CSCRF retention rules typically require minimum 180 days of operational logs). Backup integrity verification confirms last night’s full backup is restorable. DR-site replication confirmation closes out the day’s compliance items. By 06:00 next morning, the cycle restarts.

Caution

Peak-margin shortfall has compounding cost. A single snapshot shortfall draws a percentage-based penalty (the exact slabs are in the clearing corp’s penalty circular). Repeated shortfalls in a month escalate the penalty rate; sustained shortfalls trigger inspection and possible suspension. The compliance cost of a tight RMS during the four snapshot windows is dwarfed by the penalty cost of even moderate shortfall — which is why brokers invest heavily in real-time margin monitoring.

Tip

T+1 default versus T+0 beta. T+1 became default in January 2023; T+0 began as a beta in March 2024 for the top 25 stocks and expanded to the top 500 in December 2024. T+0 is a separate session from the regular session — not an acceleration. Brokers participating in T+0 effectively run a parallel settlement cycle for the day’s T+0-flagged trades. Most retail brokers default clients to T+1 unless the client opts in explicitly.

Note

Direct-payout-to-demat changed the broker pool-account structure. Before June 2024, the broker held client-bought securities in a pool account briefly during settlement. SEBI’s direct-payout-to-demat circular (phased Nov 2024 / Jan-Feb 2025) routes securities from clearing directly to the client’s demat, eliminating the broker’s intermediate custody. This required new pool-account designations — TM CUSPA (Trading Member Client Unpaid Securities Pledgee Account), CM CUSPA (Clearing Member equivalent), TM CSMFA (Trading Member Client Securities Margin Funded Account) — each with specific permissible balances. Brokers running their own chart of accounts had to update during the rollout windows.

3. The Settlement Cycle

The trading day produces obligations; the settlement cycle clears them. India has been on T+1 (trade plus one business day) settlement for the cash segment by default since January 2023 — among the fastest cycles globally. A T+0 (same-day) beta began in March 2024 and expanded in December 2024 to the top 500 stocks. Derivatives, MTF positions, and corporate-action items follow their own settlement clocks.

T+1 mechanics

For every trade executed today, settlement happens tomorrow. The broker has two obligations on T+1 morning: deliver funds for any net-buy positions, and deliver securities for any net-sell positions. Cut-offs are typically 11:00 IST for funds and 11:30 IST for securities; the clearing corporation then nets across all members, computes obligations, and runs the pay-in / pay-out cycle — funds out of paying brokers and into receiving brokers in the same session, securities similarly. By end of T+1 the client typically has the funds or securities they bought, though the broker’s intermediate processing may push the visible settlement to T+1 close.

T+0 beta scope

The T+0 segment runs as a separate session, not an acceleration of T+1. Orders flagged for T+0 trade in a defined window earlier in the day (currently 09:15–13:30 with settlement complete by EOD), match against T+0-eligible counter-orders, and settle the same evening. Only the top 500 stocks (as of December 2024) participate; the broker’s OMS must explicitly support T+0-flagged orders. Most retail brokers default clients to T+1 unless the client opts in.

Short delivery and auction

If a selling broker fails to deliver securities on T+1, the exchange auctions on T+2 morning to acquire the shortfall and complete the buyer’s settlement. The auction price plus a penalty are recovered from the failing broker. This is one of the visible failure modes a broker must monitor closely — a chronic auction pattern is both a financial cost and a surveillance flag. Typical causes are mis-mapped client securities, pledge release failures, or short-selling without inventory; each has different remediation.

Give-up and take-up

For institutional flow, the trade executor and the trade clearer are often different members. Give-up / take-up is the formal mechanism by which the execution member transfers the trade to the clearing member who will honour the settlement obligation. The exchange manages the give-up file format; the operational responsibility sits with both members to confirm the transfer within the day’s cut-off.

MTF settlement

Margin Trading Facility — where the broker funds the client’s purchase against pledged collateral — has its own settlement nuances. The bought securities are pledged to the broker as collateral; the broker pays the seller (via clearing); funds owed by the client to the broker carry as a loan. The broker maintains an “unpaid MTF” file tracking client positions where funds haven’t been received against MTF facility usage. SEBI’s framework requires that MTF positions be settled or unwound within specified timeframes.

Direct payout to demat (post June 2024)

Before June 2024, securities being paid out by the clearing corp landed first in the broker’s pool account, then the broker pushed them to the client’s demat. SEBI’s direct-payout-to-demat circular changed this — securities now flow directly from the clearing pool to the client’s demat, bypassing the broker’s intermediate custody.

The rollout was phased: phase 1 in November 2024 covering equity segment; phase 2 in January–February 2025 extending to additional segments. The change required restructuring broker pool accounts — TM CUSPA (Trading Member Client Unpaid Securities Pledgee Account, for trades where the client hasn’t paid), CM CUSPA (Clearing Member equivalent), and TM CSMFA (Trading Member Client Securities Margin Funded Account, for MTF pledged securities). Each account has specific permissible balances and reporting requirements; the back-office chart of accounts had to be updated during the rollout windows.

MFOS / FDR upstreaming

Margin Funded Order System (MFOS) instruments and Fixed Deposit Receipts pledged by the broker as collateral with the clearing corp are upstreamed daily per the June 2023 client funds upstreaming mandate. The intent of the mandate is to keep client funds off the broker’s balance sheet — held with the clearing corp or in segregated bank accounts instead — so that broker default doesn’t put client funds at risk. The broker submits collateral allocations to the clearing corp at EOD; the clearing corp confirms acceptance and applies the collateral against the broker’s margin obligations for the next day.

ASBA-style UPI Block (mandatory for QSBs since Feb 2025)

Qualified Stock Brokers — defined by SEBI based on client count, fund-base, and other thresholds — must offer ASBA-style UPI Block functionality, mandatory since 1 February 2025. The mechanism: the client’s funds aren’t actually transferred to the broker’s pool ahead of trading; instead, an amount equal to the client’s intended trading exposure is blocked in the client’s own bank account via UPI. When a trade executes, only the executed amount is debited from the block — the rest releases back. The client’s blocked funds earn interest in their own bank, and the broker’s counterparty exposure is reduced because the broker doesn’t hold client funds for the unutilised portion.

Payin default mechanics

If a broker fails to honour payin on T+1 — typically because of an internal funds shortage or operational failure — the clearing corp’s default fund (Core Settlement Guarantee Fund, or Core SGF) covers the obligation to keep the rest of the market settling cleanly. The defaulting broker faces immediate consequences: position closure, member suspension or cancellation, and recovery action by the clearing corp against the broker’s deposits and own funds. This is the worst-case outcome that the entire margin and upstreaming framework is designed to prevent.

Caution

Auction penalty is asymmetric. If a broker is on the failing side of a short delivery, the auction-acquired price plus a fixed-percent penalty are charged. The penalty rate is meaningful (typically several percent above the auction price), and the auction price itself can be substantially above the market price for an illiquid security. Repeated auctions in a month trigger surveillance and possible suspension. Most brokers prefer to buy in the open market to cover known shorts before the auction, even at a loss, rather than face the auction penalty.

Note

UPI Block changed the broker’s funds-handling model. Pre-Block, brokers held client funds in a pool account, earned float on it (within SEBI rules), and faced credit risk if a client defaulted on a trade. With UPI Block, the funds stay in the client’s bank, earning interest for the client. The broker loses the float economics but gains a cleaner counterparty model — no funds to upstream for the unutilised portion, no segregation overhead for those amounts. For Qualified Stock Brokers the switch is mandatory; smaller brokers can offer it as an option, and several have done so to differentiate.

4. Daily Reporting Touchpoints

Most of the day’s compliance evidence is produced by side-effect of normal operations. A few items, though, need explicit reporting submissions — daily or near-daily flows to regulators and clearing infrastructure. Each item below is one of those touchpoints, with the artefact that proves it was done.

Daily Margin File (DMF)

The DMF is the most operationally consequential daily report. Generated post-EOD from the day’s four intraday peak-margin snapshots (11:30 / 12:30 / 13:30 / 14:30), it is submitted to the clearing corp and reconciled against the clearing-corp’s peak-margin response file. Shortfalls trigger penalties. The DMF format is prescribed by NSCCL / ICCL / MCXCCL with member-segment-specific columns. See the Margin compliance domain for the full row.

Client Funding Report (CFR)

A weekly submission (typical Friday cut-off), not daily — but mentioned here because the data collection is daily. The CFR captures client-by-client funding positions (funds collected, deployed, free, blocked) across the week. Submitted to the exchange in the prescribed format.

UCC daily upload

New clients onboarded today (any client whose application reached ACTIVE in business hours) and modifications to existing clients (address, bank, segment activation) feed the daily UCC upload to NSE, BSE, and MCX. The exchange acknowledges with status codes per client; rejections require manual remediation the next morning.

KRA daily upload

Any KYC modification or new KYC record from the day is uploaded to the relevant KRA (CVL, NDML, DOTEX, CAMS, KFintech). The submission is typically batched overnight. KRA acknowledges within its own SLA — most return “Registered” same day, with “Validated” status following in 2–3 days.

Peak margin snapshots

The four intraday snapshots are themselves the evidence — the broker’s RMS preserves snapshot-time client position and margin state for clearing-corp inspection. The DMF is the consolidated daily artefact, but each snapshot is a discrete compliance event.

Surveillance reports

NORMS-driven surveillance produces a slate of daily reports: Order-to-Trade Ratio breaches, GSM-list trade reports, abnormal-trade flags, social-media surveillance findings, manipulative-trade tags. Some flow real-time to the exchange (technical glitches, system outages); most batch out at EOD.

CSCRF logs

The cyber security framework mandates retention of operational logs — typically 180 days minimum, longer for specific log categories. The daily touchpoint isn’t a submission but a verification: the log feed is intact, rotation has run, the backup is restorable. Auditors will sample these during the annual cyber audit.

Technical glitch reports

If any operational glitch caused order rejection, system downtime, or material customer impact, SEBI requires intraday reporting within prescribed minutes. The exchange has a dedicated channel for these reports. False alarms still get logged but with lower escalation.

CTR (Cash Transaction Report) to FIU-IND

Mandatory under PMLA whenever cash transactions cross the Rs.10 lakh threshold per client per month — relatively rare in pure broking but possible. Reported via FIU-IND’s FINnet 2.0 portal using the prescribed XML format. See the AML domain.

STR (Suspicious Transaction Report) to FIU-IND

Event-triggered, not daily — but the operational flow is daily. The broker’s surveillance team reviews flagged trades and customer patterns daily; if a pattern crosses the threshold for suspicion (per the broker’s documented STR policy), the report is filed within the prescribed window. Most days produce zero STRs; the systematic part is the daily review itself.

Sanctions list re-check

UNSC and India MEA UAPA lists update periodically. Brokers are required to screen their active client base against the current list — typical implementation is a daily delta check (new additions to the list vs. existing client base). Hits trigger immediate action under PMLA / UAPA frameworks.

Tip

Evidence trails: which file proves which compliance? Operators sometimes find themselves in audits where the same trade file is cited as evidence for margin compliance, settlement compliance, and surveillance — and that’s correct. The trade file is the primary record; downstream artefacts (DMF, position file, surveillance report) all derive from it. Mapping evidence-to-source once and reusing that map across compliance domains is one of the highest-leverage exercises a new compliance officer can do.

5. Recurring Cycles

The daily clock is the densest layer; on top of it sit weekly, monthly, quarterly, half-yearly, and annual cycles. Each cycle has its own owner role and evidence artefacts. Most operations teams build a master compliance calendar from these cadences and slot recurring items into the weekly ops standup agenda.

Weekly

• Client Funding Report (CFR) submission to the exchange, typically with a Friday cut-off, covering the prior week’s client funding positions. Owner: Compliance Officer.
• Internal reconciliation — broker’s client funds bank books reconciled against bank statements, clearing-corp confirmations, and the broker’s back-office ledger. A reconciliation break flagged late in the week becomes a compliance event by the next weekly cycle if not closed.

Monthly

• Client funding to exchange — monthly aggregated submission of client-level funding positions per exchange-prescribed format. Different from the weekly CFR; deeper aggregation.
• GST returns — monthly under the regular regime (GSTR-1 by 11th, GSTR-3B by 20th). GST applies on brokerage and exchange charges; the broker must collect and remit. Owner: Finance / Accounts.
• TDS deposit — monthly deposit by 7th of next month for tax deducted at source (typically TDS on dividends paid via the demat account, NRI client payouts, etc.).
• STT monthly deposit — Securities Transaction Tax collected on every trade is remitted monthly. Reconciled to exchange records.
• Complaint MIS — monthly grievance summary to the exchange and SCORES; counts of complaints received, disposed, pending, by category. Owner: Customer Service Lead / Compliance.
• Networth maintenance check — minimum networth (Rs.3 crore for a stockbroker, segment-specific higher thresholds for clearing membership) must be maintained; a monthly check ensures no breach has occurred since the last quarterly statement. Owner: Finance / Compliance.

Quarterly

• Running-account settlement at calendar quarter-ends (April, July, October, January) — SEBI mandates that all funds and securities lying with the broker beyond the client’s actual exposure be returned to the client unless the client has explicitly authorized retention. The authorization itself has format requirements (specific consent text, periodic renewal). This is one of the most-penalty-attracting items in SEBI inspections; brokers run the settlement on the 31st / 30th of the quarter-end month and produce a per-client artefact (statement of account confirming zero-balance or authorized retention).
• FATCA / CRS refresh — for foreign-tax-residency clients, quarterly self-certification refresh and reporting cycle.
• BCP drill — quarterly disaster-recovery test (some member categories require half-yearly; clearing corp mandates quarterly). The broker runs failover from primary to DR site, validates trading-system continuity, documents the drill, submits the report to the exchange / clearing corp. Owner: CISO / IT / Compliance.
• Quarterly statement of accounts — issued to every active client; covers trades, charges, ledger entries, holding positions. Mandatory dispatch via email per SEBI investor servicing framework.

Half-yearly

• Compliance certificate to SEBI — signed by the broker’s Compliance Officer attesting to compliance with all applicable SEBI / exchange / depository rules for the period. Submitted to SEBI via the prescribed portal.
• Internal audit report submission — the broker’s appointed internal auditor (independent CA firm) submits a half-yearly internal audit report to SEBI, covering broker funds, securities, operational controls, and compliance evidence. Owner: Internal Auditor / Compliance.

Annual

• Statutory audit — annual audit by an independent CA firm; produces the broker’s audited financial statements. Filed with SEBI, exchanges, and tax authorities.
• KRA audit — annual audit of the broker’s KYC processes, KRA upload accuracy, and CKYC compliance. Conducted by a SEBI-empanelled auditor; report submitted to SEBI.
• System audit — every two years per SEBI (alternate annual cycle); covers IT systems, RMS, OMS, back-office, surveillance, cybersecurity. Conducted by a CERT-In-empanelled auditor.
• DP audit — annual audit of the broker’s depository participant function (CDSL or NSDL or both). Covers BO opening / modification / transmission / pledge processes.
• Cyber audit per CSCRF — annual or biennial depending on the broker’s CSCRF category (Qualified RE / Mid-size RE / Small RE per the August 2024 framework).
• Fit-and-proper refresh — annual self-certification by directors, KMPs, and senior management; continuing fit-and-proper compliance per SEBI Intermediaries Regulations.
• NISM re-certification — for compliance officer, principal officer, authorized persons, dealers; NISM certifications have validity windows (typically 3 years) and re-certification cycles. Tracking and ensuring no certifications expire is an ongoing task with annual visibility.
• ITR Form-16A dispatch — annual TDS certificates dispatched to clients who had TDS deducted by the broker.
• Advertisement approval renewal cycles — running advertising programs require periodic re-approval by the exchange / SEBI; the broker maintains the active-approvals register.
• Exchange membership renewal — NSE, BSE, MCX membership fees and compliance attestations renewed annually.

Event-triggered (briefly)

• Loss events — operational losses (system failure, fraud, settlement default) require reporting within prescribed windows.
• Technical glitches — reported intraday (mentioned in Section 4) plus a post-incident review cycle.
• KMP changes — director, compliance officer, principal officer changes intimated to SEBI and exchanges within prescribed days.
• Segment additions / branch openings — new segment activation, new branch location, new authorized person each have their own intimation flows.

Caution

Quarterly running-account settlement is strictly enforced. This is the single most-frequently-penalized item in SEBI broker inspections. The rule is unambiguous: funds and securities beyond the client’s actual exposure must be returned at the end of each calendar quarter unless the client has explicitly authorized retention in the prescribed format. Implicit “convenience” retention by the broker — even if the client doesn’t object — is a violation. The authorization itself has periodic renewal requirements. Most brokers run a strict end-of-quarter sweep with a per-client artefact and a follow-up confirmation cycle.

Tip

Build the compliance calendar. The single highest-leverage exercise a new compliance officer can do is to take every item in Section 4 and Section 5 of this page, plus every row in the Compliance Blueprint, and slot them into a master calendar by day-of-week / day-of-month / date-of-quarter. The calendar drives the weekly standup agenda, the month-end checklist, the quarter-end project plan. Done well, this calendar is one of the most-referenced documents in the compliance function and survives staff turnover better than most operational systems.

6. Lifecycle Events

An account that’s gone ACTIVE rarely stays static. Clients change address, change banks, add nominees, activate new segments. Some accounts go dormant; some close voluntarily; some pass to a nominee on death. Some clients become NRIs or stop being NRIs. Each event has its own flow, its own evidence trail, and its own constellation of regulatory touchpoints.

Modifications

Address change. Triggered by client request with proof (Aadhaar / utility bill / bank statement under three months old). Updates flow to: KRA (daily upload), CKYC (within 7 days), exchange UCC (next daily upload), depository BO records (next batch). The change is treated as a re-KYC trigger for the address field only; the full re-KYC cycle is not restarted.

Bank account change. Penny-drop verification on the new account (Re. 1 transfer with name-match validation). On success, the change is propagated to KRA, exchange UCC, and depository (for direct-payout-to-demat routing). Settlement must continue uninterrupted; if a settlement is pending when the change request arrives, the broker typically completes pending settlements on the old account before switching.

Nominee change. Per the SEBI January 2025 nominee revamp (see journey screen 7 for the onboarding-time capture), up to 10 nominees may be added with percentage allocation (must sum to 100%). The change is eSigned by the client. For demat accounts, the change flows to the depository; for trading accounts, to the broker’s back-office. Opt-out (no nominee) requires a 30-day video declaration window — trading can continue pending the video, but the nomination status remains “pending opt-out” until the video is captured.

Segment additions. Activating F&O / CD / COM post-onboarding requires the segment-specific risk acknowledgement and (for F&O and COM) income proof. The income proof flow is identical to the onboarding flow — AA-fetched bank statement, ITR upload, or salary slip. On activation, the exchange UCC is updated to reflect the new segment, and the broker’s OMS enables order entry in that segment.

Mobile / email change. Triggers OTP re-verification — the new number / address receives an OTP that the client confirms. Once verified, KRA, exchange, and depository records update. Some brokers also require physical-mail confirmation to the old address as an anti-fraud step (rare but seen at risk-averse brokers).

Name change. Triggered by life events (marriage, court order, gender change). Requires legal proof. On exchange side, BSE specifically uses the “Unfreeze” process — the existing UCC is frozen, the new identity is validated through Protean (PAN-Aadhaar-DOB-Name), and the UCC is re-opened in the new name. NSE has a parallel modification flow. KRA records are updated with the new identity; CKYC reflects the change.

Re-KYC periodicity

SEBI’s risk-based re-KYC framework specifies refresh cycles by client risk category:

• High-risk clients (PEP exposure, high-risk-country residency, large-value transaction patterns) — re-KYC every 2 years.
• Medium-risk clients — every 8 years.
• Low-risk clients — every 10 years.

The refresh process: re-validate identity (PAN + Aadhaar / DigiLocker re-fetch), re-validate address (utility bill / Aadhaar re-fetch), update contact details (OTP re-verify), capture any segment / declaration changes. The artefact is a re-KYC record uploaded to KRA and CKYC. Failure to complete re-KYC by the anniversary triggers an account hold per SEBI guidelines.

Dormancy

A trading account is treated as dormant after no trading activity for a defined window. Industry practice varies: some brokers flag at 12 months, exchange-level dormancy typically applies at 24 months. On dormancy:

• Segment activations may auto-disable (especially F&O / COM where ongoing margin is required).
• Modifications are restricted — client must reactivate before submitting modification requests.
• The account is included in the broker’s monthly dormant-account MIS to the exchange.

Reactivation

Client-initiated, triggered by a written / digital request. If the account has been dormant beyond 12 months, a re-KYC is typically required (current address re-validated, current bank re-confirmed). Segment re-activation goes through the original-onboarding rules (income proof for F&O / COM). UCC unfreeze, BO reactivation, and KRA / CKYC updates follow.

Voluntary closure

Client-initiated closure follows a structured flow:

1. Settle outstanding obligations. Any pending trades, MTF positions, or unsettled payouts must clear.
2. Withdraw funds. Client funds in the broker’s client-funds account are refunded to the client’s registered bank account.
3. Release pledged securities. Margin pledges, MTF pledges, and any other holds on the demat account are released.
4. DP BO closure with CDSL or NSDL — the depository closes the BO account with a formal closure intimation.
5. UCC deactivation at each exchange the client was active on (NSE, BSE, MCX as applicable).
6. KRA closure intimation — the KRA record is updated to “closed” status; CKYC is not closed (CKYC records persist as identity reference).

Transmission (deceased client)

The most operationally sensitive lifecycle event.

Single holder deceased. If a nominee is registered: the nominee submits death certificate, identity proof, and KYC (if not already KYC-registered). The BO account is transferred to the nominee’s name; the nominee can then continue trading or close the account. If no nominee: succession path required — probate of will, succession certificate, or letters of administration. Operationally heavier and slower (months rather than weeks).

Joint account, one holder deceased. Survivor mode — the surviving holder(s) continue with the BO. Death certificate and identity proof submitted; the deceased holder is removed from the BO records.

Joint account, all holders deceased. Same succession path as single-holder-no-nominee.

Transmission flows are governed by depository operational circulars (CDSL and NSDL each publish detailed transmission procedure guides) and SEBI investor protection guidelines. The edge-case compliance domain enumerates the specific obligations.

NRI ↔ Resident conversion

Resident → NRI. Triggered by the client moving abroad and acquiring NRI status. Requires: passport with visa / residency proof, new NRE / NRO bank accounts, PIS (Portfolio Investment Scheme) letter from an AD-Category-I bank. On conversion: existing positions may need to be unwound (some segments are PIS-restricted); UCC is updated to NRI client type; depository BO is re-mapped; segment restrictions apply (e.g., PIS-route NRI is delivery-only, no intraday or F&O).

NRI → Resident. Triggered by the client returning to India. Requires: address and contact-detail re-validation, removal of PIS account linkage, full re-KYC as resident. Segment restrictions lift; the client can resume intraday and F&O / COM trading (subject to standard income-proof requirements).

Note

The SEBI January 2025 nominee revamp. Earlier rules limited nominees to three per account. The January 2025 framework expanded this to ten per account with percentage allocation. The opt-out path (no nominee) was tightened simultaneously — opt-out now requires a video declaration, completed within 30 days. The change has been industry-impactful: brokers had to update their nominee capture workflows, demat platforms had to extend their data models, and KRA / depository records gained new fields. Some brokers offer guided nominee setup flows during onboarding now; opt-out is intentionally a slightly higher-friction path.

Caution

Minor → age-18 conversion has a 30-day deadline. A guardian-operated account for a minor must be converted to an individual account within 30 days of the minor turning 18, or the account is frozen by the broker / depository. The conversion is a re-KYC event — the now-adult must complete their own KYC, providing PAN, identity, address, and bank-account details under their own name. Brokers track upcoming birthdays in their dormancy / lifecycle MIS and trigger reminder notifications at 60 / 30 / 7 days before the 18th birthday to avoid forced freezes.

Practical notes

• [industry practice] Compliance calendars: ops teams routinely build a master compliance calendar from the recurring cycles in Section 5 plus the daily reporting in Section 4. The day-of-the-week and day-of-the-month columns drive the weekly ops standup agenda and the month-end checklist.
• [gotcha] The 4 intraday peak margin snapshots (11:30 / 12:30 / 13:30 / 14:30) are snapshots, not averages — a margin shortfall in even one snapshot triggers a DMF flag and possible penalty. RMS systems must hold the margin position stable across the full snapshot window, which means avoiding settlement-driven swings or fund-transfer-driven balance changes around the snapshot times.
• [industry practice] Direct-payout-to-demat (post November 2024 / January–February 2025) significantly reduced broker pool-account complexity but introduced TM CUSPA / CM CUSPA / TM CSMFA distinctions that required careful chart-of-accounts updates and back-office reconciliation logic changes. Brokers that didn’t get this right in the rollout windows faced settlement-confirmation discrepancies for weeks.
• [cost optimization] Subscribing to exchange and clearing-corp email circular distribution lists costs nothing and saves the periodic site-scrape effort; for broker compliance teams this is the lowest-overhead reliable feed. The compliance officer should be on every relevant list (SEBI, NSE, BSE, MCX, CDSL, NSDL, NSCCL, ICCL, MCXCCL, NPCI, CERSAI, FIU-IND, MeitY where applicable).
• [risk trade-off] Outsourcing back-office to TechExcel / Aastha / Shilpi / ProSarva reduces in-house ops headcount but increases dependence on the vendor’s compliance refresh schedule. Large brokers retain in-house back-office partly for this reason — when a SEBI circular changes a contract-note format with two weeks’ notice, an in-house team can adapt faster than a multi-tenant vendor coordinating the change across all clients.
• [gotcha] Quarterly running-account settlement on calendar quarter-ends (April / July / October / January) is one of the most-penalty-attracting items in SEBI inspections. Explicit client authorization for retention is the only exception, and the authorization itself has format and periodic-renewal requirements. Most brokers run a strict end-of-quarter sweep with a per-client confirmation artefact.
• [industry practice] The same trade file is evidence for multiple compliance domains (margin, settlement, surveillance). Mapping evidence-to-source once and reusing the map across compliance reports is one of the highest-leverage exercises a new compliance officer can do — it reduces both audit prep effort and the risk of citing inconsistent evidence across reports.

Verified through

2026-05-14

---

AI-generated and not legal, financial, or compliance advice. See the project README for full disclaimer.