PartyRole (FIX tag 452)

intFIX 4.4

PartyRole (tag 452) is an int field defined in FIX 4.4. It appears in 44 message types, always optionally. It is an enumerated field with 37 defined values.

At a glance

Tag
452
Name
PartyRole
Datatype
int
Dialects
FIX 4.4
Messages
44
Valid values
37

What the specification says

Identifies the type or role of the PartyID (448) specified. See "Appendix 6-G – Use of <Parties> Component Block"

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

A real message using tag 452

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength153
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
453NoPartyIDs2 entries2repeating group
448PartyIDEXAMPLE
452PartyRole1Executing Firm (formerly FIX 4.2 ExecBroker)
448PartyIDEXAMPLE
452PartyRole1Executing Firm (formerly FIX 4.2 ExecBroker)
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
10CheckSum234
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.

Valid values

A value outside this list is not a parse error — the message still decodes — but validate() reports it as validate/value-not-in-enum.

ValueMeaningSymbolic name
1Executing Firm (formerly FIX 4.2 ExecBroker)EXECUTING_FIRM
2Broker of Credit (formerly FIX 4.2 BrokerOfCredit)BROKER_OF_CREDIT
3Client ID (formerly FIX 4.2 ClientID)CLIENT_ID
4Clearing Firm (formerly FIX 4.2 ClearingFirm)CLEARING_FIRM
5Investor IDINVESTOR_ID
6Introducing FirmINTRODUCING_FIRM
7Entering FirmENTERING_FIRM
8Locate/Lending Firm (for short-sales)LOCATE_LENDING_FIRM
9Fund manager Client ID (for CIV)FUND_MANAGER_CLIENT_ID
10Settlement Location (formerly FIX 4.2 SettlLocation)SETTLEMENT_LOCATION
11Order Origination Trader (associated with Order Origination Firm – e.g. trader who initiates/submits the order)ORDER_ORIGINATION_TRADER
12Executing Trader (associated with Executing Firm - actually executes)EXECUTING_TRADER
13Order Origination Firm (e.g. buyside firm)ORDER_ORIGINATION_FIRM
14Giveup Clearing Firm (firm to which trade is given up)GIVEUP_CLEARING_FIRM
15Correspondant Clearing FirmCORRESPONDANT_CLEARING_FIRM
16Executing SystemEXECUTING_SYSTEM
17Contra FirmCONTRA_FIRM
18Contra Clearing FirmCONTRA_CLEARING_FIRM
19Sponsoring FirmSPONSORING_FIRM
20Underlying Contra FirmUNDERLYING_CONTRA_FIRM
21Clearing OrganizationCLEARING_ORGANIZATION
22ExchangeEXCHANGE
24Customer AccountCUSTOMER_ACCOUNT
25Correspondent Clearing OrganizationCORRESPONDENT_CLEARING_ORGANIZATION
26Correspondent BrokerCORRESPONDENT_BROKER
27Buyer/Seller (Receiver/Deliverer)BUYER_SELLER
28CustodianCUSTODIAN
29IntermediaryINTERMEDIARY
30AgentAGENT
31Sub custodianSUB_CUSTODIAN
32BeneficiaryBENEFICIARY
33Interested partyINTERESTED_PARTY
34Regulatory bodyREGULATORY_BODY
35Liquidity providerLIQUIDITY_PROVIDER
36Entering TraderENTERING_TRADER
37Contra TraderCONTRA_TRADER
38Position AccountPOSITION_ACCOUNT

Where tag 452 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.

MessageMsgTypeRequirednessWhere in the message
AllocationInstructionJConditionalinside the Parties component
AllocationInstructionAckPConditionalinside the Parties component
AllocationReportASConditionalinside the Parties component
AllocationReportAckATConditionalinside the Parties component
AssignmentReportAWConditionalinside the Parties component
CollateralAssignmentAYConditionalinside the Parties component
CollateralInquiryBBConditionalinside the Parties component
CollateralInquiryAckBGConditionalinside the Parties component
CollateralReportBAConditionalinside the Parties component
CollateralRequestAXConditionalinside the Parties component
CollateralResponseAZConditionalinside the Parties component
ConfirmationAKConditionalinside the Parties component
CrossOrderCancelReplaceRequesttConditionalinside SideCrossOrdModGrp › Parties
CrossOrderCancelRequestuConditionalinside SideCrossOrdCxlGrp › Parties
ExecutionReport8Conditionalinside the Parties component
MassQuoteiConditionalinside the Parties component
MassQuoteAcknowledgementbConditionalinside the Parties component
MultilegOrderCancelReplaceACConditionalinside the Parties component
NewOrderCrosssConditionalinside SideCrossOrdModGrp › Parties
NewOrderListEConditionalinside ListOrdGrp › Parties
NewOrderMultilegABConditionalinside the Parties component
NewOrderSingleDConditionalinside the Parties component
OrderCancelReplaceRequestGConditionalinside the Parties component
OrderCancelRequestFConditionalinside the Parties component
OrderMassStatusRequestAFConditionalinside the Parties component
OrderStatusRequestHConditionalinside the Parties component
PositionMaintenanceReportAMConditionalinside the Parties component
PositionMaintenanceRequestALConditionalinside the Parties component
PositionReportAPConditionalinside the Parties component
QuoteSConditionalinside the Parties component
QuoteCancelZConditionalinside the Parties component
QuoteRequestRConditionalinside QuotReqGrp › Parties
QuoteRequestRejectAGConditionalinside QuotReqRjctGrp › Parties
QuoteResponseAJConditionalinside the Parties component
QuoteStatusReportAIConditionalinside the Parties component
QuoteStatusRequestaConditionalinside the Parties component
RegistrationInstructionsoConditionalinside the Parties component
RegistrationInstructionsResponsepConditionalinside the Parties component
RequestForPositionsANConditionalinside the Parties component
RequestForPositionsAckAOConditionalinside the Parties component
SettlementInstructionRequestAVConditionalinside the Parties component
SettlementInstructionsTConditionalinside SettlInstGrp › Parties
TradeCaptureReportAEConditionalinside TrdCapRptSideGrp › Parties
TradeCaptureReportRequestADConditionalinside the Parties 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 452 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 partyRole = message.fields[452]?.raw;// e.g. "1" — Executing Firm (formerly FIX 4.2 ExecBroker)// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(452)  ?.enumValues?.find((e) => e.value === partyRole)  ?.description;

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