Rule80A (FIX tag 47)

charFIX 4.2

Rule80A (tag 47) is a char field defined in FIX 4.2. It appears in 4 message types, always optionally. It is an enumerated field with 23 defined values.

At a glance

Tag
47
Name
Rule80A
Datatype
char
Dialects
FIX 4.2
Messages
4
Valid values
23

What the specification says

Note that the name of this field is changing to "OrderCapacity" as Rule80A is a very US market-specific term. Other world markets need to convey similar information, however, often a subset of the US values. . See the "Rule80A (aka OrderCapacity) Usage by Market" appendix for market-specific usage of this field.

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

A real message using tag 47

OrderSingle · FIX 4.2
TagFieldWire valueMeaning
8BeginStringFIX.4.2
9BodyLength132
35MsgTypeDOrder Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
21HandlInst1Automated execution order, private, no Broker intervention
55SymbolEUR/USD
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
47Rule80AAAgency single order
10CheckSum092
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.2 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
AAgency single orderAgencySingleOrder
BShort exempt transaction (refer to A type)ShortExemptTransactionAType
CProgram Order, non-index arb, for Member firm/orgProprietaryNonAlgo
DProgram Order, index arb, for Member firm/orgProgramOrderMember
ERegistered Equity Market Maker tradesShortExemptTransactionForPrincipal
FShort exempt transaction (refer to W type)ShortExemptTransactionWType
HShort exempt transaction (refer to I type)ShortExemptTransactionIType
IIndividual Investor, single orderIndividualInvestor
JProgram Order, index arb, for individual customerProprietaryAlgo
KProgram Order, non-index arb, for individual customerAgencyAlgo
LShort exempt transaction for member competing market-maker affiliated with the firm clearing the trade (refer to P and O types)ShortExemptTransactionMemberAffliated
MProgram Order, index arb, for other memberProgramOrderOtherMember
NProgram Order, non-index arb, for other memberAgentForOtherMember
OCompeting dealer tradesProprietaryTransactionAffiliated
PPrincipalPrincipal
RCompeting dealer tradesTransactionNonMember
SSpecialist tradesSpecialistTrades
TCompeting dealer tradesTransactionUnaffiliatedMember
UProgram Order, index arb, for other agencyAgencyIndexArb
WAll other orders as agent for other memberAllOtherOrdersAsAgentForOtherMember
XShort exempt transaction for member competing market-maker not affiliated with the firm clearing the trade (refer to W and T types)ShortExemptTransactionMemberNotAffliated
YProgram Order, non-index arb, for other agencyAgencyNonAlgo
ZShort exempt transaction for non-member competing market-maker (refer to A and R types)ShortExemptTransactionNonMember

Where tag 47 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
ExecutionReport8Optionaldirectly on the message body
OrderCancelReplaceRequestGOptionaldirectly on the message body
OrderListEOptionaldirectly on the message body
OrderSingleDOptionaldirectly on the message body

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 47 in TypeScript

decode.tsts
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix42";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const rule80A = message.fields[47]?.raw;// e.g. "A" — Agency single order// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(47)  ?.enumValues?.find((e) => e.value === rule80A)  ?.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-fix42