Asset Atrium Compliance Framework
Internal Use Only
Blocking behavior
Pre-trade compliance runs synchronously in the ATIM order submission path. A hard breach blocks the order from reaching the FIX Gateway. Soft breaches require authorized override before routing. All decisions are logged to the compliance audit trail.

How pre-trade compliance works

When a portfolio manager submits an order in Asset Atrium Investment Manager (ATIM), the compliance engine evaluates the proposed trade against all active rules assigned to the fund. The engine simulates the post-trade portfolio state ("what-if") and checks every applicable limit.

  1. Order submitted in ATIM (single order or block order with allocations).
  2. What-if calculation: engine computes projected positions, exposures, and weights assuming the order executes at limit price or last price.
  3. Rule evaluation: every active compliance rule for the fund is checked against the projected state.
  4. Result: PASS (no breaches), SOFT BREACH (override allowed), or HARD BREACH (order blocked).
  5. Audit log: all rule evaluations and results recorded with timestamps and user IDs.

Rule categories

CategoryExample RulesBreach Type
Asset AllocationMax 60% equities, min 20% fixed income, max 10% alternativesSoft
Sector ExposureMax 25% in any single GICS sectorSoft
Country ExposureMax 30% in any single country; max 10% in emerging marketsSoft
Issuer ConcentrationMax 5% in any single issuer (UCITS 5/10/40)Hard
Instrument EligibilityNo unrated bonds; no equities below $500M market capHard
Credit QualityMin average rating BBB-; max 10% below investment gradeSoft
LiquidityMin 80% of portfolio in instruments tradeable within 5 daysSoft
Currency ExposureMax 20% unhedged non-base currency exposureSoft
Counterparty LimitsMax 10% OTC derivative exposure to any single counterpartyHard
Regulatory LimitsUCITS Art. 52: max 5% in single issuer (10% with conditions)Hard

Hard vs. soft breaches

Breach TypeBehaviorOverrideAudit
HardOrder blocked — cannot proceed to FIX GatewayNot allowed — PM must modify or cancel the orderLogged as HARD_BREACH with rule details
SoftWarning displayed — PM can request overrideRequires compliance officer approval (4-eye)Logged as SOFT_BREACH + override decision

Override workflow

When a soft breach is detected, the portfolio manager can request an override through the ATIM compliance panel:

  1. PM provides written justification for the override request.
  2. Request is routed to the designated compliance officer for the fund.
  3. Compliance officer reviews the breach details, projected exposure, and justification.
  4. Compliance officer approves or rejects the override with documented rationale.
  5. If approved, the order proceeds to execution with the override flag attached.
  6. Override is recorded in the compliance audit trail with full approval chain.
Override escalation
If a single fund accumulates more than 3 active soft breach overrides in a rolling 30-day period, an automatic escalation is triggered to the Chief Compliance Officer (CCO) for review. This threshold is configurable per fund risk tier.

Block order compliance

For block orders that allocate across multiple funds, Asset Atrium runs compliance checks against each recipient fund individually. A breach in one fund does not block allocation to other compliant funds — the non-compliant allocation is held pending override while compliant allocations proceed.

Performance considerations

Testing compliance rules
New or modified compliance rules should be tested in UAT using the ATIM compliance simulation mode, which evaluates rules without blocking orders. Simulation results are logged separately for review before production activation.