LegSettlDate (FIX tag 588)
LegSettlDate (tag 588) is a LocalMktDate field defined in FIX 4.4. It appears in 10 message types, always optionally.
At a glance
- Tag
- 588
- Name
- LegSettlDate
- Datatype
- LocalMktDate (String)
- Format
- YYYYMMDD
- Dialects
- FIX 4.4
- Messages
- 10
What the specification says
Refer to description for SettlDate[64]
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 588
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIX.4.4 | |
| 9 | BodyLength | 189 | |
| 35 | MsgType | 8 | Execution Report |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 37 | OrderID | ORD-10042 | |
| 17 | ExecID | EXEC-88117 | |
| 150 | ExecType | 0 | New |
| 39 | OrdStatus | 0 | New |
| 54 | Side | 1 | Buy |
| 151 | LeavesQty | 0 | |
| 14 | CumQty | 1000000 | |
| 6 | AvgPx | 1.09215 | |
| 555 | NoLegs2 entries | 2 | repeating group |
| 600 | LegSymbol | EXAMPLE | |
| 588 | LegSettlDate | 20240101 | |
| 600 | LegSymbol | EXAMPLE | |
| 588 | LegSettlDate | 20240101 | |
| 10 | CheckSum | 205 |
Shown with | separators for readability. On the wire FIX uses SOH (0x01), an invisible control byte — and because BodyLength and CheckSum are computed over the actual bytes, the two forms have different checksums. Both are valid and both decode here.
Generated from the FIX 4.4 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.
Where tag 588 appears
Requiredness is a property of the message, not of the field: the same tag can be optional in one message and conditionally required in another.
| Message | MsgType | Requiredness | Where in the message |
|---|---|---|---|
| ExecutionReport | 8 | Conditional | inside the InstrmtLegExecGrp component |
| MultilegOrderCancelReplace | AC | Conditional | inside the LegOrdGrp component |
| NewOrderMultileg | AB | Conditional | inside the LegOrdGrp component |
| Quote | S | Conditional | inside the LegQuotGrp component |
| QuoteRequest | R | Conditional | inside QuotReqGrp › QuotReqLegsGrp |
| QuoteRequestReject | AG | Conditional | inside QuotReqRjctGrp › QuotReqLegsGrp |
| QuoteResponse | AJ | Conditional | inside the LegQuotGrp component |
| QuoteStatusReport | AI | Conditional | inside the LegQuotStatGrp component |
| TradeCaptureReport | AE | Conditional | inside the TrdInstrmtLegGrp component |
| TradeCaptureReportAck | AR | Conditional | inside the TrdInstrmtLegGrp component |
Wire format
A calendar date in the market's local timezone, with no time component and no offset. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.
Read tag 588 in TypeScript
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[588];field?.name; // "LegSettlDate"field?.raw; // the verbatim wire stringfield?.value; // coerced to a stringOther LocalMktDate fields
- 611LegMaturityDate
- 542UnderlyingMaturityDate
- 541MaturityDate
- 504PaymentDate
- 503CardStartDate
- 490CardExpDate
- 486DateOfBirth
- 696YieldRedemptionDate
- 701YieldCalcDate
- 715ClearingBusinessDate
- 739LegDatedDate
- 743DeliveryDate
- 432ExpireDate
- 866EventDate
- 873DatedDate
- 874InterestAccrualDate
- 915AgreementDate
- 916StartDate
- 259BasisFeatureDate
- 917EndDate
- 254LegRedemptionDate
- 249LegIssueDate
- 248LegCouponPaymentDate
- 247UnderlyingRedemptionDate
Decode this in your own code
The same engine that produced the decoded example above is an Apache-2.0 npm package with zero runtime dependencies. It runs in Node and in the browser, and parse() returns problems as data instead of throwing.
npm i @boarteam/fix @boarteam/fix-dict-fix44