Side (FIX tag 54)

charFIX 4.4FIX 4.2

Side (tag 54) is a char field defined in FIX 4.4 and FIX 4.2. It appears in 36 message types and is required in 17 of them. It is an enumerated field with 16 defined values.

At a glance

Tag
54
Name
Side
Datatype
char
Dialects
FIX 4.4 and FIX 4.2
Messages
36
Valid values
16

What the specification says

Side of order

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

A real message using tag 54

Quote · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength80
35MsgTypeSQuote
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
117QuoteIDEXAMPLE
54Side1Buy
10CheckSum139
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 nameDialects
1BuyBUY / BuyFIX 4.4, FIX 4.2
2SellSELL / SellFIX 4.4, FIX 4.2
3Buy minusBUY_MINUS / BuyMinusFIX 4.4, FIX 4.2
4Sell plusSELL_PLUS / SellPlusFIX 4.4, FIX 4.2
5Sell shortSELL_SHORT / SellShortFIX 4.4, FIX 4.2
6Sell short exemptSELL_SHORT_EXEMPT / SellShortExemptFIX 4.4, FIX 4.2
7Undisclosed (valid for IOI and List Order messages only)UNDISCLOSED / UndisclosedFIX 4.4, FIX 4.2
8Cross (orders where counterparty is an exchange, valid for all messages except IOIs)CROSS / CrossFIX 4.4, FIX 4.2
9Cross shortCROSS_SHORT / CrossShortFIX 4.4, FIX 4.2
ACross short exemptCROSS_SHORT_EXEMPTFIX 4.4
B"As Defined" (for use with multileg instruments)AS_DEFINEDFIX 4.4
C"Opposite" (for use with multileg instruments)OPPOSITEFIX 4.4
DSubscribe (e.g. CIV)SUBSCRIBEFIX 4.4
ERedeem (e.g. CIV)REDEEMFIX 4.4
FLend (FINANCING - identifies direction of collateral)LENDFIX 4.4
GBorrow (FINANCING - identifies direction of collateral)BORROWFIX 4.4

Where tag 54 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
AllocationInstructionJRequiredRequireddirectly on the message body
AllocationReportASRequireddirectly on the message body
BidRequestkOptionalOptionalinside the BidCompReqGrp component
BidResponselOptionalOptionalinside the BidCompRspGrp component
CollateralAssignmentAYOptionaldirectly on the message body
CollateralInquiryBBOptionaldirectly on the message body
CollateralReportBAOptionaldirectly on the message body
CollateralRequestAXOptionaldirectly on the message body
CollateralResponseAZOptionaldirectly on the message body
ConfirmationAKRequireddirectly on the message body
CrossOrderCancelReplaceRequesttRequiredinside the SideCrossOrdModGrp component
CrossOrderCancelRequestuRequiredinside the SideCrossOrdCxlGrp component
DontKnowTradeQRequiredRequireddirectly on the message body
ExecutionReport8RequiredRequireddirectly on the message body
IOI6RequiredRequireddirectly on the message body
ListStrikePricemOptionalOptionalinside the UndInstrmtStrkPxGrp component
MultilegOrderCancelReplaceACRequireddirectly on the message body
NewOrderCrosssRequiredinside the SideCrossOrdModGrp component
NewOrderListERequiredRequiredinside the ListOrdGrp component
NewOrderMultilegABRequireddirectly on the message body
NewOrderSingleDRequiredRequireddirectly on the message body
OrderCancelReplaceRequestGRequiredRequireddirectly on the message body
OrderCancelRequestFRequiredRequireddirectly on the message body
OrderMassCancelReportrOptionaldirectly on the message body
OrderMassCancelRequestqOptionaldirectly on the message body
OrderMassStatusRequestAFOptionaldirectly on the message body
OrderStatusRequestHRequiredRequireddirectly on the message body
QuoteSConditionaldirectly on the message body
QuoteRequestROptionalOptionalinside the QuotReqGrp component
QuoteRequestRejectAGOptionalinside the QuotReqRjctGrp component
QuoteResponseAJOptionaldirectly on the message body
QuoteStatusReportAIOptionaldirectly on the message body
QuoteStatusRequestaOptionaldirectly on the message body
SecurityDefinitiondOptionaldirectly on the message body
SecurityDefinitionRequestcOptionaldirectly on the message body
SettlementInstructionRequestAVOptionaldirectly on the message body
SettlementInstructionsTOptionalOptionalinside the SettlInstGrp component
TradeCaptureReportAERequiredinside the TrdCapRptSideGrp component
TradeCaptureReportRequestADOptionaldirectly on the message body

Wire format

A single character. Most char fields are enumerated, so the value is one of a fixed set rather than arbitrary text. @boarteam/fix keeps the value as a string and, for enumerated fields, reports validate/value-not-in-enum when it is not a defined value.

Read tag 54 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 side = message.fields[54]?.raw;// e.g. "1" — Buy// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(54)  ?.enumValues?.find((e) => e.value === side)  ?.description;

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