Friday, 20 November 2026 · Free. No paywall. No subscription.
Search The MidPoint News

Search articles, videos and sections. Press / to open, Esc to close.

FIX 4.4Field

TimeInForce <59>

Tag
59
Type
char · code set TimeInForceCodeSet
FIXML name
TmInForce
Pedigree
Added FIX 2.7
Versions
FIX Latest ✓ · FIX 4.4 ✓ · FIX 4.2 ✓

This page shows TimeInForce <59> as defined in FIX 4.4. For the current standard, see tag 59 TimeInForce in FIX Latest.

TimeInForce <59> in plain English

Summary by The MidPoint News, based on the FIX Latest description in the Orchestra file. The FIX 4.4 description is quoted in full below and may differ.

TimeInForce says how long an order stays in effect. If the field is absent the order is treated as a day order.

Common values

ValueNameMeaning (from the Orchestra file)
59=0DayDay (or session)Day (or session)
59=1GoodTillCancelGood Till Cancel (GTC)Good Till Cancel (GTC)
59=2AtTheOpeningAt the Opening (OPG)At the Opening (OPG)
59=3ImmediateOrCancelImmediate or Cancel (IOC)Immediate or Cancel (IOC)
59=4FillOrKillFill or Kill (FOK)Fill or Kill (FOK)
59=6GoodTillDateGood Till DateGood Till Date
59=7AtTheCloseAt the CloseAt the Close

A selection. The full list of values is in the table further down.

Where it is used

NewOrderSingle (35=D), ExecutionReport (35=8), OrderCancelReplaceRequest (35=G), NewOrderCross (35=s), CrossOrderCancelReplaceRequest (35=t), NewOrderMultileg (35=AB), MultilegOrderCancelReplace (35=AC), ListOrdGrp (repeating group) and 2 more. In all, 10 messages in FIX 4.4 can carry it. Full list.

Example message

8=FIX.4.4|9=153|35=D|49=BUYSIDE|56=SELLSIDE|34=215|52=20261116-08:30:00.000|11=ORD-1001|1=ACCT-01|21=1|55=AAPL|54=1|60=20261116-08:30:00.000|38=1000|40=2|44=190.50|59=0|10=130

Illustrative example, not real orders or market data. A NewOrderSingle (35=D) in FIX 4.4, shown with BeginString FIX.4.4. Instrument identifiers (such as AAPL, ISIN US0378331005, ESZ6, XNAS, XCME) are real public codes used for illustration. Order and execution IDs, accounts, prices, quantities and times are made up. Fields are separated by | here; on the wire the separator is the SOH character (ASCII 1). BodyLength (9) and CheckSum (10) are calculated for this example. Every tag and value in it is checked against the FIX 4.4 dictionary, but it is not a complete specification of the message.

Description (from the Orchestra file)

Specifies how long the order remains in effect. Absence of this field is interpreted as DAY.

Values (8)

ValueNameDescriptionPedigreeIn LatestIn 4.2
0 DayDay (or session) Day (or session) Added FIX 2.7 ✓✓
1 GoodTillCancelGood Till Cancel (GTC) Good Till Cancel (GTC) Added FIX 2.7 ✓✓
2 AtTheOpeningAt the Opening (OPG) At the Opening (OPG) Added FIX 2.7 ✓✓
3 ImmediateOrCancelImmediate or Cancel (IOC) Immediate or Cancel (IOC) Added FIX 2.7 ✓✓
4 FillOrKillFill or Kill (FOK) Fill or Kill (FOK) Added FIX 2.7 ✓✓
5 GoodTillCrossingGood Till Crossing (GTX) Good Till Crossing (GTX) Added FIX 2.7 ✓✓
6 GoodTillDateGood Till Date Good Till Date Added FIX 4.0 ✓✓
7 AtTheCloseAt the Close At the Close Added FIX 4.3 ✓–

Used in

Messages (7)

Components and repeating groups (3)

NameKindPresence
ListOrdGrpRepeating groupOptional
MDFullGrpRepeating groupOptional
MDIncGrpRepeating groupOptional
All 10 messages that can carry TimeInForce, including through components and groups