QuantityDate (FIX tag 976)

LocalMktDateFIX 5.0 SP2

QuantityDate (tag 976) is a LocalMktDate field defined in FIX 5.0 SP2. It appears in 5 message types, always optionally.

At a glance

Tag: 976
Name: QuantityDate
Datatype: LocalMktDate (String)
Format: YYYYMMDD
Dialects: FIX 5.0 SP2
Messages: 5

What the specification says

Date associated to the quantity that is being reported for the position.

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

A real message using tag 976

AdjustedPositionReport · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	137
35	MsgType	BL	AdjustedPositionReport
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
721	PosMaintRptID	EXAMPLE
715	ClearingBusinessDate	20240101
702	NoPositions2 entries	2	repeating group
703	PosType	ALC	Allocation Trade Qty
976	QuantityDate	20240101
703	PosType	ALC	Allocation Trade Qty
976	QuantityDate	20240101
10	CheckSum	010

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 976 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
AdjustedPositionReport	BL	Optional	inside the PositionQty component
AssignmentReport	AW	Optional	inside the PositionQty component
PositionMaintenanceReport	AM	Optional	inside the PositionQty component
PositionMaintenanceRequest	AL	Optional	inside the PositionQty component
PositionReport	AP	Optional	inside the PositionQty component

Wire format

A calendar date in the market's local timezone, with no time component and no offset. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

Read tag 976 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[976];field?.name;   // "QuantityDate"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