ContractMultiplier (FIX tag 231)

floatFIX 4.4FIX 4.2FIX 5.0 SP2

ContractMultiplier (tag 231) is a float field defined in FIX 4.4, FIX 4.2 and FIX 5.0 SP2. It appears in 59 message types, always optionally.

At a glance

Tag
231
Name
ContractMultiplier
Datatype
float
Dialects
FIX 4.4, FIX 4.2 and FIX 5.0 SP2
Messages
59

What the specification says

FIX 4.4

Specifies the ratio or multiply factor to convert from "nominal" units (e.g. contracts) to total units (e.g. shares) (e.g. 1.0, 100, 1000, etc). Applicable For Fixed Income, Convertible Bonds, Derivatives, etc. In general quantities for all classes should be expressed in the basic unit of the instrument, e.g. shares for equities, nominal or par amount for bonds, currency for foreign exchange. When quantity is expressed in contracts, e.g. financing transactions and bond trade reporting, ContractMultiplier should contain the number of units in one contract and can be omitted if the multiplier is the default amount for the instrument, i.e. 1,000 par of bonds, 1,000,000 par for financing transactions.

FIX 4.2

Specifies the ratio or multiply factor to convert from contracts to shares (e.g. 1.0, 100, 1000, etc). Applicable For Fixed Income, Convertible Bonds, Derivatives, etc. Note: If used, quantities should be expressed in the "nominal" (e.g. contracts vs. shares) amount.

FIX 5.0 SP2

Specifies the ratio or multiply factor to convert from "nominal" units (e.g. contracts) to total units (e.g. shares) (e.g. 1.0, 100, 1000, etc). Applicable For Fixed Income, Convertible Bonds, Derivatives, etc.

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

A real message using tag 231

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength119
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
231ContractMultiplier1.0
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
10CheckSum091
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 231 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.2FIX 5.0 SP2Where in the message
AdjustedPositionReportBLOptionalinside InstrmtGrp › Instrument
Advertisement7OptionalOptionalOptionalinside the Instrument component
AllocationInstructionJOptionalOptionalOptionalinside the Instrument component
AllocationInstructionAlertBMOptionalinside the Instrument component
AllocationReportASOptionalOptionalinside the Instrument component
AssignmentReportAWOptionalOptionalinside the Instrument component
CollateralAssignmentAYOptionalOptionalinside the Instrument component
CollateralInquiryBBOptionalOptionalinside the Instrument component
CollateralInquiryAckBGOptionalOptionalinside the Instrument component
CollateralReportBAOptionalOptionalinside the Instrument component
CollateralRequestAXOptionalOptionalinside the Instrument component
CollateralResponseAZOptionalOptionalinside the Instrument component
ConfirmationAKOptionalOptionalinside the Instrument component
ContraryIntentionReportBOOptionalinside the Instrument component
CrossOrderCancelReplaceRequesttOptionalOptionalinside the Instrument component
CrossOrderCancelRequestuOptionalOptionalinside the Instrument component
DerivativeSecurityListAAOptionalOptionalinside RelSymDerivSecGrp › Instrument
DerivativeSecurityListUpdateReportBROptionalinside RelSymDerivSecUpdGrp › Instrument
DontKnowTradeQOptionalOptionalOptionalinside the Instrument component
EmailCOptionalOptionalOptionalinside InstrmtGrp › Instrument
ExecutionAcknowledgementBNOptionalinside the Instrument component
ExecutionReport8OptionalOptionalOptionalinside the Instrument component
IOI6OptionalOptionalOptionalinside the Instrument component
ListStrikePricemOptionalOptionalOptionalinside InstrmtStrkPxGrp › Instrument
MarketDataIncrementalRefreshXOptionalOptionalOptionalinside MDIncGrp › Instrument
MarketDataRequestVOptionalOptionalOptionalinside InstrmtMDReqGrp › Instrument
MarketDataSnapshotFullRefreshWOptionalOptionalOptionalinside the Instrument component
MassQuoteiOptionalOptionalOptionalinside QuotSetGrp › QuotEntryGrp › Instrument
MassQuoteAcknowledgementbOptionalOptionalOptionalinside QuotSetAckGrp › QuotEntryAckGrp › Instrument
MultilegOrderCancelReplaceACOptionalOptionalinside the Instrument component
NewOrderCrosssOptionalOptionalinside the Instrument component
NewOrderListEOptionalOptionalOptionalinside ListOrdGrp › Instrument
NewOrderMultilegABOptionalOptionalinside the Instrument component
NewOrderSingleDOptionalOptionalOptionalinside the Instrument component
NewsBOptionalOptionalOptionalinside InstrmtGrp › Instrument
OrderCancelReplaceRequestGOptionalOptionalOptionalinside the Instrument component
OrderCancelRequestFOptionalOptionalOptionalinside the Instrument component
OrderMassActionReportBZOptionalinside the Instrument component
OrderMassActionRequestCAOptionalinside the Instrument component
OrderMassCancelReportrOptionalOptionalinside the Instrument component
OrderMassCancelRequestqOptionalOptionalinside the Instrument component
OrderMassStatusRequestAFOptionalOptionalinside the Instrument component
OrderStatusRequestHOptionalOptionalOptionalinside the Instrument component
PositionMaintenanceReportAMOptionalOptionalinside the Instrument component
PositionMaintenanceRequestALOptionalOptionalinside the Instrument component
PositionReportAPOptionalOptionalinside the Instrument component
QuoteSOptionalOptionalOptionalinside the Instrument component
QuoteCancelZOptionalOptionalOptionalinside QuotCxlEntriesGrp › Instrument
QuoteRequestROptionalOptionalOptionalinside QuotReqGrp › Instrument
QuoteRequestRejectAGOptionalOptionalinside QuotReqRjctGrp › Instrument
QuoteResponseAJOptionalOptionalinside the Instrument component
QuoteStatusReportAIOptionalOptionalinside the Instrument component
QuoteStatusRequestaOptionalOptionalOptionalinside the Instrument component
RFQRequestAHOptionalOptionalinside RFQReqGrp › Instrument
RequestForPositionsANOptionalOptionalinside the Instrument component
RequestForPositionsAckAOOptionalOptionalinside the Instrument component
SecurityDefinitiondOptionalOptionalOptionalinside the Instrument component
SecurityDefinitionRequestcOptionalOptionalOptionalinside the Instrument component
SecurityDefinitionUpdateReportBPOptionalinside the Instrument component
SecurityListyOptionalOptionalinside SecListGrp › Instrument
SecurityListRequestxOptionalOptionalinside the Instrument component
SecurityListUpdateReportBKOptionalinside SecLstUpdRelSymGrp › Instrument
SecurityStatusfOptionalOptionalOptionalinside the Instrument component
SecurityStatusRequesteOptionalOptionalOptionalinside the Instrument component
SettlementObligationReportBQOptionalinside SettlObligationInstructions › Instrument
StreamAssignmentReportCDOptionalinside StrmAsgnRptGrp › StrmAsgnRptInstrmtGrp › Instrument
StreamAssignmentRequestCCOptionalinside StrmAsgnReqGrp › StrmAsgnReqInstrmtGrp › Instrument
TradeCaptureReportAEOptionalOptionalinside the Instrument component
TradeCaptureReportAckAROptionalOptionalinside the Instrument component
TradeCaptureReportRequestADOptionalOptionalinside the Instrument component
TradeCaptureReportRequestAckAQOptionalOptionalinside the Instrument component
TradingSessionStatushOptionalinside the Instrument component

Wire format

A decimal number. The wire form keeps its trailing zeros, which is why decoders expose the raw string alongside the parsed number. @boarteam/fix parses the value as a number and reports parse/invalid-float when it does not lex as one; the raw string is kept so precision and trailing zeros are never lost.

Read tag 231 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[231];field?.name;   // "ContractMultiplier"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a number

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