NoStipulations (FIX tag 232)

NumInGroupFIX 4.4FIX 5.0 SP2group counter

NoStipulations (tag 232) is a NumInGroup field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 21 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: 232
Name: NoStipulations
Datatype: NumInGroup (int)
Dialects: FIX 4.4 and FIX 5.0 SP2
Messages: 21

What the specification says

FIX 4.4

Number of stipulation entries (Note tag # was reserved in FIX 4.1, added in FIX 4.3).

FIX 5.0 SP2

Number of stipulation entries

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

A real message using tag 232

NewOrderSingle · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	133
35	MsgType	D	Order – Single
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
11	ClOrdID	ORD-10042
54	Side	1	Buy
60	TransactTime	20240101-12:00:00.000
232	NoStipulations2 entries	2	repeating group
233	StipulationType	AMT	AMT (y/n)
233	StipulationType	AMT	AMT (y/n)
40	OrdType	1	Market
10	CheckSum	107

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 232 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 5.0 SP2	Where in the message
AllocationInstruction	J	Optional	Optional	inside the Stipulations component
AllocationInstructionAlert	BM	—	Optional	inside the Stipulations component
AllocationReport	AS	Optional	Optional	inside the Stipulations component
CollateralAssignment	AY	Optional	Optional	inside the Stipulations component
CollateralInquiry	BB	Optional	Optional	inside the Stipulations component
CollateralReport	BA	Optional	Optional	inside the Stipulations component
CollateralRequest	AX	Optional	Optional	inside the Stipulations component
CollateralResponse	AZ	Optional	Optional	inside the Stipulations component
Confirmation	AK	Optional	Optional	inside the Stipulations component
CrossOrderCancelReplaceRequest	t	Optional	Optional	inside the Stipulations component
ExecutionReport	8	Optional	Optional	inside the Stipulations component
IOI	6	Optional	Optional	inside the Stipulations component
NewOrderCross	s	Optional	Optional	inside the Stipulations component
NewOrderList	E	Optional	Optional	inside ListOrdGrp › Stipulations
NewOrderSingle	D	Optional	Optional	inside the Stipulations component
Quote	S	Optional	Optional	inside the Stipulations component
QuoteRequest	R	Optional	Optional	inside QuotReqGrp › Stipulations
QuoteRequestReject	AG	Optional	Optional	inside QuotReqRjctGrp › Stipulations
QuoteResponse	AJ	Optional	Optional	inside the Stipulations component
QuoteStatusReport	AI	Optional	Optional	inside the Stipulations component
SecurityDefinition	d	—	Optional	inside the Stipulations component
SecurityDefinitionRequest	c	—	Optional	inside the Stipulations component
SecurityDefinitionUpdateReport	BP	—	Optional	inside the Stipulations component
SecurityList	y	Optional	Optional	inside SecListGrp › Stipulations
SecurityListUpdateReport	BK	—	Optional	inside SecLstUpdRelSymGrp › Stipulations
TradeCaptureReport	AE	Optional	Optional	inside TrdCapRptSideGrp › Stipulations
TradeCaptureReportAck	AR	—	Optional	inside TrdCapRptAckSideGrp › Stipulations

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