SettlCurrFxRateCalc (FIX tag 156)

charFIX 4.4FIX 4.2

SettlCurrFxRateCalc (tag 156) is a char field defined in FIX 4.4 and FIX 4.2. It appears in 8 message types, always optionally. It is an enumerated field with 2 defined values.

At a glance

Tag: 156
Name: SettlCurrFxRateCalc
Datatype: char
Dialects: FIX 4.4 and FIX 4.2
Messages: 8
Valid values: 2

What the specification says

FIX 4.4

Specifies whether or not SettlCurrFxRate(155) should be multiplied or divided

FIX 4.2

Specifies whether or not SettlCurrFxRate should be multiplied or divided.

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

A real message using tag 156

ExecutionReport · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	139
35	MsgType	8	Execution Report
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
37	OrderID	ORD-10042
17	ExecID	EXEC-88117
150	ExecType	0	New
39	OrdStatus	0	New
54	Side	1	Buy
151	LeavesQty	0
14	CumQty	1000000
6	AvgPx	1.09215
156	SettlCurrFxRateCalc	M	Multiply
10	CheckSum	070

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	Dialects
M	Multiply	MULTIPLY	FIX 4.4
D	Divide	DIVIDE	FIX 4.4

Where tag 156 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	Where in the message
AllocationInstruction	J	Optional	Optional	inside the AllocGrp component
AllocationReport	AS	Optional	—	inside the AllocGrp component
Confirmation	AK	Optional	—	directly on the message body
ExecutionReport	8	Optional	Optional	directly on the message body
Quote	S	Optional	—	directly on the message body
QuoteResponse	AJ	Optional	—	directly on the message body
QuoteStatusReport	AI	Optional	—	directly on the message body
TradeCaptureReport	AE	Optional	—	inside the TrdCapRptSideGrp 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 156 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 settlCurrFxRateCalc = message.fields[156]?.raw;// e.g. "M" — Multiply// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(156)  ?.enumValues?.find((e) => e.value === settlCurrFxRateCalc)  ?.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