CME Matching Algorithms: How Globex Decides Who Gets Filled
A matching algorithm is the rule that splits an incoming order's quantity among the resting orders it hits, and CME's client documentation lists nine of them, some keyed to arrival time and some to order size.

A matching algorithm is the rule an exchange applies when an incoming order meets resting orders, to decide which of them trade and how much each one gets. CME's client documentation defines it as the technique for allocating matched quantity, lists nine algorithms by name, and explains that the trading engine assigns one to each product. That assignment is what settles whether your resting limit order is paid for being early or paid for being large.
If you only send market orders, none of this reaches you: you are the incoming order and you take what the book has. It matters to anyone working a limit order who has watched the market trade at their price without filling them.
What is a matching algorithm in futures trading?
A matching algorithm is the method CME Globex uses to allocate matched quantity when one aggressing order meets one or many resting orders. CME's Supported Matching Algorithms page gives order matching three stages: find the prices opposite the aggressor, work out the quantity available at the best of them, then allocate that quantity using the product's algorithm.
The documentation treats each algorithm as a sequence of steps. CME's Matching Algorithms page applies the incoming quantity to the first step, distributes whatever that step's rules distribute, and passes any unmatched remainder to the next step until nothing is left over. The Matching Algorithm Steps page adds that a step can be skipped or appear more than once in an algorithm, and that a step's own rules never change between algorithms: a FIFO step behaves identically whether it is the only step or the last of seven.
Three constraints in the documentation are worth holding on to: no algorithm is applied to an instrument more than once, an algorithm that has started does not stop or reset partway, and implied quantity never matches against implied quantity.
How does FIFO allocate a partial fill?
FIFO matches resting orders in timestamp order and uses nothing else. The earliest order at the price fills first, then the next earliest, until the incoming quantity runs out. CME's Matching Algorithm Steps page works an example that shows how little the rest of the book matters.
Six buy orders sit at one price, in arrival order, for 5, 9, 57, 4, 28 and 300 lots. That is 403 lots at the level. A 50-lot sell order arrives at the same price. The first two orders fill completely, 14 lots between them, and the 36 lots remaining go into the third order, which CME's first FIFO example leaves holding 21 lots. The fourth, fifth and sixth orders get nothing at all.
The 300-lot order is the interesting one. It is about 74% of the quantity at that price and receives zero, because it arrived last. That is why queue position gets talked about: joining a 403-lot queue means waiting for more than 400 lots to trade at the price before one of yours does.
How does pro-rata allocation work, and why can a small order get nothing?
A pro-rata step allocates by share of size. CME's documentation calculates each resting order's displayed working quantity as a fraction of the total working lots at the price, multiplies that by the match quantity, and rounds the result down. Only quantities enter that formula, and CME's own note on one of its pro-rata examples is that the outcome does not turn on timestamps.
Take the same book: 5, 9, 57, 4, 28 and 300 lots, and the same 50-lot aggressor, with the pro-rata minimum for the contract set to 2. CME's worked example gives the 300-lot order 37.22, cut to 37; the 57-lot order 7.07, cut to 7; and the 28-lot order 3.47, cut to 3. The 9-lot order computes 1.11, the 5-lot 0.62, the 4-lot 0.49, and all three receive nothing, because an allocation below the pro-rata minimum is dropped to zero.
That floor has a hard consequence for small orders, and it follows from arithmetic. No order can be allocated more lots than it is working, so the best a one-lot order's calculation can come to is one lot. Where the pro-rata minimum is 2, that is under the floor every time, and the one-lot order takes nothing from the step. It has still been calculated for, and a calculation that comes to nothing is what qualifies an order for the levelling step described below.
FIFO versus pro-rata: what changes for a resting order?
The two steps reward opposite things. Under FIFO a fill depends on when the order joined the queue, and under pro-rata it depends on how large the order is relative to everyone else at the price. The same order on the same book can go from fully filled to untouched.
They also differ in whether they can finish a match. Rounding down leaves a pro-rata step short: 37 plus 7 plus 3 is 47 of the 50 lots in the example above. CME's documentation says pro-rata is never the final step of an algorithm for that reason, and is always followed by FIFO, or by a levelling step and then FIFO. Levelling gives one lot each to the orders that qualified for pro-rata and got nothing, largest first, with timestamp as the tiebreak, and the documentation calls it unique to the Configurable algorithm. In the other pro-rata algorithms, those three leftover lots go to whoever is earliest in the queue.
| FIFO step | Pro-rata step | |
|---|---|---|
| What decides allocation | Timestamp order, earliest first | Share of total working quantity at the price |
| Effect of a large order behind you | None; it waits | It takes the biggest slice |
| Smallest workable order | One lot can fill | Below the pro-rata minimum it is dropped to zero |
| Can it end an algorithm | Yes | No, per CME's documentation |
| Our example book, 50-lot aggressor | 5 and 9 filled, 57 part-filled | 37, 7 and 3 lots to the three largest |
What makes an order lose its place in the queue?
Three modifications cost a FIFO timestamp, per CME's documentation: increasing the order's working quantity, changing its price, and changing the account number on it. A re-queued order goes behind everything that arrived while it was waiting, so adding a lot to a working order restarts the wait for the whole thing.
Duration does not cost you anything by itself. A GTC order keeps its original timestamp across later trading sessions from the moment it was entered, as long as nothing on the priority-losing list happens to it.
Hidden size is treated differently. A display-quantity order shows a slice of itself to the market, and after a match event CME refreshes that slice and puts the refreshed order at the lowest priority at the price level. An iceberg working through a large quantity therefore goes to the back of the queue on every refresh, while an unmodified limit order keeps the timestamp it was given on entry.
A TOP order, covered next, carries its own conditions: immediate loss on a quantity increase, on a reprice that leaves the market no tighter, or on an account number change, and a separate loss on cancellation, on a new same-side TOP order arriving, or on its TOP Max being satisfied. The documentation adds that an order losing TOP through TOP Max being met keeps its timestamp.
What is a TOP order, and how does an order get one?
A TOP order is a single order on one side of the market that is entitled to fills ahead of the allocation step, up to a parameter called TOP Max, for as long as it holds the status. CME's documentation gives an order two ways to become TOP: it enters and tightens the bid-ask spread, or it consumes every resting lot in the book and the remainder it leaves behind becomes a new best bid or offer. Either way its displayed quantity must be at least the product's TOP Min.
Three parameters govern it. TOP Min is the qualifying size, set to 1 in most CME markets that use TOP, though the documentation gives grain options a value of 10. TOP Max caps the lots the TOP step can hand over, counting only fills received after the order came to rest. TOP Percentage, where used, multiplies the aggressing quantity and rounds down, sending the remainder to the next step.
Two conditions catch people out. Cancelling a TOP order does not pass the status down the line, and a later arrival can claim TOP at an established price level only if no TOP order has existed there since that level was established. GTC orders can take TOP at entry but do not carry it over a weekend.
What happens when an incoming order is bigger than the whole price level?
It gets filled FIFO, whatever algorithm the product normally runs. CME's documentation describes two related shortcuts. Before any allocation, Globex asks whether the aggressing quantity covers everything available at the relevant price levels, counting only the displayed quantity of resting orders. If it does, no algorithm is needed and the quantity goes to every order by time priority, since all of them trade anyway.
The Matching Algorithm Steps page states the same thing as an exception: once an aggressor's quantity matches or exceeds what a price level is displaying, FIFO replaces the product's designated algorithm, filling by best price and earliest timestamp. Hidden size stops hiding here. Display-quantity orders are counted at their full remaining quantity, displayed plus hidden, which the page explains as stopping an aggressor from trading past such an order while any of it is unfilled.
The exception can sweep several price levels in one match, with conditions rechecked at each one. It stops where the remaining aggressing quantity is smaller than the resting quantity at a level, handing that level back to the product's own algorithm, or at the aggressor's last price level. Any remainder rests on the book there, and where the product supports TOP and its conditions are met, that remainder is eligible to become the TOP order.
Do market makers and institutions get filled before a retail order?
In CME's futures products, the market-maker step does not apply. CME's Matching Algorithm Steps page is explicit in its LMM rules: "LMMs do not exist in futures products at CME Group." Four of the nine listed algorithms include a Lead Market Maker step, so the algorithm list read without that sentence overstates how much of CME's matching is reserved.
Where the step does run, the documentation describes designated participants with a liquidity agreement taking a percentage of each match ahead of other orders. The percentages are proprietary between CME Group and the party, a product can have several LMMs, and a product's total is stated to be below 50%. A share is rounded down but floored at one lot, and when there is not enough quantity for every eligible LMM to get that lot, the earlier timestamp wins. Everything still resting at the level afterwards, LMM orders included, is matched FIFO.
The Institutional Prioritization algorithm does sort by who you are. It runs two FIFO passes keyed to Globex Firm IDs: the first fills orders from the aggressor's own institution group, the second fills orders with no group association. Time is the only criterion inside each pass.
Which matching algorithm does my contract use?
CME's Supported Matching Algorithms page lists nine of them, and pairs each with the letter it carries in tag 1142, the field its table labels MatchAlgorithm. The step matrix on the companion page covers eight, leaving out V, the two-pass Institutional Prioritization algorithm.
Reading across that matrix, the families are easy to see. F is one FIFO step and nothing else. Pro-Rata (C) runs a pro-rata step then FIFO, and both Allocation (A) and Threshold Pro-Rata (O) put a TOP step in front of that pair. Threshold Pro-Rata with LMM (Q) adds a market-maker step between the TOP and the pro-rata. Two more are FIFO with a market-maker step, one of them with TOP (S) and one without (T). The Configurable algorithm (K) is the composite, at seven steps: a Split step divides the incoming quantity between a FIFO portion and a pro-rata portion by percentages CME sets per product, with levelling and a closing FIFO step afterwards. CME's example splits 49 lots 40/60 into 20 and 29, rounding the FIFO portion up.
What these pages do not carry is a product-by-product list of which algorithm runs where. The Supported Matching Algorithms page sends you elsewhere for that: to CME's GCC Product Resources for the products with a pro-rata component, and to its GCC Product Reference Sheet for the Configurable algorithm's parameters product by product. Two product-specific facts do come through. SOFR futures carry the pro-rata allocation algorithm, with SOFR packs and bundles matching FIFO instead. Grain options are the worked case of a TOP Min above 1, at 10. For anything else, the field carrying the answer is tag 1142.
Does queue position mean anything on a simulated funded account?
Less than it does on a live account. The number on an order line is an estimate, and Sierra Chart's documentation sets out how its own is built: an optional readout on a limit order's line that starts at the bid or ask quantity at the order's price plus the order's own quantity, deducts the size of each trade at that price, and resets lower when the displayed quantity falls. With no depth data, or at a price that is not the best bid or offer, the figure is simply the order's own quantity. The documentation lists the readout as working in simulation mode as well as outside it.
What that estimate counts is quantity sitting at your price, which is what a FIFO step works through in order. A pro-rata step does not work through it in order: it divides the match by each order's share of that quantity, so a countdown towards zero is not a description of what that step will do to your order. It is still a description of the FIFO step behind it, since CME's documentation has a pro-rata step always followed by FIFO, or by levelling and then FIFO.
Then there is simulation itself. Our own side-by-side of the two programs lists fills as simulated on a funded account and "real, and worse" on a live one, and warns that a one or two tick scalp can look profitable in a simulator while losing money against genuine liquidity, for the reason that the simulator filled every order. The matching rules above are what that gap consists of. The wider version of the point is in what changes when an order leaves the platform, and the ladder these queues sit in is the DOM.
FAQ
Is CME FIFO?
FIFO is one of the nine algorithms CME's documentation lists, and it is also the fallback: an aggressor whose quantity reaches or passes the displayed size at a price level is filled FIFO instead of by the product's designated algorithm. Which algorithm a contract runs the rest of the time is assigned per product by the trading engine, and the field that carries the answer is tag 1142, the MatchAlgorithm value CME's table pairs with each algorithm name. For the assignments themselves the Supported Matching Algorithms page points to CME's separate product reference material.
Does changing my order lose my place in the queue?
Three modifications cost a FIFO timestamp, per CME's documentation: increasing the working quantity, changing the price, and changing the account number. A GTC order keeps its original timestamp across later sessions provided none of those happen. A TOP order has a wider list of ways to lose that status, which includes a reprice that leaves the market no tighter, a cancellation, and a new TOP order arriving on the same side.
Can a one-lot order ever get a pro-rata allocation?
No, where the pro-rata minimum is 2. CME's formula tests an order's proportional allocation against that minimum and drops anything below it to zero, and an order cannot be allocated more lots than it is working. In CME's worked example the 9-lot, 5-lot and 4-lot orders all computed allocations under 2 and received nothing in the pro-rata step. Small orders in pro-rata products depend on the levelling or residual FIFO step that follows.
Why do iceberg orders lose priority?
Because of how the refresh works. CME's documentation has a display-quantity order filled on its displayed working quantity, and after the match the displayed slice is refreshed and the order is placed at the lowest priority at that price level. The same documentation treats such an order at its full displayed-plus-hidden quantity during the FIFO exception, so hidden size is counted when an aggressor sweeps the level.
Sources
- CME Group Client Systems Wiki — Supported Matching Algorithms (tag 1142 table; Allocation; FIFO; Pro-Rata; Configurable; Threshold Pro-Rata; LMM; Institutional Prioritization; SOFR pro-rata allocation)
- CME Group Client Systems Wiki — CME Globex Matching Algorithms (Algorithmic Matching Process; Predetermination of Aggressing Quantity)
- CME Group Client Systems Wiki — CME Globex Matching Algorithm Steps (Algorithm Matrix; FIFO; Pro Rata; LMM; Split; Leveling; TOP; FIFO - Exception)
- Sierra Chart — Global Trade Settings (Enable Estimated Position in Queue Tracking)
- Lumen Futures Help Center — Simulated funded vs live
Educational content about futures markets and simulated trading. Not investment advice, and not a solicitation to trade. Trading futures involves substantial risk of loss. Read the full risk disclosure.