AllocAccount (FIX tag 79)

StringFIX 4.4FIX 4.2FIX 5.0 SP2

AllocAccount (tag 79) is a String field defined in FIX 4.4, FIX 4.2 and FIX 5.0 SP2. 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, FIX 4.2 and FIX 5.0 SP2
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
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength151
35MsgTypeGOrder Cancel/Replace Request
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
41OrigClOrdIDORD-10041
11ClOrdIDORD-10042
78NoAllocs2 entries2repeating group
79AllocAccountEXAMPLE
79AllocAccountEXAMPLE
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
10CheckSum245
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.

MessageMsgTypeFIX 4.4FIX 4.2FIX 5.0 SP2Where in the message
AllocationInstructionJConditionalOptionalOptionalinside the AllocGrp component
AllocationInstructionAckPConditional—Optionalinside the AllocAckGrp component
AllocationInstructionAlertBM——Optionalinside the AllocGrp component
AllocationReportASConditional—Optionalinside the AllocGrp component
AllocationReportAckATConditional—Optionalinside the AllocAckGrp component
ConfirmationAKRequired—Requireddirectly on the message body
ConfirmationRequestBHOptional—Optionaldirectly on the message body
CrossOrderCancelReplaceRequesttConditional—Optionalinside SideCrossOrdModGrp › PreAllocGrp
ExecutionReport8——Optionalinside the PreAllocGrp component
MultilegOrderCancelReplaceACConditional—Optionalinside the PreAllocMlegGrp component
NewOrderCrosssConditional—Optionalinside SideCrossOrdModGrp › PreAllocGrp
NewOrderListEConditionalOptionalOptionalinside ListOrdGrp › PreAllocGrp
NewOrderMultilegABConditional—Optionalinside the PreAllocMlegGrp component
NewOrderSingleDConditionalOptionalOptionalinside the PreAllocGrp component
OrderCancelReplaceRequestGConditionalOptionalOptionalinside the PreAllocGrp component
SettlementInstructionRequestAVOptional—Optionaldirectly on the message body
SettlementInstructionsT—Required—directly on the message body
TradeCaptureReportAEConditional—Optionalinside TrdCapRptSideGrp › TrdAllocGrp
TradeCaptureReportAckARConditional—Optionalinside 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

Other String fields

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