AllocAccount (FIX tag 79)

StringFIX 4.4FIX 4.2

AllocAccount (tag 79) is a String field defined in FIX 4.4 and FIX 4.2. It appears in 16 message types and is required in 1 of them.

At a glance

Tag: 79
Name: AllocAccount
Datatype: String
Dialects: FIX 4.4 and FIX 4.2
Messages: 16

What the specification says

Sub-account mnemonic

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

A real message using tag 79

OrderCancelReplaceRequest · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	151
35	MsgType	G	Order Cancel/Replace Request
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
41	OrigClOrdID	ORD-10041
11	ClOrdID	ORD-10042
78	NoAllocs2 entries	2	repeating group
79	AllocAccount	EXAMPLE
79	AllocAccount	EXAMPLE
54	Side	1	Buy
60	TransactTime	20240101-12:00:00.000
40	OrdType	1	Market
10	CheckSum	245

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 79 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
AllocationInstruction	J	Conditional	Optional	inside the AllocGrp component
AllocationInstructionAck	P	Conditional	—	inside the AllocAckGrp component
AllocationReport	AS	Conditional	—	inside the AllocGrp component
AllocationReportAck	AT	Conditional	—	inside the AllocAckGrp component
Confirmation	AK	Required	—	directly on the message body
ConfirmationRequest	BH	Optional	—	directly on the message body
CrossOrderCancelReplaceRequest	t	Conditional	—	inside SideCrossOrdModGrp › PreAllocGrp
MultilegOrderCancelReplace	AC	Conditional	—	inside the PreAllocMlegGrp component
NewOrderCross	s	Conditional	—	inside SideCrossOrdModGrp › PreAllocGrp
NewOrderList	E	Conditional	Optional	inside ListOrdGrp › PreAllocGrp
NewOrderMultileg	AB	Conditional	—	inside the PreAllocMlegGrp component
NewOrderSingle	D	Conditional	Optional	inside the PreAllocGrp component
OrderCancelReplaceRequest	G	Conditional	Optional	inside the PreAllocGrp component
SettlementInstructionRequest	AV	Optional	—	directly on the message body
SettlementInstructions	T	—	Required	directly on the message body
TradeCaptureReport	AE	Conditional	—	inside TrdCapRptSideGrp › TrdAllocGrp
TradeCaptureReportAck	AR	Conditional	—	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 79 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[79];field?.name;   // "AllocAccount"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