On a busy trading desk, the hardest question is rarely “can we send this order?”
It is usually: what still needs a decision?
One parent order may be partly filled at two venues, working passively at a third, close to its limit and behind its benchmark. A trader needs to see that state in one place before deciding whether to wait, cancel, change an algorithm, release more quantity or stop trading.
That is the job of an execution management system, or EMS: the software traders use to plan, send, monitor and measure live orders. It brings market data, orders, broker and venue connections, execution algorithms, fills and analytics into one workspace.
In short:
- An EMS is where traders work orders in the market: they split them, choose algorithms and routes, and watch every fill as it arrives.
- An order management system (OMS) keeps the official order record, and the EMS handles how the order is executed. Products that do both are called OEMS.
- A good EMS keeps every child order tied to its parent, so filled, working and unreleased quantities always add up to the original order.
- After the order is done, the EMS measures the result against a benchmark such as the arrival price. That review is called transaction cost analysis (TCA).
A firm can connect to ten venues and still have a weak execution workflow if its traders cannot see the real order state, act on it and explain the outcome later. That gap is what an EMS closes.
What an execution management system actually does
An EMS covers the active part of an order’s life: the time between “this order is approved” and “this order is done”. It turns a trading instruction into a controlled execution process.
| EMS function | What the trader needs from it |
|---|---|
| Order staging | Create or receive a parent order with side, quantity, limit, benchmark, urgency and instructions intact |
| Market context | See live prices, liquidity, news, the order book and relevant analytics without leaving the workflow |
| Execution control | Send orders manually, use an algorithm, release quantity in stages or change the plan while the order is working |
| Connectivity | Reach approved brokers, liquidity providers and venues, usually over the FIX protocol, with reliable session and order-state handling |
| Live supervision | Track fills, child orders, cancels, rejects, exposure and remaining quantity in real time |
| Compliance and controls | Apply pre-trade limits, restricted-list checks and price collars, and record who decided what |
| Post-trade analysis | Compare the execution with a benchmark and review how venues, brokers and algorithms performed |
Traders keep the EMS open for the whole session and act through it. That is why speed, clarity and correct order states matter more here than in most back-office software.
Key terms in plain English
| Term | What it means |
|---|---|
| Parent order | The full instruction the trader receives, for example “buy 60,000 shares” |
| Child order | A smaller order sent to one broker or venue to work part of the parent order |
| Execution algorithm | Software that slices an order and decides when and how to send each piece |
| Participation algorithm | An algorithm that trades a set share of market volume, for example 10% |
| VWAP | Volume-weighted average price over a period, used both as an algorithm target and as a benchmark |
| Arrival price | The market price when the order arrived for execution, usually the midpoint between the best bid and ask |
| Slippage | The difference between the execution price and the benchmark price |
| Basis point (bp) | One hundredth of one percent (0.01%), the usual unit for execution costs |
| Implementation shortfall | The full cost of executing an order compared with the price when the decision to trade was made, including delay, market impact, fees and any shares never bought |
| Markout | How the price moved shortly after a fill; it shows whether a route tends to fill just before the price turns against you |
| Transaction cost analysis (TCA) | The review of execution costs against benchmarks after the order is done |
| FIX protocol | The standard message format most brokers and venues use to receive orders and report fills |
| Direct market access (DMA) | Sending orders straight to an exchange’s order book through a broker’s connection and risk checks, without the broker handling them |
| OEMS | A single product that combines order management (OMS) and execution management (EMS) |
How an EMS works: one order from start to finish
Assume a trader receives this instruction at 10:00:
BUY 60,000 ABC
Limit: $85.60
Benchmark: arrival price
Complete by: 11:00
Instruction: avoid taking unnecessary impactAt 10:00, ABC is quoted at $85.18 bid and $85.22 ask, so the arrival price (the midpoint) is $85.20. The order is larger than the size available at the best ask. Sending it all at once would probably push the price up, while leaving it fully passive could mean missing the order if the market rises.
An EMS gives the trader a way to work through that choice.
1. The order enters the execution workspace
The EMS receives the order from an OMS, a portfolio system, an API or a manual ticket. It keeps the parent order’s identity, account, instrument, quantity, limit and instructions.
Before anything leaves the desk, the system applies the relevant controls: account permissions, size limits, restricted securities, available buying power, price checks and venue eligibility.
2. The trader chooses an execution plan
For this order, the trader picks a participation algorithm, keeps the $85.60 limit and allows three routes: Venue A, Venue C and an algorithm at Broker B. Another trader might work the first 10,000 shares by hand and then hand the rest to the algorithm.
The EMS should make the plan visible. A status that only says “algo running” tells the trader very little. The trader needs the target quantity, how much has been released, where it is working, what has filled and what remains under the parent order.
3. The EMS creates child orders
At 10:05, the trader releases the first 32,000 shares as child orders: 14,000 to Venue A, 10,000 to Broker B and 8,000 to Venue C. The other 28,000 stay with the parent order for later.
Child orders can go to a broker’s algorithm, straight to an exchange through direct market access, or to a smart order router that picks the destination for each piece at that moment.
The EMS remains the control surface. It shows every child order and its current state: pending new, working, partially filled, pending cancel, canceled, rejected or filled.
4. The trader watches the order against the market
At 10:18, the order has filled 21,500 shares: 14,000 at Venue A and 7,500 at Venue C. The plan called for about 27,000 by this time. The best ask has risen to $85.52, eight cents below the limit, and Broker B still has 10,000 shares working with no fills in 13 minutes.
The trader could reduce participation, change the limit, accept a slower fill or move quantity to a route with more liquidity. Any of these can be reasonable. What matters is that the EMS shows enough to make the choice deliberately.
Here the trader cancels the child order at Broker B to move its quantity to Venue A. Before the cancel is confirmed, 2,000 shares fill at Broker B. The EMS adds them to the parent order and releases only the 8,000 shares that were actually canceled. Had it re-sent all 10,000 as soon as the cancel went out, the desk could have ended up buying 62,000 shares.
5. The EMS records the result
At 10:54, the final fills arrive. The EMS rolls them up to the parent order: 60,000 shares at an average price of $85.41. Against the $85.20 arrival price, that is 21 cents a share, or about 25 basis points: $12,600 before fees.
The EMS also keeps the execution trail: who changed the order, what was sent, what came back and when. With that trail, the desk can separate the part of the cost that came from the market rising during the order from the part that came from its own decisions.
How one order moves through an EMS
Done: 60,000 at $85.41, 25 bp (about $12,600) above arrival.
- 10:00, arrive: the order to buy 60,000 ABC shares arrives from the OMS with a $85.60 limit; the arrival price is $85.20. Nothing has been sent.
- 10:05, release: 32,000 shares go out as child orders, 14,000 to Venue A, 10,000 to Broker B and 8,000 to Venue C. 28,000 are held back.
- 10:18, exception: 21,500 filled against about 27,000 planned; the best ask is $85.52, eight cents below the limit; Broker B has had no fills for 13 minutes.
- 10:19, decision: the child order at Broker B is canceled. 2,000 shares fill before the cancel is confirmed, so only 8,000 move to Venue A.
- 10:54, review: 60,000 filled at an average of $85.41, 21 cents or about 25 basis points ($12,600) above the arrival price. Venue A 36,000, Broker B 2,000, Venue C 22,000. The fills go back to the OMS for booking.
At every step of the example, the filled, working and unreleased quantities add up to 60,000. If they ever stop adding up, something in the execution record is wrong, and a good EMS makes that visible straight away.
EMS vs OMS: the difference that causes the most confusion
The two can be separate products, tightly integrated, or sold as one system, usually called an OEMS (order and execution management system). Inside an OEMS, the split of responsibilities stays the same.
| OMS | EMS | |
|---|---|---|
| Primary focus | Order ownership and business workflow | Active execution and trader control |
| Typical user | Portfolio manager, operations, compliance, middle office | Trader, execution desk, sales trader |
| Main questions | Who owns the order? Which account? Is it approved? | How should it trade now? Which orders are live? |
| Typical states | New, approved, allocated, booked, completed | Working, partially filled, pending cancel, canceled, rejected |
| Market data | Often limited or contextual | Central to the workflow |
| After the trade | Allocation, confirmation, records, handoff to operations | Execution analysis, benchmark and venue review |
The cleanest setup is the one where an order keeps its identity while moving between applications, however many there are.
A practical way to test an integration is to trace one order from the moment it is created to the moment its fills are booked. If the parent ID, account, restrictions or timestamps disappear between the OMS and the EMS, the integration is not finished.
EMS vs smart order router, matching engine and trading platform
An EMS can call a router, display venue data and send orders through a trading platform. Each of these components still has its own job.
| Component | Its narrow job | The question it answers |
|---|---|---|
| EMS | Shows and controls the execution process for the trader | How should this order be worked right now? |
| OMS | Keeps the official business record and workflow around the parent order | Who owns the order, and is it approved? |
| Smart order router | Selects destinations for a child order based on rules and live market conditions | Which destination should get this child order? |
| Matching engine | Matches compatible orders within a venue’s order book | Which buy and sell orders trade with each other? |
| Trading platform | Provides order entry, market access and account-facing trading functions | How do clients and staff place and follow orders? |
For example, an EMS may show a parent order with 38,500 shares still open. It can ask a smart order router to find a destination for the next child order. Once that child order reaches an exchange, the matching engine decides whether it trades.
An EMS can leave routing, matching and order entry to other components. Its job is to present the decision and the result as one coherent workflow.
What traders should be able to see without asking anyone
An EMS earns its place when it removes status-chasing during a live order. For every parent order, the trader should find these answers quickly:
- What is the original instruction, and what has changed?
- How much is filled, working, canceled and not yet released to a route?
- Which child orders are at each broker or venue?
- Are any cancels, rejects or risk checks still pending?
- How close is the average price to the limit and the benchmark?
- Is the order ahead of or behind its plan?
- Who made the latest change, and why?
- Can the trader pause, amend or cancel safely without creating duplicate exposure?
If a desk needs spreadsheets, chat messages and several browser tabs to answer those questions, it has connections to the market but no single execution workflow.
Who uses an EMS
Buy-side firms (asset managers, pension funds and hedge funds) use an EMS to work orders through several brokers, compare their algorithms and show that client orders were executed well.
Sell-side firms (brokers and banks) use one to work client orders, especially large or sensitive ones, and to manage their own trading.
Proprietary trading firms use execution tools alongside their strategies and risk limits, often with a higher share of automated flow.
Retail forex and CFD brokers rarely run a separate institutional EMS for client orders. Their execution usually runs through the trading platform, a liquidity bridge to liquidity providers and the broker’s risk settings for A-book and B-book flow. The questions an EMS answers still apply: what was requested, what traded and what still needs a decision.
Where an EMS adds the most value
Multi-broker or multi-venue execution
The more execution destinations a desk uses, the harder it becomes to see the full state. An EMS consolidates the parent order while keeping broker, venue and child-order detail.
Larger or more sensitive orders
An order that can move the market needs more judgment than a one-click trade. The trader may balance urgency, market impact, fill probability and information leakage as conditions change.
Multi-asset desks
Equities, options, FX, futures and fixed income have different execution mechanics. A good EMS gives the desk one consistent workflow while keeping product-specific controls where they matter, such as expiry dates for futures, value dates for FX or request-for-quote trading for bonds.
Outsourced or agency execution
When another desk or broker works an order, the firm that sent it still needs a reliable record of the instruction, status, fills and exceptions. “We sent it to the broker” is not an execution trail.
Firms with execution oversight obligations
Under MiFID II, ESMA’s best-execution guidance expects firms to monitor both the execution quality they obtain and the quality of their execution arrangements, and to take remedial action when they find deficiencies. That monitoring depends on clean order and fill data. An EMS helps by turning the execution policy into settings traders actually work with and by recording what happened for later review.
What an EMS should measure after the order is done
The average fill price is useful, but it says little on its own. The review of execution costs is usually called transaction cost analysis (TCA), and it looks at several measures together.
| Measure | What it tells you |
|---|---|
| Fill rate | Did the desk complete the quantity it intended to trade? |
| Time to fill | How quickly did the order complete, including periods spent waiting or paused? |
| Arrival-price performance | How did the final result compare with the market when the order arrived? |
| Implementation shortfall | What did delay, market movement and execution cost add compared with the decision price? |
| Market impact | Did the order move the market while it was being executed? |
| Venue and broker quality | Which routes delivered fills, rejects, price improvement or adverse markouts? |
| Exception rate | How often did the workflow need manual recovery because of rejects, breaks or stale states? |
The benchmark has to fit the order. Arrival price suits an urgent order. VWAP can make sense for an order designed to follow the day’s volume. Measuring every trade against one benchmark produces tidy reports and weak conclusions.
In the example above, the order finished 21 cents, or about 25 basis points, above its arrival price. TCA would then ask how much of that came from the market rising while the order was working and how much from the desk’s own choices, such as the 13 minutes Broker B spent without a fill.
Common EMS failures
It shows fills but hides the parent-order state
A fill blotter shows activity. To stay in control, the trader also needs the remaining quantity, child-order status, limits and execution plan.
It treats a cancel request as a cancel
“Cancel sent” and “cancel confirmed” are different states, and a fill can arrive in between, as it did at Broker B in the example. If the EMS assumes the order is gone too early, a replacement order can create unintended exposure.
It has broker connections but no clean reconciliation
Different systems can label the same order differently. The EMS must map executions, cancel confirmations and rejects back to the correct parent order. Otherwise, the trader and the back office can end the day with different positions.
It makes automation impossible to question
An algorithm can work well most of the time and still be wrong for one order. Traders need clear controls to pause, amend and restrict routes, and to see why the system sent a child order where it did.
The flash crash of 6 May 2010 shows what an unexamined execution setting can cost. According to the joint report of the CFTC and SEC staffs, a mutual fund complex started a program to sell 75,000 E-mini S&P 500 futures contracts, worth about $4.1 billion, through an algorithm set to trade 9% of the previous minute’s volume “without regard to price or time.” On an earlier occasion, the same trader had needed more than five hours to sell a similar amount, using manual orders and algorithms that took price, time and volume into account. On 6 May, with markets already under stress, the sale took about 20 minutes. The report’s first lesson is that the automated execution of a large order can trigger extreme price moves in stressed markets, especially when the algorithm ignores price.
Execution tools earn their keep in exactly these moments: showing price, time and participation side by side, flagging an algorithm that runs much faster than planned, and putting a pause control one click away.
It measures only price
A fast fill at a good price can still be a poor execution if it broke the limit, traded the wrong quantity, created a duplicate position or ignored a client instruction. Execution quality is an outcome with constraints, not one number.
Does every trading firm need an EMS?
No.
A firm with one execution counterparty and simple, small orders may not need a dedicated EMS. A clear trading platform, risk controls, a back office and a reconciliation process can be enough.
The case gets stronger with several execution sources, active manual oversight, large orders, client-specific execution instructions or a need to compare fills across venues and brokers.
A simple test: when an order behaves unexpectedly, can the team reconstruct what happened, and why, in minutes? If the answer involves several systems and a manual search through FIX logs, a better execution workspace is probably justified.
Signs of a well-built EMS
Whether you are choosing a system, using one at work or simply want to know what good looks like, these situations separate a reliable EMS from a fragile one:
| Situation | What a well-built EMS does |
|---|---|
| A large order is split across several routes | Keeps every child order linked to the parent and shows filled, working and unreleased quantities that add up |
| A cancel is sent while the order can still trade | Shows “pending cancel” until it is confirmed and counts any late fill before releasing the quantity elsewhere |
| A broker connection drops | Marks the affected orders as unresolved and checks their real status before anything is re-sent |
| Market data goes stale | Warns the trader and holds actions that depend on current prices |
| A trader changes the plan mid-order | Records who changed what, when and why, and keeps the audit trail intact |
| An algorithm trades much faster or slower than planned | Shows the gap against the plan and lets the trader pause or adjust it |
| Someone asks how an old order was executed | Reconstructs the instruction, decisions, child orders, venue responses, fills and benchmark result |
Coverage matters too: which asset classes, order types and broker or venue protocols the system supports today, whether permissions and routing rules can differ by account, trader and instrument, and which benchmarks and raw timestamps are available for TCA.
The most revealing test is a complete execution trace for one real parent order: the instruction, decisions, child orders, venue responses, changes, fills, exceptions and final booking. It shows far more than a feature checklist.
The practical test
An execution management system should make an active order easier to understand and safer to control.
At any moment, the trader should know what was requested, what is working, what has filled, what changed and what decision remains. If the system can show that clearly, keep the audit trail and measure the outcome against the right benchmark, it is doing the job an EMS exists for.
