RoundingModulus (FIX tag 469)

floatFIX 4.4

RoundingModulus (tag 469) is a float field defined in FIX 4.4. It appears in 18 message types, always optionally.

At a glance

Tag: 469
Name: RoundingModulus
Datatype: float
Dialects: FIX 4.4
Messages: 18

What the specification says

For CIV - a float value indicating the value to which rounding is required. i.e. 0 means round to a multiple of 0 units/shares; 0.5 means round to a multiple of 0.5 units/shares. The default, if RoundingDirection (468) is specified without RoundingModulus, is to round to a whole unit/share.

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

A real message using tag 469

NewOrderSingle · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	119
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
469	RoundingModulus	1.0
40	OrdType	1	Market
10	CheckSum	104

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 469 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	Requiredness	Where in the message
CrossOrderCancelReplaceRequest	t	Optional	inside SideCrossOrdModGrp › OrderQtyData
CrossOrderCancelRequest	u	Optional	inside SideCrossOrdCxlGrp › OrderQtyData
DontKnowTrade	Q	Optional	inside the OrderQtyData component
ExecutionReport	8	Optional	inside the OrderQtyData component
IOI	6	Optional	inside the OrderQtyData component
MultilegOrderCancelReplace	AC	Optional	inside the OrderQtyData component
NewOrderCross	s	Optional	inside SideCrossOrdModGrp › OrderQtyData
NewOrderList	E	Optional	inside ListOrdGrp › OrderQtyData
NewOrderMultileg	AB	Optional	inside the OrderQtyData component
NewOrderSingle	D	Optional	inside the OrderQtyData component
OrderCancelReplaceRequest	G	Optional	inside the OrderQtyData component
OrderCancelRequest	F	Optional	inside the OrderQtyData component
Quote	S	Optional	inside the OrderQtyData component
QuoteRequest	R	Optional	inside QuotReqGrp › OrderQtyData
QuoteRequestReject	AG	Optional	inside QuotReqRjctGrp › OrderQtyData
QuoteResponse	AJ	Optional	inside the OrderQtyData component
QuoteStatusReport	AI	Optional	inside the OrderQtyData component
TradeCaptureReport	AE	Optional	inside the OrderQtyData 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 469 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[469];field?.name;   // "RoundingModulus"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

Try the decoder Source on GitHub