FIX Standard Errors and Omissions 2025

,
1

This thread is intended to capture errors and omissions discovered in the FIX Standard during 2025, e.g. misspellings or gaffes in the description. These will eventually be reviewed by the Global Technical Committee (GTC) and be corrected with a standard Gap Analysis and a FIX Extension Pack.

Please report errors you may encounter when using the FIX Protocol. The GTC will use the same thread to capture issues it identifies.

Thank you,
GTC Project Management (gtcpm)

2

MsgType=P - AllocAckGrp/AllocText(161) has an incorrect comment: Can be used here to hold text relating to the rejection of this AllocAccount(366)). I thik this should be referencing AllocAccount(79).

3

Agree. Looks like the error was introduced when the AllocAckGrp fieldRef was updated in EP192-CME-Regulatory-Reporting-Enhancements.

<fixr:group name="AllocAckGrp" added="FIX.4.4" category="Allocation" abbrName="AllocAck" updatedEP="196" updated="FIX.5.0SP2" id="2002">
	...
    <fixr:fieldRef updatedEP="192" added="FIX.4.4" updated="FIX.5.0SP2" id="161">
        <fixr:annotation>
            <fixr:documentation>
                Can be used here to hold text relating to the rejection of this AllocAccount(366))</fixr:documentation>
        </fixr:annotation>
    </fixr:fieldRef>

Impacts messages: AllocationInstructionAck, AllocationReportAck

Noticed this is not the only instance of this type of error. For instance:

Line 46086: See EncodedSecurityDesc (35) field for description</fixr:documentation> // should be EncodedSecurityDesc(351)

<fixr:field name="EncodedLegSecurityDesc" added="FIX.4.3" type="data" abbrName="EncLegSecDesc" id="622" lengthId="621">
    <fixr:annotation>
        <fixr:documentation purpose="SYNOPSIS">
            Multileg instrument's individual security's EncodedSecurityDesc.</fixr:documentation>
        <fixr:documentation purpose="SYNOPSIS">
            See EncodedSecurityDesc (35) field for description</fixr:documentation>
    </fixr:annotation>
</fixr:field>

See FIX.Latest_EP299 Field #622

Line 46486: See BidPx (32) for description and valid values.</fixr:documentation>. // should be BidPx(132)

<fixr:field name="LegBidPx" added="FIX.4.4" type="Price" abbrName="BidPx" id="681">
    <fixr:annotation>
        <fixr:documentation purpose="SYNOPSIS">
            Bid price of this leg.</fixr:documentation>
        <fixr:documentation purpose="SYNOPSIS">
            See BidPx (32) for description and valid values.</fixr:documentation>
    </fixr:annotation>
</fixr:field>

See FIX.Latest_EP299 Field #681

Line number references are correct as of Orchestra EP299.

4

@jhaas and @martinat, thank you for raising these issues. We can confirm them and will capture them. Unfortunately there are more as follows:

  • Field definition of DerivativeEncodedIssuerLen(1277) refers to DerivativeEncodedSecurityDesc(1281) instead of DerivativeEncodedIssuer(1278), i.e. wrong field name and tag number.

  • Field usage description of DerivativeEncodedSecurityDescLen(1280) in component DerivativeInstrument refers to DerivativeEncodedSecurityDesc(1280) instead of DerivativeEncodedSecurityDesc(1281), i.e. wrong tag number.