ClearingFeeIndicator (FIX tag 635)
ClearingFeeIndicator (tag 635) is a String field defined in FIX 4.4. It appears in 9 message types, always optionally. It is an enumerated field with 14 defined values.
At a glance
- Tag
- 635
- Name
- ClearingFeeIndicator
- Datatype
- String
- Dialects
- FIX 4.4
- Messages
- 9
- Valid values
- 14
What the specification says
Indicates type of fee being assessed of the customer for trade executions at an exchange. Applicable for futures markets only at this time. (Values source CBOT, CME, NYBOT, and NYMEX):
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 635
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIX.4.4 | |
| 9 | BodyLength | 117 | |
| 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 | |
| 635 | ClearingFeeIndicator | B | CBOE Member |
| 54 | Side | 1 | Buy |
| 60 | TransactTime | 20240101-12:00:00.000 | |
| 40 | OrdType | 1 | Market |
| 10 | CheckSum | 020 |
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.
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.
| Value | Meaning | Symbolic name |
|---|---|---|
| B | CBOE Member | CBOE_MEMBER |
| C | Non-member and Customer | NON_MEMBER_AND_CUSTOMER |
| E | Equity Member and Clearing Member | EQUITY_MEMBER_AND_CLEARING_MEMBER |
| F | Full and Associate Member trading for own account and as floor Brokers | FULL_AND_ASSOCIATE_MEMBER_TRADING_FOR_OWN_ACCOUNT_AND_AS_FLOOR_BROKERS |
| H | 106.H and 106.J Firms | 106H_AND_106J_FIRMS |
| I | GIM, IDEM and COM Membership Interest Holders | GIM_IDEM_AND_COM_MEMBERSHIP_INTEREST_HOLDERS |
| L | Lessee and 106.F Employees | LESSEE_AND_106F_EMPLOYEES |
| M | All other ownership types | ALL_OTHER_OWNERSHIP_TYPES |
| 1 | 1st year delegate trading for his own account | 1ST_YEAR_DELEGATE_TRADING_FOR_HIS_OWN_ACCOUNT |
| 2 | 2nd year delegate trading for his own account | 2ND_YEAR_DELEGATE_TRADING_FOR_HIS_OWN_ACCOUNT |
| 3 | 3rd year delegate trading for his own account | 3RD_YEAR_DELEGATE_TRADING_FOR_HIS_OWN_ACCOUNT |
| 4 | 4th year delegate trading for his own account | 4TH_YEAR_DELEGATE_TRADING_FOR_HIS_OWN_ACCOUNT |
| 5 | 5th year delegate trading for his own account | 5TH_YEAR_DELEGATE_TRADING_FOR_HIS_OWN_ACCOUNT |
| 9 | 6th year and beyond delegate trading for his own account | 6TH_YEAR_AND_BEYOND_DELEGATE_TRADING_FOR_HIS_OWN_ACCOUNT |
Where tag 635 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 |
|---|---|---|---|
| CrossOrderCancelReplaceRequest | t | Optional | inside the SideCrossOrdModGrp component |
| ExecutionReport | 8 | Optional | directly on the message body |
| MultilegOrderCancelReplace | AC | Optional | directly on the message body |
| NewOrderCross | s | Optional | inside the SideCrossOrdModGrp component |
| NewOrderList | E | Optional | inside the ListOrdGrp component |
| NewOrderMultileg | AB | Optional | directly on the message body |
| NewOrderSingle | D | Optional | directly on the message body |
| OrderCancelReplaceRequest | G | Optional | directly on the message body |
| TradeCaptureReportAck | AR | Optional | directly on the message body |
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 635 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 clearingFeeIndicator = message.fields[635]?.raw;// e.g. "B" — CBOE Member// The dictionary also carries the labels:const label = fix.dictionary .fieldByTag(635) ?.enumValues?.find((e) => e.value === clearingFeeIndicator) ?.description;Other String fields
- 628HopCompID
- 644RFQReqID
- 625TradingSessionSubID
- 649QuoteStatusReqID
- 620LegSecurityDesc
- 617LegIssuer
- 654LegRefID
- 655ContraLegRefID
- 659SideComplianceID
- 609LegSecurityType
- 608LegCFICode
- 606LegSecurityAltIDSource
- 664ConfirmID
- 605LegSecurityAltID
- 603LegSecurityIDSource
- 602LegSecurityID
- 601LegSymbolSfx
- 600LegSymbol
- 599LegInstrRegistry
- 671LegAllocAccount
- 598LegLocaleOfIssue
- 672LegIndividualAllocID
- 597LegStateOrProvinceOfIssue
- 674LegAllocAcctIDSource
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