CollInquiryQualifier (FIX tag 896)

intFIX 4.4FIX 5.0 SP2

CollInquiryQualifier (tag 896) is an int field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 2 message types, always optionally. It is an enumerated field with 8 defined values.

At a glance

Tag: 896
Name: CollInquiryQualifier
Datatype: int
Dialects: FIX 4.4 and FIX 5.0 SP2
Messages: 2
Valid values: 8

What the specification says

Collateral inquiry qualifiers:

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

A real message using tag 896

CollateralInquiryAck · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	100
35	MsgType	BG	Collateral Inquiry Ack
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
909	CollInquiryID	EXAMPLE
945	CollInquiryStatus	0	Accepted
938	NoCollInquiryQualifier2 entries	2	repeating group
896	CollInquiryQualifier	0	TradeDate
896	CollInquiryQualifier	0	TradeDate
10	CheckSum	105

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
0	TradeDate	TRADEDATE / TRADE_DATE
1	GC Instrument	GC_INSTRUMENT
2	CollateralInstrument	COLLATERALINSTRUMENT / COLLATERAL_INSTRUMENT
3	Substitution Eligible	SUBSTITUTION_ELIGIBLE
4	Not Assigned	NOT_ASSIGNED
5	Partially Assigned	PARTIALLY_ASSIGNED
6	Fully Assigned	FULLY_ASSIGNED
7	Outstanding Trades (Today < end date)	OUTSTANDING_TRADES

Where tag 896 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 5.0 SP2	Where in the message
CollateralInquiry	BB	Conditional	Optional	inside the CollInqQualGrp component
CollateralInquiryAck	BG	Conditional	Optional	inside the CollInqQualGrp component

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 896 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 collInquiryQualifier = message.fields[896]?.raw;// e.g. "0" — TradeDate// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(896)  ?.enumValues?.find((e) => e.value === collInquiryQualifier)  ?.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