CollAsgnReason (FIX tag 895)

intFIX 4.4

CollAsgnReason (tag 895) is an int field defined in FIX 4.4. It appears in 3 message types and is required in 3 of them. It is an enumerated field with 8 defined values.

At a glance

Tag
895
Name
CollAsgnReason
Datatype
int
Dialects
FIX 4.4
Messages
3
Valid values
8

What the specification says

Reason for Collateral Assignment

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

A real message using tag 895

CollateralResponse · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength125
35MsgTypeAZCollateral Response
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
904CollRespIDEXAMPLE
902CollAsgnIDEXAMPLE
895CollAsgnReason0Initial
905CollAsgnRespType0Received
60TransactTime20240101-12:00:00.000
10CheckSum228
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.

ValueMeaningSymbolic name
0InitialINITIAL
1ScheduledSCHEDULED
2Time WarningTIME_WARNING
3Margin DeficiencyMARGIN_DEFICIENCY
4Margin ExcessMARGIN_EXCESS
5Forward Collateral DemandFORWARD_COLLATERAL_DEMAND
6Event of defaultEVENT_OF_DEFAULT
7Adverse tax eventADVERSE_TAX_EVENT

Where tag 895 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.

MessageMsgTypeRequirednessWhere in the message
CollateralAssignmentAYRequireddirectly on the message body
CollateralRequestAXRequireddirectly on the message body
CollateralResponseAZRequireddirectly 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 895 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 collAsgnReason = message.fields[895]?.raw;// e.g. "0" — Initial// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(895)  ?.enumValues?.find((e) => e.value === collAsgnReason)  ?.description;

Other int 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