AllocText (FIX tag 161)

StringFIX 4.4FIX 4.2

AllocText (tag 161) is a String field defined in FIX 4.4 and FIX 4.2. It appears in 4 message types, always optionally.

At a glance

Tag
161
Name
AllocText
Datatype
String
Dialects
FIX 4.4 and FIX 4.2
Messages
4

What the specification says

FIX 4.4

Free format text related to a specific AllocAccount (79).

FIX 4.2

Free format text related to a specific AllocAccount.

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

A real message using tag 161

AllocationInstruction · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength180
35MsgTypeJAllocation Instruction
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
70AllocIDEXAMPLE
71AllocTransType0New
626AllocType1Calculated (includes MiscFees and NetMoney)
857AllocNoOrdersType0Not specified
54Side1Buy
53Quantity1000000
6AvgPx1.09215
75TradeDate20240101
78NoAllocs2 entries2repeating group
79AllocAccountEXAMPLE
161AllocTextEXAMPLE
79AllocAccountEXAMPLE
161AllocTextEXAMPLE
10CheckSum140
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 161 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.2Where in the message
AllocationInstructionJOptionalOptionalinside the AllocGrp component
AllocationInstructionAckPOptionalinside the AllocAckGrp component
AllocationReportASOptionalinside the AllocGrp component
AllocationReportAckATOptionalinside the AllocAckGrp 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 161 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[161];field?.name;   // "AllocText"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