AllocRejCode (FIX tag 88)

intFIX 4.4FIX 4.2

AllocRejCode (tag 88) is an int field defined in FIX 4.4 and FIX 4.2. It appears in 3 message types, always optionally. It is an enumerated field with 14 defined values.

At a glance

Tag
88
Name
AllocRejCode
Datatype
int
Dialects
FIX 4.4 and FIX 4.2
Messages
3
Valid values
14

What the specification says

FIX 4.4

Identifies reason for rejection

FIX 4.2

Identifies reason for rejection.

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

A real message using tag 88

AllocationInstructionAck · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength109
35MsgTypePAllocation Instruction Ack
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
70AllocIDEXAMPLE
60TransactTime20240101-12:00:00.000
87AllocStatus0accepted (successfully processed)
88AllocRejCode0unknown account(s)
10CheckSum027
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 nameDialects
0unknown account(s)UNKNOWN_ACCOUNT / UnknownAccountFIX 4.4, FIX 4.2
1incorrect quantityINCORRECT_QUANTITY / IncorrectQuantityFIX 4.4, FIX 4.2
2incorrect average priceINCORRECT_AVERAGE_PRICE / IncorrectAveragegPriceFIX 4.4, FIX 4.2
3unknown executing broker mnemonicUNKNOWN_EXECUTING_BROKER_MNEMONIC / UnknownExecutingBrokerMnemonicFIX 4.4, FIX 4.2
4commission differenceCOMMISSION_DIFFERENCE / CommissionDifferenceFIX 4.4, FIX 4.2
5unknown OrderID (37)UNKNOWN_ORDERID / UnknownOrderIDFIX 4.4, FIX 4.2
6unknown ListID (66)UNKNOWN_LISTID / UnknownListIDFIX 4.4, FIX 4.2
7other (further in Note 58=)OTHER / OtherSeeTextFIX 4.4, FIX 4.2
8incorrect allocated quantityINCORRECT_ALLOCATED_QUANTITYFIX 4.4
9calculation differenceCALCULATION_DIFFERENCEFIX 4.4
10unknown or stale ExecID (17)UNKNOWN_OR_STALE_EXECIDFIX 4.4
11mismatched data value (further in Note 58=)MISMATCHED_DATA_VALUEFIX 4.4
12unknown ClOrdID (11)UNKNOWN_CLORDIDFIX 4.4
13warehouse request rejectedWAREHOUSE_REQUEST_REJECTEDFIX 4.4

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

MessageMsgTypeFIX 4.4FIX 4.2Where in the message
AllocationInstructionAckPConditionalOptionaldirectly on the message body
AllocationReportASConditionaldirectly on the message body
AllocationReportAckATConditionaldirectly 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 88 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 allocRejCode = message.fields[88]?.raw;// e.g. "0" — unknown account(s)// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(88)  ?.enumValues?.find((e) => e.value === allocRejCode)  ?.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