Data & Analytics Insights

Adding a multi-asset execution layer without replacing your IMS or OMS

David Tattan

EMEA Lead, Buy-side Trading Solutions, LSEG
  • A specialist execution layer can sit around an existing IMS or OMS, allowing firms to deepen execution capabilities without replacing the core investment platform.
  • Successful integration depends on clear ownership of orders, positions, allocations, reference data and exceptions, not just connectivity between systems.
  • Firms can start with one workflow or asset class, test normal and exception scenarios, then expand rather than moving the entire trading desk at once

For many large institutional buy-side firms, the investment management system (IMS) or order management system (OMS) often remains the core investment platform. It holds positions, runs mandate compliance, generates orders, supports allocations and connects into accounting and operations. Years of configuration and controls sit around it. 

The gap may still be in execution. The portfolio and order management process may work well while the trading desk needs better access to venues and brokers, more automation or a cleaner record of how orders were worked. 

A specialist order and execution management system (OEMS) or multi-asset execution layer can, depending on the existing architecture and integration requirements, be added around that investment platform without replacing it.

Separate the investment layer from the execution layer

Each system needs a defined role. The investment platform typically holds the portfolio, creates the order, applies mandate-level compliance and remains the authoritative source for positions and books and records. The execution layer takes over when the order reaches the trading desk. It gives the trader the tools to work the order across venues and brokers, apply execution rules, manage partial fills and capture the relevant activity in the market. The portfolio manager continues working in the investment environment, while the trader gets a deeper execution workflow around the same order. 

Why the connection matters more now

An OMS or IMS integration needs to carry more than the initial order and the final execution. Order states, fills, allocations and exceptions need to be communicated consistently between systems.

The operating window around a trade is getting shorter. As major European markets move towards T+1 settlement, firms have less time to resolve breaks between execution, allocation and downstream processing. 

What needs to flow between the two

Orders need to leave the IMS/OMS with the identifiers, account information and instructions required by the desk.

Executions should return promptly so the IMS/OMS reflects what has been traded. Order status updates also need to keep both systems aligned on what remains working. 

A portfolio manager may change an instruction while the trader is already working it. Amendments and cancellations need a clear path to the execution layer, particularly when fills may be arriving at the same time. 

Allocation ownership needs to be explicit. Block orders can span several runs or accounts. Firms need a clear owner for the allocation process so that the investment and execution layers do not maintain competing versions. 

Both systems need to identify the same instrument. Using a common reference data source can reduce reconciliation work, although identifiers and mappings still need to be aligned between systems. 

A simple filled order is easy to pass between systems. A partially filled order that has been amended, split across several routes and substituted into another bond puts the integration quality under a much harder test. How those events are handled also affects the quality of the order and execution data available for automation, analytics and AI.

Keep the ownership clear

The execution layer may maintain real-time positions, working quantities, execution controls and the information the trader needs during the day. The IMS or OMS can still remain authoritative for the portfolio, mandate compliance, allocations and the books and records. Unclear ownership creates reconciliation work if a trader sees one working quantity while the portfolio manager sees another. At that point, reconciliation becomes an operating model issue rather than an execution issue. The same problem arises if an allocation is changed in two places or an instrument is mapped differently across systems. Each system should own a defined set of data and actions, with exceptions visible when the two disagree.

The whole trading desk does not need to move at once

Firms may start with the workflow where the existing execution setup is under the most pressure. 

Fixed income is one example. Orders may already originate in the IMS/OMS and fills return electronically, while requests for quotes (RFQs), list trading, broker routes, voice activity and pre-trade liquidity information still sit across several workflows.

Elsewhere the pressure might come from derivatives automation, API-driven equity execution, commodities, FX or expansion into another asset class. Start with one workflow, test order states, fills, reference data and exception handling, then expand.

Starting with one workflow also allows the firm to test implementation within a defined scope. The firm is improving a defined trading workflow rather than beginning a wholesale technology replacement. 

Test exceptions, not only the normal flow 

Straight-through processing (STP) rarely exposes the difficult parts of integration. A better test is what happens when an order is partially filled and then amended, when a connection drops or when two systems disagree on status. 

Buyers should ask how an integration behaves in production: which order states are supported, how amendments and cancellations are acknowledged, how failures are recovered and who owns the problem when an order gets stuck between systems. A live connection alone does not show how the integration behaves when something goes wrong.

When the requirement is broader than execution

Some requirements go beyond execution. If a firm also needs to rethink portfolio management, compliance, accounting, investment books and records, or the way those workflows fit together, the requirement is broader than the trading desk.

Where the issue sits mainly in execution, a multi-asset execution layer can fit around the existing investment platform. If the change also affects portfolio management, compliance, accounting or books and records, the investment management platform itself needs to be considered.

Read more about

Stay updated

Subscribe to an email recap from:

Legal Disclaimer

Republication or redistribution of LSE Group content is prohibited without our prior written consent. 

The content of this publication is for informational purposes only and has no legal effect, does not form part of any contract, does not, and does not seek to constitute advice of any nature and no reliance should be placed upon statements contained herein. Whilst reasonable efforts have been taken to ensure that the contents of this publication are accurate and reliable, LSE Group does not guarantee that this document is free from errors or omissions; therefore, you may not rely upon the content of this document under any circumstances and you should seek your own independent legal, investment, tax and other advice. Neither We nor our affiliates shall be liable for any errors, inaccuracies or delays in the publication or any other content, or for any actions taken by you in reliance thereon.

Copyright © 2026 London Stock Exchange Group. All rights reserved.