LegSettlCurrency (FIX tag 675)

CurrencyFIX 4.4FIX 5.0 SP2

LegSettlCurrency (tag 675) is a Currency field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 2 message types, always optionally.

At a glance

Tag
675
Name
LegSettlCurrency
Datatype
Currency (String)
Dialects
FIX 4.4 and FIX 5.0 SP2
Messages
2

What the specification says

FIX 4.4

Identifies settlement currency for the Leg. See SettlCurrency(120) for description and valid values

FIX 5.0 SP2

Identifies settlement currency for the Leg.

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

A real message using tag 675

NewOrderMultileg · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength176
35MsgTypeABNew Order - Multileg
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
54Side1Buy
555NoLegs1 entry1repeating group
600LegSymbolEXAMPLE
670NoLegAllocs2 entries2repeating group
671LegAllocAccountEXAMPLE
675LegSettlCurrencyEUR
671LegAllocAccountEXAMPLE
675LegSettlCurrencyEUR
60TransactTime20240101-12:00:00.000
40OrdType1Market
10CheckSum157
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 675 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 5.0 SP2Where in the message
ExecutionReport8Optionalinside the InstrmtLegExecGrp component
MultilegOrderCancelReplaceACOptionalOptionalinside LegOrdGrp › LegPreAllocGrp
NewOrderMultilegABOptionalOptionalinside LegOrdGrp › LegPreAllocGrp
TradeCaptureReportAEOptionalinside the TrdInstrmtLegGrp component
TradeCaptureReportAckAROptionalinside the TrdInstrmtLegGrp 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 675 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[675];field?.name;   // "LegSettlCurrency"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