Lesson 27.3: Post-Trade Compliance Checks

Where This Lesson Fits

Lesson 27.2 established pre-trade compliance monitoring as the preventive control that evaluates proposed trades before execution, blocking violations before they occur. Pre-trade monitoring is effective for violations directly caused by a proposed trading action, but it has a structural gap: it evaluates proposed trades, not the ongoing portfolio state. Violations that arise without any trading action — a concentration limit breached by differential price appreciation, a credit quality minimum violated by a rating downgrade, an asset class exposure limit exceeded by a corporate action that converts one security class into another — are invisible to a pre-trade system that only activates when a new order is submitted.

Post-trade compliance monitoring closes this gap. It evaluates the portfolio against all applicable guidelines on a periodic basis, regardless of whether any trades occurred, detecting violations arising from the full range of events that can alter a portfolio's characteristics without a deliberate investment decision. Post-trade monitoring is the detective control that complements the preventive control of pre-trade monitoring — together, they provide comprehensive coverage of the compliance risk landscape.

This lesson also addresses the post-execution validation function of post-trade monitoring: confirming that trades executed in the previous session (or the current intraday period, for continuous monitoring environments) did not introduce unexpected violations due to execution price differences, partial fills, or other execution-level discrepancies from the pre-trade simulation. This validation closes the loop on the pre-trade compliance process and ensures that the compliance picture presented by pre-trade simulation matches the reality of executed positions. Lesson 27.4 will extend this framework to the specific analysis of concentration limits — one of the most frequently triggered post-trade compliance findings.

Lesson Objective

By the end of this lesson, students should be able to define post-trade compliance monitoring and explain how it differs from and complements pre-trade compliance monitoring; identify the four primary categories of non-trading events that create post-trade compliance violations; describe the cadence and scope of post-trade compliance evaluation runs and explain how evaluation frequency is calibrated to the compliance risk level of the portfolio; explain the post-execution validation function — how post-trade monitoring confirms that executed trades matched pre-trade compliance assumptions; describe the workflow for investigating and escalating post-trade compliance findings; distinguish between post-trade findings that require immediate remediation and findings that may be managed through a documented cure period; and apply the post-trade compliance framework to evaluate a described portfolio scenario and determine the appropriate compliance response.

Lesson Overview

Post-trade compliance monitoring is the periodic evaluation of a portfolio's actual holdings and characteristics against all applicable guideline restrictions, performed after trades have been executed and positions have been updated in the portfolio accounting system. Unlike pre-trade monitoring, which evaluates a hypothetical future state based on a proposed trade, post-trade monitoring evaluates the actual current state of the portfolio — the positions, weights, credit qualities, durations, and other characteristics that exist after all executed trades, market movements, and other position-affecting events have been reflected.

Post-trade compliance is typically run on a scheduled basis — daily end-of-day runs are the standard in most wealth management environments, with intraday runs in firms managing portfolios with high trading frequency or under particularly stringent mandate constraints. The daily post-trade run produces a compliance report for each monitored portfolio: a list of rules evaluated, a pass or breach status for each rule, and — for breaches — the magnitude of the violation, the date the breach was first identified, and the required escalation timeline. The compliance report is the primary operational artifact of the post-trade monitoring process and the trigger for breach detection, reporting, and remediation workflows.

The scope of post-trade compliance evaluation is broader than pre-trade evaluation because it must consider the full range of events that can alter portfolio characteristics between trading sessions. A portfolio that was fully compliant at yesterday's close may be non-compliant today due to any of the following: differential price appreciation that changes the relative weights of held positions; a credit rating downgrade on a held security; a corporate action such as a merger, spin-off, or conversion that changes the characteristics of a held security; a regulatory change that reclassifies a previously permitted instrument as prohibited; or an update to third-party ESG data that reclassifies a held company under an ESG screen. Post-trade monitoring must be sensitive to all of these triggers, which requires that the compliance evaluation uses the most current available data for all relevant security characteristics — not just price, but also credit rating, industry classification, country of domicile, and any other characteristics referenced in the guideline rules.

Why This Matters in Wealth & Asset Operations

Post-trade compliance monitoring is the primary mechanism by which a wealth management firm maintains ongoing visibility into its guideline adherence across the entire managed account population. Without post-trade monitoring, the firm's compliance program would be blind to any violation that does not arise from a specific trading action — and in practice, a significant proportion of guideline breaches arise from exactly these non-trading events. Rating downgrades to below-investment-grade status (creating "fallen angel" violations), market-driven concentration limit breaches in rapidly-appreciating positions, and corporate actions that alter the characteristics of held securities are all common sources of post-trade violations that pre-trade monitoring cannot detect.

For institutional clients — pension funds, endowments, sovereign wealth funds — post-trade compliance reporting is often a contractual obligation. The investment management agreement may require the manager to provide periodic compliance certifications confirming that the portfolio is managed within its guidelines, and the institutional client's own investment committee or board may receive compliance reports as part of its governance oversight of the manager. Deficiencies in post-trade monitoring that result in undetected breaches create liability both for the firm (failure to meet a contractual obligation) and for the fiduciaries who relied on inaccurate compliance certifications.

From an operations perspective, post-trade compliance monitoring requires coordination across the portfolio accounting, pricing, security master, rating data, and compliance systems — all of these data inputs must be current, accurate, and consistently sourced for the compliance evaluation to produce reliable results. Operations teams responsible for post-trade compliance must understand both the compliance rules being evaluated and the data dependencies that make accurate evaluation possible — and must have controls in place to detect and resolve data quality issues before they contaminate the compliance output.

Core Concept

Post-Trade Compliance Monitoring — The periodic evaluation of a portfolio's actual holdings and characteristics against all applicable guideline restrictions, performed after trades have been executed and positions updated. Post-trade monitoring is the detective control that identifies violations arising from market movements, rating changes, corporate actions, and other non-trading events, as well as validating that executed trades did not introduce violations relative to pre-trade compliance assumptions.

Non-Trading Violation — A guideline breach that arises without any deliberate investment decision or trading action, caused by external events that alter the portfolio's characteristics. The four primary categories are: (1) market drift violations, where differential price movements change position weights; (2) credit event violations, where a rating downgrade causes a held security to fall below the quality minimum; (3) corporate action violations, where a merger, spin-off, conversion, or other corporate event changes the characteristics of a held security; and (4) data reclassification violations, where an update to third-party data (ESG, industry classification, country of domicile) changes the compliance status of a held security without any change to the security itself.

Post-Execution Validation — The post-trade monitoring function that confirms executed trades matched the pre-trade compliance assumptions underlying the pre-trade check. Execution price differences, partial fills, and order modifications between pre-trade check and execution can alter the post-trade portfolio state relative to the pre-trade simulation. Post-execution validation identifies these discrepancies and assesses whether the actual executed trades — as opposed to the proposed trades — remain within applicable guidelines.

Compliance Evaluation Run — A complete evaluation of all applicable guideline rules for a portfolio (or set of portfolios) against the current portfolio state, producing a compliance report that identifies passing and failing rules. Evaluation runs may be scheduled (end-of-day, intraday) or triggered by specific events (rating change notification, corporate action settlement). The evaluation run is the operational mechanism of post-trade monitoring.

Cure Period — A defined time window within which a post-trade compliance violation must be remediated before it is required to be reported to the client or escalated to regulatory reporting. Cure periods allow portfolio managers time to bring the portfolio back into compliance through normal trading processes without requiring immediate forced liquidation. Cure period lengths are typically specified in the investment management agreement or the firm's compliance policy; they vary by restriction type, with hard restriction violations typically having shorter cure periods than soft restriction exceedances.

Compliance Report — The primary output of the post-trade compliance evaluation run: a document listing all rules evaluated for a portfolio, the pass or breach status of each rule, and — for breaches — the magnitude of the violation, the date the breach was first identified, the cure period end date, and the required escalation path. Compliance reports are generated daily (or more frequently) and reviewed by the compliance monitoring team, the portfolio manager, and — for institutional clients — often by the client's own investment committee.

Fallen Angel — A security that was investment-grade at the time of purchase but has been downgraded to below-investment-grade status. Portfolios with minimum credit quality restrictions that hold fallen angels are in violation of those restrictions, even though the purchase was compliant. Fallen angels are a classic source of non-trading violations in fixed income mandates and must be identified promptly through post-trade monitoring that incorporates current rating data.

Non-Trading Violation Categories: Triggers and Detection

Post-trade compliance monitoring must be sensitive to four primary categories of non-trading events that can create guideline violations without any deliberate portfolio management action. Each category requires different data inputs and detection logic.

• Market Drift Violations. Differential price movements across held positions change the relative weights of those positions without any trading action. The classic scenario: a portfolio holds 10 positions at approximately equal weights; one position appreciates significantly while others are flat, increasing its weight past the concentration limit. The violation arises not from a decision to overweight the position, but from the market's movement. Market drift violations are detected by the daily compliance evaluation run using current market prices — the same prices used for portfolio valuation — to calculate current position weights and compare them against concentration and allocation limits. Detection requires that the compliance evaluation use end-of-day prices, not purchase-cost-based position values.
• Credit Event Violations. A credit rating downgrade on a held security can violate both individual security quality minimums (the specific security is now below the required minimum rating) and portfolio-level weighted average quality minimums (the downgrade reduces the portfolio's average credit quality). Credit event violations are triggered by rating agency actions — S&P, Moody's, or Fitch downgrade notifications — and must be detected within the same business day as the rating change to initiate the cure period promptly. Detection requires that the compliance evaluation system receive rating change feeds (typically from the same data vendors that supply security master data) and immediately re-evaluate affected portfolios when a rating change is received. Some firms run intraday compliance checks triggered by rating change events, rather than waiting for the end-of-day run.
• Corporate Action Violations. Corporate events — mergers, acquisitions, spin-offs, security conversions, and changes in company ownership, domicile, or business activity — can alter the characteristics of a held security in ways that affect compliance status. The most common scenarios: a merger converts a held equity position into shares of the acquiring company, which may be in a prohibited industry or domicile; a spin-off creates a new position in a security that may not meet the quality or market cap requirements of the mandate; a company changes its primary business activity, reclassifying it under a different industry code that may be restricted under an ESG screen. Corporate action violations require that the compliance evaluation system be linked to a corporate actions processing workflow that identifies these events and triggers re-evaluation of affected portfolios.
• Data Reclassification Violations. Updates to third-party data — ESG ratings, industry classifications, country of domicile, or other security characteristics — can change the compliance status of a held security without any change to the security itself or any trading action. The most common scenario in ESG-screened portfolios: a data provider updates its revenue attribution data for a company, now attributing more than the threshold percentage of revenue to a prohibited activity, reclassifying the company as a restricted holding. The portfolio has not changed; the data's view of the company has changed. Data reclassification violations are detected when the compliance evaluation system uses updated third-party data and the new classification conflicts with an existing holding. Detection timeliness depends on the frequency of data updates — if ESG data is updated quarterly, reclassification violations may not be detected until the next quarterly data refresh.

Post-Trade Compliance Evaluation: Cadence, Scope, and Output

The cadence and scope of post-trade compliance evaluation runs are calibrated to the compliance risk profile of the portfolio population and the sensitivity of the applicable guidelines to intraday market movements and events.

• End-of-Day Daily Run. The standard post-trade compliance evaluation in most wealth management environments is a daily end-of-day run, executed after the day's prices have been verified and loaded and the portfolio accounting system reflects all trades executed and settled during the trading session. The daily run evaluates all active portfolios against their complete guideline sets using end-of-day market prices. It produces the compliance report that is reviewed by the compliance team each morning as the first step in the next trading day's compliance workflow. Daily end-of-day runs are appropriate for portfolios managed against relatively stable guideline sets where intraday guideline breaches would be detected and remediated at the next day's open.
• Intraday Runs. Portfolios with high trading frequency, tight concentration limits, or intraday monitoring requirements may receive intraday compliance evaluation runs — typically after each trading session or on a defined hourly schedule. Intraday runs allow the compliance team to detect violations created by morning trades before additional trades are executed in the afternoon, and to respond to intraday market events (rating changes, corporate action announcements) more promptly than a daily run would permit. Intraday compliance runs increase the operational workload and system resource requirements of the compliance monitoring function but reduce the duration of undetected violations.
• Event-Triggered Runs. In addition to scheduled runs, post-trade compliance evaluations are triggered by specific events that create an immediate compliance risk: a rating agency downgrade notification affecting a held security; a corporate action announcement that will change the characteristics of a held position; a guideline amendment that changes the applicable rules for a portfolio; or a market event that creates a high probability of market drift violations in concentration-sensitive portfolios. Event-triggered runs focus on the portfolios affected by the triggering event rather than the full portfolio population, allowing rapid response to high-priority compliance risks.
• Post-Settlement Runs. Trade settlement creates the final, legally binding transfer of securities and cash. Some compliance runs are specifically designed to evaluate portfolios after trade settlement — confirming that settled positions match expected positions, that settlement failures have not created unintended position changes, and that the settled portfolio is within all applicable guidelines. Post-settlement runs are particularly important for fixed income portfolios where settlement timing mismatches (a sale settling one day later than expected while a purchase settles on time) can create temporary position imbalances that trigger compliance alerts.

Pre-Trade vs. Post-Trade: Detection Scope and Limitation Comparison

The strengths and limitations of pre-trade and post-trade compliance monitoring are inverse — each covers the territory the other cannot reach, making their combination more powerful than either alone.

Pre-trade monitoring excels at detecting violations that would be directly caused by a proposed trade: a purchase of a prohibited security, a trade that would push a position over its concentration limit, or a transaction that would reduce portfolio quality below the minimum. These are violations that exist only in the proposed future state of the portfolio — if the trade is blocked, the violation never materializes. Pre-trade monitoring cannot detect violations that already exist in the current portfolio (arising from prior events), and it cannot detect violations that will arise from future events unrelated to the current proposed trade.

Post-trade monitoring excels at detecting the full landscape of violations in the current portfolio: violations arising from market movements, rating changes, corporate actions, and data reclassifications that pre-trade monitoring cannot anticipate; violations that existed before the current trading session began; and violations introduced by execution differences between the pre-trade simulation and the actual execution. Post-trade monitoring evaluates the actual state of the world rather than a hypothetical simulated future state, making it a more comprehensive compliance picture but less useful as a prevention mechanism — it detects violations that already exist, requiring remediation rather than prevention.

The operational implication of this distinction is that pre-trade and post-trade monitoring serve different functions in the compliance program: pre-trade prevents new violations from being introduced through trading decisions, while post-trade maintains comprehensive visibility into all existing violations regardless of their origin. A compliance program that relies solely on pre-trade monitoring will have blind spots for non-trading violations; a program that relies solely on post-trade monitoring will detect violations only after they exist, requiring more frequent remediation. Both controls are necessary components of a comprehensive compliance monitoring framework.

Operational Workflow: Daily Post-Trade Compliance Process

The daily post-trade compliance process begins after the end-of-day pricing run and position update and produces the compliance report that anchors the next trading day's compliance workflow.

1. Data Preparation. Before the compliance evaluation run begins, the compliance team confirms that all required data inputs are available and current: verified end-of-day prices (from the pricing run completed per the Unit 26 process); settled and pending trade positions from the portfolio accounting system; current credit ratings from the rating data feed; current industry classifications, country codes, and ESG data from the security master and third-party data providers; and the current guideline rule set from the compliance rule database. Any data input that is missing, stale, or flagged as unreliable must be investigated before the compliance run proceeds — a compliance evaluation using incorrect input data produces compliance results that do not accurately reflect the portfolio's actual compliance status.
2. Compliance Evaluation Run. The compliance system evaluates each monitored portfolio against its complete guideline set using the confirmed data inputs. For each portfolio, the system calculates the relevant metrics — position weights, sector concentrations, asset class allocations, weighted average credit quality, portfolio duration, and other characteristics referenced in the rules — and compares each calculated metric against the applicable restriction. Each rule produces a pass or breach result; breaching rules produce a finding entry in the compliance report with the magnitude of the violation and the current vs. permitted values.
3. Compliance Report Generation. The compliance system generates compliance reports for each monitored portfolio. The report format typically includes: a compliance summary (number of rules evaluated, number passing, number failing); a detailed breach list (each breaching rule, the violation magnitude, and the first detection date); a cure period status for each breach (cure period start and end dates, days remaining); and any escalation flags (breaches exceeding their cure period or breaches requiring immediate escalation based on violation type or magnitude). Reports are distributed to the compliance monitoring team, the portfolio manager, and — for institutional accounts — sometimes to the client's investment committee or compliance contact.
4. Morning Review. The compliance team reviews the previous night's compliance reports as the first activity of each trading day. The review focuses on: new breaches identified in the overnight run (first occurrence); existing breaches approaching their cure period deadline; and changes in the magnitude of previously identified breaches (increasing magnitude may indicate the portfolio is moving further out of compliance; decreasing magnitude indicates progress toward resolution). The morning review produces a compliance action list — a prioritized list of breaches requiring investigation or remediation action during the current trading day.
5. Portfolio Manager Notification. Breaches identified in the overnight run are communicated to the portfolio manager immediately upon morning review. The notification includes the breach details, the applicable cure period, and the required remediation action. For hard restriction breaches, the portfolio manager must acknowledge the breach and provide a remediation plan by a defined deadline — typically by end of the same business day. For soft restriction breaches, the portfolio manager must assess whether the breach is intentional (a managed deviation requiring documentation) or unintentional (requiring corrective action within the cure period).
6. Breach Investigation and Classification. Not every compliance report finding is a genuine breach — some findings arise from data errors (incorrect price, stale rating data, incorrect security classification) that must be investigated before a remediation plan is developed. The compliance team investigates each finding to confirm that the reported violation reflects the actual portfolio state. If a finding is attributable to a data error, the error is corrected and the compliance evaluation re-run; if the finding reflects the actual portfolio state, it is classified as a genuine breach and escalated to the remediation workflow described in Lesson 27.6.
7. Breach Log Update. Confirmed breaches are entered into the breach log with the first detection date, the violation details, the portfolio manager and compliance officer notified, and the cure period start and end dates. The breach log is updated daily as remediation progresses — each day's compliance run updates the magnitude of each logged breach, and the entry is closed when the breach is resolved. The breach log is the primary audit record of post-trade compliance findings and is reviewed in regulatory examinations of the firm's compliance monitoring program.

Real-World Example

A wealth management firm manages a diversified equity portfolio for a pension fund client. The mandate includes a maximum single-issuer concentration of 5% of portfolio value (hard restriction) and a prohibition on holding securities of companies with more than 10% of revenue derived from thermal coal extraction (ESG hard restriction). The portfolio has 40 positions across multiple sectors, each within its concentration limit, and all passing the ESG screen using data that was last updated six months ago at the previous quarterly data refresh.

Overnight, the quarterly ESG data update is loaded into the compliance system. The update contains a reclassification for one of the portfolio's holdings: a diversified industrial company that previously had 7% coal revenue (within the 10% threshold) is now attributed 14% coal revenue following an acquisition that substantially increased its coal operations. The morning compliance run, using the updated ESG data, identifies this position as a data reclassification violation — the company's current revenue profile violates the 10% coal threshold under the portfolio's ESG restriction.

Simultaneously, the overnight run identifies a market drift violation: another position — a large-cap technology company — appreciated 18% over the prior month while the rest of the portfolio was approximately flat. The technology company now represents 5.6% of portfolio value, exceeding the 5% hard limit by 60 basis points, without any trading action by the portfolio manager.

The compliance team's morning review identifies both violations as new findings. The compliance officer notifies the portfolio manager of both breaches before 9:00 AM. The coal revenue violation triggers the firm's ESG breach protocol — the client's IPS specifies that ESG violations must be remediated within 10 business days. The portfolio manager confirms the reclassification is based on accurate data (a brief conversation with the ESG data provider confirms the acquisition increased coal revenue above the threshold) and begins a search for a replacement investment within the same sector. The concentration violation — the 5.6% technology position — requires the portfolio manager to sell a sufficient quantity to bring the position back below 5%, which is accomplished through a trade order submitted in the morning session.

Both violations are logged in the breach log with first detection dates, violation magnitudes, cure period deadlines, and remediation actions. The concentration violation is resolved by end of the same business day following the sale. The ESG violation remains open until the replacement investment is identified and the coal company position is liquidated — accomplished on day 7 of the 10-day cure period. The breach log entries for both violations are closed with resolution dates, and the portfolio's next compliance report shows both rules passing.

Common Mistakes

Mistake 1: Running Post-Trade Compliance Before Prices Are Verified

The post-trade compliance evaluation run must use verified end-of-day prices — prices that have passed the verification process described in Unit 26 — not raw vendor feed prices. A compliance run using unverified prices may produce concentration limit results based on incorrect position values: a position that appears to be 6% of portfolio value at an incorrect price might actually be 4.5% at the correct price, producing a false positive breach, or vice versa. The Unit 26 pricing verification process must complete before the post-trade compliance run begins, and the compliance team must confirm that the prices used in the compliance evaluation match the verified pricing output.

Mistake 2: Failing to Update Rating Data Before the Daily Compliance Run

Credit quality restrictions are among the most frequently triggered post-trade violations, and they depend entirely on the currency of the rating data used in the compliance evaluation. Firms that use rating data updated less frequently than daily — weekly or monthly rating refreshes — will fail to detect credit event violations during the gap period between data updates. Rating agencies issue downgrades at any time; a downgrade issued on a Tuesday and not reflected in the compliance system until the following Monday represents five days of undetected violation, during which the firm's compliance certifications are inaccurate. Daily rating data updates are the minimum standard for portfolios with minimum credit quality restrictions.

Mistake 3: Treating All Post-Trade Findings as Genuine Breaches Without Investigation

Post-trade compliance findings include both genuine violations and false positives arising from data errors — an incorrect price, a stale rating, a misclassified industry code. Operations teams that treat every finding as a genuine breach without investigation may initiate remediation actions (trade execution to correct the "violation") based on incorrect information, creating unnecessary transaction costs and potentially introducing actual violations in the process of remediating phantom ones. Every post-trade finding should be investigated before remediation begins: confirm that the reported violation reflects the actual portfolio state using the correct data before initiating any corrective action.

Mistake 4: Failing to Log Breach First Detection Dates Accurately

The cure period for a compliance breach begins on the first detection date — the date the breach was first identified in the compliance evaluation run. Firms that delay logging a breach in the breach log until the investigation is complete may inadvertently compress the available cure period, because the cure period clock runs from first detection regardless of when the formal log entry is made. Some firms make the opposite error: logging the first detection date as the date the investigation concluded rather than the date the finding first appeared in the compliance report. Both errors produce inaccurate cure period tracking. The first detection date must be recorded as the date the finding first appeared in the compliance report, and the log entry must be created promptly upon completion of the initial investigation.

Mistake 5: Relying on Post-Trade Compliance as the Sole Detection Mechanism for Trading-Driven Violations

Some firms implement post-trade compliance monitoring without pre-trade monitoring, reasoning that the daily end-of-day run will catch any violation introduced by trading. This approach accepts that violations created by the day's trading will exist for up to one trading day before detection — and in an environment where portfolio managers execute dozens of trades per day, "one day" may represent a substantial volume of undiscovered violations. The end-of-day run also does not provide the portfolio manager with real-time feedback during the trading session, meaning violations are discovered after the fact rather than at the point when they could be prevented. Post-trade monitoring is essential but insufficient as the sole compliance control; pre-trade monitoring must be implemented alongside it.

Practical Exercises

Exercise 1: Non-Trading Violation Identification

A fixed income portfolio is fully compliant at Monday's close. By Friday's close, the following events have occurred without any portfolio manager trading action: (a) A corporate bond in the portfolio was downgraded from BBB+ to BB+ by S&P on Wednesday — the portfolio's guidelines require a minimum rating of BBB- for any individual holding. (b) A U.S. equity ETF held in the portfolio completed a merger on Thursday — the ETF converted into shares of the acquiring fund, which invests in international equities. The portfolio's guidelines specify that at least 80% of equity holdings must be in U.S.-domiciled securities. (c) The market appreciation of one technology holding has increased its weight from 4.3% to 5.4% of portfolio value. For each event, identify: the violation category (market drift, credit event, corporate action, or data reclassification); the specific guideline restriction triggered; whether the violation is a hard or soft restriction breach; the earliest date the violation could have been detected by the daily compliance run; and the data inputs required for detection.

Exercise 2: Post-Execution Validation

A portfolio manager proposes to purchase 15,000 shares of a security at a limit price of $45.00 per share. The pre-trade compliance system approves the trade, projecting a post-trade position weight of 4.7% against a 5.0% hard limit (at an assumed execution price of $45.00 and current portfolio value of $14.4 million). The order is executed partially: only 10,000 shares are filled, at an average price of $46.20 per share. Describe the post-execution validation analysis: calculate the actual post-trade position weight using the actual execution price and quantity; compare the actual post-trade state to the pre-trade simulation; determine whether the actual executed trades created any compliance findings not anticipated in the pre-trade check; and describe what compliance actions, if any, are required based on the actual execution.

Exercise 3: Compliance Run Data Readiness Assessment

You are the operations manager responsible for ensuring data readiness before the daily post-trade compliance run. Your checklist for tonight's run shows the following status: (a) Verified end-of-day prices: complete for equities and investment-grade fixed income; three high-yield bond positions still pending verification due to an exception under investigation. (b) Rating data: last updated 3 days ago; today's S&P rating actions have not yet been loaded. (c) ESG data: quarterly update loaded yesterday; current for all positions. (d) Holdings positions: all settled trades reflected; two pending trades (purchased today, settling T+2) not yet reflected. For each data input category, assess whether it is in a state that supports an accurate compliance run. For any that are not, describe the specific compliance risk created by proceeding with the run, identify the temporary control or decision required, and explain what must be resolved before the run can produce reliable results.

Exercise 4: Cure Period Management

The compliance team identifies the following open breaches in a portfolio's breach log on Monday morning: (a) Concentration violation: a single equity issuer is at 5.4% against a 5.0% hard limit; first detected last Thursday; IMS specifies a 5-business-day cure period for hard restrictions. (b) Credit quality violation: a corporate bond downgraded to BB+ (below the BBB- minimum) was first detected last Tuesday; IMA specifies a 10-business-day cure period for credit event violations. (c) Asset allocation violation: the equity weight is at 68% against a 65% soft limit (hard limit 75%); first detected three weeks ago; no documented cure period in the IMA (the IMA refers to "reasonable efforts to remediate promptly"). For each breach, calculate the cure period deadline (assuming standard 5-business-day weeks); assess the urgency of remediation action required this week; and describe what actions must be taken by the compliance team and portfolio manager today if the cure period deadline is within this week. For item (c), describe what criteria you would use to determine the appropriate response when no cure period is specified.

Key Terms

Post-Trade Compliance Monitoring — The periodic evaluation of a portfolio's actual holdings and characteristics against all applicable guideline restrictions, performed after trades are executed and positions updated. Detects violations arising from market movements, rating changes, corporate actions, data reclassifications, and execution differences.

Non-Trading Violation — A guideline breach arising without any deliberate investment decision or trading action, caused by market drift, credit events, corporate actions, or data reclassifications that alter the portfolio's characteristics externally.

Market Drift Violation — A concentration or allocation limit breach caused by differential price movements that change the relative weights of portfolio positions without any trading action.

Credit Event Violation — A quality minimum breach caused by a rating agency downgrade on a held security, converting a previously compliant holding into a violation (a "fallen angel" for investment-grade mandates).

Corporate Action Violation — A guideline breach caused by a merger, spin-off, conversion, or other corporate event that changes the characteristics of a held security in ways that conflict with the portfolio's restrictions.

Data Reclassification Violation — A compliance breach caused by an update to third-party data — ESG ratings, industry classifications, country of domicile — that changes the compliance status of a held security without any change to the security itself.

Post-Execution Validation — The post-trade monitoring function confirming that executed trades matched pre-trade compliance assumptions, identifying discrepancies between the simulated and actual post-trade portfolio states arising from execution price differences, partial fills, or order modifications.

Compliance Evaluation Run — A complete evaluation of all applicable guideline rules for a portfolio or set of portfolios against the current portfolio state, producing the compliance report. May be scheduled (end-of-day, intraday) or event-triggered.

Compliance Report — The primary output of the post-trade compliance evaluation run, listing all rules evaluated, pass or breach status for each, and — for breaches — the magnitude, first detection date, cure period status, and escalation requirements.

Cure Period — The defined time window within which a post-trade violation must be remediated before it is required to be reported to the client or escalated to regulatory reporting. Begins on the first detection date and varies by restriction type and the terms of the investment management agreement.

Fallen Angel — A fixed income security that was investment-grade at purchase but subsequently downgraded to below-investment-grade, creating a quality minimum violation in mandates that prohibit below-investment-grade holdings.

Breach Log — The compliance record documenting all post-trade violations: first detection date, violation details, portfolio manager and compliance officer notifications, cure period timeline, remediation progress, and resolution date. The primary audit record of post-trade compliance findings.

Knowledge Check

Question 1

A portfolio that was fully compliant at Friday's close is found to have a concentration violation at Monday morning's compliance run — a single equity position now represents 5.4% of portfolio value against a 5.0% hard limit. No trades were executed over the weekend. What is the most likely cause of this violation?

• A. A coding error in the compliance system that incorrectly calculates position weights
• B. A market drift violation — the position appreciated relative to the rest of the portfolio over the weekend, increasing its weight above the limit without any portfolio manager action
• C. A settlement failure — a trade intended to reduce the position failed to settle, leaving the position larger than intended
• D. A pre-trade compliance failure — the compliance system failed to block a trade that exceeded the limit

Correct Answer: B — Market drift is the most likely explanation for a concentration violation that appeared between Friday's close and Monday's open without any trading activity. While settlement failures and coding errors are possible, the scenario specifically states no trades were executed and describes a straightforward concentration measurement (position as % of portfolio value), making market drift the most operationally likely explanation. The compliance team should still investigate to confirm the cause — a data error could produce the same symptom — but market drift is the primary hypothesis to evaluate first.

Question 2

Why must the post-trade compliance evaluation run use verified end-of-day prices rather than raw vendor feed prices?

• A. Regulatory requirements mandate the use of verified prices for compliance calculations
• B. Raw vendor feed prices may contain errors that would cause incorrect position weight calculations, producing false positive or false negative compliance findings. Using unverified prices could cause the compliance system to report violations that do not exist (false positives based on overstated prices) or fail to detect genuine violations (false negatives based on understated prices)
• C. Verified prices are more current than raw vendor prices and therefore produce more accurate compliance results
• D. The compliance system is technically incapable of using raw vendor prices because they are in a different data format

Correct Answer: B — The Unit 26 pricing verification process exists precisely because vendor feed prices can contain errors. Using unverified prices in compliance calculations means that any pricing error would propagate into the compliance output, potentially producing false positives (phantom violations that waste investigation resources and may trigger unnecessary remediation trading) or false negatives (real violations masked by understated position values). The pricing verification and post-trade compliance workflows must be sequenced so that verification always precedes compliance evaluation.

Question 3

A corporate bond in a portfolio was rated BBB at purchase. The portfolio's guideline requires a minimum credit quality of BBB-. The bond is subsequently downgraded by one notch to BBB-. Is this a violation?

• A. Yes — any downgrade on a held bond is a violation regardless of the resulting rating
• B. No — BBB- is the minimum permitted rating, and a BBB- rating exactly meets the minimum; this is a compliance pass at the minimum threshold, not a violation
• C. Yes — a downgrade always creates a cure period obligation regardless of the resulting rating
• D. No — the bond was rated BBB at purchase, so the purchase was compliant and the downgrade creates no ongoing obligation

Correct Answer: B — A BBB- rating exactly meets a minimum BBB- requirement; it is at the boundary, not below it. This is a compliance pass, not a violation, though it is close enough to the limit that the compliance team should flag it as a watch-list item — a further one-notch downgrade to BB+ would create a genuine violation. The compliance system should be configured to generate a soft alert or watch-list notification for holdings at the minimum rating threshold, providing early warning of a potential future violation.

Question 4

The cure period for a hard restriction breach begins on the first detection date. A portfolio has a position in a prohibited security that was present in the portfolio for three trading days before the compliance monitoring team noticed it in the breach log. The IMA specifies a 5-business-day cure period for hard restriction violations. How many days remain in the cure period?

• A. 5 days — the cure period begins when the compliance team formally logs the breach
• B. 2 days — the cure period began on the first detection date (the day the violation first appeared in the compliance evaluation run), regardless of when the team formally acknowledged it
• C. 5 days — the cure period begins when the portfolio manager is notified, not when the violation first appeared in the report
• D. 3 days — the cure period begins when the violation was created, not when it was detected

Correct Answer: B — The cure period runs from the first detection date — the date the breach first appeared in the compliance evaluation report — not from when it was noticed in the breach log or when the portfolio manager was notified. If the violation first appeared in Monday's compliance run but the team did not notice it until Thursday, three days of the 5-day cure period have already elapsed, leaving only 2 days. This is why daily review of the compliance report and prompt breach logging are operationally essential — delayed review compresses the remediation time available within the cure period.

Question 5

A post-trade compliance finding shows a credit quality violation: a fixed income holding appears to have a CC rating (well below the BBB- minimum). Before initiating remediation, what is the required first step?

• A. Immediately sell the position — a CC-rated bond is a severe violation requiring immediate action
• B. Investigate the finding to confirm it reflects the actual portfolio state: verify the current rating in the rating data feed, check when the data was last updated, and confirm that the reported rating matches the rating agency's published current rating for the security — the finding may be attributable to stale or incorrect rating data
• C. Notify the client immediately — violations of this magnitude require same-day client communication
• D. Escalate to the investment committee before taking any other action

Correct Answer: B — A compliance finding must be investigated before remediation is initiated. The finding could reflect a genuine violation (the bond was actually downgraded to CC, which would be severe and would require urgent action) or a data error (the rating data feed is stale or incorrectly reflects a different rating). Selling the position based on an incorrect compliance finding would create unnecessary transaction costs and potentially introduce other compliance issues. The investigation — which should be completed promptly given the severity of a CC rating — will either confirm the violation (triggering immediate remediation) or identify the data error (triggering data correction and a re-run of the compliance evaluation).

Lesson Summary

Post-trade compliance monitoring evaluates the portfolio's actual holdings and characteristics against all applicable guidelines after trades are executed and positions updated — functioning as the detective control that pre-trade monitoring cannot provide. It detects the four categories of non-trading violations that arise without deliberate portfolio manager action: market drift violations from differential price movements, credit event violations from rating downgrades, corporate action violations from events that change security characteristics, and data reclassification violations from updates to third-party data.

The daily post-trade compliance evaluation run uses verified end-of-day prices and current security reference data to produce the compliance report that anchors each trading day's compliance workflow. Evaluation frequency is calibrated to portfolio risk: standard environments use daily end-of-day runs; high-sensitivity portfolios use intraday or event-triggered runs. Post-execution validation — comparing actual executed positions against pre-trade simulation assumptions — closes the loop on the pre-trade monitoring process, confirming that execution differences did not introduce violations not anticipated in the pre-trade check.

Every compliance finding must be investigated before remediation begins to distinguish genuine violations from data errors. Confirmed violations are logged in the breach log with the first detection date — which starts the cure period clock — and tracked through resolution. The cure period runs from first detection regardless of when the formal log entry is made, making prompt compliance report review and accurate breach logging essential operational disciplines.

Looking Ahead

Lesson 27.4 examines concentration limits in depth — one of the most frequently triggered post-trade compliance findings and one of the most operationally complex restrictions to monitor continuously. Concentration limits require ongoing measurement of position weights that shift with every market movement, raising questions about how to measure exposure (market value basis vs. commitment basis), how to aggregate related positions (issuer groups, affiliated entities), and how to apply limits across multi-sleeve and multi-currency portfolios. The market drift violation introduced in this lesson is one of the primary mechanisms through which concentration limits are breached, and Lesson 27.4 examines the monitoring infrastructure required to detect and manage concentration limit breaches across a diverse portfolio population.

The breach log introduced in this lesson is extended in Lesson 27.5's treatment of breach detection and reporting, which examines how individual breach records aggregate into the firm-wide compliance reporting picture. The cure period management framework described here connects directly to Lesson 27.6's remediation procedures, which address how to correct violations within cure periods and what happens when cure periods are exceeded.

Study Support

How to Approach This Lesson

This lesson extends the pre-trade framework from Lesson 27.2 into the post-execution world. Focus on understanding the four categories of non-trading violations and why each requires different data inputs for detection. The cure period concept — and the critical importance of the first detection date — is operationally essential and frequently tested in examination scenarios.

Key Patterns to Recognize

• Post-trade monitoring detects violations that pre-trade monitoring cannot: those arising from market movements, rating changes, corporate actions, and data reclassifications.
• Compliance evaluation runs must use verified prices and current reference data — running compliance on incorrect data produces incorrect results.
• Every finding must be investigated before remediation — a data error can produce a false positive that looks identical to a genuine violation.
• The cure period begins on the first detection date, not when the team formally logs the breach or notifies the portfolio manager.
• Post-trade monitoring is a detective control; it detects violations that already exist, rather than preventing them.

Questions to Test Your Understanding

• Can you name the four categories of non-trading violations and give an example of each?
• Can you explain why a post-trade compliance run must be sequenced after the pricing verification run?
• Can you describe the investigation step that must precede any remediation action on a compliance finding?
• Can you explain why the cure period begins on the first detection date and what operational consequences follow from delayed breach logging?
• Can you describe a scenario where post-trade monitoring detects a violation that pre-trade monitoring would have missed?

Common Areas of Confusion

The most common confusion is between the first detection date and the remediation action date. Students sometimes assume the cure period begins when remediation is initiated, when it actually begins on the first detection date regardless of any subsequent actions. This distinction is critical operationally: a team that delays investigating a breach for several days before logging it in the breach log may discover that the cure period has already partially elapsed, significantly constraining the time available for orderly remediation. A secondary confusion involves the treatment of findings as certain violations before investigation — the investigation step is not optional, even when the finding appears severe and the remediation seems urgent.

How This Connects to the Larger System

Post-trade compliance monitoring is the detective layer that complements the preventive layer of pre-trade monitoring. Together they provide comprehensive coverage of the compliance risk landscape. The non-trading violation categories identified in this lesson are a primary source of findings in the concentration limit monitoring (27.4) and breach detection (27.5) processes. The breach log and cure period framework introduced here are the operational foundation of the remediation process (27.6). The integrated compliance control system in Lesson 27.7 shows how all of these monitoring layers — pre-trade, post-trade, concentration, breach detection — interact as a unified system.

Practical Application

Application 1: Rating Change Alert Integration

For portfolios with minimum credit quality restrictions, the timeliness of credit event violation detection depends on the frequency and latency of the rating data feed. Operations teams managing fixed income compliance should establish a formal rating alert integration: a process that receives rating change notifications from rating agencies (typically through a commercial data feed) within the business day, identifies which held portfolios are affected by each change, and triggers an immediate event-driven compliance run for those portfolios. This allows credit event violations to be detected on the day of the downgrade rather than at the next scheduled run, maximizing the available cure period. The rating alert integration should be tested regularly to confirm that it correctly identifies affected portfolios and triggers the event-driven run within the required time window.

Application 2: Corporate Action Compliance Review Procedure

Corporate actions — particularly mergers and acquisitions — often create compliance issues that are not immediately apparent when the action is announced. When a merger is announced, the compliance team should conduct a prospective compliance review: analyzing the terms of the transaction (what will the merged entity look like in terms of business activity, domicile, credit quality, and market characteristics?), identifying which held portfolios have positions in either party to the transaction, and assessing whether the merged entity would meet the guidelines of each affected portfolio. This prospective review allows the firm to plan for post-merger compliance before the event occurs — either taking action to reduce or exit affected positions before the merger closes, or documenting a plan for post-close remediation. Last-minute, forced post-close remediation is more disruptive and more costly than planned pre-close action.

Application 3: Compliance Report Automation and Exception Management

In firms managing hundreds or thousands of portfolios, the daily post-trade compliance report population can be too large for manual review of every portfolio. Operations teams in scale environments should implement exception-based compliance report management: an automated system that identifies the highest-priority compliance findings across the full portfolio population and surfaces them for human review, suppressing routine "no breach" reports while flagging all breach reports and all reports showing approaching-threshold situations. The exception priority ranking should be based on severity (hard restriction breach vs. soft alert), cure period urgency (days remaining vs. days elapsed), and portfolio significance (AUM, client tier, regulatory designation). Exception-based management concentrates human review resources on the highest-priority findings while maintaining a complete audit trail for all routine reports.

Application 4: Post-Trade Compliance in Separately Managed Account Programs

Separately managed account (SMA) programs — in which a sponsor firm places hundreds of individual client accounts with an investment manager — create a post-trade compliance challenge specific to their operating model: each client account may have unique guideline customizations (individual security exclusions, sector tilts, tax lots to preserve) overlaid on the base strategy guidelines. The post-trade compliance system must be configured to evaluate each client account's individual guideline set, not just the base strategy guidelines. An investment manager running a large SMA program may have hundreds of different guideline configurations in the compliance system, each reflecting one client's unique customizations. The operational discipline required to maintain this guideline database — onboarding new customizations, tracking changes, and ensuring every account's guidelines are current — is a substantial investment management operations function in its own right.

Lesson Navigation