LegAllocSettlCurrency (FIX tag 1367)

CurrencyFIX 5.0 SP2

LegAllocSettlCurrency (tag 1367) is a Currency field defined in FIX 5.0 SP2. It appears in 3 message types, always optionally.

At a glance

Tag: 1367
Name: LegAllocSettlCurrency
Datatype: Currency (String)
Dialects: FIX 5.0 SP2
Messages: 3

What the specification says

Identifies settlement currency for the leg level allocation.

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

A real message using tag 1367

ExecutionReport · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	189
35	MsgType	8	ExecutionReport
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
555	NoLegs1 entry	1	repeating group
600	LegSymbol	EXAMPLE
670	NoLegAllocs2 entries	2	repeating group
671	LegAllocAccount	EXAMPLE
1367	LegAllocSettlCurrency	EUR
671	LegAllocAccount	EXAMPLE
1367	LegAllocSettlCurrency	EUR
10	CheckSum	095

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 5.0 SP2 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Where tag 1367 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
ExecutionReport	8	Optional	inside InstrmtLegExecGrp › LegPreAllocGrp
MultilegOrderCancelReplace	AC	Optional	inside LegOrdGrp › LegPreAllocGrp
NewOrderMultileg	AB	Optional	inside LegOrdGrp › LegPreAllocGrp

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 1367 in TypeScript

decode.tsts

import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[1367];field?.name;   // "LegAllocSettlCurrency"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

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-fix50sp2

Try the decoder Source on GitHub