AllocRejCode (FIX tag 88)

intFIX 4.4FIX 4.2FIX 5.0 SP2

AllocRejCode (tag 88) is an int field defined in FIX 4.4, FIX 4.2 and FIX 5.0 SP2. 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, FIX 4.2 and FIX 5.0 SP2
Messages: 3
Valid values: 14

What the specification says

FIX 4.4

Identifies reason for rejection

FIX 4.2

Identifies reason for rejection.

FIX 5.0 SP2

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

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	109
35	MsgType	P	Allocation Instruction Ack
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
70	AllocID	EXAMPLE
60	TransactTime	20240101-12:00:00.000
87	AllocStatus	0	accepted (successfully processed)
88	AllocRejCode	0	unknown account(s)
10	CheckSum	027

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	unknown account(s)	UNKNOWN_ACCOUNT / UnknownAccount	FIX 4.4, FIX 4.2, FIX 5.0 SP2
1	incorrect quantity	INCORRECT_QUANTITY / IncorrectQuantity	FIX 4.4, FIX 4.2, FIX 5.0 SP2
2	incorrect average price	INCORRECT_AVERAGE_PRICE / IncorrectAveragegPrice / INCORRECT_AVERAGEG_PRICE	FIX 4.4, FIX 4.2, FIX 5.0 SP2
3	unknown executing broker mnemonic	UNKNOWN_EXECUTING_BROKER_MNEMONIC / UnknownExecutingBrokerMnemonic	FIX 4.4, FIX 4.2, FIX 5.0 SP2
4	commission difference	COMMISSION_DIFFERENCE / CommissionDifference	FIX 4.4, FIX 4.2, FIX 5.0 SP2
5	unknown OrderID (37)	UNKNOWN_ORDERID / UnknownOrderID	FIX 4.4, FIX 4.2, FIX 5.0 SP2
6	unknown ListID (66)	UNKNOWN_LISTID / UnknownListID	FIX 4.4, FIX 4.2, FIX 5.0 SP2
7	other (further in Note 58=)	OTHER / OtherSeeText	FIX 4.4, FIX 4.2, FIX 5.0 SP2
8	incorrect allocated quantity	INCORRECT_ALLOCATED_QUANTITY	FIX 4.4, FIX 5.0 SP2
9	calculation difference	CALCULATION_DIFFERENCE	FIX 4.4, FIX 5.0 SP2
10	unknown or stale ExecID (17)	UNKNOWN_OR_STALE_EXECID	FIX 4.4, FIX 5.0 SP2
11	mismatched data value (further in Note 58=)	MISMATCHED_DATA_VALUE / MISMATCHED_DATA	FIX 4.4, FIX 5.0 SP2
12	unknown ClOrdID (11)	UNKNOWN_CLORDID	FIX 4.4, FIX 5.0 SP2
13	warehouse request rejected	WAREHOUSE_REQUEST_REJECTED	FIX 4.4, FIX 5.0 SP2
99	Other	OTHER_1	FIX 5.0 SP2

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.

Message	MsgType	FIX 4.4	FIX 4.2	FIX 5.0 SP2	Where in the message
AllocationInstructionAck	P	Conditional	Optional	Optional	directly on the message body
AllocationReport	AS	Conditional	—	Optional	directly on the message body
AllocationReportAck	AT	Conditional	—	Optional	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 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;

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