Skip to main content
Sapinover - Click to go home

24-HOUR TRADING // WORKED EXAMPLE

A 5 PM order for the 8 PM overnight session

Your OMS rolls its business date at midnight. Your FIX session recycles at 6 PM. At 5:00 PM ET on Monday December 7, 2026 you want a limit order to start working at 8:00 PM, in the first overnight session. Can it be a DAY order, what does it look like, and what breaks?

The short answer

A DAY order can go into the overnight session; the venue is not the problem. The OMS is: it labels the order with the wrong date, and its midnight roll can kill the order in your books while it is still live at the broker. GTC is not the fix. Use GTD with an explicit UTC expiry, hold the order until 8 PM, and book fills on the trade date the broker sends back.

The night, hour by hour (ET)

TimeWhat happensTrade date
Mon 5:00 PMOrder staged in the OMS and held (see the options below)Mon
Mon 6:00 PMYour FIX session recycles; sequence numbers resetMon
Mon 8:00 PMTrade date rolls to Tuesday. Nasdaq and Cboe EDGX cancel resting day orders and pause; overnight ATSs keep tradingTue
Mon 8:55 PMCboe EDGX starts accepting and queuing overnight ordersTue
Mon 9:00 PMExchange night sessions open, where the exchange has launched oneTue
Mon 11:59 PMFills so far are booked by an unfixed OMS under MondayTue
Tue 12:00 AMThe OMS rolls its date and expires Monday's DAY ordersTue
Tue 3:59 AMUnder its rules, Nasdaq deactivates open Night Session orders just before 4:00 AMTue
Wed Dec 9Settlement, T+1 from trade date Tuesday

What breaks with an unfixed OMS

The wrong date at entry

At 8:30 PM the OMS still thinks today is Monday, so a DAY order carries Monday's business date. The street treats everything after 8:00 PM Monday as trade date Tuesday.

Fills before midnight land on the wrong day

Execution reports should carry TradeDate(75)=20261208. An OMS that books by its own clock puts those fills on Monday's blotter, feeding the wrong date to allocations, confirmations and compliance, and settling them on Tuesday instead of Wednesday.

The midnight roll orphans the order

A normal end-of-day job expires Monday's DAY orders while the order is still live at the broker. Fills after midnight then arrive for an order the OMS considers dead: rejected, unmatched or repaired by hand, and pre-trade risk loses sight of a live order.

One order, two dates

Fills from 9 PM to midnight sit on Monday and later ones on Tuesday, all for trade date Tuesday. Average price, allocations and commissions come out split.

The 6 PM recycle

Harmless for an order released at 8 PM. The risks sit elsewhere: the recycle does not line up with the 8 PM date boundary, post-market fills can be missed while the session is down, messages from before a sequence reset cannot be recovered with a ResendRequest, and a broker that cancels on disconnect will kill live orders. Confirm that behaviour.

DAY, GTC or GTD

DAY 59=0

Valid, but it means whatever each venue says it means, and an OMS will still expire it at its own midnight. The FIX FAQ advises against 59=0 on its own: pair it with the target session.

GTC 59=1

Survives the OMS roll, but at the broker it can keep working in later sessions, including the next nights, unless the session is scoped. That is the unintended-fill risk. Do not use GTC to paper over an OMS date problem.

GTD 59=6 with ExpireTime(126)

The cleanest fix: an explicit end in UTC that means the same thing at the broker and in your OMS. In December, 4:00 AM ET is 09:00 UTC; recheck at the March daylight-saving change. The FAQ recommends against ExpireDate(432) overnight, because a local date is ambiguous once a session crosses midnight.

Hold it, or send it early?

A. Hold in the OMS, release at 8 PM (recommended)B. Send at 5 PM with a future start time
HowThe OMS keeps the order unsent and releases it at 20:00 ETSend at 5 PM with EffectiveTime(168) = 01:00 UTC; the broker holds it
6 PM recycleNothing in flight, so no exposureThe order lives through the recycle: cancel-on-disconnect risk, and no resend across the reset
8 PM venue cancelsReleased after themMust be designated for the night session or it is cancelled with the day's orders
Trade dateReleased after the 8 PM roll, so natively TuesdayEntered on Monday's date, trades on Tuesday's: one order spanning two dates
Price checksRun at release, against the evening's overnight bandsA 5 PM limit can fall outside the overnight price bands
Broker supportNothing specialNot every broker or venue honours EffectiveTime overnight; get it confirmed

OMS settings for Option A

Business-date roll
20:00 ET. If that is not possible: orders released after 20:00 get the next trade date
Order status at 5 PM
Staged or held, not sent
Scheduled release
20:00 ET Monday (01:00 UTC Tuesday December 8)
Trade date on the order
2026-12-08
Time in force
GTD with ExpireTime 09:00 UTC (4:00 AM ET, end of the night session); 21:00 UTC instead to keep it working through the day
Session
Overnight, in the TradingSessions group: 386=1, 336=6, 625=3
Order type
Limit only. Cboe EDGX, for one, accepts only limit orders outside regular hours; block market and on-open/on-close orders for overnight
Price collar
An internal collar inside each venue's overnight price bands; check each venue's band and reference price
Compliance and risk check
At release, not at staging
Midnight end-of-day job
Exclude live GTD and overnight orders from DAY expiry, or reconcile against broker status before purging
Booking rule
Book fills on TradeDate(75) from the execution report, never on the OMS clock
Settlement date
T+1 from trade date: Wednesday December 9
FIX recycle
Keep 18:00 ET, but complete it before the 20:00 release with nothing outstanding

The wire, end to end: break it yourself

Break it yourself

Set up the desk the way yours is set up. The diagram below marks every step that breaks or carries a risk.

5 breaks

2 further risks

OMS date roll
Time in force
At 5 PM
Book fills on
Broker cancel-on-disconnect
5 / 13 · Mon 5:00 PM (sent early)
Your OMSFIX engineBrokerVenuesClearingMon 5:00 PM22:00Z MonStage the order; hold itMon 6:00 PM23:00Z Mon✕Daily recycle: Logout, then Logon with resetMon 8:00 PM01:00Z Tue✕Nasdaq and EDGX cancel resting day orders; pause to 9 PMMon 8:00 PM01:00Z TueTrade date becomes Tuesday Dec 8Mon 8:00 PM01:00Z Tue!Release: NewOrderSingle (risk checks run now)Mon 8:00 PM01:00Z TueExecutionReport: NewMon 8:15 PM01:15Z Tue✕Partial fill, executed on an overnight ATSMon 8:55 PM01:55Z TueChild orders queue for the night sessionMon 9:00 PM02:00Z TueExchange night sessions open; further fillsTue 12:00 AM05:00Z Tue✕OMS midnight roll skips the live GTD orderTue 3:59 AM08:59Z TueVenues cancel open night ordersTue 4:00 AM09:00Z Tue!ExecutionReport: ExpiredWed Dec 9✕Settlement: T+1 from trade date Tuesday

Mon 5:00 PM (sent early) · 01:00Z Tue

Release: NewOrderSingle (risk checks run now)

| |
| | |
|(limit)
(DAY: ends when each venue says)
(EffectiveTime: start at 8:00 PM ET)
| |(overnight session)
(TransactTime, UTC)

Risk: Depends on EffectiveTime. Sent at 5 PM to start at 8 PM: the broker must honour EffectiveTime(168) overnight, and the limit is checked before the evening's overnight band reference.

Compliance and limit checks run at release, not at staging, because restrictions can change between 5 and 8 PM.

Hover or tap any tag to decode it. Click a row, use the arrows, or play the night.

Your books against the broker's

What your OMS believes about the order, hour by hour, next to what the broker believes. Highlighted rows are where they disagree.

Time (ET)Your OMSBroker
Mon 5:00 PMSent, workingHeld until 8 PM
Mon 6:00 PMWorkingCancelled on disconnectout of sync
Mon 8:00 PMWorking, dated MonCancelledout of sync
Mon 8:15 PMWorking (no fills arrive)Cancelledout of sync
Tue 12:05 AMExpired by the midnight jobCancelled
Tue 4:00 AMExpired; new fills do not matchCancelled
Tue 8:15 PMClosedClosed

TransactTime(60) in UTC already reads Tuesday at 8:00 PM ET. Neither UTC midnight nor local midnight lines up with the 8 PM ET boundary, which is why nothing should work out the trade date from a clock. For Option B, the same order goes at 5 PM with EffectiveTime(168)=20261208-01:00:00 and the same tags 59, 126 and the session group.

Questions for your OMS, EMS, broker and venues

The full question set, grouped by who you ask and tied to your own stack, is in the 23/5 Readiness Map questionnaire, along with acceptance tests to run before the first overnight ticket.

Sources