ClearingInstruction (FIX tag 577)

intFIX 4.4

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

AllocationInstruction · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength163
35MsgTypeJAllocation Instruction
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
70AllocIDEXAMPLE
71AllocTransType0New
626AllocType1Calculated (includes MiscFees and NetMoney)
857AllocNoOrdersType0Not specified
54Side1Buy
53Quantity1000000
6AvgPx1.09215
75TradeDate20240101
78NoAllocs1 entry1repeating group
79AllocAccountEXAMPLE
576NoClearingInstructions2 entries2repeating group
577ClearingInstruction0process normally
577ClearingInstruction0process normally
10CheckSum066
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
0process normallyPROCESS_NORMALLY
1exclude from all nettingEXCLUDE_FROM_ALL_NETTING
2bilateral netting onlyBILATERAL_NETTING_ONLY
3ex clearingEX_CLEARING
4special tradeSPECIAL_TRADE
5multilateral nettingMULTILATERAL_NETTING
6clear against central counterpartyCLEAR_AGAINST_CENTRAL_COUNTERPARTY
7exclude from central counterpartyEXCLUDE_FROM_CENTRAL_COUNTERPARTY
8Manual mode (pre-posting and/or pre-giveup)MANUAL_MODE
9Automatic posting mode (trade posting to the position account number specified)AUTOMATIC_POSTING_MODE
10Automatic give-up mode (trade give-up to the give-up destination number specified)AUTOMATIC_GIVE_UP_MODE
11Qualified Service Representative (QSR) -QUALIFIED_SERVICE_REPRESENTATIVE
12Customer TradeCUSTOMER_TRADE
13Self clearingSELF_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.

MessageMsgTypeRequirednessWhere in the message
AllocationInstructionJOptionalinside AllocGrp › ClrInstGrp
AllocationReportASOptionalinside AllocGrp › ClrInstGrp
TradeCaptureReportAEOptionalinside 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

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

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