SecondaryIndividualAllocID (FIX tag 989)

StringFIX 5.0 SP2

SecondaryIndividualAllocID (tag 989) is a String field defined in FIX 5.0 SP2. It appears in 7 message types, always optionally.

At a glance

Tag: 989
Name: SecondaryIndividualAllocID
Datatype: String
Dialects: FIX 5.0 SP2
Messages: 7

What the specification says

Will allow the intermediary to specify an allocation ID generated by their system.

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

A real message using tag 989

TradeCaptureReport · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	148
35	MsgType	AE	TradeCaptureReport
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
32	LastQty	1000000
31	LastPx	1.09210
552	NoSides1 entry	1	repeating group
54	Side	1	Buy
78	NoAllocs2 entries	2	repeating group
79	AllocAccount	EXAMPLE
989	SecondaryIndividualAllocID	EXAMPLE
79	AllocAccount	EXAMPLE
989	SecondaryIndividualAllocID	EXAMPLE
10	CheckSum	149

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 5.0 SP2 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Where tag 989 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	Requiredness	Where in the message
AllocationInstruction	J	Optional	inside the AllocGrp component
AllocationInstructionAck	P	Optional	inside the AllocAckGrp component
AllocationInstructionAlert	BM	Optional	inside the AllocGrp component
AllocationReport	AS	Optional	inside the AllocGrp component
AllocationReportAck	AT	Optional	inside the AllocAckGrp component
TradeCaptureReport	AE	Optional	inside TrdCapRptSideGrp › TrdAllocGrp
TradeCaptureReportAck	AR	Optional	inside TrdCapRptAckSideGrp › TrdAllocGrp

Wire format

Free-form text. Any byte except the SOH separator is legal, so values are not trimmed or case-folded on the wire. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

Read tag 989 in TypeScript

decode.tsts

import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[989];field?.name;   // "SecondaryIndividualAllocID"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

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-fix50sp2

Try the decoder Source on GitHub