ClearingInstruction (FIX tag 577)
ClearingInstruction (tag 577) is an int field defined in FIX 4.4. It appears in 3 message types, always optionally. It is an enumerated field with 14 defined values.
At a glance
- Tag
- 577
- Name
- ClearingInstruction
- Datatype
- int
- Dialects
- FIX 4.4
- Messages
- 3
- Valid values
- 14
What the specification says
Eligibility of this trade for clearing and central counterparty processing
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 577
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIX.4.4 | |
| 9 | BodyLength | 163 | |
| 35 | MsgType | J | Allocation Instruction |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 70 | AllocID | EXAMPLE | |
| 71 | AllocTransType | 0 | New |
| 626 | AllocType | 1 | Calculated (includes MiscFees and NetMoney) |
| 857 | AllocNoOrdersType | 0 | Not specified |
| 54 | Side | 1 | Buy |
| 53 | Quantity | 1000000 | |
| 6 | AvgPx | 1.09215 | |
| 75 | TradeDate | 20240101 | |
| 78 | NoAllocs1 entry | 1 | repeating group |
| 79 | AllocAccount | EXAMPLE | |
| 576 | NoClearingInstructions2 entries | 2 | repeating group |
| 577 | ClearingInstruction | 0 | process normally |
| 577 | ClearingInstruction | 0 | process normally |
| 10 | CheckSum | 066 |
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 |
|---|---|---|
| 0 | process normally | PROCESS_NORMALLY |
| 1 | exclude from all netting | EXCLUDE_FROM_ALL_NETTING |
| 2 | bilateral netting only | BILATERAL_NETTING_ONLY |
| 3 | ex clearing | EX_CLEARING |
| 4 | special trade | SPECIAL_TRADE |
| 5 | multilateral netting | MULTILATERAL_NETTING |
| 6 | clear against central counterparty | CLEAR_AGAINST_CENTRAL_COUNTERPARTY |
| 7 | exclude from central counterparty | EXCLUDE_FROM_CENTRAL_COUNTERPARTY |
| 8 | Manual mode (pre-posting and/or pre-giveup) | MANUAL_MODE |
| 9 | Automatic posting mode (trade posting to the position account number specified) | AUTOMATIC_POSTING_MODE |
| 10 | Automatic give-up mode (trade give-up to the give-up destination number specified) | AUTOMATIC_GIVE_UP_MODE |
| 11 | Qualified Service Representative (QSR) - | QUALIFIED_SERVICE_REPRESENTATIVE |
| 12 | Customer Trade | CUSTOMER_TRADE |
| 13 | Self clearing | SELF_CLEARING |
Where tag 577 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 AllocGrp › ClrInstGrp |
| AllocationReport | AS | Optional | inside AllocGrp › ClrInstGrp |
| TradeCaptureReport | AE | Optional | inside TrdCapRptSideGrp › ClrInstGrp |
Wire format
A whole number, optionally signed. Leading zeros are legal on the wire and are preserved in the raw value. @boarteam/fix parses the value as a number and reports parse/invalid-int when it does not lex as one; the raw string is kept either way.
Read tag 577 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 clearingInstruction = message.fields[577]?.raw;// e.g. "0" — process normally// The dictionary also carries the labels:const label = fix.dictionary .fieldByTag(577) ?.enumValues?.find((e) => e.value === clearingInstruction) ?.description;Other int fields
- 581AccountType
- 582CustOrderCapacity
- 569TradeRequestType
- 585MassStatusReqType
- 567TradSesStatusRejReason
- 565LegCoveredOrUncovered
- 563MultiLegRptTypeReq
- 560SecurityRequestResult
- 559SecurityListRequestType
- 557TotNoSecurityTypes
- 550CrossPrioritization
- 549CrossType
- 607LegProduct
- 538NestedPartyRole
- 537QuoteType
- 533TotalAffectedOrders
- 626AllocType
- 522OwnerType
- 519ContAmtType
- 638PriorityIndicator
- 507RegistRejReasonCode
- 658QuoteRequestRejectReason
- 495TaxAdvantageType
- 660AcctIDSource
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