OpenCloseSettlFlag (FIX tag 286)

MultipleValueStringFIX 4.4FIX 4.2

OpenCloseSettlFlag (tag 286) is a MultipleValueString field defined in FIX 4.4 and FIX 4.2. It appears in 3 message types, always optionally. It is an enumerated field with 6 defined values. FIX 4.2 calls this field OpenCloseSettleFlag; the tag number is unchanged, so the two are the same field on the wire.

Also known as OpenCloseSettleFlag

FIX 4.2 calls tag 286 OpenCloseSettleFlag. It is the same field on the wire — only the name changed — so a message encoded by either side interoperates.

At a glance

Tag: 286
Name: OpenCloseSettlFlag
Datatype: MultipleValueString (String)
Dialects: FIX 4.4 and FIX 4.2
Messages: 3
Valid values: 6

What the specification says

FIX 4.4

Flag that identifies a market data entry (Prior to FIX 4.3 this field was of type char)

FIX 4.2

Flag that identifies a price.

Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.

A real message using tag 286

MarketDataSnapshotFullRefresh · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	93
35	MsgType	W	Market Data-Snapshot/Full Refresh
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
268	NoMDEntries2 entries	2	repeating group
269	MDEntryType	0	Bid
286	OpenCloseSettlFlag	0	Daily Open / Close / Settlement entry
269	MDEntryType	0	Bid
286	OpenCloseSettlFlag	0	Daily Open / Close / Settlement entry
10	CheckSum	034

Edit and decode it yourself

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.

Open in the full decoder →

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.

Valid values

A value outside this list is not a parse error — the message still decodes — but validate() reports it as validate/value-not-in-enum.

Value	Meaning	Symbolic name	Dialects
0	Daily Open / Close / Settlement entry	DAILY_OPEN / DailyOpen	FIX 4.4, FIX 4.2
1	Session Open / Close / Settlement entry	SESSION_OPEN / SessionOpen	FIX 4.4, FIX 4.2
2	Delivery Settlement entry	DELIVERY_SETTLEMENT_ENTRY / DeliverySettlementEntry	FIX 4.4, FIX 4.2
3	Expected entry	EXPECTED_ENTRY	FIX 4.4
4	Entry from previous business day	ENTRY_FROM_PREVIOUS_BUSINESS_DAY	FIX 4.4
5	Theoretical Price value	THEORETICAL_PRICE_VALUE	FIX 4.4

Where tag 286 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	FIX 4.4	FIX 4.2	Where in the message
MarketDataIncrementalRefresh	X	Optional	Optional	inside the MDIncGrp component
MarketDataRequest	V	Optional	—	directly on the message body
MarketDataSnapshotFullRefresh	W	Optional	Optional	inside the MDFullGrp component

Wire format

Several values in one field, separated by spaces. Decoders return an array. @boarteam/fix splits the value on its delimiter and returns an array of strings.

Read tag 286 in TypeScript

decode.tsts

import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const openCloseSettlFlag = message.fields[286]?.raw;// e.g. "0" — Daily Open / Close / Settlement entry// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(286)  ?.enumValues?.find((e) => e.value === openCloseSettlFlag)  ?.description;

Other MultipleValueString fields

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

Try the decoder Source on GitHub