Price bands and trading halts
Your limit order was rejected for an invalid price and the price was a legal increment, above zero, and within your balance. Or trading simply stopped, your resting orders were still listed, and nothing was matching.
Both are venue rules operating as designed. A price band constrains which prices may be submitted; a halt suspends matching altogether. They are related mechanisms with the same purpose, and the part worth understanding is what each does to orders you already have.
The problem both mechanisms address
A matching engine will do exactly what its rule says with whatever arrives. On a thin book a single large market order can consume every resting level and print a price very far from anything that was trading a moment earlier. Nothing about that is a malfunction — it is the book walking — but the resulting print is then a fact in the record, and other mechanisms reference prints.
Prints feed stop triggers, mark price calculations, index composition and liquidations. A single extreme fill can therefore propagate into consequences well beyond the participants who traded it. Price bands and halts are the two structural responses: constrain what can print, or stop printing.
Static and dynamic bands
A price band is a range around a reference price, outside which orders are refused. Two common forms, and venues frequently run both at once.
A static band is anchored to a slow-moving reference — a session open, a daily reference price, or an index level — and permits some distance either side of it. It bounds the total move within a period regardless of path.
A dynamic band is anchored to something recent, typically the last trade or a short-window average, and permits a smaller distance. It bounds the size of a single step, so a market can travel a long way by many small moves but not in one jump.
Bands are also applied to different things. Some constrain the submission price of any order, so an order priced outside the band never reaches the book. Some constrain only the execution price, letting an order rest but preventing a match beyond the boundary. The difference is visible in the rejection: one refuses the order, the other accepts it and then does not fill it.
What a band does to an order you already have
This is the part with consequences, and it has three distinct cases.
Submission is refused. The order never enters the book. If this happens as the second leg of a cancel-replace, the amend has removed your original and left you holding nothing.
A resting order is left outside the band. As the reference price moves, an order that was legal when submitted can end up beyond the current boundary. Some venues cancel such orders; some leave them resting and inert, unable to match until the band moves back over them. An inert order looks identical to a working one in most interfaces.
A market order is capped. Where a band constrains execution, an aggressive order stops consuming levels at the boundary rather than continuing. The remainder is then cancelled or left resting, depending on the venue — which means an order you expected to complete may not have.
Halts
A halt is the venue suspending matching for an instrument. The engine stops applying incoming instructions to the book, and typically continues to accept cancellations.
What varies is almost everything else. Whether new orders can be submitted during a halt, whether resting orders survive it or are purged, whether the halt applies to one instrument or a group, how long it lasts, and how trading resumes are all venue decisions.
The resumption mechanism is the one worth knowing about, because it is not always a simple restart. Many venues reopen through a single-price auction rather than continuous matching, precisely because the book at the moment of resumption is likely to be one-sided and an immediate continuous open would produce another extreme print.
The mechanism
THE MECHANISM — bands, halts and your orders
· Order priced outside the band
→ rejected at validation. Never in
the book, never in the tape.
· Rejected as the replace leg of an amend
→ you hold NO ORDER. The cancel leg
already succeeded.
· Resting order left outside a moved band
→ inert, or cancelled. Both
behaviours exist and neither is
obvious in the interface.
· Market order reaching the boundary
→ stops consuming. NO GUARANTEE of
completion; remainder cancelled
or left resting.
· Trading halted
→ matching suspended. Cancels are
usually still accepted; new
orders often are not.
· A stop order during a halt
→ cannot submit into a book that is
not matching. The trigger and the
fill are separated by the halt.
· Band widths, reference prices, purge
behaviour and how trading resumes
→ VENUE-SPECIFIC. Static and
dynamic bands, auction reopens and
simple restarts all exist.Worked example
Illustrative figures, synthetic throughout. Suppose a venue with a dynamic band of 2% either side of the last trade, and a last trade of 40,000. The permitted range is 39,200 to 40,800.
You submit a limit buy at 39,000 as a resting bid well below the market. It is refused — the price is legal as an increment and outside the band, and the rejection message is about the band, not the increment.
You submit a limit buy at 39,300 instead, which is accepted and rests. The market then moves up and the last trade becomes 41,000, so the band becomes 40,180 to 41,820. Your order at 39,300 is now outside it. On a venue that leaves such orders resting, it sits there unable to match. Nothing tells you it has become inert; it simply never fills, including in a later move back down through 39,300 if the band has not caught up by then.
Now the other direction. A market sell for a large size arrives against a book whose bids are 40,000, 39,900 and then nothing until 38,000. Under an execution band with the same 2% boundary, the order consumes 40,000 and 39,900 and stops — the 38,000 level is outside the band and cannot be matched. The order is complete for part of its size and, depending on the venue, cancelled or resting for the rest.
Same band, three quite different outcomes, and in only one of them did anything look like an error.
The protection is not free
It is tempting to read bands and halts as unambiguously protective. Mechanically they are a trade, and the cost falls on a specific side.
A band that prevents an extreme print also prevents trading at that price. Anyone who wanted to exit a position, at any price, cannot do so while the boundary sits between them and the available liquidity. The mechanism does not remove the move; it removes access to the market during it. A halt does the same thing more completely: no fills, no exits, no entries, and a reopening price that can be a long way from where matching stopped.
There is no version of this without that trade-off, and which side of it any given participant is on depends entirely on what they held when it triggered.
The failure mode
The characteristic trap is assuming that a resting order is a working order. Both bands and halts create states in which an order exists, is listed, and cannot match — and the interface generally shows open orders rather than matchable ones.
The sharper case is stops. A stop is a trigger, not a price, and a triggered stop must submit an order into a book to achieve anything. A halt separates those two events: the condition can be met while the venue is not matching, and the order it submits then waits for the reopen along with everything else. The same is true of a band — a stop that triggers and submits a market order into a capped book gets the capped fill.
Neither mechanism is a failure of the venue. Both are cases where a protective-sounding instruction and a protective-sounding venue rule interact to produce no protection at all, which is exactly the combination that is easiest to assume away.