LegAllocAcctIDSource (FIX tag 674)

StringFIX 4.4FIX 5.0 SP2

LegAllocAcctIDSource (tag 674) is a String field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 2 message types, always optionally.

At a glance

Tag
674
Name
LegAllocAcctIDSource
Datatype
String
Dialects
FIX 4.4 and FIX 5.0 SP2
Messages
2

What the specification says

FIX 4.4

The source of the LegAllocAccount(671) See AllocAcctIDSource(660) for description and valid values.

FIX 5.0 SP2

Identifies the source of the LegAllocAccount(671).

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

A real message using tag 674

NewOrderMultileg · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength184
35MsgTypeABNew Order - Multileg
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
54Side1Buy
555NoLegs1 entry1repeating group
600LegSymbolEXAMPLE
670NoLegAllocs2 entries2repeating group
671LegAllocAccountEXAMPLE
674LegAllocAcctIDSourceEXAMPLE
671LegAllocAccountEXAMPLE
674LegAllocAcctIDSourceEXAMPLE
60TransactTime20240101-12:00:00.000
40OrdType1Market
10CheckSum218
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 674 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 5.0 SP2Where in the message
ExecutionReport8Optionalinside InstrmtLegExecGrp › LegPreAllocGrp
MultilegOrderCancelReplaceACOptionalOptionalinside LegOrdGrp › LegPreAllocGrp
NewOrderMultilegABOptionalOptionalinside LegOrdGrp › LegPreAllocGrp

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 674 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[674];field?.name;   // "LegAllocAcctIDSource"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