StipulationValue (FIX tag 234)

StringFIX 4.4

StipulationValue (tag 234) is a String field defined in FIX 4.4. It appears in 21 message types, always optionally.

At a glance

Tag
234
Name
StipulationValue
Datatype
String
Dialects
FIX 4.4
Messages
21

What the specification says

For Fixed Income. Value of stipulation. The expression can be an absolute single value or a combination of values and logical operators: < value > value <= value >= value value value – value2 value OR value2 value AND value2 YES NO (Note tag # was reserved in FIX 4.1, added in FIX 4.3)

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

A real message using tag 234

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength157
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
54Side1Buy
60TransactTime20240101-12:00:00.000
232NoStipulations2 entries2repeating group
233StipulationTypeAMTAMT (y/n)
234StipulationValueEXAMPLE
233StipulationTypeAMTAMT (y/n)
234StipulationValueEXAMPLE
40OrdType1Market
10CheckSum055
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 234 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.

MessageMsgTypeRequirednessWhere in the message
AllocationInstructionJOptionalinside the Stipulations component
AllocationReportASOptionalinside the Stipulations component
CollateralAssignmentAYOptionalinside the Stipulations component
CollateralInquiryBBOptionalinside the Stipulations component
CollateralReportBAOptionalinside the Stipulations component
CollateralRequestAXOptionalinside the Stipulations component
CollateralResponseAZOptionalinside the Stipulations component
ConfirmationAKOptionalinside the Stipulations component
CrossOrderCancelReplaceRequesttOptionalinside the Stipulations component
ExecutionReport8Optionalinside the Stipulations component
IOI6Optionalinside the Stipulations component
NewOrderCrosssOptionalinside the Stipulations component
NewOrderListEOptionalinside ListOrdGrp › Stipulations
NewOrderSingleDOptionalinside the Stipulations component
QuoteSOptionalinside the Stipulations component
QuoteRequestROptionalinside QuotReqGrp › Stipulations
QuoteRequestRejectAGOptionalinside QuotReqRjctGrp › Stipulations
QuoteResponseAJOptionalinside the Stipulations component
QuoteStatusReportAIOptionalinside the Stipulations component
SecurityListyOptionalinside SecListGrp › Stipulations
TradeCaptureReportAEOptionalinside TrdCapRptSideGrp › Stipulations

Wire format

Free-form text. Any byte except the SOH separator is legal, so values are not trimmed or case-folded on the wire. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

Read tag 234 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[234];field?.name;   // "StipulationValue"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

Other String fields

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