RoundingDirection (FIX tag 468)

charFIX 4.4

RoundingDirection (tag 468) is a char field defined in FIX 4.4. It appears in 18 message types, always optionally. It is an enumerated field with 3 defined values.

At a glance

Tag: 468
Name: RoundingDirection
Datatype: char
Dialects: FIX 4.4
Messages: 18
Valid values: 3

What the specification says

Specifies which direction to round For CIV – indicates whether or not the quantity of shares/units is to be rounded and in which direction where CashOrdQty (52) or (for CIV only) OrderPercent (56) are specified on an order. The default is for rounding to be at the discretion of the executing broker or fund manager. e.g. for an order specifying CashOrdQty or OrderPercent if the calculated number of shares/units was 325.76 and RoundingModulus (469) was 0 – "round down" would give 320 units, "round up" would give 330 units and "round to nearest" would give 320 units.

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

A real message using tag 468

NewOrderSingle · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	117
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
468	RoundingDirection	0	Round to nearest
40	OrdType	1	Market
10	CheckSum	006

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.

Value	Meaning	Symbolic name
0	Round to nearest	ROUND_TO_NEAREST
1	Round down	ROUND_DOWN
2	Round up	ROUND_UP

Where tag 468 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 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 468 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 roundingDirection = message.fields[468]?.raw;// e.g. "0" — Round to nearest// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(468)  ?.enumValues?.find((e) => e.value === roundingDirection)  ?.description;

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