LegGrossTradeAmt (FIX tag 1075)

AmtFIX 5.0 SP2

LegGrossTradeAmt (tag 1075) is an Amt field defined in FIX 5.0 SP2. It appears in 3 message types, always optionally.

At a glance

Tag: 1075
Name: LegGrossTradeAmt
Datatype: Amt (float)
Dialects: FIX 5.0 SP2
Messages: 3

What the specification says

The gross trade amount of the leg. For FX Futures this is used to express the notional value of a fill when LegLastQty and other quantity fields are express in terms of contract size.

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

A real message using tag 1075

ExecutionReport · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	183
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	NoLegs2 entries	2	repeating group
600	LegSymbol	EXAMPLE
1075	LegGrossTradeAmt	125000.00
600	LegSymbol	EXAMPLE
1075	LegGrossTradeAmt	125000.00
10	CheckSum	233

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 1075 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 the InstrmtLegExecGrp component
TradeCaptureReport	AE	Optional	inside the TrdInstrmtLegGrp component
TradeCaptureReportAck	AR	Optional	inside the TrdInstrmtLegGrp component

Wire format

A decimal monetary amount, in the currency named by the message's currency field. @boarteam/fix parses the value as a number and reports parse/invalid-float when it does not lex as one; the raw string is kept so precision and trailing zeros are never lost.

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

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