We are pleased to announce the release of Transact Comply version 1.11, which introduces important regulatory, functional, and performance enhancements to further strengthen the platform’s compliance capabilities. This release includes regulatory reporting support for the Nepal jurisdiction, aligned with goAML Nepal requirements, enabling seamless and compliant submission of regulatory reports. It also introduces Capital Market–specific rules, expanding the platform’s coverage and applicability for capital market participants.
In addition, version 1.11 delivers a significant performance milestone, with the platform now capable of processing up to 10 million transactions within 24 hours, ensuring scalability and reliability for high-volume environments.
Transact Comply now supports regulatory reporting for the Nepal jurisdiction, enabling registered entities to generate goAML-compliant XML reports such as STRs and TTRs directly from the platform. The feature includes the ability to pre-fill customer and transaction details within regulatory forms, significantly reducing manual effort, improving accuracy, and accelerating the overall reporting process.
This release introduces a new MIS and Capital Markets–specific reporting module, providing enhanced visibility and operational insights across the platform. The module includes a comprehensive set of MIS reports such as Case Level Report, Rule Level Report, etc., enabling users to effectively monitor system performance and compliance activity. In addition, the release adds Capital Markets–specific reports, including Exchange/DP Alerts Summary, Quarterly Reports, and other regulatory-focused outputs, supporting more efficient analysis and reporting for Capital Markets surveillance requirements.
We have a added several new functions like GroupBy Client ID, MultiplyIf, Concat, etc. within the Rules Engine to support advanced Capital Markets compliance use cases. With these additions, users can now configure more accurate and targeted surveillance rules, improve the detection of suspicious trading activity and strengthen overall market integrity monitoring.
We have made significant enhancements to our transaction processing engine, enabling the system to efficiently handle up to 10 million transactions within a 24-hour window. This improvement delivers higher throughput, increased scalability, and improved system performance—ensuring faster processing times, better stability under heavy loads, and an overall more seamless experience for high-volume users.
Introduced the capability to store and manage additional file types required for Capital Markets monitoring. The system now supports ingestion of IP Address & Device ID Files and Price Band Files, enabling users to build rules that rely on these enriched datasets.
As part of this release, we have deployed a comprehensive set of Capital Markets–specific monitoring rules to strengthen surveillance and regulatory compliance coverage. A total of 100 new rules have been introduced, addressing a wide range of Capital Markets scenarios and risk patterns.
The detailed list of deployed rules, along with their respective descriptions, is provided below for reference.
Scenario 1: New / Dormant Account Activity & Early-Stage Risk
1. Transactions greater than INR [X] in newly opened account within [Y] days/months of account opening
2. Transactions greater than INR [X] in dormant account within [Y] days of reactivation
3. Large Initial Outflow from New Account
4. Large Initial Inflow with Wealth Check
5. First-Time Transaction After Long Gap
6. New Account Trading Surge
7. Dormant-to-Spike with Wealth Mismatch
8. Multiple New Account Coordination
9. Account Lifecycle Risk
Scenario 2: High Transaction Value / Volume Threshold Breaches
1. Excessive Trading Volume
2. Significantly Increase in Client Activity
3. Aggregate Trade Count
4. Aggregate Buy Value
5. Aggregate Sell Value
6. Excessive Buy Value
7. Excessive Selling Value
8. Cash Segment Volume Alert
9. Single Client Volume Threshold
10. Consistent High-Volume Pattern
11. Trade Count / Frequency-Based Monitoring
Scenario 3: Net Worth / Income / Capacity Mismatch (KYC-Based)
1. Delivery Turnover vs Declared Capacity
2. Trading–Net Worth Mismatch
3. Trading–Income Discrepancy
4. Net Income Trading Imbalance
5. Net Worth Trading Imbalance
6. Net Income & Net Worth Trading Imbalance
7. Net Buying Exceeds Declared Income
8. Net Selling Beyond Declared Capacity
9. Net Transactions Exceeding Income Multiple
10. High trade value against net worth
11. High pay-in/payout as compared to income/net worth
Scenario 4: Suspicious High Trading by Low Net Worth / Income Clients
1. Suspicious Low-Networth High-Trade Alert
2. Suspicious Low-Income High-Trade Alert
3. Suspicious Low-Networth High-Trade Alert (Networth)
4. Suspicious Low-Income High-Trade Alert (Income)
5. Suspicious Low-Income & Low Net Worth High-Trade Alert
Scenario 5: Pay-In / Pay-Out & Fund Flow Anomalies
1. Client delivery pay-in/payout greater than INR [X] in a month/year
2. Recurrent High Pay-Outs with Capacity Check
3. Recurrent High Pay-Ins with Inconsistency
4. Pay-in Surge Alert
5. Excessive Pay-in Ratio (Networth + Income)
6. Excessive Pay-in Ratio (Networth)
7. Excessive Pay-in Ratio (Income)
8. Monthly Net Outflow Spike with Wealth Mismatch
9. Monthly Net Inflow Spike with Wealth Mismatch
10. Single-Day Net Outflow Spike with Net-Worth Check
11. Single-Day Net Inflow Spike with Wealth Check
Scenario 6: Market Manipulation & Market Abuse Indicators
1. Market Abuse Indicator
2. Volume Concentration Alert
3. Single-Day Dominance in One Scrip
4. Bulk Off-Market Accumulation vs Issued Capital
5. Single-Day Turnover Relative to Issued Capital
6. 30-Day Scrip Concentration Over Threshold
7. Consistent Profit/Loss Deviation
8. Extreme Outcome Alert
9. Turnover / Contribution-Based Risk
Scenario 7: Wash Trades, Circular Trading & Artificial Volume Creation
1. Same-Day Matched Equity Trades (Wash)
2. Same-Day Matched F&O Trades
3. Repeated Buy-Sell Cycles Creating Volume (Cash)
4. Sequential Cancellation Alert
5. High Frequency Micro-Quantity Orders
6. Minimum Lot Frequency Rule
7. Transaction Structuring / Aggregation Behavior
Scenario 8: F&O / Derivatives-Specific Trading Behavior
1. Frequent Small-Value F&O Orders by Client
2. Concentrated Single-Day F&O Activity by Client Type
3. Disproportionate F&O Volume Share
4. Intraday F&O Turnover vs KYC Multiplier
5. Excessive Trading Leverage
6. Options Trading Suitability Rule
7. Extreme Speculative Profit/Loss Thresholds
Scenario 9: Intraday Trading & Turnover Abuse
1. Intraday Cash Turnover vs KYC Multiplier
2. Cash Segment Volume Alert
Scenario 10: Scrip-Specific & Regulatory Watchlist Activity
1. Activity in GSM-Listed Scrips (Low Threshold)
2. Activity in ASM-Listed Scrips (Low Threshold)
3. High Value Odd Lot Transfer
4. Equity-Specific Trade Concentration
Scenario 11: Device, IP & Digital Identity Abuse
1. Frequent Device Switching
2. Frequent Device Switching Alert
3. Frequent IP Overlap Alert
4. Repeated IP Overlap Alert
5. Internal IP Usage Consistency
6. IP Consistency Breach
7. IP/Device Overlap Multi-Client Alert
8. Shared Device Usage Alert
9. Shared Device Multiple Clients
10. Shared IP Multiple Clients
11. Multiple Clients Same IP
12. Shared IP/Device Multiple Clients
13. Multiple Onboardings from Single IP
14. AP Session Variability Alert
Scenario 12: Coordinated / Group Trading Behavior
1. Coordinated Group F&O Activity
2. Coordinated Group Equity Turnover
3. Group of New Clients Concentrated in One Equity
4. Rapid Concentration by New Client in Equity
5. High contribution by customers
Scenario 13: Mule Account & Identity Misuse
1. Mule Account Activity Alert – Net Worth
2. Mule Account Activity Alert – Income
Scenario 14: KYC Consistency & Profile Mismatch
1. Transaction Activity Not Matching KYC Declared Occupation
2. Mobile / Email Linking Across Multiple Accounts
3. Client Linking / Identity Correlation
We’ve resolved several known issues to enhance overall application performance, delivering a more stable, responsive, and reliable user experience.
Copyright © 2026 ZIGRAM Data Technologies Pvt Ltd