SettlCurrency (FIX tag 120)

CurrencyFIX 4.4FIX 4.2

SettlCurrency (tag 120) is a Currency field defined in FIX 4.4 and FIX 4.2. It appears in 12 message types, always optionally.

At a glance

Tag
120
Name
SettlCurrency
Datatype
Currency (String)
Dialects
FIX 4.4 and FIX 4.2
Messages
12

What the specification says

Currency code of settlement denomination.

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

A real message using tag 120

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength119
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
120SettlCurrencyEUR
10CheckSum181
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 120 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.

MessageMsgTypeFIX 4.4FIX 4.2Where in the message
AllocationInstructionJConditionalOptionalinside the AllocGrp component
AllocationReportASConditionalinside the AllocGrp component
ConfirmationAKOptionaldirectly on the message body
CrossOrderCancelReplaceRequesttConditionalinside the SideCrossOrdModGrp component
ExecutionReport8OptionalOptionaldirectly on the message body
MultilegOrderCancelReplaceACConditionaldirectly on the message body
NewOrderCrosssConditionalinside the SideCrossOrdModGrp component
NewOrderListEOptionalOptionalinside the ListOrdGrp component
NewOrderMultilegABConditionaldirectly on the message body
NewOrderSingleDConditionalOptionaldirectly on the message body
OrderCancelReplaceRequestGConditionalOptionaldirectly on the message body
TradeCaptureReportAEConditionalinside the TrdCapRptSideGrp component

Wire format

A three-letter ISO 4217 code. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

Read tag 120 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[120];field?.name;   // "SettlCurrency"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

Other Currency 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