Brokers often redefine Tag 59 (TimeInForce) semantics so Day orders don’t always expire when you expect.

You see Day as “valid for the trading day,” but exchanges and brokers can apply different clocks: regular session close, extended-session close, or even the next business session after a halt or holiday. That mismatch means your intended intraday behavior can become a multi-session exposure or get cancelled without clear notice.

Why it happens: Exchanges define session boundaries and enforcement rules; your broker implements those rules and may layer operational policies (routing, order batching, risk checks). During after hours or around halts, some systems auto-convert or reject Day orders, treat them as active until the next official session, or purge them at the exchange’s discretion.

Common surprises: your Day limit order posts in extended hours and executes against thin liquidity; a Day market order is queued and executed at the opening after a halt; orders you thought expired on a holiday are retained as GTC by the broker’s system. Some brokers’ mobile apps don’t surface the conversion, leaving you thinking your TIF behaved one way when it didn’t.

How to protect your trades: check your broker’s TIF definitions and the exchange rulebook, set explicit TIF values like GTD with a date, avoid relying on implicit Day behavior around announcements, and use market-on-close or limit-on-close for session-end goals. Monitor order confirmations and post-trade status, and test with small orders if you need deterministic behavior.

Best practice: treat Tag 59 as a contract between you, your broker, and the exchange: read the fine print, log the executed TIF, and design automation that accounts for session boundaries, after hours rules, and the possibility of halts or holidays altering semantics.

Oh hi there 👋
It’s nice to meet you.

Sign up to get access and receive our gift: FIX Standard introductory book.

We don’t spam! Read our privacy policy for more info.

Explore More

Smart Order Routers and FIX: How Dynamic Venue Selection Impacts Execution Quality

Execution in modern markets depends on Smart Order Routers (SORs) and the FIX protocol to route orders across venues in real time; you must understand how algorithmic logic and FIX messaging shape outcomes. When tuned correctly, dynamic venue selection can significantly improve fills and reduce slippage, but latency, hidden liquidity

FIX Protocol > FIX tag 305 UnderlyingSecurityIDSource

Tag 305 is an important component of the FIX Protocol, serving as a key identifier in trading transactions. It refers to the UnderlyingSecurityIDSource, which specifies the source of the identifier for an underlying security. In other words, when you engage in financial trading, this tag tells you where the security

FIX Protocol > FIX tag 262 MDReqID

There’s a lot to unpack when it comes to the financial industry, especially when delving into the details of the FIX Protocol. One of the integral components within the FIX framework is the FIX tag 262 MDReqID. Understanding this tag is imperative for effective communication and data exchange in trading