CashOrderQty (FIX tag 152)

QtyFIX 4.4FIX 4.2FIX 5.0 SP2

CashOrderQty (tag 152) is a Qty field defined in FIX 4.4, FIX 4.2 and FIX 5.0 SP2. It appears in 18 message types, always optionally.

At a glance

Tag: 152
Name: CashOrderQty
Datatype: Qty (float)
Dialects: FIX 4.4, FIX 4.2 and FIX 5.0 SP2
Messages: 18

What the specification says

FIX 4.4

Specifies the approximate order quantity desired in total monetary units vs. as tradeable units (e.g. number of shares). The broker or fund manager (for CIV orders) would be responsible for converting and calculating a tradeable unit (e.g. share) quantity (OrderQty (38)) based upon this amount to be used for the actual order and subsequent messages.

FIX 4.2

Specifies the approximate order quantity desired in total monetary units vs. as a number of shares. The broker would be responsible for converting and calculating a share quantity (OrderQty) based upon this amount to be used for the actual order and subsequent messages.

FIX 5.0 SP2

Specifies the approximate order quantity desired in total monetary units vs. as tradeable units (e.g. number of shares). The broker or fund manager (for CIV orders) would be responsible for converting and calculating a tradeable unit (e.g. share) quantity (OrderQty (38)) based upon this amount to be used for the actual order and subsequent messages.

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

A real message using tag 152

NewOrderSingle · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	123
35	MsgType	D	Order – Single
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
11	ClOrdID	ORD-10042
54	Side	1	Buy
60	TransactTime	20240101-12:00:00.000
152	CashOrderQty	1000000
40	OrdType	1	Market
10	CheckSum	026

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 152 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.

Message	MsgType	FIX 4.4	FIX 4.2	FIX 5.0 SP2	Where in the message
CrossOrderCancelReplaceRequest	t	Conditional	—	Optional	inside SideCrossOrdModGrp › OrderQtyData
CrossOrderCancelRequest	u	Conditional	—	Optional	inside SideCrossOrdCxlGrp › OrderQtyData
DontKnowTrade	Q	Conditional	Optional	Optional	inside the OrderQtyData component
ExecutionAcknowledgement	BN	—	—	Optional	inside the OrderQtyData component
ExecutionReport	8	Conditional	Optional	Optional	inside the OrderQtyData component
IOI	6	Conditional	—	Optional	inside the OrderQtyData component
MultilegOrderCancelReplace	AC	Conditional	—	Optional	inside the OrderQtyData component
NewOrderCross	s	Conditional	—	Optional	inside SideCrossOrdModGrp › OrderQtyData
NewOrderList	E	Conditional	Optional	Optional	inside ListOrdGrp › OrderQtyData
NewOrderMultileg	AB	Conditional	—	Optional	inside the OrderQtyData component
NewOrderSingle	D	Conditional	Optional	Optional	inside the OrderQtyData component
OrderCancelReplaceRequest	G	Conditional	Optional	Optional	inside the OrderQtyData component
OrderCancelRequest	F	Conditional	Optional	Optional	inside the OrderQtyData component
Quote	S	Conditional	—	Optional	inside the OrderQtyData component
QuoteRequest	R	Conditional	—	Optional	inside QuotReqGrp › OrderQtyData
QuoteRequestReject	AG	Conditional	—	Optional	inside QuotReqRjctGrp › OrderQtyData
QuoteResponse	AJ	Conditional	—	Optional	inside the OrderQtyData component
QuoteStatusReport	AI	Conditional	—	Optional	inside the OrderQtyData component
TradeCaptureReport	AE	Conditional	—	Optional	inside the OrderQtyData component
TradeCaptureReportAck	AR	—	—	Optional	inside TrdCapRptAckSideGrp › TradeReportOrderDetail › OrderQtyData

Wire format

A decimal quantity. Fractional quantities are legal, which is why this is a float family rather than an integer. @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 152 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[152];field?.name;   // "CashOrderQty"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a number

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

Try the decoder Source on GitHub