NoSettlOblig (FIX tag 1165)

NumInGroupFIX 5.0 SP2group counter

NoSettlOblig (tag 1165) is a NumInGroup field defined in FIX 5.0 SP2. It appears in 1 message type, 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: 1165
Name: NoSettlOblig
Datatype: NumInGroup (int)
Dialects: FIX 5.0 SP2
Messages: 1

What the specification says

Number of settlement obligations

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

A real message using tag 1165

SettlementObligationReport · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	103
35	MsgType	BQ	SettlementObligationReport
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
1160	SettlObligMsgID	EXAMPLE
1159	SettlObligMode	1	Preliminary
1165	NoSettlOblig2 entries	2	repeating group
430	NetGrossInd	1	Net
430	NetGrossInd	1	Net
10	CheckSum	036

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 1165 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
SettlementObligationReport	BQ	Optional	inside the SettlObligationInstructions component

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 1165 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);// NoSettlOblig is a group counter, so the entries live on message.groups —// NOT on message.fields. message.fields[1165] is undefined.const entries = message.groups[1165] ?? [];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-fix50sp2

Try the decoder Source on GitHub