UnderlyingSettlPrice (FIX tag 732)

PriceFIX 4.4FIX 5.0 SP2

UnderlyingSettlPrice (tag 732) is a Price field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 2 message types and is required in 2 of them.

At a glance

Tag: 732
Name: UnderlyingSettlPrice
Datatype: Price (float)
Dialects: FIX 4.4 and FIX 5.0 SP2
Messages: 2

What the specification says

FIX 4.4

Underlying security’s SettlPrice. See SettlPrice (730) field for description

FIX 5.0 SP2

Underlying security's SettlPrice.

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

A real message using tag 732

PositionReport · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	210
35	MsgType	AP	Position Report
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
721	PosMaintRptID	EXAMPLE
728	PosReqResult	0	Valid Request
715	ClearingBusinessDate	20240101
1	Account	ACCT-11223
581	AccountType	1	Account is carried on customer Side of Books
730	SettlPrice	1.09210
731	SettlPriceType	1	Final
734	PriorSettlPrice	1.09210
711	NoUnderlyings2 entries	2	repeating group
311	UnderlyingSymbol	EXAMPLE
732	UnderlyingSettlPrice	1.09210
733	UnderlyingSettlPriceType	1
311	UnderlyingSymbol	EXAMPLE
732	UnderlyingSettlPrice	1.09210
733	UnderlyingSettlPriceType	1
10	CheckSum	011

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 732 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 5.0 SP2	Where in the message
AssignmentReport	AW	Required	Optional	directly on the message body
PositionReport	AP	Required	Optional	inside the PosUndInstrmtGrp component

Wire format

A decimal price. Precision is a venue convention, not a protocol rule, so compare the raw string when exactness matters. @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 732 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[732];field?.name;   // "UnderlyingSettlPrice"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