AllocStatus (FIX tag 87)

intFIX 4.4FIX 4.2

AllocStatus (tag 87) is an int field defined in FIX 4.4 and FIX 4.2. It appears in 3 message types and is required in 3 of them. It is an enumerated field with 6 defined values.

At a glance

Tag: 87
Name: AllocStatus
Datatype: int
Dialects: FIX 4.4 and FIX 4.2
Messages: 3
Valid values: 6

What the specification says

FIX 4.4

Identifies status of allocation

FIX 4.2

Identifies status of allocation.

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

A real message using tag 87

AllocationInstructionAck · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	104
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)
10	CheckSum	056

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	accepted (successfully processed)	ACCEPTED / Accepted	FIX 4.4, FIX 4.2
1	block level reject	BLOCK_LEVEL_REJECT / BlockLevelReject	FIX 4.4, FIX 4.2
2	account level reject	ACCOUNT_LEVEL_REJECT / AccountLevelReject	FIX 4.4, FIX 4.2
3	received (received, not yet processed)	RECEIVED / Received	FIX 4.4, FIX 4.2
4	incomplete	INCOMPLETE	FIX 4.4
5	rejected by intermediary	REJECTED_BY_INTERMEDIARY	FIX 4.4

Where tag 87 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
AllocationInstructionAck	P	Required	Required	directly on the message body
AllocationReport	AS	Required	—	directly on the message body
AllocationReportAck	AT	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 87 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 allocStatus = message.fields[87]?.raw;// e.g. "0" — accepted (successfully processed)// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(87)  ?.enumValues?.find((e) => e.value === allocStatus)  ?.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