AllocID (FIX tag 70)

StringFIX 4.4FIX 4.2FIX 5.0 SP2

AllocID (tag 70) is a String field defined in FIX 4.4, FIX 4.2 and FIX 5.0 SP2. It appears in 14 message types and is required in 3 of them.

At a glance

Tag: 70
Name: AllocID
Datatype: String
Dialects: FIX 4.4, FIX 4.2 and FIX 5.0 SP2
Messages: 14

What the specification says

FIX 4.4

Unique identifier for allocation message. (Prior to FIX 4.1 this field was of type int)

FIX 4.2

Unique identifier for allocation message. (Prior to FIX 4.1 this field was of type int)

FIX 5.0 SP2

Unique identifier for allocation message.

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

A real message using tag 70

NewOrderSingle · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	122
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
70	AllocID	EXAMPLE
54	Side	1	Buy
60	TransactTime	20240101-12:00:00.000
40	OrdType	1	Market
10	CheckSum	163

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 70 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
AllocationInstruction	J	Required	Required	Required	directly on the message body
AllocationInstructionAck	P	Required	Required	Required	directly on the message body
AllocationInstructionAlert	BM	—	—	Required	directly on the message body
AllocationReport	AS	Optional	—	Optional	directly on the message body
AllocationReportAck	AT	Required	—	Optional	directly on the message body
Confirmation	AK	Optional	—	Optional	directly on the message body
ConfirmationRequest	BH	Optional	—	Optional	directly on the message body
CrossOrderCancelReplaceRequest	t	Optional	—	Optional	inside the SideCrossOrdModGrp component
ExecutionReport	8	—	—	Optional	directly on the message body
MultilegOrderCancelReplace	AC	Optional	—	Optional	directly on the message body
NewOrderCross	s	Optional	—	Optional	inside the SideCrossOrdModGrp component
NewOrderList	E	Optional	—	Optional	inside the ListOrdGrp component
NewOrderMultileg	AB	Optional	—	Optional	directly on the message body
NewOrderSingle	D	Optional	—	Optional	directly on the message body
OrderCancelReplaceRequest	G	Optional	—	Optional	directly on the message body
SettlementInstructions	T	—	Optional	—	directly on the message body
TradeCaptureReport	AE	Optional	—	Optional	inside the TrdCapRptSideGrp component
TradeCaptureReportAck	AR	—	—	Optional	inside the TrdCapRptAckSideGrp 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 70 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[70];field?.name;   // "AllocID"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