NoDlvyInst (FIX tag 85)

NumInGroupFIX 4.4FIX 4.2group counter

NoDlvyInst (tag 85) is a NumInGroup field defined in FIX 4.4 and FIX 4.2. It appears in 7 message types, always optionally. Its datatype is NumInGroup, which makes it a repeating-group counter: its value is the number of entries that follow, not a quantity in its own right.

At a glance

Tag: 85
Name: NoDlvyInst
Datatype: NumInGroup (int)
Dialects: FIX 4.4 and FIX 4.2
Messages: 7

What the specification says

FIX 4.4

Number of delivery instruction fields in repeating group. Note this field was removed in FIX 4.1 and reinstated in FIX 4.4.

FIX 4.2

Number of delivery instruction fields to follow No longer used. Included here for reference to prior versions.

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

A real message using tag 85

AllocationInstruction · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	162
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
75	TradeDate	20240101
78	NoAllocs1 entry	1	repeating group
79	AllocAccount	EXAMPLE
85	NoDlvyInst2 entries	2	repeating group
165	SettlInstSource	1	Broker’s Instructions
165	SettlInstSource	1	Broker’s Instructions
10	CheckSum	000

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 85 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	—	inside AllocGrp › SettlInstructionsData › DlvyInstGrp
AllocationReport	AS	Optional	—	inside AllocGrp › SettlInstructionsData › DlvyInstGrp
CollateralAssignment	AY	Optional	—	inside SettlInstructionsData › DlvyInstGrp
CollateralInquiry	BB	Optional	—	inside SettlInstructionsData › DlvyInstGrp
CollateralReport	BA	Optional	—	inside SettlInstructionsData › DlvyInstGrp
Confirmation	AK	Optional	—	inside SettlInstructionsData › DlvyInstGrp
SettlementInstructions	T	Optional	—	inside SettlInstGrp › SettlInstructionsData › DlvyInstGrp

Wire format

The number of entries in the repeating group that follows. The next field on the wire is the group's delimiter tag. @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 85 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);// NoDlvyInst is a group counter, so the entries live on message.groups —// NOT on message.fields. message.fields[85] is undefined.const entries = message.groups[85] ?? [];for (const entry of entries) {  // entry.fields is keyed by tag; entry.groups holds nested groups}

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