# FIX Standard Errors and Omissions 2026

**URL:** <https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2026/18086>\
**Category:** General Q&A\
**Tags:** errors, fixlatest\
**Created:** [February 22, 2026, 1:48pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2026/18086 "2026-02-22T13:48:45Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![gtcpm](https://avatars.discourse-cdn.com/v4/letter/g/b2d939/32.png) [@gtcpm](https://forum.fixtrading.org/u/gtcpm)\
**Post date:** [February 22, 2026, 1:48pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2026/18086/1 "2026-02-22T13:48:45Z")

</div>

This thread is intended to capture errors and omissions discovered in the FIX Standard during 2026, 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)

---

<div class="post-metadata">

**Author:** ![martinat](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.fixtrading.org/martinat/32/776_2.png) [@martinat](https://forum.fixtrading.org/u/martinat)\
**Post date:** [February 23, 2026, 2:07pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2026/18086/2 "2026-02-23T14:07:09Z")

</div>

Fields `IOIid` and `AvdId` do not follow FIX field naming conventions using “`ID`”

Orchestra 4.2  
`<fixr:field id="23" name="IOIid" type="String" added="FIX.2.7">`  
`<fixr:field id="3" name="AdvRefID" type="String" added="FIX.2.7">`  
`<fixr:field id="2" name="AdvId" type="String" added="FIX.2.7">`

Orchestra 4.4  
`<fixr:field id="23" name="IOIID" type="String" added="FIX.2.7" abbrName="IOIID" baseCategory="Indication" baseCategoryAbbrName="ID">`  
`<fixr:field id="3" name="AdvRefID" type="String" added="FIX.2.7" abbrName="AdvRefID">`  
`<fixr:field id="2" name="AdvId" type="String" added="FIX.2.7" abbrName="AdvId">`

Orchestra FIX Latest  
`<fixr:field type="String" baseCategory="Indication" baseCategoryAbbrName="ID" id="23" name="IOIID" abbrName="IOIID" added="FIX.2.7">`  
`<fixr:field type="String" id="3" name="AdvRefID" abbrName="AdvRefID" added="FIX.2.7">`  
`<fixr:field type="String" id="2" name="AdvId" abbrName="AdvId" added="FIX.2.7">`

Required changes:

1. Rename `IOIid` → `IOIID` in FIX 4.2
2. Rename `AdvId` → `AdvID` in FIX 4.2, FIX 4.4 and FIX Latest

---

<div class="post-metadata">

**Author:** ![martinat](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.fixtrading.org/martinat/32/776_2.png) [@martinat](https://forum.fixtrading.org/u/martinat)\
**Post date:** [February 23, 2026, 2:11pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2026/18086/3 "2026-02-23T14:11:45Z")

</div>

Legacy versions of FIXimate [4.0-4.2] are incorrectly using message names `OrderSingle` and `OrderList`.

In the source documentation the `MsgType` comments refer to “Order - Single” and “Order - List” but the message descriptions clearly use `New Order - Single` and `New Order -List`.

This issue is also present in the Orchestra XML for 4.2 where the `MsgType` values do not match message names.

```xml
<fixr:codeSet name="MsgTypeCodeSet" id="35" type="String">
  <fixr:code name="NewOrderSingle" id="35014" value="D" sort="13" added="FIX.2.7">
    <fixr:annotation>
      <fixr:documentation purpose="SYNOPSIS">Order Single</fixr:documentation>
    </fixr:annotation>
  </fixr:code>
  <fixr:code name="NewOrderList" id="35015" value="E" sort="14" added="FIX.2.7">
    <fixr:annotation>
      <fixr:documentation purpose="SYNOPSIS">Order List</fixr:documentation>
    </fixr:annotation>
  </fixr:code>
</fixr:codeSet>

```

```xml
<fixr:message name="OrderSingle" id="14" msgType="D" category="SingleGeneralOrderHandling" added="FIX.2.7">
  <fixr:structure>
    <fixr:componentRef id="1001" presence="required" added="FIX.2.7">
      <fixr:annotation>
        <fixr:documentation>MsgType = D</fixr:documentation>
      </fixr:annotation>
    </fixr:componentRef>
  </fixr:structure>
</fixr:message>
<fixr:message name="OrderList" id="15" msgType="E" category="ProgramTrading" added="FIX.2.7">
  <fixr:structure>
    <fixr:componentRef id="1001" presence="required" added="FIX.2.7">
      <fixr:annotation>
        <fixr:documentation>MsgType = E</fixr:documentation>
      </fixr:annotation>
    </fixr:componentRef>
  </fixr:structure>
</fixr:message>

```

---

<div class="post-metadata">

**Author:** ![ltaikit](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.fixtrading.org/ltaikit/32/743_2.png) [@ltaikit](https://forum.fixtrading.org/u/ltaikit)\
**Post date:** [February 23, 2026, 2:20pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2026/18086/4 "2026-02-23T14:20:39Z")

</div>

Martin, in the legacy versions of FIX those were the official message names. They are correct names for those versions.

---

<div class="post-metadata">

**Author:** ![martinat](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.fixtrading.org/martinat/32/776_2.png) [@martinat](https://forum.fixtrading.org/u/martinat)\
**Post date:** [February 23, 2026, 2:22pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2026/18086/5 "2026-02-23T14:22:50Z")

</div>

Orchestra identifiers should map uniquely to a single semantic name and should not be reassigned or recycled.

**Issue:** Component IDs for `StandardHeader` and `StandardTrailer` were recycled in FIX 4.4. Component IDs **1001** and **1002** break the one-to-one mapping between identifiers and semantic names.

Orchestra FIX 4.2

```auto
<fixr:component name="StandardHeader" id="1001" category="Session" added="FIX.4.0">
<fixr:component name="StandardTrailer" id="1002" category="Session" added="FIX.4.0">

```

Orchestra FIX 4.4

```auto
<fixr:component category="Session" added="FIX.4.0" id="1024" name="StandardHeader" abbrName="Hdr">
<fixr:component category="Session" added="FIX.4.0" id="1025" name="StandardTrailer" abbrName="Trlr">
<fixr:component category="Common" added="FIX.4.4" id="1001" name="DiscretionInstructions" abbrName="DiscInstr">
<fixr:component category="Common" added="FIX.4.4" id="1002" name="FinancingDetails" abbrName="FinDetls">

```

Orchestra FIX Latest

```auto
<fixr:component category="Session" added="FIX.4.0" updated="FIX.Latest" updatedEP="271" id="1024" name="StandardHeader" abbrName="Hdr">
<fixr:component category="Session" added="FIX.4.0" id="1025" name="StandardTrailer" abbrName="Trlr">
<fixr:component category="Common" added="FIX.4.4" id="1001" name="DiscretionInstructions" abbrName="DiscInstr">
<fixr:component category="Common" added="FIX.4.4" updated="FIX.5.0SP2" updatedEP="161" id="1002" name="FinancingDetails" abbrName="FinDetls">

```

---

<div class="post-metadata">

**Author:** ![martinat](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.fixtrading.org/martinat/32/776_2.png) [@martinat](https://forum.fixtrading.org/u/martinat)\
**Post date:** [February 23, 2026, 2:36pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2026/18086/6 "2026-02-23T14:36:40Z")

</div>

The Orchestra XML for FIX 4.2 should use consistent names for `message.name` and `MsgTypeCodeSet/code.name`.

Note the original source specification for FIX 2.7 refers to New Order Single.

 ![Screenshot 2026-02-23 at 14.29.33](https://canada1.discourse-cdn.com/flex010/uploads/fixtrading2/original/1X/bf2ac800ada7427eca49051a35ab0dcb23ee79cd.png)

---

<div class="post-metadata">

**Author:** ![martinat](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.fixtrading.org/martinat/32/776_2.png) [@martinat](https://forum.fixtrading.org/u/martinat)\
**Post date:** [February 23, 2026, 2:43pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2026/18086/7 "2026-02-23T14:43:18Z")

</div>

In FIX 4.0 the description for code `EncryptMethodCodeSet=4[PGPDES]` was updated to include “defunct”. Can this code be marked as deprecated?

The following code definition appears in Orchestra 4.2, 4.4 and FIX.Latest:

```xml
<fixr:codeSet type="int" id="98" name="EncryptMethodCodeSet" added="FIX.2.7">
  ...
  <fixr:code value="4" sort="5" id="98005" name="PGPDES" added="FIX.3.0">
    <fixr:annotation>
      <fixr:documentation purpose="SYNOPSIS">
                    PGP / DES (Defunct)</fixr:documentation>
    </fixr:annotation>
  </fixr:code>

```

The release notes for FIX 4.0 only reference _adding_ new codes:

_5. Additional enumerations have been added to the EncryptMethod(98) field._

---

<div class="post-metadata">

**Author:** ![ltaikit](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.fixtrading.org/ltaikit/32/743_2.png) [@ltaikit](https://forum.fixtrading.org/u/ltaikit)\
**Post date:** [February 23, 2026, 2:52pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2026/18086/8 "2026-02-23T14:52:55Z")

</div>

I stand corrected 👍

---

<div class="post-metadata">

**Author:** ![martinat](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.fixtrading.org/martinat/32/776_2.png) [@martinat](https://forum.fixtrading.org/u/martinat)\
**Post date:** [February 24, 2026, 7:43pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2026/18086/9 "2026-02-24T19:43:44Z")

</div>

The Orchestra XML for FIX 4.2 does not include a definition for `SettlCurrFxRateCalcCodeSet`, which was introduced in FIX 4.1.

```auto
<fixr:field type="char" id="156" name="SettlCurrFxRateCalc" added="FIX.4.1">
  <fixr:annotation>
    <fixr:documentation purpose="SYNOPSIS">Specifies whether or not SettlCurrFxRate should be multiplied or divided.</fixr:documentation>
  </fixr:annotation>
</fixr:field>

```

 ![Screenshot 2026-02-24 at 19.38.58](https://canada1.discourse-cdn.com/flex010/uploads/fixtrading2/original/1X/b7fea7cfa7d0659be86301811b04f3a5401d74d2.png)

---

<div class="post-metadata">

**Author:** ![martinat](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.fixtrading.org/martinat/32/776_2.png) [@martinat](https://forum.fixtrading.org/u/martinat)\
**Post date:** [February 24, 2026, 8:06pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2026/18086/10 "2026-02-24T20:06:28Z")

</div>

The Orchestra XML for FIX 4.2 does not include a definition for `SettlDeliveryTypeCodeSet`, which was introduced in FIX 4.1.

```auto
<fixr:field type="int" id="172" name="SettlDeliveryType" added="FIX.4.1">
  <fixr:annotation>
    <fixr:documentation purpose="SYNOPSIS">Identifies type of settlement</fixr:documentation>
  </fixr:annotation>
</fixr:field>

```

 ![Screenshot 2026-02-24 at 20.04.06](https://canada1.discourse-cdn.com/flex010/uploads/fixtrading2/original/1X/7bdb28f0a17b1d1b7321a3a94ee93ee7647a2baa.png)

---

<div class="post-metadata">

**Author:** ![gtcpm](https://avatars.discourse-cdn.com/v4/letter/g/b2d939/32.png) [@gtcpm](https://forum.fixtrading.org/u/gtcpm)\
**Post date:** [February 24, 2026, 8:31pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2026/18086/11 "2026-02-24T20:31:09Z")

</div>

Agree, looks like the error was only corrected in FIX 4.4. [SettlCurrFxRateCalc(156)](https://fiximate.fixtrading.org/en/FIX.Latest/tag156.html) should have a code set in FIX 4.2.

---

<div class="post-metadata">

**Author:** ![gtcpm](https://avatars.discourse-cdn.com/v4/letter/g/b2d939/32.png) [@gtcpm](https://forum.fixtrading.org/u/gtcpm)\
**Post date:** [February 24, 2026, 9:33pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2026/18086/12 "2026-02-24T21:33:27Z")

</div>

Agree, looks like the error was only corrected in FIX 4.4. [SettlDeliveryType(172)](https://fiximate.fixtrading.org/en/FIX.Latest/tag172.html) should have a code set in FIX 4.2.

---

<div class="post-metadata">

**Author:** ![martinat](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.fixtrading.org/martinat/32/776_2.png) [@martinat](https://forum.fixtrading.org/u/martinat)\
**Post date:** [March 10, 2026, 1:47pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2026/18086/13 "2026-03-10T13:47:51Z")

</div>

BidTypeCodeSet (added in FIX 4.2) is missing from the Orchestra XML for FIX 4.2. It is present in 4.2 and FIX.Latest Orchestra XML specs.

```xml
<fixr:field type="int" id="394" name="BidType" added="FIX.4.2">
  <fixr:annotation>
    <fixr:documentation purpose="SYNOPSIS">Code to identify the type of Bid Request.</fixr:documentation>
  </fixr:annotation>
</fixr:field>

```

 ![Screenshot 2026-03-10 at 13.46.09](https://canada1.discourse-cdn.com/flex010/uploads/fixtrading2/original/1X/ea4f7b57ba0678314116a9e40c021c68770ad971.png)

---

<div class="post-metadata">

**Author:** ![martinat](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.fixtrading.org/martinat/32/776_2.png) [@martinat](https://forum.fixtrading.org/u/martinat)\
**Post date:** [March 10, 2026, 1:52pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2026/18086/14 "2026-03-10T13:52:59Z")

</div>

BidDescriptorTypeCodeSet (added in FIX 4.2) is missing from the Orchestra XML for FIX 4.2. It is present in 4.2 and FIX.Latest Orchestra XML specs.

```xml
<fixr:field type="int" id="399" name="BidDescriptorType" added="FIX.4.2">
  <fixr:annotation>
    <fixr:documentation purpose="SYNOPSIS">Code to identify the type of BidDescriptor.</fixr:documentation>
  </fixr:annotation>
</fixr:field>

```

 ![Screenshot 2026-03-10 at 13.52.36](https://canada1.discourse-cdn.com/flex010/uploads/fixtrading2/original/1X/d926ac8221bf9003f9333760071f85e030d34eb7.png)

---

<div class="post-metadata">

**Author:** ![martinat](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.fixtrading.org/martinat/32/776_2.png) [@martinat](https://forum.fixtrading.org/u/martinat)\
**Post date:** [March 10, 2026, 2:01pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2026/18086/15 "2026-03-10T14:01:42Z")

</div>

SideValueIndCodeSet (added in FIX 4.2) is missing from the Orchestra XML for FIX 4.2.

```xml
<fixr:field type="int" id="401" name="SideValueInd" added="FIX.4.2">
  <fixr:annotation>
    <fixr:documentation purpose="SYNOPSIS">Code to identify which "SideValue" the value refers to. SideValue1 and SideValue2 are used as opposed to Buy or Sell so that the basket can be quoted either way as Buy or Sell.</fixr:documentation>
  </fixr:annotation>
</fixr:field>

```

Orchestra XML for FIX 4.4 is missing codeSet pedigree, and code pedigree values are incorrect (should be FIX 4.2)

```xml
<fixr:codeSet type="int" id="401" name="SideValueIndCodeSet">
  <fixr:code value="1" id="401001" name="SideValue1" added="FIX.4.3">
    <fixr:annotation>
      <fixr:documentation purpose="SYNOPSIS">
     SideValue1
  </fixr:documentation>
    </fixr:annotation>
  </fixr:code>
  <fixr:code value="2" id="401002" name="SideValue2" added="FIX.4.3">
    <fixr:annotation>
      <fixr:documentation purpose="SYNOPSIS">
     SideValue 2
  </fixr:documentation>
    </fixr:annotation>
  </fixr:code>
</fixr:codeSet>

```

Orchestra XML for FIX Latest has correct codeSet pedigree, but code pedigree values are also incorrect (should be FIX 4.2)

```xml
<fixr:codeSet type="int" id="401" name="SideValueIndCodeSet" added="FIX.4.2">
  <fixr:code value="1" sort="1" id="401001" name="SideValue1" added="FIX.4.3">
    <fixr:annotation>
      <fixr:documentation purpose="SYNOPSIS">
                    Side Value 1</fixr:documentation>
    </fixr:annotation>
  </fixr:code>
  <fixr:code value="2" sort="2" id="401002" name="SideValue2" added="FIX.4.3">
    <fixr:annotation>
      <fixr:documentation purpose="SYNOPSIS">
                    Side Value 2</fixr:documentation>
    </fixr:annotation>
  </fixr:code>
</fixr:codeSet>

```

 ![Screenshot 2026-03-10 at 13.54.05](https://canada1.discourse-cdn.com/flex010/uploads/fixtrading2/original/1X/e546f287c4a14e93d30a2a12407f72c2c26f6ac7.png)

---

<div class="post-metadata">

**Author:** ![gtcpm](https://avatars.discourse-cdn.com/v4/letter/g/b2d939/32.png) [@gtcpm](https://forum.fixtrading.org/u/gtcpm)\
**Post date:** [March 10, 2026, 9:16pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2026/18086/16 "2026-03-10T21:16:59Z")

</div>

@martinat thank you for raising the issues above, which are quite similar in nature. It seems that the [Basic and Unified Repository published for FIX 4.2](https://www.fixtrading.org/packages/fix-repository-2010/) at the time were missing enumerations for a number of fields that do show a list in the specification. These inconsistencies were corrected in FIX 4.3, albeit with a pedigree showing the version it was corrected in.

The [Orchestra representation of FIX 4.2](https://github.com/FIXTradingCommunity/orchestrations/tree/master/FIX%20Standard) hence has the same error as the legacy repository formats and will be fixed in the Orchestra XML file. We will also analyse the pedigree issues and correct them.

---

<div class="post-metadata">

**Author:** ![martinat](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.fixtrading.org/martinat/32/776_2.png) [@martinat](https://forum.fixtrading.org/u/martinat)\
**Post date:** [March 11, 2026, 11:30am UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2026/18086/17 "2026-03-11T11:30:45Z")

</div>

ListStatusTypeCodeSet (added in FIX 4.2) is missing from the Orchestra XML for FIX 4.2.

```xml
    <fixr:field type="int" id="429" name="ListStatusType" added="FIX.4.2">
      <fixr:annotation>
        <fixr:documentation purpose="SYNOPSIS">Code to represent the price type.</fixr:documentation>
      </fixr:annotation>
    </fixr:field>

```

Pedigree information in FIX 4.4 and FIX Latest is incorrect, should be added FIX 4.2.

```xml
<fixr:codeSet type="int" id="429" name="ListStatusTypeCodeSet">
  <fixr:code value="1" id="429001" name="Ack" added="FIX.4.3">
    <fixr:annotation>
      <fixr:documentation purpose="SYNOPSIS">
     Ack
  </fixr:documentation>
    </fixr:annotation>
  </fixr:code>
  <fixr:code value="2" id="429002" name="Response" added="FIX.4.3">
    <fixr:annotation>
      <fixr:documentation purpose="SYNOPSIS">
     Response
  </fixr:documentation>
    </fixr:annotation>
  </fixr:code>
  <fixr:code value="3" id="429003" name="Timed" added="FIX.4.3">
    <fixr:annotation>
      <fixr:documentation purpose="SYNOPSIS">
     Timed
  </fixr:documentation>
    </fixr:annotation>
  </fixr:code>
  <fixr:code value="4" id="429004" name="ExecStarted" added="FIX.4.3">
    <fixr:annotation>
      <fixr:documentation purpose="SYNOPSIS">
     ExecStarted
  </fixr:documentation>
    </fixr:annotation>
  </fixr:code>
  <fixr:code value="5" id="429005" name="AllDone" added="FIX.4.3">
    <fixr:annotation>
      <fixr:documentation purpose="SYNOPSIS">
     AllDone
  </fixr:documentation>
    </fixr:annotation>
  </fixr:code>
  <fixr:code value="6" id="429006" name="Alert" added="FIX.4.3">
    <fixr:annotation>
      <fixr:documentation purpose="SYNOPSIS">
     Alert
  </fixr:documentation>
    </fixr:annotation>
  </fixr:code>
</fixr:codeSet>

```

---

<div class="post-metadata">

**Author:** ![martinat](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.fixtrading.org/martinat/32/776_2.png) [@martinat](https://forum.fixtrading.org/u/martinat)\
**Post date:** [March 11, 2026, 11:33am UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2026/18086/18 "2026-03-11T11:33:52Z")

</div>

Same issue applies to `ListOrderStatusCodeSet`

```xml
<fixr:field type="int" id="431" name="ListOrderStatus" added="FIX.4.2">
  <fixr:annotation>
    <fixr:documentation purpose="SYNOPSIS">Code to represent the status of a list order.</fixr:documentation>
  </fixr:annotation>
</fixr:field>

```

---

<div class="post-metadata">

**Author:** ![gtcpm](https://avatars.discourse-cdn.com/v4/letter/g/b2d939/32.png) [@gtcpm](https://forum.fixtrading.org/u/gtcpm)\
**Post date:** [March 11, 2026, 4:07pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2026/18086/19 "2026-03-11T16:07:45Z")

</div>

@martinat thanks again, here is the current list of fields that do not show enumerated values for FIX 4.2 in the [legacy FIXimate](https://fiximate.fixtrading.org/legacy/index.html):

> - SettlCurrFxRateCalc(156)
> - SettlDeliveryType(172)
> - BidType(394)
> - BidDescriptorType(399)
> - SideValueInd(401)
> - ListStatusType(429)
> - ListOrderStatus(431)

To be extended if necessary…

---

<div class="post-metadata">

**Author:** ![martinat](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.fixtrading.org/martinat/32/776_2.png) [@martinat](https://forum.fixtrading.org/u/martinat)\
**Post date:** [March 13, 2026, 6:46pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2026/18086/20 "2026-03-13T18:46:35Z")

</div>

Typo in code name [IncorrectAveragegPrice](https://orchimate.org/-/fix-4.2/4.2/codeSets/AllocRejCodeCodeSet) for field `AllocRejCode(88)` in Orchestra XML FIX 4.2 and 4.4.

```xml
  <fixr:code value="2" id="88003" name="IncorrectAveragegPrice" added="FIX.2.7">
    <fixr:annotation>
      <fixr:documentation purpose="SYNOPSIS">
     incorrect average price
  </fixr:documentation>

```

[Next page](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2026/18086.md?page=2)