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.2Field

SettlmntTyp <63>

Tag
63
Type
char · code set SettlmntTypCodeSet
Pedigree
Added FIX 2.7
Versions
FIX Latest ✓ · FIX 4.4 ✓ · FIX 4.2 ✓

This page shows SettlmntTyp <63> as defined in FIX 4.2. For the current standard, see tag 63 SettlType in FIX Latest.

SettlmntTyp <63> in plain English

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

SettlType gives the settlement period for an order. If SettlDate (64) is present it overrides this field; if both are absent, regular settlement for the security on the exchange of execution applies.

Common values

ValueNameMeaning (from the Orchestra file)
63=0RegularRegular
63=1CashCash
63=2NextDayNext DayNext Day
63=3TPlus2T+2T+2
63=6FutureFuture

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), Allocation (35=J), BidCompReqGrp (repeating group), BidCompRspGrp (repeating group), ListOrdGrp (repeating group) . In all, 7 messages in FIX 4.2 can carry it. Full list.

Example message

8=FIX.4.2|9=158|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|63=0|10=092

Illustrative example, not real orders or market data. A NewOrderSingle (35=D) in FIX 4.2, shown with BeginString FIX.4.2. 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.2 dictionary, but it is not a complete specification of the message.

Description (from the Orchestra file)

Indicates order settlement period. Absence of this field is interpreted as Regular. Regular is defined as the default settlement period for the particular security on the exchange of execution.

Values (10)

ValueNameDescriptionPedigreeIn LatestIn 4.4
0 Regular Regular Added FIX 2.7 ✓✓
1 Cash Cash Added FIX 2.7 ✓✓
2 NextDayNext Day Next Day Added FIX 2.7 ✓✓
3 TPlus2T+2 T+2 Added FIX 2.7 ✓✓
4 TPlus3T+3 T+3 Added FIX 2.7 ✓✓
5 TPlus4T+4 T+4 Added FIX 2.7 ✓✓
6 Future Future Added FIX 2.7 ✓✓
7 WhenAndIfIssuedWhen Issued When Issued Added FIX 2.7 ✓✓
8 SellersOptionSellers Option Sellers Option Added FIX 2.7 ✓✓
9 TPlus5T+ 5 T+ 5 Added FIX 3.0 ✓✓

Used in

Messages (4)

MessageMsgTypePresence
ExecutionReport8Optional
NewOrderSingleDOptional
OrderCancelReplaceRequestGOptional
AllocationJOptional

Components and repeating groups (3)

NameKindPresence
BidCompReqGrpRepeating groupOptional
BidCompRspGrpRepeating groupOptional
ListOrdGrpRepeating groupOptional
All 7 messages that can carry SettlmntTyp, including through components and groups