StipulationValue (FIX tag 234)
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
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIX.4.4 | |
| 9 | BodyLength | 157 | |
| 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) |
| 234 | StipulationValue | EXAMPLE | |
| 233 | StipulationType | AMT | AMT (y/n) |
| 234 | StipulationValue | EXAMPLE | |
| 40 | OrdType | 1 | Market |
| 10 | CheckSum | 055 |
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.
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.
| Message | MsgType | Requiredness | Where in the message |
|---|---|---|---|
| AllocationInstruction | J | Optional | inside the Stipulations component |
| AllocationReport | AS | Optional | inside the Stipulations component |
| CollateralAssignment | AY | Optional | inside the Stipulations component |
| CollateralInquiry | BB | Optional | inside the Stipulations component |
| CollateralReport | BA | Optional | inside the Stipulations component |
| CollateralRequest | AX | Optional | inside the Stipulations component |
| CollateralResponse | AZ | Optional | inside the Stipulations component |
| Confirmation | AK | Optional | inside the Stipulations component |
| CrossOrderCancelReplaceRequest | t | Optional | inside the Stipulations component |
| ExecutionReport | 8 | Optional | inside the Stipulations component |
| IOI | 6 | Optional | inside the Stipulations component |
| NewOrderCross | s | Optional | inside the Stipulations component |
| NewOrderList | E | Optional | inside ListOrdGrp › Stipulations |
| NewOrderSingle | D | Optional | inside the Stipulations component |
| Quote | S | Optional | inside the Stipulations component |
| QuoteRequest | R | Optional | inside QuotReqGrp › Stipulations |
| QuoteRequestReject | AG | Optional | inside QuotReqRjctGrp › Stipulations |
| QuoteResponse | AJ | Optional | inside the Stipulations component |
| QuoteStatusReport | AI | Optional | inside the Stipulations component |
| SecurityList | y | Optional | inside SecListGrp › Stipulations |
| TradeCaptureReport | AE | Optional | inside 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
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 stringOther String fields
- 233StipulationType
- 235YieldType
- 239RepoCollateralSecurityType
- 243UnderlyingRepoCollateralSecurityType
- 222BenchmarkCurvePoint
- 221BenchmarkCurveName
- 250LegRepoCollateralSecurityType
- 217RoutingID
- 214SettlInstRefID
- 255CreditRating
- 256UnderlyingCreditRating
- 257LegCreditRating
- 262MDReqID
- 198SecondaryOrderID
- 196AllocLinkID
- 278MDEntryID
- 280MDEntryRefID
- 187CashSettlAgentContactPhone
- 186CashSettlAgentContactName
- 282MDEntryOriginator
- 185CashSettlAgentAcctName
- 283LocationID
- 184CashSettlAgentAcctNum
- 284DeskID
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