AvgPxPrecision (FIX tag 74)

intFIX 4.4FIX 4.2

AvgPxPrecision (tag 74) is an int field defined in FIX 4.4 and FIX 4.2. It appears in 3 message types, always optionally. FIX 4.2 calls this field AvgPrxPrecision; the tag number is unchanged, so the two are the same field on the wire.

Also known as AvgPrxPrecision

FIX 4.2 calls tag 74 AvgPrxPrecision. It is the same field on the wire — only the name changed — so a message encoded by either side interoperates.

At a glance

Tag: 74
Name: AvgPxPrecision
Datatype: int
Dialects: FIX 4.4 and FIX 4.2
Messages: 3

What the specification says

Indicates number of decimal places to be used for average pricing. Absence of this field indicates that default precision arranged by the broker/institution is to be used.

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

A real message using tag 74

AllocationInstruction · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	134
35	MsgType	J	Allocation Instruction
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
70	AllocID	EXAMPLE
71	AllocTransType	0	New
626	AllocType	1	Calculated (includes MiscFees and NetMoney)
857	AllocNoOrdersType	0	Not specified
54	Side	1	Buy
53	Quantity	1000000
6	AvgPx	1.09215
74	AvgPxPrecision	1
75	TradeDate	20240101
10	CheckSum	078

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 74 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	Optional	Optional	directly on the message body
AllocationReport	AS	Optional	—	directly on the message body
Confirmation	AK	Optional	—	directly on the message body

Wire format

A whole number, optionally signed. Leading zeros are legal on the wire and are preserved in the raw value. @boarteam/fix parses the value as a number and reports parse/invalid-int when it does not lex as one; the raw string is kept either way.

Read tag 74 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[74];field?.name;   // "AvgPxPrecision"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-fix44

Try the decoder Source on GitHub