CommCurrency (FIX tag 479)

CurrencyFIX 4.4FIX 5.0 SP2

CommCurrency (tag 479) is a Currency field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 13 message types, always optionally.

At a glance

Tag
479
Name
CommCurrency
Datatype
Currency (String)
Dialects
FIX 4.4 and FIX 5.0 SP2
Messages
13

What the specification says

FIX 4.4

Specifies currency to be used for Commission (2) if the Commission currency is different from the Deal Currency - see "Appendix 6-A; Valid Currency Codes".

FIX 5.0 SP2

Specifies currency to be used for Commission(12) if the commission currency is different from the deal currency.

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

A real message using tag 479

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

Where tag 479 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.

MessageMsgTypeFIX 4.4FIX 5.0 SP2Where in the message
AllocationInstructionJOptionalOptionalinside AllocGrp › CommissionData
AllocationInstructionAlertBMOptionalinside AllocGrp › CommissionData
AllocationReportASOptionalOptionalinside AllocGrp › CommissionData
BidResponselOptionalOptionalinside BidCompRspGrp › CommissionData
ConfirmationAKOptionalOptionalinside the CommissionData component
CrossOrderCancelReplaceRequesttOptionalOptionalinside SideCrossOrdModGrp › CommissionData
ExecutionReport8OptionalOptionalinside the CommissionData component
MultilegOrderCancelReplaceACOptionalOptionalinside the CommissionData component
NewOrderCrosssOptionalOptionalinside SideCrossOrdModGrp › CommissionData
NewOrderListEOptionalOptionalinside ListOrdGrp › CommissionData
NewOrderMultilegABOptionalOptionalinside the CommissionData component
NewOrderSingleDOptionalOptionalinside the CommissionData component
OrderCancelReplaceRequestGOptionalOptionalinside the CommissionData component
TradeCaptureReportAEOptionalOptionalinside TrdCapRptSideGrp › CommissionData
TradeCaptureReportAckAROptionalinside TrdCapRptAckSideGrp › CommissionData

Wire format

A three-letter ISO 4217 code. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

Read tag 479 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 field = message.fields[479];field?.name;   // "CommCurrency"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

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