IndividualAllocID (FIX tag 467)

StringFIX 4.4FIX 5.0 SP2

IndividualAllocID (tag 467) is a String field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 15 message types, always optionally.

At a glance

Tag: 467
Name: IndividualAllocID
Datatype: String
Dialects: FIX 4.4 and FIX 5.0 SP2
Messages: 15

What the specification says

Unique identifier for a specific NoAllocs (78) repeating group instance (e.g. for an AllocAccount).

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

A real message using tag 467

NewOrderSingle · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	162
35	MsgType	D	Order – Single
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
11	ClOrdID	ORD-10042
78	NoAllocs2 entries	2	repeating group
79	AllocAccount	EXAMPLE
467	IndividualAllocID	EXAMPLE
79	AllocAccount	EXAMPLE
467	IndividualAllocID	EXAMPLE
54	Side	1	Buy
60	TransactTime	20240101-12:00:00.000
40	OrdType	1	Market
10	CheckSum	031

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.

Where tag 467 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 5.0 SP2	Where in the message
AllocationInstruction	J	Optional	Optional	inside the AllocGrp component
AllocationInstructionAck	P	Optional	Optional	inside the AllocAckGrp component
AllocationInstructionAlert	BM	—	Optional	inside the AllocGrp component
AllocationReport	AS	Optional	Optional	inside the AllocGrp component
AllocationReportAck	AT	Optional	Optional	inside the AllocAckGrp component
Confirmation	AK	Optional	Optional	directly on the message body
ConfirmationRequest	BH	Optional	Optional	directly on the message body
CrossOrderCancelReplaceRequest	t	Optional	Optional	inside SideCrossOrdModGrp › PreAllocGrp
ExecutionReport	8	—	Optional	inside the PreAllocGrp component
MultilegOrderCancelReplace	AC	Optional	Optional	inside the PreAllocMlegGrp component
NewOrderCross	s	Optional	Optional	inside SideCrossOrdModGrp › PreAllocGrp
NewOrderList	E	Optional	Optional	inside ListOrdGrp › PreAllocGrp
NewOrderMultileg	AB	Optional	Optional	inside the PreAllocMlegGrp component
NewOrderSingle	D	Optional	Optional	inside the PreAllocGrp component
OrderCancelReplaceRequest	G	Optional	Optional	inside the PreAllocGrp component
TradeCaptureReport	AE	Optional	Optional	inside TrdCapRptSideGrp › TrdAllocGrp
TradeCaptureReportAck	AR	Optional	Optional	inside the TrdAllocGrp component

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 467 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 field = message.fields[467];field?.name;   // "IndividualAllocID"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-fix44

Try the decoder Source on GitHub