SettlCurrency (FIX tag 120)
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
| 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 | |
| 40 | OrdType | 1 | Market |
| 120 | SettlCurrency | EUR | |
| 10 | CheckSum | 181 |
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.
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.
| Message | MsgType | FIX 4.4 | FIX 4.2 | Where in the message |
|---|---|---|---|---|
| AllocationInstruction | J | Conditional | Optional | inside the AllocGrp component |
| AllocationReport | AS | Conditional | — | inside the AllocGrp component |
| Confirmation | AK | Optional | — | directly on the message body |
| CrossOrderCancelReplaceRequest | t | Conditional | — | inside the SideCrossOrdModGrp component |
| ExecutionReport | 8 | Optional | Optional | directly on the message body |
| MultilegOrderCancelReplace | AC | Conditional | — | directly on the message body |
| NewOrderCross | s | Conditional | — | inside the SideCrossOrdModGrp component |
| NewOrderList | E | Optional | Optional | inside the ListOrdGrp component |
| NewOrderMultileg | AB | Conditional | — | directly on the message body |
| NewOrderSingle | D | Conditional | Optional | directly on the message body |
| OrderCancelReplaceRequest | G | Conditional | Optional | directly on the message body |
| TradeCaptureReport | AE | Conditional | — | inside 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
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 stringOther Currency fields
- 138MiscFeeCurr
- 220BenchmarkCurveCurrency
- 15Currency
- 318UnderlyingCurrency
- 478CashDistribCurr
- 479CommCurrency
- 521ContAmtCurr
- 556LegCurrency
- 675LegSettlCurrency
- 676LegBenchmarkCurveCurrency
- 736AllocSettlCurrency
- 767AllowableOneSidednessCurr
- 918AgreementCurrency
- 941UnderlyingStrikeCurrency
- 942LegStrikeCurrency
- 947StrikeCurrency
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