BenchmarkCurvePoint (FIX tag 222)

StringFIX 4.4

BenchmarkCurvePoint (tag 222) is a String field defined in FIX 4.4. It appears in 22 message types, always optionally.

At a glance

Tag: 222
Name: BenchmarkCurvePoint
Datatype: String
Dialects: FIX 4.4
Messages: 22

What the specification says

Point on benchmark curve. Free form values: e.g. "Y", "7Y", "INTERPOLATED". Sample values: M = combination of a number between 1-12 and a "M" for month Y = combination of number between 1-100 and a "Y" for year} 10Y-OLD = see above, then add "-OLD" when appropriate INTERPOLATED = the point is mathematically derived 2/2031 5 3/8 = the point is stated via a combination of maturity month / year and coupon See Fixed Income-specific documentation at http://www.fixprotocol.org for additional values. (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 222

NewOrderSingle · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	123
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
40	OrdType	1	Market
222	BenchmarkCurvePoint	EXAMPLE
10	CheckSum	211

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 222 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 SpreadOrBenchmarkCurveData component
AllocationReport	AS	Optional	inside the SpreadOrBenchmarkCurveData component
CollateralAssignment	AY	Optional	inside the SpreadOrBenchmarkCurveData component
CollateralInquiry	BB	Optional	inside the SpreadOrBenchmarkCurveData component
CollateralReport	BA	Optional	inside the SpreadOrBenchmarkCurveData component
CollateralRequest	AX	Optional	inside the SpreadOrBenchmarkCurveData component
CollateralResponse	AZ	Optional	inside the SpreadOrBenchmarkCurveData component
Confirmation	AK	Optional	inside the SpreadOrBenchmarkCurveData component
CrossOrderCancelReplaceRequest	t	Optional	inside the SpreadOrBenchmarkCurveData component
ExecutionReport	8	Optional	inside the SpreadOrBenchmarkCurveData component
IOI	6	Optional	inside the SpreadOrBenchmarkCurveData component
NewOrderCross	s	Optional	inside the SpreadOrBenchmarkCurveData component
NewOrderList	E	Optional	inside ListOrdGrp › SpreadOrBenchmarkCurveData
NewOrderSingle	D	Optional	inside the SpreadOrBenchmarkCurveData component
OrderCancelReplaceRequest	G	Optional	inside the SpreadOrBenchmarkCurveData component
Quote	S	Optional	inside the SpreadOrBenchmarkCurveData component
QuoteRequest	R	Optional	inside QuotReqGrp › SpreadOrBenchmarkCurveData
QuoteRequestReject	AG	Optional	inside QuotReqRjctGrp › SpreadOrBenchmarkCurveData
QuoteResponse	AJ	Optional	inside the SpreadOrBenchmarkCurveData component
QuoteStatusReport	AI	Optional	inside the SpreadOrBenchmarkCurveData component
SecurityList	y	Optional	inside SecListGrp › SpreadOrBenchmarkCurveData
TradeCaptureReport	AE	Optional	inside the SpreadOrBenchmarkCurveData component

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

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