Data Integration for Investment Management: OMS, Custody, Market Data, and Risk Connected

Investment management integration touches systems that span decades of technology generations. FIX protocol for trade execution between the OMS, EMS, brokers, and exchanges. SWIFT messages for custody and corporate actions. Bloomberg BPIPE and Refinitiv real-time data feeds. Prime broker SFTP files for daily P&L and margin. ISO 20022 for newer settlement workflows. Custodian APIs that emerged in the last few years. Market data vendor APIs with vendor-specific quirks. Each interface has its own conventions, error handling, and reconciliation requirements. When something breaks during a trading day, the on-call team has to identify which interface failed and what positions are affected — fast, because trading desk waits don't extend.

Investment integration that works follows industry-specific patterns. FIX protocol implementation with proper sequence number management, recovery, and the conformance testing each broker requires. SWIFT messaging with the message type handling (MT540s for trade confirmations, MT564s for corporate actions, MT535s for holdings) custody integration uses. Real-time market data with conflation policies appropriate to each consumer. Custody and prime broker file integration with the validation that catches missing days or partial files. Reconciliation jobs that prove the OMS, custodian, fund accountant, and risk system all agree on positions every day. Done with this discipline, integration is reliable enough to support trading. Done generically, it breaks during the most consequential moments.