AllocAcctIDSource (FIX tag 661)

intFIX 4.4FIX 5.0 SP2

AllocAcctIDSource (tag 661) is an int field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 16 message types, always optionally.

At a glance

Tag
661
Name
AllocAcctIDSource
Datatype
int
Dialects
FIX 4.4 and FIX 5.0 SP2
Messages
16

What the specification says

FIX 4.4

Used to identify the source of the AllocAccount (79) code. See AcctIDSource (660) for valid values.

FIX 5.0 SP2

Used to identify the source of the AllocAccount (79) code.

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

A real message using tag 661

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength150
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
78NoAllocs2 entries2repeating group
79AllocAccountEXAMPLE
661AllocAcctIDSource1
79AllocAccountEXAMPLE
661AllocAcctIDSource1
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
10CheckSum094
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 661 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
AllocationInstructionJConditionalOptionalinside the AllocGrp component
AllocationInstructionAckPConditionalOptionalinside the AllocAckGrp component
AllocationInstructionAlertBMOptionalinside the AllocGrp component
AllocationReportASConditionalOptionalinside the AllocGrp component
AllocationReportAckATConditionalOptionalinside the AllocAckGrp component
ConfirmationAKOptionalOptionaldirectly on the message body
ConfirmationRequestBHOptionalOptionaldirectly on the message body
CrossOrderCancelReplaceRequesttConditionalOptionalinside SideCrossOrdModGrp › PreAllocGrp
ExecutionReport8Optionalinside the PreAllocGrp component
MultilegOrderCancelReplaceACConditionalOptionalinside the PreAllocMlegGrp component
NewOrderCrosssConditionalOptionalinside SideCrossOrdModGrp › PreAllocGrp
NewOrderListEConditionalOptionalinside ListOrdGrp › PreAllocGrp
NewOrderMultilegABConditionalOptionalinside the PreAllocMlegGrp component
NewOrderSingleDConditionalOptionalinside the PreAllocGrp component
OrderCancelReplaceRequestGConditionalOptionalinside the PreAllocGrp component
SettlementInstructionRequestAVConditionalOptionaldirectly on the message body
TradeCaptureReportAEConditionalOptionalinside TrdCapRptSideGrp › TrdAllocGrp
TradeCaptureReportAckARConditionalOptionalinside the TrdAllocGrp 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 661 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[661];field?.name;   // "AllocAcctIDSource"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a number

Other int 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