The Technology Landscape in Investment Management
What this domain tests
The exam tests whether you can draw the front-to-back system map of an investment manager and explain why each layer exists, how data and orders move between layers, and what breaks when they do not connect. Front office covers research, portfolio construction, order management (OMS) and execution management (EMS). Middle office covers compliance, risk, performance and data management. Back office covers fund accounting, transfer agency, custody and settlement. Enterprise systems - CRM, data warehouse, reporting - cut across all three.
Core rules and concepts
- Order path: PM decision → OMS pre-trade check → FIX message to broker or EMS → execution → allocation → booking to the investment book of record (IBOR) → confirmation → settlement → accounting book of record (ABOR).
- STP: straight-through processing is the design goal. Every manual touchpoint - re-keying, spreadsheets, fax, email confirmations - is both a cost and a control weakness.
- Integration styles: point-to-point, service-oriented, API/microservices and event-driven messaging. Latency, data freshness and failure handling determine which fits.
- Build vs buy: decide on total cost of ownership, differentiation, time to market, vendor concentration and exit cost - not licence price alone.
- Cloud: IaaS/PaaS/SaaS moves spend from capital to operating, but adds data residency, resilience and outsourcing obligations.
Worked example
A manager buys 250,000 shares. The OMS sends a FIX NewOrderSingle (tag 35=D) carrying ClOrdID, symbol, side, quantity and limit price. The broker fills in three parts at an average of 412.6p. The OMS allocates the fills across three funds pro rata, books them trade-date into the IBOR, sends allocations to the custodian and books settlement-date into the ABOR. Reasoning: the architecture matters because the compliance check must run at fund level, and allocation must be rule-based. If allocation is done manually in a spreadsheet, IBOR and ABOR diverge, reconciliation breaks appear, and the audit trail from decision to settlement is broken.
Traps that cost marks
Treating the OMS and the portfolio management system as the same product; assuming the accounting book is the real-time position source; quoting licence fees as total cost of ownership; ignoring the latency and data-quality cost of each integration hop; forgetting that a system map is only as good as its weakest manual interface.