From advisory-practice
Advises on RIA order management from entry to settlement: block trading, fair allocation, pre-trade compliance, custodian routing, cash management, trade errors, and OMS evaluation.
npx claudepluginhub joellewis/finance_skills --plugin advisory-practiceThis skill uses the workspace's default tool permissions.
Provides comprehensive guidance on order management systems and trade workflows for registered investment advisers and advisory practices. Covers the full trade lifecycle from investment decision through settlement, including order types and time-in-force instructions, block trading and fair allocation, pre-trade compliance checks, custodian integration and order routing, model-driven trading a...
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Provides comprehensive guidance on order management systems and trade workflows for registered investment advisers and advisory practices. Covers the full trade lifecycle from investment decision through settlement, including order types and time-in-force instructions, block trading and fair allocation, pre-trade compliance checks, custodian integration and order routing, model-driven trading at scale, cash management in the trading workflow, trade error handling and correction, and audit trail and recordkeeping requirements. This skill enables the design, evaluation, and operation of advisory trading infrastructure that is efficient, compliant, and scalable.
10 — Advisory Practice (Front Office)
prospective
The order management system is the operational bridge between investment decisions and trade execution. In an advisory practice, the OMS receives trade instructions generated by the portfolio management system (PMS), validates them against compliance rules, aggregates them into block orders where appropriate, routes them to custodians or brokers for execution, and tracks them through settlement.
Advisory OMS platforms differ materially from institutional OMS platforms. An advisory OMS is optimized for model-driven trading across many small accounts — a single model change may generate hundreds or thousands of individual account-level trades that must be aggregated, compliance-checked, and routed efficiently. An institutional OMS, by contrast, is designed for large orders with complex execution strategies such as algorithmic trading, dark pool access, and multi-venue order splitting.
Core OMS functions in an advisory context include:
The OMS sits between the PMS (which generates trades) and the custodian (which executes and settles them). Data flows bidirectionally: the PMS sends trade proposals to the OMS, and the OMS sends execution results back to the PMS for portfolio accounting updates.
Common advisory OMS platforms include Orion Trading (integrated with Orion Portfolio Solutions), Tamarac Trading (part of the Envestnet ecosystem), Schwab iRebal (now part of Schwab Advisor Services, widely used by RIAs custodying at Schwab), and Fidelity's trading tools (available to advisors on the Fidelity Institutional platform). Many of these platforms combine OMS and rebalancing functionality, blurring the line between PMS and OMS.
Advisors use a range of order types depending on the security, market conditions, and client objectives.
Standard order types:
Time-in-force instructions:
NAV-sensitive orders (mutual funds):
ETF vs. mutual fund order handling: ETFs trade intraday on exchanges like stocks and support all standard order types (market, limit, stop, stop-limit) and time-in-force instructions. Mutual funds trade once per day at NAV and support only purchase, redemption, and exchange orders. This distinction has significant implications for block trading — ETF blocks can be executed with price control during market hours, while mutual fund blocks settle at the same NAV regardless of when the order is placed (provided it is before the cutoff).
Block trading is the practice of aggregating orders for the same security across multiple client accounts into a single block order. This achieves better execution through larger order size (which may access better pricing or reduce per-share transaction costs) and operational efficiency (one order instead of hundreds).
Regulatory framework:
Block trading by investment advisers is governed by SEC no-action letters (most notably the SMC Capital, Inc. no-action letter of 1995) and FINRA guidance. The SEC has permitted block trading by advisers provided that:
Fair allocation methods:
Partial fills: When a block order is only partially filled, the allocation methodology must be applied to the partial fill. Under pro-rata allocation, each account receives its proportional share of the partial fill, rounded to whole shares. Rounding adjustments should follow a documented, consistent procedure (e.g., accounts with the largest fractional shares round up first, or rounding priority rotates). The remaining unfilled portion may be carried forward as a new order or canceled, depending on the advisor's trading policy.
Documentation requirements:
Pre-trade compliance is the automated (and sometimes manual) checking of proposed orders against a set of rules and restrictions before the orders are submitted for execution. This is a critical control point in the trade workflow — catching violations before execution avoids costly corrections, client harm, and regulatory exposure.
Common pre-trade compliance checks:
Hard blocks vs. soft blocks:
Regulatory expectations: Pre-trade compliance is not merely a best practice — it is a regulatory expectation. FINRA Rule 3110 (supervision) requires firms to establish supervisory systems reasonably designed to prevent violations. Automated pre-trade compliance checks are a key component of that supervisory system. SEC examination staff routinely evaluate the scope, effectiveness, and documentation of pre-trade compliance processes. Gaps in pre-trade compliance — such as failure to screen against restricted lists or failure to enforce IPS constraints — are common examination findings.
The end-to-end trade lifecycle in an advisory firm proceeds through a defined sequence of stages, each with specific responsible parties, system interactions, and exception-handling requirements.
Stage 1 — Investment decision: The investment committee, portfolio manager, or individual advisor decides to make a trade. This may be a model portfolio change (replacing one holding with another across all accounts assigned to the model), a rebalance (bringing drifted accounts back to target weights), or an ad hoc trade (a client-specific transaction such as raising cash for a withdrawal).
Stage 2 — Trade generation in PMS: The portfolio management system translates the investment decision into account-level trade proposals. For a model change, the PMS identifies every account assigned to the affected model, calculates the required trade for each account based on current holdings and target weights, and generates a trade list. For a rebalance, the PMS applies drift thresholds and target weights to generate trades that bring each account back into alignment.
Stage 3 — Pre-trade compliance check: The generated trades are screened against the compliance rule engine. Hard blocks are flagged for resolution. Soft blocks are flagged for review. Trades that pass all checks are marked as compliant and eligible for execution.
Stage 4 — Advisor review and approval: Depending on the firm's workflow, an advisor or portfolio manager reviews the trade list before submission. Some firms require explicit approval for all trades; others auto-approve model-driven trades and require manual approval only for exceptions. The review step provides a human checkpoint for catching errors that automated compliance may miss (e.g., a trade that is technically compliant but inappropriate given a client conversation that occurred that morning).
Stage 5 — Order routing to custodian/broker: Approved orders are transmitted to the custodian or executing broker. The OMS applies routing rules based on account-custodian mapping (each account is held at a specific custodian), order type (some custodians support certain order types that others do not), and any firm preferences for execution venues. Orders may be transmitted electronically via FIX protocol, custodian API, or in some cases entered manually into the custodian's trading platform.
Stage 6 — Execution: The custodian or broker executes the order on an exchange, through an internal execution desk, or via a third-party broker. The execution may occur in a single fill or multiple partial fills over time.
Stage 7 — Fill notification: The custodian transmits fill confirmations back to the OMS. The fill data includes the execution price, quantity filled, execution time, and execution venue.
Stage 8 — Allocation (for blocks): For block orders, the OMS allocates the execution results to individual accounts according to the pre-trade allocation methodology. Each account receives its share of the fill at the average execution price.
Stage 9 — Confirmation generation: The OMS generates trade confirmations for each client account reflecting the allocated execution details. Confirmations are delivered to clients per SEC Rule 10b-10 requirements.
Stage 10 — Settlement: Securities and cash are exchanged between counterparties. As of May 28, 2024, the standard settlement cycle for U.S. equities is T+1 (one business day after trade date). Mutual funds generally settle at T+1 as well, though certain fund types may have different settlement cycles. Government securities settle T+1. Options settle T+1 as of May 2024.
Status tracking: The OMS maintains real-time status for each order: pending (awaiting compliance check), approved (compliance passed, awaiting submission), submitted (sent to custodian), partially filled, filled, allocated, confirmed, and settled. Exception statuses include rejected (by custodian or compliance), canceled, and error.
Exception handling: Rejected orders require investigation — common reasons include insufficient buying power, invalid security identifier, or custodian system error. Partial fills require a decision on whether to leave the remaining order open, cancel it, or resubmit. Busted trades (trades canceled by the exchange after execution, typically due to erroneous pricing) require reversal of the allocation and client notification.
Advisory firms route orders to custodians for execution. The integration between the OMS and custodian systems is a critical operational link.
FIX protocol (Financial Information eXchange): FIX is the industry-standard protocol for electronic order routing, execution reporting, and trade allocation messaging. FIX connections provide real-time, automated order submission and fill reporting. Most institutional custodians and executing brokers support FIX connectivity. FIX messages follow a defined tag-value format that includes order type, quantity, price, time-in-force, account identifier, and other trade parameters.
Custodian proprietary APIs: Some custodians offer proprietary APIs in addition to or instead of FIX. These APIs may provide functionality beyond basic order routing, such as account data queries, position reporting, and cash balance inquiries. Schwab, Fidelity, and Pershing each provide proprietary APIs for their advisor platforms.
Manual entry: As a fallback, orders can be entered manually into the custodian's trading platform (web-based or desktop). Manual entry is error-prone, slow, and does not scale, but it may be necessary for custodians that do not support electronic integration, for order types not supported by the electronic interface, or during system outages.
Multi-custodian environments: Many advisory firms custody client assets at multiple custodians (e.g., Schwab for some clients, Fidelity for others, Pershing for others). The OMS must maintain an account-custodian mapping and route each order to the correct custodian. A single block trade may need to be split into custodian-specific sub-blocks, each routed to the appropriate custodian. The allocation engine must then reconcile fills across custodians.
Execution venues: Orders routed to a custodian may be executed through several venues:
Best execution: Advisory firms have a fiduciary obligation to seek best execution for client trades. This does not necessarily mean obtaining the lowest possible price on every trade — it means considering the totality of execution quality factors including price improvement, speed of execution, certainty of execution, and overall cost. In a multi-custodian environment, best execution reviews must evaluate execution quality across all custodians. Firms should conduct periodic best execution reviews (typically quarterly or annually) that compare execution quality metrics across custodians, analyze price improvement statistics, assess the impact of custodian-specific order handling practices, and document findings and any corrective actions taken.
Model-driven trading is the systematic process of generating and executing trades based on changes to model portfolios. This is the dominant trading paradigm for advisory firms that use model-based portfolio management.
Model change workflow:
Scale considerations: A single model change can generate hundreds or thousands of individual account trades. A firm with 2,000 accounts on a single model, implementing a two-security swap, generates up to 4,000 individual trades (one sell and one buy per account). The OMS must handle this volume efficiently, with automated compliance checking, block aggregation, and allocation.
Market impact management: When a model change requires buying or selling a significant quantity of a security across many accounts, the aggregate order may be large enough to move the market. Managing market impact requires consideration of:
Cash management within the trading workflow ensures that client accounts maintain appropriate cash levels to meet obligations and investment targets.
Core cash management functions:
Cash threshold alerts: The OMS should flag accounts where cash levels are outside acceptable ranges:
Cash raise priority: When selling securities to raise cash, the firm must define a priority methodology:
Systematic cash sweep vs. manual cash management: Some custodians automatically sweep excess cash into money market funds or bank deposit programs. The OMS should account for sweep timing and thresholds when calculating investable cash. Manual cash management gives the advisor more control but requires more frequent monitoring.
Pending cash flows: The OMS should account for known future cash events when generating trades. Scheduled withdrawals, expected deposits, pending fee debits, and anticipated dividend payments should be factored into cash projections so that trades are not generated that would leave the account short of cash.
Trade errors are an operational reality in advisory practices. The firm's ability to detect, correct, and document errors is a measure of its operational integrity.
Common trade errors:
Error identification timeline:
Error correction process:
Regulatory requirements:
Error prevention: The OMS can implement controls to reduce error frequency:
Error rate tracking: Firms should track error rates (errors per trade volume) as an operational risk metric. Increasing error rates may indicate system issues, training deficiencies, or staffing problems. Error rate data should be reported to management and compliance periodically.
Every trade in an advisory practice must be supported by a complete and accessible audit trail. The audit trail enables regulatory examination, internal supervision, client dispute resolution, and operational analysis.
Components of a complete trade audit trail:
SEC Rule 17a-3/17a-4 (broker-dealer recordkeeping): For dual-registered firms or advisors operating through a broker-dealer, Rule 17a-3 requires creation of order tickets for every transaction, and Rule 17a-4 requires retention of order records for a minimum of six years (the first two years in an easily accessible place). Order tickets must include the terms of the order, the time of entry, the time of execution, the price, and the identity of the associated person who accepted and executed the order.
SEC Rule 204-2 (investment adviser recordkeeping): For SEC-registered investment advisers, Rule 204-2 requires retention of memoranda of each order given for the purchase or sale of any security. These records must be retained for five years from the end of the fiscal year in which the last entry was made.
Consolidated Audit Trail (CAT): The Consolidated Audit Trail, which replaced FINRA's Order Audit Trail System (OATS), requires broker-dealers to report detailed information about orders and executions to a central repository. CAT tracks the entire lifecycle of an order from receipt through routing, execution, modification, and cancellation. While CAT reporting obligations fall primarily on broker-dealers, advisory firms that route orders through affiliated BDs or that are dual-registered must understand the CAT data flowing from their trading activity.
Retention periods: Order records, execution records, and allocation records must be retained for a minimum of six years for broker-dealers (Rule 17a-4) or five years for investment advisers (Rule 204-2). Best practice is to apply the longer period (six years) across all records regardless of registration type.
Supervisory review documentation: FINRA Rule 3110 requires documented supervisory review of trading activity. The supervisor must review trade blotters, exception reports, and allocation records. The review must be documented with the reviewer's identity, the date of review, the scope of the review, and any findings or actions taken. Supervisory review records are themselves subject to the firm's retention schedule.
Scenario: An RIA managing $1.2 billion across 800 client accounts decides to replace iShares Russell 1000 Value ETF (IWD) with Vanguard Value ETF (VTV) across its Large-Cap Value model portfolio. The 800 accounts are custodied at three custodians: 500 accounts at Schwab, 200 at Fidelity, and 100 at Pershing. The firm discovers that 50 of the 800 accounts have client-specific restrictions that prevent the trade: 30 accounts have tax restrictions (holding IWD shares with very low cost basis that the client has instructed not to sell), 15 accounts have ESG restrictions that exclude VTV due to its holdings in certain energy companies, and 5 accounts are in estate settlement with a trading freeze.
Design Considerations:
The trade workflow proceeds as follows:
The PMS generates 800 sell-IWD orders and 800 buy-VTV orders. For each account, the system calculates the exact share quantity based on the account's current IWD position and the target VTV allocation.
Pre-trade compliance screening flags the 50 restricted accounts: the 30 tax-restricted accounts receive hard blocks on the IWD sell (the client instruction to retain low-basis shares overrides the model change); the 15 ESG-restricted accounts receive hard blocks on the VTV buy (VTV fails the ESG screen); and the 5 estate accounts receive hard blocks on both sides (trading freeze). These 50 accounts are excluded from the trade list, and the portfolio manager is notified to determine alternative treatment — the tax-restricted accounts will retain IWD, the ESG-restricted accounts may receive an alternative ESG-compatible value ETF, and the estate accounts will be addressed after the trading freeze is lifted.
The remaining 750 accounts proceed to block aggregation. The OMS creates three custodian-level sub-blocks for each side of the trade: Schwab block (450 accounts, sell approximately 120,000 shares of IWD and buy approximately 150,000 shares of VTV), Fidelity block (200 accounts, sell approximately 55,000 shares of IWD and buy approximately 68,000 shares of VTV), and Pershing block (100 accounts, sell approximately 28,000 shares of IWD and buy approximately 35,000 shares of VTV).
Tax-lot selection for the IWD sell must be specified at the account level before aggregation. The firm's default method is specific identification with a tax-efficient priority: sell highest-cost-basis lots first, then short-term lots (to minimize the net gain), then long-term lots. For accounts with only low-basis lots and no tax restriction, the lots are sold per the default method. The OMS records the specific lot selection for each account as part of the pre-trade allocation documentation.
Each custodian sub-block is routed via FIX to the respective custodian. The IWD sell blocks are executed first to generate cash for the VTV purchases. Given the aggregate size (approximately 203,000 shares of IWD, representing roughly 2-3% of IWD's average daily volume), the trading desk elects to execute the IWD sells using a VWAP algorithm over two hours to minimize market impact. The VTV buys are executed after the IWD sells are confirmed, also via VWAP.
Analysis:
Post-execution, the OMS allocates fills to individual accounts using pro-rata allocation at the average execution price within each custodian sub-block. Each account at Schwab receives the same average price for its IWD sell and the same average price for its VTV buy. Because the three custodian sub-blocks may execute at slightly different average prices (due to timing differences and market movement), accounts at different custodians may receive slightly different prices. This is acceptable — fair allocation requires consistency within each block, not identical pricing across custodians.
The 50 excluded accounts are documented with the reason for exclusion and the alternative treatment plan. The compliance department reviews the exclusion list to confirm that each restriction was properly identified and applied. The portfolio manager signs off on the alternative treatment for each group of restricted accounts.
The entire process — from model change decision to allocation completion — should be documented in the OMS with timestamps, decision records, compliance check results, routing details, execution data, and allocation records. This audit trail satisfies SEC Rule 204-2 and provides the documentation needed for best execution review and supervisory oversight.
Scenario: On Tuesday afternoon, an operations analyst reviewing the daily trade blotter notices that an advisor entered a sell order for 1,000 shares of Johnson & Johnson (JNJ) in a client account. The account held 1,000 shares of JNJ, and the trade was executed at $158.50 per share (total proceeds: $158,500). However, the advisor intended to sell 1,000 shares of JPMorgan Chase (JPM), which the account also held, to raise cash for a planned withdrawal. The JNJ sale has already settled (the error is discovered on Wednesday, one day after the T+1 settlement). Meanwhile, JNJ has risen to $160.00 and JPM has fallen from $195.00 to $193.00.
Design Considerations:
The error correction process follows these steps:
First, the error is documented immediately: the operations analyst records the nature of the error (wrong security — JNJ sold instead of JPM), the account affected, the trade details, the person who entered the order, and the financial impact.
Second, the corrective trades are determined. To restore the client's account to its intended position:
Third, the corrective trades are executed through the firm's error account. The JNJ repurchase at $160.00 and the JPM sale at $193.00 flow through the error account. The net cost to the firm is: the $1,500 loss on JNJ (bought back higher than sold) plus the $2,000 shortfall on JPM (sold at a lower price than was available when the original trade should have occurred), totaling approximately $3,500. The client's account is made whole — it ends up holding the same securities it would have held if the correct trade had been executed, and the cash raised is $193,000 (the JPM proceeds) rather than the $195,000 that would have been available on Tuesday, but the firm absorbs this difference.
Fourth, the client is notified. The advisor calls the client to explain the error, the correction, and that the client has been made whole. A written confirmation follows.
Analysis:
The firm should investigate how the error occurred and what controls could prevent it. Potential OMS enhancements include: (1) security validation that requires the advisor to confirm the security name in addition to the ticker symbol before submission — displaying "Johnson & Johnson (JNJ)" prominently on the order confirmation screen would help catch ticker confusion; (2) a warning when an order would liquidate an entire position, prompting the advisor to confirm intent; (3) a reconciliation check that compares the security being sold against the stated purpose of the trade (if the advisor flagged the trade as "cash raise for withdrawal," the system could verify that the selected security aligns with the cash-raise priority methodology).
The error, correction, and associated costs are logged in the firm's error account records and reported to compliance. If the firm is a dual registrant with a broker-dealer, the error may need to be evaluated under FINRA Rule 4530 for reportability. The error account activity is subject to supervisory review and regulatory examination.
Over time, the firm should analyze error patterns. If wrong-security errors are recurring, it may indicate systemic issues with the OMS interface, training gaps, or workflow problems that need to be addressed.
Scenario: A mid-size RIA custodies client assets at three custodians — Schwab (60% of AUM), Fidelity (30% of AUM), and Pershing (10% of AUM). The firm's compliance committee has tasked the trading desk with conducting the annual best execution review to evaluate execution quality across all three custodians and document findings for the firm's fiduciary records.
Design Considerations:
The best execution review should follow a structured methodology:
Data collection: The OMS maintains execution records for all trades at each custodian. The trading desk extracts 12 months of trade data including: security, order type, order size, execution price, National Best Bid and Offer (NBBO) at time of execution, execution venue, fill time (time from order submission to execution), price improvement or disimprovement versus NBBO, and effective spread (the difference between the execution price and the midpoint of the NBBO at the time of order entry). This data is segmented by custodian, security type (equity, ETF, mutual fund, fixed income), order size, and market conditions.
Evaluation criteria: The review evaluates each custodian across multiple dimensions:
Comparative analysis: The trading desk compares execution quality metrics across the three custodians using standardized measures. For example, if Schwab provides average price improvement of 1.2 cents per share on equity orders while Fidelity provides 0.8 cents and Pershing provides 1.0 cent, this difference is documented. However, best execution is not determined by a single metric — the review must consider the totality of factors including execution speed, reliability, order handling capabilities, and the overall cost of the custodial relationship.
Analysis:
The review findings are documented in a written report that includes: the methodology used, the data period and sample size, the metrics evaluated, the results for each custodian, a comparative analysis, and conclusions. If the review identifies material execution quality concerns at any custodian — for example, consistently poor price improvement or high rejection rates — the report should include recommended actions such as engaging the custodian to discuss execution practices, modifying order routing preferences, or in extreme cases considering a custodian change for affected accounts.
The report is presented to the compliance committee and retained as part of the firm's books and records. SEC and FINRA examiners routinely request best execution review documentation. The review should reference the firm's best execution policy, which establishes the frequency of reviews (at least annually), the metrics to be evaluated, the responsible parties, and the escalation process for identified deficiencies.
The OMS facilitates this process by maintaining comprehensive execution data in a structured, queryable format. Firms without adequate OMS reporting capabilities may need to supplement with data from custodian execution quality reports (Rule 605 reports, formerly Rule 11Ac1-5) and Transaction Cost Analysis (TCA) services provided by third-party vendors.