ListOrderStatus (FIX tag 431)

intFIX 4.4FIX 4.2

ListOrderStatus (tag 431) is an int field defined in FIX 4.4 and FIX 4.2. It appears in 1 message type and is required in 1 of them. It is an enumerated field with 7 defined values.

At a glance

Tag: 431
Name: ListOrderStatus
Datatype: int
Dialects: FIX 4.4 and FIX 4.2
Messages: 1
Valid values: 7

What the specification says

FIX 4.4

Code to represent the status of a list order

FIX 4.2

Code to represent the status of a list order.

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

A real message using tag 431

ListStatus · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	162
35	MsgType	N	List Status
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
66	ListID	EXAMPLE
429	ListStatusType	1	Ack
82	NoRpts	1
431	ListOrderStatus	1	InBiddingProcess
83	RptSeq	1
68	TotNoOrders	1
73	NoOrders1 entry	1	repeating group
11	ClOrdID	ORD-10042
14	CumQty	1000000
39	OrdStatus	0	New
151	LeavesQty	0
84	CxlQty	1000000
6	AvgPx	1.09215
10	CheckSum	123

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
1	InBiddingProcess	INBIDDINGPROCESS	FIX 4.4
2	ReceivedForExecution	RECEIVEDFOREXECUTION	FIX 4.4
3	Executing	EXECUTING	FIX 4.4
4	Canceling	CANCELING	FIX 4.4
5	Alert	ALERT	FIX 4.4
6	All Done	ALL_DONE	FIX 4.4
7	Reject	REJECT	FIX 4.4

Where tag 431 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
ListStatus	N	Required	Required	directly on the message body

Wire format

A whole number, optionally signed. Leading zeros are legal on the wire and are preserved in the raw value. @boarteam/fix parses the value as a number and reports parse/invalid-int when it does not lex as one; the raw string is kept either way.

Read tag 431 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 listOrderStatus = message.fields[431]?.raw;// e.g. "1" — InBiddingProcess// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(431)  ?.enumValues?.find((e) => e.value === listOrderStatus)  ?.description;

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