Form 26AS evidence requires successor-entity accounting verification after business transfer, while invoice-supported related-party advertising expend...
Money-laundering judgment timing requires awaiting the scheduled-offence decision despite continuation of the underlying trial where outcomes directly...
Accredited investor eligibility expands through securities-market exposure, while alternative investment fund disputes require prescribed resolution a...
Page of 4916
Press 'Enter' after typing page number.
41 to 60 of 98302 Results
❮
❯
❯❯
0 / 200
Expand Note
Add to Folder
No Folders have been created
+
Are you sure you want to delete "My most important" ?
The instrument revises the technical-glitch framework: it...
Broker trading-system "technical glitch" redefinition and narrowed incident-reporting regime for large IBT/STWT brokers requiring 2-hr notice and 14-working-day RCA
Contents
Summary
Note
Bookmark
Share
✓ Copied successfully !
Print
Print Options
For full text, please login
Login to TaxTMI
Verification Pending
The Email Id has not been verified. Click on the link we have sent on
The instrument revises the technical-glitch framework: it redefines "technical glitch" to mean broker-system malfunctions impacting trading/risk functions for ≥5 contiguous minutes and excludes specified external or non-trading/back-office issues, thereby narrowing reportable events. It limits applicability to brokers operating IBT/STWT platforms with >10,000 active clients, thereby excluding smaller brokers from the regime. It prescribes streamlined reporting - notify exchange and clients within 2 hours, file a preliminary incident report by T+1 (next trading day if holiday) and an RCA within 14 working days via a Common Reporting Platform - thereby standardizing timelines and submission. It rationalizes capacity-planning, software-testing, BCP/DRS and financial disincentives by broker size, mandates exchanges to issue detailed guidelines and publish incidents, and supersedes the earlier circular; effective January 9, 2026.
The instrument revises the technical-glitch framework: it redefines "technical glitch" to mean broker-system malfunctions impacting trading/risk functions for ≥5 contiguous minutes and excludes specified external or non-trading/back-office issues, thereby narrowing reportable events. It limits applicability to brokers operating IBT/STWT platforms with >10,000 active clients, thereby excluding smaller brokers from the regime. It prescribes streamlined reporting - notify exchange and clients within 2 hours, file a preliminary incident report by T+1 (next trading day if holiday) and an RCA within 14 working days via a Common Reporting Platform - thereby standardizing timelines and submission. It rationalizes capacity-planning, software-testing, BCP/DRS and financial disincentives by broker size, mandates exchanges to issue detailed guidelines and publish incidents, and supersedes the earlier circular; effective January 9, 2026.
Note: It is a system-generated summary and is for quick reference only.