Charles River IMS
Practitioner-level guidance on translating investment policy constraints into Charles River IMS compliance configuration. The mapping exercise that determines whether your compliance engine works — or just appears to.
The challenge
The Charles River compliance engine is powerful. It can enforce concentration limits, regulatory requirements, client-specific investment constraints, ESG screening rules, and cross-mandate restrictions — all in pre-trade and post-trade contexts. The problem is not the engine. The problem is the mapping exercise that determines what the engine actually enforces.
Most CRD implementations treat compliance rule mapping as a documentation task: pull the investment policy statements, extract the constraints, enter them into the compliance rule editor. This approach produces compliance configuration that is technically complete and operationally wrong. The constraints in an IPS are written by lawyers for legal purposes. The constraints in a CRD compliance rule are executed by software against real positions in real time. The gap between those two representations of the same requirement is where compliance failures live.
The specific problems that surface most often: concentration limits that apply to the wrong security universe; regulatory thresholds that use the wrong basis (market value vs. par value vs. notional) for a given instrument type; restricted list rules that correctly flag individual securities but miss derivatives referencing them; and cross-fund restrictions that enforce correctly on the long book and incorrectly on derivatives overlay strategies. None of these are obvious in UAT. All of them surface in production.
The mapping process
Every compliance constraint source — investment policy statement, ISDA agreement, regulatory filing, client guidelines — is catalogued and cross-referenced. Each constraint is assigned a source document, a section reference, and an effective date. Constraints without traceable source documents are flagged for legal review before configuration begins.
Each constraint is decomposed into its executable components: the security universe it applies to, the measurement basis (market value, par, notional, number of shares), the threshold type (absolute, percentage of portfolio, percentage of issuer), the timing (pre-trade, post-trade, end-of-day), and the action on breach (block, warn, report). Ambiguous constraints are resolved before configuration, not after.
Each decomposed constraint is implemented in CRD's compliance rule editor with explicit configuration documentation. The documentation records what each rule is testing, what it is not testing, and which source document section it implements. Rules are grouped by mandate and labeled for operational review.
Rule testing includes the standard cases and the edge cases that reveal configuration gaps: multi-leg strategies, block trades with partial fills, derivatives referencing restricted securities, cross-currency positions, and end-of-day rebalancing scenarios. We build and document the test case library so your compliance team can re-run it after configuration updates.
PBW's approach
Most compliance consultants deliver a configured system. We deliver a configured system plus a compliance rule map: a structured document that traces every CRD compliance rule back to its source constraint, records the configuration decisions made during implementation, and documents the known limitations of each rule.
That documentation matters because compliance configuration changes. New mandates come in. Regulatory requirements update. Investment strategies evolve. Without a compliance rule map, every configuration change requires reconstructing the reasoning behind the existing rules — which means either leaving rules in place that should be updated or making changes without understanding what they affect.
The compliance rule map is also the foundation for a compliance workflow review: a systematic assessment of which rules are generating the most alerts, which alerts are being overridden, and which override patterns suggest configuration gaps rather than genuine investment decisions. PBW offers compliance workflow reviews as standalone engagements for firms already live on CRD who want to improve their compliance posture without a full reimplementation.
Whether you are starting a new CRD implementation or reviewing an existing compliance configuration, start with a scoping call. We will assess your current rule coverage and identify gaps before they surface in production.
Related resources
Detailed practitioner walkthrough of the compliance rule mapping process for Charles River IMS.
Downloadable worksheet for systematically mapping IPS constraints to CRD compliance rules.
Full-scope CRD implementation: compliance configuration, IBOR, T+1 readiness, and go-live support.
Senior CRD practitioner with current implementation delivery experience.