FundRenewWaiv (FIX tag 497)

charFIX 4.4

FundRenewWaiv (tag 497) is a char field defined in FIX 4.4. It appears in 13 message types, always optionally. It is an enumerated field with 2 defined values.

At a glance

Tag
497
Name
FundRenewWaiv
Datatype
char
Dialects
FIX 4.4
Messages
13
Valid values
2

What the specification says

A one character code identifying whether the Fund based renewal commission is to be waived.

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

A real message using tag 497

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength117
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
497FundRenewWaivYYes
10CheckSum049
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.

Valid values

A value outside this list is not a parse error — the message still decodes — but validate() reports it as validate/value-not-in-enum.

ValueMeaningSymbolic name
YYesYES
NNoNO

Where tag 497 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 AllocGrp › CommissionData
AllocationReportASOptionalinside AllocGrp › CommissionData
BidResponselOptionalinside BidCompRspGrp › CommissionData
ConfirmationAKOptionalinside the CommissionData component
CrossOrderCancelReplaceRequesttOptionalinside SideCrossOrdModGrp › CommissionData
ExecutionReport8Optionalinside the CommissionData component
MultilegOrderCancelReplaceACOptionalinside the CommissionData component
NewOrderCrosssOptionalinside SideCrossOrdModGrp › CommissionData
NewOrderListEOptionalinside ListOrdGrp › CommissionData
NewOrderMultilegABOptionalinside the CommissionData component
NewOrderSingleDOptionalinside the CommissionData component
OrderCancelReplaceRequestGOptionalinside the CommissionData component
TradeCaptureReportAEOptionalinside TrdCapRptSideGrp › CommissionData

Wire format

A single character. Most char fields are enumerated, so the value is one of a fixed set rather than arbitrary text. @boarteam/fix keeps the value as a string and, for enumerated fields, reports validate/value-not-in-enum when it is not a defined value.

Read tag 497 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 fundRenewWaiv = message.fields[497]?.raw;// e.g. "Y" — Yes// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(497)  ?.enumValues?.find((e) => e.value === fundRenewWaiv)  ?.description;

Other char 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