Pre-Trade Compliance — Worked Examples
Example 1: Designing a Pre-Trade Compliance Rule Engine for a Multi-Custodian RIA
Scenario: A registered investment adviser manages $3 billion across 4,500 accounts custodied at Schwab, Fidelity, and Pershing. The firm uses model-based portfolio management with 12 model portfolios ranging from conservative income to aggressive growth. The compliance team needs to design a pre-trade compliance rule engine that can handle batch compliance checks for model-driven trades (up to 10,000 orders per model change) as well as real-time checks for individual advisor-initiated trades.
Design Considerations:
The rule engine architecture uses a hybrid evaluation approach. A fast-fail gate evaluates the three most critical rules first in sequence: (1) account status — is the account frozen, suspended, or closed? (2) restricted list — is the security on the firm restricted list? (3) account trading authority — does the firm have discretionary authority or has the client authorized this specific trade? If any of these fail, the order is immediately hard-blocked without evaluating further rules, saving computational resources. Orders that pass the fast-fail gate proceed to parallel evaluation of all remaining rules.
The rule set is organized into seven categories with defined block types:
Category 1 — Account status rules (hard block): Account must be in active status. Account must not be flagged for pending paperwork, regulatory hold, estate settlement, or AML investigation. These rules check account-level flags in the client master database.
Category 2 — Restricted and watch list rules: Firm restricted list match produces a hard block. Watch list match produces a Level 2 soft block (requires compliance officer approval). Personal trading restricted list match produces a hard block for employee accounts. Client-specific restricted security match produces a hard block for that account.
Category 3 — Concentration limits: Single security exceeding 10% of account value produces a Level 1 soft block (advisor can self-authorize with documentation). Single security exceeding 15% produces a Level 2 soft block. Single sector exceeding 30% produces a Level 1 soft block. Single issuer (aggregated across all security types) exceeding 10% produces a Level 2 soft block. These thresholds apply to the post-trade position — the compliance check must calculate what the portfolio will look like after the proposed trade is executed.
Category 4 — Regulatory limits: Wash sale detection (30-day window, cross-account within household) produces a Level 1 soft block with detailed diagnostic information showing the prior loss sale and the wash sale tax consequence. Free-riding detection in cash accounts produces a hard block. Pattern day trader detection (approaching four day trades in five business days) produces a Level 2 soft block.
Category 5 — Client-specific restrictions: IPS asset class range violation produces a Level 1 soft block. ESG screen violation produces a hard block (if the client has a formal ESG mandate) or Level 1 soft block (if the ESG screen is advisory). Tax-loss harvesting wash sale coordination produces a hard block (the tax benefit is the explicit purpose, so overriding defeats the objective).
Category 6 — Position and exposure limits: Firm-level aggregate position exceeding 3% of a security's outstanding shares produces a Level 3 soft block (CCO approval required, due to 13D/13G reporting implications). Account-level notional exposure exceeding 150% of account value produces a Level 2 soft block.
Category 7 — Model and guideline compliance: Trade deviating from the model allocation by more than 5 percentage points produces a Level 1 soft block. Trade in a security not included in any approved model produces a Level 1 soft block (to catch unauthorized ad hoc trades).
For batch processing of model-driven trades, the engine processes orders in three phases. Phase 1: aggregate all orders by security and calculate the total firm-level position post-trade to check firm-level limits once rather than per-order. Phase 2: evaluate account-level rules for each order in parallel across multiple processing threads. Phase 3: compile results and present the compliance summary showing the total order count, the number passing all checks, the number with soft blocks (by level), and the number with hard blocks.
Analysis:
The design prioritizes diagnostic completeness over raw speed for the batch workflow — when processing 10,000 orders from a model change, the compliance team needs to see all violations across all accounts to make informed decisions about overrides and exclusions. For the real-time single-order workflow, the fast-fail gate ensures that obviously non-compliant orders are blocked immediately while the full rule set is evaluated in under 200 milliseconds. The tiered override structure ensures that routine guideline deviations can be handled efficiently by advisors while significant deviations require compliance officer or CCO involvement. All override activity flows into a monthly compliance report that tracks override volume, frequency by rule, and patterns by advisor.
Example 2: Implementing Restricted List Management for a Broker-Dealer with Investment Banking Affiliates
Scenario: A full-service broker-dealer has an investment banking division that engages in M&A advisory, equity underwriting, and debt capital markets. The firm also operates a wealth management division serving 15,000 retail and high-net-worth clients, and a proprietary trading desk. The compliance department must implement a restricted list management system that prevents insider trading violations while minimizing unnecessary trading restrictions.
Design Considerations:
The restricted list system has three distinct lists with different scopes and actions:
The firm restricted list is driven by investment banking engagements. When the investment banking division begins work on a transaction involving a public company, the compliance department adds the issuer to the restricted list. The addition includes: the issuer name, all related ticker symbols, CUSIP numbers for all outstanding securities (common stock, preferred stock, convertible bonds, corporate bonds), the date of addition, the reason (type of engagement), and the expected duration. The restriction applies to all firm accounts: proprietary trading, wealth management client accounts, and employee personal accounts. The restriction produces a hard block on all buy and sell orders.
Issuer propagation is critical. When the firm is advising on an acquisition of Company A by Company B, both issuers and all their subsidiaries must be restricted. The compliance system maintains a corporate hierarchy database sourced from a third-party data provider (such as Bloomberg or Refinitiv) that maps parent-subsidiary relationships. When Company A is added to the restricted list, the system automatically identifies and restricts all subsidiaries and affiliates. The compliance team reviews the propagated list to confirm completeness and add any entities not captured by the automated hierarchy (such as recently formed joint ventures or entities with non-obvious corporate relationships).
The watch list contains securities where the firm has reason for heightened surveillance but has not determined that a full restriction is warranted. This includes: companies where the investment banking division is in preliminary discussions (before a formal engagement letter is signed), companies where a research analyst has recently changed a rating or is preparing to publish a significant research report, and companies where the compliance department has received a tip or complaint about potential insider trading. Watch list matches produce soft blocks that route to the compliance surveillance team for review before the trade is permitted to proceed.
The personal trading restricted list adds further restrictions for firm employees. In addition to the firm restricted list (which already applies to personal accounts), employees in the investment banking division are prohibited from trading in any securities of companies within their coverage sector for the duration of their assignment. Research analysts are prohibited from trading in securities they cover. All access persons must pre-clear personal trades through the compliance system, and the pre-clearance check validates against all three lists.
List maintenance follows a defined workflow. Additions to the firm restricted list require: a request from the investment banking division's deal team or the compliance department, approval by the compliance officer or designated deputy, and immediate distribution to all trading desks and the OMS. Removals require: confirmation that the engagement has concluded or the MNPI has become public (e.g., the transaction was announced or the engagement was terminated), approval by the compliance officer, and a documented record of the removal date and reason. The compliance department conducts a weekly review of the restricted list to confirm that all entries remain valid, with quarterly comprehensive audits that reconcile the restricted list against the active engagement list from investment banking.
Analysis:
The system must balance insider trading prevention with operational efficiency. Over-restriction — keeping securities on the restricted list longer than necessary or restricting overly broad corporate families — prevents legitimate client trading and creates client dissatisfaction. Under-restriction — failing to add securities promptly or missing related entities — creates regulatory risk. The compliance team tracks metrics including: average time from engagement commencement to restricted list addition (target: same business day), average time from engagement termination to list removal (target: within two business days of public announcement), the number of false-hit blocks per month (orders blocked that are subsequently determined to be legitimate), and the number of watch list escalations that result in full restriction. These metrics are reported to the Chief Compliance Officer monthly and inform process improvements.
Example 3: Configuring Concentration and Diversification Limits Across a Household of Accounts
Scenario: A high-net-worth household has five accounts at the firm: a joint taxable account ($2M), the husband's IRA ($800K), the wife's IRA ($600K), a revocable trust ($1.5M), and a custodial account for a minor child ($100K). Total household assets: $5M. The family's patriarch is a retired executive of a large technology company and holds 40% of the joint taxable account ($800K) in concentrated stock of his former employer. The compliance team must configure concentration limits that address both individual account diversification and household-level exposure, while accommodating the legacy concentrated position.
Design Considerations:
The concentration limit configuration operates at two levels: account-level and household-level.
Account-level limits are set per account based on the account's investment policy. The joint taxable account has a special carve-out for the legacy concentrated position: the standard single-security limit of 10% is suspended for the employer stock, but a separate declining limit is established — the position must not exceed 45% of the account currently (providing a 5-percentage-point buffer above the current 40% holding) and must decline to 30% within two years as the family executes a systematic diversification plan. Any purchase of additional employer stock is hard-blocked. All other securities in the joint account are subject to the standard 10% single-security limit and a 30% single-sector limit. The IRAs and trust are subject to standard limits: 10% single security, 30% single sector, and asset class ranges per the IPS (equity 50-70%, fixed income 25-45%, alternatives 0-10%, cash 1-5%). The custodial account, given its smaller size, has a relaxed single-security limit of 15% (because a $100K account holding a minimum position size of $5K would reach 5% concentration with a single position, making a strict 10% limit impractical without limiting the number of holdings to fewer than 20).
Household-level limits aggregate holdings across all five accounts. The household single-security limit is set at 10% of total household assets ($500K). The employer stock position ($800K, or 16% of household assets) currently exceeds this limit. Because this is a legacy position under an active diversification plan, the household limit for this specific security is set at 18% currently with a declining schedule matching the account-level diversification plan. The household single-sector limit is 30%. Given that the employer stock is a technology company and the household already has 16% of assets in this single technology stock, the effective available allocation to other technology securities across all accounts is limited to approximately 14% of household assets (30% sector limit minus 16% in the concentrated position).
The compliance system must perform cross-account aggregation in real-time. When a trade is proposed in any of the five accounts, the system must: (1) look up the household linkage for that account, (2) retrieve current positions in all linked accounts, (3) calculate the post-trade household-level exposure for the relevant security, sector, and asset class, and (4) compare against household-level limits. This cross-account check must also run for wash sale monitoring — if the husband's IRA sells a security at a loss, the system must prevent the joint account, wife's IRA, trust, or custodial account from purchasing the same or substantially identical security within the 30-day wash sale window.
Analysis:
The configuration accommodates the reality that high-net-worth households often have legacy concentrated positions that cannot be immediately eliminated. The declining limit schedule creates a compliance-enforced glide path for diversification — the system will automatically begin hard-blocking if the position exceeds the scheduled limit, providing a structural mechanism to ensure the diversification plan stays on track. The household-level aggregation prevents the family from inadvertently building additional concentration by purchasing the same securities across multiple accounts. The cross-account wash sale monitoring protects the tax benefits of tax-loss harvesting across the household. The compliance team reviews the household-level limits quarterly and adjusts the declining schedule for the concentrated position based on market conditions, tax considerations, and the family's progress toward their diversification target.