TradeAllocIndicator (FIX tag 826)

intFIX 4.4

TradeAllocIndicator (tag 826) is an int field defined in FIX 4.4. It appears in 1 message type, always optionally. It is an enumerated field with 3 defined values.

At a glance

Tag: 826
Name: TradeAllocIndicator
Datatype: int
Dialects: FIX 4.4
Messages: 1
Valid values: 3

What the specification says

Identifies how the trade is to be allocated

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

A real message using tag 826

TradeCaptureReport · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	195
35	MsgType	AE	Trade Capture Report
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
571	TradeReportID	EXAMPLE
570	PreviouslyReported	N	not reported to counterparty
32	LastQty	1000000
31	LastPx	1.09210
75	TradeDate	20240101
60	TransactTime	20240101-12:00:00.000
552	NoSides2 entries	2	repeating group
54	Side	1	Buy
37	OrderID	ORD-10042
826	TradeAllocIndicator	0	Allocation not required
54	Side	1	Buy
37	OrderID	ORD-10042
826	TradeAllocIndicator	0	Allocation not required
10	CheckSum	088

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
0	Allocation not required	ALLOCATION_NOT_REQUIRED
1	Allocation required (give up trade) allocation information not provided (incomplete)	ALLOCATION_REQUIRED
2	Use allocation provided with the trade	USE_ALLOCATION_PROVIDED_WITH_THE_TRADE

Where tag 826 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
TradeCaptureReport	AE	Optional	inside the TrdCapRptSideGrp component

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 826 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 tradeAllocIndicator = message.fields[826]?.raw;// e.g. "0" — Allocation not required// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(826)  ?.enumValues?.find((e) => e.value === tradeAllocIndicator)  ?.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